|
Investigation of this event is pending and a supplemental report will be sent upon its completion.Continuation of d10: dtmb1qq icd implanted (b)(6) 2025.Additional products: d1: heartware ventricular assist system controller 2.0 d4: model #: 1420 / catalog #: 1420 / expiration date: 31-jan-2024 serial #: (b)(6); d9: no.H3: no h4: mfg date: 03-jan-2023 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.
|
|
It was reported that a review of log file data revealed a motor start event with parameters outside of the typical range.It was also reported that the ventricular assist device (vad) exhibited high power, and the patient experienced multiple pump stops due to double power disconnects.The vad coordinator reported that the patient is elderly and likely performs double power disconnects while changing power supplies, resulting in pump stops.The vad and controller remain in use.No patient complications have been reported as a result of this event.
|
|
A supplemental report is being submitted for investigation summary.Additional product: serial# (b)(6) h3: yes h6: the codes present in section h6 correspond to components/products that comprise the reported event.Product event summary: the ventricular assist device (vad) (b)(6) and the controller ((b)(6)) were not returned for evaluation.A review of the device history records was not performed as the reported event and analysis are not related to a manufacturing or servicing issue.Log file analysis revealed one (1) vad disconnect alarm logged on (b)(6) 2025 at 22:55:03, indicating a physical disconnection of the driveline from the controller.Review of the event file and available motor start report revealed two (2) motor start events recorded on (b)(6) 2025 at 09:07:34 and (b)(6) 2025 at 22:57:20, in which parameters were atypical.No anomalies were found involving (b)(6) within the analyzed period.As a result, the reported atypical motor start events and reported vad stop event was confirmed.Log file analysis revealed no controller power-up events, indicating a loss of power or double disconnection of power sources to the controller, within the analyzed period.As a result, the reported double disconnect event was not confirmed.However, the reported double disconnect event was likely refers to the vad stop event.In addition, log file analysis revealed power consumption was within normal operating range during the analyzed period.As a result, the reported high power event was not confirmed; however, the reported h igh power event likely refers to the atypical motor start event.Based on risk documentation, the most likely root cause of atypical motor start parameters may be attributed, but not limited, to outer shroud contact that creates more friction at the housing to imp eller interface during pump startup.The most likely root cause of the vad disconnect alarm, correlating the reported vad stop event, can be attributed to a physical disconnection of the driveline from the controller, as described in the reported event details.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.
|