Catalog Number MS25755 |
Device Problems
No Audible Prompt/Feedback (2282); Communication or Transmission Problem (2896)
|
Patient Problem
Arrhythmia (1721)
|
Event Date 12/10/2023 |
Event Type
Injury
|
Event Description
|
It was reported that the patient left the ward on the doe at approx.5am.The patient was found on the floor in their room between 7 and 8am and in need of resuscitation.After re-entering the ward, the m300 obviously did not go online again.Patient is in the intensive care unit; according to the doctor, the patient has not suffered any further damage as a result of this incident.
|
|
Manufacturer Narrative
|
The investigation has just started; results will be provided in a follow-up report.H3 other text : ongoing.
|
|
Event Description
|
It was reported that the patient left the ward on the doe at approx.5am.The patient was found on the floor in their room between 7 and 8am and in need of resuscitation.After re-entering the ward, the m300 obviously did not go online again.Patient is in the intensive care unit; according to the doctor, the patient has not suffered any further damage as a result of this incident.
|
|
Manufacturer Narrative
|
The user facility provided two (b)(4) units for evaluation because they were not able to clearly identify the device which was involved into the event.The units could not be tested in detail because this requires the connection of a data cable to the spo2 port which was defective at both devices - it is thus unclear if both devices were able to establish network connection or not.The faulty spo2 port has no causal connection to a potential loss of network connection - it is just the case here that dräger is unable to verify if network communication with these two (b)(4) units works in general.Log files for the devices covering the period in question were not provided by the customer.Logs for the infinity central station were available for evaluation.The entries show that one m300 on ward m3 lost network connection during the period in question.The entries in the logs show that other m300s also repeatedly were losing connection to the ics as well.Although the involved device could not be identified due to lack of information, the logs of the ics provide evidence that one m300 used in this ward lost network connection.The loss of network connection triggered a corresponding audible and visual alarm at the ics.Due to the fact that the particular patient was reportedly moving around, it cannot be excluded that he went to an area of weak network signal strength.On the other hand, there's evidence that other m300 units lost connection to the central station as well - it would thus also be imaginable that the signal quality and stability of the network is insufficient.Dräger concludes that the ics behaved as specified for this error condition - an offline message and a corresponding audio alarm were posted upon loss of connection to the bed place.It is under responsibility and control of the user to respond in a timely manner upon technical alarms.
|
|
Search Alerts/Recalls
|