| Model Number |
1650 |
| Medical Device Problem Code |
Battery Problem (2885)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
06/28/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
Investigation of this event is pending, and a supplemental report will be sent upon its completion.H6: the codes present in section h6 correspond to components/products that comprise the reported event.Additional products: d1: heartware ventricular assist system - battery d4: model#: 1650 / catalog#: 1650 / expiration date: 30-sept-2024 / serial#: (b)(6).D9: no h3: no h4: mfg date: 24-sept-2023 h5: no d1: heartware ventricular assist system - battery d4: model#: 1650 / catalog#: 1650 / expiration date: 30-sept-2024 / serial#: (b)(6).D9: no h3: no h4: mfg date: 06-sept-2023 h5: no d1: heartware ventricular assist system - battery d4: model#: 1650 / catalog#: 1650 / expiration date: 30-sept-2024 / serial#: (b)(6).D9: no h3: no h4: mfg date: 24-sept-2023 h5: no d1: heartware ventricular assist system - battery d4: model#: 1650 / catalog#: 1650 / expiration date: 28-aug-2023 / serial#: (b)(6).D9: no.H3: no.H4: mfg date: 31-aug-2024 h5: no.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.
|
| |
|
Event or Problem Description
|
|
It was reported that a review of log files data revealed several batteries exhibited power disconnect alarms.The batteries were removed from service.No patient complications have been reported as a result of this event.
|
| |
|
Additional Manufacturer Narrative
|
|
A supplemental report is being submitted as additional information has being received for this event and sections h ave been updated.Additional products: d1: heartware ventricular assist system ¿ battery d4: model #:1650/ catalog #:1650/ expiration date: 30-sep-2024 / serial or lot#: (b)(6) d9: no h3: no h4: mfg date: 05-sep-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.
|
| |
|
Event or Problem Description
|
|
It was further reported that during review of log files an additional battery with communication errors was noted.
|
| |
|
Additional Manufacturer Narrative
|
|
A supplemental report is being submitted for analysis and investigation completion.Product event summary: one (1) controller ((b)(6)) and six (6) batteries ((b)(6)) were not returned for evaluation.No performance allegations were made against (b)(6).A review of the manufacturing documentation was not performed as the reported event and analysis are not related to a manufacturing or servicing issue.Review of the event file associated with (b)(6) revealed a controller power up event with an associated motor start event was logged on (b)(6) 2025 at 14:16:51.Various parameters, including time, patient id, and pump id were programmed on (b)(6) 2025 prior to the controller power up event, indicating the power up event occurred during the initial programming of the controller and/or a controller exchange.Additionally, log file analysis revealed that the controller in use during the reported event ((b)(6)) contained a feature that records whether a power source experienced a communication error or a disconnection within each 15 minute interval.Analysis of the data log file revealed several instances involving (b)(6), where the batteries' relative state of charge (rsoc) value was logged between 101-201, which is indicative of a communication error.A communication error will t rigger a power disconnect alarm if the other power source is a battery with an rsoc greater than (b)(4).As a result, the reported event was confirmed.The batteries were lubricated prior to release.Possible root causes of the communication errors and resulting power disconnect alarms can be attributed to momentary disconnections on the communication pins of the controller, the controller not receiving responses from the batteries, and/or due to the packet error checking method detecting bit errors.Based on available information, the most likely root cause of the controller power up event associated with (b)(6) can be attributed to a controller exchange.Additional product: d1: heartware ventricular assist system ¿ battery d4: serial #: (b)(6) h3: yes d1: heartware ventricular assist system ¿ battery d4: serial #: (b)(6) h3: yes d1: heartware ventricular assist system ¿ battery d4: serial #: (b)(6) h3: yes d1: heartware ventricular assist system ¿ battery d4: serial #: (b)(6) h3: yes d1: heartware ventricular assist system ¿ battery d4: serial #: (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.
|
| |
|
Search Alerts/Recalls
|