The customer requests event log review.The event logs have not been received.A follow up report will be submitted with evaluation results should the logs be received for evaluation.Volume overload secondary to nephrotic syndrome; lower extremity cellulitis.The patient experience hypokalemia, customer stated;"but it is difficult to attribute this to possible inadvertent changes in the fluid rate because his rate was intentionally increased and his dose of metolazone was also increased".No devices received, log review only.
|
Correction on initial report: b.2 & g.3 (disregard other).Additional information provided: d.4, d.11 & h.4.The report of infusing faster than expected was not confirmed.The pump module was not returned for investigation.The pcu event log contained no obvious programming errors that would result in the reported event.There were no alarms observed during the entire period reviewed that would suggest the fluid container emptied earlier than it should have.The starting/ending volume of the fluid container cannot be determined through log review.The volumes recorded as being infused for the first three instances match up with the durations of the infusion.The fourth instance confirms the rate changes that were reported however the device was channeled off at 11:44 am on (b)(6) 2019 and not at 9:45 am on 2019 as was reported.The event description appears to describe four separate instances of the bumex infusion.First: the first instance shows pump module s/n (b)(6) was programmed to infuse bumetanide continuous 25mg/100ml (drugid 61) at 6:16 pm on (b)(6) 2019.The user entered 2ml/hr for the rate, which made the dose 0.5mg/hr.The user entered 90ml for the vtbi, which would infuse over 45 hours and not 48 hours as was reported.The infusion ran until 10:46 am on (b)(6) 2019 when the device was channeled off.There were no alarms prior to the user channeling the device off.The volume recorded as being infused during this period was 76.502ml.The infusion ran for 40 hours and 30 minutes during this period however the device was not infusing for approximately 2 hours and 13 minutes due to being channeled off, delay programming or patient side occlusion alarm.Second: the second instance shows pump module s/n (b)(6) was programmed to infuse bumetanide continuous 25mg/100ml (drugid 61) at 12:10 pm on (b)(6) 2019.The user entered 2ml/hr for the rate, which made the dose 0.5mg/hr.The user entered 95ml for the vtbi, which would infuse over 47.5 hours.The infusion ran until 2:17 am on (b)(6) 2019 when the user changed the vtbi of the bumetanide continuous 25mg/100ml (drugid 61) infusion running at 2ml/hr to 100ml.The volume recorded as being infused during this period was 74.609ml.The infusion ran for 38 hours and 7 minutes during this period however the device was not infusing for approximately 1 hour due to delay programming or patient side occlusion alarm.Third: the third instance started at 2:17 am on (b)(6) 2019 when the user changed the vtbi of the bumetanide continuous 25mg/100ml (drugid 61) infusion running at 2ml/hr to 100ml.The infusion ran until 9:12 pm on (b)(6) 2019 when the user changed the vtbi to 90ml.The volume recorded as being infused during this period was 84.849ml.The infusion ran for 42 hours and 55 minutes during this period however the device was not infusing for approximately 28 minutes and 36 seconds due to delay programming or patient side occlusion alarms.During this period, the device was not infusing for approximately 28 minutes and 36 seconds due to delay programming or patient side occlusion alarms.Fourth: the fourth instance started at 9:12 pm on (b)(6) 2019 when the user changed the vtbi of the bumetanide continuous 25mg/100ml (drugid 61) infusion running at 2ml/hr to 90ml.The rates were changed as reported at 9:58 am on (b)(6) 2019 to 3ml/hr (dose = 0.75mg/hr) and ran at 3ml/hr until 10:38 am to 4ml/hr (dose = 1mg/hr).The infusion ran at 4ml/hr until 11:44 am on (b)(6) 2019 when the device was channeled off and not at 9:45 am on (b)(6) 2019 as was reported.There were no alarms prior to the user channeling the device off.The customer did not allege an overinfusion for this instance since the infusion ran at different rates.There were no alarms prior to the user channeling the device off.The root cause of the customer¿s report of infusing faster than expected was not identified.No device was returned for investigation.
|