On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting communication loss between CARESCAPE Central Station, CIC Pro, network switches, bedside monitors, or CARESCAPE Gateway interfaces.
Step-by-Step Troubleshooting
Ensure Patient Safety First
A central monitoring communication issue can prevent alarms, waveforms, or patient data from displaying where staff expect to see them.
Action:
- Confirm patients are being monitored directly at the bedside.
- Notify clinical staff that central monitoring or gateway communication may be unreliable.
- Have staff verify alarms locally at the bedside monitor.
- Do not rely on the central station as the only alarm observation point until communication is restored.
Expected outcome: Patient monitoring continues safely while the network communication issue is investigated.
Why it matters: A network issue may affect visibility of alarms and patient data at the central station, even if the bedside monitor is still functioning.
If patient monitoring is protected and bedside monitoring is functional, continue.
Verify the Reported Communication Problem
Confirm exactly what is not communicating.
Action:
- Determine whether the issue affects one bedside monitor.
- Determine whether the issue affects one patient sector.
- Determine whether the issue affects one CIC Pro station.
- Determine whether the issue affects one CARESCAPE Central Station.
- Determine whether the issue affects multiple central stations.
- Determine whether the issue affects the CARESCAPE Gateway interface.
- Determine whether the issue affects an entire unit or VLAN/network segment.
Expected outcome: The failure pattern helps separate a single-device issue from a network switch, gateway, or system-wide communication issue.
If only one bedside monitor is affected, focus on that monitor, wall jack, cable, and assigned bed configuration first.
If multiple devices are affected, continue network path troubleshooting.
Check Whether Bedside Monitoring Is Still Working Locally
Go to the affected bedside monitor.
Action:
- Verify the monitor is powered on.
- Confirm ECG, SpO2, NIBP, invasive pressure, or other active parameters are displaying locally.
- Check whether local alarms are active and audible.
- Confirm the patient is assigned to the correct bed or care area if applicable.
Expected outcome: The bedside monitor should still show patient data locally even if central communication is down.
If the bedside monitor itself is malfunctioning, troubleshoot the bedside monitor first.
If the bedside monitor is functioning locally but not visible centrally, continue.
Verify the Scope at the Central Station
Check the CARESCAPE Central Station or CIC Pro display.
Action:
- Look for messages such as Bed offline.
- Look for messages such as No communication.
- Look for messages such as Monitor disconnected.
- Look for messages such as Data unavailable.
- Look for messages such as Gateway communication failure.
- Look for messages such as Blank patient sector.
- Look for messages such as Missing waveforms or delayed data.
- Confirm whether the issue is isolated to one bed or multiple beds.
Expected outcome: The central station should help identify whether communication loss is limited or widespread.
If only one bed is offline, continue with the bedside network path.
If many beds are offline at once, skip ahead to switch, gateway, or network infrastructure checks.
Check the Physical Network Cable at the Bedside Monitor
Inspect the network connection for the affected bedside monitor or docking location.
Action:
- Verify the Ethernet cable is fully seated.
- Check for a broken latch, loose connector, damaged cable jacket, or kinked cable.
- Confirm the cable is connected to the correct wall jack or network port.
- If available and allowed by site policy, swap with a known-good network cable.
Expected outcome: A loose or damaged network cable should be corrected, and communication may restore after the device reconnects.
If communication restores, confirm the bed appears correctly at the central station and stop.
Check the Wall Jack or Network Drop
Inspect the wall port serving the affected monitor.
Action:
- Confirm the Ethernet cable is connected to the correct labeled jack.
- Look for damaged wall plates, loose ports, bent contacts, or signs of impact.
- If the room has another known-good clinical network jack approved for monitoring, test from that jack according to site policy.
- Avoid using random network jacks that may be assigned to a different VLAN or non-monitoring network.
Expected outcome: The monitor should communicate when connected to a valid, active monitoring network jack.
If the issue follows the wall jack, escalate to IT/network support for jack, patch panel, or switch-port investigation.
Check Network Link Lights Where Accessible
At the bedside device, dock, switch, or patch point, check link/activity indicators if visible and accessible.
Action:
- Look for network link lights.
- Compare with a known-working bed or station.
- Verify that the port is not dark, intermittently flashing abnormally, or physically damaged.
Expected outcome: A valid network connection usually shows link/activity at the active network port.
If there are no link lights on a known powered device, suspect cable, jack, patching, switch port, or network configuration.
Verify CARESCAPE Central Station or CIC Pro Power and Network Connection
Check the central station workstation or CIC Pro station.
Action:
- Confirm the station is powered on and not frozen.
- Verify the network cable is connected.
- Check that the workstation is on the correct clinical monitoring network.
- Look for disconnected cables behind the workstation, under the desk, or at the wall jack.
- Confirm the keyboard, mouse, display, and system are responsive.
Expected outcome: The central station should be powered, responsive, and physically connected to the correct network.
If the station is frozen but other stations are working, perform a controlled restart only if approved by site policy and patient monitoring coverage is maintained.
Compare With Another Central Station or Viewer
Determine whether the same beds are visible on another central station.
Action:
- Check a nearby CARESCAPE Central Station, CIC Pro station, or approved viewer.
- Compare whether the same patient sectors are online or offline.
- Confirm whether alarms and waveforms appear normally elsewhere.
Expected outcome: If another central station displays the beds correctly, the issue may be local to one workstation, network port, or software session.
If all central stations lose the same beds, suspect upstream network, switch, gateway, or bedside monitor communication.
Check Network Switch Power and Basic Status
If the issue affects multiple beds or an entire area, check the related network switch if accessible to Clinical Engineering.
Action:
- Verify the switch has power.
- Check for power supply alarms, dark status LEDs, or abnormal indicator lights.
- Confirm network cables are seated.
- Look for accidental unplugging, recent work in the closet, or a tripped power strip/UPS issue.
- Do not move patch cables unless authorized and properly documented.
Expected outcome: The switch should be powered, stable, and showing active links on expected monitoring ports.
If the switch is powered off, unstable, or showing abnormal status, escalate to IT/network support immediately and keep clinical leadership informed.
Check for Recent Network or Room Changes
Communication failures often follow physical changes.
Action:
- Ask whether a room move occurred recently.
- Ask whether a monitor swap occurred recently.
- Ask whether a bed reassignment occurred recently.
- Ask whether network closet work occurred recently.
- Ask whether a switch replacement occurred recently.
- Ask whether a patch panel change occurred recently.
- Ask whether a software update occurred recently.
- Ask whether a power outage occurred recently.
- Ask whether construction or cabling work occurred recently.
Expected outcome: Recent changes may explain why the bedside monitor, CIC Pro, CARESCAPE Central Station, or Gateway is no longer communicating correctly.
If the issue started after network work, involve IT/network support with the affected rooms, switch ports, and timestamps.
Verify CARESCAPE Gateway Communication
If the issue involves data not reaching another system, check the CARESCAPE Gateway path.
Action:
- Confirm whether bedside data is visible at the central station.
- Confirm whether the issue is only with data leaving the monitoring network, such as export to an EMR, interface engine, or downstream system.
- Check the Gateway workstation/server power and network connection if accessible.
- Look for gateway-related error messages or interface communication warnings.
Expected outcome: If central monitoring works but downstream data does not transfer, the issue may be isolated to the CARESCAPE Gateway or interface path.
If the Gateway is not communicating, escalate to the appropriate GE, IT, or interface support team according to site policy.
Check for IP Address, Bed Assignment, or Configuration Mismatch
Do not assume hardware failure if communication fails after a device swap or bed move.
Action:
- Confirm the bedside monitor is assigned to the correct bed/location.
- Verify that the central station sector corresponds to the correct care area.
- Check whether the device was recently replaced with another monitor.
- Confirm whether the replacement device is approved and configured for that unit.
Expected outcome: The monitor should be assigned to the correct location and recognized by the central monitoring system.
If configuration appears wrong, escalate to the authorized system administrator, GE support, or Clinical Engineering staff trained on CARESCAPE network configuration.
Restart Only When Safe and Appropriate
A restart may restore a local workstation or monitor connection, but it should not be the first step during active monitoring.
Action:
- Confirm patient monitoring coverage before restarting anything.
- Restart only the affected device or workstation if allowed by site policy.
- Do not restart network switches, central stations, CIC Pro systems, or gateway servers without understanding the patient monitoring impact.
- After restart, confirm communication, waveforms, parameters, and alarms return.
Expected outcome: A temporary software or session issue may clear after a controlled restart.
If the problem returns, treat it as unresolved and escalate.
Confirm Alarm and Waveform Recovery
Once communication appears restored, verify more than just the bed name.
Action:
- Confirm the patient sector is visible.
- Verify ECG waveform or active parameters are updating.
- Confirm alarm status is displayed appropriately.
- Check that delayed, stale, or frozen data is not being mistaken for live data.
- Ask clinical staff to confirm the patient appears correctly at the central station.
Expected outcome: The central station should show current patient data, live waveforms, and expected alarm behavior.
If data is incomplete, delayed, or unstable, continue escalation.
If the Problem Persists
If power, cables, wall jacks, bedside monitor status, central station status, switch status, and basic configuration checks have been ruled out, the issue is likely beyond simple external troubleshooting.
The affected device, station, network path, or gateway should be removed from clinical reliance if monitoring is compromised, labeled Out of Service if the local device or workstation is suspected, sent for repair, bench evaluation, or authorized system/network support, and escalated to GE Healthcare support, IT/network support, or the interface team as appropriate.
Knowing when to stop is proper troubleshooting. Central monitoring network issues can affect multiple patients, so unnecessary resets, random cable moves, or undocumented configuration changes can create larger failures.
Clinical Use Tip
Do not troubleshoot a central monitoring communication issue as if it is only a computer problem. Confirm bedside monitoring and alarm visibility first. If central monitoring is unreliable, clinical staff must monitor patients locally or move them to a verified monitoring setup until communication is restored. Do not troubleshoot on an active patient without moving the patient to a backup device or verified monitoring method first when therapy or monitoring continuity is at risk.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"ICU reported that multiple beds were offline at the GE CARESCAPE Central Station and one CIC Pro station was not receiving patient data."
Cause
What was observed during troubleshooting.
Example:
"Found bedside monitors functioning locally, but the affected unit switch had no active link on several monitoring ports after recent network closet work."
Resolution
What action was taken.
Example:
"Verified patient safety with clinical staff, documented affected beds and switch location, escalated to IT/network support, and confirmed central station communication restored after switch port issue was corrected."
Helpful Details to Include (If Known)
- Alarm behavior or central station messages displayed
- Accessories swapped, including network cable, wall jack, or workstation connection
- Power behavior, including outlet, UPS, switch, workstation, or bedside monitor power status
- Environmental factors, including recent room moves, network closet work, construction, cabling work, or power outages
- Indicator lights, including network link lights, switch status LEDs, workstation status, or gateway status
- Final device status, including whether one bed, one station, multiple beds, CIC Pro, CARESCAPE Gateway, or the monitoring network remained affected
Final Thought
Central monitoring communication issues should be handled with a patient-safety-first mindset. Start with what can be verified externally: bedside monitoring, cables, wall jacks, workstation status, network switch power, and the scope of the failure. Escalate when the issue points to network infrastructure, gateway communication, configuration, or recurring system instability. Clear CCR documentation helps separate a single-device failure from a larger monitoring network problem.
That is successful troubleshooting.