FDA record research

Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) — FDA decisions, comparisons and evidence

The 2021–2025 analysis contains 4 selected substantially-equivalent FDA decisions under primary product code PZI. Use it to compare documented submissions and evidence with your product. A separate 2026 update contains 1 decisions through 2026-09-27. The latest selected decision across the acquired endpoint is dated 2026-06-12. Neither set establishes a suitable predicate or the route for your device. The complete-year window has 4 decisions; the separate all-observed-date count is 14. These denominators describe different date ranges.

Evidence retrieved 2026-10-07. Source versions and topic-specific limits are listed below.

Recorded scope and its declared regulatory reference

An exact FDA-record regulation_number match to one acquired Title 21 section. Records with the same normalized scope definition, class, regulation and recorded submission/GMP flags are grouped. Sparse definitions and generic exemption boilerplate do not qualify. No text-similarity equivalence or legal applicability is inferred.

What scope does the FDA record describe?

Intended for use in near-patient testing settings for in vitro diagnostic, multiple-patient use for the quantitative determination of glucose throughout all hospital and all professional healthcare settings for use in determining dysglycemia.

Compare the proposed indication, user, anatomy, technology and operating principle with this actual scope; record differences and unresolved facts.

Cited source

Which current section does the record cite?

§ 862.1345 Glucose test system. (a) Identification. A glucose test system is a device intended to measure glucose quantitatively in blood and other body fluids. Glucose measurements are used in the diagnosis and treatment of carbohydrate metabolism disorders including diabetes mellitus, neonatal hypoglycemia, and idiopathic hypoglycemia, and of pancreatic islet cell carcinoma. (b) Classification. Class II (special controls). The device, when it is solely intended for use as a drink to test glucose tolerance, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 862.9. [52 FR 16122, May 1, 1987, as amended at 84 FR 71796, Dec. 30, 2019; 85 FR 18445, Apr. 2, 2020]

Read the identification, classification, conditions and referenced limitations in the cited section. A numeric reference match is not a buyer classification or exemption determination.

Cited source

Historical FDA comparison

2021–2025: five complete calendar years

Primary code PZI

All statistics in this section use decisions dated 2021-01-01 to 2025-12-31. The partial 2026 update below is excluded from these distributions.

4Selected decisions in these five years
WithheldMedian receipt-to-decision calendar days
4Valid date pairs in the distribution

There are 4 valid recent date pairs. Distribution summaries require at least 20; older records are not substituted for a current benchmark.

20210
20221
20230
20243
20250

Statistical source: FDA openFDA 510(k) decision dataset. Partition 1 Download the identified records and dates (CSV).

Filters, exclusions and reproducible calculation

Deduplicate by official submission ID across the complete current manifest partitions. Select exact primary product code, K-number format and the stated SE decision codes with valid dates. Recent distributions use the five complete calendar years preceding the latest valid endpoint decision year. Partial-year counts compare equal January-to-cutoff periods. Quartiles use linear interpolation at (n-1)*p and are withheld below 20 valid date pairs. The analysis n describes only its declared complete-year window; selected_se_n separately counts all selected recorded dates through the cutoff.

14 selected records across all observed dates; 0 other/invalid identifier or decision-date records excluded. 0 missing or invalid date pairs in the five-year window.

Date fields: date_received → decision_date. Quantiles: Hyndman–Fan type 7: linear interpolation at (n − 1) × p; displayed to one decimal; n ≥ 20 valid pairs.

Receipt-to-decision calendar elapsed time includes time outside active FDA review; it is not FDA review time, a promised project timeline or an estimate of future clearance. This selected recorded cohort does not include all applications or establish a success probability, predicate suitability, market size, current market availability or legal authorization for another product.

Calculation fda-buyer-research-3 · database cutoff 2026-09-27. CSV rows identify each official K-number, cohort, date pair, exclusion reason and source version.

Separate partial-year update

2026 decisions through 2026-09-27

1 selected decisions from 2026-01-01 to 2026-09-27. The equivalent previous-year period contains 0 decisions through 2025-09-27. These counts describe the records; they are not market growth or submission success rates.

Named records to investigate

Latest decisions across the database

These dated records may come from 2026 or earlier years. They are a separate investigation list, not the five-year statistical cohort. Compare the actual indications and technology before considering a record as a comparator.

Official record / deviceRecorded applicantDecisionRecorded typeCalendar days
K252323 ↗cobas pulse blood glucose monitoring systemRoche Diagnostics2026-06-12Dual Track322
K221349 ↗XPER Technology PREMIUM Pro Blood Glucose Monitoring SystemTaidoc Technology Corporation2024-11-19Dual Track925
K220272 ↗cobas pulse blood glucose monitoring systemRoche Diagnostics2024-04-26Dual Track816
K232075 ↗StatStrip Glucose Hospital Meter SystemNova Biomedical Corporation2024-02-23Dual Track226
K200788 ↗Assure Titanium Blood Glucose Monitoring SystemArkray, Inc.2022-05-23Dual Track788
K182552 ↗StatStrip Xpress Glucose Hospital Meter SystemNova Biomedical Corporation2018-12-13Dual Track87
K182549 ↗StatStrip Xpress 2 Glucose Hospital Meter SystemNova Biomedical Corporation2018-12-13Dual Track87
K181043 ↗StatStrip Glucose Hospital Meter SystemNova Biomedical Corporation2018-07-12Dual Track84

Supporting documents actually acquired

Go beyond the database row

Read the source context, then compare the evidence with your design. Topic locations below are text matches, including possible limitations or negative statements; they are not a mandatory test list.

The documents are a bounded sample of acquired summaries, not complete evidence coverage of the cohort.

Recorded classification context

Known context: US. Match the intended use and design with the recorded category before treating it as applicable.

Source factRecorded value
FDA product codePZI [1]
Generic device categoryPrescription Use Blood Glucose Meter For Near-Patient Testing [1]
Recorded scopeIntended for use in near-patient testing settings for in vitro diagnostic, multiple-patient use for the quantitative determination of glucose throughout all hospital and all professional healthcare settings for use in determining dysglycemia. [1]
Recorded class2 [1]
Regulation862.1345 [1]
Medical specialtyClinical Chemistry [1]

Build a comparison that explains the differences

Use this checklist to gather your business or product details before speaking with a specialist. The items below explain what to record and suggest useful supporting documents. You can add your own answers in the editable project brief.

  1. Which specific part of the recorded scope fits or differs?

    Put your proposed label and design beside the quoted definition. Record matching facts, differences and missing facts separately; naming the category alone cannot resolve scope.

    Useful evidence: Proposed indication/design and a definition-to-product comparison with source locators.

  2. Have the cited section and its limitations been reviewed?

    Record the applicable paragraph, conditions and cross-referenced limitations after specialist review. Keep a claimed exemption separate from actual establishment, listing and quality-system responsibilities.

    Useful evidence: Dated classification/route rationale and the current provisions relied on, with unresolved conditions.

  3. Compare your intended use with a named decision

    Choose a named record above. Put your proposed claim beside its actual indications-for-use statement. Record different patients, users, anatomy, settings and output claims; do not treat a shared code as proof of equivalence.

    Useful evidence: Your draft indications for use + the selected official summary and its exact page.

  4. Explain the technology and evidence differences

    For each comparison, record the different materials, hardware, software functions and operating conditions. Link each difference to existing evidence or an unresolved evaluation task.

    Useful evidence: A three-column matrix: comparator fact / your design fact / evidence or unresolved gap.

  5. Prepare a scope-based schedule without a sparse timing benchmark

    This recent cohort has fewer than 20 valid date pairs, so it supplies no median or percentile benchmark. Ask for a schedule based on actual preparation, evidence gaps, interactions and response assumptions; keep any historical decision context separately dated.

    Useful evidence: Document/test readiness, unresolved route/evidence tasks and the assumptions behind the specialist’s proposed sequence.

Work packages and dependencies

What needs to happen first

Questions for providers

Sources and data dates

Read the official document in context. The audit details identify the precise locators and preserved versions used for this page.

FDA openFDA — device classification records ↗

2026-10-05 · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D01 · snapshot 936de5f5d47b9293b702fc32512a79173969fb788c74a63d9b91abe73f3b86a5

  • [1] device-classification-0001-of-0001.json:results[2142] · record 5fd7994a1f6de0397317d86fdb6f9cf0f30cae6e8370228a27e9ca60d473ac7c

FDA 510(k) summary — K252323 ↗

Mon, 06 Jul 2026 18:32:04 GMT · retrieved 2026-10-06

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 334a6a27ca13ef1d26305b00b9644146efe37c7e946efb905ec4b9db2e4d336e

  • [2] PDF page 9 · record 0372ce0c4f9d685a3817f75e1f313ab81d0132d01437b052b7d35819321b9511
  • [3] PDF page 10 · record 3ac7e0f3b5935f4b58049a51d7877d0e2ef439af65ab5877fcdf90e9e9aa9510

FDA 510(k) summary — K221349 ↗

Wed, 20 Nov 2024 19:39:33 GMT · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 7c1c0d6adf5ead814f9467d66ea59b964d4374d8ddc550f657dfe5c636854a76

  • [5] PDF page 9 · record 3ea21b24826e40d4b2933b00798cfc495a6092c9f6dc98fcc1933c45fcd37a76

FDA 510(k) summary — K232075 ↗

Sat, 24 Feb 2024 22:21:34 GMT · retrieved 2026-10-07

Audit details: precise locators and snapshot identifiers

Source key D02 · snapshot 0de5882a1f4d9f4c28b73cb466dbed4ef9c417ab88b034b31258874d3408b01e

  • [6] PDF page 6 · record 192aefdd1c238832906b17c9a7d56148759d0de59e3d01307c1f9f1899a6c6a2

Prepare an editable project brief

Confirm the facts, scope and contact preference before sharing your project. Preparing this page sends no provider outreach.

Choose work packages to discuss

Compare FDA 510(k) Submission Services

Find FDA US Agent Services | Compare & Get Quotes · FDA QMSR Transition & Inspection Readiness (ISO 13485 Alignment)