| Model Number |
N/A |
| Medical Device Problem Codes |
Disconnection (1171); Fracture (1260)
|
| Health Effect - Clinical Code |
No Known Impact Or Consequence To Patient (2692)
|
| Date of Event |
06/12/2019
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
This medwatch is submitted to send the initial report of this complaint.Product is not available and it will not be returned, no evaluation could be performed.The review of the device history records is ongoing.Investigation still in progress.Product not available.
|
| |
|
Event or Problem Description
|
|
Mobi-c p&f us : disassembled before insertion.As reported by sales rep, : implant fell apart upon opening, before insertion.No other information was provided.No patient impact or surgery complication were reported.Additional information was requested.Investigation still in progress.
|
| |
|
Additional Manufacturer Narrative
|
|
Without a product return, no product evaluation is able to be conducted.Current information is insufficient to permit a valid conclusion about the cause of this event.If additional information is obtained that adds value to the relevant content of this report and/or a conclusion can be drawn, a follow-up report will be sent.
|
| |
|
Event or Problem Description
|
|
It was reported that the peek cartridge was broken when the package was opened.The implant never touched the patient and a second implant was opened and used to complete the surgery.No patient impacts were reported.
|
| |
|
Event or Problem Description
|
|
It was reported that the mobi-c peek cartridge was broken when the package was opened.The implant never touched the patient and a second implant was opened and used to complete the surgery.No patient impacts were reported.
|
| |
|
Additional Manufacturer Narrative
|
|
Additional information in b5, d4 (udi number), e4, h4, and h6: method, results, and conclusions codes.The implant was not returned for evaluation, so no results are available and no conclusions can be drawn.A review of the dhr did not find any issues which would have contributed to this event.
|
| |
|
Search Alerts/Recalls
|