The reported issue was investigated via remote support by a philips remote clinical applications support specialist (rcass).According to the biomed at the customer site, a member of the clinical staff was standing in front of the mx800 and saw that the spo2 value was dropping below the desat limit before returning to a level above the desat limit violation.The staff member expected a desat alarm for the drop below the desat limit which was not announced by the monitor.The rcass reviewed the audit log from the central station together with the biomed and multiple yellow spo2 alarms as well as some red desat alarms were found for the patient.The rcass advised the biomed of the alarm delay configuration of 10 seconds for a spo2 low limit alarm and 20 seconds for a desat alarm.The spo2 value returned above the desat limit threshold within the alarm delay time, which was the reason why the alarm was not indicated.The biomed stated that the clinical staff was not aware of the alarm delay functionality and that she would instruct the staff accordingly.The rcass provided the biomed with information regarding the alarm behavior to be forwarded to the clinical users.The biomed was also instructed on how to access and review the alarm review on the monitor.Additionally, the biomed advised that she had tested the monitor and found it to be working as intended.It is considered that this issue was resolved by the remote clinical application support specialist instructing the biomed regarding the alarm delay functionality and providing information regarding the alarm behavior.The monitor worked as intended and there was no malfunction of the device.This issue was caused by the alarm delay configuration.
|