| Model Number |
106531 |
| Medical Device Problem Codes |
Improper or Incorrect Procedure or Method (2017); Complete Loss of Power (4015)
|
| Health Effect - Clinical Codes |
No Consequences Or Impact To Patient (2199); No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
12/16/2020
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
No further information was provided.A supplemental report will be submitted when the manufacturer's investigation is completed.
|
| |
|
Event or Problem Description
|
|
Reference mfr report number: 2916596-2020-06400.It was reported that the patient was sleeping on batteries and the batteries expired.At that point, the emergency backup battery engaged, but it too eventually expired.The patient's pump was off for an unknown amount of time before the patient woke up, walked to the mobile power unit (mpu), connected herself back to power, and the pump restarted.The patient denies hearing any alarms.Fortunately, the patient recovered left ventricular function with left ventricular ejection fraction (lvef) at 55% with aortic valve (av) opening, but has very poor right ventricular (rv) function.The patient thinks this happened on saturday night/sunday am, but it is difficult to tell by interrogation because the date was reset when the controller and pump lost power.The patient was educated on never sleeping on batteries and to always use the mpu.The vad coordinator demonstrated the alarm difference between being connected to battery power verses mpu as the mpu amplifies the alarms.The patient also understands to change to batteries in the mpu to ensure alarm function and will do this when she gets home.The patient denied any symptoms and her international normalized ratio (inr) has been therapeutic for a few months.Technical services (ts) reviewed the event log data and noted controller clock corrupt events and was unable to see when the battery depletion actually took place.Ts explained that the events described by the vad coordinator appear accurate, as the main reason for the clock to default to 1/1/2000 is total depletion of power resulting in the pump stopping.
|
| |
|
Event or Problem Description
|
|
It was reported that the patient was doing fine and was not hospitalized.No changes were made to the patient's medical therapy.The patient had left ventricular recovery, but right heart function was reduced.This precludes the patient from lvad explant.
|
| |
|
Additional Manufacturer Narrative
|
|
Manufacturer's investigation conclusion: the reported event of the controller failing to alarm was not confirmed.A review of the submitted log file spanned approximately 3 days ((b)(6) 2000 per time stamp).The controller clock was not set throughout the entire log file.The low flow alarm was active on (b)(6) 2000 at 19:57 and (b)(6) 2000 at 03:10 due to flow falling below the 2.5 lpm threshold.This low flow incident is covered under the pump investigation under manufacturer report number 2916596-2020-06400.There were also routine low power advisory alarms that the patient reacted to by switching to new batteries indicating that the controller is alarming appropriately.No other notable alarms were active in the log file.A review of the periodic log file spanned approximately 11 days ((b)(6) 2020 and (b)(6) 2000 per time stamp).The controller lost power on (b)(6) 20200 at 04:10 due to a full battery depletion.The patient was without power for several hours and when the controller turned on again, the clock was not set.This incident is covered under manufacturer report number 2916596-2020-06400.No other notable alarms were active in the log file.The 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.Heartmate 3 instructions for use section b-¿technical specifications¿ explains that the correct audio level specification for controller advisory and hazard alarms is ~85 db.Device history records were reviewed and showed no deviations from manufacturing or qa specifications.A root cause for the reported event cannot be conclusively determined through this analysis.No further information was provided.The manufacturer is closing the file on this event.
|
| |
|
Search Alerts/Recalls
|