|
Model Number MON-000006 |
Device Problems
Adverse Event Without Identified Device or Use Problem (2993); Appropriate Term/Code Not Available (3191)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 08/17/2022 |
Event Type
malfunction
|
Manufacturer Narrative
|
The risk of a prolonged or delayed procedure is documented in 105-000363-00, rev h, dfmea arms & idms, platform 2.Based on the available information for this event, the root cause is still undetermined pending investigation.
|
|
Event Description
|
It was reported that the patient underwent a monarch bronchoscope procedure.During that procedure, it was reported the monarch system had multiple 1403-50-0-0 ethercat faults.The physician did not have a backup scope, removed the scope, and aborted the case.
|
|
Manufacturer Narrative
|
This follow-up report is being submitted to relay additional information.The following there was no communication between the ethercat chain and the slave application (two power distribution units, one staging motor, and two robotic arms).This could be due to multiple reasons- umbilical cable between the tower and cart is damaged or not plugged in, firmware defect or hardware defect in one of the slave devices, interplay between hardware and firmware.Hardware malfunction could be introduced by external factors like temperature changes, high frequency noise in the alternating current (ac) input of the power supply.The issue is typically resolved after a hard power cycle is performed.The 1403 fault was followed by an 804 or e-stop fault.Because of the interruption in communication (ethercat) chain between the tower and cart that triggered the 804 e-stop fault.The system normally would need to be rebooted when an 804 fault occurs to resolve the issue.The system behaved as intended.The field service engineer (fse) was not able to replicate the fault.As such, a cause could not be determined.A review for similar report shows this to be a known issue where a cause is specific to each individual case.A review of the device history record (dhr) for the system did not reveal any nonconforming issue that would relate to the reported incident.The incident will continue to be tracked in regular trend review meetings.
|
|
Search Alerts/Recalls
|
|
|