Patient monitoring systems · Carescape family

GE Healthcare Carescape Gateway: troubleshooting and error codes

The ServiceForge knowledge base holds 97 documented symptoms for the GE Healthcare Carescape Gateway, with 174 ranked causes, 104 diagnostic checks with test points and expected values, and 42 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI

Symptoms

ADT query fails - service unavailable patient safety

ADT query fails some or all of the time due to service or licensing issues

Ranked causes

1. Multiple ADT service providers (occasional)
2. No ADT licenses available or license count is zero (common)
3. ADT service is disabled (common)
4. License file may have been deleted (occasional)
5. License key may be invalid (occasional)

First check

Verify only one ADT service provider

Test point: CIC Pro center query or Webmin ADT service configuration
Expected: Only one ADT service provider offering service

1 more check with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cannot connect to Webmin

Remote computer cannot establish connection to CARESCAPE Gateway Webmin web interface.

Ranked causes

1. Internet Explorer proxy server settings incorrect (common)
2. Incorrect network settings on remote computer (common)
3. Remote computer on wrong network (MC or S/5) (occasional)
4. Network problems on Gateway (occasional)
5. Problem with CARESCAPE Gateway (occasional)

First check

Verify Internet Explorer proxy server settings

Test point: Internet Explorer proxy settings dialog
Expected: Proxy settings configured per network administrator requirements

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

HSDI outbound waveform and numeric data not sent to all beds

Client not receiving real-time numeric and waveform data for one or more beds on the system

Ranked causes

1. CARESCAPE Gateway to client network is down (common)
2. Client is down or not operational (common)
3. No High Speed Data Interface Client Connection Count licenses available (occasional)
4. Too many clients are connected (occasional)
5. Reserved client connections have wrong IP address (rare)

First check

Verify network connectivity

Test point: CARESCAPE Gateway to client network
Expected: Network functioning and connected

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Incorrect patient data at monitor patient safety

Patient data ADT workflow mapping error or missing ADT events

Ranked causes

1. Incorrect ADT workflow setting (common)
2. Missing ADT^A02 transfer event (occasional)
3. ADT^A08 update re-admits patient when should just update (occasional)
4. Missing ADT^A02 transfer, new transfer to non-vacated bed (rare)
5. Missing ADT^A03 discharge, new transfer to non-vacated bed (rare)

First check

Verify ADT workflow mapping

Test point: Webmin Configuration > ADT workflow configuration
Expected: ADT workflow set to current customer customization

5 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

No numeric and waveform data collected from admitted bed

Bed is admitted but not sending numeric or waveform data; bed offline or not on network

Ranked causes

1. Bed was never admitted from the monitor (common)
2. Bed does not exist on the network (common)
3. Network problems or monitor communication issues (common)
4. Bed was never added to filter list via Webmin (occasional)
5. Bed is not supported by CARESCAPE Gateway (rare)

First check

Check device compatibility

Test point: Appendix C device list
Expected: Bed model listed as supported

3 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

VOD client fails to connect to CARESCAPE Gateway

VOD client application unable to establish connection to CARESCAPE Gateway system

Ranked causes

1. Ping from VOD client to CARESCAPE Gateway fails (common)
2. Incorrect network setup with invalid IP configurations (common)
3. Ping succeeds but Cloverleaf/VOD not configured for correct ports (occasional)
4. Firewall on VOD client host blocking traffic on VOD port (occasional)
5. CARESCAPE Gateway firewall incorrectly configured blocking incoming VOD connections (occasional)

First check

Test network connectivity with ping

Test point: VOD client host to CARESCAPE Gateway
Expected: Ping response successful

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway does not send VOD response message

VOD client connects and sends requests but receives no response messages from system

Ranked causes

1. VOD request and response queues backed up with messages (occasional)
2. Cloverleaf not configured properly or has become corrupt (occasional)
3. VOD request message not well-formed HL7 or improper query type (occasional)
4. Cloverleaf recovery database purge delayed request (rare)

First check

Monitor VOD queue status

Test point: Cloverleaf queue monitoring
Expected: Request and response queues not backed up

1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway responds with VOD error message

VOD client receives error response instead of valid data; various error messages indicate specific issues

Ranked causes

1. VOD request message not formatted properly (occasional)
2. Requested device name or session not found (common)
3. Device found but data not available from monitor (occasional)
4. VOD feature not licensed (rare)

First check

Verify device in bed list and admitted

Test point: CARESCAPE Gateway bedlist configuration
Expected: Device online and in Admitted state

1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

No data collected from admitted bed patient safety

CARESCAPE Gateway is not collecting data from a bed that has been admitted

Ranked causes

1. Bed was never admitted from the monitor (common)
2. Bed does not exist on network or network problems (occasional)
3. Bed not supported by CARESCAPE Gateway or does not offer trends (occasional)
4. Bed not added to filter list via Webmin (occasional)

First check

Verify device compatibility

Test point: Device specifications against Appendix C
Expected: Bed model supported by CARESCAPE Gateway

1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Total network connection failure

CARESCAPE Gateway cannot communicate on any network interface; no connectivity to remote computers or services.

Ranked causes

1. Swapped or loose network cables (common)
2. Network LEDs indicating no connection (common)
3. Internet Explorer cookies disabled (occasional)
4. Failed Network Interface Card (NIC) (occasional)

First check

Verify network cable connections are secure and not swapped

Test point: RJ-45 Ethernet connectors for MC Network, IX Network, S/5 Network, iLO
Expected: All cables firmly seated in correct ports

1 more check with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

ADT request times out with no error message

Query times out and returns no matching patient records, no error displayed

Ranked causes

1. CCG Patient Data Cache and/or PostgreSQL Database services not running (common)
2. CCG_PROD not running in cloverleaf (occasional)
3. Permission errors in CCG_prod site log (occasional)

First check

Verify service status

Test point: System Manager Webmin page
Expected: CCG Patient Data Cache and PostgreSQL Database services running

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cannot add beds to bed list

Unable to add beds to the configured bed list

Ranked causes

1. No licenses available or available license count is zero (common)
2. License file may have been deleted (occasional)
3. License key may be invalid (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

HL7 outbound not being sent to HIS

HL7 messages are not reaching the HIS system

Ranked causes

1. HIS software upgrade not compatible with Cloverleaf setup (occasional)
2. HIS is down or not operational (common)
3. Cloverleaf response times greater than 40 seconds (occasional)

3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

License key cannot be added via Webmin

Operation fails with message stating key was not able to be added, it is invalid in the given context

Ranked causes

1. License key may be invalid (common)
2. Access denied or CARESCAPE Gateway lacks license file access (occasional)
3. License bed count lower than current bed list (occasional)

First check

Verify license key was entered correctly

Test point: Webmin license entry field
Expected: License key matches shipped documentation

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Loss of HL7 inbound/outbound data

System may be in continuous reboot cycle; no HL7 messages flowing in or out

Ranked causes

1. License keys became invalid (occasional)
2. Disconnected CARESCAPE Network IX or MC interface cable (common)
3. Bad IP address configuration (occasional)

First check

Inspect network cables

Test point: CARESCAPE Network IX or MC interface
Expected: Cables connected and undamaged

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Network connectivity lost or degraded

System cannot communicate on network; connectivity LEDs off or not showing activity; network applications unavailable

Ranked causes

1. Network cable disconnected or improperly connected (common)
2. Network interface card failure or malfunction (occasional)
3. Network switch or infrastructure issue (occasional)

First check

Inspect network cable connections at back panel

Test point: All RJ-45 ports on CARESCAPE Gateway rear panel
Expected: All cables fully inserted with click engagement; no loose connectors

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Patient record cannot be found patient safety

ADT HL7 inbound data not being stored in Patient data cache

Ranked causes

1. Required services not running (Cloverleaf, Cache, PostgreSQL) (common)
2. Cloverleaf processes not running (common)
3. ADT message translation failures (occasional)

First check

Verify Cloverleaf Engine is running

Test point: System Manager Webmin module
Expected: Cloverleaf Engine service status: running

4 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Power is not supplied to system high voltage

System does not power on; no lights visible on front panel; system is unresponsive

Ranked causes

1. Power cord not plugged in or loose connection (common)
2. Wall outlet is not functional (occasional)
3. UPS device malfunction or power failure (occasional)

First check

Verify power cord is fully connected to wall outlet and CARESCAPE Gateway

Test point: Power cord inlet and wall outlet
Expected: Power cord firmly seated at both ends; no visible gaps or loose connections

2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Suspected CARESCAPE Network IX problem

CARESCAPE Network IX port is unresponsive to ping or network communication from remote computers.

Ranked causes

1. Network configuration incorrect on Gateway or hospital switch (common)
2. Failed Network Interface Card (NIC) (occasional)
3. Network IX port or cable defective (occasional)

First check

Ping CARESCAPE Network IX port from remote computer

Test point: CARESCAPE Gateway CARESCAPE Network IX IP address
Expected: Successful ping response from Gateway

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Suspected CARESCAPE Network MC problem

CARESCAPE Network MC port is unresponsive to ping or network communication from remote computers.

Ranked causes

1. Network configuration incorrect on Gateway or hospital switch (common)
2. Failed Network Interface Card (NIC) (occasional)
3. Network MC port or cable defective (occasional)

First check

Ping CARESCAPE Network MC port from remote computer

Test point: CARESCAPE Gateway CARESCAPE Network MC IP address
Expected: Successful ping response from Gateway

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Suspected S/5 Network problem

S/5 Network port is unresponsive to ping or network communication from remote computers.

Ranked causes

1. Network configuration incorrect on Gateway or hospital switch (common)
2. Failed Network Interface Card (NIC) (occasional)
3. S/5 Network port or cable defective (occasional)

First check

Ping S/5 Network port from remote computer

Test point: S/5 Network IP address
Expected: Successful ping response from Gateway

1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unit does not boot

CARESCAPE Gateway fails to start up or enter operational mode after power application.

Ranked causes

1. Loose or disconnected cables and connectors (common)
2. Incorrect BIOS boot order configuration (occasional)
3. Hardware failure detected by diagnostics (occasional)

First check

Verify power connection and cable seating

Test point: Power connector and all component connections
Expected: All cables properly connected and seated

2 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Account number not correct in HL7 outbound message

Account number reconciliation not populating account number in HL7 outbound message

Ranked causes

1. Domain field does not match ADT inbound feed from HIS (common)
2. Integrated ADT data feature is disabled (occasional)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Account number not in HL7 outbound message

HL7 outbound messages missing correct account number; field not populated properly

Ranked causes

1. Account number reconciliation not populating field (occasional)
2. Domain field does not match ADT inbound feed (common)

First check

Compare CARESCAPE Gateway domain with HIS ADT feed

Test point: CARESCAPE Gateway configuration vs HIS system
Expected: Domain values match

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

ADT information has incorrect PID patient safety

ADT data received with wrong patient ID from domain or typecode mismatch

Ranked causes

1. Incorrect Cloverleaf configuration for domain and patient ID typecode (common)
2. Incorrect CARESCAPE Gateway domain or patient ID typecode (common)

First check

Compare CARESCAPE Gateway domain setting

Test point: Properties configuration page 7-20
Expected: Domain matches Cloverleaf translation

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Bed not appearing in collection filter list via Webmin

Bed does not appear in collection/filter list when viewed via Webmin

Ranked causes

1. Device not compatible or does not offer trends (occasional)
2. Bed disconnected from network (common)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Bed not appearing in collection/filter list

Bed does not appear in Webmin bed list or filter list even though bed is on network

Ranked causes

1. Bed may be disconnected from network (common)
2. Bed may not be supported by CARESCAPE Gateway (occasional)

First check

Verify bed is supported model

Test point: Appendix C compatibility list
Expected: Bed model listed as compatible

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Bed offline in CARESCAPE Gateway

Bed appears in Webmin bed list but shows as Offline; not communicating with system

Ranked causes

1. Bed may be disconnected from network (common)
2. Bed may not be supported by CARESCAPE Gateway (rare)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway does not adjust from NTP server

No time adjustment being made from NTP server

Ranked causes

1. NTP Server not properly configured (common)
2. Time Master properties not configured correctly (occasional)

First check

Enter NTP server network address in Webmin

Test point: Configuration > System Time > NTPD Settings
Expected: Network address of valid NTP server

3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway Service communication failure with bed/monitor

Multiple communication errors logged including socket timeouts, failed responses, device offline messages when trying to poll beds/monitors for trend data

Ranked causes

1. Monitor removed from network or patient discharged (common)
2. Network communication problems or connectivity issue (occasional)

First check

Review log messages for communication pattern

Test point: CSG.log file
Expected: Brief errors on monitor disconnect; errors stop when monitor reconnects

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

HIS does not acknowledge HL7 message

HIS system not acknowledging HL7 outbound messages

Ranked causes

1. HIS software upgrade incompatible with Cloverleaf setup (occasional)
2. HIS is down or not operational (common)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

No matching patient found when querying by location patient safety

Query by Unit or Unit and Bed from central station or monitor returns no results

Ranked causes

1. Multiple ADT service providers active (occasional)
2. ADT HL7 inbound data not in Patient data cache (occasional)

First check

Determine if multiple ADT providers offering service

Test point: CIC Pro Clinical Information Center
Expected: Only one ADT service provider (CARESCAPE Gateway, MUSE Gateway, or Aware Gateway)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Not sending HL7 from some beds

Selected beds are not transmitting HL7 data

Ranked causes

1. Beds no longer on bed list (common)
2. HL7 license key file is missing or corrupt (occasional)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Not sending numeric and waveform data from some beds

Numeric and waveform data collection failing for beds that were previously on bed list; offline status

Ranked causes

1. Beds are no longer on the bed list (occasional)
2. HL7 license key file is missing or corrupt (occasional)

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Performance degrades over time

Cloverleaf system performance degradation observed over extended operation

Ranked causes

1. HL7 outbound messages backing up at inter-process communication ports (common)
2. Excessive translations, data manipulations, or procedural calls (occasional)

First check

Monitor CARESCAPE Gateway service queue

Test point: Webmin > Configuration > CARESCAPE Gateway Configuration > Dashboard HL7/Cloverleaf section
Expected: Message queue not building up

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

System health indicator shows critical or degraded status

Red or amber Health LED illuminated on front panel; system status page shows fault conditions

Ranked causes

1. Hardware fault detected by monitoring system (unknown)
2. iLO management system detecting component failure (unknown)

First check

Observe front panel Health LED color

Test point: Health LED on front panel
Expected: Green indicates system health is normal

1 more check with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI

Too many records returned from ADT query

Querying by last name or unit name only returns more records than desired

Ranked causes

1. Many patient records in database (common)
2. Old patient records in database not cleaned (occasional)

First check

Evaluate query specificity

Test point: Query input fields
Expected: Last name AND first name or unit AND bed specified

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Unable to request ADT data - no data server present patient safety

Message displayed at monitoring device indicates no data server

Ranked causes

1. Invalid or corrupt ADT license (common)
2. CARESCAPE Network MC misconfigured or network connectivity lost (occasional)

First check

Verify ADT license is valid and current

Test point: Webmin License screen, ADT license configuration page 7-28
Expected: Valid ADT license for current MAC address present and active

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Webmin properties page displays Serious Error

Properties page malfunctions showing Serious Error and referring to log files

Ranked causes

1. ugsUser.properties file size is zero (common)
2. Restore configuration defaults (occasional)

First check

Check ugsUser.properties file size

Test point: /usr/gehc/csg/resources/ugsUser.properties
Expected: File size > 0 bytes

3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Administrator login to iLO password not accepted

iLO authentication fails for administrator account despite correct password entry.

Ranked causes

1. iLO password corrupted or needs reset (occasional)

First check

Reset iLO password through Webmin

Test point: Webmin Lights-Out Management interface
Expected: Password reset successfully; administrator login accepted

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

ADT functionality disabled due to missing or invalid license

ADT service turned off when no valid license key available

Ranked causes

1. No valid ADT license key configured (common)

First check

Verify ADT license in Webmin

Test point: Webmin Configuration > License section
Expected: Valid ADT license key present

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

ADT information has default PID patient safety

No matching domain or patient ID typecode found in ADT Query Response

Ranked causes

1. No matching domain or patient ID typecode in response (occasional)

ADT query returns data with question mark characters

Data returned contains question mark characters in place of expected values

Ranked causes

1. Non-ASCII character in patient data in database cannot map (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

ADT query returns intermittent unit/bed not found error

Some messages returned indicate unit or bed not found intermittently

Ranked causes

1. More than one ADT service provider (common)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Advanced iLO does not work

Advanced iLO functionality unavailable after factory default reset or battery replacement with server unplugged.

Ranked causes

1. iLO reset to factory defaults or lost power during battery replacement (occasional)

First check

Restart or reset iLO functionality

Test point: Webmin Lights-Out Management interface
Expected: iLO restarted or reset; advanced features available

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

All Cloverleaf threads stopped

All threads are in stopped state, system requires manual intervention to restart processes

Ranked causes

1. Threads stopped for unknown reason (unknown)

First check

Verify thread status in Interface Monitor

Test point: Interface Monitor
Expected: All threads running

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Applications or subsystems not running patient safety

CARESCAPE Gateway applications show status Off; services not responding; system appears to be running but no patient monitoring or data available

Ranked causes

1. Application services stopped or disabled (common)

First check

Verify all CARESCAPE applications show status On in Webmin

Test point: Webmin Start/Stop CARESCAPE Gateway page
Expected: All required applications and subsystems showing status On

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Applications will not start

Attempts to start Cloverleaf Engine fail

Ranked causes

1. /var or /tmp are full (common)

First check

Check disk space on /var and /tmp

Test point: /var, /tmp filesystems
Expected: Less than 100% full
Tools: df command

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Bed offline; CARESCAPE Gateway not detecting patient safety

Bed appears in collection list via Webmin but is noted as Offline

Ranked causes

1. Device not compatible or does not offer trends (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cannot connect to iLO, Webmin or VNC

Remote management interfaces (iLO, Webmin, VNC) are not accessible from remote computer or KVM.

Ranked causes

1. iLO network configuration not set up (common)

First check

Local iLO configuration via keyboard and monitor

Test point: iLO setup during system boot
Expected: iLO network settings configured and saved

2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI

Cannot resend failed message via Configuration Network Monitor

Error displayed when attempting to resend failed message; cannot retrieve process name for CCG_Inbound

Ranked causes

1. Communication problem between service interface and Cloverleaf (occasional)

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway application will not start

System Manager page shows CARESCAPE Gateway application as stopped and multiple restart attempts have failed

Ranked causes

1. Corrupt configuration file (common)

First check

Verify application configuration integrity

Test point: CARESCAPE Gateway configuration files
Expected: Valid configuration present and readable

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway not sending network data

System configuration reviewed and correct, services restarted but data not transmitted

Ranked causes

1. Firewall or router blocking network connections (common)

First check

Restart CARESCAPE Gateway firewall

Test point: Configuration > System Manager in Webmin
Expected: Firewall service restarted

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway OS time wrong

Service disabled or time outside 8 hour maximum adjustment window

Ranked causes

1. Service disabled or time outside 8 hour window (occasional)

First check

Verify time difference from NTP is within 8 hours

Test point: System clock vs NTP server time
Expected: Time difference less than 8 hours

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway Service exit with code 20

Service shuts down unable to establish TCP connections to Enterprise Gateway

Ranked causes

1. Enterprise Gateway system down or unreachable (common)

First check

Verify Enterprise Gateway TCP connectivity

Test point: Network connectivity to EG IP address and port
Expected: TCP connection successful on expected port

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway Service exit with code 30

Service shuts down unable to establish TCP connections to Cloverleaf

Ranked causes

1. Cloverleaf system down or unreachable (common)

First check

Verify Cloverleaf TCP connectivity

Test point: Network connectivity to Cloverleaf IP address and port
Expected: TCP connections established; default is 20 connections

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway Service exit with code 50

Service shuts down due to Cloverleaf being in indeterminate state and unable to communicate

Ranked causes

1. Cloverleaf internal error or crash (occasional)

First check

Monitor Cloverleaf connection status

Test point: CSG.log Cloverleaf Connection messages
Expected: Cloverleaf Connection xx created messages appear for all expected connections

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway service not running

Configuration link in Webmin module returns 'Failed to connect to 127.0.0.1:9093: Connection refused'

Ranked causes

1. CARESCAPE Gateway service stopped (common)

First check

Verify CARESCAPE Gateway service status

Test point: Webmin service management
Expected: Service running and responding on 127.0.0.1:9093

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway Service shutdown due to command queue overflow

Service exits with code 60 when internal queue depth exceeds maximum allowed commands

Ranked causes

1. Cloverleaf slow or unable to process HL7 messages (common)

First check

Monitor command queue depth in logs

Test point: CSG.log Total queue depth message
Expected: Queue depth below maximum allowed commands threshold

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

CARESCAPE Gateway time set incorrectly

Monitor time wrong, time service not running

Ranked causes

1. Time Master properties configured incorrectly (common)

First check

Verify Time Master Properties in Webmin

Test point: Configuration > CARESCAPE Gateway Configuration > Setup > Properties
Expected: All Time Master settings correct per configuration document

1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI

More symptoms

CARESCAPE Network device clocks fluctuate between times
Cloverleaf IDE becomes unresponsive
Cloverleaf IDE unable to launch separate process
Cloverleaf interface threads not restarting
Cloverleaf Monitor daemon restarts automatically
Cloverleaf response times exceed 40 seconds
Desktop GUI cannot perform all functions
Duplicate UNIT|BED name detected on network
HL7 Outbound data not being sent to HIS
HL7 outbound HIS connection failure after HIS restart
HSDI outbound numeric data not sent to all beds
HSDI outbound waveform data not sent to all beds
Incorrect time propagated to network
Interface Monitor/Management unavailable
Internal database vista error recovery
Internal thread errors in down state
Invalid license key in license file
Left mouse click does not work in VNC
Logging has stopped
Monitor time wrong after daylight savings
No time update from CARESCAPE Network master
No time update from NTP server
One or few Cloverleaf threads stopped
Patient data with HIS mapping causing wrong location query
Patient record lookup in ADT database fails
PCD-01 HL7 trend messages missing EEG site information
Response is not in requested HL7 version
Some beds not being collected in real time
Some beds not collected in real time
Statistics subsystem unable to record performance data
Threads and processes in down state refuse to start
Time at CARESCAPE Gateway does not match network time
Translation or database error on ADT admit event
Trended data not showing after HIS mapping update
Trended PA values not being delivered
Unit name lookup in ADT database fails
Unsupported combination of patient query fields

37 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI

Error codes

Code	Meaning	Trigger	Severity
`ADT-Communication-Error-CSG-PDC`	The CSG application is not communicating with Patient Data Cache (PDC), resulting in an ADT failure	CSG application loses communication with PDC	error
`ADT-Communication-Recovered-CSG-PDC`	The CSG application starts communicating with the Patient Data Cache (PDC), having recovered from the previous failed state	CSG application resumes communication with PDC	info
`Cannot process ADT request`	ADT service disabled due to missing or invalid license key	ADT data request received when ADT license not available or invalid	warning
`CIS-Connection-Error`	The system shall notify when the Clinical Information System has been disconnected for 20 minutes unexpectedly	CIS disconnects for 20 minutes	warning
`Cloverleaf License Issue`	Cloverleaf license not valid or not installed	System startup or runtime when Cloverleaf module is accessed	warning
`cpqDa6LogDrvStatusChange`	Logical drive status changes	Logical drive status changes	error
`cpqDa7PhyDrvStatusChange`	Physical drive status changes	Physical drive status changes	error
`cpqHe3FltTolFanDegraded`	Fan degraded	Fan performance degrades	warning
`cpqHe3FltTolFanFailed`	Fan failed	Fan fails	warning
`cpqHe3FltTolPowerRedundancyLost`	Power redundancy lost	Power redundancy fails	warning
`cpqHe3FltTolPowerRedundancyRestored`	Power supply redundancy is restored	Power redundancy restored after loss	info
`cpqHe3FltTolPowerSupplyInserted`	Power supply inserted	Power supply inserted into system	info
`cpqHe3FltTolPowerSupplyRemoved`	Power supply removed	Power supply removed from system	warning
`cpqHe3ThermalCpuFanFailed`	CPU fan failed	CPU fan fails	error
`cpqHe3ThermalCpuFanOk`	CPU fan transitions from failed to OK	CPU fan recovers from failed state	info
`cpqHe3ThermalSystemFanDegraded`	System fan degraded	System fan performance degrades	warning
`cpqHe3ThermalSystemFanFailed`	System fan failed	System fan fails	warning
`cpqHe3ThermalSystemFanOk`	System fan transitions from failed to OK	System fan recovers from failed state	info
`cpqHe4FltTolPowerSupplyACpowerloss`	Power supply AC power loss	AC power input is lost	warning
`cpqHe4FltTolPowerSupplyDegraded`	Power supply degraded	Power supply performance degrades	warning
`cpqHe4FltTolPowerSupplyFailed`	Power supply failed	Power supply fails	warning
`cpqHe4FltTolPowerSupplyOk`	Power supply transitions from failed to OK	Power supply recovers from failed state	info
`cpqHo2GenericTrap`	Generic trap	Hardware fault condition detected	info
`cpqHo2NicStatusFailed`	NIC has failed	Network interface card fails	error
`cpqHo2NicStatusOk`	NIC status transitions from failed to OK	NIC recovers from failed state	info
`cpqNic3ConnectivityLost`	Network interface has lost connectivity	Network connectivity is lost	error
`cpqNic3ConnectivityRestored`	Network connectivity restored	Network connectivity restored after loss	info
`cpqNic3RedundancyIncreased`	Ethernet interface team's redundancy restored	Ethernet interface redundancy restored	info
`cpqNic3RedundancyReduced`	Ethernet interface team loses redundancy	Ethernet interface redundancy fails	warning
`Critical-Process-Restart-Threshold`	Watchdog fails to restart a process	Watchdog unable to restart critical process	error
`Duplicate UNIT\|BED detected`	Another device with same unit/bed name found on network	CARESCAPE Gateway discovers duplicate unit\|bed identifier during device scanning	warning
`Exit Code 20`	Unable to make TCP socket connections to Enterprise Gateway (EG down)	CARESCAPE Gateway cannot establish TCP connection to Enterprise Gateway system at startup or runtime	critical
`Exit Code 30`	Unable to make TCP socket connections to Cloverleaf (Cloverleaf down)	CARESCAPE Gateway cannot establish TCP connections to Cloverleaf system at startup or runtime	critical
`Exit Code 50`	Cloverleaf in indeterminate state unable to communicate with CARESCAPE Gateway Service (Cloverleaf down)	CARESCAPE Gateway detects Cloverleaf communication failure indicating system crash or internal error	critical
`Exit Code 60`	CARESCAPE Gateway collecting trend data faster than can be sent to Cloverleaf (Cloverleaf down or slow)	Internal command queue depth exceeds predefined maximum threshold	critical
`HL7/ADT License Issue`	HL7 or ADT license not valid or not installed	System startup or runtime when HL7/ADT module is accessed	warning
`HL7-Communication-Error-CSG-Cloverleaf`	The CSG application is not communicating with Cloverleaf, resulting in an HL7 failure	CSG application loses communication with Cloverleaf	error
`HL7-Communication-Recovered-CSG-Cloverleaf`	The CSG application starts communicating with Cloverleaf, having recovered from the previous failed state	CSG application resumes communication with Cloverleaf	info
`HSDI-Client-Connection-Error`	A client unexpectedly disconnected from the High Speed Data Interface (HDSI)	Client disconnects from HDSI	warning
`INVALID license key`	License keys in licensefile.txt do not match MAC address in macaddress.txt	CARESCAPE Gateway starts and validates license keys against stored MAC address	critical
`Time-Out-of-Sync-Recovered`	The time update to the time master has recovered after a previous error	Time synchronization restored after failure	info
`Time-Out-of-Sync-Threshold`	The system is unable to update the time master's time for an hour	Time synchronization fails for one hour	warning

Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI

Community

0 fixes logged by technicians through their AI, with outcomes, for this model.

ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.