|
Model Number 209999 |
Device Problems
Incorrect, Inadequate or Imprecise Result or Readings (1535); Output Problem (3005)
|
Patient Problem
No Known Impact Or Consequence To Patient (2692)
|
Event Date 10/16/2019 |
Event Type
malfunction
|
Manufacturer Narrative
|
As part of the 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
|
During the straight cuts on the femur (anterior), a vizidisc popped off of the femur array.The surgeon pressed the array back down and then checked his anterior cut to find it was notching.We validated that the registration was off (both by checking the cut with the planar probe and check point).We re-registered the bone where we had not made cuts yet, and completed the femur cuts.The plan was planned 2 degrees away from notching.He redid his cuts manually and ended up going ts.(note: no checkpoints were used.The surgeon picks a spot on the array clamp and uses that as the checkpoint.Case type: tka.Surgical delay: 15 minutes.Procedure was completed manually.
|
|
Event Description
|
During the straight cuts on the femur (anterior), a vizidisc popped off of the femur array.The surgeon pressed the array back down and then checked his anterior cut to find it was notching.We validated that the registration was off (both by checking the cut with the planar probe and check point).We re-registered the bone where we had not made cuts yet, and completed the femur cuts.The plan was planned 2 degrees away from notching.He redid his cuts manually and ended up going ts.(note: no checkpoints were used.The surgeon picks a spot on the array clamp and uses that as the checkpoint.Case type: tka.Surgical delay: =15 minutes.Procedure was completed manually.
|
|
Manufacturer Narrative
|
Reported event: an event regarding implant notching involving 3.0 rio® robotic arm - mics, catalog: 209999 was reported.It was reported ¿during the straight cuts on the femur (anterior), a vizidisc popped off of the femur array.The surgeon pressed the array back down and then checked his anterior cut to find it was notching.We validated that the registration was off (both by checking the cut with the planar probe and check point).We re-registered the bone where we had not made cuts yet and completed the femur cuts.The plan was planned 2 degrees away from notching.He redid his cuts manually and ended up going ts.(note: no checkpoints were used.The surgeon picks a spot on the array clamp and uses that as the checkpoint.¿ method & results: product evaluation and results: the problem statement for this complaint investigation was regarding the system failing to prevent the anterior cut to be prepared deeper than planned, resulting in a notch on the femur.Upon investigating, it may be concluded that a combination of sub-optimal bone registration and bone preparation was the root cause of the notch that was observed on the femur.Product history review: review of the device history records associated with rio 640 indicate quality inspection procedures were completed with no reported discrepancies.Complaint history review: a search of the complaint database under device identification pn 209999 reports similar complaints for tka software - inaccurate resection.The complaint record numbers are: (b)(4).Conclusions: the problem statement for this complaint investigation was regarding the system failing to prevent the anterior cut to be prepared deeper than planned, resulting in a notch on the femur.Upon investigating, it may be concluded that a combination of sub-optimal bone registration and bone preparation was the root cause of the notch that was observed on the femur.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 - inaccurate resection.
|
|
Search Alerts/Recalls
|
|
|