The customer reported that a patient passed away on (b)(6) 2023 and they need to see if the monitor alarmed for the spo2.The customer biomedical engineer (biomed) verified the concern as a potential failure of monitor to alarm.A philips remote service engineer (rse) remotely accessed the philips patient information ix (pic ix) system and it showed the monitor comes online and the ecg alarms come on, but the spo2 does not show to come on.Follow-up with the customer found the clinical audit log indeed show spo2 on/off for the alarms.A philips technical consultant (tc) pulled clinical audit logs, pic ix logs, and device configuration and logs.Tc used simulators to generate both ecg and sp02 alarms on both monitor and central station using biomed surveillance.Further troubleshooting is expected.
|
The philips technical consultant (tc) pulled the clinical audit logs, pic ix logs, and device configuration and logs.The fse used simulators to generate both ecg and spo2 alarms on both the monitor and central station using biomedical surveillance.The pic ix appeared to alarm as expected.The complaint was escalated for technical investigation and the results indicate that the equipment was functioning properly and that alarms should have been heard at the pic ix.The provided logs were reviewed by a business unit product support engineer (pse).The pse reviewed the audit log, and on (b)(6) 2023 at 04:21, spo2 was turned on, but at 04:59, the ¿sensor off¿ inop was generated and then ended a few seconds later.A ¿sensor off¿ inoperative (inop) error means that the sensor is connected to the mx100 device, but not properly applied to the patient.Inops are technical alarms that indicate the monitor cannot measure or detect alarm conditions reliably.A ¿spo2 sensor off¿ inop interrupts monitoring and alarm generation.The measurement numeric is replaced with a ¿-?-¿, and the inop tone plays.There were multiple instances of the ¿sensor off¿ inop, meaning the connection of the sensor to the patient was not properly connected and the monitor was not able to generate alarms.At 04:59, there is indication of spo2 being low, which means that the alarm was generated at the pic ix.After the alarms sounded, there is an ¿acknowledge¿ from the bedside by the user.This acknowledges all active alarms by switching off audible alarm indicators and lamps; however, the visual alarm indicators remain while the alarm condition is active and are displayed at the monitor and the pic ix.The customer was concerned about the gap in clinical audit logs.The pse advised in the stardate logs, the 3s-mx14 device is shown as being associated to the patient and started monitoring at 04:21 before it was disassociated at around 05:31.A minute before at 04:19, there are shown to be network alerts from the access point (ap)/access point controllers (apcs), which could indicate an issue with the ap/apc itself, which could cause the wireless monitors to not respond properly until the patient is within a better coverage of the ap/apc range.If there is an issue with the apcs/aps, they have to be resolved first.After those have been resolved, the patient must be within network coverage.The cause of the gap in clinical audit logs could be either the apcs/aps and/or the network coverage of the patient.Based on the information available and the testing conducted, the device was functioning as intended and there is no malfunction on the device.The reported problem was not confirmed.No further action is necessary at this time.
|