A medtronic representative inspected the imaging system on-site and a software investigation was completed.On-site, the reported behavior could not be replicated after extensive testing.The system functioned normally.The software investigation also proved inconclusive.The logs for this date were examined to investigate the incident.The exact time of the incident was not given.In the logs, there were no warnings or errors that would help diagnose the incident.The drive system was manufactured by (b)(4).The imaging system does not get status reports from (b)(4)¿s drive system.The (b)(4) drive system did not provide any information to help diagnose the incident.It is not possible to determine root cause without further information.A full imaging system check-out was completed and all tests passed.Full system functionality was confirmed and the system was returned to service.No further issues reported.
|
A medtronic representative reported that during a spinal fusion procedure, the imaging system was not driving as expected.It was reported that when the drive handle was pushed down to move the system backwards, it unexpectedly moved forward and impacted the patient bed.The contact with the bed damaged the imaging system cover.The clutch was disengaged and the system was manually moved away from the bed and out of the operating room.Outside the operating room, the clutch was re-engaged and the issue recurred.At this point, the system was docked.After the system was docked, the issue could not be replicated.This issue occurred after the final confirmation spin in the case, while removing the system from the room.The patient was not impacted by this, and the delay was minimal (less than one hour).No additional details were provided.
|