It was reported that the controller exhibited an unexpected power loss, the light emitting diodes would not illuminate when connected to power sources, exhibited a date format issue, and data was unable to transfer.The controller was exchanged.No patient complications have been reported as a result of this event.
|
Product event summary: one (1) controller was returned for evaluation.Various analyses were conducted and reviewed in order to evaluate the performance of the device in relation to the reported event.Failure analysis of the returned controller revealed that the device passed visual inspection.Functional testing revealed that the front panel battery capacity indicators did not illuminate.As a result, the reported "leds not illuminating" event was confirmed.Functional testing also revealed that the controller was unable to communicate with external batteries on both power ports, resulting in critical battery alarms.Internal inspection of the controller revealed a damaged diode on the communication line pertaining to power port 2.Additionally, it was observed that the integrated circuit responsible for the communication between the controller and batteries was damaged.The damaged integrated circuit is also connected to the real time clock circuit and may have caused the date and time stamp to remain frozen.As a result, the controller was unable to determine the capacity of the battery, causing the controller to trigger a critical battery alarm.Additionally, internal inspection of the controller revealed a crack on a standoff post within the controller housing.The observed crack on the standoff post is not related to the reported event.Based on an investigation, the root cause of the crack was determined to be due to mineral oil applied to the controller¿s internal main gasket and/or to the silicone adhesive applied around the controller¿s internal battery coming into contact with the standoff post.The mineral oil and/or silicone adhesive contributed to environmental stress cracking.Log files were able to be properly downloaded from the controller; as a result, the reported data transfer error event could not be confirmed.Log file analysis revealed a controller power up event on 25/jul/2019 at 17:39:44.The data point prior to the loss of power revealed that a battery was connected to power port one (1) with 51% relative state of charge (rsoc), and a battery was connected to power port two (2) with 99% rsoc.The data point recorded after the loss of power revealed that a controller power adapter was connected to power port 1, and no power source was connected to power port 2.The controller was without power for 16 seconds.Log file analysis also revealed multiple critical battery alarms logged with an incorrect date stamp and no battery capacity, id, or cycle count.As a result, the reported power loss event, controller display error and data format error events were confirmed.The most likely root cause of the controller display error can be attributed to communication errors between the controller and batteries.The most likely root cause of the incorrect date format error can be attributed to a damaged integrated circuit.A possible root cause for the damaged diode and integrated circuit on the communication line can be attributed to a misalignment of the cac adapter on power port 2 of the controller, causing a voltage spike on the communication pin of the connector.A possible root cause of the loss of power can be attributed to a disconnection of both power sources and/or to an intermittent disconnection on one or both power sources.Internal evaluation was initiated to capture events involving the controller losing power.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided 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.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.
|
A supplemental report is being submitted as remedial action and correction number information was received.If new information is received, the file will be re-opened and a supplemental will be submitted.Medtronic is submitting this report to comply with fda reporting regulations under 21 cfr parts 4 and 803.This report is based upon information obtained by medtronic, which the company may not have been able to fully investigate or verify prior to the date the report was required by the fda.Medtronic has made reasonable efforts to obtain more complete information and has provided 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.In particular, this report does not constitute an admission by anyone that the product described in this report has any ¿defects¿ or has ¿malfunctioned¿.These words are included in the fda 3500a form and are fixed items for selection created by the fda to categorize the type of event solely for the purpose of regulatory reporting.Medtronic objects to the use of these words and others like them because of the lack of definition and the connotations implied by these terms.This statement should be included with any information or report disclosed to the public under the freedom of information act.If information is provided in the future, a supplemental report will be issued.
|