| Model Number |
03R89-23 |
| Medical Device Problem Code |
Computer Software Problem (1112)
|
| Health Effect - Clinical Codes |
Insufficient Information (4580); No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
11/09/2022
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
An evaluation is in process.A follow-up report will be submitted when the evaluation is complete.All available patient information was included.Additional patient details are not available.
|
| |
|
Event or Problem Description
|
|
The customer experienced a delay in reporting patient results (hbcore and hcv-ii) due to the customer's lis not receiving data from the aliniq ams.It was discovered that the aliniq ams was unable to transfer the results because the cpu went out.Field service had to reset the ams server to resolve the issue.The customer stated that due to hcv-ii results being delayed approximately 24 hours, transfusion of blood product was delayed to one patient.It is unknown what type of blood product, patient diagnosis or whether there was any patient harm due to the delay.No additional patient details were available.
|
| |
|
Additional Manufacturer Narrative
|
|
Data communication between the aliniq ams and the customer middleware and lis are performed via sftp file transfer that is managed by the laboratory it department.Technical investigations confirmed that all the samples were correctly received by the aliniq ams from the alinity s and they were properly managed by the aliniq ams on november 09, 2022.All test result files were sent from the aliniq ams to lis via labonlinelink (as the evidence of the correct transmission the result files were re-named from.Xxx to.Res).The root cause of the event was a customer use error: sftp communication failure occurred between november 09, 2022 12.49pm and (b)(6) 2022 at ~6pm in the customer environment where the customer it department is responsible for its infrastructure security and availability.Delays in data file transfer from the aliniq ams to lis was caused by acts or omissions of the laboratory it department.Being the customer it department is the owner of the environment and fully responsible to ensure infrastructure security and availability, actions to restore communications within the laboratory were taken by the customer it team.On (b)(6) 2022 the customer restarted their servers but they did not provide any details about actions or troubleshooting performed by their it department to restore system connections and data transfer.Therefore, as no issue was confirmed on the aliniq ams, no actions were taken on the aliniq ams product.The local abbott representative supported the customer in re-sending test results managed by the aliniq ams on 09 and (b)(6) 2022 and in the verification that all results were present and transferred to the lis.Trending review determined no trend for the issue for the product.No additional complaints similar to the issue described in the current complaint were identified.Device history record review did not show any potential non-conformances, or deviations.Labeling was reviewed and found to adequately address the issue under review.Based on the investigation, no malfunction or deficiency for the aliniq ams was identified.
|
| |
|
Search Alerts/Recalls
|