Reported event: the reported device is a 3.0 rio® robotic arm - mics, catalog: 209999.Device history review: a review of the dhr associated with rio 285 found quality inspection procedures and the pt review successfully passed.Complaint history: based on the device identification (pn 209999) the complaint databases were reviewed from 2011 to present for similar reported events regarding having to register the robot multiple times.There were no other reported events for the listed catalog number.Conclusion: the session and vp log data from the case was reviewed.An analysis of the session file, implant planning page, the checkpoints values, bone registration values, rio registration values, bone preparation checkpoints values, burrlist, sequence of events, and base array placement was performed.The reason that rio registration had to be performed multiple times was that the base array was either not secured properly, bumped repeatedly, or a combination of the two.This leads to a reduction in accuracy and causes the system to lose track of array relationships.There are three likely causes for base array movement: a loose fisso arm.If the base array arm is not locked tightly into position, the arm could slowly fall due to gravity.Minor movement could cause large translation of the base array with regard to the camera due to the distance between the two.The base array or fisso arm is bumped.If caution is not taken to avoid the fisso arm or base array in the or, the array could be bumped and move.It has been shown that if the fisso arm is locked in position very close to the shell of j1, the shell could actually bump the arm.This may also be cause by a tight drape over the robot, where tension on the drape pulls the arm in a direction.All verification values were within the accuracy tolerance region.The mako operated as expected.No system defect or malfunction is suspected.
|