H10: a philips field service engineer (fse) went to the customer site.The engineer tested the device in demo mode and with a simulator and found that the curves and numerical values were correctly displayed on the screen and that the visual and audible alarm indicators were correctly reported, especially for spo2 alarms.The fse provided audit logs, however after the logs were reviewed it was determined that the logs were for the incorrect bedside label and the incorrect day.The fse provided a screenshot of the correct logs.Review of the screenshot determined that there is not enough information to determine whether the device did not alarm.The configuration logs were requested but not provided.The screenshot shows the yellow alarm was generated at spo2 84% and again at 80%.The low limit was set to 85%.The config files would help determine what the desat limit was set to and how much time the patient has to be at that level for the alarm to occur.Spo2 alarms have a delay time for high and low and a separate delay time for desat.That is set in configuration.The default is 10 sec for high and low and 20 sec for desat.This complaint is about an spo2 of 78 not sounding.If the patient had a 78 spo2 and it didn¿t alarm either the desaturation limit was lower than 78 or the patient did not stay at 78 for greater than the desaturation alarm limit time.The low spo2 alarm was silenced at the pic 2 min later followed by an extreme bradycardia (xbrady 45<50) at 11:55 which was also silenced at the pic.Without the config, philips cannot speak to the desat limit setting (which can be changed per patient) or the desat alarm delay setting which can¿t be changed per patient.The cause of the event is unknown.The device was removed from service.
|