A philips field service engineer (fse) visited the customer site to evaluate the alleged malfunctioning device, collect logs, and clinical audit trails.Functional tests performed and log review couldn¿t replicate the issue.Both x2 and mx-800 devices were working per specification.A philips product support engineer (pse) evaluated the clinical audit log and determined that the following alarms were on during the incident timeframe: ecg alarms, spo2 alarms, nbp alarms (from bedside device).Physiological alarms were provided for: vtach, vent fib/tach, **hr high limit violations, *pvc limit, *afib, *irregular hr.Technical inop alarms were provided for: ecg leads off, rl lead off, resp lead off, cannot analyze ecg, spo2 no sensor, spo2 sensor off, spo2 no pulse, nbp measurement failed.The customer initiated abp (arterial blood pressure) monitoring at 07:53:22 and abp alarms were turned on for the parameter." another pse reviewed the audit logs and stated "from the patient information center ix side, the system performed as expected ¿ frequent alarms for the beds/times in question, were sent to 3 pic¿s.The supplied alarm log shows frequent alarms being sent from the b355 to 3 different pic ix hosts (wkhix112/114/116) for the time period in question.Several of the alarms are for sp02 sensors off, a few for npb measurement failures.(b)(6) 2023 07:37:39 wellstar kennestone b355 acknowledge wkhix112 acknowledge.(b)(6) 2023 07:26:14 wellstar kennestone b355 acknowledge wkhix112 acknowledge.(b)(6) 2023 07:26:14 wellstar kennestone b355 acknowledge wkhix112 acknowledge.(b)(6) 2023 07:17:10 wellstar kennestone b355 acknowledge m355 acknowledge.(b)(6) 2023 07:05:30 wellstar kennestone b355 acknowledge m355 acknowledge.(b)(6) 2023 06:53:54 wellstar kennestone b355 acknowledge m355 acknowledge." a philips clinical specialist (cs) evaluated the clinical audit logs and configuration files, stating the following: "i do not see an apnea alarm in this case.There is a desat alarm at 4:38:20 that ended at 4:38:58.Previously, there were lots of spo2 low and desat alarms.After this, there are multiple spo2.No pulse and interference inops.They must have their alarms set to not latch since the alarms stop on their own without and acknowledgement of the alarm.There are also low nbp alarms during this time and the nbp measurement failed at 7:19:28.The vent fib/tach alarm was generated at 7:33:19." i see the following alarms in the audit log between 07 to 0730 on (b)(6) 2023: low nbp alarms, spo2 no sensor, sensor off, and no pulse inops, afib , nbp measurement failed inop the spo2 was having inops since (b)(6), 2023 at 14;22;56.Between 0700 and 0730, the spo2 was displaying inop alarms.Nbps 82<90 alarm was generated at 07:00:23.The nbp measurement failed inop was generated at 07:16:34, 17:19:52, and 7:332:37.Respiratory leads off was generated at 7:32:58.The configuration file revealed the respiratory alarms are off by default as shown below.The cs also confirmed that if the intellivue x2 is docked to the host monitor (mx800), alarming would occur at the host monitor.Main setup - measurements - resp: item= measmt.Adult measmt.Pedi measmt.Neo high limit= 40 rpm, 30 rpm, 100 rpm, 30 rpm.Low limit= 8 rpm, 8 rpm, 30 rpm, 8 rpm.Apnea time= 20 sec, 20 sec, 20 sec, 20 sec.Alarms= off, on, on, on.Resp= on, on, on, on.Based on the information available and the testing conducted, the cause of the reported problem was an user configuration issue, as respiratory alarms (includes apnea) were set to off by default.The reported problem was not confirmed.There was no malfunction of the intellivue mx800 patient monitor.The device was confirmed to have alarmed and worked per specifications.
|