Note: this report pertains to a spyscope ds and a spyglass ds controller used during the same procedure.It was reported to boston scientific corporation that a spyscope ds and a spyglass ds controller were used in the bile duct during an endoscopic retrograde cholangiopancreatography (ercp) procedure performed on (b)(6) 2021.Prior to the procedure, the spyscope ds ii catheter was connected into the controller.Shortly after, a series of dots and lines presented on the screen.The controller then randomly switched off and it could not be turned on again.Connections were tested and still the problem was not resolved.The procedure was not completed due to this event.There were no patient complications reported as a result of this event.
|
Note: this report pertains to a spyscope ds and a spyglass ds controller used during the same procedure.It was reported to boston scientific corporation that a spyscope ds and a spyglass ds controller were used in the bile duct during an endoscopic retrograde cholangiopancreatography (ercp) procedure performed on (b)(6) 2021.Prior to the procedure, the spyscope ds ii catheter was connected into the controller.Shortly after, a series of dots and lines presented on the screen.The controller then randomly switched off and it could not be turned on again.Connections were tested and still the problem was not resolved.The procedure was not completed due to this event.There were no patient complications reported as a result of this event.The device was not returned.
|
Block h6 (device codes): medical device problem code a27 is being used to capture the reportable event of aborted/cancelled procedure.Block h10: the returned spyglass ds digital controller was analyzed by enercon technologies, and no functional problem found.No errors in the error log.The light engine was disassembled.The catheter interface contacts and connector socket assembly were cleaned.Replaced top cover and cover gasket.Performed light engine calibration and tests.Performed electrical safety tests.The unit passed all tests.The reported event was not confirmed since they were unable to duplicate the customer described problem and was not verified according to product analysis.Upon analysis, the problem is unlikely related to manufacturing, as product analysis identified problems related to use and maintenance and did not identify any manufacturing defect.In addition, during a device history record review conducted by the sfmd, it was confirmed that the device met all manufacturing specifications.Even though the problem was not verified, the unit presented cosmetic damage on the top cover, front panel and the bumper.Based on this information, it is likely that the problem presented was intermittent.Although the number of procedures/recycles of the unit are unknown, improper handling of the device or wear/tear on internal components over time likely contributed to the event.Therefore, the conclusion code selected for this event is cause traced to maintenance, which indicates that problems are traced to improper routine or preventative maintenance.A review of the manufacturing documentation for this device revealed that no anomalies or deviations related to the event occurred during manufacturing.A search of the complaint database confirmed that no similar complaint exist for the specified lot.
|