Alarm history and patient data file review found four new alarms recorded in the freedom driver's alarm history indicating the driver was power cycled multiple times prior to return to syncardia.One of the fault codes observed occurs as a result of secondary motor engagement.Visual inspection of internal components found damage including a fractured bottom right housing boss and missing insert, which was found on the corresponding bolt, the secondary motor's cam follower was out of the bottom dead center position, and a small scuff mark on the main power control board assembly, all of which indicate impact shock.Visual inspection of external components revealed no abnormalities.The device passed all incoming functional testing.Additional/subsequent testing was performed on secondary system.The driver passed all functional testing.Failure investigation for this complaint confirmed the reported fault alarm.The complaint was not replicated via functional/observational testing; however, the fault alarm was able to be duplicated by forcing the secondary motor to engage during additional testing.The driver is designed to alarm when operating on the secondary motor and therefore functioned as intended.The root cause of the fault alarm could not be conclusively determined.It is likely an impact to the driver caused the secondary motor to unintentionally engage.While the freedom driver is designed to switch to operation on the secondary motor by design to mitigate risk to patient health and safety when a functional issue occurs, the driver is not intended to operate on the secondary motor and therefore alarms to alert the patient and caregivers that a driver switch is required.(b)(4).Follow-up report 1.
|