On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting a Spacelabs Qube patient monitor that is not communicating with the EMR, central station, or network. Common signs include:
- Monitor fails to upload patient data to the EMR
- Central station does not display monitor data
- Network error messages on the monitor
- Delayed or missing alarm notifications on networked systems
This guide focuses on external and easily verifiable network and connection issues before assuming internal network card or software failure.
Step-by-Step Troubleshooting
Verify Physical Network Connections
- Check that the Ethernet cable is fully seated in both the monitor and network port.
- Look for damaged or loose cables.
- Test the same cable with a known working monitor to rule out cable failure.
Check Network Indicators
- Verify the monitor’s network LED lights (if present) for activity and link status.
- Ensure the network switch port shows a connection.
Confirm IP Address / Network Settings
- Access the monitor’s network configuration menu.
- Check that it has a valid IP address, subnet mask, and gateway for your hospital network.
- Confirm the EMR or central station IP and port settings match hospital network requirements.
Ping / Connectivity Test
- Use a hospital PC or network tool to ping the monitor’s IP address.
- If the ping fails, confirm network switch configuration and VLAN assignment.
Check for EMR / Central Station Issues
- Confirm the central station or EMR server is operational.
- Ensure no known network maintenance or outages are in progress.
- Verify other monitors can communicate to the same server.
Restart the Monitor / Network Interface
- Safely power down the monitor, wait 10–15 seconds, and power it back on.
- Some network issues clear with a reboot.
Swap Ports / Switches
- If the monitor still fails to communicate, try connecting it to a known working switch port.
- This helps isolate potential port or switch-level issues.
If the Problem Persists
External network and configuration issues have been ruled out. The problem may be internal (network card, software corruption, or firmware issue).
- Remove the monitor from service.
- Label it Out of Service.
- Send to Clinical Engineering bench for repair or escalate to manufacturer service.
Knowing when to stop troubleshooting prevents wasted effort and protects patient safety.
Clinical Use Tip
Do not troubleshoot on an active patient. Move the patient to another monitor that is confirmed operational. Ensure alarms are active on the replacement device before disconnecting the original.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Monitor data not appearing on central station; network error displayed.”
Cause
What was observed during troubleshooting.
Example:
“Ethernet cable and switch port confirmed functional; monitor IP settings verified; monitor still fails to communicate.”
Resolution
What action was taken.
Example:
“Device removed from service, labeled Out of Service, and sent to Clinical Engineering bench for further evaluation.”
Helpful Details to Include
- Outlet and network port tested
- Cables swapped
- Indicator lights status
- EMR/central station status
- Any error codes displayed on monitor
- Final device status
Final Thought
Effective troubleshooting of networked patient monitors relies on a logical progression: check connections, verify configuration, test communication, and escalate when necessary. Accurate documentation ensures continuity, patient safety, and supports cost-effective repair strategies.
That is successful troubleshooting.