As described by customer "i had a crew attempting to take a transcutaneous pacing patient and they attached the equipment to the patient and when they tried to apply power through the ls, they received the code ¿hardware fault dpm¿.The call is complicated by the fact that the hospital staff detached their 3 lead ecg cables on their monitor as soon as our crew arrived, and their pacer began asynchronous pacing instead of demand, so there were shocks being given that weren¿t necessary.The crew received the same fault message when they tried to pace a second time without the hospital equipment attached.They called for a second ambulance and switched ls units and continued the call that way.The ls unit is passing the self test, and it also behaves exactly as i would expect now that i am testing it with a rhythm generator.From the manufacturer investigation based on the provided logfile and information, the pacer stopped due to the error 26.However, the trigger and actual root cause of the error 26 cannot be concluded at this stage.It is not sure whether the error was caused due to use error or a device error.
|
This report is based on information provided by schiller repair service personnel and has been investigated by the philips complaint handling team.Philips received a complaint on the tempus pro indicating that tempus ls failed to pace patient.Crew attempted to take a transcutaneous pacing patient and they attached the equipment to the patient and when they tried to apply power through the ls, they received the code ¿hardware fault dpm¿.The call is complicated by the fact that the hospital staff detached their 3 lead ecg cables on their monitor as soon as our crew arrived, and their pacer began asynchronous pacing instead of demand, so there were shocks being given that weren¿t necessary.The crew received the same fault message when they tried to pace a second time without the hospital equipment attached.They called for a second ambulance and switched ls units and continued the call.The ls unit passed the self test, and it passed test with a rhythm generator.The investigation of this issue was performed based on the provided information and logfile.The investigation of the logfile showed that the issue is caused by an error 26.The same issue was not found to be appearing before and after the complained date of occurrence.This complained issue appears to be a non-reporoducible pacer error, which is logged as error 26 in the logfile.As the error is not reproducible, the root cause can't be concluded.However, it is suspected that the error is caused due to communication issue to the dpm board.This error is under observation in sagqi-137 - tempus ls: pacer issues.The data entered in this complaint record will be utilized for product quality and safety improvements per the post market surveillance and risk management processes.The investigation concludes that no further action is required at this time.
|