Model Number 9013.02.303 |
Device Problem
Connection Problem (2900)
|
Patient Problem
No Known Impact Or Consequence To Patient (2692)
|
Event Date 07/29/2015 |
Event Type
malfunction
|
Manufacturer Narrative
|
No anomalies which could have contributed to the issue by checking the manufacturing charts of the lot number of instrument involved.No other similar complaints registered on these lot number, on a total of (b)(6) (handles) and (b)(6) (sleeves) instruments manufactured with these lot number.We will receive the instruments involved and analyze them before submitting our final report.
|
|
Event Description
|
Intra-op issue during a surgery dated (b)(6) 2015.It was difficult to insert the sleeve (product code 9013.52.141) onto the handle (product code 9013.02.303).It appeared that the problem was in the handle.The event occurred in (b)(6).
|
|
Manufacturer Narrative
|
No anomalies which could have contributed to the issue by checking the manufacturing charts of the lot # of handle involved.No other similar complaints registered on this lot #, on a total of (b)(4) (handles) manufactured with this lot #.We received the handle involved.A dimensional check was performed on the handle and no anomaly was detected on the part of the instrument intended to be connected to the sleeve.The functionality of the handle was tested with a sleeve available in house and the coupling handle-sleeve was functional.A total of three (3) similar complaints were reported, involving difficulty to engage/disengage the sleeve to the handle, on a total of (b)(4) smr inserter-extractor handle manufactured with the product codes 9013.02.302-9013.02.303.The other two cases are still under evaluation (instruments involved not returned yet).No corrective action has been planned for this specific event.Limacorporate will keep monitoring the market on the reoccurrence of this event.
|
|
Event Description
|
Intra-op issue during a surgery dated (b)(6) 2015.It was difficult to insert the sleeve (product code 9013.52.141) onto the handle (product code 9013.02.303).It appeared that the problem was in the handle.Event occured in (b)(6).
|
|
Search Alerts/Recalls
|