|
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: the battery (bat(b)(6) was 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.No performance allegations were made against bat(b)(6); therefore, the purpose of this investigation is solely to address the finding identified during analysis of the controller log files.Log file analysis revealed that the controller in use during the reported event, (b)(6), contained a software with a feature that records whether a power source experienced a communication error or a disconnection within each 15-minute interval.Analysis of the alarm log file revealed one (1) critical battery alarm due to a communication error on (b)(6) 2024 at 00:39:51 involving bat(b)(6).As a result, the finding was confirmed.The battery had been lubricated prior to release.The most likely root cause of the critical battery alarm can be attributed to a communication error between the controller and the battery.Possible root causes of the communication error can be attributed to momentary disconnections on the communication pins of the controller, the controller not receiving responses from the battery, and/or due to the packet error checking method detecting bit errors.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.
|