On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting B. Braun Space Infusion Pumps that fail to communicate with the EMR (Electronic Medical Record) system or drug library server. Common issues are often related to network connectivity, server access, or configuration rather than internal pump failure. This guide focuses on external, verifiable checks before escalation.
Step-by-Step Troubleshooting
Confirm Device Power and Operation
- Ensure the pump powers on fully and completes self-tests without errors.
- A pump not passing self-test may indicate broader hardware issues affecting communication.
Check Network Connectivity
- Verify the Ethernet or Wi-Fi connection is secure.
- If using Ethernet, confirm the cable is seated and not damaged.
- If using Wi-Fi, confirm the network credentials and signal strength.
Verify Network Settings on Pump
- Confirm IP address, subnet mask, gateway, and DNS are configured correctly.
- Ping the server from the pump (if available) or confirm the network port is accessible.
Confirm Server Availability
- Verify the EMR or drug library server is online and responding.
- Check for scheduled maintenance or network outages that may impact connectivity.
Check Firewall and Security Settings
- Ensure the pump’s IP address is allowed through network firewalls.
- Verify port requirements are met for communication with the EMR or drug library server.
Test with Alternate Device or Port
- Connect another pump or device to the same network connection to rule out port or switch issues.
- Swap network cables if necessary.
Restart Devices
- Restart the pump and, if possible, the network switch or EMR interface module to clear temporary communication errors.
If the Problem Persists
External checks have been exhausted; the issue may be internal to the pump or server interface.
- Remove the pump from service.
- Label as “Out of Service.”
- Send for repair or bench evaluation.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
- Do not attempt network troubleshooting while the pump is actively infusing a patient.
- Move the patient to another functioning pump before performing troubleshooting.
- Verify connectivity only when the pump is idle or safely offline.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
Pump unable to communicate with EMR/drug library; alerts displayed on interface.
Cause
What was observed during troubleshooting.
Example:
Observed network connectivity issues; pump IP settings confirmed correct; server reachable from another device.
Resolution
What action was taken.
Example:
Pump removed from service and sent to Clinical Engineering bench for evaluation.
Helpful Details to Include
- Network cable checked
- Alternate network port tested
- Server reachable from other devices
- Pump power-on self-test results
- Any error messages displayed on the pump interface
- Final device status: Out of Service
Final Thought
Patient safety is the top priority. Logical, stepwise troubleshooting reduces risk and ensures proper escalation. Accurate CCR documentation helps maintain clear communication and justifies removal from service when needed. External checks often resolve the majority of communication issues without opening the pump.
That is successful troubleshooting.