BOSTON SCIENTIFIC CORPORATION EXALT CONTROLLER; DUODENOSCOPE AND ACCESSORIES, FLEXIBLE/RIGID
|
Back to Search Results |
|
Model Number M00542430 |
Device Problem
Optical Problem (3001)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 02/01/2024 |
Event Type
malfunction
|
Event Description
|
Note: this report pertains to one of two devices used during the same procedure.Refer to manufacturer report number 3005099803-2024-00770 for the exalt controller, and 3005099803-2024-00890 for the exalt model d scope it was reported to boston scientific corporation that an exalt model d controller was used during an unspecified procedure on an unknown date.Thought the procedure, intermittent loss of the image was experienced.It was reported that this issue manifested across multiple exalt model d scopes, necessitating the facility to use tape and hold the scopes to secure the controller's connection with the exalt model d scopes as a workaround to prevent further image loss.At the time of this report, the information suggests that this issue has been observed across various cases.However, despite good faith efforts (gfe), precise details regarding the number and specifics of the affected procedures remain unknown.No patient complications were reported as a result of this event.
|
|
Manufacturer Narrative
|
B3: the exact date of the event is unknown.The provided event date, (b)(6) 2024, was chosen as the best estimate based on the date that the manufacturer became aware of the event, (b)(6) 2024.H6 (device codes): problem code a06 captures the reportable event of loss of visualization inside the patient.
|
|
Manufacturer Narrative
|
Block b3: the exact date of the event is unknown.The provided event date, 02/01/2024, was chosen as the best estimate based on the date that the manufacturer became aware of the event, 02/08/2024.Block h6 (device codes): problem code a06 captures the reportable event of loss of visualization inside the patient.Block h10: with all the available information boston scientific concludes that the reported event was able to be confirmed, as the customer's complaint was verified.Device analysis: the controller and single-use device (sud) assembly is damaged by fluid ingress.The light engine requires new catheter contacts and socket assembly.The controller also requires a rebuild to repair.A discolored connector socket is observed and there's evidence of fluid ingress and cover seams.Labeling review: a labeling review was performed and, from the information available, this device was used per the instructions for use (ifu) / product label.Device history review: a review of the manufacturing documentation for this device revealed that no anomalies or deviations related to the event occurred during manufacturing.Risk review: a risk review was completed and confirmed that the event of loss of visualization was defined in the risk documentation and is documented accordingly in the prr table.This event type has been accounted for during product risk analysis to support acceptable risk benefit for the product.Investigation conclusion: according to the report provided, the console was damaged by fluid ingress.It is likely that the fluid ingress evidence is a result of cleaning solution getting into the housing and contacting the internal components.Therefore, based on all gathered information, the conclusion code selected for this event is cause traced to maintenance, which indicates that problems are traced to improper routine or preventative maintenance.
|
|
Event Description
|
It was reported to boston scientific corporation that an exalt model d controller was used during an unspecified procedure on an unknown date.Through the procedure, intermittent loss of the image was experienced.It was reported that this issue manifested across multiple exalt model d scopes, necessitating the facility to use tape and hold the scopes to secure the controller's connection with the exalt model d scopes as a workaround to prevent further image loss.At the time of this report, the information suggests that this issue has been observed across various cases.However, precise details regarding the number and specifics of the affected procedures remain unknown.No patient complications were reported as a result of this event.
|
|
Search Alerts/Recalls
|
|
|