Model Number 209999 |
Device Problems
Use of Device Problem (1670); Patient Data Problem (3197)
|
Patient Problems
Tissue Damage (2104); No Known Impact Or Consequence To Patient (2692)
|
Event Date 03/18/2019 |
Event Type
Injury
|
Manufacturer Narrative
|
As part of normal complaint follow-up, an evaluation of the event has been initiated by mako surgical.A supplemental report will be submitted when additional information becomes available.
|
|
Event Description
|
Sales rep reported that the surgical plan was planned for the wrong operative side.After putting the pins in the patient, this issue was noticed and the surgeon completed the case manually.The rep mentioned that the surgeon hadn¿t taken the time to review the pre plan properly before putting the pins in the pelvis.Hence the delayed time to catch the issue.Surgical delay < 5 minutes.Case was completed manually.Additional information received from rep: patient time out.Realised wrong plan was loaded, due to patient name and noticed the two plans for the day had each plan been labelled for the wrong surgeon.(i was covering for a colleague.) when correct plan was opened the ct info was used to verify patient on table and then surgeon was keen to proceed with his pins without reviewing the plan even after i requested.Following femoral neck cut before bone registration we notice landmarks were reversed due to the wrong side and we abandoned and went to manual.Surgeon was happy to continue manually and with his final result, using the pre plan as a visual guide for implant sizing.Pelvic pins inserted in stab incision of the illiac crest.Small impaction check point placed in greater trochanter was inserted (standard procedure for robotic hips).Case was then completed manually rendering the pelvic pins/check point unnecessary.
|
|
Event Description
|
Sales rep reported that the surgical plan was planned for the wrong operative side.After putting the pins in the patient, this issue was noticed and the surgeon completed the case manually.The rep mentioned that the surgeon hadn¿t taken the time to review the pre plan properly before putting the pins in the pelvis.Hence the delayed time to catch the issue.Surgical delay < 5 minutes case was completed manually.Additional information received from rep: patient time out.Realised wrong plan was loaded, due to patient name and noticed the two plans for the day had each plan been labelled for the wrong surgeon.(i was covering for a colleague.) when correct plan was opened the ct info was used to verify patient on table and then surgeon was keen to proceed with his pins without reviewing the plan even after i requested.Following femoral neck cut before bone registration we notice landmarks were reversed due to the wrong side and we abandoned and went to manual.Surgeon was happy to continue manually and with his final result, using the pre plan as a visual guide for implant sizing.Pelvic pins inserted in stab incision of the illiac crest.Small impaction check point placed in greater trochanter was inserted (standard procedure for robotic hips).Case was then completed manually rendering the pelvic pins/check point unnecessary.
|
|
Manufacturer Narrative
|
Reported event: an event regarding a incorrect patient data and user error involving 3.0 rio® robotic arm - mics, catalog: 209999 was reported, robot serial #: unknown.It was reported that the surgical plan was planned for the wrong operative side.After putting the pins in the patient, this issue was noticed and the surgeon completed the case manually.The rep mentioned that the surgeon had not taken the time to review the pre plan properly before putting the pins in the pelvis.Method & results: product evaluation and results: not performed as case session data was not provided.Product history review: a review of the device history records could not be performed as the robot serial number was not reported.Complaint history review: a search of the complaint database under device identification pn 209999 reports no similar complaints for tha software - incorrect patient data.Conclusions: the failure could not be determined as no case session data or logs were provided after three communication attempts were made.No additional investigation or specific actions are required at this time.If additional information is received such as the session files, then the complaint will be reopened.Corrective action/preventive action: a search of the nc/capa database under device identification pn 209999 reports no records related to tha software - incorrect patient data h3 other text : device not returned.
|
|
Search Alerts/Recalls
|