H10: h3, h6: the device was used in treatment and it was reported that the system would not boot up.The software version was not recorded, but dhr review shows that all navio software versions released to the field have been validated.A complaint history review identified prior similar event, this issue will continue to be monitored.This failure is an identified failure mode within the risk file.The navio surgical system user's manual released at the time of the complaint provides instructions for the user in the "troubleshooting information" section.The point of failure for this case was during startup: "navio¿ surgical system fails to launch" and the solution was "contact smith & nephew robotics customer service".Accordingly, product labeling has been ruled out as a cause of the complaint.We could not confirm if there was a relationship established between the reported event and the device.The log files were returned for evaluation and the review revealed an error in communication between the cpu and ups (see photo in complaint folder).The nature of the error relates itself to the usb cable between the cpu and ups being damaged or disconnected in some way.Other possible causes could have been a bad usb receptacle on the ups, or a bad usb port on the cpu.Service was onsite and the system booted safely several times with no issues, thus reducing the probability of deficient components.The most likely explanation is an undetected disconnection in the usb cable caused the initial error(s).However, the ups, cpu, and usb cable were replaced for precautionary reasons.These results support that the most likely cause was that a usb cable was not fully seated.The root cause was undetermined after investigation.
|