| Catalog Number |
11128543 |
| Medical Device Problem Code |
Low Test Results (2458)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
09/26/2024
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
The customer reported the observation of three erroneous falsely depressed patient results with insulin-like growth factor i (igf-i), lot number: 317 on an immulite® 2000 xpi immunoassay system, serial number: (b)(6).The falsely depressed patient results were reported to the physicians and were questioned.The samples were reprocessed on the other immulite 2000 xpi analyzer and one result was corrected sample: sample id (b)(6).There are no known reports of patient intervention or adverse health consequences due to the issue.
|
| |
|
Additional Manufacturer Narrative
|
|
An outside the united states customer contacted the siemens healthcare diagnostics remote services center (rsc) regarding the observation of three erroneous falsely depressed patient results with insulin-like growth factor i (igf-i) lot 317 on an instrument is an immulite® 2000 xpi immunoassay system.Quality control (qc) did not recover within range when samples were initially tested.The qc on the alternate instrument used for reprocessing the samples qc was in range.Siemens is currently investigating the issue.
|
| |
|
Additional Manufacturer Narrative
|
|
Mdr 1219913-2024-00442 was filed on 24-october-2024.Additional information - 12-november-2024: siemens reviewed the information provided by the customer.There were no instrument interventions that occurred when the depressed results were observed.Repeat igf-1 testing of samples prior to the elevated results showed no issues.Review of quality control (qc) indicated failures (values which were low out of range) were observed during the same time period as the discrepant results.The customer replaced the reagents with new packs from the same lot and performed a new adjustment.Qc came in range.The customer is operational.The issue was resolved by routine troubleshooting.
|
| |
|
Search Alerts/Recalls
|