Device type · PZI
Prescription Use Blood Glucose Meter For Near-Patient Testing
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
PZI
Clinical Chemistry
Device class
Class II
FDA decisions since 2015
13
510(k), De Novo and PMA
Adverse event reports
108
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Prescription Use Blood Glucose Meter For Near-Patient Testing
- Product code
- PZI
- Device class
- Class II
- Review panel
- Clinical Chemistry
- Regulation
- 21 CFR 862.1345
- FDA record
- Classification database entry for PZI
Latest FDA decisions
The 8 newest of 13 since 2015.
K252323 · Decided Jun 12, 2026 · 322 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K221349 · Decided Nov 19, 2024 · 925 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K220272 · Decided Apr 26, 2024 · 816 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K232075 · Decided Feb 23, 2024 · 226 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K200788 · Decided May 23, 2022 · 788 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K182549 · Decided Dec 13, 2018 · 87 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K182552 · Decided Dec 13, 2018 · 87 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
K181043 · Decided Jul 12, 2018 · 84 days after receipt
Device type: Prescription Use Blood Glucose Meter For Near-Patient Testing (PZI) · Laboratory Medicine & Pathology
Reports received
108
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
100
93% of reports
Injury reports
4
3.7% of reports
Death reports
4
3.7% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 0 | 0 | 0 | 0 |
| Jan 24 | 0 | 0 | 0 | 0 |
| Feb 24 | 0 | 0 | 0 | 0 |
| Mar 24 | 0 | 0 | 0 | 0 |
| Apr 24 | 0 | 0 | 0 | 0 |
| May 24 | 0 | 0 | 0 | 0 |
| Jun 24 | 0 | 0 | 0 | 0 |
| Jul 24 | 0 | 0 | 0 | 0 |
| Aug 24 | 0 | 0 | 0 | 0 |
| Sep 24 | 2 | 0 | 0 | 0 |
| Oct 24 | 1 | 0 | 0 | 0 |
| Nov 24 | 2 | 0 | 0 | 0 |
| Dec 24 | 0 | 0 | 0 | 0 |
| Jan 25 | 2 | 0 | 0 | 0 |
| Feb 25 | 1 | 0 | 0 | 0 |
| Mar 25 | 1 | 0 | 0 | 0 |
| Apr 25 | 2 | 0 | 0 | 0 |
| May 25 | 7 | 0 | 0 | 0 |
| Jun 25 | 15 | 0 | 0 | 0 |
| Jul 25 | 2 | 0 | 0 | 0 |
| Aug 25 | 0 | 0 | 0 | 0 |
| Sep 25 | 1 | 0 | 0 | 0 |
| Oct 25 | 0 | 0 | 0 | 0 |
| Nov 25 | 2 | 0 | 0 | 0 |
| Dec 25 | 2 | 0 | 0 | 0 |
| Jan 26 | 11 | 0 | 0 | 0 |
| Feb 26 | 4 | 0 | 0 | 0 |
| Mar 26 | 7 | 0 | 0 | 0 |
| Apr 26 | 9 | 1 | 0 | 0 |
| May 26 | 4 | 0 | 0 | 0 |
| Jun 26 | 4 | 0 | 1 | 0 |
| Jul 26 | 2 | 1 | 1 | 0 |
| Aug 26 | 4 | 1 | 2 | 0 |
| Sep 26 | 44 | 1 | 0 | 0 |
| Oct 26 | 7 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Computer Software Problem67
- Incorrect, Inadequate or Imprecise Result or Readings12
- Output Problem8
- Electrical /Electronic Property Problem4
- High Test Results3
- Low Test Results3
- Non Reproducible Results3
- Communication or Transmission Problem2
- Connection Problem2
- Incorrect Measurement2
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions100
- Insufficient Information8
- Hyperglycemia2
- Hypoglycemia1
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
Z-3128-2026 · Started Jul 29, 2026 · Posted by FDA Sep 11, 2026
Reason given: A software synchronization/timing issue in the barcode scanning and patient data processing component that causes the device to intermittently retain a previously scanned barcode including patient identification (ID) barcodes and quality control (QC) solution ID barcodes when a new barcode is scanned, resulting in the...
Cause as FDA categorized it: Software design
Z-3129-2026 · Started Jul 29, 2026 · Posted by FDA Sep 11, 2026
Reason given: A software synchronization/timing issue in the barcode scanning and patient data processing component that causes the device to intermittently retain a previously scanned barcode including patient identification (ID) barcodes and quality control (QC) solution ID barcodes when a new barcode is scanned, resulting in the...
Cause as FDA categorized it: Software design
Z-3130-2026 · Started Jul 29, 2026 · Posted by FDA Sep 11, 2026
Reason given: A software synchronization/timing issue in the barcode scanning and patient data processing component that causes the device to intermittently retain a previously scanned barcode including patient identification (ID) barcodes and quality control (QC) solution ID barcodes when a new barcode is scanned, resulting in the...
Cause as FDA categorized it: Software design
Z-3131-2026 · Started Jul 29, 2026 · Posted by FDA Sep 11, 2026
Reason given: A software synchronization/timing issue in the barcode scanning and patient data processing component that causes the device to intermittently retain a previously scanned barcode including patient identification (ID) barcodes and quality control (QC) solution ID barcodes when a new barcode is scanned, resulting in the...
Cause as FDA categorized it: Software design
Z-3132-2026 · Started Jul 29, 2026 · Posted by FDA Sep 11, 2026
Reason given: A software synchronization/timing issue in the barcode scanning and patient data processing component that causes the device to intermittently retain a previously scanned barcode including patient identification (ID) barcodes and quality control (QC) solution ID barcodes when a new barcode is scanned, resulting in the...
Cause as FDA categorized it: Software design
- StatStrip Glucose Hospital Meter System. Model/Catalog Number: 63685. Prescription use blood glucose meter for near-patient testing.Open, Classified
Z-0681-2025 · Started Nov 20, 2024 · Posted by FDA Dec 20, 2024
Reason given: A software bug within the Gen 2 StatStrip Hospital Meter firmware leads to transmission of erroneous glucose patient test results to a healthcare institution's data management system (DMS) at healthcare sites using WiFi if a user navigates to the Review Results screen while the meter is in the process of transmitting...
Cause as FDA categorized it: Software design
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.