GE Healthcare CARESCAPE Canvas

Asset Type

Patient Monitor

Manufacturer

GE Healthcare

Model

CARESCAPE Canvas

What This Guide Helps With

Troubleshooting missing central-station communication caused by network connections, configuration, admission, duplicate addressing, infrastructure, or communication-service issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot network communication while the CARESCAPE Canvas is the only monitor supporting an actively monitored patient.

If central monitoring is unavailable:

• Notify the clinical team immediately.
• Confirm that local monitoring, waveforms, parameter values, and alarms remain functional.
• Assign direct observation or transfer the patient to another verified monitoring system when central surveillance is clinically required.
• Do not assume local alarms are being received at the central station.

Expected outcome: Patient monitoring continues without relying on an unavailable central-station connection.

Continue Clinical Engineering troubleshooting only when it is safe to do so.

2. Confirm the Exact Communication Failure

Determine whether:

• The monitor is completely absent from the central station.
• The patient tile is present but shows communication loss.
• Waveforms or values are delayed, frozen, or intermittent.
• Alarms are not reaching the central station.
• The monitor connects briefly and then disconnects.
• Only one monitor, one room, or an entire care area is affected.

Check whether the local monitor displays a network, central-station, or communication message.

Expected outcome: The scope and behavior of the failure are clearly identified.

If several monitors are affected, investigate shared network or central-station infrastructure before replacing monitor components.

3. Verify Local Monitoring Operation

Confirm that the CARESCAPE Canvas:

• Powers on normally.
• Displays current patient waveforms and parameter values.
• Produces local visual and audible alarms.
• Responds normally to controls.
• Does not show a system freeze, repeated reboot, or configuration-loading error.

Expected outcome: The monitor operates normally except for central-station communication.

If the monitor is also freezing, rebooting, or losing local parameters, remove it from service and evaluate the broader monitor failure first.

4. Verify Patient Admission and Bed Assignment

Confirm that:

• The patient is properly admitted or associated with the correct bed.
• The monitor has the expected unit, room, and bed assignment.
• The same patient or bed is not active on another monitor.
• The central station is configured to display that bed.
• The monitor has not been moved from another care area without being discharged or reassigned.

Correct obvious admission or bed-assignment errors according to facility workflow.

Expected outcome: The correct patient and bed appear at the intended central station.

If communication is restored, verify live waveforms and alarm delivery, document the correction, and stop.

5. Inspect the Physical Network Connection

For a wired installation:

• Confirm the Ethernet cable is fully seated at the monitor or docking connection.
• Confirm the wall jack or network connection is secure.
• Inspect the cable and connector tabs for damage.
• Look for bent contacts, contamination, or a loose docking interface.
• Check for network link or activity indicators when visible.

Reseat the cable at both accessible ends.

Expected outcome: The connection is secure and network link activity is present.

If communication returns and remains stable, complete a functional verification and stop.

6. Test with a Known-Good Network Cable

Replace the existing network cable with a verified compatible cable.

Do not use visibly damaged, tightly kinked, crushed, or unapproved cables.

Expected outcome: A known-good cable establishes stable communication.

If the replacement cable resolves the problem, remove the defective cable from use, verify central waveforms and alarms, document the replacement, and stop.

7. Test the Network Port or Wall Jack

When permitted by facility network policy:

• Connect the monitor to a known-working approved network port assigned to the monitoring network.
• Alternatively, connect a known-good compatible monitor to the suspect port.
• Do not connect the monitor to an unapproved general-purpose network.

Expected outcome: Testing identifies whether the failure follows the monitor or remains with the network port.

If the known-good monitor also fails, escalate the port, switch, VLAN, or network-path issue to the appropriate IT or network support team.

If the CARESCAPE Canvas fails on a verified working connection, continue monitor-specific checks.

8. Check the Docking or Mounting Connection

If network communication passes through a dock, mounting interface, or connected system component:

• Confirm the monitor is fully seated.
• Inspect accessible contacts for contamination or damage.
• Remove and reseat the monitor only when it is safe and permitted.
• Verify that the dock or mounting component has power and is recognized.

Expected outcome: The monitor establishes a reliable connection through the docking interface.

If reseating restores communication, verify stability by observing live data at the central station before returning the device to service.

9. Review Network and Central-Station Status Messages

Record any messages indicating:

• Network disconnected
• Central station unavailable
• Duplicate network address
• Invalid configuration
• Bed already assigned
• Communication timeout
• Server or monitoring-network unavailable

Do not change IP addresses, VLAN settings, host names, certificates, or protected network configuration without approved documentation and authorization.

Expected outcome: The displayed message directs troubleshooting toward a connection, configuration, addressing, or infrastructure problem.

10. Check for Duplicate or Incorrect Network Identity

Coordinate with the facility’s monitoring-network administrator or IT department to confirm that the monitor has:

• The approved network identity.
• The correct assigned address or approved addressing method.
• No duplicate IP address or host identity.
• The correct monitoring-network segment or VLAN.
• The expected unit and central-station association.

A duplicate network identity may cause intermittent communication, repeated disconnection, or the wrong monitor appearing at the central station.

Expected outcome: The monitor has a unique, approved identity on the correct monitoring network.

If an addressing or assignment error is corrected, verify communication, patient association, waveforms, and alarm delivery before returning the monitor to use.

11. Determine Whether Other Devices Are Affected

Check other monitors connected to:

• The same wall jack area.
• The same network switch.
• The same care unit.
• The same central station.

Also confirm whether the central station is powered, operating normally, and receiving data from other beds.

Expected outcome: The problem is isolated to the monitor, a specific network location, or shared infrastructure.

The CARESCAPE Central Station is designed to display monitoring information delivered through the CARESCAPE monitoring network, so widespread loss generally indicates a shared network or central-system issue rather than simultaneous monitor failures.

12. Perform a Controlled Restart

After confirming that the patient is no longer dependent on the device:

• Discharge or preserve patient information according to facility policy.
• Shut down the monitor using the normal procedure.
• Wait briefly for shutdown to complete.
• Restart the monitor.
• Allow network and monitoring services to initialize fully.
• Reconfirm the unit, bed, and patient association.

Do not repeatedly cycle power as a substitute for identifying an ongoing network problem.

Expected outcome: Communication services initialize and the monitor reconnects to the central station.

If communication returns, observe the connection long enough to confirm it remains stable.

13. Verify Central Monitoring and Alarm Communication

Before returning the monitor to service:

• Confirm the correct bed appears at the central station.
• Confirm live waveforms and values update continuously.
• Compare central values with the local monitor.
• Generate an approved test alarm or use an approved simulator.
• Confirm the visual and audible alarm is received at the intended central station.
• Confirm alarm clearing and patient identification operate correctly.

Expected outcome: Live data and alarm communication are correctly transmitted and displayed.

If values appear but alarms are not received, keep the device out of service until the alarm-routing problem is corrected.

If the Problem Persists

If known-good cables, network ports, bed assignments, docking connections, approved network configuration, and central-station availability have been verified, common external causes have been ruled out.

The failure may involve:

• The monitor’s network interface
• Docking or mounting communication hardware
• Corrupted configuration
• Authentication or certificate services
• Internal communication software
• Monitoring-network infrastructure
• Central-station software or server services

The device should be:

• Removed from service
• Labeled Out of Service
• Sent for bench evaluation or authorized repair
• Escalated to GE HealthCare support and the facility network team as appropriate

Do not perform unapproved internal disassembly or alter protected network settings. Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

A locally functioning monitor does not guarantee that waveforms or alarms are reaching the central station. Never troubleshoot central communication on an active patient without alternate monitoring or direct clinical observation.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the CARESCAPE Canvas displayed patient data locally but did not appear at the CARESCAPE Central Station."

Cause

What was observed during troubleshooting.

Example:
"The monitor’s network cable failed substitution testing and did not establish a stable network link."

Resolution

What action was taken.

Example:
"Replaced the damaged network cable, confirmed live waveforms and test-alarm delivery at the assigned central station, and returned the monitor to service."

Helpful Details to Include (If Known)

• Local monitoring and alarms verified
• Exact communication message displayed
• Patient, unit, room, and bed assignment
• Whether one or multiple monitors were affected
• Ethernet link or activity indicator status
• Network cable inspected or replaced
• Alternate network port tested
• Docking connection reseated
• Duplicate address or configuration issue identified
• Central station operating status
• Live waveforms verified at central
• Test alarm successfully received
• IT or GE HealthCare case number
• Final device status

Final Thought

Central-station failures require confirmation of patient safety, local monitoring, physical connections, bed assignment, network infrastructure, and alarm delivery. Logical isolation and complete CCR documentation support safe escalation and prevent unnecessary monitor replacement.

That is successful troubleshooting.