|
Catalog Number 530.705 |
Device Problems
Appropriate Term/Code Not Available (3191); Physical Resistance/Sticking (4012); Complete Loss of Power (4015)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Type
malfunction
|
Event Description
|
It was reported that the battery reamer/drill device was out of service.It was further reported that the device was not running.During in-house engineering evaluation, it was observed that the trigger was sticky, and the device would not run.It was further determined that the device had corrosion/rusting/pitting and fluid ingress.It was further determined that the device failed pretest for general condition, check cannulation, check for sticky trigger, check function of device and check power with power test bench.It was not reported if the device was used in surgery, or if there was patient involvement.It was not reported if there were any delays in a surgical procedure or if a spare device was available for use.There were no reports of injuries, medical intervention or prolonged hospitalization.The exact date of the event was unknown.All available information has been disclosed.If additional information should become available, a supplemental medwatch report will be submitted accordingly.
|
|
Manufacturer Narrative
|
This report is being submitted pursuant to the provisions of 21 cfr, part 803.This report may be based on information which has not been investigated or verified prior to the required reporting date.This report does not reflect a conclusion by depuy synthes, or its employees that the report constitutes an admission that the product, depuy synthes, or its employees caused or contributed to the potential event described in this report.Device was used for treatment, not diagnosis.If information is obtained that was not available for this medwatch, a supplemental medwatch report will be filed as appropriate.H10 additional narrative: device evaluation: the actual device was returned for evaluation.During repair, an evaluation was performed and it was determined that the sticky trigger, identified during service and evaluation was confirmed.The assignable root cause was determined to be traced to user, which is use error.Udi: (b)(4).
|
|
Search Alerts/Recalls
|
|
|