|
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 device evaluation.Product event summary: the controller (b)(6) was returned for evaluation.A review of the device history record was not performed as the reported event and analysis is not related to a manufacturing or servicing issue.Various analyses were conducted and reviewed in order to evaluate the performance of the device in relation to the reported event.External visual inspection revealed contamination inside of both power ports, serial port, and pump connectors.The observed contamination is an additional finding not related to the reported event, likely due to handling of the device.Functional testing revealed that the "no power" alarm only sounded briefly when both power sources were disconnected from the controller and a controller fault alarm was triggered during testing.Internal inspection revealed that the internal nickel-metal hydride (nimh) battery, which powers the no power alarm, was slightly swollen.After the internal battery was replaced, the controller performed as expected.Log file analysis revealed one (1) controller fault alarm logged on (b)(6) 2026 at 19:05:08, indicating an issue with the internal battery.In addition, log files revealed that the controller was in use for more than two (2) years.One (1) vad disconnect alarm was logged on (b)(6) 2026 at 22:04:08, indicating a physical disconnection of the driveline, likely due to 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 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.Capa: pr00492825 investigated internal battery issues with controller 2.0.Even though this capa is closed, (b)(6) falls within the bounds of this capa.Based on the available information, a possible root cause of the reported vad disconnect can be attributed to a physical disconnection of the driveline from the controller, likely due 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.
|