The tas database in use at the facility had in total (b)(4) tracings and had been in use for over a year (it was created on 10/14/2020).Prior to the creation of that database, an it administrator at the facility had been archiving and creating a new database on roughly a monthly basis.After the it administrator left the position, database archival was no longer being performed.The large size of the database could have contributed to the teg manager agent incorrectly reading from the tas patient database to retrieve the calculated inhibition/aggregation results for a teg 5000 result.It was not able to be proven that this was the root cause of this issue during testing, however from haemonetics analysis, it is believed that the database size played a big role in causing this event.In order to reduce the chance of a large database leading to issues with erroneous results, customers need to be diligent about compacting and archiving their tas patient database on a regular basis.Implementing a warning message into the teg manager agent that alerts the end user when the database needs to be archived will help reduce chances of a large database leading to erroneous inhibition/aggregation test results.Improving labeling to inform customers on the need for database compacting/archiving could also help raise awareness of this issue.
|
On november 19, 2021, haemonetics was made aware of a customer complaint describing an instance where the adp inhibition/aggregation for a teg 5000 plateletmapping adp cluster displayed incorrectly in teg manager.The plateletmapping adp inhibition/aggregation displays correctly in tas.The medical director at the user facility initially noticed the discrepancy when reviewing the result in teg manager.The physician was not aware of any treatment given to the patient based on the erroneous result and there was no reported harm or injury to the patient.
|