Model Number 4515-70-102 |
Device Problems
Break (1069); Unintended System Motion (1430); Intermittent Loss of Power (4016)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 02/08/2022 |
Event Type
malfunction
|
Event Description
|
It was reported that prior to a procedure, it was observed that the saw handpiece device, while being used with a base station device and satellite station device stuttered back and forth without the saw trigger being pressed.
It was reported that this occurred at the first cut (distal femur cut) before the trigger was pulled for any part of the procedure.
It was reported that the oscillating behavior of the saw was very slow, operating at about 2 oscillations per sec and continued for 5-10 seconds.
During that time, the surgeon held the saw still with one hand and tested the trigger forward with the other, which did not affect the behavior.
As a troubleshooting measure, the surgeon again tried pulling the trigger rapidly.
On the 3rd pull, the saw was fully engaged and ran at full power for a brief time.
However, it stopped running briefly, and the surgeon repeated the troubleshooting step of rapidly pulling the trigger.
The saw ran for a short time and stopped again.
The surgeon repeated the rapid trigger pulling action, and the saw started running for a brief time and again stopped running.
On the third iteration of this behavior, the saw started at full power and ran for the remainder of the case.
However, it appeared to stop running very briefly throughout the case.
There seemed to be no apparent reason for this behavior because the surgeon's saw technique gave no indication he was causing the issue, and the camera could easily see the saw.
For example, the surgeon moved the saw with constant force in short intervals giving the saw time to cut bone effectively.
The surgeon also moved the saw straight in and out, allowing it to use the maximum cutting surface and not allowing the blade's sides to be bound by an uncut surface.
No delays to the case were reported due to the event.
It was reported that all cuts were made successfully with good outcomes.
There was patient involvement.
There were no injuries, medical intervention or prolonged hospitalization.
All available information has been disclosed.
If additional information should become available, a supplemental medwatch will be submitted accordingly.
|
|
Manufacturer Narrative
|
If information is obtained that was not available for the initial report, a follow-up report will be filed as appropriate.
Device was used for treatment, not diagnosis.
If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
Additional narrative: as of this date, the device has not been returned for evaluation; therefore, the reported condition cannot be confirmed and/or duplicated.
Concomitant medical devices and therapy dates, satellite station device and base station device, (b)(4) 2022.
Udi :(b)(4).
|
|
Manufacturer Narrative
|
If information is obtained that was not available for the initial report, a follow-up report will be filed as appropriate.
Device was used for treatment, not diagnosis.
If information is obtained that was not available for the initial medwatch, a follow-up medwatch will be filed as appropriate.
Additional narrative: as of this date, the device has not been returned for evaluation; therefore, the reported condition cannot be confirmed and/or duplicated.
Concomitant medical devices and therapy dates, satellite station device and base station device, (b)(4) 2022.
Udi :(b)(4).
|
|
Event Description
|
It was reported that prior to a procedure, it was observed that the saw handpiece device, while being used with a base station device and satellite station device stuttered back and forth without the saw trigger being pressed.
It was reported that this occurred at the first cut (distal femur cut) before the trigger was pulled for any part of the procedure.
It was reported that the oscillating behavior of the saw was very slow, operating at about 2 oscillations per sec and continued for 5-10 seconds.
During that time, the surgeon held the saw still with one hand and tested the trigger forward with the other, which did not affect the behavior.
As a troubleshooting measure, the surgeon again tried pulling the trigger rapidly.
On the 3rd pull, the saw was fully engaged and ran at full power for a brief time.
However, it stopped running briefly, and the surgeon repeated the troubleshooting step of rapidly pulling the trigger.
The saw ran for a short time and stopped again.
The surgeon repeated the rapid trigger pulling action, and the saw started running for a brief time and again stopped running.
On the third iteration of this behavior, the saw started at full power and ran for the remainder of the case.
However, it appeared to stop running very briefly throughout the case.
There seemed to be no apparent reason for this behavior because the surgeon's saw technique gave no indication he was causing the issue, and the camera could easily see the saw.
For example, the surgeon moved the saw with constant force in short intervals giving the saw time to cut bone effectively.
The surgeon also moved the saw straight in and out, allowing it to use the maximum cutting surface and not allowing the blade's sides to be bound by an uncut surface.
No delays to the case were reported due to the event.
It was reported that all cuts were made successfully with good outcomes.
There was patient involvement.
There were no injuries, medical intervention or prolonged hospitalization.
All available information has been disclosed.
If additional information should become available, a supplemental medwatch will be submitted accordingly.
|
|
Search Alerts/Recalls
|
|