Catalog Number 8416400 |
Device Problems
Visual Prompts will not Clear (2281); Device Displays Incorrect Message (2591)
|
Patient Problems
Death (1802); Hypoventilation (1916); Decreased Respiratory Rate (2485)
|
Event Date 12/16/2015 |
Event Type
malfunction
|
Manufacturer Narrative
|
The investigation was started but is not yet concluded.The investigation result will be reported in a follow up-report.
|
|
Event Description
|
It was reported, that the customer filed a medwatch report with the fda which documented the following event: ventilator was on a patient and just stopped breathing and alarmed with a device failure alarm that could not be cleared.The only way to stop alarm was to turn the ventilator off.The nurses and technicians were forced to swap out the ventilator with another to put back on the patient.The customer indicated in the medwatch report that an adverse event had occurred (death).Drager quality followed up with the customer to determine if the statement was correct.The customer stated that the patient death did not result but they considered the event life threatening.The customer also stated that no harm was done to the patient due to the error.
|
|
Manufacturer Narrative
|
The device log was downloaded and analyzed.The analysis revealed that the ventilator performed several reboots, beginning on (b)(6) 2015 at 4:19am.This behavior was caused by a malfunction of the central pcb, the so called therapy control unit.The device internal monitoring had recognized data inconsistency and therefore triggered these reboots to restore the data base for ventilation.As this was a hardware failure, the reboots were not successful and were repeated 7 times within 16 minutes.Each reboot needs about 7 seconds.After a further period without reboots the device finally stopped ventilation at 5:23am with alarm.During a reboot and after stop of ventilation as well the breathing system is automatically opened to atmosphere in order to allow breathing efforts of the patient.This is accompanied by alarm.The failure rate of the concerned pcb is low and within the accepted range.The manufacturer comes to the conclusion that the device behaved as specified in this failure case.
|
|
Event Description
|
Please see initial-report.
|
|
Search Alerts/Recalls
|