|
### 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 investigation summary.Product event summary: one (1) controller ((b)(6)) was not returned for evaluation.Review of the manufacturing documentation confirmed that the associated device met all requirements for release.Log file analysis revealed several controller power up events without an associated motor start event were logged on (b)(6) 2026 between 14:42:39 and 15:03:27, as well as four (4) vad disconnect alarms were logged on (b)(6) 2026 at 14:42:46, 14:43:54, 14:44:44, and 15:01:52, indicating that the controller was powered on without the driveline connected.Review of the data log file revealed that the controller was not in use prior to the event date; the first data point was logged on (b)(6) 2026 at 14:45:13, indicating that the controller power up events likely occurred during the initial programming of the controller and/or a controller exchange.As a result, the reported data transfer error could not be confirmed due to insufficient evidence.Based on the available information, there is no evidence to suggest that a malfunction of the autologs report caused or contributed to the reported data transfer error event.The most likely root cause of the reported data transfer error can be attributed to insufficient data in the raw log files to generate an autologs report due to the controller being initially put to use.The most likely root cause of the vad disconnect alarms can be attributed to the controller being powered on without the driveline cable connected.Based on the available information, the most likely root cause of the observed controller power up events can be attributed to the initial programming of the controller prior to the controller being put to use.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.
|