| Model Number |
N/A |
| Medical Device Problem Code |
Failure to Cut (2587)
|
| Health Effect - Clinical Code |
Perforation of Vessels (2135)
|
| Date of Event |
03/28/2023
|
|
Type of Reportable Event
|
Serious Injury
|
|
Additional Manufacturer Narrative
|
|
Zimmer biomet complaint (b)(4).D2: product code: lry.Customer has indicated that the product is in process of being returned to zimmer biomet for investigation.Once the investigation has been completed, a follow-up mdr will be submitted.
|
| |
|
Event or Problem Description
|
|
It was reported by the rep that the punch did not make a clean cut and the surgeon had to do additional suturing to the site.Delay is thought to be 2 to 3 minutes.Attempts have been made and additional information on the reported event is unavailable at this time.
|
| |
|
Additional Manufacturer Narrative
|
|
This follow-up report is being submitted to relay additional information.A visual inspection was conducted on the returned punch.The punch was returned with original packaging, the packaging was opened and the punch shows light signs of use.When the plunger was pulled back on the punch the cutting tip full retracted into the punch body as designed.There were no signs of binding or manufacturing defects.When the plunger was released the punch returned to its original position as designed.The complaint cannot be recreated.Review of the device history record(s) identified no deviations or anomalies during manufacturing.A definitive root cause cannot be determined.If any further information is found which would change or alter any conclusions or information, a supplemental report will be filed accordingly.Zimmer biomet will continue to monitor for trends.
|
| |
|
Event or Problem Description
|
|
No further event information is available at the time of this report.
|
| |
|
Additional Manufacturer Narrative
|
|
This follow-up report is being submitted to relay additional information.Upon reassessment of the reported event, it was determined to be not reportable as this component was reported under the incorrect mfr number.The event will be reported under the correct mfr number 0002242056-2024-00007; therefore, this report should be voided.
|
| |
|
Event or Problem Description
|
|
Upon reassessment of the reported event, it was determined to be not reportable as this component was reported under the incorrect mfr number and should therefore be voided.
|
| |
|
Search Alerts/Recalls
|