|
Catalog Number LONG |
Device Problem
Naturally Worn (2988)
|
Patient Problem
No Known Impact Or Consequence To Patient (2692)
|
Event Date 05/23/2017 |
Event Type
malfunction
|
Manufacturer Narrative
|
(b)(4).The actual device has been returned and is currently pending evaluation.Once the evaluation of the device has been completed, a supplemental medwatch report will be sent accordingly.
|
|
Event Description
|
It was reported that during an unspecified surgical procedure, it was observed that the long attachment device bearings were worn.It was reported that there was no delay in the procedure due to the event as an unspecified spare device was available for use.There was patient involvement reported.There were no patient or user injuries reported.It was reported there was no medical intervention or prolonged hospitalization.All available information has been disclosed.If additional information should become available, a supplemental medwatch report will be submitted accordingly.
|
|
Manufacturer Narrative
|
The actual device was returned for evaluation.Reliability engineering evaluated the device and determined that the device had worn bearings.Therefore, the reported condition was confirmed.An assessment was performed on the device which found that the device failed the cutter insertion assessment.It was also observed that the device had a bend on the tip of the nose tube and excessive scratches on the nose cone.During repair it was observed that the bearings were worn out and loose creating a situation where the cutter is not able to be inserted.It was determined that this is because the bearings are no longer in axial alignment not allowing the cutter to pass through.The assignable root cause of this condition was determined to be component damage from normal use over time, the failure was caused by worn out bearings.It was further determined that the condition the nose tube and the nose cone is consistent with mishandling of the device and/or from excessive force being placed on the device during use.The assignable root cause was determined to be component damage due to user error.If additional information should become available, a supplemental medwatch will be submitted accordingly.
|
|
Search Alerts/Recalls
|
|
|