|
Additional product: d1: heartware ventricular assist system ¿controller 2.0 d4: model #: 1420/ catalog #:1420/ expiration date:31-mar-2024 /serial or lot#: (b)(6) d9: no h3: no h4: mfg date: 14-mar-2023 h5: no h6: the codes present in section h6 correspond to components/products that comprise the reported event.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 ventricular assist device (vad) ((b)(6)) and controller ((b)(6)) were not returned for evaluation.A review of the device history record was not performed as the reported event and analysis are not related to a manufacturing or servicing issue.The reported suction event was confirmed via log file analysis, which revealed three (3) suction alarms logged since (b)(6) 2025.Based on the available information, the device may have caused or contributed to the reported suction event.Based on the risk documentation, possible causes of the reported suction event may be attributed to multiple factors including but not limited to thrombus at the inflow cannula, poor vad filling, and/or inappropriate vad rotational speed.Log file analysis also revealed a controller power-up event, with an associated motor start event, logged on (b)(6) 2025 at 10:20:20, indicating a loss of power to the controller.The data point recorded prior to the loss of power revealed that a power adapter was connected to power port one (1) and (b)(6) was connected to power port two (2) with (b)(4) relative state of charge (rsoc).The data point recorded after the loss of power revealed that no power source was connected to power port one (1) and (b)(6) was connected to power port two (2).No anomalies were recorded leading up to the loss of power.The controller was without power for seven (7) seconds.As a result, the reported loss of power event was confirmed.The most likely root cause of the loss of power can be attributed to the reported disconnection of both power sources, as described in the event details.Capa pr00551638 investigated controller losses of power.Even though this capa is now closed, (b)(6) falls in scope of this capa.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.
|