On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting profiles, display configurations, patient settings, or care-area defaults that fail to load because of workflow, connection, software, or configuration issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety First
Do not troubleshoot profile or configuration problems while the CARESCAPE Canvas is the only monitor supporting an active patient.
If required settings, alarm limits, waveforms, or patient information cannot be confirmed:
- Notify the clinical team.
- Transfer the patient to another verified monitoring device.
- Verify alarm limits and monitored parameters on the replacement equipment.
- Do not assume the intended settings loaded successfully.
Expected outcome: Patient monitoring continues on equipment with confirmed parameters, alarm limits, and patient identification.
Continue Clinical Engineering troubleshooting only after the affected system is safely removed from active patient use.
2. Confirm the Exact Failure
Determine what is not loading:
- Patient information or demographics
- Patient category
- Care-area or unit configuration
- User or clinical profile
- Display page or waveform layout
- Parameter settings
- Alarm limits or alarm configuration
- Network-delivered configuration
- Previously saved settings after restart
Record any message displayed and note whether the system loads incorrect defaults, remains on a loading screen, freezes, or returns to the previous configuration.
Expected outcome: The failure is clearly defined before settings are changed.
If the requested profile loads normally, verify its displayed settings and stop troubleshooting.
3. Confirm the Correct Patient and Care Location
Verify that the monitor is associated with the intended:
- Patient
- Bed
- Room
- Unit or care area
- Patient category
A patient or bed association mismatch may prevent the expected configuration from appearing or may cause a different default profile to load.
Do not alter or overwrite patient demographic information without following the facility’s approved patient-association workflow.
Expected outcome: The patient, bed, care area, and requested configuration correspond correctly.
If correcting the association restores the intended profile, verify all alarm limits and parameters, document the action, and stop.
4. Check for an Incomplete Admission, Discharge, or Transfer Workflow
Determine whether the problem began after:
- Admitting a new patient
- Discharging a previous patient
- Transferring a patient between beds or units
- Moving the monitor or acquisition equipment
- Reconnecting a CARESCAPE ONE monitor
- Changing patient category
Confirm that the previous patient session was properly completed and that the new patient was correctly admitted or selected.
Expected outcome: No incomplete patient session or transfer is preventing the new configuration from loading.
If completing the approved workflow resolves the issue, verify the loaded patient information and settings, then stop.
5. Verify the Requested Profile Is Available
Review the profiles, display pages, or configuration choices available through the normal clinical interface.
Confirm that:
- The requested profile appears in the selection list.
- The correct care area is active.
- The user has appropriate access to select the profile.
- The requested profile has not been renamed, replaced, or removed.
- The monitor is not intentionally restricted to an approved default configuration.
Do not enter service-level configuration areas or modify protected institutional defaults without authorization.
Expected outcome: The intended profile is present and selectable.
If the profile is absent on multiple Canvas systems in the same area, escalate the issue as a configuration-management problem rather than changing individual monitors.
6. Check the CARESCAPE ONE Connection
CARESCAPE Canvas may operate with CARESCAPE ONE as part of its monitoring platform. Confirm that the CARESCAPE ONE monitor is:
- Fully seated in its mount or docking connection
- Powered normally
- Free of startup or communication messages
- Connected using undamaged approved hardware
- Recognized by the Canvas display
Inspect accessible connectors for looseness, contamination, bent contacts, or physical damage. Do not probe connector contacts or perform internal disassembly.
Expected outcome: The acquisition monitor and Canvas display communicate normally.
If reseating an approved external connection restores the profile, verify patient information, parameters, alarm limits, and waveform layout before returning the system to service.
7. Inspect External Network Connections
If profiles, patient information, or care-area settings are delivered through the hospital network, inspect the accessible network path.
Check:
- Ethernet cable connection
- Wall jack connection
- Docking or mounting-station connection
- Visible link or communication indicators
- Cable damage or loose connectors
- Whether the network-disconnected symbol or message is present
Use a known-good approved cable or verified network port when permitted by facility policy.
Do not change IP addresses, VLAN settings, hostnames, certificates, or enterprise network parameters without coordinating with the responsible network or integration team.
Expected outcome: The monitor has a stable physical network connection without communication warnings.
If restoring the connection allows the configuration to load, verify the complete patient profile and stop troubleshooting.
8. Compare the Issue With Another Canvas System
When available, compare the affected system with a working CARESCAPE Canvas assigned to the same care area.
Determine whether:
- The requested profile appears on the comparison system.
- Both systems are assigned to the same unit.
- Both systems show normal network connectivity.
- The problem follows a particular CARESCAPE ONE monitor.
- The problem remains with the Canvas display or bed location.
- Multiple systems are affected simultaneously.
Do not move equipment supporting an active patient for comparison testing.
Expected outcome: The failure is isolated to the profile, acquisition monitor, Canvas display, network connection, bed location, or broader system.
If multiple systems are affected, notify the monitoring, integration, or network support team rather than repeatedly restarting individual devices.
9. Attempt a Controlled Profile Reload
Using only normal operator-accessible controls:
- Exit the current configuration screen.
- Return to the approved profile-selection area.
- Select a known valid profile.
- Allow sufficient time for the configuration to load.
- Observe for error messages, freezing, partial loading, or a return to defaults.
Avoid repeatedly switching profiles or saving changes during a failed loading process.
Expected outcome: A valid profile loads completely and remains stable.
If the profile loads, verify alarm limits, patient category, enabled parameters, display pages, and patient identification before stopping.
10. Perform a Controlled Restart
Confirm the device is removed from patient use and that restarting will not interrupt active monitoring or networked patient data.
Use the normal shutdown process. Allow the system to shut down completely before restoring power.
After restart:
- Observe the complete startup sequence.
- Record any errors or unusually long loading periods.
- Confirm communication with connected monitoring components.
- Attempt to load a known valid profile.
- Verify that the selected settings remain stable.
Do not repeatedly cycle power if the system freezes, restarts unexpectedly, or consistently fails at the same point.
Expected outcome: The system completes startup and loads an approved configuration normally.
If a controlled restart resolves the issue, complete a functional inspection and verify all safety-critical alarm settings before returning the monitor to service.
11. Check for Unsaved or Unauthorized Configuration Changes
Ask whether the issue began after:
- A software update
- Configuration deployment
- Unit relocation
- Network maintenance
- Profile editing
- Monitor replacement
- CARESCAPE ONE replacement
- Integration or central-station work
Determine whether the requested settings were formally saved and distributed through the facility’s approved configuration process.
Do not attempt to rebuild institutional profiles from memory or copy settings without authorization. Incorrect profiles may create inappropriate alarm limits, patient categories, or parameter behavior.
Expected outcome: Configuration history identifies whether the issue followed an authorized system change.
If the issue began after a deployment or update, preserve the displayed error information and escalate to the system administrator or GE HealthCare support.
12. Verify Operation Before Return to Service
After the profile loads successfully, confirm:
- Correct patient category
- Correct patient and bed association
- Expected waveform layout
- Required parameters are available
- Alarm limits are appropriate
- Alarm volume and visual indicators function
- Settings remain after navigating between screens
- Network communication remains stable
- No configuration or communication messages return
Perform testing according to facility policy using approved simulators or test equipment when applicable.
Expected outcome: The intended configuration loads completely, remains stable, and supports safe clinical monitoring.
Do not return the system to service if settings are incomplete, incorrect, unstable, or cannot be independently verified.
If the Problem Persists
If the patient association, workflow, available profiles, external connections, network path, CARESCAPE ONE connection, profile selection, and controlled restart have been checked, common external causes have been ruled out.
The problem may involve:
- Corrupted or missing configuration data
- Software instability
- Internal storage failure
- Canvas-to-CARESCAPE ONE communication failure
- Network configuration or server communication
- Failed configuration deployment
- Access-control or licensing problems
The system should be:
- Removed from service
- Labeled Out of Service
- Sent for bench evaluation or authorized repair
- Escalated to the facility monitoring-system administrator, network team, or GE HealthCare support as appropriate
Preserve error messages, timestamps, affected profile names, software information, and the sequence that reproduces the failure.
Do not perform repeated restarts, unauthorized software reloads, configuration restores, or internal disassembly.
Knowing when to stop and escalate is proper troubleshooting.
Clinical Use Tip
Never assume that displayed defaults match the intended clinical profile. After any loading failure, clinicians must verify the patient category, parameters, alarm limits, and alarm behavior before use.
Do not troubleshoot on an active patient. Move the patient to a verified backup monitoring device first so therapy and monitoring continuity are maintained.
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 would not load the adult ICU patient profile and returned to the default display configuration."
Cause
What was observed during troubleshooting.
Example:
"The CARESCAPE ONE connection was not fully seated, preventing the Canvas system from completing communication and loading the assigned profile."
Resolution
What action was taken.
Example:
"Removed the system from patient use, reseated the external CARESCAPE ONE connection, restarted the system, loaded the approved ICU profile, and verified patient category, parameters, alarm limits, waveforms, and network communication."
Helpful Details to Include (If Known)
- Patient safely transferred before troubleshooting
- Exact profile or configuration affected
- Patient, bed, and care-area association verified
- Patient category displayed
- Admission, discharge, or transfer status checked
- CARESCAPE ONE connection inspected
- Network cable and wall connection checked
- Network or communication indicators observed
- Known-good cable or network port tested
- Comparison system tested
- Error messages recorded exactly
- Time and frequency of failure documented
- Controlled restart performed
- Recent update or configuration deployment identified
- Alarm limits and alarm operation verified
- Accessories swapped or external connections reseated
- Power behavior during startup and restart
- Environmental factors or recent equipment relocation
- Indicator lights and communication symbols observed
- Final device status documented
Final Thought
Configuration failures are safety concerns because incorrect patient categories, alarm limits, or parameter settings may appear valid. Protect the patient first, isolate external causes logically, verify every restored setting, and escalate persistent failures with detailed CCR documentation.
That is successful troubleshooting.