On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Loss of communication between bedside monitors and central station, including intermittent dropouts, missing waveforms, or alarms not appearing centrally.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the patient is being actively monitored at the bedside. Do not rely on central station visibility during troubleshooting.
Verify Bedside Monitor is Powered and Active
- Check that the bedside monitor is ON, not in standby, and actively displaying patient data.
- If the monitor is off or frozen, resolve locally first.
Check Network Connectivity Indicator on Bedside Monitor
- Look for network/communication icons or messages (e.g., disconnected, searching, or no network).
- A visible disconnect indicates a network issue rather than central station failure.
Confirm Central Station is Operational
- Ensure the Sentinel central station is powered on, application is running, and not frozen.
- Restart application if unresponsive.
Check for Multiple Monitor Dropouts
- Determine if the issue affects:
- One monitor → likely local issue
- Multiple monitors → likely network or server issue
- This helps narrow scope quickly.
Inspect Network Cables (Wired Systems)
- Ensure Ethernet cable is securely connected at bedside monitor and wall port
- Look for damaged or loose cables
- Reseat connections
- Loose or damaged cables are a common cause of dropouts.
Verify Network Switch Port Activity
- Check link/activity lights at the network port or switch (if accessible).
- No activity suggests a port, cable, or network issue.
Check Wireless Signal (If Applicable)
- For wireless monitors: confirm signal strength indicator and check for known dead zones.
- Reposition monitor if needed. Weak signal commonly causes intermittent dropouts.
Confirm Correct Network Assignment / Unit Configuration
- Verify the bedside monitor is assigned to the correct unit/central station.
- Misconfiguration can cause the monitor to not appear centrally.
Restart Bedside Monitor (If Safe)
- Power cycle the bedside monitor after ensuring patient is safely monitored elsewhere.
- This can resolve temporary communication or software issues.
Restart Central Station Application or Workstation
- If multiple monitors are affected, restart the central station software or workstation (if approved).
- Clears software/network session issues.
Check Hospital Network Status
- Confirm with IT if there are network outages, VLAN issues, or server/interface problems.
- Central monitoring relies heavily on hospital network infrastructure.
Verify Server / Interface Connectivity
- If applicable, confirm communication with backend servers (e.g., Spacelabs network server).
- Loss here will affect multiple devices.
Observe for Recurring Dropouts
- Monitor for patterns (specific room, time, or movement-related).
- Patterns often point to infrastructure issues.
If the Problem Persists
If all external checks (power, cables, configuration, and network) have been verified, the issue is likely internal (network interface card, communication module, or server-side failure).
- Remove affected equipment from service if unreliable
- Label as Out of Service
- Send for bench evaluation or escalate to vendor/IT
Knowing when to stop prevents unnecessary risk and is proper troubleshooting.
Clinical Use Tip
Always transfer the patient to a confirmed working monitoring system before troubleshooting communication issues. Central visibility is secondary to bedside monitoring.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Central station not displaying patient data from bedside monitor in Room 12."
Cause
What was observed during troubleshooting.
Example:
"Loose Ethernet cable at wall port causing intermittent network disconnect."
Resolution
What action was taken.
Example:
"Reseated and secured network cable; confirmed stable communication to central station."
Helpful Details to Include (If Known)
- Bedside monitor powered and functional
- Network cable reseated/tested
- Switch port activity verified
- Wireless signal strength (if applicable)
- Central station operational status
- Number of devices affected
- Any IT/network outages reported
- Final device status (working, removed from service, escalated)
Final Thought
Central station communication issues are most often network-related, not device failure. Start with simple external checks, isolate scope quickly, and involve IT early when multiple devices are affected. Always prioritize patient monitoring at the bedside and document clearly to support ongoing reliability.
That is successful troubleshooting.