|
Investigation of this event is pending and a supplemental report will be sent upon its completion. continuation of d10: additional products: d1: heartware ventricular assist system controller 2.0 d4: model #: 1420 / catalog #: 1420 / expiration date: unknown / serial or lot#: (b)(6) (c) d9: no h3: no h4: mfg date: unknown h5: no h6: the codes present in section h6 correspond to components/products that comprise the reported event.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: two (2) controllers ((b)(6)) were not returned for evaluation.A review of the manufacturing documentation was not performed as the reported event and analysis are not related to a manufacturing or a servicing issue.Log file analysis associated with con415008 revealed two (2) controller fault alarm events logged on (b)(6) 2025 at 19:38:35 and on (b)(6) 2025 at 00:08:29, 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 associated with (b)(6) revealed a controller power up event with an associated pump start event was logged on (b)(6) 2025 at 10:30:39.Various parameters, including time, patient id, and pump id were programmed on (b)(6) 2025 prior to the controller power up event, indicating the power up event occurred during the initial programming of the controller and/or a controller exchange.The alarm log file associated with (b)(6) was not available for analysis.Of note, (b)(6) was loaded with a software containing the pump start algorithm c.As a result, the reported events were confirmed.Applicable risk documentation, experience with events of similar circumstances, and the available information were considered; possible root causes of the controller fault alarms 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 associated with (b)(6) can be attributed to the initial programming of the controller and/or a controller exchange.Additional products: d1: controller d4: (b)(6).H3: yes.H6: the codes present in section h6 correspond to components/products that comprise the reported event.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.
|