On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Identifies causes for lost or delayed data from bedside monitors, missing alarms, or connection errors due to network, server, or configuration issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm all patients are actively monitored at the bedside. If needed, move monitoring to backup devices to prevent interruptions.
Check Network Connectivity
- Verify the central station is connected to the hospital network.
- Inspect Ethernet cables and patch panels for secure connections.
- Expected outcome: network link lights are active; no intermittent drops.
Ping Central Station from Server/Workstation
- Use network tools to ping the central station and confirm IP connectivity.
- Expected outcome: consistent response; no timeouts.
Check Server Status and Services
- Confirm Spacelabs server or database is operational.
- Restart relevant services if safe and authorized.
- Expected outcome: services report as running; central station reconnects.
Verify Configuration Settings
- Confirm IP, subnet mask, gateway, and port settings match hospital network requirements.
- Ensure firewall or VLAN settings allow communication.
- Expected outcome: no configuration mismatch; device can reach server.
Examine Logs for Errors
- Review central station and server logs for recent network errors, failed authentication, or dropped packets.
- Expected outcome: errors indicate whether the issue is network or server-side.
Test with Alternate Network Port or Switch
- Move central station to a known-good network port or switch to rule out hardware network issues.
- Expected outcome: stable communication if original port or switch was faulty.
If the Problem Persists
External network and configuration causes are ruled out. The issue is likely internal to the central station hardware or software.
- Remove the central station from service.
- Label as Out of Service.
- Send for vendor repair or bench evaluation.
Knowing when to stop prevents patient risk and wasted troubleshooting time.
Clinical Use Tip
Never troubleshoot network or server issues on a device actively monitoring patients.
Always ensure alternate monitoring is in place before any network intervention.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Central station intermittently losing connection to server; alarms not received."
Cause
What was observed during troubleshooting.
Example:
"Network cables and switch port tested; configuration settings verified; issue persists."
Resolution
What action was taken.
Example:
"Device removed from service; labeled Out of Service; sent for repair."
Helpful Details to Include (If Known)
- Outlet and network port tested
- Ethernet cables swapped
- Switch port verified
- Ping results documented
- Service logs reviewed
- Final device status labeled Out of Service
Final Thought
Clinical troubleshooting must balance patient safety with methodical problem-solving. Start with external checks, escalate when needed, and document thoroughly. This approach reduces risk and maximizes effective repairs.
That is successful troubleshooting.