| Model Number |
03R89-48 |
| Medical Device Problem Code |
Computer Software Problem (1112)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
11/24/2022
|
|
Type of Reportable Event
|
Malfunction
|
|
Event or Problem Description
|
|
The customer observed mixed results between two aliniq ams test codes.The issue occurred while the customer was implementing and testing a new rule for interpreting results.The rule was intended for assays that require retests in which the final interpretation is only sent after the initial and two additional retests were completed.While testing of the rule patient tubes were placed on the track, measured and the results were reported.It was subsequently discovered that the results were mixed up between two ams test codes.A look back was completed and sample id (b)(6) anti-hbc results were impacted by the error.The interpretation (pos/neg) was correct however for each sample one of the values was havab igg.No impact to patient management was reported.
|
| |
|
Additional Manufacturer Narrative
|
|
An evaluation is in process.A follow-up report will be submitted when the evaluation is complete.Patient identified: multiple: (b)(6).Patient information: no further patient information was provided.
|
| |
|
Additional Manufacturer Narrative
|
|
The abbott specialist determined the mixed results between two aliniq ams test codes and related incorrect results released by the middleware to lis was due to a combination of multiple factors: rule requirements agreed and confirmed by the customer were misinterpreted by the abbott customization specialist and such they were wrongly implemented in the rule code (the rule logic was considering only one test result to be managed instead of multiple ones.) rule testing was not properly performed and documented by the abbott customization specialist before the installation and activation in the customer environment.A complete verification of the rule could have detected the incorrect rule behavior in case of multiple tests have been configured in the template.Lab technicians performed incorrect sample management during the test and validation phase of the aliniq ams rule: real patient tubes were placed on the track, measured and incorrect results were reported to the lis.Testing should be performed in a protected environment not using real patient samples.This scenario was addressed through a combination of actions within the middleware: aliniq ams configurator was configured in order to receive and store measurement and interpretation results in dedicated fields of the same test code instead of using two separate test codes for each serology assay; two (custom) rules were created for serology test results evaluation.These new rules use the qplinfo field to copy the first measurement.This field is replicated for each individual test of the sample avoiding the risk of mixing results between different tests.Each configured test uses its own qplinfo field to copy the corresponding first measurement instead of the qplnote field, which is unique for all tests of the sample.Customer validated the new aliniq ams settings and confirmed that the system was working as expected and corrections performed met their needs and expectations.A review of tracking and trending of the aliniq found no additional complaints related to the complaint issue.A review of the manufacturing documentation did not identify any issues associated with the complaint issue.Labeling was reviewed and adequately addresses the issue under review.Based on the investigation no systemic issue or deficiency with the aliniq ams was identified.
|
| |
|
Search Alerts/Recalls
|