What happened

A widely used hospital glucose meter has a software defect that can attach a patient's glucose result to the wrong person's medical record, and the fix is not available yet. Nova Biomedical calls the action a global Medical Device Correction, and the FDA published the company's announcement on October 6, 2026.

The issue affects the most recent model of the StatStrip Glucose Hospital Meter System, known as Gen 2.0. The earlier models (Gen 1.0, 1.75, 1.86 and 1.87) are not affected.

The wording of the action matters for how hospitals track it. The FDA page carries a company announcement, and the company describes the action as a correction rather than a recall.

What the software problem actually does

When a caregiver scans a patient ID barcode, information from a previous patient can remain on the meter screen. If that leftover information is accepted, the new glucose result is filed under the previous patient's record.

If nobody notices, clinical decisions can be made using another patient's glucose value. The company lists delayed treatment, unnecessary treatment including inappropriate insulin administration, and failure to treat the intended patient. Severity depends on the patient's real glucose status and condition, so the announcement does not describe a single outcome.

What the company has reported so far

On July 17, 2026, before the correction was initiated, Nova Biomedical received one report of an adverse event in the United States involving inappropriate insulin administration based on another patient's glucose results. The company says no adverse events were reported outside the United States for this issue and that no serious adverse events related to it have been reported.

The correction was initiated on July 24, 2026. The FDA published the announcement on October 6, a day after the company's own October 5 notice.

Which devices are covered

The correction applies to all serial numbers of six listed products: 63685 (StatStrip Glucose Hospital Meter System, US and global), 66739 (multipack, US and global), 63683 (glucose and beta-ketone meter, global excluding the US), 63726 (Japan), 63910 (UK and Canada version, global excluding the US) and 66249 (Rilibäk version, Germany). Device identifiers are published for each.

Because the scope is defined by product rather than by serial range, a hospital cannot resolve this by checking one lot or one build date. It has to match part numbers and device identifiers against its own inventory.

Nova has placed a shipment hold on all StatStrip Glucose Hospital Meter Systems while corrective actions are developed and validated. The company says it intends to roll out a software update in November 2026 in phases, and that the update will also carry non-safety improvements.

What staff are told to do until then

Enable patient validation and operator log settings, which the company says are already available in current StatStrip meters and in NovaNet middleware.

After every barcode scan, check on the device that the displayed patient ID belongs to the patient being tested, confirming name, date of birth and other identifiers on the Confirm Patient ID screen before pressing Accept.

After the result appears, verify again that the patient ID on the result screen belongs to the patient being tested. The company states that the ID shown at the time of the result should not be assumed to match the one verified at the time of scanning.

If a glucose level is assigned to the wrong patient, notify the administrator immediately. Where no alternative device is available, staff must keep following these steps until the software fix arrives. Where an alternative is available, the company says the affected device should not be used.

Concept graphic showing an identity check after scanning and another identity check at the result stage under CHECK TWICE.
Nova's interim guidance requires checking the patient's identity after the barcode scan and again when the result appears. Concept illustration.

Why the double check is the hard part

The recommended workflow asks a caregiver to verify patient identity twice per test, on a device often used in time-critical situations. That is a workable instruction and also a realistic source of error, which is one reason the announcement leads with configuration options rather than attention alone.

Which part numbers does a hospital own, and where are the meters used? Can patient validation and operator logging be enabled everywhere or only in some units? What record shows that staff were instructed and that misassigned results were monitored until the update arrives?

The timeline adds pressure. A phased rollout in November leaves some units running unpatched firmware for weeks, and the correction is global, so hospitals in several jurisdictions face the same constraint at once.

What patients and the public can take from this

This is a hospital device, so the affected population is patients whose glucose is measured on a StatStrip Gen 2.0 meter, not people using home glucose monitors. Nothing in the announcement suggests patients should change anything themselves.

If a patient is told that a glucose result was assigned to the wrong record, the step to take is raising it with the treating team, because the clinical risk lies in decisions made from the wrong value. The company's correction page and the FDA notice are the authoritative places to check part numbers and instructions.

Provider contacts are published: technical support in the United States at 1-800-545-6682 and in Canada at 1-800-263-5999, available around the clock, with customers elsewhere directed to their authorised distributor.

The open questions

The announcement does not say how many devices are in service, how many hospitals have been notified, or what share of the installed base runs the affected Gen 2.0 model. It does not explain how the defect arose, whether it affects one firmware version or several, or what a hospital should do if the November update slips.

The FDA page is a company announcement posted as a public service, and the agency states that posting it is not an endorsement of the product or the company. For anyone tracking the correction, the company's own page remains where instructions and the update schedule are expected to appear first.