| Catalog Number |
05060303001 |
| Medical Device Problem Code |
Patient Data Problem (3197)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
03/28/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
The investigation is ongoing.
|
| |
|
Event or Problem Description
|
|
The initial reporter stated there was an issue with an alleged patient result mismatch when using accu-chek inform ii meter serial number (b)(6).At 7:04 a.M., operator a performed a glucose test on patient a (with identifier ending with (b)(6) with the meter.Patient an id was correctly scanned and resulted 11.0 mmol/l on the meter.This result was transmitted to the customer's laboratory information system (lis) under the correct patient id (id ending with (b)(6).At 7:07 a.M., operator b performed a glucose test on patient b (id ending with (b)(6) using the meter.Patient b id was correctly scanned and resulted 7.7 mmol/l on the meter.When this result was transmitted to the lis, it was somehow tagged to patient a's id (ending with (b)(6) instead.Operator b checked on the meter and found that 2 results (11.0 mmol/l and 7.7 mmol/l) were both tagged to patient a's id (ending with (b)(6).The result for patient b (id ending with (b)(6) could not be found on the meter.The nurse in charge confirmed that the result of 7.7 mmol/l does not belong to patient a as the expected glucose result for patient a is around 10-11 mmol/l and a decrease of 3.3 mmol/l within 3 minutes was deemed not possible.Investigations performed at the customer site ruled out any possibility of a user error such as accidentally scanning the wrong patient id.The patients were in different rooms and different operators handle the different rooms.The meter was logged out before operator b performed glucose testing on patient b.Operator b scanned the barcode on the patient's wrist tag and reflected as patient b's id.Operator b confirmed and verified that the id belonged to patient b before proceeding with the test.Testing was repeated on patient b using the same workflow and the result transmitted correctly to the lis as patient b's id.
|
| |
|
Additional Manufacturer Narrative
|
|
The investigation did not identify a product issue.Several potential root causes such as communication issues, programming issues, decoding issues, production issues, and handling issues were analyzed.All root causes are very unlikely and most can be ruled out.The most possible root cause is a handling issue in creation of the wrist bands, having different barcode contents.
|
| |
|
Search Alerts/Recalls
|