Fresenius Kabi Agilia

Software Freeze, Reboot Loop, or Startup Failure

On this page

Asset Type

Infusion Pump

Manufacturer

Fresenius Kabi

Model

Agilia

What This Guide Helps With

Troubleshooting a frozen display, repeated restarting, incomplete startup, failed self-test, or unresponsive pump caused by power, accessory, configuration, or software issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot a frozen, restarting, or unreliable Agilia pump while it is actively delivering medication to a patient.

Expected outcome: The patient’s therapy continues safely without relying on a pump that may stop, restart, or change operating state unexpectedly.

If the pump cannot complete its startup self-test or remain operational, it must not stay in clinical use.

2. Clarify the Reported Failure

Determine whether the pump:

Record any displayed message, code, unusual LED sequence, alarm pattern, or point in the startup process where the failure occurs.

Expected outcome: The exact failure mode is identified before components or power sources are changed.

3. Inspect for Damage, Contamination, or Heat

Disconnect the pump from clinical use and inspect the exterior for:

Do not energize a pump that shows liquid intrusion, burning odor, smoke, excessive heat, or significant impact damage.

Expected outcome: No visible condition is found that would make further powered testing unsafe.

If damage or contamination is present, stop and send the pump for bench evaluation.

4. Verify the AC Power Source

Connect the pump directly to a known-good hospital-grade outlet using an approved, undamaged power cord.

Agilia instructions specify checking that the power indicator illuminates when the pump is connected to AC power.

Expected outcome: The pump receives stable external power and begins its normal startup sequence.

If the pump starts normally, the original outlet, power cord, rack connection, or power-distribution accessory was likely responsible. Replace or correct the external cause and stop troubleshooting.

5. Test the Pump Outside the Agilia Link Rack

If the pump was installed in an Agilia Link rack or docking system:

Inspect the rack position and pump interface for contamination, damaged contacts, looseness, or misalignment.

Expected outcome: The pump starts normally when isolated from the rack.

If it does, inspect the rack, power-distribution position, and associated connections rather than assuming the pump has failed.

6. Disconnect Nonessential External Accessories

Remove approved nonessential external connections, including:

Do not disconnect or manipulate accessories while the pump is connected to a patient.

Restart the pump using only direct AC power.

Expected outcome: The pump completes startup without an accessory causing a communication conflict, electrical load, or physical connection problem.

If startup succeeds, reconnect accessories individually to identify the external source of the failure.

7. Perform One Controlled Power Cycle

With the pump removed from patient use:

Do not repeatedly cycle power to force the pump through a persistent technical error.

During startup, the pump performs an automatic functional self-test, and its indicator lights should activate as part of the power-on sequence.

Expected outcome: The pump completes its self-test and reaches the normal operating screen without restarting or freezing.

If the pump starts normally, continue with operational verification before returning it to service.

8. Observe the Startup Self-Test

Watch for:

Do not bypass, ignore, or repeatedly acknowledge a persistent technical alarm.

Fresenius Kabi guidance states that when alarms persist after the pump is powered on again, the device should not be used on a patient and qualified biomedical personnel or the manufacturer should be contacted.

Expected outcome: The pump completes startup without technical alarms or abnormal behavior.

9. Evaluate AC and Battery Behavior

After the pump starts successfully on verified AC power:

The pump can operate from its internal battery, but Fresenius Kabi recommends regular connection to AC power to maintain battery charge.

Expected outcome: The pump transitions between AC and battery operation without rebooting.

If it operates normally on AC but restarts or shuts down on battery, suspect a depleted, deteriorated, disconnected, or otherwise unreliable battery system. Remove the pump from service for battery evaluation.

10. Check for a Stuck or Intermittent Keypad Control

Inspect the power key and remaining keypad controls for:

Do not pry, remove, or disassemble the keypad during floor troubleshooting.

Expected outcome: All controls release normally and respond consistently.

A stuck power key or defective keypad may cause unintended shutdowns, restarts, or startup interruptions. Remove the pump from service if keypad operation is unreliable.

11. Verify Whether the Failure Is Configuration-Specific

Determine whether the pump freezes only when:

Do not alter the approved drug library, software, network configuration, or clinical profile merely to clear the symptom.

Expected outcome: The technician determines whether the pump fails during basic standalone operation or only after loading a particular configuration.

If multiple pumps exhibit the same problem after a recent software, drug-library, or configuration deployment, preserve the evidence and escalate to the infusion-system administrator, IT integration team, and Fresenius Kabi.

12. Complete a Standalone Operational Check

If the pump now starts normally:

Do not use patient-connected tubing or medication for testing.

Expected outcome: The pump remains stable and completes functional testing without freezing, restarting, or generating technical alarms.

If the issue cannot be reproduced, document the original complaint and all testing performed. Follow facility policy regarding observation, extended testing, or return to service after an intermittent software complaint.

If the Problem Persists

If the Agilia continues to freeze, restart, fail its self-test, or stop during startup after external power sources, cords, racks, accessories, battery behavior, and visible controls have been evaluated, common external causes have been ruled out.

The problem may involve the internal power system, battery connection, keypad circuitry, display assembly, memory, software installation, processor electronics, or another internal component.

The device should be:

Do not attempt unapproved software installation, factory resets, configuration changes, or internal board-level repair.

Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Never troubleshoot an Agilia pump that is freezing or restarting while it remains responsible for an active infusion. Move the patient’s therapy to a verified device first. A pump that appears to recover after a reboot must still complete functional and alarm testing before clinical use.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the Fresenius Kabi Agilia pump repeatedly restarted at the startup screen and could not be programmed."

Cause

What was observed during troubleshooting.

Example:
"Pump rebooted on both verified AC power and battery power with all external accessories removed, indicating an internal hardware or software failure."

Resolution

What action was taken.

Example:
"Removed the pump from service, applied an Out of Service label, documented the displayed technical error, and forwarded the unit for bench evaluation and manufacturer-supported repair."

Helpful Details to Include (If Known)

Final Thought

Software and startup complaints require patient safety, disciplined isolation of external causes, and careful observation of the failure sequence. Stable power, accessories, battery operation, and configuration should be evaluated before internal failure is assumed. Persistent or intermittent rebooting warrants removal from service, appropriate escalation, and detailed CCR documentation.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide