| Catalog Number |
03R70-01 |
| Medical Device Problem Code |
Patient Data Problem (3197)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
01/08/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
An evaluation is in process.A final report will be submitted when the evaluation is complete.Completed information for section a1 - patient identifier: sids (b)(6).All available patient information was included.Additional patient details are not available.
|
| |
|
Event or Problem Description
|
|
The customer observed a falsely elevated magnesium result generated by the alinity ci-series scm module for a patient.It was observed that the dilution factor was applied to add on orders, from a previous manual order.The following information was provided: (b)(6) 2025 sample id (b)(6) glucose result = >800, manual 1:5 dilution was ordered and result = 1300.Customer is not questioning this result and 1300 was reported out.Magnesium (mg) add on order for the same sid (b)(6) was completed on the lis beaker system.The 1:5 dilution factor was also applied to this order and result of 12 mg/dl was obtained.The customer was not aware that the dilution factor was still entered into the software when this result was run.Sample was run neat and result = 2.6 mg/dl.Customer¿s reference range is 1.8-2.6 mg/dl customer states that the same issue happened on (b)(6) 2025, a known ferritin sample (sample id (b)(6) that needs to be run diluted was run with manual 1:20 dilution.Ferritin result was not questioned or discrepant.There was an add on for cmp for the same sid, and all results had the 1:20 dilution factor applied which generated erroneous results.Customer did not report out cmp, reran sample neat and results were within normal range.No specific results and/or data for cmp was provided.No impact to patient management was reported.
|
| |
|
Event or Problem Description
|
|
The customer observed a falsely elevated magnesium result generated by the alinity ci-series scm module for a patient.It was observed that the dilution factor was applied to add on orders, from a previous manual order.The following information was provided: (b)(6) 2025 sample id (b)(6) glucose result = >800, manual 1:5 dilution was ordered and result = 1300.Customer is not questioning this result and 1300 was reported out.Magnesium (mg) add on order for the same sid (b)(6) was completed on the lis beaker system.The 1:5 dilution factor was also applied to this order and result of 12 mg/dl was obtained.The customer was not aware that the dilution factor was still entered into the software when this result was run.Sample was run neat and result = 2.6 mg/dl.Customer¿s reference range is 1.8-2.6 mg/dl.Customer states that the same issue happened on (b)(6) 2025, a known ferritin sample (sample id (b)(6)) that needs to be run diluted was run with manual 1:20 dilution.Ferritin result was not questioned or discrepant.There was an add on for cmp for the same sid, and all results had the 1:20 dilution factor applied which generated erroneous results.Customer did not report out cmp, reran sample neat and results were within normal range.No specific results and/or data for cmp was provided.No impact to patient management was reported.
|
| |
|
Additional Manufacturer Narrative
|
|
Additional information section h4 - device mfg date updated.The complaint investigation included a search for similar complaints, ticket trending review, and labeling review.Return testing was not completed as returns were not available.The customer observed an issue where a dilution factor from a previous test order was incorrectly applied to an add-on order on the alinity ci-series system control module (scm), (b)(6).The search for similar complaints found additional complaints related to the text query, however, there have been no subsequent tickets opened for dilution factor from a previous test order being incorrectly applied to an add-on order to the alinity ci-series system control module.A review of the result log was performed by the alinity software engineering team.The evaluation determined the information contained in the result log did not provide enough information to determine why the dilution factor from a previous manual order was applied to the add on order, however no additional issues were identified.A review of tracking and trending for the alinity system software did not identify an increase in complaint activity related to the complaint issue.The device history record was reviewed and also did not identify any non-conformances or potential non-conformances related to the current complaint.Labeling was reviewed and found to be adequate.Based on the investigation, no systemic issue or deficiency was identified with the alinity ci-series system control module, serial number (b)(6), or the alinity system software v3.5.1.
|
| |
|
Search Alerts/Recalls
|