|
Continuation of d10: 6935m62 lead implanted (b)(6) 2019, 5076-52 lead implanted (b)(6) 2019, 383069 lead implanted (b)(6) 2019, dtpa2d4 icd implanted (b)(6) 2024.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 analysis and investigation completion.Product event summary: one (1) controller (b)(6) was not returned for evaluation as it was discarded by the customer.A review of the manufacturing documentation was not performed as the reported event and analysis are not related to a manufacturing or servicing issue.Log file analysis associated with con401843 revealed one (1) controller fault alarm logged on 11/apr/2025 at 22:21:27, as well as multiple event exceptions logged on 11/apr/2025, 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.Log file analysis also revealed one (1) vad disconnect alarm logged on 12/apr/2025 at 05:19:31, indicating a physical disconnection of the driveline from the controller, likely due to the reported controller exchange.Log file analysis associated with (b)(6) revealed nineteen (19) vad disconnect alarms logged on 12/apr/2025 between 03:49:31 and 05:20:14, indicating that the controller was powered up without the driveline connected, likely due to troubleshooting during a controller exchange.In addition, log file analysis associated with (b)(6) revealed a controller power up event with an associated pump start event logged on 12/apr/2025 at 05:20:10.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 indicating that the controller power up likely occurred during the initial programming of the controller during the reported controller exchange.As a result, the reported event was confirmed.Applicable risk documentation, experience with events of similar circumstances, and the available information were considered; possible root causes of the reported controller fault alarm may be attributed, but not limited, to a reduced charge capacity of the internal battery and/or a faulty internal battery charger integrated circuit.Based on the available information, the most likely root cause of the controller power up event can be attributed to 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.
|