On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting BD Alaris infusion pumps that fail to connect to the hospital network, either via wireless (Wi-Fi) or wired Ethernet. Symptoms may include the pump failing to communicate with the EMR, Guardrails Library updates not completing, or alarms indicating network errors. This guide emphasizes external, easily verifiable causes before considering internal network module issues.
Step-by-Step Troubleshooting
Verify Network Settings on Pump
- Check that the pump’s network configuration matches hospital requirements (SSID, VLAN, IP settings).
- Incorrect configuration is a common cause of connectivity failure.
Inspect Physical Connections (Ethernet Only)
- Ensure the Ethernet cable is fully seated at both the pump and wall port.
- Swap the cable with a known working one to rule out cable failure.
Check Wi-Fi Signal and Coverage
- Confirm the pump is within range of the access point.
- Observe signal strength indicator; weak signal can cause intermittent connectivity.
Verify Network Availability
- Ping the network or test another device at the same port or Wi-Fi access point to ensure connectivity.
- If other devices fail, the issue may be with the network rather than the pump.
Restart Network Services on Pump
- Power cycle the pump to refresh network connection.
- Some network errors are resolved with a simple reboot.
Check for IP Conflicts or DHCP Issues
- Ensure the pump is receiving a valid IP address.
- If using static IPs, confirm no duplicate IPs exist.
Observe Network Indicators and Logs
- Look for any network error codes, flashing LEDs, or system messages.
- Document any codes for escalation.
If the Problem Persists
External network issues, cables, or settings have been ruled out.
Likely causes include internal network module failure or corrupted network configuration.
- Remove pump from service.
- Label as Out of Service.
- Send to BD service or Clinical Engineering bench for evaluation.
- Avoid attempting internal repair beyond configuration reset.
Clinical Use Tip
Never troubleshoot the network while the pump is actively infusing a patient.
Move the patient to another pump if necessary.
Ensure patient safety takes priority over connectivity troubleshooting.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Pump not communicating with EMR; wireless connection failing.”
Cause
What was observed during troubleshooting.
Example:
“Pump unable to connect; verified network settings, Wi-Fi coverage, and Ethernet cable; other devices on network functional.”
Resolution
What action was taken.
Example:
“Pump removed from service, labeled Out of Service, sent to Clinical Engineering for network module evaluation.”
Helpful Details to Include
- Network type used (Wireless / Ethernet)
- IP configuration (DHCP / static)
- SSID name and signal strength if wireless
- Wall port or switch tested
- Any error codes observed
- Pump software version
Final Thought
Patient safety comes first; network connectivity is critical for EMR integration but should never compromise an active infusion. Logical, stepwise troubleshooting ensures external causes are resolved before escalating to internal repair. Accurate documentation in CCR format helps track patterns and supports cost avoidance when vendor intervention is required.
That is successful troubleshooting.