On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the BD Alaris pump fails to load the Guardrails Drug Library or displays errors suggesting the library is corrupted. Users may report missing drug profiles, blocked infusions, or error messages indicating library issues. Many library issues are caused by simple communication, file, or software problems rather than internal pump failure.
Step-by-Step Troubleshooting
Verify Pump Power and Boot
- Ensure the pump powers on fully without error messages.
- A failed self-test can prevent the library from loading correctly.
- Why: Without full boot, the pump cannot access or display the library.
Check Network / EMR Connection
- Confirm the pump is connected to the hospital network (wired or wireless) and has IP access if using network-based library updates.
- Ping the EMR server or library server to confirm connectivity.
- Why: Library downloads require network communication; failures here often look like corrupted libraries.
Verify Library File on Update Media
- Check the USB drive or SD card used for library updates.
- Ensure it contains the correct, uncorrupted Guardrails Library file.
- Reformat media and reload the file if necessary.
- Why: A corrupt or incomplete file transfer can prevent loading.
Check Pump Software Version
- Ensure pump firmware/software is compatible with the current Guardrails Library version.
- Why: Mismatched software can cause loading failures or errors.
Attempt Manual Library Load
- Insert the update media (USB/SD) into the pump.
- Follow the pump prompts to manually load the library.
- Observe any error codes displayed during the process.
- Why: Confirms whether the pump can process the library independently of EMR connectivity.
Swap to Known-Good Library
- If available, try a previously verified library file to determine whether the problem is with the pump or the library file.
- Why: Differentiates between pump corruption and library corruption.
Document Any Error Messages
- Record any error codes, messages, or unusual behaviors for CCR documentation and possible vendor escalation.
If the Problem Persists
External causes have been ruled out (power, network, file integrity).
The pump may have internal software corruption or storage failure.
Next Steps:
- Remove the pump from service.
- Label as Out of Service.
- Send for manufacturer repair or bench evaluation.
Knowing when to stop is proper troubleshooting. Do not attempt internal software fixes beyond Clinical Engineering scope.
Clinical Use Tip
- Never attempt to infuse medication using a pump with a corrupted or missing library.
- Move the patient to another properly functioning pump first.
- Only troubleshoot library issues when the device is not in active use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Pump displays error ‘Drug Library Not Loaded’ and blocks infusion orders.”
Cause
What was observed during troubleshooting.
Example:
Confirmed that network connection is stable and update media file is correct; library fails to load manually, suggesting internal corruption.
Resolution
What action was taken.
Example:
Pump removed from service, labeled Out of Service, sent to BD for repair/bench evaluation.
Helpful Details to Include
- Pump software version and serial number
- USB/SD media type and last update date
- Error codes displayed during manual load attempt
- Any network connectivity tests performed
Final Thought
Patient safety and accurate infusion management depend on reliable library access. Following a logical troubleshooting sequence—from power and network checks to file integrity—reduces unnecessary downtime and ensures proper escalation when internal pump issues are suspected. Accurate CCR documentation supports patient safety, departmental efficiency, and cost avoidance.
That is successful troubleshooting.