Model Number 261221 |
Device Problem
Dull, Blunt (2407)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 06/14/2022 |
Event Type
malfunction
|
Manufacturer Narrative
|
An investigation has been initiated based on the reported information.Upon completion of the investigation, a follow-up report will be submitted.
|
|
Event Description
|
A physician reported an issue with a perforator (id (b)(6)).The physician couldn't drill the bone as expected, and felt the perforator was too dull.He had difficulty perforating during the procedure, however the procedure was completed with the same device.No adverse consequences to the patient were observed.No information about surgical delay was available.The drill used with the perforator was a midas.As per customer, it is unknown if the perforator clicked in place on the drill.It is also unknown if the recommended spring tests were performed between each burr hole.
|
|
Manufacturer Narrative
|
The disposable perforator was returned for evaluation.Device history record (dhr) - there is no indication that the production process may have contributed to this complaint.All test results passed procedural specifications.Failure analysis - the perforator unit was inspected using the unaided eye.The unit was lightly soiled and had a worn eo label, but no other anomalies were observed.Unit passed spring / functional test and functioned as intended.The instructions for use testing was performed with no observed anomalies.The functional testing was performed using the same protocol it underwent at finished goods testing prior to release: the unit was found to perform as intended and fulfilled the acceptance criteria.The complaint could not be verified through failure analysis.The root cause is undetermined and was unable to be confirmed in the complaint evaluation.A review of the device history record and trending were performed as part of the evaluation.Product was received for analysis and the investigation could not confirm the complaint.The risk remains acceptable per the risk analysis.Possible root cause is "user misuse".
|
|
Search Alerts/Recalls
|