| Model Number |
M00583100 |
| Medical Device Problem Codes |
Break (1069); Deformation Due to Compressive Stress (2889); Material Deformation (2976)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
08/28/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Block h6: imdrf device code a0401 captures the reportable event of cutting wire broken.Imdrf device code a0406 captures the reportable event of cutting wire kinked.
|
| |
|
Event or Problem Description
|
|
Note: this report pertains to one of two devices that were used in the same patient and procedure.It was reported to boston scientific corporation (bsc) that a truetome jag 44 was attempted to be used in the bile duct during an endoscopic retrograde cholangiopancreatography (ercp) procedure performed on (b)(6) 2025.During the procedure, incision of the papilla was performed and the cutting wire on the proximal side of the device broke.A second truetome jag 44 was attempted to be used but, during incision of the papilla, the cutting wire also broke on the proximal side of the device.The procedure was completed with a non-bsc device.It was reported that no part of the cutting wires detached and fell into the patient.Photos of the complaint devices outside the patient were provided by the customer and both showed the cutting wire was broken and kinked.There were no patient complications reported as a result of this event.
|
| |
|
Additional Manufacturer Narrative
|
|
Block h6: imdrf device code a0401 captures the reportable event of cutting wire broken.Imdrf device code a0406 captures the reportable event of cutting wire kinked.Block h11: (investigation result) the returned truetome jag 44 was analyzed, and a visual evaluation noted that the cutting wire was blackened, kinked, and broken at 10 mm from the proximal pierce hole.Additionally, media evaluation noted that the cutting wire was kinked and broken.No other problems with the device were noted.The reported event of cutting wire break was confirmed.Upon analysis, it was found that the cutting wire was blackened, kinked, and broken at 10mm from the proximal pierce hole.Based on the condition of the device, the wire break could have been generated if there was contact between the device and the scope during energization or if the generator exceeded the maximum of voltage during the procedure.Also, energizing the device prior to performing sphincterotomy can compromise the cutting wire integrity and cause a premature cutting wire fatigue.Once the cutting wire breaks, any attempt to remove the device from the scope can lead to the broken section hitting the working channel of the scope.This can kink the cutting wire.It is most likely that procedural or anatomical factors encountered during the use of the device could have affected the device performance and its integrity.Based on all gathered information, the most probable root cause is adverse event related to procedure.A labeling review was performed and, from the information available, this device was used per the instructions for use (ifu) / product label.
|
| |
|
Event or Problem Description
|
|
Note: this report pertains to one of two devices that were used in the same patient and procedure.It was reported to boston scientific corporation (bsc) that a truetome jag 44 was attempted to be used in the bile duct during an endoscopic retrograde cholangiopancreatography (ercp) procedure performed on (b)(6) 2025.During the procedure, incision of the papilla was performed and the cutting wire on the proximal side of the device broke.A second truetome jag 44 was attempted to be used but, during incision of the papilla, the cutting wire also broke on the proximal side of the device.The procedure was completed with a non-bsc device.It was reported that no part of the cutting wires detached and fell into the patient.Photos of the complaint devices outside the patient were provided by the customer and both showed the cutting wire was broken and kinked.There were no patient complications reported as a result of this event.
|
| |
|
Search Alerts/Recalls
|