|
Model Number 999.893 |
Device Problem
Human-Device Interface Problem (2949)
|
Patient Problem
Spinal Column Injury (2081)
|
Event Date 01/03/2022 |
Event Type
malfunction
|
Event Description
|
Mis tlif l4-5 was planned with non-globus implants (k2m), pre-op workflow.Drb was placed on left psis and surveillance marker was fixed on right psis.Everything was going smooth and fluoro merge was also good.Surgeon did not use high speed burr or drill and placed the screws in following sequence: 1.L4-r with mis awl+ kwire + mis screw.2.L5-r with same workflow.After placing l5-r screw, system gave warning "possible shift in drf" but accuracy was ok and we decided to proceed for left side screws.3.L4-l with same workflow.4.L5-l with mis awl + kwire (no screw).Fluoro shot was taken to verify the screws and found that l5-r was placed inferiorly while it was in the right position in planning.Other two screws and k-wire were placed perfectly as per the plan.After getting surveillance marker warning message left side screws were placed perfectly so it means drb position was not changed and the accuracy was good.Finally l5-r was repositioned by free hand.
|
|
Manufacturer Narrative
|
This report is being resubmitted for an incident that occurred earlier.Investigation revealed that there was no system malfunction.Engineering evaluations revealed that there was no system malfunction.Investigation of the case logs showed that the root cause is likely due to user technique; however, a definitive cause could not be determined due to the use of a competitive implant.The starting point of the l5-r screw was planned in a potential high-skive area.Additional pedicle preparation would have been needed to help place the screw due to the risk of skiving upon entrance.Additionally, during the bone work for l5-r, the software detected excessive forces on the load cell during bone work.This is the result of skiving forces detected while a tool is inserted in the end effector.Software correctly detected the warning and alerted the user.The cause of the reported issue was traced to user technique.
|
|
Search Alerts/Recalls
|
|
|