Livanova received report that about after 20 minutes from procedure started, there was no flow despite rpm of the centifugal pump 5 (cp5) being 3800.Flow was down and there was negative line pressure.The original thought was a pressure excursion which could be excluded by user because as they hand cranked everything flowed.The vacuum was removed and the cannula was verified not to be occluded.The user turned the cp5 off and back on while continuing to hand crank and the problem persisted.The user turned the device off and back on again and this time everything went back to normal and hand crank was stopped.The procedure could be completed with no further issues.Reportedly, there were no alarms or error messages.There was no patient injury.
|
H10: through follow-up communication livanova learned that differently from what stated in b5 section of the initial report "the user turned the cp5 off and back on while continuing to hand crank and the problem persisted.", the user did not turn off the device the first time but only the speed control knob was set to zero rpm while performing hand crank.The issue, as reported in b.5 section of the initial report, could be solved afterwards when the vacuum was off and by turning the pump off and back on.Based on additional information provided, the reported no flow issue was not related to any device malfunction and could be traced back to configuration applied by the user during surgery, in detail the vacuum used in combination with a non obstructive pump generating a negative pressure in the reservoir higher than pressure created by revolution pump and consequently leading to no forward flow.This scenario is compatible with all information provided by the customer.Indeed, the issue could be resolved once the vacuum was de-activated, the pump turned off and back on allowing the reset of the previous pressure control condition and then device could be used to complete the procedure.Considering the available information, the reportability decision changes to not reportable event since the reported issue was related to configuration technique and not related to device failure.
|