|
|
| Model Number |
286725020 |
| Medical Device Problem Code |
Break (1069)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
09/29/2021
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Complainant part is expected to be returned for manufacturer review/investigation, but has yet to be received.The investigation could not be completed; no conclusion could be drawn, as no product was received.Based on the information available, it has been determined that no corrective and/or preventative action is proposed.This complaint will be accounted for and monitored via post market surveillance activities.If additional information is made available, the investigation will be updated as applicable.Device was used for treatment, not diagnosis.If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
|
| |
|
Event or Problem Description
|
|
Device report from (b)(6) reports an event as follows: it was reported that on (b)(6) 2021 during a spinal fusion (l1) to treat diffuse idiopathic skeletal hyperostosis (dish), the tip of the driver shaft broke off during the extra screw tightening against the hardened bone.The fragment was removed from the patient¿s body.The procedure was completed with less than a 30-minute surgical delay.Concomitant device: unknown screws (part# unknown, lot# unknown, quantity 1).This report is for one (1) viper 2 system driver, cannulated t20.This is report 1 of 1 for (b)(4).
|
| |
|
Additional Manufacturer Narrative
|
|
Depuy synthes is submitting this report pursuant to the provisions of 21 cfr, part 803.This report may be based on information which depuy synthes has not been able to investigate or verify prior to the required reporting date.This report does not reflect a conclusion by fda, depuy synthes or its employees that the report constitutes an admission that the device, depuy synthes, or its employees caused or contributed to the potential event described in this report.If the information is unknown, not available or does not apply, the section/field of the form is left blank.H10 additional narrative: h3, h4, h6- visual analysis of the returned sample revealed that viper2 t20 hexlobe driver shaf the tip of the driver was broken, and broken piece was also returned no other issues were identified.The dimensional inspection was not performed due to post manufacturing damage.The observed condition of viper2 t20 hexlobe driver shaf in the device was consistent with a random component failure that may have been caused by exposure to unintended forces.As part of depuy synthes quality process, all devices are manufactured, inspected, and released to approved specifications.The overall complaint was confirmed as the observed broken condition of the viper2 t20 hexlobe driver shaf.While no definitive root cause could be determined, it is probable that the viper2 t20 hexlobe driver shaf was broken due to the unintended forces.There was no indication that a design or manufacturing issue contributed to the complaint.Based on the investigation findings, it has been determined that no corrective and/or preventative action is proposed.Additional monitoring for any potential safety signals will be conducted through complaint trending and other post-market safety surveillance activities.Device history lot: a review of the receiving inspection (ri) for viper2 t20 hexlobe driver shaf was conducted identifying that lot number so2028626 was released in a single batch.Batch1: lot qty of units were released on 05 apr 2017 with no discrepancies.As a result, the ri identified no issues during the manufacturing and release of this device that could have contributed to the problem reported by the customer.Device was used for treatment, not diagnosis.If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
|
| |
|
Search Alerts/Recalls
|
|
|