On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide addresses situations where the Efficia CM Series monitor intermittently or completely loses network connectivity. Symptoms may include:
- Central station not displaying the patient
- Monitor dropping off telemetry view
- “Network Disconnected” or similar message
- Intermittent data gaps in EMR
- Wired LAN icon missing or flashing
The focus is on ruling out external and easily verifiable causes before assuming internal network board failure.
Step-by-Step Troubleshooting
1. Verify the Clinical Situation First
- Confirm the patient is stable.
- If actively monitored via central station, move the patient to another monitor if necessary before troubleshooting.
- This prevents patient safety risks during connectivity loss.
2. Confirm Power Stability
- Verify the monitor is powered on and not cycling.
- Check for loose AC power cord.
- Confirm outlet is functional (test with outlet tester or alternate device).
- Observe for recent power interruptions.
- Network drops are often secondary to brief power loss or brownouts.
3. Inspect the Ethernet Cable
- Confirm Ethernet cable is fully seated in:
- Monitor LAN port
- Wall jack or network switch
- Remove and firmly reseat the cable.
- Inspect for:
- Bent locking tab
- Damaged insulation
- Crushed or kinked cable
- Loose or damaged cables are one of the most common causes of intermittent network drops.
4. Check Link/Activity Indicators
- Observe link lights at the monitor LAN port.
- Observe link lights at the wall jack or switch (if accessible).
- Note if lights are:
- Solid (normal)
- Flashing (activity)
- Off (no connection)
- No link light typically indicates physical layer issue (cable, port, switch).
5. Swap the Ethernet Cable
- Replace with a known-good network cable.
- Avoid reusing the same cable even if it “looks fine.”
- This rules out intermittent internal conductor breaks.
6. Test Alternate Network Port (If Available)
- Move the monitor to a nearby known-working network jack.
- Confirm whether connectivity stabilizes.
- If the issue resolves, suspect:
- Faulty wall drop
- Patch panel issue
- Switch port failure
7. Verify Network Configuration
- Confirm correct network settings:
- IP configuration (DHCP vs static)
- Correct VLAN (per facility standard)
- Check for incorrect manual IP assignment.
- Power-cycle the monitor after verifying configuration.
- Incorrect configuration can cause intermittent authentication or registration issues.
8. Check for Hospital Network Issues
- Ask unit staff:
- Are other monitors affected?
- Is the central station online?
- Contact IT/network team to verify:
- Switch status
- Port errors
- VLAN disruptions
- Multiple devices dropping at once suggests infrastructure issue, not device failure.
9. Perform Controlled Power Cycle
- Remove monitor from patient.
- Power down fully.
- Disconnect AC power for 60 seconds.
- Restart and observe boot process.
- Confirm network reconnects automatically.
- This resets the network stack and clears transient communication faults.
10. Observe for Recurrence
- Leave monitor connected for a monitoring period.
- Confirm:
- No repeated disconnect alerts
- Continuous central station visibility
- Stable EMR data transmission
- Intermittent faults may require extended observation.
If the Problem Persists
If:
- Multiple cables and ports have been ruled out
- Network infrastructure is confirmed functional
- Configuration is correct
The monitor continues to drop connectivity. The issue is likely internal, such as:
- Failing internal network interface
- Main board communication fault
- Internal power regulation instability
At this point:
- Remove the device from service
- Label it Out of Service
- Send for bench evaluation or manufacturer repair
Knowing when to escalate prevents unnecessary downtime and protects patient safety.
Clinical Use Tip
Do not troubleshoot network connectivity on an actively monitored critical patient. Always transition the patient to a confirmed working monitor before performing power cycles or cable swaps.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
Nursing reported monitor intermittently dropping off central station and displaying “Network Disconnected.”
Cause
What was observed during troubleshooting.
Example:
Intermittent Ethernet cable failure identified. Link light lost when cable manipulated.
Resolution
What action was taken.
Example:
Replaced Ethernet cable with known-good cable. Verified stable connection for 30 minutes. Monitor remained online at central station.
Helpful Details to Include in Documentation
- Outlet tested
- Ethernet cable swapped
- Alternate port tested
- Link light behavior
- IT contacted (if applicable)
- Final network status
- Device returned to service or removed
Final Thought
Effective troubleshooting starts with the physical layer: power and cabling. Most network connectivity issues are external and easily corrected. When those are ruled out, escalating appropriately protects patient monitoring integrity and ensures efficient repair workflow.
That is successful troubleshooting.