Glucose Meter Software May Link Results to the Wrong Patient: How Can Medical Device Buyers Verify Identity Data?
Medical device buyers should test consecutive patient changes, barcode mapping and recovery from disruptions, and control software versions and event logs.
On October 6, 2026, the FDA published information on a global correction for Nova Biomedical StatStrip hospital glucose meters. A software issue may leave the previous patient's information on the screen. If the operator accepts that information, a new test result may be entered into the wrong patient's medical record. Incorrect data may lead to delayed treatment, unnecessary treatment or incorrect insulin use.
This incident shows that medical device procurement cannot focus only on measurement accuracy. Patient identification, barcode scanning, screen prompts and data transfer are also safety functions.
Procurement testing must cover the complete workflow
Buyers should test devices in real hospital workflows. Test scenarios should include testing several patients in succession, failed scans, repeated scans, network interruptions, returning to the previous screen and resuming operation after standby. At every step, testers should confirm that the patient information on the screen matches the record ultimately uploaded.
The system must not depend on operators remembering to clear old data. The interface should give a clear prompt when patients change and prevent an old identity from being automatically combined with a new result. Buyers should also check the mapping between the device, laboratory information systems, electronic medical records and barcode systems.
Keep software versions under control
Procurement contracts should specify software versions, configurations and responsibility for updates. When hospitals receive an update, they should first validate it in a test environment and then deploy it in stages. The equipment asset register should show each device's serial number, software version and deployment location.
Suppliers should also provide event logs. These logs should record patient scans, result generation, data transfer and user actions so that problems can be traced when an incident occurs.
A checklist buyers can put into practice now
- Test consecutive patient changes and scenarios in which old data remains.
- Check identity mapping between devices, barcodes and electronic medical records.
- Lock down software versions and configuration change procedures.
- Perform local validation before full deployment.
- Maintain a list of serial numbers, versions and locations of use.
- Confirm that event logs support problem investigation.
Source: U.S. FDA correction notice