|
Continuation of d10: 800sr28 heart ring implant date: (b)(6) 2016.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 not returned for evaluation.A review of device history records was not performed as the reported event and analysis are not related to manufacturing or servicing issue.Log file analysis revealed that (b)(6) was the primary controller in use during the reported event.Log files associated with (b)(6) did not reveal any alarms within the analyze period.Of note, log files associated with (b)(6) did not cover the reported event date.As a result, the reported controller fault alarm could not be confirmed due to insufficient evidence.Log files associated with (b)(6) revealed three (3) vad disconnect alarm was then logged on (b)(6) 2025 at 14:14:53, (b)(6) 2025 at 17:58:46, (b)(6) 2025 at 17:09:34, indicating a physical disconnection of the driveline from the controller.The two (2) vad disconnect alarms in (b)(6) are additional findings, unrelated to the reported event, likely due to powering the controller without the driveline connected.The vad disconnect alarm (b)(6) 2025 is likely due to the reported controller exchange.Log file analysis associated with (b)(6) also revealed two (2) controller power up events with an associated pump start event logged on (b)(6) 2025 at 17:11:34, indicating a loss of power to the controller.Review of the event log file revealed that, prior to the power up event, the controller last had power on (b)(6) 2025.Review of the data log file revealed that the controller was not in use prior to the reported event, indicating that the controller power up event occurred during a controller exchange.Applicable risk documentation and experience with events of similar circumstances were considered; a possible root cause of the reported controller fault alarm event may be attributed, but not limited, to a faulty internal component, memory corruption, and/or the patient allowing the batteries to deplete completely.The most likely root cause of the vad disconnect alarms can be attributed to a physical disconnection of the driveline from the controller and/or the controller being powered on without the driveline connected.Based on available information, the most likely root cause of the controller power up events 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.
|