| Catalog Number |
MS25520 |
| Medical Device Problem Codes |
Disconnection (1171); Connection Problem (2900); Intermittent Communication Failure (4038)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
05/20/2024
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
The investigation has just started; results will be provided in a follow-up report.
|
| |
|
Event or Problem Description
|
|
The customer reported that the m540 disconnected from the cockpit during surgery, and that the replaced m540 reset the system.The customer retrieved a m540 from storage, power it on, and connect the pt to the monitor.The customer confirmed that there was a 5-10 minute delay in patient care with no patient injury or adverse impact.No patient death reported.
|
| |
|
Event or Problem Description
|
|
The customer reported that the m540 disconnected from the cockpit during surgery, and that the replaced m540 reset the system.The customer retrieved a m540 from storage, power it on, and connect the pt to the monitor.The customer confirmed that there was a 5-10 minute delay in patient care with no patient injury or adverse impact.No patient death reported.
|
| |
|
Additional Manufacturer Narrative
|
|
Review of the logs provided showed that the timing between m540 and cockpit was not aligned.A signature entry following the timing discrepancy was identified (i2c [inter-integrated circuit] master communication error).When this communication error occurs, the cockpit attempts to correct the issue and in the cases it cannot, as a result, the cockpit closes all communications to the m540.When this occurs, the m540 maintains monitoring capability as intended as a stand-alone patient monitor.Notably, discharging the patient from the m540 resolves the issue, re-establishes connection and the patient can be reassigned to the monitor.Attempts to reproduce the disconnect issue at draeger have been unsuccessful in a simulated clinical test setup.Hardware testing was performed including a radio frequency (rf) immunity test on a customer returned system with focus on radio frequency identification (rfid) frequencies and applications.This was performed as it had been observed that systems with a capsule rf card reader nearby had disconnected.This testing was performed at a certified test lab (reference: (b)(4).The disconnect issue could not be reproduced.Additionally, a comparative study of the m540 i2c bus timing was made on a known good m540 unit as compared to an m540 unit which was returned from the field with a report of a cockpit disconnect.No anomalies were identified.Based on draeger investigation, the following causes of the m540 disconnects were excluded: iacs/m540 hardware defects.No returned device malfunctions were identified.Use of non-medical grade power cords.Iacs/m540s being plugged in through the apollo anesthesia power strip instead directly to the ac wall outlet.This was assessed to isolate the iacs power source and exclude any power quality/degradation factors from obtaining power through the apollo workstation's power strip or impacts from other devices connected to the strip.(e.G., ac wall outlet to apollo workstation power supply to iacs power supply to m500 docking station and cockpit).Compatibility of the m500 firmware in the iacs systems (vg4.2 compatible with firmware versions 4.0 or 4.4).Emi (electromagnetic interference) from sources in environment.Potential electrical interference from the site power line coming in.Site patient profiles in use during disconnections were tested during attempts to recreate the issue at draeger.After extensive investigation where no device malfunctions were identified and the above external factors were excluded, specific root cause cannot be definitively established beyond the potential for an environmental anomaly localized to these operating rooms/sites.Though the specific root cause cannot be determined, based on this investigation, draeger has identified an opportunity to develop software code changes that are intended to prevent the cockpit from disconnecting due to timing alignment issues, regardless of the cause, for a future software release.
|
| |
|
Search Alerts/Recalls
|