A field service engineer (fse) went to the customer site on (b)(6) 2015 and was told by the customer's biomedical engineer that they did not want philips to evaluate the device involved in the reported incident.The biomed stated that they were going to do an internal investigation and did not require philips testing of the device.Since the customer would not allow philips to evaluate the device we cannot confirm that the device was operating per specifications.The device remains at the customer site.A patient death occurred.The customer reported that the pacer detection was not turned on for a paced patient and the mx40 telemetry device failed to alarm for an asystole event resulting in a patient death.Strips were provided for (b)(4) on (b)(6) 2015 from 18:44 to 18:50 timeframe.The strips demonstrate that paced mode was set for: not paced at 18:44 on (b)(6) 2015 a paced rhythm is shown with "n" for normal beat labels instead of "p" for paced which is what would be expected for a paced rhythm when pacing is turned on.Strip shows occasional failure to capture with pace pulse shown but no captured beat.At 18:47 there are increasing failed capture with absent qrss.Pacer spikes are being labeled as "a" or "v" as the system attempts to classify these as beats.At 18:50 the hr is listed as 68 which is reflecting only spikes.There are only 3 captured beats on the page in approximately a 20 second timeframe.The strips are consistent with behavior when pacing is not turned on.Product labeling provides explicit warnings about the importance of enabling paced mode for paced patients to avoid such occurrences.The information is not consistent with any product malfunction.The issue is consistent with a use issue.Submission of a report does not constitute an admission that medical personnel, user facility, importer, distributor, manufacturer, or product caused or contributed to the event.
|