|
Getinge became aware of an issue with one of our tabletops ¿ 118010a0 basis tabletop, individual configuration.During a 4-hour cardiac surgery, the patient was placed in a supine position, and a stage ii pressure sore developed on the buttocks.There was no malfunction of the tabletop or table pad, the injury resulted from prolonged ischemia time and the patient¿s general condition.The injury was described as significant, requiring additional treatment, extended hospital stay, and possibly surgical intervention.We decided to report the issue due to the serious injury of the patient.
|
|
Getinge became aware of an issue with one of our tabletops ¿ 118010a0 basis tabletop, individual configuration.During a 4-hour cardiac surgery, the patient was placed in a supine position, and a stage ii pressure sore developed on the buttocks.According to the provided information, the injury resulted from prolonged ischemia time and the patient¿s general condition.The injury was described as significant, requiring additional treatment, extended hospital stay, and possibly surgical intervention.We decided to report the issue due to the serious injury of the patient.
|
|
The correction of b5 describe event and problem and h6 medical device ¿ problem code deems required.This is based on the internal evaluation.Previous b5 describe event and problem: getinge became aware of an issue with one of our table tops ¿ 118010a0 basis table top, individual configuration.During a 4-hour cardiac surgery, the patient was placed in a supine position, and a stage ii pressure sore developed on the buttocks.There was no malfunction of the table top or table pad, the injury resulted from prolonged ischemia time and the patient¿s general condition.The injury was described as significant, requiring additional treatment, extended hospital stay, and possibly surgical intervention.We decided to report the issue due to the serious injury of the patient.Corrected b5 describe event and problem: getinge became aware of an issue with one of our table tops ¿ 118010a0 basis table top, individual configuration.During a 4-hour cardiac surgery, the patient was placed in a supine position, and a stage ii pressure sore developed on the buttocks.According to the provided information, the injury resulted from prolonged ischemia time and the patient¿s general condition.The injury was described as significant, requiring additional treatment, extended hospital stay, and possibly surgical intervention.We decided to report the issue due to the serious injury of the patient.Previous h6 medical device ¿ problem code: adverse event without identified device or use problem 2993.Corrected h6 medical device ¿ problem code: patient device interaction problem 4001.Getinge became aware of an issue with one of our tabletops ¿ 118010a0 basis tabletop, individual configuration.During a 4-hour cardiac surgery, the patient was placed in a supine position, and a stage ii pressure sore developed on the buttocks.According to the provided information, the injury resulted from prolonged ischemia time and the patient¿s general condition.The injury was described as significant, requiring additional treatment, extended hospital stay, and possibly surgical intervention.We decided to report the issue due to the serious injury of the patient.Based on the information provided by the customer, no defect of the table top or pad was found.With the investigation performed it was concluded that upon the event occurrence, the device was being used for the patient¿s treatment, and thus was also directly involved with the reported incident.As no relevant malfunction with the device was reported, it has been assessed that the getinge device was up to the specification.In the instructions for use, the user is warned that improper positioning can be detrimental to patient health (e.G.Causing bedsores).The user is advised to position the patient correctly and maintain continuous observation (ga 1180.01 rev.16, page 21).In summary, this issue was caused by the patient¿s general condition.Therefore, the most probable root cause for this issue is user¿operational context.We currently do not have any information that would warrant further action regarding device manufacturing or devices on the market, however as per our complaint handling processes will continue to monitor the customer experiences with the device for any future information.
|