|
Investigation of this event is pending and a supplemental report will be sent upon its completion.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.
|
|
A supplemental report is being submitted for additional information.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.
|
|
A supplemental report is being submitted for device evaluation.Product event summary: the controller ((b)(6)) was not returned for evaluation.Review of the device history record confirmed that the associated device met all requirements for release.Log file analysis associated with (b)(6) revealed two (2) controller fault alarms logged on (b)(6) 2025 at 10:48:19 and at 13:06:34, indicating an issue with the internal battery.In addition, log files revealed that the controller had been in use for more than two (2) years.Additionally, log file analysis associated with (b)(6) revealed a controller power-up event, with an associated pump start event, logged on (b)(6) 2025 at 14:19:53.Analysis of the event log file revealed that the date, pump id, and alarm limits were being set prior to the controller power up event.Additionally, review of the data log file revealed that the controller was not in use prior to the controller power up event; the first data point was logged on (b)(6) 2025 at 14:20:29, indicating that the controller power up likely occurred during the initial programming of the controller and/or a controller exchange.Review of the alarm file revealed one (1) vad disconnect alarm logged on (b)(6) 2025 at 14:20:01, indicating that the controller was powered on without the driveline connected.The alarm cleared at 14:20:22, indicating that the driveline was connected.As a result, the reported event was confirmed.Based on the available information, the most likely root cause of the reported loss of power event can be attributed to the initial programming of the controller and/or the reported controller exchange.Applicable risk documentation, experience with events of similar circumstances, and the available information were considered; possible root causes of the reported controller fault alarm event may be attributed, but not limited, to a reduced charge capacity of the internal battery and/or a faulty internal battery charger integrated circuit.The most likely root cause of the vad disconnect alarm can be attributed to the controller being powered on without the driveline connected, likely during the reported controller exchange.Investigation of this event is completed and the file will be closed.If new information is received, the file will be re-opened and a supplemental will be submitted.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.
|