It was reported that the patient was instructed to change the system controller due to battery connection alarms.Once the controller was exchanged, everything appeared to be normal until around 10:30 am when the patient had a communication fault alarm.The alarm repeated an hour later.The system controller was later unable to pull up these alarms, pulsatility index (pi) parameters, and power values.The date and time on the system controller was not set.The log files showed an internal time base controller fault that indicated that the clock used was corrupt.The system controller was exchanged again.There were no further alarms after the exchange.
|
Manufacturer's investigation conclusion: the reported event of an intermittent communication fault alarm and the pump parameters not being displayed on the controller¿s screen can be confirmed.During the evaluation of the returned system controller, serial number (b)(6), an intermittent call hospital contact/controller fault alarm accompanied by a yellow wrench symbol was reproduced.In addition to the alarm there was a compromised communication between the controller and the system monitor and the controller and the pump; however, the pump support was not affected.The log files were retrieved and the data contained in the event log file revealed that the system operated at the set speed with active controller internal fault and controller clock corrupt alarms.The alarms were associated with internal error codes (f28) timebase and (f49) clock_invalid.In addition to these alarms, there were some entries where the communication with the pump was lost (loss_of_lvad_comm) and a controller reset was captured (reset_controller).The events recorded in the periodic log file revealed that the system operated at the set speed with the controller¿s clock being corrupted.Further evaluation of the system controller isolated the problem to the printed circuit board (pcb); however, the specific root cause was not able to be identified.The company will continue to monitor and track similar events.The device history records were reviewed and the records revealed the system controller was manufactured in accordance with mfg and qa specifications.Heartmate 3 patient handbook under section 5 ¿alarms and troubleshooting¿ and heartmate 3 instructions for use, under section 7 ¿alarms and troubleshooting¿ explain all alarms and the proper actions to take if the alarms cannot be resolved.Heartmate 3 patient handbook cautions the users to call their hospital contacts if they think, for any reason, any portion of their equipment is not functioning as usual, is broken, or they are uncomfortable with the operation of the equipment.No further information was provided.The manufacturer is closing the file on this event.
|