Philips obtained the data logs from the piic (philips intellivue information center) from the customer's biomedical engineer. data logs were reviewed a clinical specialist, quality investigator and r&d (research and development) engineer.The investigation was limited due to the timing on the collection of the piic data logs which were not collected until 3/23/2017 when the issue was reported to philips. stored data from the time of the event on (b)(6) 2017 was no longer available on some of the data logs provided. no strips or stored data were provided as the customer stated that a patient report was printed and the patient was discharged with all data deleted and the patient report (paper) was lost. data logs collected show that the mx40 was alarming for ***asystole red alarm from07:15:05 through 07:15:43. additional information provided stated that a physician checked the hr on the telemetry device in question at 12:30 pm and also checked the power by pressing the blue button on the mx40, indicating that battery was working at this time.A nurse tested the tele15 (telemetry device used at the time of the event) later in the afternoon (no time specified) in parallel with another mx40 (both with connected ecg) and found that tele15 showed dropouts (<1min) and the other tele (telemetry not in use at the time of the event) showed no dropouts.Data log evaluation did find that the device was frequently losing connection and reconnecting throughout the day on (b)(6) 2017. without complete data logs provided for activity on 3/9/2017, philips cannot conclude the reason for the loss of connection. philips can confirm that the device was connected to the piic for bed f5 from 10:56 ¿ 13:33 with no disconnects on (b)(6) 2017, although no alarming could be confirmed. the mx40 telemetry device was not returned to philips for evaluation or tested by philips at the customer site, therefore no conclusions can be made. without a complete understanding of the event including all logs, wave strip exports, alarm settings, device logs and device evaluation, philips cannot determine the cause of the reported issue. an ecg leads off, inop (inoperative) message (dependent on configurable alarm severity, red, yellow, or cyan) may have been in effect, however insufficient information was provided to conclude that was the case. the customer has been provided a review of the available data. it is unknown if the device is in use at the customer site.The cause for the failure to alarm for asystole and the disconnection issues cannot be determined with the information provided as the log data was incomplete and patient strips were not provided.Use of the device is considered to be a factor as the customer said the patient was deteriorating before the asystole alarm occurred and staff were not aware.Philips will consider that the ecg alarming may have been impacted by a leads off alarm at the time of the event thereby preventing ecg alarms, however insufficient information was provided to make that determination.A malfunction preventing ecg alarming cannot be ruled out.
|