It was reported that when inserting the bur during the setup phase during a cori assisted ukr surgery, a system time out (the robotic drill has been deactivated) message prompted after pressing the ¿unlock¿ button (b)(4).Multiple attempts to recover were conducted including pressing ¿continue¿, ¿quit¿ and exiting out of the case and resuming the case.They disconnected the drill multiple times and had an equipment swap with two drills.The same error messages continued to persist and a full reboot of the system was conducted with no resolution (b)(4).A "communication failure" message and an internal error (the system has detected the application unexpectedly exited) were prompted (b)(4).They presumed that there was a connection problem associated with the console.So they borrowed a new cori console and tray from a nearby facility.They plugged in two of the previous "bad drills" into the brand new console and the error message still prompted.Therefore, the issue was caused by the drills and not the console (b)(4).To recover they used a new drill from a different facility and plugged that in to the new console and they were able to proceed with the case.The procedure was completed with a delay of over one hour with the patient under anesthesia and open on the table by using the s+n back-up device.The outcome of the patient¿s surgery was successful and there was no harm to the patient due to this error.
|
H3, h6: the real intelligence cori, pn: rob10024, sn: sn000120 used for treatment was not returned to the designated complaint unit for evaluation.Although the product was not returned the software files were downloaded from the device and provided for investigation.The system time out error was confirmed during bur loading.However, the necessary logs (naviosystem.Log and xsession.Log) to further identify the cause were not provided.Although the cause of the error was not identified, factors that may have contributed to the reported issue may have been associated with the drill or the software.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.A review of prior escalation actions was performed and found no actions that are applicable to the scope of the reported complaint.This issue will be continuously monitored through complaint investigation and post market surveillance.Based on the investigation, no containment or corrective actions are recommended at this time.
|