This medwatch is reporting primary console (b)(4).Primary console (b)(4) is reported under medwatch mfr report # 2916596-2019-00946, motor (b)(4) is reported under medwatch mfr report # 2916596-2019-00948, and motor (b)(4) is reported under medwatch mfr report # 2916596-2019-00949.No further information was provided.A supplemental report will be submitted when the manufacturer¿s investigation is complete.
|
The patient was placed on extracorporeal membrane oxygenation (ecmo) support.It was reported that during patient transport between (b)(6) hospital to (b)(6) hospital, the primary console ((b)(4)) alarmed and displayed "----" for the flow reading.The flow probe was repositioned with no success.The primary console was exchanged to the backup console ((b)(4)).After approximately 10 minutes, the flow displayed ¿----¿.Despite repositioning the flow probe and switching the console off and on, the fault would not resolve.The healthcare professional relied on oxygen saturation levels, pressures, etc.As indicators of adequate flow, and the rest of the transport was uneventful from this respect.It was reported that when the flow probes, etc.Were being adjusted, the healthcare professional could feel an electrical tingling sensation when in contact with the cart and some of its components.On arrival at the hospital, the crew disconnected the trolley from the ambulance dc supply and moved the patient directly to the ct scanner.It was reported that the healthcare professional did not notice any action which could lead to cable damage.A flow probe from (b)(6) hospital was connected, but this still failed to register a flow so it was assumed that the fault was in the console.The patient was transferred to (b)(6) ecmo device, which immediately displayed the expected flow of approximately 4 l/min.No additional information was provided.
|
Manufacturer investigation conclusion: the centrimag 2nd generation primary console was returned to the service depot for analysis.The returned console was evaluated and tested under work order # (b)(4).The service depot was unable to confirm or duplicate the reported blank flow.The console was tested with the associated motor and flow probe.The console performed as intended and there were no disruptions in the set rpms or flow speeds at any point.No dashes were observed in the lpm reading either.A full functional checkout was performed, and the unit passed all tests.A log file was extracted from the system for analysis.A review of the log file showed data spanning approximately 178 days (14sep18 ¿ 11mar19 per time stamp).On 11nov18 at 14:58, the stack tracer error, ¿st_i2c_com_failed¿ was logged.At the time stamp of 14:59, the ¿tech: flow error¿ ¿can bus send error¿ and the sub fault ¿sf_flow_other¿ occurred triggering a ¿system alert: s3¿.The ¿system alert: s3¿ was able to be muted.The flow dropped to 0 lpm and was coincident with the sub fault ¿sf_flow_low_amplitude¿ and the fault ¿flow signal interrupted: f2¿.The flow remained at 0 lpm for the remainder of the log file.The root cause for the blank flow and observed s3 alarm was not conclusively determined through this analysis.No further information was provided.The manufacturer is closing the file on this event.
|