On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the Infinity Delta monitor loses connection to the network or central station. Symptoms may include loss of patient visibility at the central station, intermittent disconnects, network alarms, or no communication with charting systems. The focus is on verifying external connections, network infrastructure, and configuration before assuming internal failure.
Step-by-Step Troubleshooting
Verify the Monitor is Powered On and Fully Booted
- Ensure the monitor is on and not in a startup or error state.
- A partially booted system may not establish network communication.
Check Network Cable Connection (Hardwired Systems)
- Confirm the Ethernet cable is securely connected at the monitor and wall port.
- Look for link/activity lights on the port (if visible).
- Reseat the cable to rule out a loose connection.
Inspect the Network Cable for Damage
- Check for bent pins, frayed cable, or damaged connectors.
- Swap with a known good cable to rule out cable failure.
Verify Wall Port Functionality
- Test the wall port using another known working device if possible.
- If the port is not active, the issue may be upstream (switch/network).
Confirm Correct Network Jack is Being Used
- Ensure the monitor is plugged into the designated patient monitoring network port, not a general data or inactive port.
Check Network Settings on the Monitor
- Verify IP address, subnet, and gateway (if accessible).
- Ensure the monitor is configured for DHCP or static IP per facility standards.
- Incorrect settings can prevent communication with the central station.
Restart the Monitor
- Power cycle the monitor to reset network communication.
- This can clear temporary communication or software faults.
Check Central Station Status
- Confirm the central station is operational and not down.
- Verify other monitors are connecting successfully.
Look for Network or Communication Alarms
- Note any error messages such as “network disconnected” or “server unavailable.”
- These can help identify whether the issue is local or system-wide.
Verify Device is Assigned/Admitted Correctly
- Ensure the monitor is properly associated with a patient/location in the system.
- Misconfiguration may appear as a connectivity issue.
Check for Recent Network Changes
- Determine if IT performed updates, VLAN changes, or switch maintenance.
- Network configuration changes commonly impact connectivity.
If the Problem Persists
If all external connections, cables, ports, and network conditions have been verified, the issue is likely internal to the monitor (network interface hardware or internal communication board).
- Remove the device from service
- Label it Out of Service
- 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 monitor is actively in use on a patient. Move the patient to a properly functioning monitor first to maintain continuous central monitoring and patient safety.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
Monitor not showing on central station; staff reports intermittent disconnects.
Cause
What was observed during troubleshooting.
Example:
Loose Ethernet cable connection identified at monitor; no link light observed.
Resolution
What action was taken.
Example:
Reseated and replaced Ethernet cable; verified network connection restored and monitor visible on central station.
Helpful Details to Include
- Network port tested
- Cable swapped
- Link/activity lights status
- Central station operational status
- Any network alarms displayed
- IP address/configuration verified
- Final connectivity status confirmed
Final Thought
Effective network troubleshooting starts with simple physical checks before escalating to configuration or internal faults. Maintaining patient visibility at the central station is critical, so always prioritize safe patient transfer before troubleshooting. Clear documentation ensures repeat issues can be identified and resolved faster.
That is successful troubleshooting.