|
Model Number 9735665 |
Device Problem
Human-Device Interface Problem (2949)
|
Patient Problem
No Clinical Signs, Symptoms or Conditions (4582)
|
Event Date 12/18/2020 |
Event Type
malfunction
|
Manufacturer Narrative
|
Concomitant medical products: product id: 9735737, serial/lot#: version: (b)(4).Device evaluated by mfr: a medtronic representative went to the site to test the equipment.The hardware, software, and instruments passed the system checkout.The system was found to be fully functional.If information is provided in the future, a supplemental report will be issued.
|
|
Event Description
|
Medtronic received information regarding a navigation system that was during a cranial resection procedure.It was reported that the surgeon was having difficulty registering the patient in a tumor resection case this morning.The patient had 8 fiducials placed and 6 were recognized by the software when the exam was loaded.When registering with the fiducials he was unable to get a passing registration.Surgeon then performed a trace registration which passed but then felt inaccurate.Patient was positioned on her side.Surgeon decided to have patient rescanned.Troubleshooting was performed.Attempted to combine trace points with fiducials without improvement.Edited the 3d model to remove artifact around the chin, added anatomical touchpoints, which when used with tracing but not the fiducials brought the accuracy metric to 1.7.The surgeon still felt that he was off in the posterior direction by more than he was comfortable.The site got a ct of the patient and merged it with the mri.They were able to get an acceptable registration.Looking at the mri several of the fiducial marker where compressed in the scan and some noticeable skin movement.There was a reported delay of one and half hours.There is no known impact on patient outcome.
|
|
Manufacturer Narrative
|
H3: analysis of the software was completed by reviewing the archives.It was shown that there were 4 mri scans, two were thickness more than 2 mm and the others had missing slices and no registration data found, but provided insufficient information to determine root cause of the reported behavior.Fdc d14, fdm b01, fdr c19.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided 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.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.Any required fields that are unpopulated are blank because the information is currently unknown or unavailable.A good faith effort will be made to obtain the applicable information relevant to the report.If information is provided in the future, a supplemental report will be issued.
|
|
Search Alerts/Recalls
|
|
|