Section b event date was corrected from 02/01/2023 to 01/31/2023.The field service engineer (fse) went to the customer's site and was unable to reproduce the customer's issue.No other problems were detected during testing, the device was fully functional.The fse pulled logs and clinical audit data.The product support engineer (pse) analyzed the logs.The bedside ivpm bedside xmon14 alarm review photos provided prove that there were alerts, including red alerts at 10:18 am, 10:22 am, and 10:24 am, for the bed during the timeframe of 10:12 am to 10:29 am.For the nibp measurement, there could not be an alert for the time of approximately 10:20 am since the last nibp measurement was done at 09:28 am.The nibp measurement was likely set to manual by user, instead of automatic (default).For the spo2 measurement, the spo2 sensor was detached at 10:17 am from the finger.This was a technical inop announced as a cyan alarm, but as there were other higher alarms raised (red ecg vent fib/tachy), only the red alarms were announced.Since the spo2 sensor was detached, there could not be any other alarms afterwards for spo2.There were several ecg red alerts for the timeframe alleged.The monitor seems to have been disconnected from the central for approximately 35 seconds, which means for that for the alleged timeframe, no alerts of bedside ivpm xmon14 were given at the picix.Nevertheless, the ivpm bedside xmon14 alerted this condition to the user by an inop ¿no central¿, and this alert was silenced at the ivpm bedside xmon14 by the user according to the picix audit log.Which leads to the conclusion that a clinical user was operating the ivpm bedside xmon14.The pic ix log confirmed the conditions seen at ivpm bedside xmon14 alarm review including the disconnect situation.It cannot be determined why the ivpm bedside xmon14 got disconnected.Nevertheless, the ivpm bedside xmon14 alerted during that timeframe independently, which seem to be noticed by the user.
|