It was reported that during a cori assisted tka surgery while cutting the anterior femur, the real intelligence robotic drill had a disconnect error message (case (b)(4)), it was proceed to quit out of the case and was then prompted an "internal error" message (case-(b)(4)).They dismissed the message and disconnected the drill.The drill was then reconnected and were able to resume the surgery.Later, while entering the tibia bone removal screen, a bone model generation error message was prompted (case(b)(4)), then they added a couple more collection points to the tibia and were able to proceed to tibia bone removal.The procedure was completed with a minimal delay (fewer than 30 minutes) using the same devices.No patient injuries and no other complications were reported.
|
The real intelligence cori, pn: rob10024, sn: (b)(6) used for treatment was not returned to the designated complaint unit for evaluation, and the log files required to confirm the internal error as well as the tibia bone mesh generation error were not provided.Therefore, visual and functional inspections and log/case file assessments could not be performed.The reported errors could not be confirmed, however, both errors are likely to be occurrences of known software issues that have been corrected and released in cori-v1.4.3 software.In the event of a system failure, refer to the recovery procedure guidelines in the cori user¿s manual.A failure can consist of, but is not limited to, a system software crash, unrecoverable hardware failure, handpiece failure with no backup available, tracker failure or loss of contact with bone that is unrecoverable, etc.Refer to the real intelligence cori for knee arthroplasty user manual for data point collection, including tibia free collection.If a collection error occurs, a message displays, reporting the specific error to the user, and providing instruction for solution.Most indications require clearing the message from the screen, by pressing ok, and performing the steps again to re-collect.This situation is captured in the risk assessment released at the time of the complaint.The failure mode and associated risk have been anticipated within the risk file and that the documented risk level is still adequate.A review of manufacturing records indicate the software met all specifications upon release into distribution.A complaint history review found similar reports.Escalation actions applicable to the scope of the reported complaint have been identified, and it was determined that no further action is required at this time.This issue will be continuously monitored through complaint investigation and post market surveillance.If the case files associated with this event are returned at a future date, this evaluation will be reopened for investigation.No containment or corrective actions are recommended at this time.
|