| Model Number |
VPR-GW-FT14 |
| Medical Device Problem Codes |
Material Separation (1562); Noise, Audible (3273)
|
| Health Effect - Clinical Codes |
Foreign Body In Patient (2687); No Known Impact Or Consequence To Patient (2692)
|
| Date of Event |
11/30/2018
|
|
Type of Reportable Event
|
Serious Injury
|
|
Additional Manufacturer Narrative
|
|
Analysis of the reported device is in progress.A supplemental report will be submitted when the device analysis is completed.Csi id: (b)(4).
|
| |
|
Event or Problem Description
|
|
The viperwire fractured following an unusual audible noise heard during the procedure in the superior femoral artery, which was 40-70% stenosed.The wire fragment was located in the external illiac artery, but attempts to remove the fragment over the next two hours were unsuccessful.A hematoma formed at the access site.Anticoagulants were administered to the patient and the fragment was then surgically removed.The patient was discharged home the following day.
|
| |
|
Additional Manufacturer Narrative
|
|
(b)(4).
|
| |
|
Additional Manufacturer Narrative
|
|
Failure analysis conclusion: the viperwire and orbital atherectomy device (oad) were returned for investigation.The initial visual and tactile examination of the guide wire revealed the core wire to be fractured near the distal end.The fracture site exhibited post fracture surface wear as a result of the guide wire having been spun over after the fracture.The distal fractured section was not returned.Scanning electron microscopy of the guide wire fractures revealed the guidewire to be severely ground on the outer diameter.The core wire fracture sites and face also exhibited surface wear resulting in outside diameter reduction.It is hypothesized that the proximal guide wire fracture may be a result of the device spinning over a bend or kink in the guide wire.However, the exact cause of the fracture remains unknown.The oad was tested and spun during all three speeds with no abnormalities observed.At the conclusion of the failure analysis, the guide wire fracture was confirmed.However, the report of audible noise could not be confirmed through analysis.The device history records for these viperwire and oad lot numbers have been reviewed.No issues or discrepancies were noted during this review that would have contributed to the reported events.Prior to distribution the wire and device met material, assembly, and quality control requirements.Csi id: (b)(4).
|
| |
|
Additional Manufacturer Narrative
|
|
The device fragment was returned to csi for analysis and the investigation was reopened.Scanning electrom microscopy (sem) showed the proximal fracture face to be consistent with the mating fracture face and supports the original conclusions regarding the fracture.Sem analysis revealed the presence of ductile torsional stresses on the spring tip fracture face of the returned guide wire fragment.Although the exact root cause of the spring tip fracture is undetermined, the sem analysis is consistent with spinning over a tight bend or kink in the wire.Csi id: (b)(4).
|
| |
|
Search Alerts/Recalls
|