On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting missing, outdated, incomplete, or failed Agilia drug-library updates caused by connectivity, assignment, power, server, or configuration issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not troubleshoot, restart, reconfigure, or update an Agilia pump while it is actively delivering medication to a patient.
- Notify the responsible clinical staff.
- Transfer the infusion to another verified pump if the current drug library cannot be confirmed.
- Do not assume that displayed drug names, concentrations, or dose limits are current.
- Follow the facility’s approved downtime or manual-programming procedure when continued therapy is necessary.
Expected outcome: Patient therapy continues without relying on an unverified or outdated drug library.
If the pump’s drug-library status cannot be confirmed, remove it from clinical use until the issue is resolved.
2. Clarify the Reported Failure
Determine whether:
- The pump does not receive the drug-library download.
- The download begins but does not complete.
- The pump appears connected but retains an older library version.
- The correct library is installed, but the expected clinical profile is missing.
- Only one pump is affected.
- Multiple pumps, a rack, a care area, or the entire fleet is affected.
- The issue involves a wireless Agilia Connect deployment or a direct cable connection.
Record any displayed message, synchronization status, library version, profile name, date, and time.
Expected outcome: The problem is narrowed to an individual pump, connection method, profile assignment, or system-wide deployment issue.
3. Confirm That the Correct Library Was Released
Contact the pharmacy, medication-safety, or drug-library administrator and verify:
- The new library was approved and released for distribution.
- The release applies to the affected Agilia pump model.
- The pump’s clinical area or profile was included.
- The expected library version and release date.
- The deployment has not been paused, withdrawn, or scheduled for a later time.
Vigilant Master Med is used to create, customize, and distribute drug libraries, while Vigilant Centerium supports remote library distribution to connected Agilia pumps.
Expected outcome: The expected library is confirmed as valid, released, and assigned to the affected pump population.
If the library was not released or assigned, stop troubleshooting the pump and refer the issue to the drug-library administrator.
4. Verify the Pump’s Installed Library and Profile
With the pump removed from patient use:
- Power it on normally.
- Review the displayed drug-library version, profile, ward, or configuration information available through the normal user interface.
- Compare the information with the approved version supplied by the drug-library administrator.
- Confirm that the pump is not operating in a basic profile or another clinical area’s profile.
Agilia configurations may support multiple customized profiles, so an incorrect profile assignment can resemble a failed library download.
Expected outcome: The installed version and selected clinical profile match the approved deployment.
If the correct library is present but the wrong profile is selected, follow the facility-approved profile-selection process and retest. Stop if resolved.
5. Check Power and Allow the Update to Complete
Confirm that:
- The pump has adequate battery charge.
- The pump is connected to approved AC power when possible.
- The pump remains powered on throughout the synchronization period.
- The device is not being repeatedly removed from power, restarted, or moved between coverage areas.
- No low-battery, power-loss, or startup error is present.
A download may be delayed or interrupted if the pump powers down or loses communication before the transfer is complete.
Expected outcome: The pump remains continuously powered and available for the full update process.
If the library completes after stable power is restored, verify the version and return the device according to facility policy.
6. Inspect the Wireless or Rack Connection
For wireless Agilia Connect installations:
- Confirm that the pump is a Wi-Fi-capable Agilia model.
- Check the pump’s normal wireless or network-status indication.
- Move the pump to a known working coverage area approved for device testing.
- Compare its behavior with another Agilia pump that successfully synchronized in the same location.
- If the pump is rack-mounted, confirm it is fully seated and that the rack or Link+ system has power and normal status indicators.
- Inspect accessible communication contacts and connectors for contamination, damage, or incomplete engagement.
Wireless Agilia pumps can receive drug-library updates through the Agilia Connect system and Centerium infrastructure.
Expected outcome: The pump establishes normal communication or the failure is isolated to the pump, rack position, or network location.
If reseating the pump or moving it to a verified coverage area resolves the problem, confirm the downloaded version before returning it to service.
7. Compare With a Known-Good Pump and Location
Use a known-good Agilia pump of the same type and configuration.
- Place the known-good pump in the same rack position or wireless location.
- Place the affected pump in a location where another pump synchronized successfully.
- Observe whether the problem follows the pump or remains with the location.
- Do not exchange pump components or open the enclosure.
Expected outcome:
- If the problem follows the pump, suspect pump registration, configuration, communication hardware, or software.
- If the problem remains with the location, suspect the rack, wireless coverage, network, or server pathway.
- If multiple pumps fail simultaneously, suspect a system-wide deployment or infrastructure issue.
8. Verify Pump Registration and Assignment
Have the appropriate system administrator confirm that:
- The pump is present in Centerium or the facility’s Agilia management environment.
- The serial number or device identifier matches the physical pump.
- The pump is assigned to the correct facility, care area, and profile group.
- The pump has not been retired, duplicated, quarantined, or incorrectly assigned.
- The correct library package is targeted to the device.
- The pump’s communication and update status is current.
Agilia Partner is intended for biomedical configuration and maintenance support, while Centerium manages communication between connected pumps and software applications.
Expected outcome: The pump is correctly recognized and targeted by the drug-library management system.
If an assignment or registration error is corrected, allow the pump to synchronize and verify the final library version.
9. Check for a Fleet-Wide or Server-Side Problem
If several pumps are affected:
- Determine whether all affected pumps share the same unit, profile, access point, rack, or network segment.
- Contact the drug-library, pharmacy, network, or server administrator.
- Confirm that Centerium and associated Vigilant services are operational.
- Verify that the deployment job is active and not reporting errors.
- Check for recent network, certificate, firewall, authentication, or server changes.
- Do not repeatedly reset individual pumps when the failure is clearly system-wide.
Expected outcome: The problem is identified as a central deployment, server, network, or configuration issue rather than multiple simultaneous pump failures.
Escalate infrastructure problems to the responsible IT and Fresenius Kabi support teams.
10. Inspect a Direct Cable Connection When Used
For facilities that update standalone pumps through Vigilant Drug’Lib:
- Use only the approved isolated Fresenius Kabi Agilia USB or RS-232 communication cable.
- Inspect the cable, connector, and pump communication port for damage or contamination.
- Confirm the connector is correctly aligned and fully secured.
- Try a known-good approved cable and computer port.
- Confirm the Vigilant Drug’Lib software is running.
- Verify that the required USB communication driver is installed.
- Attempt the connection again using the approved application workflow.
Fresenius Kabi documentation identifies approved Agilia USB and RS-232 cables for standalone pump transfers and notes that the USB driver must be installed before connection.
Expected outcome: The pump appears as a connected device and the approved library transfer completes.
If a known-good cable and workstation communicate with other pumps but not the affected unit, remove the pump from service for evaluation.
11. Perform One Controlled Restart
When the pump is off the patient and no download is actively progressing:
- Disconnect it from the rack or communication cable.
- Power it down normally.
- Wait briefly.
- Restore approved AC power.
- Restart the pump.
- Reconnect it to the normal communication pathway.
- Allow sufficient time for registration and synchronization.
Do not repeatedly cycle power because repeated interruptions may prevent a pending update from completing.
Expected outcome: The pump reconnects and receives the assigned library.
If the update completes, verify the library version, profile, date, and operational status before return to service.
12. Verify the Completed Update
After the synchronization reports completion:
- Restart the pump if required by the approved workflow.
- Confirm the new drug-library version.
- Confirm the correct clinical profile.
- Verify that representative approved drugs, concentrations, units, and limits are displayed.
- Ensure no download, configuration, communication, or software error remains.
- Perform the facility-required functional and operational checks.
- Do not alter clinical drug limits solely to test the pump.
Expected outcome: The correct approved library and profile are installed and the pump passes operational verification.
If the expected library cannot be verified, do not return the pump to clinical use.
If the Problem Persists
If power, profile selection, release status, device assignment, wireless coverage, rack seating, approved cables, and server availability have been checked, the problem may involve internal communication hardware, corrupted configuration, incompatible software, or a system-management fault.
The device should be:
- Removed from service.
- Labeled Out of Service.
- Sent for bench evaluation or authorized repair.
- Escalated to the drug-library administrator, IT/network team, or Fresenius Kabi technical support as appropriate.
Do not perform unapproved software loading, database modification, internal disassembly, or component-level repair.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
Never assume that a drug library is current because drug names appear on the screen. Before clinical use, verify the approved library version and profile according to facility policy.
Do not troubleshoot synchronization problems while the pump is attached to an active patient. Move the patient’s infusion to another verified device first.
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 did not receive the newly released drug library and continued displaying the previous version."
Cause
What was observed during troubleshooting.
Example:
"The pump was registered in Centerium under the incorrect clinical profile group and was not targeted by the current library deployment."
Resolution
What action was taken.
Example:
"Corrected the device assignment with the system administrator, completed synchronization, verified the approved library version and profile, and returned the pump to service after functional testing."
Helpful Details to Include (If Known)
- Pump type and exact Agilia model recorded
- Asset tag and serial number recorded
- Current library version recorded
- Expected library version recorded
- Clinical profile or ward recorded
- AC power and battery status checked
- Wireless status or rack position checked
- Known-good location tested
- Known-good pump compared
- Approved cable swapped
- Pump registration verified
- Deployment assignment verified
- Other affected pumps identified
- Displayed error message recorded
- Server or network issue reported
- Final library version verified
- Final device status documented
Final Thought
Drug-library failures require a structured check of patient safety, release status, pump assignment, connectivity, power, and deployment infrastructure. Confirm the approved version before clinical use, escalate internal or system-level failures appropriately, and clearly document the final device status.
That is successful troubleshooting.