It was reported by the mcs coordinator that a patient called in and reported a "vad stop, change controller" alarm.He reported hearing a battery connect beep sporadically for about a week.At those times, there was nothing on the screen.When the patient heard the beep this time, the patient was instructed by the controller to change his controller.The patient changed the controller without incident.
|
It was reported that the patient reported a "vad stop, change controller" alarm and reported hearing 'battery connect' beeps sporadically.At those times there was nothing on the screen. the 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 controller revealed that the device passed visual inspection and functional testing.The controller did not alarm a vad disconnect alarm when a driveline was connected to the controller.Additionally, the controller was able to properly alarm a vad disconnect alarm when the driveline was physically disconnected from the controller.The controller did not alarm sporadic beeps during testing; the controller was able to accept uninterrupted power from power sources connected to the controller.Log files analysis revealed that on (b)(6) 2017 at 11:52:53 a critical battery alarm was logged for bat219753.Shortly thereafter, at 11:53:29 the controller logged a vad disconnect alarm due to a physical disconnection of the driveline from the controller.The data logs indicate that at 11:39:52 hours, moments before the "critical battery" alarm, bat219753 was connected to ps1 with 94% rsoc and bat208209 was connected to ps2 with 96% rsoc.The battery connected to ps1 was driving the controller.This one was the last data entry. at 11:52:53, during the critical battery alarm, bat219753 went from 94% rsoc to 0%.These are events are most often related to communication errors, an internal investigation has being open.Analysis of the data files also revealed power switching events.These events may be due to communication errors and/or momentary disconnections between the controller and batteries.Momentary disconnections will result in an audible tone, or beep.Momentary disconnections are being addressed on an internal investigation.The alarm files did not reveal a controller fault/failed alarm that would of instructed the patient to exchange the controller.The most likely root cause of the reported vad stopped alarm can be attributed to a physical disconnection of the driveline from the controller.A possible root cause of the reported beeps can be attributed to momentary disconnections between the controller and batteries.Heartware will submit a supplemental report when new facts arises which materially alters information submitted in a previous mdr report.
|