|
|
| Model Number |
COCKPIT |
| Medical Device Problem Code |
Application Program Problem (2880)
|
| Health Effect - Clinical Code |
No Clinical Signs, Symptoms or Conditions (4582)
|
| Date of Event |
04/24/2025
|
|
Type of Reportable Event
|
Malfunction
|
|
Additional Manufacturer Narrative
|
|
A.1.-a.5.Patient information was not provided.H11: livanova deutschland manufactures the essenz console.The incident occurred in amsterdam, netherlands.The cockpit log files have been requested and analyzed.The analysis confirmed the problem.The backup control unit maintains control during the reboot.In this type of event, the cockpit screen may reboot showing the livanova logo and once the cockpit user interface is restored, the ¿last case¿ button enables users to retrieve all prior settings and proceed without any data loss.During the reboot, the heart-lung machine's critical functions, including pumps, alarms, sensors, and safety systems, continued to perform as designed.The gas blender may return to the original settings selected by the user and may require the operator to adjust flows if changed during operation.If any additional information pertinent to the reported event is received, it will be provided in a supplemental report.
|
| |
|
Event or Problem Description
|
|
Livanova deutschland received a report that, at the end of the case, the cockpit screen of an essenz console was frozen.It was tried to lower the arterial flow, but it was not visible on the screen.Then, the flow was lowered through the backup control unit, which was also not visible on the cockpit screen.After sixty (60) seconds suddenly the cockpit rebooted by itself and functioned again.Then the lowered flow was visible again on the cockpit (the flow was apparently lowered, but that was not visible on the cockpit where the value was still the same until it rebooted).There was no patient injury.
|
| |
|
Additional Manufacturer Narrative
|
|
Through follow-up communication, it was learned that the cockpit will be scrapped.A detailed investigation has been conducted.Results revealed that this type of event can be caused by specific high-level processes, such as the logger or window manager applications, which can trigger a segmentation fault or watchdog timeout.This leads the operating system to reset the applications to restore normal operation.Livanova initiated an improvement action in order to further decrease the already low frequency of occurrence of this type of event.The risk is in the acceptable region.No specific action was currently deemed necessary.Livanova will keep monitoring the market.
|
| |
|
Search Alerts/Recalls
|
|
|