On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting missing Wi-Fi connection, failed data transfer, server communication errors, or intermittent network connectivity caused by external configuration or coverage issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not interrupt an active infusion solely to troubleshoot a wireless or network communication problem.
- Confirm the pump is delivering the programmed therapy correctly.
- Verify that no infusion, battery, occlusion, air-in-line, or system alarm is active.
- Move the patient to another verified pump if the communication problem is accompanied by abnormal pump operation.
- Coordinate any power cycle, relocation, or configuration testing with clinical staff.
Expected outcome: Patient therapy remains safe while the communication issue is evaluated separately.
Agilia wireless communication is not required for the pump to continue infusing. Pending data may be stored and retransmitted when communication becomes available.
2. Confirm the Pump Has Wireless Capability
Inspect the device identification label and configuration to verify that the affected pump is a Wi-Fi-equipped Agilia model.
Agilia configurations may include:
- Agilia VP MC WiFi
- Agilia SP MC WiFi
- Other Agilia Connect Wi-Fi variants
Do not assume every Agilia pump contains wireless hardware.
Expected outcome: The device is confirmed to be a network-capable model assigned to the facility’s wireless system.
If the pump is not a Wi-Fi model, stop troubleshooting the network connection and correct the equipment assignment or work order description.
3. Identify the Exact Communication Failure
Record what is being reported or observed:
- Wireless icon is absent.
- Wireless icon shows no connection.
- Connection is intermittent.
- Drug-library updates are not received.
- Infusion or event data is not uploaded.
- The pump does not appear in the applicable server application.
- Communication fails only in one room or department.
- Multiple pumps are affected simultaneously.
Also record any displayed communication message or error code.
Expected outcome: The failure is narrowed to the individual pump, wireless coverage, data transfer, or server-side communication.
4. Check Whether the Problem Is Location-Specific
Move the pump, when clinically safe, to a known area with reliable Agilia wireless connectivity.
Compare its connection behavior with another known-good Agilia Wi-Fi pump in the same location.
- If both pumps fail in the same area, suspect wireless coverage, access-point, VLAN, or network infrastructure problems.
- If only the affected pump fails, continue device-level checks.
- If the affected pump connects in another area, document the original location and escalate the coverage issue to the appropriate network team.
Expected outcome: The issue is identified as either location-related or isolated to the pump.
5. Verify Normal Power and Startup
Connect the pump to a known-good AC power source and confirm:
- The pump starts normally.
- The display and controls operate correctly.
- No battery, power, or internal system error is present.
- The pump completes its normal startup sequence.
A low battery, incomplete startup, or system fault may prevent normal communication behavior.
Expected outcome: The pump is fully powered and operating without unrelated system errors.
If normal operation is restored and wireless communication returns, perform a functional check, document the result, and stop.
6. Inspect the Pump Externally
Check the pump for:
- Cracked or damaged housing
- Evidence of impact or liquid intrusion
- Missing labels or incorrect asset identification
- Unusual heat, odor, or discoloration
- Damage near the rear or upper housing
- Signs that the device was recently dropped or serviced
Do not open the housing or attempt antenna or board-level repair during floor troubleshooting.
Expected outcome: No external physical condition is found that could indicate internal communication-hardware damage.
If damage, heat, odor, or fluid intrusion is present, remove the pump from service immediately.
7. Check Wireless Status Indicators
Observe the pump’s wireless or communication indicator.
Determine whether it shows:
- Wireless disabled
- Searching for a network
- Connected with weak signal
- Connected normally
- Communication fault
- No wireless indicator at all
Allow sufficient time after startup or relocation for the pump to reconnect. Agilia wireless transactions are device-initiated and periodic, so communication may not appear instantaneous.
Expected outcome: The displayed status identifies whether the pump is failing to associate with Wi-Fi or failing to communicate after association.
8. Perform a Controlled Restart
When the pump is not connected to a patient and clinical use has ended:
- Power the pump off normally.
- Wait briefly for the shutdown to complete.
- Connect it to AC power.
- Restart the pump.
- Observe the wireless indicator and any communication messages.
Do not repeatedly power-cycle a pump that displays a persistent system error or enters a restart loop.
Expected outcome: A temporary software or network-association problem clears and communication returns.
If communication is restored, confirm that the device appears in the appropriate management application before returning it to service.
9. Compare With a Known-Good Pump
Place a known-good Agilia Wi-Fi pump beside the affected device and compare:
- Wireless indicator behavior
- Time required to connect
- Network availability
- Server visibility
- Drug-library or data-transfer status
Use pumps assigned to the same facility, profile, and network environment whenever possible.
Expected outcome: The comparison confirms whether the problem follows the pump or affects the surrounding network.
If both devices fail, escalate the network or server issue rather than replacing parts in the pump.
10. Confirm Device Assignment and Network Enrollment
Using approved Clinical Engineering or system-management resources, verify that:
- The pump’s serial number and asset record are correct.
- The wireless-capable device is enrolled in the proper system.
- The pump is assigned to the correct facility or department.
- The device has not been retired, replaced, or duplicated in the management database.
- Required network credentials or certificates have not expired.
- The pump is assigned to the intended wireless configuration.
Agilia Wi-Fi models may use IEEE 802.11 wireless networking with TCP/IP, IPv4, DHCP, and supported enterprise or pre-shared-key security configurations.
Do not change network credentials or security settings without authorization and approved configuration tools.
Expected outcome: Administrative records and network enrollment match the physical device.
11. Check for a Broader Network or Server Problem
Determine whether:
- Multiple Agilia pumps are offline.
- A specific nursing unit is affected.
- Recent wireless, firewall, DHCP, VLAN, or access-point changes occurred.
- The Agilia management or software server is unavailable.
- Other connected medical devices are also experiencing communication problems.
- Scheduled maintenance or an outage is active.
Coordinate with the facility’s network, cybersecurity, pharmacy informatics, or infusion-system administrator as appropriate.
Expected outcome: A system-wide infrastructure issue is identified or ruled out before the pump is sent for repair.
12. Verify Communication After Recovery
When the connection returns, confirm the expected function rather than relying only on the wireless icon.
Verify, as applicable:
- The pump appears online in the management application.
- Device identification is correct.
- The current configuration or drug-library version is displayed.
- Pending data transfers successfully.
- No communication error returns during observation.
- The pump continues to perform its primary infusion functions normally.
Do not simulate clinical documentation or transmit patient-associated data unless the approved test environment and procedure permit it.
Expected outcome: Communication is stable and the pump is correctly recognized by the connected system.
If the issue is resolved, complete the required operational inspection, document the repair, and return the pump to service according to facility policy.
If the Problem Persists
If wireless communication remains unavailable after power, location, coverage, device assignment, server availability, and network conditions have been checked, common external causes have been ruled out.
The problem may involve the pump’s internal wireless hardware, stored configuration, security credentials, software, or communication circuitry.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or authorized repair
- Escalated to the infusion-system administrator, network team, or Fresenius Kabi technical support when appropriate
Do not open the housing, replace communication components, or alter protected network settings without the approved service documentation, training, and authorization.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
A network failure does not automatically mean the Agilia pump has stopped infusing. Confirm therapy and local pump alarms first. Never delay medication delivery solely to restore wireless communication.
Do not troubleshoot the pump while it is being used on an active patient. Move the patient to a verified backup device first when troubleshooting could affect therapy, and maintain therapy continuity throughout the process.
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 showed no wireless connection and was not appearing in the infusion-management system."
Cause
What was observed during troubleshooting.
Example:
"The pump connected normally in another department, while a known-good pump also failed in the original room, indicating a location-specific wireless network issue."
Resolution
What action was taken.
Example:
"Verified normal infusion operation, reported the affected location to the network team, and returned the pump to service after stable communication was confirmed in a known-good coverage area."
Helpful Details to Include (If Known)
- Exact Agilia model and software version
- Wi-Fi-capable model confirmed
- Complete displayed message or error code
- Wireless indicator behavior
- Original room and department
- Connection tested in another location
- Known-good pump comparison completed
- AC power and startup tested
- Physical or liquid damage observed
- Multiple pumps affected
- Pump visible in management software
- Drug-library or configuration version
- Network or server outage identified
- Clinical Engineering, IT, or vendor escalation completed
- Final device status
Final Thought
Protect the patient and confirm the pump’s primary infusion function before investigating connectivity. Use location and known-good-device comparisons to separate pump failures from infrastructure problems, and document the final status clearly.
That is successful troubleshooting.