On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Loss of communication between monitor and central station, missing patient data, or network disconnection due to cables, ports, or configuration issues.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Confirm the patient is still being monitored locally on the S5 monitor.
- If central station visibility is required, move the patient to a functioning monitored device.
- Expected: Patient monitoring remains active at bedside.
- Why it matters: Network loss affects remote visibility, not necessarily bedside monitoring—but can impact clinical awareness.
Verify the Reported Issue
- Confirm the monitor is not visible on the central station or network.
- Observe:
- Missing patient from central station list
- Network icon/status indicators on screen
- Any communication or network-related messages
- Expected: Confirmed loss of connectivity, not user selection issue.
- Why it matters: Ensures this is a true network issue and not workflow-related.
Check Network Cable Connection
- Inspect the Ethernet cable at the monitor.
- Ensure cable is firmly connected to the monitor port
- Check for loose or damaged connectors
- Reseat the cable
- Expected: Secure physical connection with no visible damage.
- Why it matters: Loose or damaged cables are the most common cause of connectivity loss.
Check Wall Port / Network Jack
- Verify the wall network connection.
- Confirm cable is fully inserted into wall jack
- Check for activity lights (if present)
- Move to a known working network port if available
- Expected: Active network port with link/activity lights.
- Why it matters: The issue may be with the infrastructure, not the monitor.
Inspect Network Indicator Lights on Monitor
- Look at the Ethernet port LEDs on the monitor.
- Observe link light (solid) and activity light (blinking)
- Expected: Lights indicate active network connection.
- Why it matters: No lights may indicate cable, port, or internal NIC issue.
Verify Network Configuration Settings
- Access network settings on the monitor.
- Confirm correct network mode (DHCP vs static)
- Verify IP address is assigned
- Check subnet and gateway if applicable
- Expected: Valid IP address within hospital network range.
- Why it matters: Incorrect configuration prevents communication even with good physical connection.
Power Cycle the Monitor
- Perform a controlled reboot of the S5 monitor.
- Expected: Network reconnects after reboot.
- Why it matters: Clears temporary communication or software faults.
Check Central Station Status
- Verify that the central station is operational.
- Confirm other monitors are visible
- Ask clinical staff if multiple devices are affected
- Expected: Central station functioning normally.
- Why it matters: Rules out system-wide outages vs single device issue.
Swap Known Good Cable
- Replace the Ethernet cable with a known working one.
- Expected: Connectivity restored if cable was faulty.
- Why it matters: Fast way to isolate cable failure without deeper troubleshooting.
If the Problem Persists
All common external causes have been ruled out. The issue is likely internal (network interface card, communication board, or software fault).
Remove the device from service, label it Out of Service, and send for repair or bench evaluation.
Knowing when to stop prevents unnecessary risk and wasted troubleshooting time.
Clinical Use Tip
Do not troubleshoot network connectivity while the device is actively being used on a patient requiring central monitoring. Transition first, then troubleshoot safely.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Monitor not appearing on central station; no network connectivity."
Cause
What was observed during troubleshooting.
Example:
"Faulty Ethernet cable with no link activity at port."
Resolution
What action was taken.
Example:
"Replaced Ethernet cable; confirmed restored communication with central station."
Helpful Details to Include (If Known)
- Network cable checked and/or replaced
- Wall port tested
- Network indicator lights status
- IP address presence or absence
- Central station operational status
- Device reboot performed
- Final connectivity status
Final Thought
Effective troubleshooting starts with simple, external checks like cables and ports before assuming internal failure. Patient safety and monitoring continuity must always come first. Clear documentation ensures future issues are resolved faster and builds reliability in the system.
That is successful troubleshooting.