|
Correction: concomitant med prod data annex b: b21, annex c: c21, annex d: d16.Additional information: device available for eval?, returned to manufacturer on, device eval by manufacturer?, and manufacturer narrative.Annex a: a23, a2101, a0404, a0401, annex b: b01, b14, annex c: c23, c070606, annex d: d15, d11, d1102, annex g: g0200802, g02017, g04080.A device history record, complaint history review, and risk review on failure modes are performed on each device with reportable malfunction(s) along with other methods of investigation as coded in section h6 of this mdr report.Investigation summary: the report of the under infusing was confirmed during laboratory testing.The pcu or pcu event logs were not returned, without the pcu event logs, and due to limited information, that the pca logs contain, drug information (such as the exact drug programmed and its concentration), total volume infused, and unit power-off times cannot be determined.A review of the pca module error log showed no errors relevant to the reported complaint.The pca module event log showed that on 05dec2025 at 10:49 pm the unit was selected, a pca-only infusion was programmed with the following parameters: dose=1 mg; concentration=1 mg/1 ml; syringe=bd 30 ml; volume=43.1947 ml (this is related to the reported complaint, the user selected a wrong syringe size, as observed in the syringe volume detected by the suspect pca module, it is suspected that the actual syringe utilized was a bd 50/60 ml).Between 11:35 pm and 6:20 am on 06dec2025 there were 25 pca requests registered, however, the pca only delivered 11 doses which amounted to a primary volume infused (pvi) of 11 ml after the last pca request was made.Initial volume infused accuracy test results measured showed that the device would under infuse, however, the issue was fixed after the device was calibrated, an additional volume infused accuracy test showed that the device delivered fluid within specification.No errors or issues were observed during the test.Preventive maintenance tests results showed the device to be working within specification.The alaris system user manual v9.33 mentions that proper operation of the bd alaris¿ system requires that you are familiar with related features, setup, programming, iv sets, and accessories.Read all instructions, including those for all attached module(s) and associated disposables before using the bd alaris¿ system.The manual further specifies that the clinician must ensure that the displayed syringe manufacturer and syringe size match the installed syringe.Mismatches can impact flow rate accuracy.To minimize potential startup delays, delivery inaccuracies, and delayed occlusion alarm generation when loading a new syringe, the manual recommends selecting the smallest appropriate syringe size (for example, using a 3 ml syringe to infuse 2.3 ml of fluid).Additionally, the programmed flow rate should be equal to or greater than the minimum recommended flow rate for the selected syringe.The bd alaris user manual also includes a warning indicating that errors when entering the drug amount or diluent volume may result in over infusion or under infusion.An external and internal inspection of the suspect pca module s/n (b)(6) showed no obvious issues or anomalies.The device was in use for treatment purposes as intended per 21 cfr 820.198(d)(2).Root cause: the root cause for the device under infusing was attributed to the device being uncalibrated and to use error, as it was observed in the logs that an incorrect syringe selection was made by the user.Laboratory testing showed that after calibration, the device delivered fluid within specification.Note that this report lists imdrf annex a23, a2101, a0404, a0401, c23, c070606, d11, d15, g0200802, g04080, g02017 codes not associated with the reported event but identified as reportable malfunctions observed on the device during investigation are unrelated to the reported issue.These other failures presumptively did not cause or contribute to the reported issue.Per 803.52(f)(11)(iii) the information provided was obtained from servicing activities performed on the device.There were no additional details obtainable or provided at the time of service.
|