FDA Classifies Nova StatStrip Gen 2 Hospital Glucose Meter Recall as Class I in 2026: Barcode Defect Can Mismatch Results to the Wrong Patient

FDA Classifies Nova StatStrip Gen 2 Hospital Glucose Meter Recall as Class I in 2026: Barcode Defect Can Mismatch Results to the Wrong Patient

On September 11, 2026, the U.S. Food and Drug Administration (FDA) classified a voluntary recall initiated by Nova Biomedical of its StatStrip (Gen 2) hospital glucose meters as a Class I recall, the most serious classification. The failure cited by FDA is a software synchronization and timing defect in the barcode scanning and patient data handling component: when a new barcode is scanned, the device intermittently retains the previous barcode, so patient identity may be attributed to the wrong person. If the operator does not notice and accepts the incorrect information, the current patient's glucose result is filed to the previous patient's record and transmitted to the Data Management System (DMS), while the current patient's record does not receive the result. The defect does not affect the analytical accuracy of the glucose measurement. The recall covers models including the MultiPack (Model 66739) and the Glucose and Ketone (Model 63683) configurations; the manufacturer has suspended shipments and plans to resolve the issue through a firmware update.

Recall Registration and Classification

On July 29, 2026, the FDA's Center for Devices and Radiological Health (CDRH) registered a voluntarily initiated recall by Nova Biomedical in its Medical Device Recall Database. On September 11, the FDA classified it as a Class I recall, the most severe level. The recall applies to the Nova StatStrip (Gen 2) hospital glucose meter series, including the MultiPack (Model 66739, recall number Z-3129-2026) and the Glucose and β-Ketone model (Model 63683, recall number Z-3130-2026), event number 99546.

Failure Mode

The failure cited by FDA is a software synchronization and timing defect in the barcode scanning and patient data handling component. When the device scans a new barcode, it intermittently retains the previously scanned barcode, covering both patient identity (ID) barcodes and quality control solution ID barcodes, with the result that the screen continues to display the information of the previous barcode.

Once an operator accepts the incorrectly displayed patient information without noticing the inconsistency, the current patient's glucose result is recorded in the previous patient's medical record and transmitted to the Data Management System (DMS). The current patient's record does not receive the result. For critically ill patients, neonates and infants who cannot express symptoms or act on their own behalf, a mismatched result may trigger inappropriate clinical intervention, while a missing record removes the basis for subsequent treatment decisions. The defect also affects quality control barcode scanning: quality control results may be linked to the wrong identifier, or quality control may fail without the user being able to identify the true cause.

FDA explicitly states that the defect does not affect the analytical accuracy of the glucose measurement. All software versions from 0.00.13.10 through 1.5.14.25 are affected. On July 29, the manufacturer issued an “URGENT MEDICAL DEVICE RECALL” customer notification by email to consignees and suspended shipments of the StatStrip (Gen 2) series pending development and validation of corrective action, with a firmware update targeted for September 2026.

Units Affected and Distribution Scope

In terms of quantities and distribution, 10,941 MultiPack units were in commercial distribution, together with 1,858 units of the Glucose and β-Ketone model. Distribution covers the entire United States and multiple markets outside the United States. The markets listed on the database page include Austria, Belgium, Bolivia, Brazil, Canada, the Cayman Islands, Chile, Croatia, the Dominican Republic, Finland, France, Germany, Ireland, Israel, Italy, the Netherlands, New Zealand, South Korea, Switzerland, Thailand, Turkey and the United Kingdom, among others.

The affected devices were cleared for marketing under 510(k) number K232075, product code PZI, regulation 21 CFR 862.1345, as a Class II glucose test system.

Interim Actions Recommended by the Manufacturer

The manufacturer's field safety notice provides four interim recommendations:

• After each patient barcode scan, and before accepting that patient's record or result, verify that the patient information displayed on the screen exactly matches the barcode that was scanned.
• If a mismatch occurs, stop using the device and notify the administrator.
• Forward the notice to all users within the facility and post it where the devices are stored and used.
• Complete and return the acknowledgement form.

The manufacturer states in the notice that it has received 24 related reports from U.S. customers.

Timeline

In terms of sequence, this recall followed an “act first, classify later” pattern: at the end of July the manufacturer issued the notice and stopped shipments, and in mid-September the FDA completed classification. For facilities currently using this series, manual verification remains the safeguard during the window before the firmware update is available.

AIMEILI Regulatory Interpretation

A Class I designation is assigned when a reasonable probability exists that use of a violative product will cause serious adverse health consequences or death. In this case, FDA's Class I classification was not driven by analytical measurement error — which FDA states is unaffected — but by the patient-identification and result-attribution pathway. A glucose value that is analytically correct but attached to the wrong patient is still a hazardous output, because clinical decisions for both patients may be based on incorrect data. This illustrates that for in vitro diagnostic systems, the identification, association and transfer of results are safety-critical functions in their own right.

Several regulatory themes are worth noting for manufacturers and registration holders:

• Software-related failure modes are treated with the same severity as analytical failure modes. A synchronization and timing defect in a scanning workflow is a design and human-factors issue, not merely an information technology issue, and was classified at the highest recall level.
• Corrective action by firmware requires verification and validation. The manufacturer suspended shipments pending development and validation of the correction. The validation package should demonstrate that the corrected software consistently discards or overwrites the prior barcode, that the displayed identifier always corresponds to the most recent scan, and that the correction does not introduce regression in other device functions.
• Change control implications. Depending on the nature and extent of the software change, a firmware update intended to correct a safety-related defect may require reassessment against the applicable premarket notification or approval requirements in each jurisdiction before release.
• Global vigilance obligations are not limited to the United States. Where the same devices are distributed in the European Union, Canada, the United Kingdom and other markets, corresponding field safety corrective action and reporting obligations are typically triggered under the applicable vigilance frameworks. Reporting timelines and terminology differ by jurisdiction, and the scope of a local action may differ from the U.S. record.
• Labeling and instructions for use. The interim manual verification step is effectively a temporary control. Interim controls of this kind should be traceable in the manufacturer's quality system and superseded by the permanent correction in a documented manner.

This article reflects an interpretation of publicly available regulatory information. It should not be treated as a conclusion or commitment regarding any specific product, company or registration application; the official original texts prevail, and the information may change as regulators and the manufacturer issue further updates.

Business Impact

• Inventory and shipment hold. Distributors and hospital customers holding the affected models face a shipping and deployment freeze while awaiting the firmware update, with consequent effects on order fulfillment, backorders and cold-chain or consumable planning linked to the meter platform.
• Operational burden at the point of care. The requirement to verify the displayed patient information against each scanned barcode before accepting a record adds a manual step to every glucose test. Facilities should expect workflow documentation, staff communication and competency checks, plus monitoring to confirm the step is actually performed.
• Data integrity and retrospective review. Results already filed to the wrong patient record in the DMS may require identification and correction. Hospitals may need to reconcile results, notify clinicians, and document the review under their own quality and accreditation systems, including corrective and preventive action processes.
• Supply chain and competitive dynamics. A Class I recall on a widely distributed point-of-care platform can prompt hospitals to review alternative meters, backup testing pathways or dual-vendor strategies, which may shift market share and affect tender and group purchasing arrangements.
• Contractual and financial exposure. Recall execution costs, service and support obligations, potential customer claims, and communication with group purchasing organizations and integrated delivery networks all require coordinated handling across manufacturers, distributors and service providers.
• Regulatory coordination across jurisdictions. Distributors, authorized representatives and importers in markets outside the United States should assess local reporting triggers, timelines and customer notification expectations, and align their communications with the manufacturer's field safety notice.
• Firmware deployment logistics. Installing and verifying the corrected firmware across a distributed fleet requires version tracking, installation evidence and confirmation that each unit in service has been updated, particularly where devices are shared across departments or held in reserve inventory.

Sources

• U.S. Food and Drug Administration (FDA) — Medical Device Recall Database (StatStrip Glucose Hospital Meter System MultiPack, Z-3129-2026), September 11, 2026. https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfRes/res.cfm?ID=221820
• U.S. Food and Drug Administration (FDA) — Medical Device Recall Database (StatStrip Glucose and Ketone Hospital Meter System, Z-3130-2026), September 11, 2026. https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfRes/res.cfm?ID=222044
• Nova Biomedical — StatStrip Global Medical Device Correction (Customer Advisory Notice 02-26NG), July 1, 2026. https://www.novabiomedical.com/statstrip-global-medical-device-correction

Scope of Verification and Applicability

Verification scope and access date: the FDA recall database records and the manufacturer's field safety notice pages listed above were reviewed; the access date was October 5, 2026. Corresponding announcements in other regulatory jurisdictions (for example, the European Union, Canada and the United Kingdom) were not individually verified, and their content may differ from the statements in this article. Applicability: this article is an interpretation of publicly available regulatory information and does not constitute a conclusion or commitment regarding any specific product, company or registration application. The official original texts prevail, and the information may change as regulators and the manufacturer issue subsequent updates.