On (b)(6) 2022, the operator was completing routine work and bumped into the glp equipment of the alinity ci series system.The operator was holding samples from several patients, causing the samples to accidentally fall on her body and face.The operator used the eyewash and sinks for self-cleaning and was sent to the hospital.The operator also had a shower, flushed eyes, changed clothes, is being followed by hospital every six months, serology tests has been done, she took medicine to prevent any other problem (medication names: dolutegravir sódico, fumarato de tenofir, and retrovirall de anti-hiv).
|
The field service representative (fsr) stated that the operator bumped into the track end cover r (part number g-41751-01) for the glp track end, serial (b)(4), during the middle of the glp track installation process.The fsr specified that the operator was holding several patient samples when the arm hit against the track section for the alinity ci series instrument, causing the samples to splash on the operator¿s body and face.The abbott automation solutions (aas) technical group performed an investigation based on the complaint information.Aas was able to determine that the glp module and track did not cause or contribute to the event and a malfunction was not identified.Since no issues could be identified with the glp track, no further actions were performed.Current labeling provides field service and operators the safety information and advises caution to the user involving the risk of contamination and injury due to inattentive handling or not observing proper personal protective equipment (ppe).Trending review did not identify any trends for the issue under review.No malfunction was identified.Based on the information within the complaint record, the device met performance specifications and performed as intended at the customer site.The issue is considered a use error as the customer caused the mishandling of the sample tubes.The track end cover or the glp track end did not cause or contribute to the event.This issue was previously reported under mdr number 3016438761-2023-00025-00 under a different suspect device.All further information will be documented under this mdr 3023268435-2023-00012-00.
|