Model Number ROSA ONE 3.1 |
Device Problems
Connection Problem (2900); Application Program Freezes, Becomes Nonfunctional (4031)
|
Patient Problems
No Patient Involvement (2645); No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 02/09/2021 |
Event Type
malfunction
|
Manufacturer Narrative
|
The device has not been evaluated yet for investigation purpose.Once the evaluation is performed, a follow-up medwatch report will be submitted.Unique identifier (udi) #: (b)(4).
|
|
Event Description
|
The robot would not connect to the controller the first try.The clinical representative (cr) opened an old patient folder to connect to the controller before the case started.The controller did not connect when the cr tried to initiate contactless registration.The software appeared to freeze and then eventually (>30 seconds after initiating controller connection) a windows error message popped up and stated that the rosannabrain.Exe software was not responding and asked if he would like to restart the program.Upon restart, the same thing happened.The software froze and the system never connected to the controller.At this point, the cr shutdown and unplugged the system for a minute or two.The cr restarted the system, opened the same patient folder and was able to connect the second time.There was no delay to the case and no patient involvement.
|
|
Event Description
|
The robot would not connect to the controller the first try.The clinical representative (cr) opened an old patient folder to connect to the controller before the case started.The controller did not connect when the cr tried to initiate contactless registration.The software appeared to freeze and then eventually (>30 seconds after initiating controller connection) a windows error message popped up and stated that the rosannabrain.Exe software was not responding and asked if he would like to restart the program.Upon restart, the same thing happened.The software froze and the system never connected to the controller.At this point, the cr shutdown and unplugged the system for a minute or two.The cr restarted the system, opened the same patient folder and was able to connect the second time.There was no delay to the case and no patient involvement.
|
|
Manufacturer Narrative
|
A full analysis of the data logs has been performed and concluded that both software freeze occurred when attempting to connect the arm for automatic registration and were due to a crash of the application.No other elements permit to determine the cause for the issue.
|
|
Search Alerts/Recalls
|