MEDTRONIC NAVIGATION, INC. (LOUISVILLE) STEALTHSTATION S7 SYSTEM; NEUROLOGICAL STEREOTAXIC INSTRUMENT
|
Back to Search Results |
|
Model Number S7 |
Device Problems
Thermal Decomposition of Device (1071); Device Displays Incorrect Message (2591)
|
Patient Problem
No Consequences Or Impact To Patient (2199)
|
Event Date 08/04/2016 |
Event Type
malfunction
|
Manufacturer Narrative
|
On 08/05/2016 a medtronic representative performed a navigation system check-out, all areas passed.System performed as intended.Return requested.Replacement axiem portable shipped to site 08/04/2016.Medtronic investigation of returned suspect axiem portable finds that when tested on test bench, and after running and getting to operating temperature, amp board c has a temp fault.The axiem fault light comes on and in the software, axiem box is red and shows red status.The axiem is still able to track in this state.Confirmed electrical failure.System fault code.On 08/26/2016 a medtronic representative, following-up at the site, reported the axiem box was not warm to the touch.The issue was identified prior to the start of the procedure while we setting-up the room.The yellow fault lights were on the box and the 'emitter details' tab had the red message, noting: emitter box overheat.No further issues have been reported.
|
|
Event Description
|
A medtronic representative reported that, while in a procedure, the site's navigation system axiem box was overheating, showing red under emitter details, and was unable to track.A second axiem box was brought in to allow the surgeon to proceed.No further details regarding this issue, or specifically when it occurred, were provided.The surgeon completed the procedure with the use of the navigation system.There was no delay of therapy.There was no patient present when this issue was identified.
|
|
Manufacturer Narrative
|
A medtronic representative, following up with the site, reported that the procedure was a cranial and orbital reconstruction.The hardware investigation found that the reported event was related to a hardware issue.This issue was documented in a medtronic navigation hardware anomaly tracking database.
|
|
Search Alerts/Recalls
|
|
|