On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where the CARESCAPE Canvas loses network connectivity. Symptoms may include the monitor dropping off the central station, failure to transmit patient data, intermittent communication with the network, or network warning messages. Many network issues are caused by simple external problems such as loose cables, disconnected wall ports, or temporary network outages.
Step-by-Step Troubleshooting
Ensure Patient Safety First
- Never troubleshoot a patient monitor while it is actively being used on a patient.
- Move the patient to another functioning monitor before removing the device from service or performing troubleshooting steps.
- Patient monitoring continuity must always be maintained before beginning technical evaluation.
Confirm the monitor is powered on and operating normally
- Verify the display is active and the monitor is functioning locally.
- A monitor that appears to have network issues may actually be experiencing a broader system problem if it is not fully booted or responsive.
Check the network cable connection at the monitor
- Ensure the Ethernet cable is fully seated in the network port on the monitor or docking station.
- Loose or partially inserted cables are a common cause of dropped connections.
Inspect the wall network port connection
- Confirm the cable is firmly connected to the wall port.
- If the monitor was recently moved, the cable may have been accidentally disconnected or partially pulled out.
Look for network link indicator lights
- Many Ethernet ports have small LEDs that indicate link and activity.
- If no lights are present, the monitor may not be detecting a valid network connection.
Swap the Ethernet cable with a known-good cable
- Damaged or worn network cables can cause intermittent communication failures.
- Replacing the cable is a quick way to rule out a cable fault.
Test the wall port with another device
- If possible, connect a known-working monitor or network device to the same wall port.
- This helps determine whether the issue is with the network infrastructure rather than the monitor.
Check for recent room moves or configuration changes
- Some network drops occur when devices are moved to locations where the network port is not configured for patient monitoring equipment.
Restart the monitor
- Perform a controlled power cycle by shutting down the monitor and powering it back on.
- Temporary communication faults can sometimes be cleared during system reboot.
Verify network settings if accessible
- Confirm that the monitor has a valid IP address and that network configuration settings appear normal.
- An invalid or missing network configuration may indicate a network assignment issue.
Observe behavior after reconnection
- After checking connections and rebooting, monitor the device to confirm whether the network connection remains stable or drops again after a period of time.
If the Problem Persists
If network cables, wall ports, and basic configuration checks have been verified, the issue may involve an internal network interface fault or a deeper network infrastructure problem.
At this point the monitor should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or vendor repair if necessary
Knowing when external causes have been ruled out is an important part of effective troubleshooting.
Clinical Use Tip
Never troubleshoot a patient monitor while it is actively being used on a patient. Move the patient to another functioning monitor before removing the device from service or performing any troubleshooting steps.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“User reported that the CARESCAPE Canvas TC70 repeatedly disconnects from the central station and is not transmitting patient data.”
Cause
What was observed during troubleshooting.
Example:
“Loose Ethernet cable connection identified at the monitor docking port.”
Resolution
What action was taken.
Example:
“Reseated the network cable and verified link lights and stable network communication. Monitor returned to service.”
Helpful Details to Include (If Known)
- Outlet power verified
- Ethernet cable condition checked
- Network link lights observed
- Wall port tested with alternate device
- Cable swapped with known-good cable
- Monitor rebooted
- Network status observed after reconnection
- Final device status documented
Final Thought
Network issues on patient monitors are often caused by simple physical connection problems rather than internal device failures. Clinical Engineering should always begin with the most visible and easily verifiable components before assuming a hardware issue. Careful troubleshooting and clear documentation help ensure reliable patient monitoring and reduce unnecessary equipment downtime.
That is successful troubleshooting.