| Model Number |
9733858 |
| Medical Device Problem Codes |
Application Program Problem (2880); Application Program Freezes or Fails to Launch (4031)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
08/19/2024
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Continuation of d10: section d information references the main component of the system.Other relevant device(s) are: product id: 9735225r, serial/lot #: -, ubd: , udi#: h6: multiple annex a codes were coded for this event.A1102 was coded for the no signal message.A110201 was coded for the system not booting.H3, h6: no products were received by the manufacturer for analysis.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Event or Problem Description
|
|
Medtronic received information regarding a navigation system being used outside of a procedure.It was reported that the customer reported that the system would not boot and there was a message in the screen indicating that it does not have video signal.The probable cause was a cpu failure.There was no patient involvement.
|
| |
|
Additional Manufacturer Narrative
|
|
H3: a medtronic representative went to the site to test the equipment.Testing revealed that the central processing unit (cpu) would not boot up.The cpu was then replaced.The navigation system then passed the system checkout and was found to be fully functional.H6: fdm b01, fdr c13, fdc d02 are applicable to the system checkout.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Additional Manufacturer Narrative
|
|
Section e updated.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Additional Manufacturer Narrative
|
|
H3: the computer (product number: 9735225r, lot number: 1886989) was returned to the manufacturer for analysis.Analysis found that the reported issue was confirmed.The analyst had to use the reset switch initially to start the computer.The basic input/output system (bios) was set to(b)(6) 2007.The computer's complementary metal oxide semiconductor (cmos) battery was dead.Analysis found that the reported event was related to a computer component issue.H6: fdm b01, fdr c02, and fdc d02 are applicable to the hardware analysis.Medtronic submits this report to comply with fda regulations 21 cfr parts 4 and 803.Medtronic has made reasonable efforts to provide as much relevant information as is available to the company as of the submission date of this report.This report does not constitute an admission or a conclusion by fda, medtronic, or its employees that the device, medtronic, or its employee caused or contributed to the event described in the report.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.Medtronic will submit a supplemental report if additional relevant information becomes known.
|
| |
|
Search Alerts/Recalls
|