Model Number 00-3020 |
Device Problems
Appropriate Term/Code Not Available (3191); No Pacing (3268)
|
Patient Problem
Insufficient Information (4580)
|
Event Date 02/07/2022 |
Event Type
malfunction
|
Event Description
|
As customer described - crews responded for a patient, during the care cycle pacing was indicated, pacing was then attempted with the device stopping and initiating a ¿dpm hardware failure¿ message.A second apparatus was called and a second ls was used to pace the patient to the hospital.Patient care was transferred to the hospital, the patient was alive and being treated by hospital staff.Some time after the hospital initiated patient transfer to a more advanced hospital, the customer was dispatched for this transport.During the second encounter with this patient, a second ls failed to pace with ¿ dpm hardware failure¿, another apparatus was called to provide pacing during transportation to the advanced hospital.The log files of the device were analysed by schiller (manufacturer).As per that the pacer started several times but always stopped.The "hardware failure (dpm)¿ was displayed to the user.This event seems to be a known issue "pacer error 26" which is non-reproducible and is under trending and internal investigation with the dedicated (b)(4) (capa-(b)(4)) - tempus ls: pacer issues.
|
|
Event Description
|
As customer described - crews responded for a patient, during the care cycle pacing was indicated, pacing was then attempted with the device stopping and initiating a ¿dpm hardware failure¿ message.A second apparatus was called and a second ls was used to pace the patient to the hospital.Patient care was transferred to the hospital, the patient was alive and being treated by hospital staff.Some time after the hospital initiated patient transfer to a more advanced hospital, the customer was dispatched for this transport.During the second encounter with this patient, a second ls failed to pace with ¿ dpm hardware failure¿, another apparatus was called to provide pacing during transportation to the advanced hospital.The log files of the device were analysed by schiller (manufacturer).As per that the pacer started several times but always stopped.The "hardware failure (dpm)¿ was displayed to the user.This event seems to be a known issue "pacer error 26" which is non-reproducible and is under trending and internal investigation with the dedicated sagqi-137 (capa-0029) - tempus ls: pacer issues.The device has been investigated by the manufacturer schiller and no problem was found with the device.A report from the manufacturer has been attached.
|
|
Search Alerts/Recalls
|
|