GE Carescape Gateway

GE Healthcare
CARESCAPE™ Gateway
Technical Manual
Software version 1
HP ProLiant DL 360 G7
CARESCAPE™ Gateway
English
2052438-002 (cd)
2052437-002B (paper)
© 2011 General Electric Company.
All rights reserved.
NOTE
Due to continuing product innovation, specifications in this manual are subject to change without notice.
NOTE
For technical documentation purposes, the abbreviation GE is used for the legal entity name, GE Medical Systems
Information Technologies, Inc.
Listed below are GE Medical Systems Information Technologies, Inc., trademarks used in this manual. All other trademarks
contained herein are the property of their respective owners.
DASH, EAGLE, SOLAR, APEXPRO, are trademarks of GE Medical Systems Information Technologies, Inc., registered in
the United States Patent and Trademark Office.
CIC PRO is a trademark of GE Medical Systems Information Technologies, Inc.
CARESCAPE is a trademark of GE Healthcare.
T-2 CARESCAPE™ Gateway 2052436-002B

16 September 2011
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Manual information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Illustrations and names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Common equipment terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Manufacturer’s responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Equipment information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Equipment symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Service requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Equipment identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
2 Equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

CARESCAPE Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
CARESCAPE Gateway connection diagram . . . . . . . . . . . . . . . . . . . . . . . 2-2
Secure data link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
CARESCAPE Network IX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
CARESCAPE Network MC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Hospital enterprise network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Network connections/back panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Integrated lights-out (iLO) connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Theory of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

CARESCAPE Gateway functional description . . . . . . . . . . . . . . . . . . . . . 2-4
Multiple CARESCAPE Gateway systems on network . . . . . . . . . . . . . . . . 2-4
Transport modes and back-collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
CARESCAPE Gateway logical structure . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
CARESCAPE Gateway function description. . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Trended vital signs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Trended data (ORU) outbound overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Vitals on demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
ADT inbound. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
NTP time synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2052436-002B CARESCAPE™ Gateway i

High speed data interface (HSDI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Service utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Utility/diagnostic tool use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Service logons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
iLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Remote desktop utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
General information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Required training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Pre-installation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Pre-installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Obtain required installation tools/equipment . . . . . . . . . . . . . . . . . . . . . . . 3-7
Install the CARESCAPE Gateway server on the rack/shelf . . . . . . . . . . . 3-7
Network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Powering on the CARESCAPE Gateway . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Service laptop connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
CARESCAPE Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

iLO IP address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
CARESCAPE Network MC, IX and S/5 Network configuration . . . . . . . . 3-14
System time/date configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
NTP server computer IP address configuration . . . . . . . . . . . . . . . . . . . . 3-17
InSite Exc configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Password configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Error notification configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Cloverleaf license configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
HIS IP address/port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Check CARESCAPE Gateway status . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Configure bed list, HIS mappings, and properties . . . . . . . . . . . . . . . . . . 3-24
HL7 outbound configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Initial backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Backup CARESCAPE Gateway application settings . . . . . . . . . . . . . . . . 3-24
Backup Cloverleaf interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Cloverleaf thread startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Manufacturer recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Manufacturer responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Spilled fluids hazard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
ii CARESCAPE™ Gateway 2052436-002B

Controlling electrostatic discharge damage . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Remove power from the CARESCAPE Gateway . . . . . . . . . . . . . . . . . . . 4-4
Internal components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Fans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Ventilation ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Reconnect power to the CARESCAPE Gateway . . . . . . . . . . . . . . . . . . . 4-5
Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

About the checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Check for valid network connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Maintenance checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
HP system management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
System management homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
System availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
General fault isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
LED status indicator description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Front panel LED status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Back panel LED status indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Unit does not boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Cables and connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Network interface test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Troubleshooting network problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Cannot connect to Webmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Service tools connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Emergency CD/DVD eject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Internal component troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

SmartStart diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
2052436-002B CARESCAPE™ Gateway iii

ROM-based setup utility reset configuration . . . . . . . . . . . . . . . . . . . . . . . 5-15
Application troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

CARESCAPE Gateway troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
CARESCAPE Gateway time services troubleshooting . . . . . . . . . . . . . . 5-20
ADT troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
HL7 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Cloverleaf troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
HSDI troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Vitals on Demand troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
Cloverleaf database failure recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Event logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37

CARESCAPE Gateway log viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
CSG.log description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Webmin actions log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
Retrieving iLO log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
InSite notification events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
Database viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Open Database Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Query by patient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Query by location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
View the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
6 Field replaceable units (FRU) . . . . . . . . . . . . . . . . . . 6-1

Ordering parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
HP ProLiant DL360 G7 server FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Field replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Field replacement preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Hard drive replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
License keys and hardware MAC address . . . . . . . . . . . . . . . . . . . . . . . . 6-3
7 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
CARESCAPE Network MC/IX configuration . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
iLO management/configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
IP/netmask/(router/gateway) configuration . . . . . . . . . . . . . . . . . . . . . . . . 7-3
iLO password configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
iLO reset/reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
iLO license key activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
iLO SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Purge ADT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
iv CARESCAPE™ Gateway 2052436-002B

Backup and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Backup contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Restore factory defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Restore configuration backups/factory defaults . . . . . . . . . . . . . . . . . . . . . 7-9
Password management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
View server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
ADT workflow configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
CARESCAPE Network MC bed list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Add/Remove beds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Change collection intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
HIS mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
S/5 Network bed list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Update iCentral list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Add/Remove beds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Properties configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Time synchronization properties configuration . . . . . . . . . . . . . . . . . . . . 7-23
Display serial number information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Upload/download files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
License configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Cloverleaf license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
CARESCAPE Gateway license configuration . . . . . . . . . . . . . . . . . . . . . 7-28
Common Cloverleaf configuration changes . . . . . . . . . . . . . . . . . . . . . . . . 7-29

Launch the Cloverleaf engine IDE (integrated development environment) . 7-
29
ADT inbound domain/typecode configuration . . . . . . . . . . . . . . . . . . . . . 7-29
Data caching parameter configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Set up ADT feed forward . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Multiple CIS client support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Cloverleaf Webmin utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

Cloverleaf interface management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Cloverleaf interface backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Cloverleaf interface restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Cloverleaf license manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Interface monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
2052436-002B CARESCAPE™ Gateway v

Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
8 System fail recovery . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

System fail recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
A Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Scenario symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CARESCAPE Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Admit/Discharge/New Case scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Patient transport scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Patient transfer scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Combination Mode scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Third-Party acquisition device scenarios . . . . . . . . . . . . . . . . . . . . . . . . A-19
S/5 Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22

Admit/Discharge/New Case scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . A-22
Patient transfer scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24
B Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
C Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Device compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
D Technical specifications . . . . . . . . . . . . . . . . . . . . . . D-1

CARESCAPE Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Medical device compliance specifications . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Hardware compliance specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Physical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Default IP address settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
E Supported parameters . . . . . . . . . . . . . . . . . . . . . . . E-1

Supported parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
F Router supported services . . . . . . . . . . . . . . . . . . . . F-1

Router supported services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
vi CARESCAPE™ Gateway 2052436-002B

2052436-002B CARESCAPE™ Gateway vii
viii CARESCAPE™ Gateway 2052436-002B
1 Introduction
2052436-002B CARESCAPE™ Gateway 1-1

Introduction
Manual information
Intended audience
This manual is intended for service representatives and technical personnel with
experience servicing medical equipment who maintain, troubleshoot, or repair the
equipment.
Revision history
The part number and revision letter for this manual are at the bottom of each page.
The revision letter changes whenever the manual is revised.
Revision Comment
A Initial release.
B Updated for software changes.
Conventions
This manual uses the following styles to emphasize text or indicate action.
Style Definition
bold Indicates hardware items such as keys, labels, or text entered by the
user.
bold italic Indicates software terms such as menu items or screen text.
italic Indicates items for emphasis
+ Indicates keyboard keys to select simultaneously.
> Indicates menu options to select consecutively.
Illustrations and names

This manual uses illustrations as examples only. Illustrations in this manual may not
necessarily reflect all system settings, features, configurations, or displayed data.
Names of persons, institutions, and places and related information are fictitious; any
similarity to actual persons, entities, or places is purely coincidental.
Common equipment terms

This manual uses the following terms to simplify common equipment terms.
1-2 CARESCAPE™ Gateway 2052436-002B

Introduction
Item Description/Refers to
Acquisition device The device used to acquire patient parameters which

connects to the CARESCAPE Network MC (e.g., Dash/Solar
patient monitors, Telemetry transmitters, etc.) or S/5 Network.
Admit The admit option on the acquisition device or central station

has been selected.
ADT The Admit Discharge Transfer refers to the exchange of

patient demographic information.
Association Mode The Association Mode allows the connection of non GE

devices to a patient monitor, via a GE interface device, for
consolidated viewing and data transmission.
Back collection Trended data is retroactively transmitted to the HIS when

acquisition device returns on-line.
CARESCAPE Network The CARESCAPE Network is the network infrastructure

housing the GE patient monitoring devices.
Central station The CIC Pro Clinical Information Center or the iCentral.
CSG The CARESCAPE Gateway Service.
CIC Pro center The CIC Pro Clinical Information Center.
CIS The Clinical Information System.
Combo Mode The Combination Mode is utilizing telemetry transmitters to

acquire parameters that are displayed at the patient monitor.
Discharge The discharge option on the acquisition device or CIC Pro

center has been selected.
Episodics Episodic parameter numerics (e.g., NBP, cardiac calcs, and

pulmonary calcs) are retrieved every time episodic events are
recorded. If more than one episodic event occurs during the
same minute, the more recent episodic event overwrites the
older episodic event.
Episodic data is user or system generated.
HIS The Hospital Information System.
High speed interface The high speed interface provides a near real-time data feed
obtained from patient monitoring devices.
Hospital enterprise network The hospital's network that links together the HIS systems
and other hospital enterprise devices.
HSDI High speed data interface.
iLO The Integrated Lights-Out utility allows some remote

monitoring and control even if the server is not powered up.
IX Network The CARESCAPE Network IX (Information eXchange) is

used for non-real time data sharing and printer function.
MC Network The CARESCAPE Network MC (Mission Critical) network

connects GE patient monitoring devices and central station
devices.
Monitoring session The data gathered by an acquisition device from admit to

discharge.
MRN Medical Record Number.

Introduction
Item Description/Refers to
NTP Network Time Protocol.
On-line The acquisition device is connected (wired or wireless) to the

CARESCAPE Network MC.
Patient transfer The transfer from one acquisition device to another

acquisition device in either the same or different care areas.
Patient transport The transport from one location to another location on the
same acquisition device.
PDU Power distribution unit.
Periodics Periodic parameter numerics (e.g., heart rate) are retrieved at

one-minute resolution from the patient monitor and displayed
at one-minute resolution.
Periodic data is sampled every two seconds to yield 30

samples per minute. The displayed value is the median of the
30 samples taken in the one-minute time frame, regardless of
the interval setting. Odd number values are rounded down to
the nearest even number.
PID The patient's identification or medical record number.
S/5 Network The legacy Datex-Ohmeda network protocol.
Trended data Trended data is vital signs data that is collected from an
acquisition device (e.g., patient monitor, telemetry transmitter,
etc.).
Unity Network ID The Unity Network ID Connectivity Device.
UPS Uninterruptible power supply.
Vitals on demand The vitals on demand (VoD) feature provides a solicited HL7
interface that clinical information systems can use to obtain a
current snapshot of vital signs and patient demographic data
on the patient monitor.
VNC Virtual Network Computing.
VPN Virtual Private Network.
Webmin Webmin is an internet-based web application used for

CARESCAPE Gateway administration and service.
Ordering manuals
A paper copy of this manual will be provided upon request. Contact your local GE
representative and request the part number on the first page of the manual.
Related documentation
The CARESCAPE Gateway hardware is a development of the HP ProLiant DL360
Generation 7 server. Applicable HP documentation is shipped with the CARESCAPE
Gateway.

Introduction
Additionally, the latest associated HP documentation is also available by clicking the

HP Proliant Servers link on the HP server documentation webpage at:
http://docs.hp.com/en/hw.html.
Specific HP documentation referenced in this manual include:
 HP Integrated Lights-Out User Guide

 HP ProLiant Servers Troubleshooting Guide
 DL 360 Generation 7 (G7) Server specific:
 HP ProLiant DL360 G7 Server Maintenance and Service Guide
 HP ProLiant DL360 G7 Server User Guide
Information on interfacing with the CARESCAPE Gateway is provided in the
following reference manuals:
 CARESCAPE Gateway HL7 Reference Manual

 CARESCAPE Gateway High Speed Data Interface Reference Manual
Safety information
General
Also refer to related Hewlett-Packard safety information in the appropriate HP
manuals. See Related documentation on page 1-4.
Manufacturer’s responsibility
GE is responsible for the effects of safety, reliability, and performance only if:
 Assembly operations, extensions, readjustments, modifications, or repairs are

carried out by authorized service personnel.
 The electrical installation of the relevant room complies with the requirements of
the appropriate regulations.
 The equipment is used in accordance with the instructions for use.
Intended use
The CARESCAPE Gateway is a server that provides outbound data to systems that
are not components of the CARESCAPE Network MC or S5 network. The
CARESCAPE Gateway provides near real-time streaming data in an XML format for
vital sign data and waveforms from patient monitoring systems. The CARESCAPE
Gateway also provides outbound vital sign data in an HL7 format from patient
monitoring systems. The CARESCAPE Gateway provides ADT inbound information
to minimize incorrect data entry. CARESCAPE Gateway also relays time adjustments
from an NTP (Network Time Protocol) time source to the CARESCAPE Network
Time Master to synchronize the clocks on CARESCAPE Network devices.
The CARESCAPE Gateway is intended to electronically transfer data to and from

medical devices. However, it is not intended to control any monitoring functions of
the monitoring devices to which it connects, nor is it intended to be used in the

Introduction
monitoring of the patients connected to said devices. The server hardware itself
operates unattended and is not located near the patient or caregiver.
The CARESCAPE Gateway is a computer program that comes pre-installed on a

server supplied by GE Healthcare. The typical "user" is an information system or
application that resides outside of the monitoring network that needs this data (e.g., a
CIS system). The CARESCAPE Gateway has no clinical user interface; the only user-
interface is web-based and intended for administrators of the device.
Safety information
Safety message signal words
Safety message signal words designate the severity of a potential hazard.
DANGER indicates an imminently hazardous situation, which, if not avoided, will

result in death or serious injury.
WARNING indicates a potentially hazardous situation, which, if not avoided, could

result in death or serious injury.
CAUTION indicates a potentially hazardous situation, which, if not avoided, may

result in minor or moderate injury.
NOTE shall be used for informational messages that do not pertain to a hazard.
The order in which safety messages are presented in no way implies the order of
importance. The following safety messages apply to the device’s entire system. Safety
messages specific to parts of the system are found in the relevant section.
Danger safety messages

No danger safety messages apply to this system.
Warning safety messages

The following warning safety messages apply to this system.
WARNING
EXPLOSION HAZARD—Do not use this equipment in the
presence of flammable anesthetics, vapors or liquids.

Introduction
WARNING
INCORRECT CALCULATIONS— When a user of the monitoring
equipment retrieves patient information and associates it with the
patient being monitored, they should always confirm that the entered
patient's information is entered correctly. Regarding calculations
made by the monitoring equipment, this may include one or more of:
height, weight, sex, and date of birth. Hemodynamic and
oxygenation calculations are dependent on accurate patient height,
weight, sex and age values.
WARNING
INCORRECT ALGORITHMS, ARRHYTHMIA PROCESSING,
AND CALCULATIONS BASED ON PATIENT AGE —After
manually updating or automatically retrieving patient information
from a network database and associating it with the patient being
monitored, a user should always confirm that the entered patient’s
date of birth matches the patient’s actual date of birth. Otherwise the
appropriate age-related algorithms, arrhythmia detection, and
calculations may not be applied.
WARNING
LOSS OF FUNCTION/DATA LOSS — Be extremely careful not to
assign the same IP address to two different devices on the network.
Duplicate IP addresses will cause erratic system communication and
data loss.
WARNING
PERSONAL INJURY/EQUIPMENT DAMAGE—Observe the
following guidelines associated with rack stability:
 Ensure both the top and bottom of the rack are securely fastened
to a suitable and substantial building support.
 Ensure the rack weight is supported by the leveling jacks and
that the rack leveling jacks are in contact with the floor.
 If it is a single rack installation, ensure stabilizers are attached.
 If it is a multiple rack installation, ensure the racks are tightly
secured together.
 Do not extend more than one component outside the rack at a
time.
Read and follow rack mounting instructions in the appropriate HP
documentation, packaged with the CARESCAPE Gateway. See
Related documentation on page 1-4.

Introduction
WARNING
PERSONAL INJURY/EQUIPMENT DAMAGE/SHOCK
HAZARD—If the CARESCAPE Gateway is installed in a rack,
observe the following guidelines associated with rack stability:
secured together.
time.
For more information about working with racks, refer to the
appropriate HP ProLiant DL360 Server Setup and Installation Guide
supplied on the Documentation CD-ROM.
WARNING
SHOCK HAZARD—The CARESCAPE Gateway must not be
located in the patient environment as a shock hazard may exist. The
CARESCAPE Gateway is IEC 60950 classified equipment which
may not meet the leakage requirements of patient care area
equipment.
WARNING
SHOCK HAZARD—The CARESCAPE Gateway and all peripheral
equipment must be adequately grounded or a shock hazard may
exist.
WARNING
SHOCK HAZARD — After performing a safe shutdown,
disconnect the power cord(s) from the wall outlet to remove power
from the CARESCAPE Gateway. The on/off button on the front
panel does not disconnect the CARESCAPE Gateway from AC
power.
Additionally, wait 40 seconds after disconnecting the CARESCAPE

Gateway power cord from the wall outlet. The computer remains
energized for a period of time after shutdown. If these precautions
are not followed, the possibility of electrical shock exists.

Introduction
WARNING
SHOCK HAZARD—Make sure that all power cords and all other
cables are disconnected from the server before removing the cover.
Severe electrical shock could result from not following this
instruction.
WARNING
SHOCK HAZARD/EQUIPMENT DAMAGE—If fluids are spilled
on the CARESCAPE Gateway, shut down the unit, remove power
and disconnect all components. Perform the maintenance procedures
listed in this section and document the incident in the repair log. Do
not use the CARESCAPE Gateway if it has been damaged by the
fluid. Fluids spilled on the CARESCAPE Gateway can cause an
electrical shock hazard and may damage the equipment.
WARNING
SHOCK HAZARD/PERSONAL INJURY— Do not install the
CARESCAPE Gateway in a patient care/caregiver area. It should be
installed and located with other IT equipment, such as in a server
rack or cabinet. For additional physical environment requirements,
refer to the HP ProLiant DL360 G7 Server Maintenance and Service
Guide. See Related documentation on page 1-4.
Caution safety messages

The following caution safety messages apply to this system.
CAUTION
ACCURACY—If the data intended to be transferred is not available
or the accuracy of the data transferred is questionable, the caregiver
should access the data from the source device, such as the primary
patient monitor for physiological data and the HIS for patient
demographic information. The data provided via the CARESCAPE
Gateway is not intended to be the sole source for patient data and is
to be used in conjunction with the data at the patient monitor, central
station, and the hospital's information systems. The primary patient
monitor should always be referenced before making any patient care
decisions.

Introduction
CAUTION
ELECTROSTATIC DISCHARGE —Do not touch any internal
metal Parts. Place the server on top of a grounded electrostatic
discharge (ESD) pad. Use the disposable antistatic wrist strap
supplied with the server and stick it to the metal base of the server
before touching any of the internal components. The server contains
electronic parts that are extremely sensitive to static electricity.
Damage to the server could result if this instruction is not followed.
CAUTION
EQUIPMENT DAMAGE —The CARESCAPE Gateway is static
sensitive and should be handled using precautions to prevent
electrostatic discharge damage.
CAUTION
EQUIPMENT DAMAGE—Use an anti-static strap when cleaning
the internal components. The CARESCAPE Gateway is extremely
static sensitive and should be handled using electrostatic discharge
procedures.
CAUTION
EQUIPMENT DAMAGE — Follow the electrostatic discharge
damage control procedures. See Controlling electrostatic discharge
damage on page 4-3. The CARESCAPE Gateway is extremely static
sensitive. If the proper ESD precautions are not followed, damage to
the unit could result.
CAUTION
EQUIPMENT DAMAGE/LOSS OF FUNCTION/PERSONAL
INJURY—The manufacturer does not in any manner, assume the
responsibility for performing the recommended maintenance
schedule, unless an Equipment Maintenance Agreement exists. The
sole responsibility rests with the individuals, hospitals, or sites
utilizing the device. Failure on the part of all responsible individuals,
hospitals or sites, employing the use of this device, to implement the
recommended maintenance schedule may cause equipment failure
and possible health hazards.
CAUTION
INCORRECT PATIENT DATA — Clinicians should ensure the
historical patient data collected from the monitoring equipment
when stored in the clinical information system is associated with the
correct patient.

Introduction
CAUTION
INCORRECT PATIENT DATA — Personnel should have level 2
Cloverleaf training to configure the integration engine.
CAUTION
INCORRECT PATIENT DATA — A secure data link (IX network
router) must be installed and properly configured between the
CARESCAPE Network IX and the hospital enterprise network. The
connection between the hospital network and the CARESCAPE
Network IX requires the certain ports to be opened for the
CARESCAPE Gateway. To determine which ports need to be
opened for the CARESCAPE Gateway, refer to Router supported
services on page F-1.
CAUTION
INCORRECT PATIENT DATA —The CARESCAPE Gateway
should be isolated from strong electromagnetic fields and electrical
noise produced by electrical devices such as:
 Elevators
 Copy machines
 Air conditioners, large fans
 Large electric motors
 Radio and TV transmitters
 High frequency security devices
 High-load medical devices (e.g., imaging, defibrillators, etc.)
CAUTION
INCORRECT PATIENT DATA —Provide for the appropriate
physical and environmental specifications when planning the
installation.See Technical specifications on page D-1. Failure to
meet the specifications could result to the hard drive malfunctioning.
CAUTION
INCORRECT PATIENT DATA/IMPAIRS OPERATION OF
OTHER DEVICES — Connect the laptop to the router or the iLO
port to prevent potential contamination of malware.

Introduction
CAUTION
INCORRECT PATIENT DATA— The time zone setting on the
CARESCAPE Gateway must match the time zone setting on the
iCentrals from which it is configured to collect data. Otherwise, the
data may be incorrectly time stamped. In addition, it is
recommended that the CARESCAPE Gateway and iCentral clocks
be synchronized to an NTP server.
CAUTION
IMPAIRS OPERATION OF OTHER DEVICES — The
CARESCAPE Gateway requires that the system run on Full-Duplex
Fast Ethernet (100Mb/s) or Gigabit (1000Mb/s) networks. The
system is configured to use auto-negotiated speed and duplex by
default and this is the recommended operating mode. It is possible to
configure the system to only use 100Mb/s Full-Duplex (disabling
auto-negotiation). In order to use this mode, the network switch
must have an identical configuration.
CAUTION
LOSS OF FUNCTION—All external cabling used with the
CARESCAPE Gateway must be routed so as not to interfere with
access or operation of the system and must be installed to protect
against accidental disconnection of the cables. Failure to follow this
instruction could result in personal injury or equipment damage.
CAUTION
LOSS OF FUNCTION/PERFORMANCE—A site survey must be
performed before installing the CARESCAPE Gateway. Failure to
perform a site survey may lead to improper performance of the
CARESCAPE Gateway and may affect the performance of the
CARESCAPE Network as well.
CAUTION
PROPER ADMIT/DISCHARGE/NEW CASE— Proper admit/
discharge/new case procedures for the acquisition device must be
followed by the user to ensure that data from the different patients is
not mixed. Refer to the appropriate device operator’s manual for
proper procedures.

Introduction
CAUTION
PROPER HIS PROCEDURES—Procedures for entering and
administering patient information at the HIS must be consistent with
the site-specific CARESCAPE Gateway configuration. Proper
procedures must be followed by the user to ensure offline data is
collected from the CARESCAPE Network devices and to ensure
that data from the different patients is not mixed.
CAUTION
REGULATION COMPLIANCE/ENVIRONMENTAL
CONTAMINATION—At the end of its service life, the
CARESCAPE Gateway, as well as its accessories, must be disposed
of in compliance with the guidelines regulating the disposal of such
products. If you have questions concerning disposal of the product,
contact GE or its representatives.
CAUTION
THERMAL HAZARD—Internal components, especially power
supplies, get extremely hot when the CARESCAPE Gateway is in
operation. Shut down the CARESCAPE Gateway and allow it to
cool before touching any internal components.
CAUTION
TRIPPING HAZARD/LOSS OF FUNCTION—All cabling must be
installed to protect against tripping and accidental disconnection of
the cables. All external cabling used with the CARESCAPE
Gateway must be routed so as not to interfere with access or
operation of the system. Failure to follow this instruction could
result in personal injury or equipment damage.
CAUTION
UNIQUE PATIENT ID—Depending on the specific configuration at
your site, a valid and unique PID must be entered at the patient
monitoring device. This PID may need to match the PID at the
HIS(s). Other demographic information used for patient
identification should be verified when entered at the monitoring
equipment.
CAUTION
A user must verify the accuracy of patient demographic information
by confirming the transferred or manually entered information with
a second source.

Introduction
CAUTION
Automated or manual changes to the time or date settings (including
daylight saving time adjustments) may affect other monitoring
devices on the CARESCAPE Network, such as a loss of patient data
history. Refer to the appropriate monitoring device's product
documentation for detailed information about the effects of time
changes.
Note safety messages

The following note safety messages apply to this system.
NOTE
Do not position the CARESCAPE Gateway in an enclosed area that may restrict
dissipation of generated heat. The CARESCAPE Gateway uses an internal forced
air cooling system. Any air flow restrictions may cause a rise in internal
temperature which may result in equipment failure.
NOTE
Only external devices specifically designed to be connected to the CARESCAPE

Gateway, or approved by GE for use with the CARESCAPE Gateway should be
connected, as specified in this manual or as otherwise specified by the
manufacturer. External equipment must be connected to the system only by
qualified biomedical engineering personnel. Connecting external devices not
approved for use with the CARESCAPE Gateway may cause loss of function or
equipment damage.
NOTE
Follow the maintenance instructions in this manual and in the appropriate HP

ProLiant DL360 Server Maintenance and Service Guide. GE does not assume
responsibility for damage to the equipment caused by improperly loaded
software and/or current or future conditions of the equipment due to improper
care and maintenance.
NOTE
Shut down of the CARESCAPE Gateway causes disruption of data flow between
the CARESCAPE Network MC network devices and the hospital enterprise
network. Notify the affected users relying upon this data flow before shutting
down the CARESCAPE Gateway, or if the CARESCAPE Gateway shuts down
for any reason.
NOTE
If more than one ADT server exists on the CARESCAPE Network intermittent
lookup failures may occur. Be sure to allow only one ADT server to exist on the
CARESCAPE Network.

Introduction
NOTE
Parts and accessories used must meet the requirements of the applicable IEC
60950 series safety standards for IT equipment.
The use of accessory equipment not complying with the equivalent safety
requirements of the device may lead to a reduced level of safety of the resulting
system. Ensure there is evidence that the safety certification of the accessory has
been performed in accordance to the appropriate IEC 60950 series safety
standards for IT equipment before use.
NOTE
Contact GE for information before connecting any devices to the equipment that
are not recommended in this manual.
NOTE
Periodically, and whenever the integrity of the device is in doubt, test all
functions.
NOTE
If the IP address settings are changed, update the secure data link configuration
and the labels with the new IP address settings. Failure to follow this instruction
can cause loss of connectivity with the CARESCAPE Gateway.
NOTE
Set the CARESCAPE Network IP address using an iLO connection. If a remote

Webmin connection is used to change the CARESCAPE Network IX IP address
with the firewall enabled, the Webmin connection to the CARESCAPE Gateway
will be broken.
NOTE
The backup procedure should be performed at regular intervals and/or whenever

the CARESCAPE Gateway configuration is changed to ensure complete system
restore if it should become necessary. Failure to perform the backup procedure
after the CARESCAPE Gateway configuration changes could result in lost
licensing, interface and application configuration data.
NOTE
The Cloverleaf interface backup procedure should be performed at regular

intervals and/or whenever any Cloverleaf interface is changed to ensure complete
interface restoration if it should become necessary. Failure to perform the backup
procedure after changing any Cloverleaf interface could result in lost interface
configuration and/or HL7 and ADT data.
NOTE
Do not allow wireless devices to act as time master. Wireless devices can drop
communication packets which may cause communication problems resulting in
time errors.

Introduction
Equipment information
Equipment symbols
Some of the following symbols appear on the equipment.
ATTENTION: Consult accompanying documents before using the equipment.
SHOCK HAZARD: Indicates presence of hazardous energy circuits or electrical shock hazards.
HOT SURFACE: Indicates presence of hot components/surfaces, which present an injury potential if
contacted.
Keyboard port.
Mouse port.
USB port.
Multiple power sources.
European Union Declaration of Conformity.
Ethernet connector port.
Serial interface.
 VGA monitor port.

Introduction
Power on/standby switch.
Internal component status LED. Red or amber indicates malfunction; green indicates normal operation.
See LED status indicator description on page 5-5 and the HP ProLiant DL360 G7 Server Maintenance
and Service Guide.
Power supply status LED. Amber indicates malfunction; green indicates normal operation. See LED
status indicator description on page 5-5 and the HP ProLiant DL360 G7 Server Maintenance and
Service Guide.
Underwriters Laboratories product certification mark.
For Russia only: Russian GOST-R certification, where XXXX indicates the four digit certification body
number determined by product.
CCC Mark. Symbolizes conformity with applicable China requirements.

This symbol indicates that the waste of electrical and electronic equipment must not be disposed as
unsorted municipal waste and must be collected separately. Please contact an authorized
representative of the manufacturer for information concerning the decommissioning of your equipment.
This symbol indicates the date of manufacture of this device. The first four digits identify the year and
the last two digits identify the month.
2005-08
Manufacturer name and address.

Introduction
European authorized representative.
NOTE
The following symbols (required by China law only) are representative of what you may see on
your equipment.
The number in the symbol indicates the EFUP period in years, as explained below. Check the symbol
on your equipment for its EFUP period.
This symbol indicates the product contains hazardous materials in excess of the limits established by
the Chinese standard SJ/T11363-2006 Requirements for Concentration Limits for Certain Hazardous
Substances in Electronic Information Products. The number in the symbol is the Environment-friendly
User Period (EFUP), which indicates the period during which the toxic or hazardous substances or
elements contained in electronic information products will not leak or mutate under normal operating
conditions so that the use of such electronic information products will not result in any severe
environmental pollution, any bodily injury or damage to any assets. The unit of the period is “Year”.
In order to maintain the declared EFUP, the product shall be operated normally according to the
instructions and environmental conditions as defined in the product manual, and periodic maintenance
schedules specified in Product Maintenance Procedures shall be followed strictly.
Consumables or certain parts may have their own label with an EFUP value less than the product.
Periodic replacement of those consumables or parts to maintain the declared EFUP shall be done in
accordance with the Product Maintenance Procedures. This product must not be disposed of as
unsorted municipal waste, and must be collected separately and handled properly after
decommissioning.
Service requirements
Follow the service requirements listed below. Also, see Maintenance on page 4-1.
 Refer equipment servicing to GE authorized service personnel only.

 Any unauthorized attempt to repair equipment under warranty voids that
warranty.
 It is the user’s responsibility to report the need for service to GE or to one of their
authorized agents.
 Failure on the part of the responsible individual, hospital, or site using this
equipment to implement a satisfactory maintenance schedule may cause undue
equipment failure and possible health hazards.
 Regular maintenance, irrespective of usage, is essential to ensure that the
equipment is always functional when required.

Introduction
Equipment identification
Every GE device has a unique serial number for identification. A sample of the
information found on a serial number label is shown below.
### ## ## #### # #
A B C D E F
Description
A product code1
B year manufactured
C fiscal week manufactured
D production sequence number
E manufacturing site
F miscellaneous characteristic
1The product codes are SGC for the CARESCAPE Gateway DL360 G7
server and SGD for the CARESCAPE Gateway software v1.

Introduction

2 Equipment overview

Equipment overview
CARESCAPE Gateway
The CARESCAPE Gateway provides mechanisms for exchanging information
between devices on the hospital's enterprise network and devices on the
CARESCAPE Network MC and S/5 Network. It forms a secure data bridge so data
residing on either network can be shared across the two networks. The availability of
each feature listed below is dependent on whether the particular feature was
purchased and then implemented for your site. Please contact your system
administrator to understand how the system is implemented at your specific location
and care area.
NOTE
The data available from the trended vital signs, vitals on demand, and HSDI are
not the same. For details on the data available, refer to Appendix E.
NOTE
For additional information, see Technical specifications on page D-1.
Overview
CARESCAPE Gateway connection diagram

Equipment overview
Secure data link

The secure data link refers to the router or layer 3 switch that bridges the
CARESCAPE Network IX and the hospital enterprise network.
CARESCAPE Network IX
The CARESCAPE Network IX (Information eXchange) is used for non-real time
data sharing and printer function.
CARESCAPE Network MC
The CARESCAPE Network MC (Mission Critical) is the network that is used to
connect the server systems to the monitors and to the telemetry systems. This network
contains real time waveforms, parameters, alarms and other time-sensitive data.
Hospital enterprise network

The Hospital enterprise network is the customer’s resident enterprise network.
CARESCAPE Network IX connects to this network using the CARESCAPE
Network secure data link (CARESCAPE Network IX router).
Network connections/back panel
1 2
3 4 5 6 7
Item Description
1 CARESCAPE Network MC Network connection
2 S/5 Network connection
3 CARESCAPE Network IX Network connection
4 CARESCAPE Network MC Network connection
5 S/5 Network connection
6 CARESCAPE Network IX Network connection
7 iLO connection

Equipment overview
Integrated lights-out (iLO) connection

The iLO connection is used for service/administration tasks. See iLO on page 2-21.
Theory of operation
CARESCAPE Gateway functional description
The CARESCAPE Gateway functions as a data path between the CARESCAPE
Network, S/5 Network and the hospital enterprise network. All data is encoded in
HL7 (Health Level Seven standard [HL7, 7th OSI layer protocol for the health
environment]) format. A near real-time data stream in XML format is also provided.
NOTE
HL7 is a standard for information exchange between medical applications. It is

the communication protocol used for communication between the CARESCAPE
Network and the hospital enterprise networks and between the S/5 Network and
the hospital enterprise networks.
Examples:
 Patient demographic information residing on the hospital enterprise network

could be accessed from a bedside device on the CARESCAPE Network MC
during patient admit.
 Data collected through the CARESCAPE Network and S/5 Network is converted
and sent to the Hospital Information Server (HIS) on the hospital enterprise
network. This data includes trended patient data (vitals, SAM, ECG, ICG, SPO2,
etc.), waveforms and near-realtime numerics. No alarms or alarm histories are
included.
Multiple CARESCAPE Gateway systems on network

Multiple CARESCAPE Gateway systems can be used on the CARESCAPE Network
for load balancing, supporting a test environment, etc. When multiple CARESCAPE
Gateway systems exist on the same network the following conditions must be
followed.
 Only one CARESCAPE Gateway or Aware Gateway can update the time master
(i.e., the CARESCAPE Gateway is configured as the time source for the
network). All other CARESCAPE Gateways or Aware Gateways must have the
MC Network configured to be their time source.
NOTE
It is recommended that a CARESCAPE Gateway be the time source if both
an Aware Gateway and CARESCAPE Gateway are on the network.
 Only one CARESCAPE Gateway or Aware Gateway can offer ADT query
services on the monitoring network. If multiple CARESCAPE Gateways or
Aware Gateways are licensed to enable ADT, monitoring devices can use either
device. However, there is no control over which CARESCAPE Gateway or
Aware Gateway the monitoring devices use at any given time.

Equipment overview
 The bedlist on each CARESCAPE Gateway/Aware Gateway must not overlap

the bedlist on any other CARESCAPE Gateway/Aware Gateway. For an S/5
Network, an iCentral should be on only one CARESCAPE Gateway iCentral list.
 HL7 and HSDI clients must be configured to access the appropriate
CARESCAPE Gateway/Aware Gateway.
Transport modes and back-collection

Monitors and acquisition modules continue to accumulate data during transport.
Back-collection occurs when the monitor/acquisition module is reconnected to the
network, and the accumulated data is passed to the CARESCAPE Gateway.
NOTE
If more than one server exists, group units on the same bedlist to ensure data
continuity for patient transports between care areas. Device tracking information
is contained with each CARESCAPE Gateway or Aware Gateway and is not
shared between systems. Back collection will not occur if a patient acquisition
device moves from one server’s bedlist to another server’s bedlist.
Monitor transport mode

NOTE
Monitors in a transport state are tracked by IP address, because the monitor’s unit
or bed name may change during transport (e.g., Rover mode).
A monitor is classified to be in a transport state if both of the following are true:
 The monitor is off the network for more than two minutes.
 While the monitor is off the network, it remains admitted to the same patient.
Acquisition module transport mode

NOTE
The system tracks acquisition modules in transport mode by PID.
An acquisition module is a data collection module which connects to a monitor.

Acquisition modules can collect patient data even if disconnected from a monitor.
Acquisition modules can connect to different monitors as the patient moves

throughout the facility.
The acquisition module transport state exists if both of the following are true:
 Specific acquisition module parameters have already been collected from a

monitor by the CARESCAPE Gateway.
 Collection of acquisition module parameters from the monitor stops, but the
monitor is still admitted and on the network.
Back-collection occurs when the monitor/acquisition module is reconnected to the
network, and the accumulated data is passed to the CARESCAPE Gateway.

Equipment overview
Back-collection occurs when the acquisition module is re-connected to the network at

any monitor on that network that is also in the CARESCAPE Gateway bed list.
CARESCAPE Gateway logical structure
The following logical structure description points refer to the previous diagram:
Description Function
1 Hospital enterprise The resident enterprise network at the hospital or facility

network (comprised of the Hospital Information Server [HIS],
workstations, etc.) used for collecting/storing patient/
facility information, generic data sharing, etc. Patient
demographic information is commonly collected and
stored in the HIS database within this network as part of
normal facility operation.
NOTE
A secure data link (IX network router) is required
between the CARESCAPE Network IX and the
hospital enterprise network.
2 CARESCAPE Network The real time “Mission Critical” network used for
MC connecting CARESCAPE Network devices together.
Generally, server systems, monitors, and telemetry
cabinets. This network is used to collect and store
waveforms, parameters, alarms and other time-sensitive
data, and also for real-time monitoring of this data.
3 iCentral The S/5 Network establishes communication and allows

patient data to be sent to an iCentral.

Equipment overview
Description Function
4 CARESCAPE Gateway This server is the subject of this service manual, and is
used as a data path between the hospital enterprise
network and the CARESCAPE Network MC. The
CARESCAPE Gateway data path makes patient data
available to the HIS.
5 CARESCAPE Network This component responds to CARESCAPE Gateway

enterprise gateway requests and receives ADT data.
6 CARESCAPE Network This component encapsulates and supports the operation

interface of the Cloverleaf HL7 Interface Engine. It also provides the
send/receive connection between the CARESCAPE
Network Enterprise Gateway and the Cloverleaf HL7
Interface Engine.
7 Cloverleaf HL7 interface This component sends/receives data from the hospital
engine enterprise network. It provides custom translation of
generic HL7 encoded data to fit the specific
communication needs of the hospital enterprise network.
8 HSDI adaptor This component takes data from CARESCAPE Network

MC and S/5 Network monitors and propagates it to the
Enterprise network in XML format.
9 S/5 Network Interface A TCP/IP based network allowing communication with

iCentral systems. The S/5 Network allows for data
collection from multiple iCentral stations, each of which
may have up to 32 monitors directly attached.
CARESCAPE Gateway function description

Function descriptions in this section are generic in nature, and are shown separated
from each other for clarity. However, CARESCAPE Gateway functions often act in
concert with each other, providing interactive two-way communication between the
CARESCAPE Network, S/5 Network and the hospital enterprise networks.
Trended vital signs

Overview
The CARESCAPE Gateway transfers trended patient vital signs data that is collected
from an acquisition device (e.g., patient monitor, telemetry transmitter, etc.) to the
hospital's information system(s). Proper transfer of this data from the patient
monitoring devices to the HIS is dependent on a custom configuration of the interface
between the CARESCAPE Gateway and the hospital's information system.
Depending on the custom configuration at your site, a PID or MRN entered at both
the patient monitor device and the HIS may be required to ensure proper transfer of
patient data. If this information is required at the patient monitoring device, it must be
entered while the patient is admitted and on-line. The CARESCAPE Gateway stops
transferring data if the acquisition device goes off-line or is discharged.
Depending on the configuration for your site, all or some of the data stored by the
acquisition device while off-line may be transferred when that device returns on-line

Equipment overview
provided the patient is still admitted to the device. The data transfer mapping rules
may have been customized to suit the particular needs of your site, and therefore may
require additional information or procedures to ensure proper and timely transfer of
data. Please contact your system administrator to understand how the system is
implemented at your specific location and care area.
Trended data transfer guidelines
CAUTION
PROPER ADMIT/DISCHARGE/NEW CASE—Proper admit/
proper procedures.
CAUTION
Proper admit, discharge and transport procedures for the acquisition device must be
followed to ensure a continuous data record is transferred to the HIS(s) and that data
from different patients is not mixed. Refer to the appropriate device operator’s
manual for proper procedures.
 The acquisition device must be listed in the CARESCAPE Gateway's acquisition

Bedlist to have data transferred to the HIS(s). If a device’s name is changed to
one that is not on the bedlist, data collection for that device will stop.
 The CARESCAPE Gateway will send data at the configured time intervals of 1,
2, 3, 4, 5, 10, 15, 30, 45, and 60 minutes. Collection intervals can be set for each
device enabled to send data.
 Depending on the custom configuration at your site, the HIS(s) may require that
all patient data sent from the patient monitoring network include PID and/or
patient name. For these sites, any changes to a PID and/or patient name will be
reflected only in the new data transferred going forward.
 Acquisition module transport requires a PID to be entered upon admit to ensure
that the patient can be identified when the acquisition module returns to the
network.
 Data cannot be transferred while the device is off-line.
 Up to eight hours of data collected by the acquisition device while it is off-line
will be transferred if the patient monitoring device returns on-line and has an
admitted patient. This feature may have been limited or disabled at your site.
 The CARESCAPE Gateway can transfer both periodic and episodic parameters
collected from an acquisition device. For a detailed list of supported parameters,
refer to Supported parameters on page E-2.

Equipment overview
 Periodic data is sent as the latest minute trend as calculated by the acquisition
device. For example, if the user configures data collection intervals for one hour
intervals for the CARESCAPE Gateway, then every hour on the hour periodic
data will be sent to the HIS along with any episodic data (i.e., NBPs, etc.) that
occurred during that interval using CARESCAPE Network time stamps.
 If two acquisition devices are admitted with the same PID, the CARESCAPE
Gateway will transfer data from both acquisition devices along with the duplicate
PIDs.
 When time shifts backwards on the CARESCAPE Network due to Daylight
Saving Time, the messages produced from the monitoring devices during the
repeated time frame will have the same time timestamps as messages already
sent, but it is with the new periodic trend data. Previously-sent episodic data (e.g.
NBPs, calcs) may get sent again depending on the length of the time shift.
Trended data (ORU) outbound overview

The trended data outbound function allows access of CARESCAPE Network MC and
S/5 Network patient data from the hospital enterprise network.
The following describes the process to create ORU messages:
1. Patient data is acquired and enters the CARESCAPE Gateway over the
CARESCAPE Network MC or S/5 Network.
2. Patient data is converted to HL7 data.
3. HL7 data from the CARESCAPE Network Interface is handed off to the
Cloverleaf HL7 Interface Engine (running inside the CARESCAPE Gateway
CCG), where the data undergoes a custom translation to fit the specific
communication needs of the HIS.

Equipment overview
4. Patient data is used/stored on the HIS as appropriate: at the patient’s doctor’s

workstation, added to the patient’s record in the HIS, etc.
NOTE
It is important that the Enterprise Network time and the CARESCAPE

Network MC network time be synchronized for the time stamps on patient
data to match. The NTP Time Synchronization feature can be used to
accomplish this task. The S/5 Network time can be synchronized to the
CARESCAPE Gateway NTP Daemon.
Vitals on Demand (VoD) provides clinicians with the ability to rapidly assess a
patient’s vital signs when a request is made to CARESCAPE Gateway.
Vitals on Demand requests can be made from the IX or hospital enterprise networks.
The CARESCAPE Gateway returns the current value for the data being requested.
Vitals on demand
The vitals on demand (VOD) feature allows the CARESCAPE Gateway to obtain a
current snapshot of vital signs and patient demographic data on the patient monitor.
This allows an information system (or other client) to obtain the data from the
CARESCAPE Gateway. The VOD request does not capture trended data.
A VOD Request will fail for any patient monitor not online and no data will be
transferred.
The data transfer mapping rules may have been customized to suit the particular
needs of your site, and therefore may require additional information or procedures to
ensure proper and timely transfer of data. Please contact your system administrator to
understand how the system is implemented at your specific location and care area.
VOD guidelines
CAUTION
proper procedures.
CAUTION
Proper admit, discharge and transport procedures for the acquisition device must be
followed to ensure a data record is transferred to the HIS(s) and that data from

Equipment overview
different patients is not mixed. Refer to the appropriate device operator’s manual for
proper procedures.
 Depending on the custom configuration at your site, the HIS(s) may require that
all patient data sent from the patient monitoring network include the PID and/or
patient name.
 The set of periodic and episodic parameters supported is different from the
trended data feature.
 This feature is intended to be used for obtaining the current data from a patient
monitor upon request by a clinician. This should not be utilized for a CIS to
repeatedly make requests. The trended vital signs feature should be used for
normal charting instead.
Query data (ORF) overview

The CARESCAPE Gateway handles QRY messages as displayed in the following
diagram.
Process
1 A query for patient data is submitted at a patient’s doctor’s workstation, for example.
2 Query data is transformed by the Cloverleaf engine.
3 Patient data is acquired on the CARESCAPE Network MC or S/5 Network, and enters
the CARESCAPE Gateway via an Ethernet network connection.

Equipment overview
Process
4 Patient data is converted to HL7 data by the CARESCAPE Network or S/5 Network
Interface.
5 HL7 data from the CARESCAPE Network Interface is handed off to the Cloverleaf
HL7 Interface Engine, where the data undergoes a further custom translation to fit the
specific communication needs of the HIS.
6 Patient data is displayed to the user at the patient’s doctor’s workstation, for example.
ADT inbound
Overview
ADT provides the ability to transfer patient demographic information from the HIS(s)
ADT feed to the patient monitoring devices on the CARESCAPE Network MC. A
clinician at the patient monitor or central station must initiate the transfer of patient
demographic information. For more information, please see the operator’s manuals
for your central station or patient monitoring devices.
CAUTION
A user must verify the accuracy of patient demographic information
by confirming the transferred or manually entered information with
a second source.
There are two methods to acquire patient demographic information, which are ADT
Request Admit and ADT Picklist.
ADT Inbound function process

The ADT Inbound function is basically the opposite of the HL7 Outbound function:
with ADT Inbound, patient data from the HIS is made available to devices on the
CARESCAPE Network MC.
For the ADT Inbound interface, by default the HIS communicates with the
CARESCAPE Gateway as a TCP/IP client. The CARESCAPE Gateway ADT
inbound process uses the Cloverleaf engine to listen on a preconfigured port.

Equipment overview
The following describes the ADT Inbound function process:
1. Patient information data from the HIS periodically streams into the
CARESCAPE Gateway.
2. Patient data from the HIS is held in cache by the ADT database by the Centricity
Clinical Gateway (CCG), embedded within the CARESCAPE Gateway.
3. A clinician uses a patient monitor or central station to generate a query which is

sent to the ADT database.
4. Data held in the ADT database is sent to the requesting system.
NOTE
Refer to the CARESCAPE Gateway HL7 Reference Manual for information

about ADT business rules.
ADT Request Admit

The Request Admit feature on the acquisition device will send a query to the
CARESCAPE Gateway based on the Unit and Bed name that has been assigned to
that device.
The following fields are supported ADT Request Admit:
 Location (Unit and Bed)

 Patient name (Last, First)
 MRN
 Date of Birth
 Gender

Equipment overview
ADT Request Admit guidelines

 For a match to occur the patient must be admitted in the ADT system under the
UNIT and BED which is requesting the patient information. (For example, if the
“Request Admit” feature is used on DASH patient monitor named ED/Bed5, a
match will occur if the ADT system has sent the CARESCAPE Gateway a record
for a patient admitted to ED/Bed5.)
 During system maintenance, the ADT Request Admit feature may become
unavailable for short periods of time.
 If the ADT Request Admit function is unsuccessful when performed from the
patient monitor or central station device, please wait a few minutes and try the
request again.
 The CARESCAPE Gateway supports a limited number of languages. Patient
demographic data and patient monitors should be configured to utilize a
“CARESCAPE Gateway” supported language so that data is mapped
appropriately. Please contact your system administrator to understand how the
CARESCAPE Gateway is configured for your site.
 For a Unit and Bed query, when multiple patients are assigned to the same
location, the patient record with the newest visit information is returned.
ADT Picklist
Overview
ADT Picklist provides the ability to transfer patient demographic information from
the HIS(s) ADT feed to the patient monitoring devices on the CARESCAPE Network
MC Network. A clinician at the patient monitor or central station must initiate the
transfer of patient demographic information. For more information, please see the
operator’s manuals for your central station or patient monitoring devices.
During system maintenance, the ADT Picklist feature may become unavailable for
short periods of time.
If the ADT Picklist function is unsuccessful when performed from the patient monitor
or central station device, please wait a few minutes and try the request again.
The following fields are supported for ADT Picklist:
 Location (Unit and Bed)

 Patient name (Last, First)
 MRN
 Date of Birth
 Gender
 Ethnicity
 Visit/Account number
 Height
 Weight
Depending on the capabilities of the patient monitoring device, queries can be
performed using the following fields: Location (Unit only or Unit and Bed), Patient
name (Last name only or Last and First names), or MRN.

Equipment overview
Except for the Unit and Bed query, records are retrieved with partial matches. For
example, if the query is for Last name A, all records with patients whose last names
begin with A will be returned.
This feature can be disabled by the administrator limiting records returned to only
those with full text match.
For the Unit and Bed query, when multiple patients are assigned to the same location,
the patient record with the newest visit information is returned.
For any particular patient record that is matched, when multiple visit information
exists for the patient, the newest visit information is returned. The specific fields
contained in visit information include: MRN, height, weight, and Visit/Account
number.
Event notification
When configured, the CARESCAPE Gateway will send a notification when an error
occurred processing an ADT message from the HIS(s), such as the patient
information was not updated properly. The error notification may be delivered via
email or another notification method, depending on the site implementation. The
system administrator configures the addresses to which the event notification
messages will be sent.
The subject of each notification message contains an explanation of the reason for the
error that occurred when the CARESCAPE Gateway received the message, or
unspecified for unknown errors. The subject also contains the name of the type of
workflow that should have been performed on the CARESCAPE Gateway's copy of
the patient information (but was not due to the error). Below are some of the main
types of workflow and what it means for the set of patient data in the CARESCAPE
Gateway when an error has occurred:
 Admit, cancel discharge: The patient’s record will not be available, or will still be
marked as discharged; requests for the patient information will typically fail.
 Transfer: The assigned bed location for a patient will not have been updated;
requests for the patient information by location will only work for the old
location.
 Discharge, cancel admit, delete: The patient’s record may still be returned in
requests for patient information even though the intent was for it to not be.
 Change outpatient or inpatient status: This only affects the timing of when the
patient’s record is purged from the CARESCAPE Gateway. Typically out-patient
records are purged more frequently, but when this happens depends on your
CARESCAPE Gateway's configuration.
 Update patient info, merge: The updates to the patient’s information will not be
reflected properly in the CARESCAPE Gateway.
Each notification message also contains a copy of the ADT data that was received. If
provided by the HIS, the following data can typically be found on a line beginning
with the indicated three-letter code:
 PID: Patient name and identifier / MRN

 PV1: Assigned location / bed name and account / visit number
 OBX: Height and weight

Equipment overview
NTP time synchronization

Network time synchronization
The CARESCAPE Gateway can be configured to automatically update the clocks on
devices that reside on the CARESCAPE Network to maintain time synchronization. It
periodically confirms the network time matches its own clock and shifts the clocks on
the network when going into and out of daylight saving time (DST). The timestamps
of new data collected by the various CARESCAPE Gateway services (VoD, HSDI
and trended data) reflect the new time.
When the clocks on CARESCAPE Network monitoring devices are shifted during a
DST transition, the timestamps of a subset of the trended data are shifted due to the
way the monitoring equipment is designed to handle time changes. Periodic data
timestamps change relative to the time shift while episodic data (NBPs and calcs)
timestamps remain constant. There are scenarios where a short time period of the
trended data may not be collected, depending on the type of DST transition and
whether the equipment is online or offline during the event.
 Online monitors: In the event a clock requires a time adjustment due to DST, the
initial collection of periodic data may not occur. Also, episodic data stored at the
monitor during the minute preceding the DST transition may not be collected.
 Offline monitors and data acquisition devices: In the event a patient monitor was
offline (or acquisition modules are in transport) for greater than one hour during
DST fall-back or spring-ahead scenarios, back collection of episodic data may
not occur when the monitor comes back online (or acquisition modules are
reattached). In addition, during the DST fall-back scenario current trend data will
not be sent to an HL7 client for up to one hour after the monitor comes back
online.
CAUTION
history. Refer to the appropriate monitoring device's product
changes.
NOTE
If the CARESCAPE Gateway is not configured to automatically update the MC

network time, it must be configured to have its clock synchronized from the MC
network or from the same reliable time source. This is necessary in order to
provide the best possible handling of collection of trended data and to ensure
proper creation of timestamps in the HSDI vitals data it collects.

Equipment overview
NOTE
The following error message will appear in the CCG log when the system
statistics subsystem is unable to record performance data due to a time change.
@20000506 hh:mm:ss@ {WARN} JMXDataCollector-thread-1

com.ge.medit.common.jmx.JMXDataCollector.updateRrd (JMXDataCollector)
Could not update RRD file: RRDUPDATE failed: /etc/webmin/sysstats/
modules/csg-0.0.1/platform-heapmemoryusage.rrd: illegal attempt to update
using time 957633978 when last update time is 1304706421 (minimum one
second step)
While the CARESCAPE Gateway does support time synchronization of S/5

monitoring equipment, it does not support changing an S/5 monitoring device’s clock
while patients are admitted. Time synchronization on S/5 monitoring devices can be
accomplished using the CARESCAPE Gateway or another NTP server.
NTP synchronization function

Network Time Protocol (NTP) time synchronization provides for uniform time. This
ensures that patient data date/time stamping is consistent.
NTP time synchronization can be configured as needed at the CARESCAPE

Gateway.
The following is a description of the NTP time synchronization function only:
1. The CARESCAPE Gateway uses the NTP client/server protocol to keep its clock
synchronized to with the clock on the NTP server.
2. If the CARESCAPE Gateway is configured as time source, when the difference

with the CARESCAPE Gateway clock and the CARESCAPE Network MC

Equipment overview
network time is greater than 2 minutes, the CARESCAPE Gateway sends a time
update message to the CARESCAPE Network MC network time master. See
Time synchronization properties configuration on page 7-23.
3. The time master receives the update and broadcasts the time change to other
devices on the network.
NOTE
CARESCAPE Gateway also has the ability to act as the NTP server for the S/5
Network.
High speed data interface (HSDI)

Overview
The CARESCAPE Gateway HSDI provides a near real-time data feed obtained from
patient monitoring devices. Waveforms and parameter data are supported for this
feature.
Depending on the custom configuration at your site, a PID entered at both the patient
monitor device and the HIS may be required to ensure proper transfer of patient data.
If this information is required at the patient monitoring device, it must be entered
while the patient is admitted and on-line. The CARESCAPE Gateway stops
transferring data if the acquisition device goes off-line or is discharged.
HSDI
The CARESCAPE Gateway provides near real time data streaming, including
waveform and numerics, in an XML based protocol. This provides patient data in a
flexible protocol to meet a variety of user needs.

Equipment overview
The following is a description of the near real time data stream:
1. Patient data is acquired on the CARESCAPE Network MC and the S/5 Network,
and enters the CARESCAPE Gateway via an Ethernet network connection.
2. Patient data from both networks is sent to the HSDI adaptor, where it is converted
into XML format.
3. XML data is sent to the CARESCAPE Network IX where it is accessed and used
where appropriate.
HSDI guidelines
CAUTION
proper procedures.
CAUTION

Equipment overview
 The acquisition device must be listed in the CARESCAPE Gateway’s acquisition

Bedlist to have data transferred to the HIS(s). If a device’s name is changed to
one that is not on the bedlist, data collection for that device will stop.
Event notification
When configured, the CARESCAPE Gateway will send a notification when the
system receiving HSDI data from the CARESCAPE Gateway improperly
disconnects. The error notification may be delivered via email or another notification
method, depending on the site implementation. The system administrator configures
the addresses to which the event notification messages will be sent.
Service utilities
Utility/diagnostic tool use
For a detailed description of many service utility and diagnostic tools for the
CARESCAPE Gateway hardware, refer to the HP provided documentation, supplied
on the Documentation CD-ROM. See Related documentation on page 1-4.
Service logons
Logon Description User Name Password
FE Logon service *
Power User Logon biomed ChangeMe
FE VNC Logon prism1,3,5,7
iLO See Connecting to iLO on page 2-21.
BIOS Logon (ROM-Based Setup Utility) ungsrvc
*Contact GE for password information.
NOTE
The Power user logon is used for all three interfaces (Operating System Logon,
Webmin Logon and HP System Management Homepage User Logon).
Therefore, when the biomed password is changed it is changed for all three
interfaces.

Equipment overview
iLO
Overview
NOTE
To utilize the iLO remote console in single cursor mode Java Runtime
Environment (JRE) 1.4.2 or greater is required. For more details, refer to
java.sun.com.
NOTE
iLO requires line voltage supplied to the HP Proliant power socket to operate.
NOTE
Whenever the iLO remote console function is accessed from a remote location,
the blue UID light on the front and the back of the unit flashes.
iLO is a utility built into the CARESCAPE Gateway server. This utility operates
using its own dedicated CPU, entirely separated from the CARESCAPE Gateway.
Because of this, iLO provides functions truly independent of CARESCAPE Gateway,
allowing for remote troubleshooting even if CARESCAPE Gateway is shut down (but
still plugged into AC line power).
Additionally, iLO has a Remote Console feature, allowing you remote access to the
CARESCAPE Gateway desktop. See iLO remote console/desktop on page 2-22.
Also refer to the HP Integrated Lights-Out User Guide. See Related documentation
on page 1-4.
Connecting to iLO
If the CARESCAPE Gateway is in a powered-down state, start it up. See Powering on
the CARESCAPE Gateway on page 3-9.
1. Start the internet explorer application and navigate to the CARESCAPE Gateway
iLO IP address. The addressing syntax is: https://[iLO IP Address].
NOTE
The IP address of the iLO connection port should be displayed on a label

attached to the CARESCAPE Gateway cover. If this IP address does not
allow a connection, see the network administrator or contact GE technical
support for a review of the network design file.
2. Login to iLO.
NOTE
CARESCAPE Gateway iLO information is displayed on a label on the cover

at the front left corner. Use this information to logon to iLO.

Equipment overview
Remote desktop utilities

iLO remote console/desktop
iLO allows remote access to the CARESCAPE Gateway desktop.
NOTE
Microsoft .NET Framework 3.5 is a requirement for using the Integrated Remote
Console.
To access the remote console:
1. Login to iLO.
2. Select Remote Console > Remote Console.
3. In the Integrated Remote Console section, click Launch.

Equipment overview
VNC
VNC is an alternate remote desktop utility.
1. Start the VNC client.
2. Type the VNC password into the Password field. See Service logons on page 2-
20. Click OK.
Webmin overview
NOTE
The service laptop IP address must be configured before using Webmin. See
Service laptop connection on page 3-9.
NOTE
Internet Explorer session cookies must be enabled when using Webmin.
Webmin logon
Webmin is an internet-based web application used for CARESCAPE Gateway
administration and service. Webmin requires Microsoft Internet Explorer V5.5 SP2 or
later. The browser will need to be refreshed to view the most current information in
Webmin.
For Webmin logon username/passwords, see Service logons on page 2-20.
Running browser from within an iLO/VNC session

1. Start an iLO or VNC remote desktop session. See Remote desktop utilities on
page 2-22.
2. Double-click the Webmin icon on the CARESCAPE Gateway remote desktop in

the iLO or VNC session window.
3. Login to Webmin. See Service logons on page 2-20.
Running browser locally

1. Start the Internet Explorer locally (on the service laptop/remote computer).
2. Type https://[CARESCAPE Gateway IP address]:8080 into the Address field

and press Enter.
NOTE
[CARESCAPE Gateway IP address] is the CARESCAPE Network IX IP

address for the CARESCAPE Gateway.
3. Login to Webmin. See Service logons on page 2-20.

Equipment overview
Webmin organization
Webmin functionality is divided across a number of different windows. Refer to the
following locations for more information about functionality associated with each
window:
 Information tab on page 2-24

 Configuration tab on page 2-25
 Diagnostics tab on page 2-26
Information tab
Link Name Description
View Server Configuration Display of CARESCAPE Gateway configuration

information, such as: serial numbers, operating system
version, hostname, installation hotfixes, software
versions, configured interfaces, and Cloverleaf
licenses. See View server configuration on page 7-10.
Logout Webmin application logout. Returns user to the login

window.

Equipment overview
Configuration tab
Backup and Restore CARESCAPE Gateway configuration backup/

restore/restore data stores to factory defaults. See
Backup and restore on page 7-5.
CARESCAPE Gateway Provides the following functions:

Configuration
 CARESCAPE Network and S/5 Network bed
list configuration. See CARESCAPE Network
MC bed list on page 7-13 and S/5 Network bed
list on page 7-18.
 Setup, including the following:
 Licensing
 CARESCAPE Gateway properties
 Time master properties
 Error notification
 HSDI client information
 Dashboard - Display current performance
information.
Cloverleaf License Management Save and verify the Cloverleaf license.
Database Viewer ADT Database query.
Host Asset Settings CARESCAPE Gateway serial number

configuration. See Display serial number
information on page 7-25.
Interface Backup Back up individual Cloverleaf sites.

Equipment overview
Interface Management Deploy and activate Cloverleaf sites.
Interface Monitor Display error count information for the Cloverleaf

sites.
Lights-Out Management Configuration and restart of the HP iLO

Management Processor.
Network IP address configuration. See CARESCAPE

Network MC, IX and S/5 Network configuration on
page 3-14.
Password Management Management of the password for the biomed user

account.
Purge Configuration Configuration of ADT Database purge rules.
Remote Service Configuration for the InSite ExC (remote access)

engine.
Sendmail Configuration Configuration of sendmail for forwarding locally

generated email.
Software Management Software package search/view/installation. See

Software management on page 7-33.
System Manager Stop and start applications on the system.
System Time Interface for setting the local clock and NTP server
settings.
Logout Webmin application logout. Returns user to the

login window.
Diagnostics tab

Equipment overview
HP System Management Includes HP functions for the CARESCAPE Gateway

hardware, such as: HP System management homepage,
survey utility report, version control agent, insight
management Agent, Array configuration utility. See HP
system management on page 5-2.
Log Viewer Display of various types of CARESCAPE Gateway log

files. Includes utility for searching log files for a specific
text string. See CARESCAPE Gateway log viewer on
page 5-37.
Network Ports Utility for viewing the connected Ethernet ports and
modifying speed and duplex settings.
Network Test Interface for ping, traceroute and TCP port testing.
Process Viewer View running processes on the system.
SMART Drive Status Display predictive failure information for the attached hard
drives.
System Availability Display system up-time statistics information. See System

availability on page 5-2.
System Utilization Historical statistics on system resources, such as CPU,

memory and key application performance metrics.
Upload and Download Upload files to, or to download files from, the
CARESCAPE Gateway. See Upload/download files on
page 7-25.
Webmin Actions Log Provides audit reporting for the Webmin interface.
Logout Webmin application logout. Returns user to the login

window.
Start/stop CARESCAPE Gateway using Webmin

Webmin provides a utility allowing remote CARESCAPE Gateway application
starting, stopping and restarting.
1. Logon to the Webmin application. See Webmin logon on page 2-23.
2. Select Configuration > System Manager.
3. Click the following buttons as required:
 Disable Apps — Stops/disables the selected server subsystems (displayed

only if the server subsystems are enabled).
 Enable Apps — Starts/enables the selected server subsystems (displayed
only if the server subsystems are disabled).
 Restart — Restarts the selected server subsystems.
 Start — Starts the selected server subsystems.
 Stop — Stops the selected server subsystems.
NOTE
Buttons are displayed/hidden depending upon sever status.

Equipment overview
4. Click the details link in the Subsystems Status list to view current subsystem
process and state information.
Bootup and shutdown using Webmin

NOTE
The CARESCAPE Gateway will not boot if a USB drive is connected to one of
the USB ports. Remove all USB drives before starting or rebooting.
The Webmin application provides a remote bootup/shutdown function.
3. To reboot the CARESCAPE Gateway, click Reboot System. When prompted in

the Reboot window, click Reboot System.
4. To shut the CARESCAPE Gateway down, click Shutdown System. When

prompted in the Shutdown window, click Shutdown System.

3 Installation

Installation
General information
Required training
Proper training is required prior to installing or configuring the CARESCAPE
Gateway. Consult with the GE to determine specific training needs. GE service
representatives will perform the initial installation of the CARESCAPE Gateway.
Read and fully understand the pre-installation requirements. Verify all requirements
are met before installing the CARESCAPE Gateway system.
Before installing the CARESCAPE Gateway, read, understand and follow the
instructions and information in the appropriate HP documents. The documents
contain specific information about rack mounting and other useful information about
the CARESCAPE Gateway hardware installation. See Related documentation on
page 1-4.
Pre-installation requirements
All associated network upgrades and rack/mounting preparations must be completed
prior to installation.
Site survey
CAUTION
LOSS OF FUNCTION/PERFORMANCE—A site survey must be
performed before installing the CARESCAPE Gateway. Failure to
perform a site survey may lead to improper performance of the
CARESCAPE Gateway and may affect the performance of the
CARESCAPE Network as well.
Site surveys identify installation requirement specifics. They are performed by

authorized GE personnel.
The remainder of the pre-installation requirements section is a general overview of

topics included/considered during a site survey.
Physical environment
WARNING
SHOCK HAZARD—The CARESCAPE Gateway must not be
located in the patient environment as a shock hazard may exist. The
CARESCAPE Gateway is IEC 60950 certified equipment which
may not meet the leakage requirements of patient care area
equipment.
The CARESCAPE Gateway operates reliably within normal office environmental

limits. The installation location must be:

Installation
 Clean and reasonably free of excess dust. Dust accelerates system wear.
 Well ventilated and away from sources of heat.
 Away from sources of vibration or physical shock.
CAUTION
INCORRECT PATIENT DATA — Provide for the appropriate
installation. See Technical specifications on page D-1. Failure to
WARNING
SHOCK HAZARD/PERSONAL INJURY—Do not install the
CARESCAPE Gateway in a patient care/caregiver area. It should be
installed and located with other IT equipment, such as in a server
rack or cabinet. For additional physical environment requirements,
refer to the HP ProLiant DL360 G7 Server Maintenance and Service
Rack mounting requirements

The CARESCAPE Gateway is designed for rack mount installation. It should always
be installed in a suitable 4 post rack mount.
WARNING
PERSONAL INJURY/EQUIPMENT DAMAGE—Observe the
following guidelines associated with rack stability:
secured together.
time.
Read and follow rack mounting instructions in the appropriate HP
documentation, packaged with the CARESCAPE Gateway. See
Site survey findings should determine rack requirements and equipment orders
supporting the installation.
NOTE
Rack mounting/equipment must be provided before the CARESCAPE Gateway

installation can occur.

Installation
The rack must be installed in a location providing proper environmental, ventilation,

power, grounding, EMI/RF, and network requirements, according to the information
in this section and the referenced documentation.
Ventilation
NOTE
Do not position the CARESCAPE Gateway in an enclosed area that may restrict
dissipation of generated heat. The CARESCAPE Gateway uses an internal forced
air cooling system. Any air flow restrictions may cause a rise in internal
temperature which may result in equipment failure.
The CARESCAPE Gateway produces heat and must be physically located in an area
which allows ample air circulation to properly dissipate the heat.
Ventilation clearances
Keep the CARESCAPE Gateway ventilation openings free of obstructions. The
CARESCAPE Gateway rack installation location should provide the following
minimal clearances for the DL360 G7 Server:
 In front of rack: 63.5 cm (25 in)

 In back of rack: 76.2 cm (30 in)
 Between racks: 121.9 cm (48 in)
NOTE
Racks with forced-air ventilation systems may require smaller ventilation

clearances.
EMI/RF interference
CAUTION
INCORRECT PATIENT DATA —The CARESCAPE Gateway
should be isolated from strong electromagnetic fields and electrical
noise produced by electrical devices such as:
 Elevators
 Copy machines
 Air conditioners, large fans
 Large electric motors
 Radio and TV transmitters
 High frequency security devices
 High-load medical devices (e.g., imaging, defibrillators, etc.)
Power/grounding requirements
For additional power/grounding requirements, refer to the HP ProLiant DL360 G7
Server Maintenance and Service Guide. See Related documentation on page 1-4.

Installation
Power requirements
A properly grounded duplex wall receptacle should be provided for the CARESCAPE
Gateway. The wall receptacle must be installed in an approved junction box. Use only
a 3-prong, polarized, medical-grade wall receptacle to accept the CARESCAPE
Gateway 3-prong polarized power cord plug. If using dual power supplies, an
additional 3-prong, polarized, medical-grade wall receptacle will be required.
Receptacle wiring must satisfy all applicable IEC and UL specifications, applicable
building codes, and local electrical inspection regulations. Wiring for international
wall receptacles must comply with all internal standards agencies within the specific
country. The overall current load on the branch circuit supplying power to the
CARESCAPE Gateway must not exceed 80% of the current rating for that circuit.
Grounding requirements
To ensure safety and proper operation, the CARESCAPE Gateway must be properly
grounded in accordance with all applicable IEC and UL specifications, applicable
building codes, and local electrical inspection regulations. For international
installations, grounding must comply with all internal standards agencies within the
specific country.
The common ground point for wall receptacles should be connected to the nearest
equipotential ground through a bonded grounding system. If a bonded grounding
system is not available, the ground pin of each wall receptacle must be individually
connected (using 10 AWG stranded copper grounding cable) to a central grounding
point. Do not jumper the ground pins of the receptacles together.
The grounding system must not carry current, such as a grounded neutral, since the
current flow could produce potential differences along the ground path. Potential
differences are a shock hazard source for equipment users and patients. All grounded
objects at the installation site must be at the same ground potential.
Network requirements
CAUTION
INCORRECT PATIENT DATA — A secure data link (IX network
router) must be installed and properly configured between the
CARESCAPE Network IX and the hospital enterprise network. The
connection between the hospital network and the CARESCAPE
Network IX requires the certain ports to be opened for the
CARESCAPE Gateway. To determine which ports need to be
opened for the CARESCAPE Gateway, refer to Router supported
services on page F-1.

Installation
Physical requirements
CAUTION
IMPAIRS OPERATION OF OTHER DEVICES — The
CARESCAPE Gateway requires that the system run on Full-Duplex
Fast Ethernet (100Mb/s) or Gigabit (1000Mb/s) networks. The
system is configured to use auto-negotiated speed and duplex by
default and this is the recommended operating mode. It is possible to
configure the system to only use 100Mb/s Full-Duplex (disabling
auto-negotiation). In order to use this mode, the network switch
must have an identical configuration.
The network must be a fully-switched network.
Category 5 100Base-T network drop cables with RJ-45 connectors are required for
the following CARESCAPE Network connections:
 Two CARESCAPE Network IX (IX Network and iLO)

 CARESCAPE Network MC
 S/5 Network
NOTE
The CARESCAPE Gateway optionally supports redundant networking, in which

case, a redundant network cable will be needed for each associated network
connection.
NOTE
The CARESCAPE Network IX and S/5 Networks may be combined into a single
network.
Additionally, the following network configuration values are required for

CARESCAPE Gateway installation:
 CARESCAPE Network IX/MC and S/5 Network IP addresses and subnet mask
values.
 CARESCAPE Network IX IP address for a CARESCAPE Gateway iLO
connection.
 Routing/gateway configuration settings, if applicable.
If CARESCAPE Network time master services will be used, at least one of the
following additional requirements must be met:
 It is highly recommended that an operational CIC Pro center always be available

on the network. If any mobile CIC Pro centers are placed on the network, their IP
addresses must be numerically less than the IP addresses of all CIC Pro centers
on the network.
 If no CIC Pro centers exist on the network, the IP addresses of wireless patient
monitors must be numerically less than the IP addresses of hardwired patient
monitors.

Installation
Pre-installation verification
Verify the following items are complete before proceeding with the installation.
 A site survey for the installation must be completed. See Site survey on page 3-2.
 Ensure that the location meets the proper mounting requirements for the
CARESCAPE Gateway. See Rack mounting requirements on page 3-3 for proper
CARESCAPE Gateway mounting requirements. Mounting hardware and
location must provide for the following requirements:
 Physical environment requirements. See Physical requirements on page 3-6.
 Proper ventilation and ventilation clearances to provide proper
CARESCAPE Gateway cooling. See Ventilation on page 3-4.
 The CARESCAPE Gateway must be positioned away from possible sources
of EMI/RF interference.
 The CARESCAPE Gateway must be provided with the proper power and
grounding requirements. See Power/grounding requirements on page 3-4.
 A secure data link (IX network router) must be installed and properly configured
between the CARESCAPE Network IX and the hospital enterprise network. See
Network requirements on page 3-5.
Installation
Obtain required installation tools/equipment
The following tools and equipment are required for the CARESCAPE Gateway
installation:
 Normal hand tools, such as flat/phillips screwdrivers, adjustable wrenches, etc.

 Laptop with the following:
 Ethernet port
 Windows OS NT/2000/ME/XP/7
 .NET Framework v3.5 (for iLO3 remote console)
 Internet Explorer version 6 SP3, or later
 JRE version 1.4.2 or greater
 One of the following: VNC client, KVM, or web browser that supports iLo3
Install the CARESCAPE Gateway server on the rack/shelf
CAUTION
EQUIPMENT DAMAGE—The CARESCAPE Gateway is static

Installation
CAUTION
INCORRECT PATIENT DATA — Provide for the appropriate
installation. See Technical specifications on page D-1. Failure to
Read and follow all mounting option instructions in the HP ProLiant DL360 G7
Network connections
Overview
CAUTION
TRIPPING HAZARD/LOSS OF FUNCTION—All cabling must be
installed to protect against tripping and accidental disconnection of
the cables. All external cabling used with the CARESCAPE
Gateway must be routed so as not to interfere with access or
operation of the system. Failure to follow this instruction could
result in personal injury or equipment damage.
Verify all network connections are live and operational before connecting the network
drop cables to the CARESCAPE Gateway. For a diagram of network connections, see
Network connections/back panel on page 2-3.
NOTE
Network connections depend on the site’s requirements.
CARESCAPE Network MC connection

Connect CARESCAPE Network MC drop cable(s) to the CARESCAPE Network
MC port on the back of the CARESCAPE Gateway.
CARESCAPE Network IX connection

Connect CARESCAPE Network IX drop cable(s) to the CARESCAPE Network IX
port on the back of the CARESCAPE Gateway.
S/5 Network connection

Connect S/5 Network drop cable(s) to the S/5 Network port on the back of the
CARESCAPE Gateway.

Installation
iLO connection
Connect a CARESCAPE Network IX drop cable to the iLO port on the back of the
CARESCAPE Gateway. For more information about iLO, see Integrated lights-out
(iLO) connection on page 2-4.
Powering on the CARESCAPE Gateway

NOTE
For the CARESCAPE Gateway shutdown procedure, see Remove power from
the CARESCAPE Gateway on page 4-4. The power switch is not an On/Off
switch. It is an On/Standby switch.
1. Momentarily hold the CARESCAPE Gateway power switch in the On position,

then release it. Allow sufficient time for the CARESCAPE Gateway to complete
its power-on cycle.
Power switch
2. The power switch turns green after a successful power on.
NOTE
The power switch turns amber when the CARESCAPE Gateway is in

standby mode.
Service laptop connection

Overview
CAUTION
INCORRECT PATIENT DATA/IMPAIRS OPERATION OF
OTHER DEVICES — Connect the laptop to the router or the iLO
port to prevent the potential contamination of malware.
NOTE
Normally, a service laptop is used to remotely configure the CARESCAPE

Gateway during installation. However, non-standard networks, or conflicting
network device identification/configuration may prevent proper service laptop
connection.

Installation
1. Connect an Ethernet cable from the laptop to the service port on the secure data
link (IX network router). Alternatively, you can connect the service laptop to the
iLO port of the CARESCAPE Gateway and use Webmin via the iLO remote
console to configure the CARESCAPE Gateway IP addresses.
2. Start up the service laptop computer.
Change the service laptop IP address

NOTE
The IP address on the service laptop must match the CARESCAPE Gateway
CARESCAPE Network IX network domain. The network domain is defined by
the first numbers used for IP addressing and the subnet mask. If a default
gateway is defined, this would also be a factor.
NOTE
If firewall programs are running on the laptop, disable the service to avoid
interference with the installation.
Windows NT
1. From the Windows taskbar, click Start > Settings > Control Panel.
2. Click the Network icon in the Control Panel window.
3. On the Protocol (or Configuration) tab, select the appropriate TCP/IP Ethernet
adapter for your network card.
4. Select Properties.
5. Record the current IP address and subnet mask so you can restore them later.
6. Click Specify an IP address.
7. Type the IP address, subnet mask and default gateway values matching the
CARESCAPE Network IX network domain for the CARESCAPE Gateway. For
example:
IP Address: 172.18.x.x
Netmask: 255.255.0.0
Default Gateway: 172.18.254.254
8. Click OK.
9. Click OK.
10. Click Yes to restart the service laptop.
Windows 2000
1. From the Windows taskbar, click Start > Settings > Network and Dial-up
Connections.
2. Right-click Local Area Connection.

Installation
4. Click Internet Protocol (TCP/IP).
5. Click Properties.
7. Click Use the following IP address.
example:
Netmask: 255.255.0.0
9. Click OK.
10. Click OK.
11. For Windows 2000, instead of restarting the service laptop, you can click Start >
Settings > Network and Dial-up Connections, right-click on Local Area
Connection, select Disable and then right-click again and select Enable.
Windows XP
1. From the Windows taskbar, click Start > All Programs > Accessories >
Communications > Network Connections.
example:
Netmask: 255.255.0.0
9. Click OK.
10. Click OK.
11. For Windows XP, instead of restarting the service laptop, you can click Start >
Settings > Network and Dial-up Connections, right-click on Local Area
Connection, select Disable and then right-click again and select Enable.

Installation
Windows 7
1. From the Windows taskbar, click Start > Control Panel > Network and Internet
> View Network Status and Tasks > Change adapter settings.
example:
Netmask: 255.255.0.0
9. Click OK.
10. Click OK.
11. For Windows 7, instead of restarting the service laptop, you can right-click on
Local Area Connection, select Disable and then right-click again and select
Enable.
Service laptop iLO/Webmin logon

Internet Explorer session cookies must be enabled when using Webmin.
Logon to CARESCAPE Gateway iLO and Webmin. See Webmin logon on page 2-23
and Connecting to iLO on page 2-21.
CARESCAPE Gateway configuration

iLO IP address configuration
WARNING
LOSS OF FUNCTION/DATA LOSS—Be extremely careful not to
data loss.

Installation
NOTE
NOTE
The CARESCAPE Gateway iLO IP address can be obtained by attaching a

keyboard, monitor, and mouse, and pressing F8 during bootup to enter the iLO
settings screens available in BIOS configuration. The biomed or service login is
used when accessing this function. See Service logons on page 2-20.
For more information about the iLO utility, see iLO remote console/desktop on
page 2-22.
Standard installations use a default unique iLO IP address value set during
manufacturing. Refer to the site survey to determine if the iLO IP address value needs
to be reconfigured for the installation.
If necessary, configure the CARESCAPE Network IX iLO IP address for the

CARESCAPE Gateway. Perform the following steps:
2. Select Configuration > Lights-Out Management.
3. If required, change the iLO IP Address and Netmask values.
4. If required, change the Default Router (IP address of the router) value.
5. Click Save.
6. Click Confirm to configure the network changes.
7. Attach a new label with the new iLO IP address value to the CARESCAPE
Gateway cover.
8. Document the iLO IP address changes as appropriate.

Installation
CARESCAPE Network MC, IX and S/5 Network configuration

IP address configuration
WARNING
data loss.
NOTE
Set the CARESCAPE Network IP address using an iLO connection. If a remote

Webmin connection is used to change the CARESCAPE Network IX IP address
with the firewall enabled, the Webmin connection to the CARESCAPE Gateway
will be broken.
NOTE
Standard installations use default unique IP address values set during manufacturing.
Refer to the site survey to determine if IP address values need to be re-configured for
the installation.
If necessary, configure the CARESCAPE Network MC, IX and S/5 Network IP

addresses by performing the following steps:
1. In Webmin, select Configuration > Network > Network Interfaces.
2. Click on a network bond Name to configure the network IP address settings.
NOTE
Redundant network connections use the same IP address.
3. Change the Netmask or IP Address settings, as required. Click Save and Apply
to save any changes.

Installation
4. Attach new labels with the new IP address values to the CARESCAPE Gateway
cover.
NOTE
CARESCAPE Gateway IP addresses are specified on the site survey.

Additionally, labels displaying IP address information are attached to the
CARESCAPE Gateway cover.
Default router configuration
WARNING
data loss.
Standard installations use a default IP address value for standard routing set during
manufacturing. This value is what the CARESCAPE Gateway uses to contact the
secure data link (IX network router). Refer to the site survey to determine if the
routing IP address value needs to be re-configured for the installation.
If necessary, configure routing for the CARESCAPE Gateway using the Webmin
Network Interfaces utility by performing the following steps:
1. In Webmin, select Configuration > Network > Routing and Gateways.
2. If necessary, change the Default routes or Static routes settings by entering the
appropriate information in the dropdown menus and textboxes for Interface,
Gateway, Network, and Netmask.

Installation
EXAMPLE:
3. Click Save.
System time/date configuration
CAUTION
INCORRECT PATIENT DATA— The time zone setting on the
CARESCAPE Gateway must match the time zone setting on the
iCentrals from which it is configured to collect data. Otherwise, the
data may be incorrectly time stamped. In addition, it is
recommended that the CARESCAPE Gateway and iCentral clocks
be synchronized to an NTP server.
1. In Webmin, select Configuration > System Time > System Clock Settings.
2. In the System Time window, select the appropriate date, month, year, and time.

Installation
3. Click Apply.
4. In the Time Zone window and verify the correct time zone is coordinated with
the HIS.
NOTE
Time zone and daylight saving time may need to match HIS processing
configuration. Refer to the site survey.
NOTE
To disable daylight saving time (DST) on the system, choose the time zone
GMT + or GMT- the appropriate number of hours for the location.
5. Click Save when finished.
NTP server computer IP address configuration

Enabling the NTP time feature is optional. Refer to the site survey to determine if the
installation requires enabling this feature.
NOTE
Setting the NTP server computer IP Address will have no effect on

CARESCAPE Network time unless the Allow Time Management services
configuration is set to On. See Time synchronization properties configuration on
page 7-23.
1. If necessary, logon to Webmin. See Webmin logon on page 2-23.
2. Select Configuration > System Time > NTPD Settings.

Installation
3. Type the network address of the NTP server into the IP Address textbox and
click Save.
NOTE
Refer to the site survey for the NTP server network address.
4. To ensure connectivity to the NTP server, follow the instructions under Check
NTP configuration on page 4-7.
InSite Exc configuration

2. Select Configuration > Remote Service > Configuration.
3. Type https://us1-ws.service.gehealthcare.com into the Enterprise URL textbox

in the Remote Service Configuration section.
4. Type https://us1-rd.service.gehealthcare.com into the Enterprise Tunnel URL

textbox in the Remote Service Configuration section.
5. Click Save.
6. Select Remote Service > Control from the menu.
7. Ensure the Enabled radio button is selected for Service Agent.
8. Click Save.

Installation
NOTE
Wait until the CARESCAPE Gateway is configured completely before

enabling Event Notification. See iLO SNMP configuration on page 7-4.
9. Restart the firewall.
Password configuration
Overview
As part of installation, it is recommended that customer default passwords (excluding
iLO) are changed for increased security.
NOTE
Construct passwords which conform to accepted password best practices.

Contact the IT department for current password conventions.
Password management
The following procedure can be used to change the password for the users for
Webmin, the operating system, and HP System management.
2. Select Configuration > Password management.
3. Select the Change? checkbox and enter the password in the Password and
Retype Password text boxes for the appropriate username.
4. Click Change.
Error notification configuration

2. Select Configuration > Sendmail Configuration.
3. In the Send outgoing mail via host textbox, enter the email server in Sendmail
options.
4. Click Save and Apply.
5. Select Configuration > CARESCAPE Gateway Configuration > Configuration

> Setup > Error Notification.
6. Set Enable ADT Error Notification to true.
7. Click Update ADT Properties.
8. In the appropriate table rows, enter the appropriate email addresses in text box.
9. Click Update ADT Properties.
10. Repeat for HSDI and click Update HSDI properties.

Installation

Installation
Cloverleaf license configuration

Overview
NOTE
The Cloverleaf license key is linked to CARESCAPE Gateway CARESCAPE

Network IX MAC address values (the redundant IX ports are assigned a single
MAC address).If hardware affecting MAC address values is replaced, a new
Cloverleaf license key is required.
The CARESCAPE Gateway is pre-configured with two external threads on the

his_prod site and one in the vod_prod site. In his_prod, the HIS_Inbound thread is
used for ADT inbound messages and the GE_system_OB thread is used for HL7
outbound results. In vod_prod, the CSG_IB_Request thread is used for servicing
vitals on demand requests. All other threads are pre-configured as vendor threads.
Using Cloverleaf IDE with production licenses, navigate to the Network

Configurator. Right-click on a thread and select Thread Properties. In the Thread
Properties window, there will be two radio buttons: External and Vendor.
Vendor threads are internal threads that are used for inter-process communication
within the server. External threads are threads that connect to external devices over
the network.
Only the necessary number of external threads that are utilized for product features
need to be licensed. When a production license is used that does not allow all the
necessary external threads to be run, the unused threads can either be configured to
not be started, changed to vendor threads, or removed.
Request a license
A qualified GE representative will order the necessary Cloverleaf license to configure
the CARESCAPE Gateway during the initial installation. Please contact GE for any
assistance with requesting additional Cloverleaf licenses.
Configure
2. Select Configuration > Cloverleaf License Management.
3. Copy the license key string — everything between the two lines:
------------------- $HCIROOT/vers/license.dat --------------------
and
-------------------- hcilicset input --------------------
4. Click Edit, enter/paste the license key string into the text box and click Save.

Installation
5. Check the Webmin Cloverleaf License Management utility for valid Cloverleaf
license status. See Cloverleaf license manager on page 7-36.
HIS IP address/port configuration

2. Select Configuration > CARESCAPE Gateway Configuration > Cloverleaf

Thread Startup.
3. In the Server address and Port fields for the his_prod/outbound/GE_system_OB

thread, type the outbound HIS host IP address and port number values according
to the site survey.
4. Select Yes from the External dropdown list and click Save.

Installation
6. Select the Reload System Firewall checkbox and click Restart.
7. Check that the network connection is configured correctly. See Network interface
test on page 4-6.
Check CARESCAPE Gateway status

NOTE
Cloverleaf must be configured with a valid license key before the CARESCAPE
Gateway Service software will run. See Cloverleaf license configuration on page
3-21.
NOTE
Do not enable Application controls until Cloverleaf is properly licensed.
3. If the Disabled is displayed for CARESCAPE Gateway Application in the

Application Subsystem Status table, click Enable Apps button.
4. If the state of any desired subsystem is Off, select the checkbox (to check) for the
appropriate subsystems and click Start.
5. As the server starts, a Starting status message displays.
6. If the subsystems fail to start, see Troubleshooting on page 5-1.

Installation
NOTE
If this is an additional CARESCAPE Gateway on the CARESCAPE

Network, ensure that the ADT functionality is disabled. See CARESCAPE
Gateway license configuration on page 7-28. If ADT is enabled on multiple
ADT servers, ADT requests on the network will fail.
Configure bed list, HIS mappings, and properties

The Bed List, HIS Mappings, and Properties are configured by GE ITPS. See
CARESCAPE Network MC bed list on page 7-13, S/5 Network bed list on page 7-18,
and Properties configuration on page 7-20.
NOTE
The bed list on each CARESCAPE Gateway cannot overlap the bed list on any
other CARESCAPE Gateway.
NOTE
When adding a large number of devices to the bed list, be aware that additional
outbound threads may need to be added in Cloverleaf in order to the message
send rate to the CIS at a safe level. Refer to the CARESCAPE Gateway HL7
Reference Manual.
HL7 outbound configuration

HL7 outbound configuration is performed by GE ITPS. See Common Cloverleaf
configuration changes on page 7-29.
Initial backup
Backup CARESCAPE Gateway application settings
NOTE

the CARESCAPE Gateway configuration is changed to ensure complete system
after the CARESCAPE Gateway configuration changes could result in lost
licensing, interface and application configuration data.
Backup the application settings. See Backup on page 7-6.

Installation
Backup Cloverleaf interfaces

NOTE
The Cloverleaf interface backup procedure should be performed at regular

intervals and/or whenever any Cloverleaf interface is changed to ensure complete
interface restoration if it should become necessary. Failure to perform the backup
procedure after changing any Cloverleaf interface could result in lost interface
configuration and/or HL7 and ADT data.
Backup the Cloverleaf interfaces. See Cloverleaf interface backup on page 7-34.
Cloverleaf thread startup

Cloverleaf Thread Startup allows you to modify Cloverleaf startup as required.
2. Click the CARESCAPE Gateway Configuration > Cloverleaf Thread Startup

link.
3. Disable/enable, and arrange Cloverleaf process startups as required using the ->
and <- arrows, and the up and down buttons. Click Save.
NOTE
If any new sites and threads are added to the Process Start Configuration
table, ensure that they are added to the end. If the standard CSG threads
startup order is changed the CARESCAPE Gateway may not function
properly.
NOTE
Processes are stopped in reverse order from that listed in the Process Start
Configuration > Enabled list.
NOTE
For optimal performance Cloverleaf processes should be started and stopped

in particular order (default processes are arranged in the proper order during
manufacturing).
4. Set the proper Cloverleaf process Thread Autostart Configuration.

Installation
NOTE
Auto-start is updated to the current Cloverleaf Net Config.
NOTE
To reset Cloverleaf process startup configuration to factory defaults, click

Reset to Defaults.
5. Click Save.
NOTE
Threads set to Yes are started as the associated processes start.
Checkout procedure
To verify proper CARESCAPE Gateway operation, perform the checkout procedures.
See Checkout procedure on page 4-5.

4 Maintenance

Maintenance
Schedule
Manufacturer recommendations
In addition to the maintenance information in this manual, also refer to the HP
ProLiant DL360 G7 Server Maintenance and Service Guide for additional
recommendations. See Related documentation on page 1-4.
To make sure the CARESCAPE Gateway hardware remains in proper operational and
functional order, a good maintenance schedule must be adhered to. The manufacturer
recommends the following:
 Checkout procedure and visual inspection should be performed by qualified

service personnel upon receipt of the equipment, one time per year thereafter, and
each time the unit is serviced.
 Cleaning should be performed by service personnel each time the unit is serviced
and one time per year after receipt of the equipment.
Manufacturer responsibility
CAUTION
EQUIPMENT DAMAGE/LOSS OF FUNCTION/PERSONAL
INJURY—The manufacturer does not in any manner, assume the
responsibility for performing the recommended maintenance
schedule, unless an Equipment Maintenance Agreement exists. The
sole responsibility rests with the individuals, hospitals, or sites
utilizing the device. Failure on the part of all responsible individuals,
hospitals or sites, employing the use of this device, to implement the
recommended maintenance schedule may cause equipment failure
and possible health hazards.
Spilled fluids hazard
WARNING
SHOCK HAZARD/EQUIPMENT DAMAGE—If fluids are spilled
on the CARESCAPE Gateway, shut down the unit, remove power
and disconnect all components. Perform the maintenance procedures
listed in this section and document the incident in the repair log. Do
not use the CARESCAPE Gateway if it has been damaged by the
fluid. Fluids spilled on the CARESCAPE Gateway can cause an
electrical shock hazard and may damage the equipment.

Maintenance
Controlling electrostatic discharge damage
CAUTION
EQUIPMENT DAMAGE —The CARESCAPE Gateway is static
All external connector inputs and outputs of the device are designed with protection
from Electrostatic Discharge Damage (ESD). However, if the interior of the device
needs to be accessed for any reason, internal components and assemblies are
susceptible to ESD. This includes human hands, non-ESD protected work stations
and/or improperly grounded test equipment.
The following guidelines help make a service workstation more resistant to the ESD:
 Discharge any static charge you may have built up before handling
semiconductors or assemblies containing semiconductors. This can be done by
touching any bare metal on the CARESCAPE Gateway chassis or cable
connector jacks on the back of the unit. Do this frequently and repeatedly while
working on the unit.
 Wear a grounded, anti-static wristband (3M part number 2046 or equivalent) or
heel strap at all times while handling or repairing assemblies containing
semiconductors.
 Use properly grounded soldering and test equipment.
 Use a static-free work surface (3M part number 8210 or equivalent) while
handling or working on assemblies containing semiconductors.
 Keep the work surface free of nonconducting materials such as ordinary plastic
assembly aids and foam packing.
 Semiconductors and electrical/electronic assemblies should be stored only in
antistatic bags or boxes.
 Do not remove semiconductors or assemblies containing semiconductors from
antistatic containers (Velo-stat bags) until they arrive at the work surface and
until absolutely necessary.
 Make sure power to an assembly is turned off before removing or inserting a
semiconductor.
 Do not touch semiconductor leads, pins or circuitry unless absolutely necessary.
These guidelines cannot guaranty a 100% static-free workstation, but greatly reduce
the potential for failure of any electrical/electronic assemblies due to electrostatic
discharge.

Maintenance
Visual inspection
CAUTION
EQUIPMENT DAMAGE—Follow the electrostatic discharge
damage control procedures. See Controlling electrostatic discharge
damage on page 4-3. The CARESCAPE Gateway is extremely static
sensitive. If the proper ESD precautions are not followed, damage to
the unit could result.
Carefully inspect the CARESCAPE Gateway and its components upon receipt of the
equipment, one time each year thereafter, and each time the equipment is serviced.
To perform a complete visual inspection of the equipment, follow these steps:
1. General Inspection: Inspect the external surfaces of the CARESCAPE Gateway

components for obvious physical damage. Do not use the device if physical
damage is evident. Refer damaged equipment to qualified service personnel for
repair.
2. Fans: Inspect all cooling fans in the CARESCAPE Gateway to make sure they
are in good working order and are not clogged with dust. Proper fan operation is
vital for preventing the CARESCAPE Gateway from overheating.
3. Connectors: Inspect all external connectors for damaged pins, prongs and
connector housings. Refer damaged equipment to qualified service personnel for
repair. Ensure that all connections are properly seated and secure.
4. Cable Insulation: Inspect all cables, insulation, strain-reliefs and connectors for
damage, cracks or degradation. Refer damaged equipment to qualified service
personnel for repair.
Cleaning
Remove power from the CARESCAPE Gateway
WARNING
SHOCK HAZARD—After performing a safe shutdown, disconnect
the power cord(s) from the wall outlet to remove power from the
CARESCAPE Gateway. The on/off button on the front panel does
not disconnect the CARESCAPE Gateway from AC power.
Additionally, wait 40 seconds after disconnecting the

CARESCAPE Gateway power cord from the wall outlet. The
computer remains energized for a period of time after shutdown.
If these precautions are not followed, the possibility of electrical

shock exists.
1. Shut down the CARESCAPE Gateway.

Maintenance
2. Disconnect the power cord(s) from the back of the CARESCAPE Gateway.
NOTE
When unplugging, pull on the plug, not the cord.
Internal components
CAUTION
THERMAL HAZARD—Internal components, especially power
supplies, get extremely hot when the CARESCAPE Gateway is in
operation. Shut down the CARESCAPE Gateway and allow it to
cool before touching any internal components.
1. Follow electrostatic discharge precautions. See Controlling electrostatic

discharge damage on page 4-3.
2. Remove the CARESCAPE Gateway cover.
3. Carefully remove any accumulated dust, manually or by using a vacuum if

available.
Fans
Remove all of the dust from the fans and the fan intakes as they usually accumulate
the most dust. Accumulated dust can clog the fans and fan intakes and prevent proper
cooling.
Ventilation ports
Make sure all dust and debris is cleared away from the ventilation ports on the front
and back of the CARESCAPE Gateway.
Reconnect power to the CARESCAPE Gateway

1. Reconnect the power cord(s) from the back of the CARESCAPE Gateway.
Checkout procedure
About the checkout procedure
The checkout procedure process provides a method of verifying operational and
functional performance without having to disassemble the unit. Failure to attain the
prescribed results indicates a need for configuration or repair.
Perform the checkout procedures upon receipt of the equipment, every year thereafter,
and each time the unit is serviced.

Maintenance
The checkout procedure process is based on the assumption that the equipment being
tested is using known, good cables. It also requires that the user be familiar with the
operation of the system.
Perform all of the checkout procedures included in this section to completely test the
system for proper function and operation.
Check for valid network connections

Network interface test
The network interface test confirms physical connection and communication through
the network interface cards.
2. Select Diagnostics > Network Test.
3. See the following table for instructions on performing various tests.
To perform this test Follow these steps
Verify connectivity to a 1. In the first Address field, enter the host name or IP
remote device address of the network interface you want to test.
2. Click Ping.
Trace the network route 1. In the second Address field, Enter the host name or IP
to a remote device address of the network interface you want to test.
2. Click Traceroute.
Connect to a TCP port 1. In the third Address field, enter the host name or IP
on a remote device address of the network interface you want to test.
2. Enter the port number in the Port field.
3. Click TCP Test Port.
If the test is successful, a success message is displayed at the top of the screen. If
the test fails, a failure message is displayed.
Check time settings

Ensure the clock on the CARESCAPE Gateway matches the local time and that the
time zone is properly set for handling of DST. Furthermore, if the CARESCAPE

Maintenance
Gateway is configured to collect data from iCentrals the time zone setting must all
match.
1. In Webmin, select the Configuration > System Time > System Clock Settings.
2. Verify the time is correct.
3. Verify the correct time zone setting is selected.
4. Click Apply or Save when finished.
Check NTP configuration

If NTP is configured, verify connectivity to the NTP server.
1. In Webmin, select Configuration > System Time > NTPD Settings.
2. Verify that the IP address of the NTP server is entered correctly.
NOTE
Refer to the site survey for the NTP server IP address.
3. Click Save.
4. In Webmin, select the Diagnostic tab.
5. Select Network Test.
6. Enter the IP address of the NTP server and click Ping.
A message will result indicating if the connection was successful or failed.
Test connection to HL7 and HSDI clients

Pinging the CARESCAPE Gateway clients provides a valid test for communication
between the CARESCAPE Gateway and the HSDI client and VOD client. The
HL7receiving system for HL7 outbound trends can be further tested with a port
connection test. The port number can be found in Webmin > Configuration >
CARESCAPE Gateway Configuration > Cloverleaf Thread Startup >
GE_system_OB thread.
1. In Webmin, select the Diagnostic tab.
2. Select Network Test.
3. Enter the network address of the client and click TCP Test Port.
A message will result indicating if the connection was successful or failed.
4. Additionally, for the HL7 receiving system, enter its port number and click TCP
Test Port.
Test HSDI disconnect email notification

1. In Webmin, select Configuration > Sendmail Configuration.

Maintenance
2. Confirm the email server IP address is shown in the Send outgoing mail via host
textbox. If not, See Error notification configuration on page 3-19.

> Setup > Error Notification.
4. Confirm current value for High Speed Data Interface Disconnect Notification is
set to true. If not, select true and click Update HSDI Properties. Then click
Return to Error Notification Properties Management.
5. Test emails will be sent to the email address(es) listed in the default email address
field. If necessary, add a test email address in the new value field and click
Update HSDI Properties. Then click Return to Error Notification Properties
Management.
6. Click Send Test Email.
7. Confirm email receipt at specified email address. This may take several minutes.
8. Reset any values or email addresses modified during this test and click Update
HSDI Properties.
Check application subsystems status

1. In Webmin, select Configuration > System Manager.
2. For all CARESCAPE Gateway application subsystems, except Reload System

Firewall, ensure that the Application mode is Enabled and the Watchdog
column contains (Last check passed.)
NOTE
For any subsystem that is not Enabled and/or the Watchdog column does not
contain (Last check passed.), enable the subsystem.
Check for remote VNC and Webmin connectivity

NOTE
The remote computer must be configured properly before accessing the system
through VNC. See Service laptop connection on page 3-9.
1. Using a remote computer, start a VNC session, and logon to the CARESCAPE
Gateway desktop. See VNC on page 2-23.
2. Open an internet browser and log in to Webmin. See Webmin overview on page
2-23.
Check for InSite ExC connectivity

Contact GE Technical Support to verify that the CARESCAPE Gateway is
communicating with the GE back office.

Maintenance
Check for system management homepage connectivity

1. Using a remote computer, logon directly to the CARESCAPE Gateway System
Management Homepage. See HP system management on page 5-2.
2. Start Internet Explorer on the remote computer and type https://[CARESCAPE

Gateway CARESCAPE Network IX IP address]:2381 into the Address field
and press Enter.
3. Ensure that the page is displayed.
Check for iLO connectivity

Check for iLO connectivity by logging on to CARESCAPE Gateway iLO. See
Connecting to iLO on page 2-21.
Check iLO event log for critical events

Check the iLO Event Log for critical events:
1. If necessary, logon to iLO. See Connecting to iLO on page 2-21.
2. Click the Information tab and select iLO 3 Event Log from the menu.
3. Search the iLO 3 Event Log window for any Critical Event items.
4. If any critical event items are found, proceed with appropriate actions.
LED status indicators

The CARESCAPE Gateway is equipped with several LED status indicators, which
function to indicate component operation status including the health of the hard
drives. See Front panel LED status indicators on page 5-6 and Back panel LED status
indicators on page 5-6. Also refer to the appropriate HP documentation. See Related
documentation on page 1-4.
A steady green LED indicates normal operation. A blinking green LED indicates an
active link. An amber LED indicates system health has degraded (except on the
power LED, which indicates standby), contact GE and schedule a service check-up or

Maintenance
planned maintenance. A red LED indicates that there is a problem, contact GE for
service immediately.
NOTE
To troubleshoot network connections, see Troubleshooting network problems on

page 5-8. Also, for hardware problems see Field replacement procedures on page
6-2.
System management homepage

Access the System Management Homepage and check for any failed or degraded
component indicators.
NOTE
For more detailed information about the CARESCAPE Gateway System

Management Homepage, click the help link in the top frame in the System
Management Homepage.
Hard drive smart diagnostics

Perform hard drive smart array controller diagnostics for both internal hard drives.
1. In Webmin, select Diagnostics > HP System Management > System

Management Homepage and login if necessary.
2. In the Storage section, select the appropriate:
 DL360 G7 Server — select Smart Array P410i Controller on System Board

3. Select the appropriate port/drive.
4. Scroll to the Predictive Indicators section and verify that it states: S.M.A.R.T.
Status: OK.
Maintenance checklist
Use the following checklist to ensure maintenance completion.
Visual inspection
See Visual inspection on page 4-4.
 General
 Fans
 Connectors
 Cable insulation
Cleaning
See Cleaning on page 4-4.

Maintenance
 Internal components
 Fans
 Ventilation ports
Checkout procedure
See Checkout procedure on page 4-5.
 Check for valid network connections

 Perform network interface test
 Check time settings
 Check NTP configuration
 Test connection to HL7 and HSDI clients
 Check for VNC connectivity
 Check for InSite ExC connectivity
 Check for system management homepage connectivity
 Check for iLO connectivity
 Check iLO event log for critical events
 LED status indicators
 System management homepage
 Hard drive smart diagnostics

Maintenance

5 Troubleshooting

Troubleshooting
HP system management
Overview
The Webmin HP System Management page provides a variety of CARESCAPE
Gateway administration/troubleshooting utilities.
To access the HP System Management page:
2. Select Diagnostics > HP System Management and log into the System
Management Homepage.
3. Click the desired selection on the System Management Homepage for specific
system management utilities. For more information about System Management
Homepage selections, refer to the HP documentation. See Related
NOTE
The System Management Homepage can be accessed directly by specifying

the IP address and port number of the CARESCAPE Gateway System
Management Homepage in the Internet Explorer Address field. The port
number for the System Management Homepage is always: 2381.
For example: https://192.168.2.4:2381
System management homepage

NOTE
The iLO function can be accessed from the System Management Homepage.
See iLO on page 2-21.
The CARESCAPE Gateway System Management Homepage provides real-time,

high-level CARESCAPE Gateway availability and component status information.
The System Management Homepage is available via secure http on port:2381 at the
CARESCAPE Gateway IP address on the CARESCAPE Network IX. It is also
alternatively available through the HP Systems Management link on the Diagnostics
tab in the Webmin application.
A login/password is required to access CARESCAPE Gateway System Management

Homepage. See Service logons on page 2-20.
For more information about the CARESCAPE Gateway System Management

Homepage, click the help link in the top frame in the System Management
Homepage.
System availability
To display system up-time statistics information:

Troubleshooting
2. Select Diagnostics > System Availability.
General fault isolation

For in-depth CARESCAPE Gateway hardware troubleshooting information and
SmartStart CD information, refer to the appropriate HP documentation. See Related
1. Verify that there are no faults. If a fault LED is on, refer to the appropriate
documentation.
2. Verify that the CARESCAPE Gateway applications and subsystems are enabled,
with a status of On. See Start/stop CARESCAPE Gateway using Webmin on
page 2-27.
3. Use the diagnostic tools provided through iLO and HP System Management. See
iLO on page 2-21 and HP system management on page 5-2.
4. Reboot the CARESCAPE Gateway and press F9 immediately when the message
Press “F9” key for ROM-Based Setup Utility displays. Using BIOS
configuration, change the CARESCAPE Gateway boot order to start with the CD
drive.
5. Shutdown the CARESCAPE Gateway, insert the SmartStart CD, and boot up
the CARESCAPE Gateway. Use the SmartStart diagnostics to locate the fault.
For information on using the SmartStart CD for system diagnostics, refer to the
HP documentation and www.hp.com/servers/smartstart.
6. After completing the diagnostics, reboot the CARESCAPE Gateway and press
F9 immediately when the message Press “F9” key for ROM-Based Setup Utility
displays. Using BIOS configuration, change the CARESCAPE Gateway boot
order to start with the hard drive.
For additional assistance, contact GE. Be sure to be ready with CARESCAPE

Gateway configuration information. See View server configuration on page 7-10.

Troubleshooting
Visual inspection
A thorough visual inspection of the equipment can save time. Small things—
disconnected cables, foreign debris on circuit boards, missing hardware, loose
components—can frequently cause symptoms and equipment failures that may
appear to be unrelated and difficult to track.
It is highly recommended that the following steps be performed to remove these

failures as causes of problems.
1. Ensure that power cords are properly plugged into working wall outlets and
securely connected to the CARESCAPE Gateway.
2. If UPS devices are used, ensure the UPS devices are functioning properly, are
plugged into working wall outlets, and are properly connected to the
CARESCAPE Gateway.
3. The green power LED ( ) should be lit indicating that the CARESCAPE
Gateway is on. An amber power LED indicates the unit is in standby mode.
4. Ensure that proper data cabling is used and that all cables are properly connected
to the CARESCAPE Gateway and to the appropriate network connections. See
Cables and connectors on page 5-8.
5. Verify the LED indicators do not indicate red or amber, or that the NIC LEDs are
not off. If any of these conditions exist, see LED status indicator description on
page 5-5.
NOTE
A Server System Configuration label is applied inside the CARESCAPE

Gateway cover.
Server System Configuration label

applied inside the cover
6. Verify that the CARESCAPE Gateway applications and subsystems are enabled,
with a status of On. See Start/stop CARESCAPE Gateway using Webmin on
page 2-27.
If none of the previous steps resolve malfunction issues:
 Turn the CARESCAPE Gateway OFF. See Remove power from the
CARESCAPE Gateway on page 4-4.
 Follow proper ESD precautions. See Controlling electrostatic discharge damage
on page 4-3. Remove the cover and perform an internal visual inspection of the
components.

Troubleshooting
Take the time to make all the recommended visual checks (refer to the visual
inspection table below) before starting any detailed troubleshooting procedures.
Visual Inspection Table
Area Look for the following problems:
I/O Connectors and Interface Cables  Fraying or other damage

 Bent prongs or pins
 Cracked housing
 Loose screws in plugs
 Excessive cable tension or wear
 Secure mounting hardware
Internal Harnesses and Cables  Excessive tension or wear

 Loose connection
 Strain reliefs out of place
Circuit Boards  Moisture, dust, or debris (top and bottom)

 Loose or missing components
 Burn damage or smell of over-heated components
 Socketed components not firmly seated
 Boards not seated properly in edge connectors
 Solder problems: cracks, splashes on board, incomplete feed through, prior modifications or
repairs
Ground Wires/Wiring  Loose wires or ground strap connections

 Faulty wiring
 Wires pinched or in vulnerable position
Mounting Hardware  Loose or missing screws or other hardware, especially fasteners used as connections to
ground planes boards
 CARESCAPE Gateway mounted loosely or near vibration
Power Source  Faulty wiring, especially AC outlet

 Static discharge, resetting problems, and noise resulting from power source problems
Hard Drives Hard Drive not completely seated in the CARESCAPE Gateway
LED status indicator description

Overview
For complete LED information, refer to the HP ProLiant DL360 G7 Server
Maintenance and Service Guide. See Related documentation on page 1-4.

Troubleshooting
Front panel LED status indicators
1 2 3
LED Description
1 HP Systems Insight For a description of the HP Systems Insight Display LEDs, refer
Display to the HP ProLiant DL360 G7 Server Maintenance and Service
2 Unit Identifier (UID) Blue indicates identification is activated.

LED/button
Flashing blue indicates the system is being managed remotely.
Off indicates identification is deactivated.
3 Health Red indicates system health is critical.
Amber indicates system health is degraded.
Green indicates system health is normal.
Back panel LED status indicators

All RJ-45 ports have two indicators:
 The first LED indicates if there is a network connection.

 The second LED indicates if there is activity.
The table following the figure provides a description of the LED statuses.
2 3
1 2 3 1 4

Troubleshooting
LED Description
1 bond 0: CARESCAPE Network IX
Network Card Link On = Network Connection
Blinking = Network Connection and Activity
Off = No Network Connection
Network Card Activity Blinking = Activity
Off = No Activity
2 bond 1: CARESCAPE Network MC
Off = No Activity
3 bond 2: S/5 Network
Off = No Activity
4 iLO
Link On = Network Connection
Activity Blinking = Activity
Off = No Activity
Unit does not boot

1. Verify that all components are connected correctly and the CARESCAPE
Gateway is plugged into a known good outlet.
2. Ensure that all cables are properly seated.
3. Use the diagnostic tools provided through iLO and HP System Management. See
iLO on page 2-21 and HP system management on page 5-2.
4. Reboot the CARESCAPE Gateway and press F9 immediately when the message
Press “F9” key for ROM-Based Setup Utility displays. Using BIOS
configuration, change the CARESCAPE Gateway boot order to start with the CD
drive.

Troubleshooting
5. Insert the SmartStart CD, and start/restart the CARESCAPE Gateway. Refer to
the HP documentation for information about using the SmartStart CD for
system diagnostics. See Related documentation on page 1-4.
6. If system reload/reset is required, see System fail recovery on page 8-2.
7. After completing the diagnostics, reboot the CARESCAPE Gateway and press
F9 immediately when the message Press “F9” key for ROM-Based Setup Utility
displays. Using BIOS configuration, change the CARESCAPE Gateway boot
order to start with the hard drive.
Cables and connectors

For more information about CARESCAPE Gateway connection architecture, see
CARESCAPE Gateway connection diagram on page 2-2.
Required cables/connectors
The CARESCAPE Gateway’s cables and connectors must be in place and physically
secure for the system to function correctly. The following cables are used:
 Power (CARESCAPE Gateway to power source).

 Four RJ-45 (Ethernet CAT 5) connections to the MC Network, the IX Network,
S/5 Network and iLO connection.
Network interface test

For detailed instructions, see Network interface test on page 4-6.
Troubleshooting network problems

NOTE
Verify that the remote computer is configured correctly before troubleshooting

network problems. See Service laptop connection on page 3-9.
Possible Cause/Observation Corrective Action
Check network connections Verify the network connections are secure and correct and make sure that the cables have
not been swapped. See Network connections on page 3-8. Internet Explorer cookies must
Total connection failure be enabled when using Webmin.
Check network LEDs for proper operation. See LED status indicator description on page
5-5.
Verify Cloverleaf License Verify the Cloverleaf license. See Cloverleaf license manager on page 7-36.
Verify HL7/ADT Licenses Verify the HL7 and ADT licenses. See CARESCAPE Gateway license configuration on
page 7-28.

Troubleshooting
There is a suspected problem with the Attempt to ping the CARESCAPE Network MC port on the CARESCAPE Gateway from a
CARESCAPE Network MC remote computer’s command prompt window using this command: ping ip, where ip is the
CARESCAPE Gateway CARESCAPE Network MC IP address. If there is a response to
the ping, the CARESCAPE Gateway network configuration is correct and the network is
working at least intermittently. Work with the site’s network administrator to troubleshoot
possible CARESCAPE Network MC problems.
If the ping fails, attempt to connect directly to the CARESCAPE Gateway CARESCAPE
Network MC port by using a crossover cable between the remote computer and the
CARESCAPE Gateway. Ping the CARESCAPE Gateway from the remote computer. If the
ping is successful, the network settings on the CARESCAPE Gateway or on the hospital’s
switch may be incorrect. If the ping fails, this is most likely a failed Network Interface Card
(NIC). See SmartStart diagnostics on page 5-11.
There is a suspected problem with the Attempt to ping the CARESCAPE Network IX port on the CARESCAPE Gateway from a
CARESCAPE Network IX remote computer’s command prompt window using this command: ping ip, where ip is the
CARESCAPE Gateway CARESCAPE Network IX IP address. If there is a response to the
ping, the CARESCAPE Gateway network configuration is correct and the network is
working at least intermittently. Work with the site’s network administrator to troubleshoot
possible CARESCAPE Network IX problems.
If the ping fails, attempt to connect directly to the CARESCAPE Gateway CARESCAPE
Network IX port by using a crossover cable between the remote computer and the
CARESCAPE Gateway. Ping the CARESCAPE Gateway from the remote computer. If the
ping is successful, the network settings on the CARESCAPE Gateway or on the hospital’s
switch may be incorrect. If the ping fails, this is most likely a failed Network Interface Card
(NIC). See SmartStart diagnostics on page 5-11.
There is a suspected problem with the S/5 Attempt to ping the S/5 Network port on the CARESCAPE Gateway from a remote
Network computer’s command prompt window using this command: ping ip, where ip is the S/5
Network IP address. If there is a response to the ping, the S/5 Network configuration is
correct and the network is working at least intermittently. Work with the site’s network
administrator to troubleshoot possible S/5 Network problems.
If the ping fails, attempt to connect directly to the CARESCAPE Gateway S/5 Network port
by using a crossover cable between the remote computer and the CARESCAPE Gateway.
Ping the CARESCAPE Gateway from the remote computer. If the ping is successful, the
network settings on the CARESCAPE Gateway or on the hospital’s switch may be
incorrect. If the ping fails, this is most likely a failed Network Interface Card (NIC). See
SmartStart diagnostics on page 5-11.
The CARESCAPE Gateway network settings Verify the following CARESCAPE Gateway network settings are correct using Webmin:
are incorrect
Configuration > Network Configuration > Network Interfaces
Configuration > Network Configuration > Routing and Gateways, and
Diagnostics > Network Ports
Diagnostics > Network Test
Confirm the settings with the site’s network administrator, if necessary. GE personnel can
confirm the settings by referring to the site survey.

Troubleshooting
Cannot connect to Webmin
Internet Explorer proxy server settings are Check with the site’s network administrator for the proper proxy server settings.
incorrect
Incorrect network settings on remote computer Check with the site’s network administrator for the proper network settings.
Remote computer connected to the MC Webmin is accessible only through the CARESCAPE Gateway CARESCAPE Network IX
Network or S/5 Network connection.
Remote computer connected to wrong The site may have many networks. Verify with the site’s network administrator that you are
network connected to the correct CARESCAPE Network IX.
There are network problems See Troubleshooting network problems on page 5-8.
There may be a problem with the Examine the CARESCAPE Gateway error logs to check for logged problems.
CARESCAPE Gateway
Service tools connection problems
Cannot connect to Webmin or VNC 1. Log into iLO.
2. Access the remote console (CARESCAPE Gateway desktop).
3. Double-click the Webmin icon and logon to Webmin.
4. Access Configuration > Network > Network Interfaces and check network
settings.
Cannot connect to iLO, Webmin or VNC 1. Attach a keyboard and monitor, or KVM (keyboard/video/mouse) to the
CARESCAPE Gateway.
2. Reboot the CARESCAPE Gateway.
3. Watch for the prompt and press F8 to configure iLO.
4. Use iLO menus to configure iLO network settings.
Administrator login to iLO password not Access Webmin Configuration > Lights-Out Management to restart or reset the
accepted passwords.
Advanced iLO does not work; caused by re- Access Webmin Configuration > Lights-Out Management to restart or reset the
setting to factory default or battery replaced passwords.
with server not plugged into power
Left mouse click does not work in VNC When pressing Alt+Tab, then without letting go of Alt, pressing Alt+Shift+Tab and
releasing, the screen will sometimes stay black with the outline of the selected window
visible with the window switcher dialog still visible. If the screen stays black with the
outline, the left-click may not work anymore.
To fix, press Alt+Tab or Alt+Shift+Tab again. This step may need to be repeated until the
screen renders showing the applications.

Troubleshooting
Emergency CD/DVD eject

Use a bent paper clip to open the CD/DVD drawer as shown in the figure, when the
CARESCAPE Gateway is powered off, or if the CD/DVD drawer fails to open due to
mechanical/software failure.
Internal component troubleshooting

SmartStart diagnostics
The SmartStart CD contains diagnostic tools designed specifically for CARESCAPE
Gateway hardware troubleshooting.
To run SmartStart diagnostics:
1. Connect and log in to iLO. See Connecting to iLO on page 2-21.
3. In the Integrated Remote Console section, click Launch.
4. Insert the CD into the CD/DVD drive as appropriate. The CARESCAPE

Gateway can boot from the SmartStart CD either locally or remotely using virtual
media.
5. Click the Power Management and select Server Power from the menu.
6. Select the Cold Boot button and click OK at prompt.
7. Click in the remote console window to activate it.
8. During reboot, press F9 immediately when the message Press “F9” key for
ROM-Based Setup Utility displays. Using BIOS configuration, change the
CARESCAPE Gateway boot order to start with the CD drive.
9. After the boot order is configured, and the BIOS utility is exited, bootup
continues and the SmartStart utility is loaded.
10. Use the radio buttons/drop down list to select the proper language for the
keyboard you are using and click Next.

Troubleshooting
11. Click Agree in the warranty statement window.
12. Click the Maintenance tab in the SmartStart window and click HP Insight
Diagnostics.
13. Click the Test tab in the HP Insight Diagnostics window.

Troubleshooting
14. Define the following options on the Test tab window:
 Select the Type of Test.

 Select the Test Mode radio button.
 Select the device(s) to test.
 Select the Number of Loops radio button and enter the desired number of
test repeats.
 If desired, select the Stop on First Error checkbox.
15. Click Begin Testing.

Troubleshooting
16. The Status tab shows diagnostic tests progress status. Scroll in the test list as
required to view test progress.
17. The message Testing Completed! displays when diagnostic testing is done. Scroll
in the test list as required to view all test results.
18. For additional information about using SmartStart utilities, refer to the
appropriate HP documentation. See Related documentation on page 1-4.
19. To exit the SmartStart diagnostic test utility, click Exit at the bottom left of the
window. Click OK when prompted to exit.
20. Remove the SmartStart CD from the CD/DVD drive.
21. Click Exit Diagnostics at the bottom left of the window.
22. Click OK when prompted.
23. Click Exit at the bottom left of the window. SmartStart exits, and the
CARESCAPE Gateway reboots.
24. During reboot, press F9 immediately when the message Press “F9” key for
ROM-Based Setup Utility displays. Using BIOS configuration, change the
CARESCAPE Gateway boot order back to the original settings.
25. Exit the BIOS configuration utility to allow the CARESCAPE Gateway to start
up normally, or service the unit as required/indicated by diagnostic testing
results.

Troubleshooting
ROM-based setup utility reset configuration

If a ROM-Based Setup Utility (BIOS) reset should occur (The BIOS is reset to
factory defaults), the following procedure must be performed to restore the
CARESCAPE Gateway to proper startup configuration.
1. If prompted, press F1.
2. As the CARESCAPE Gateway boots, press F9 immediately when the message

Press “F9” key for ROM-Based Setup Utility displays.
NOTE
It is important to press F9 promptly when this message displays. The Press

“F9” key for ROM Based Setup Utility message displays only briefly. If the
ROM-Based Setup Utility does not display, reboot the CARESCAPE
Gateway using the Warm boot of system selection on the Virtual Power iLO
page and repeat this step.
3. In the ROM-Based Setup Utility, use the arrow keys to select Standard Boot
Order (IPL) and press Enter.
4. Use the arrow keys to select Hard Drive C: and press Enter.
5. Use the arrow keys to select Set the IPL Device Boot Order to 1 and press Enter.
6. Press Esc.

Troubleshooting
7. Use the arrow keys to select Server Security and press Enter.
8. Use the arrow keys to select Set Admin Password and press Enter.
9. Type ungsrvc and press Enter.
10. Press Esc.
11. Use the arrow keys to perform the following:
 DL360 G7 Server: select Server Availability and press Enter.

12. Use the arrow keys to select POST F1 Prompt and press Enter.
13. Use the arrow keys to select Disabled and press Enter.

Troubleshooting
14. Press Esc.
15. Press Esc.
16. Press F10.
Application troubleshooting
The following application troubleshooting section is divided by the following
subsystems. In each of the subsystem sections, the problem, possible cause and
solution or course of action are defined.
 See CARESCAPE Gateway troubleshooting on page 5-18.

 See CARESCAPE Gateway time services troubleshooting on page 5-20.
 See ADT troubleshooting on page 5-21.
 See HL7 troubleshooting on page 5-26.
 See Cloverleaf troubleshooting on page 5-30.
 See HSDI troubleshooting on page 5-32.
 See Vitals on Demand troubleshooting on page 5-34.

Troubleshooting
CARESCAPE Gateway troubleshooting
CARESCAPE Gateway Troubleshooting
Problem Indicator Possible Reason Solution / Course of Action
Loss of HL7 Inbound/ Cloverleaf Sitemon subsystem Cloverleaf improperly licensed  Enter a valid Cloverleaf
Outbound Data shows up in an “unknown” state license.
 Ensure all the applicable
network connections are valid
and operational.
HL7 Outbound not being The host’s IP address may not be 1. Logon to Webmin.
sent to HIS configured properly.
2. Select Information > View
Server Configuration.
3. Scroll down to the Firewall
Rules section and verify that
the Outbound TCP port is
configured. If it is not
configured, see HIS IP
address/port configuration on
page 3-22.
4. Test the network connection.

See Network interface test on
page 4-6.
Configuration link in The Configuration link in the CARESCAPE Gateway service is Start the CARESCAPE Gateway
CARESCAPE Gateway CARESCAPE Gateway Webmin not running. service. See Start/stop
Webmin module is module returns “Failed to connect CARESCAPE Gateway using
inoperative to 127.0.0.1:9093: Connection Webmin on page 2-27.
refused”
Webmin properties page Page Displays “Serious Error” The file size of 1. Check the file size of the
malfunctions (refer to log files) UgsUser.properties is zero. ugsUser.properties file in the
/usr/gehc/csg/resources.
2. If the file size is 0, copy the
ugsUser.properties file from
the /usr/gehc/factorydefaults/
GEHC-csg-
factorydefaults.tar.gz directory
to the /usr/gehc/csg/resources
directory.
3. Start the CARESCAPE

Gateway service. See Start/
stop CARESCAPE Gateway
using Webmin on page 2-27.
4. Restore the user properties to

their original setting.
CARESCAPE Gateway System Manager page shows Corrupt configuration file Restore the configuration defaults
application will not start CARESCAPE Gateway application for the CARESCAPE Gateway
as stopped and multiple attempts application.
to restart the application have
failed

Troubleshooting
CARESCAPE Gateway Troubleshooting
Applications will not start Attempts to start Cloverleaf Engine '/var or /tmp are full. The "df" Log into Webmin and navigate to
fails command shows these file Configuration>Backup and
systems as 100% full. Restore> Factory Defaults
Restore the Clean up temporary

and log files target.
NOTE
This will truncate all current
log files.
Logging has stopped High volume log files like Syslog '/var or /tmp are full. The "df" Log into Webmin and navigate to
are no longer being updated. command shows these file Configuration>Backup and
systems as 100% full. Restore> Factory Defaults
Restore the Clean up temporary

and log files target.
NOTE
This will truncate all current
log files.
CARESCAPE Gateway Reviewed system configuration, The firewall or router may be Log into Webmin and navigate to
is not sending data on and it appears correct. Restarted blocking the network connections Configuration > System
the network when it the CARESCAPE Gateway service Manager. Restart the firewall on
should. and Cloverleaf service and still the CARESCAPE Gateway and
does not work retest connectivity. If there is still no
connectivity, check to confirm the
router configuration matches. See
Appendix F.
Statistics subsystem is Log message containing Statistics database may have The service will need to wait for the
unable to record “RRDUPDATE failed” become corrupt. issue to correct itself once the time
performance data due to shift has been covered. If the
a time change. difference between the two
numbers provided is large (times
are in seconds) you may want to
reset. To reset, in Webmin navigate
to Configuration > Backup and
Restore > Factory Defaults > Reset
Historical Statistics Database.

Troubleshooting
CARESCAPE Gateway time services troubleshooting
CARESCAPE Gateway Time Services Troubleshooting
Symptom Indicator Possible Reason Solution / Course of Action
CARESCAPE Network Monitor time wrong Time service not running Check CARESCAPE Gateway
time master time set Time Master properties settings
incorrectly are configured correctly:
1. Logon to Webmin.
2. Select Configuration >

CARESCAPE Gateway
Configuration >
Configuration > Setup >
Properties.
3. Scroll to the Time Master

Properties section.
4. Verify that the settings are
correct.
CARESCAPE Network Monitor time wrong after daylight Time master properties are not Check to see that the time master
time is not automatically savings configured correctly properties are configured
adjusted for daylight correctly:
saving time
1. Logon to Webmin.

System Time > System
Clock Settings.
3. Verify that the Timezone
settings are correct.
CARESCAPE Gateway No time adjustment being made NTP Server is not properly Verify that the host server is
does not make time configured reachable and its strata is
adjustments from NTP acceptable:
server
1. Logon to Webmin.

System Time > NTPD
Settings.
3. Enter the Network address of

the host server and click
Save.
4. Check if the value of the

Ping? field for the host server
is Yes.
5. Check if the host server is

displayed in the NTP queue
at the bottom of the page.
6. Check that the value in the

ST (strata) field is lower than
the local clock.
Time Master properties are not Check to see that the Time Master
configured correctly properties are configured correctly.

Troubleshooting
CARESCAPE Gateway Time Services Troubleshooting
Symptom Indicator Possible Reason Solution / Course of Action
Incorrect time propagated Unable to connect with the NTP Invalid IP or secure data link Check IP setting and secure data
to network server (CARESCAPE IX router) link (IX network router)
configuration configuration. See NTP server
computer IP address configuration
on page 3-17 and Default router
configuration on page 3-15.
No time update from the NTP Service disabled or Check to see that the
server misconfigured to use time master CARESCAPE Gateway Time
Master properties are configured
correctly.
See NTP server computer IP

address configuration on page 3-
17.
CARESCAPE Gateway OS time Service disabled or time is Check to see that the
wrong outside of the 8 hour maximum CARESCAPE Gateway Time
time adjustment window Master properties are configured
correctly.
See System time/date

Time at CARESCAPE CARESCAPE Gateway OS time Service disabled or time is Check to see that the
Gateway does not match wrong outside of the 8 hour maximum CARESCAPE Gateway Time
time on CARESCAPE time adjustment window Master properties are configured
Network correctly.
See System time/date

No time update from the Service disabled or mis- Check to see that the
CARESCAPE Network time configured to use NTP CARESCAPE Gateway Time
master Master properties are configured
correctly.
See NTP server computer IP

address configuration on page 3-
17.
CARESCAPE Network Fluctuation between two different Multiple CARESCAPE Gateway Configure only one of the
devices' clocks fluctuate, times on CARESCAPE Network systems set as time master CARESCAPE Gateway systems
going back and forth devices to have the Time Master
between two different Properties setting CARESCAPE
times. Gateway as time source to be
On. In Webmin, select
Configuration > CARESCAPE
Gateway Configuration >
Properties.
ADT troubleshooting
NOTE
A list of all the ADT sources on the network may be obtained by using the
appropriate process at the CIC Pro Clinical Information Center.

Troubleshooting
ADT Troubleshooting
ADT information has ADT information has incorrect Incorrect Cloverleaf configuration Verify CARESCAPE Gateway domain
incorrect PID PID for domain and patient ID and patient ID typecode match the
typecode Cloverleaf translation for these fields.
See ADT inbound domain/typecode
ADT information has incorrect Incorrect CARESCAPE Gateway Change CARESCAPE Gateway
PID domain or patient ID typecode domain and patient ID typecode to
match the Cloverleaf translation for
ADT Information has default No matching domain or patient ID these fields. See Properties
PID typecode found in the ADT Query configuration on page 7-20 and ADT
Response inbound domain/typecode configuration
on page 7-29.

Troubleshooting
ADT Troubleshooting
Patient record cannot be ADT HL7 inbound data is not System Manager Webmin module Use the System Manager Webmin
found being stored in the Patient shows Cloverleaf Engine, Patient module to start the stopped services.
data cache Data Cache and/or PostgreSQL
Database services not running.
The Interface Monitor Webmin Start the stopped Cloverleaf processes.

module shows the his_prod Ensure the processes and threads are
inbound process and/or configured to automatically start.
ccg_prod process not running
All received ADT messages are Need to determine the cause of the
failing (e.g. email error failed translations in order to fix.
notifications received for many
ADT messages, Cloverleaf
process stats indicate failed
translations)
No matching patient found  More than one ADT service  Use the appropriate process from
when querying by location provider (MUSE Gateway, a CIC Pro center to determine if
(Unit or Unit and Bed) from Aware Gateway or there are multiple devices offering
central station or patient CARESCAPE Gateway) ADT services. If so, remove or de-
monitor.  ADT HL7 inbound data not license the other devices so that
being stored in the Patient only one is providing ADT, or make
data cache it so both devices are receiving the
same set of ADT data.
 Restart the CARESCAPE
Gateway.
 Translation or database Send an ADTÂ08 update message for

error on ADTÂ01 admit patient. This will cause an admit.
event
 Translation or database
error on ADTÂ06 changing
outpatient to inpatient
Using the Database Viewer Unit-only HIS mappings and complete

Webmin module shows a patient HIS mappings are utilized in ADT
record for the desired patient queries, so if the mapping matches
record. But, HIS mapping present either the provided Unit and Bed name
that is converting the desired or just the Unit name, it will be used to
location name to something else. do the query instead. See HIS mapping
on page 7-17.
Unsupported combination of CSG Application log includes the Users must provide a last name with
fields provided (e.g. first name message “MINIMUM REQUIRED first name when querying by patient
with no last name) FIELDS TO PERFORM name, and a unit name with a bed name
PICKLIST QUERY ARE NOT when querying by location.
PRESENT”

Troubleshooting
ADT Troubleshooting
Incorrect patient data at Patient data ADT workflow Incorrect ADT workflow setting Verify in Webmin that the ADT workflow
the monitor mapping errors mapping is set to the customer
customization. See ADT workflow
Incorrect patient information Missing an ADTÂ02 transfer Send an ADTÂ08 update message for
event patient. This will cause an admit.
An ADTÂ08 event received to Install an ADTÂ08 filter in Cloverleaf

update information, re-admits the that discards A08 events based on
patient discharge time.
Missing an ADTÂ02 transfer and Re-send both ADTÂ02 in order or

new ADTÂ02 transfers patient to manually update SAP database.
a non-vacated bed (two patients
at same location)
Missing ADTÂ03 discharge and Re-send ADTÂ03 and ADTÂ02 in

new ADTÂ02 transfers patient to order.
a non-vacated bed (two patients
at same location)
Problem with admit or merge ADT workflow setting Check the ADT workflow admit flag.
message Refer to the CARESCAPE Gateway
HL7 Reference Manual for information
about ADT configuration rules.
Unable to request ADT Message displayed at Invalid/corrupt license 1. Add valid ADT license key. See
data monitoring device: No data CARESCAPE Gateway license
server present configuration on page 7-28.
NOTE
The license key used must

have been generated for the
current MAC address as
shown on the License screen.
2. Delete the current ADT license in

Webmin.
CARESCAPE Network MC See Troubleshooting network problems

settings are misconfigured or loss on page 5-8.
of network connectivity
ADT query fails some or all of More than one ADT service Use the appropriate process from a CIC
the time provider Pro center to determine if there are
multiple devices offering ADT services.
If so, remove or de-license the other
devices so that only one is providing
ADT, or make it so both devices are
receiving the same set of ADT data.
 No licenses available or  License file may have been Add valid ADT license file via Webmin.
license count of zero deleted NOTE: The license key used must have
 Service is disabled  License key may be invalid been generated for the current MAC
address as shown on the License
screen. See CARESCAPE Gateway
license configuration on page 7-28.

Troubleshooting
ADT Troubleshooting
License key cannot be Message:...was not able to be  License key may be invalid 1. Make sure license key was
added via Webmin. added, it is invalid in the given  Message in the service log entered correctly.
(Operation fails) context states access denied or 2. Confirm the license key entered
CARESCAPE Gateway was generated using the MAC
does not have access to the address as shown on the license
license file. See CSG.log screen.
description on page 5-38.
3. Remove the license key from the
license page and restore the
license key based on the license
information shipped with the
system. See CARESCAPE
Gateway license configuration on
page 7-28.
Patient record lookup in Message: No matching patient Queried field has a dash Use the wildcard character “%” in place
ADT database fails records found for this query character in it. of a dash when querying.
when using the input
Database Viewer
Webmin module
No patient information ADT request times out - No System Manager Webmin page Use the System Manager webmin
returned for query error message returned shows CCG Patient Data Cache module to restart the stopped services.
and/or PostgreSQL Database If it continues to be a problem, contact
services state as not running GE.
ADT request times out - No CCG_PROD not running in Run the script /usr/gehc/csg/bin/
error message returned cloverleaf fixCCGPerms.sh to restore the correct
Permission errors listed in the file ownership permissions to the CCG
CCG_prod site log (ccg_prod- site files OR Restore the Cloverleaf
ccg.log) sites to factory defaults (or another
backup)
Data returned contains Non-ASCII character in patient Question marks (“?”) in the PID Send an ADT update message in to
question mark data in database (cannot map) update record in the ADT database
characters (“?”) cache with valid PID.
Some messages Intermittent ADT query results More than one ADT service Query RWHAT from a CIC Pro center to
returned: unit/bed not provider determine if there are multiple devices
found (intermittent) offering ADT services. If so, remove or
de-license the other devices so that
only one is providing ADT, or make it so
both devices are receiving the same set
of ADT data.

Troubleshooting
ADT Troubleshooting
Too many records Querying by last name only or Many patient records in the  Train users to provide more details
returned Unit name only and getting database when performing queries
more records than desired  Consider using HIS mappings for
standardizing searches by
location. See HIS mapping on
page 7-17.
Old patient records in the  ADT messages that change  Check to see if Discharge ADT
database patient records from being messages are failing.
admitted to discharged are  Consider adjusting purge settings
not being received to prune the database more
 Purge settings are too quickly. See Purge ADT
lenient configuration on page 7-4.
Unit name lookup in Message: No matching Unit name has a space character Use the wildcard character "%" in place
ADT database fails records found in it of any spaces when querying.
when using the
Database Viewer
Webmin module
HL7 troubleshooting
NOTE
The CARESCAPE Gateway will trend data up to two minutes behind by design.
This occurs to keep the vitals in synch with the CARESCAPE Gateway and
bedside monitors.
NOTE
If a parameter is available in the outbound trends interface, but does not appear in
the VoD interface, refer to Appendix E.
HL7 Troubleshooting
HL7 Outbound not being HIS does not acknowledge the HIS software upgrade not Review HIS upgrade release notes
sent to HIS message compatible with Cloverleaf setup and reconfigure the Cloverleaf
engine.
HIS does not acknowledge the HIS is down Verify the HIS is in an operational
message state.
Cloverleaf response times CARESCAPE Gateway Service Allow system watchdog function to
greater that 40 seconds message queue is building up via restart Cloverleaf/CCG and the
Webmin > Configuration > CARESCAPE Gateway Service.
CARESCAPE Gateway >
Configuration > Dashboard in
the HL7/Cloverleaf Processing
section. See CSG.log description
on page 5-38.

Troubleshooting
HL7 Troubleshooting
License key cannot be Message:...was not able to be  License key may be invalid 1. Make sure license key was
added via Webmin. added, it is invalid in the given  Message in the service log entered correctly.
(Operation fails) context states access denied or 2. Confirm the license key entered
CARESCAPE Gateway was generated using the MAC
does not have access to the address as shown on the
license file. See CSG.log license screen.
description on page 5-38.
3. Delete the hl7licensekey.txt in
 May be adding a license with
a number of beds lower than Webmin.
the number of beds on the 4. Restore the license key based
current bed list. on the license information
shipped with the system. See
CARESCAPE Gateway license
HL7 outbound HIS HL7 outbound HIS connection Incorrect IP or port information on Update the Cloverleaf configuration
connection failure failure after HIS restart/reset the his_prod outbound thread thread properties for the
GE_system_OB.
(IP address change)
Cannot add beds to bed No licenses available or  License file may have been Add valid device count license file
list available license count is zero deleted via Webmin.
 License key may be invalid
NOTE
The license key used must
have been generated for the
current MAC address as shown
on the License screen.
Not sending HL7 from Beds are no longer on the bed HL7 license key file is missing/ Try the following:
some beds list corrupt
 Re-enter the HL7 license and
manually reconfigure the bed
list. See License configuration
on page 7-28.
or
 Restore the previous
configuration backup. See
Restore configuration backups/
factory defaults on page 7-9.

Troubleshooting
HL7 Troubleshooting
No data collected from Bed not admitted  Bed was never admitted 1. Ensure device compatibility.
admitted bed from the monitor Refer to Appendix C.
 Bed does not exist on the 2. Make sure bed is on the
network network and offers trends.
 Network problems (monitor
communication) 3. Ensure bed is admitted from
the monitor.
 Bed was never added to the
filter list via Webmin 4. Ensure bed is on the same
 Bed is not supported by network as the CARESCAPE
Gateway. Monitor should be
CARESCAPE Gateway or
displayed via Webmin.
does not offer trends
5. Ensure bed is on the filter list. If
not, add via Webmin.
Bed not in collection/filter list Bed does not appear in collection/ 1. Ensure device compatibility.
filter list when viewed via Webmin Refer to Appendix C.
2. Make sure bed is on the

network and offers trends.
3. Add the bed to the collection/

filter list Webmin. See
CARESCAPE Network MC bed
list on page 7-13 and S/5
Network bed list on page 7-18.
Bed does not appear in list of  Bed may be disconnected  Ensure device compatibility.
beds/devices seen online/on the from the network Refer to Appendix C.
network (Webmin Network  Bed may not be supported  Check cables and assure bed
Update tab) by CARESCAPE Gateway is on the same network as the
or may not offer trends, (the CARESCAPE Gateway.
CARESCAPE Gateway
requires trends to collect
data)
Bed off network; CARESCAPE Bed appears in collection/filter list  Ensure device compatibility.
Gateway not detecting monitor/ when viewed via Webmin but is Refer to Appendix C.
bed noted as Offline  Check cables and assure bed
is on the same network as the
CARESCAPE Gateway.
Account number not Account number reconciliation Domain field does not match the Verify CARESCAPE Gateway
correct in HL7 outbound not populating account number ADT inbound feed from the HIS domain matches the ADT inbound
message in HL7 outbound message admit data populated by the HIS or
Cloverleaf translation.
Integrated ADT data into HL7 Feature is disabled Navigate to Webmin >
PID segment Configuration tab > CARESCAPE
Gateway Configuration >
Properties > Integrate ADT data
into HL7 PID Segment.
Set to True.

Troubleshooting
HL7 Troubleshooting
Response is not in MSA segment field three Not one of the supported HL7 Change the default version that the
requested HL7 version includes a message stating the versions HL7 converts or configure a translate
version that was not supported in Cloverleaf to change the HL7
and the version that it is currently version.
using
PCD-01 HL7 trend OBX-20 does not contain EEG CARESCAPE Gateway clock is Ensure CARESCAPE Gateway time
messages do not site information out of sync with monitor is in sync with monitor time.
contain EEG site
information in OBX-20
Updated the HIS HL7 messages for the device are The CARESCAPE Gateway Change the HIS mapping to not
mapping for a device being sent with patient data, but application converts a HIS have a caret or configure Cloverleaf
and now trended or the name of the originating mapping with a ‘^’ in UNIT|BED to remove the redundant ‘^’
Vitals On Demand device only has the unit name into ‘^^’ when creating the HL7
patient data is not and is missing the bed name message.
showing up in the (PV1 segment, field 3 assigned
charting system patient location)
Trended PA values not When Bx50 patient monitor is In certain versions of the Bx50 None. This is a software issue with
being delivered used, Pulmonary Artery invasive patient monitors software, when the Bx50 patient monitors. The PA
blood pressure values are the PA Wedge dialog is displayed, Wedge dialog must not be left open..
sometimes not included in the it stops trending all pulmonary
trends HL7 outbound feed. artery measurements.

Troubleshooting
HL7 Troubleshooting
Performance degrades HL7 Outbound messages Excessive translations, data  Review the size of the recovery
over time backing up at various inter- manipulations, or procedural calls and error databases in
process communication ports Cloverleaf.
CARESCAPE Gateway service
 Check the configuration
message queue is building up via
settings.
Webmin > Configuration >
CARESCAPE Gateway
Configuration > Configuration
> Dashboard in the HL7/
Cloverleaf Processing section.
See CSG.log description on page
5-38.
HIS does not acknowledge the HIS software upgrade not Review HIS upgrade release notes
message compatible with Cloverleaf setup. and reconfigure the Cloverleaf
engine.
HIS does not acknowledge the HIS is down Verify the HIS is in an operational
message state and that the IP configuration in
Cloverleaf matches.
Cloverleaf response times CARESCAPE Gateway service Allow system watchdog function to
greater that 40 seconds message queue is building up via restart Cloverleaf/CCG and the
Webmin > Configuration > CARESCAPE Gateway service.
CARESCAPE Gateway
Configuration> Configuration >
Dashboard in the HL7/
Cloverleaf Processing section.
See CSG.log description on page
5-38.
Some of the beds are The latest data coming over are CARESCAPE Gateway Try the following things in order:
not being collected in minutes old acquisition subsystem with the
real time collection interval set to 1 minute. 1. If CARESCAPE Gateway is set
If enough requests for vitals from as the MC Network time
a bed are not returned, the latest source, ensure that subsequent
data requested from the bed will NTP requests the
be one more minute old. Over CARESCAPE Gateway makes
time, the latest data delivered over time are actually satisfied.
could be minutes old instead of If it is not synchronized, then
the latest. the timestamps on the data
collected from the MC network
could be older than what the
HIS is expecting, even though
the data is actually current.
2. Ensure the switch to which

beds are attached have the
beds' ports set to full duplex
and not auto or half duplex.
Doing this will reduce the
number of dropped UDP
requests.
Cloverleaf troubleshooting
Using a VNC or iLO session, access Webmin > Interface Monitor, check the status
of the interface threads.

Troubleshooting
 If all the threads are stopped: use the Interface Monitor to start the processes
necessary for operation.
 If one or a few threads are stopped: use the Interface Monitor to start them on an
individual basis.
 For more detailed thread status information, use the Cloverleaf IDE. See Viewing
Thread Statistics
Cloverleaf Troubleshooting
Loss of HL7 inbound/ License keys became invalid  Disconnected CARESCAPE  Check network cables/
outbound data (system Network IX or MC interface connections.
may be in continuous cable.  Check for valid IP
reboot cycle)  Bad IP address(es) configuration and active
network interfaces. See
Network interface test on
page 4-6.
Internal errors - thread is in a down Interface not installed or is corrupt Consult with ITPS to have them
state and will not come up restore the interface from backup.
See Cloverleaf interface restore
on page 7-35.
Threads and processes are in a Cloverleaf license is “built-to- Check the interface’s process log
down state and refuse to start order” and the number threads for the following:
configured as External exceeds
the number of external threads You have configured <x>
allowed by the license external thread(s).
You have licensed <y> threads.
You do not seem to be licensed

to run this executable. Contact
your Customer Service
Representative for assistance.
If the message is in the log, use

the Cloverleaf IDE to configure the
CARESCAPE Gateway thread
type of each appropriately, or
request an updated license from
Cloverleaf.
Account number not Account number reconciliation not Domain field does not match the Verify CARESCAPE Gateway
correct in HL7 outbound populating account number in HL7 ADT inbound feed from the HIS domain matches the ADT inbound
message outbound message admit data populated by the HIS
or Cloverleaf translation.
Stopped Cloverleaf Shut-down Monitor daemon, The Cloverleaf service is running Shut down the Cloverleaf service
Monitor daemon, threads and/or processes start up if you need to keep the service
threads and/or automatically shut down while making changes.
processes restart
automatically
Cloverleaf IDE unable to Cloverleaf IDE shows a message hciaccess has an issue of not Close the IDE, restart it, and try
launch a separate about too many files open properly closing open handles running the command again.
process (e.g. when left running for a long period
hcienginerun) of time
Cloverleaf IDE becomes The Cloverleaf IDE displays only a Cloverleaf IDE is in a failed state Log out of the desktop and log
unresponsive white page, no action can be taken back in. Re-launch the Cloverleaf
IDE.

Troubleshooting
Cloverleaf Troubleshooting
Cannot resend a failed The following error is displayed: Communication problem between Resend messages using
message using "Could not retrieve process name service interface and Cloverleaf Cloverleaf commandline tools
Configuration> for CCG_Inbound". instead. See Retrieve and resend
Network Monitor failed messages on page 7-39.
Cannot perform all Desktop display size is too small to Default desktop size set in order Start a terminal window and run
functions in desktop GUI display the full application window to reduce network bandwidth the following command: sudo /
application usage. usr/bin/system-config-display.
Set the resolution to the desired
settings.
Interface Monitor/ Interface Monitor/Management Web service is not running Restart CCG Web Tools in
Management does not display information properly Configuration>System Manager
unavailable webmin module
HSDI troubleshooting
HSDI Troubleshooting
HSDI Outbound Client not receiving data CARESCAPE Gateway to client Verify CARESCAPE Gateway to
waveform and numeric network is down client network is functioning.
data not being sent to
client for all beds Client is down Verify the client is in an operational
state
No High Speed Data Interface  License key may be invalid 1. Make sure license key was
Client Connection Count licenses  License file may have been entered correctly.
available deleted 2. Confirm the license key entered
 Too many clients are was generated using the MAC
connected address as shown on the
license screen.
3. Delete the cccclicensekey.txt

in Webmin. See CARESCAPE
Gateway license configuration
on page 7-28.
4. Restore the license key based

on the license information
shipped with the system.
5. Verify that the correct number

of clients are connected.
6. Forcibly disconnect some or all

of the HSDI clients.
 Too many clients Verify the correct client addresses

connections have been have been reserved.
reserved
 Reserved client connections
have the wrong client IP
address

Troubleshooting
HSDI outbound numeric High Speed Data Interface  License key may be invalid 1. Make sure license key was
data not being sent to Numerics license not enabled  LIcense file may have been entered correctly.
client for all beds deleted 2. Confirm the license key entered
was generated using the MAC
address as shown on the
license screen.
3. Delete the snumlicensekey.txt

on page 7-28.

HSDI outbound High Speed Data Interface  License key may be invalid 1. Make sure license key was
waveform data not being Waveforms license not enabled  LIcense file may have been entered correctly.
sent to client for all beds deleted 2. Confirm the license key entered
was generated using the MAC
address as shown on the
license screen.
3. Delete the swavlicensekey.txt

on page 7-28.

Not sending numeric Beds are no longer on the bed HL7 license key file is missing/ Try the following:
and waveform data from list corrupt
some beds  Re-enter the HL7 license and
manually reconfigure the bed
list. See License configuration
on page 7-28.
 Restore the previous
configuration backup. See
Restore configuration backups/
factory defaults on page 7-9.

Troubleshooting
No numeric and Bed not admitted  Bed was never admitted 1. Ensure device compatibility.
waveform data collected from the monitor Refer to Appendix C.
from admitted bed  Bed does not exist on the 2. Ensure the bed is on the
network network and offers numerics
 Network problems (monitor and waveforms.
communication)
3. Ensure bed is admitted from
 Bed was never added to the the monitor.
filter list via Webmin
 Bed is not supported by 4. Ensure bed is on the same
network or the CARESCAPE
CARESCAPE Gateway
Gateway. Monitor should be
displayed via Webmin.
5. Ensure bed is on the filter list, If

not, add via Webmin.
Bed not in collection/filter list Bed does not appear in collection/ 1. Ensure device compatibility.
filter list when viewed via Webmin Refer to Appendix C.
2. Ensure the bed is on the
network and offers numerics
and waveforms.
3. Ensure bed is on the collection/

filter list in Webmin.
See CARESCAPE Network MC

bed list on page 7-13 and S/5
Network bed list on page 7-18.
Bed does not appear in list of  Bed may be disconnected  Ensure device compatibility.
beds/devices see online/on the from the network Refer to Appendix C.
network (Webmin >  Bed may not be supported  Check cables and assure bed
Configuration > CARESCAPE by CARESCAPE Gateway is on the same network as the
Gateway Configuration > CARESCAPE Gateway.
Configuration > appropriate
network bed list)
Bed off network; CARESCAPE Bed appears in collection/filter list  Ensure device compatibility.
Gateway not detecting monitor/ when viewed via Webmin but is Refer to Appendix C.
bed noted as Offline  Check cables and assure bed
is on the same network as the
CARESCAPE Gateway.
Some of the beds are The latest numeric and The client is not able to keep up  Check the logs for a message
not being collected in waveform data being sent are with the amount of data being indicating that the client was
real time minutes old sent by the CARESCAPE not able to keep up.
Gateway  Verify that the client was
designed and tested for the
number of beds currently on the
bed list.
Vitals on Demand troubleshooting

NOTE
If a parameter is available in the VoD interface, but does not appear in the
outbound trends interface, refer to Appendix E.

Troubleshooting
VOD Troubleshooting
VOD client application Ping from VOD client application Disconnected CARESCAPE Check network cables and
fails to connect to host machine to CARESCAPE Network IX or MC interface cable connections.
CARESCAPE Gateway Gateway fails
Incorrect network setup such as Check for valid IP configuration and
invalid IP configurations, etc. active network interfaces. See
Network interface test on page 4-6.
Ping from/to client and server Cloverleaf and/or VOD client Check the configuration on the VOD
succeed, but VOD client still application are not configured to client application and reload firewall
cannot connect. use the correct ports in Webmin > System Manager.
Firewall on VOD client host Reconfigure firewall(s) to allow traffic

machine or on CARESCAPE on VOD ports.
Network IX has blocked traffic on
VOD port
CARESCAPE Gateway firewall Ensure Cloverleaf is configured

has been incorrectly configured correctly and reload firewall in
and is blocking incoming VOD Webmin > System Manager.
connections
CARESCAPE Gateway VOD client application connects Cloverleaf VOD request and/or VOD requests are being sent to
does not send a VOD to CARESCAPE Gateway and VOD response queues are CARESCAPE Gateway faster than
response message sends VOD request messages, backed up with VOD messages the CARESCAPE Gateway can
but receives no VOD response respond. Reduce the number and/or
message frequency of VOD requests.
The VOD feature should be used for

incidental requests, not as a
recurring stream of data. For a
stream of near real-time data, use
the High Speed Data Interface.
Cloverleaf is not configured Contact GE ITPS to have them

properly or has become corrupt restore the interface from backup.
See Cloverleaf interface restore on
page 7-35.
VOD request message is not well- Refer to the CARESCAPE Gateway

formed HL7 or is not of the proper HL7 Reference Manual.
query type
Check the Cloverleaf error log.
A Cloverleaf recovery database Repeat the query request.

purge was automatically taking
place when request was received
and delayed the request

Troubleshooting
VOD Troubleshooting
CARESCAPE Gateway VOD response message VOD request message is not Refer to the CARESCAPE Gateway
responds to VOD indicates that the VOD request formatted properly. HL7 Reference Manual.
request message with message is invalid
an error rather than with Check the Cloverleaf error log.
a valid VOD response
message VOD response message Requested device is not online, Ensure that the request device is
indicates that the requested admitted, and on the online and in the admitted state and
device name or session was not CARESCAPE Gateway bedlist. that the device appears in the
found. CARESCAPE Gateway bedlist. See
Configure bed list, HIS mappings,
and properties on page 3-24.
VOD response message Data acquisition from monitor has If HSDI client is available, connect
indicates that the requested failed. HSDI client and determine if HIS
device name or session was data is available at the client. If not,
found but data was not available. follow troubleshooting steps for
HSDI.
If no HIS client is available, or HSDI

data is available at the HIS client, an
unknown error has occurred. Restart
the CARESCAPE Gateway service
(Webmin > Configuration >
System Manager).
VOD response message VOD feature has not been Contact GE to purchase VOD
indicates that the VOD feature is licensed. license.
not licensed.
Cloverleaf database failure recovery

The following procedure describes how to recreate Cloverleaf internal databases after
an unrecoverable failure in Cloverleaf.
NOTE
Contact GE ITPS before performing this recovery procedure.
NOTE
This procedure should be performed on these sites:
 unity_prod
 his_prod
 ccg_prod
 vod_prod
1. Double-click the Cloverleaf IDE icon on the CARESCAPE Gateway desktop.
2. In the Tools frame on the left side of the Cloverleaf IDE window, click the
Remote Commands icon.

Troubleshooting
3. Click List Command in the Remote Commands frame.
4. Select Miscellaneous Commands > hcidbdump and click OK.
5. In the Remote Commands frame, click in the Command field to place the cursor
just to the right of the hcidbdump string. Type <Space>-e and click Execute.
6. Select the -e in the Command field string and type -r. Click Execute.
NOTE
If there was an Internal database vista error, perform the following steps.
 Click List Commands.

 Navigate to the Miscellaneous Commands and select hcidbinit.
 Click Ok.
 In the Command textbox, type <space>-A<space>-C<space>-f after
hcidbinit.
 Click Execute.
 Restart the CARESCAPE Gateway (In Webmin, select Configuration >
System Manager > Restart).
7. In the Tools frame on the left side of the Cloverleaf IDE window, click the
Network Monitor icon.
8. Right-click a process under the Network Monitor tab. Select Control > Start.
9. Repeat the previous step for all processes and all interfaces.
If this procedure does not restart the threads, it may be necessary to replace the
Cloverleaf interfaces with previously backed up copies. See Cloverleaf interface
restore on page 7-35.
Event logs
CARESCAPE Gateway log viewer
The Webmin Log Viewer provides view access to several types of associated
CARESCAPE Gateway logs.
To access the Log Viewer:

Troubleshooting
2. Select Diagnostics > Log Viewer.
3. Click the Log File Category you want to view.
4. Type a string to search for within the log files and click Go,
-or-
Click the log file you want to view.
5. Scroll down to view the selected log file.
CSG.log description
The following table describes messages in the CSG.log.
Message Meaning
Servlet startup completed The CARESCAPE Gateway Service runs an embedded “servlet” container. This provides the
functionality behind the Webmin modules. The message simply indicates that it has started up
correctly. If this doesn't appear, access to Webmin may not be working properly.
Application startup completed Indication that the CARESCAPE Gateway Service was successfully started. This does not indicate,
however that all the sub-components of the CARESCAPE Gateway Service have started properly.
Cloverleaf Connection xx created This indicates that a TCP connection has been successfully made to Cloverleaf. There should be
about 20 of these, by default, where “xx” is a number from 1 to 20. If you are seeing problems with
HL7 being sent to Cloverleaf, the CARESCAPE Gateway Service restarting or just general issues
with CARESCAPE Gateway Service startup check to see that all connections were made
successfully. If not, then it is likely that Cloverleaf did not start properly.
Enterprise Gateway Connection xx This indicates that a TCP connection has been successfully made to Enterprise Gateway. There
created should be about 18 of these, by default, where “xx” is a number from 1 to 18. If you are seeing
problems with ADT, the CARESCAPE Gateway Service restarting or just general issues with
CARESCAPE Gateway Service startup check to see that all connections were made successfully. If
not, then it is likely that Cloverleaf or Enterprise Gateway did not start properly.
CARESCAPE Network MC This is the IP address of the network card being used to broadcast on the CARESCAPE Network.
broadcast address using property Check that this is correct if having difficulty receiving any bed data/traffic.
set to xxx.xxx.xxx.xxx
Admit event processed for device When a bed is on the network, admitted and has been added to the collection/filter list via Webmin,
[{unit}|{bed}] on {date} then CARESCAPE Gateway will internally “admit” the bed and prepare for data acquisition.

Troubleshooting
Message Meaning
Scheduling started for device After the bed has been admitted it will be scheduled to have trend data pulled from it at a defined rate
[{unit}|{bed}]... (default is every 1 min). This rate is adjustable via Webmin. There will actually be four threads
scheduled to pull information from each bed as it is admitted - periodic data, episodic data, Patient ID
changes, time changes. These scheduled events will occur at a defined rate until the bed is
discharged, goes offline or goes into Transport.
{disposition} - [{unit}|{bed}]==> #xx When acquiring trend data from a bed/monitor, a specific window of data is requested. This message
window[{start time} - {end time}] indicates the disposition of collecting data (Periodic or Episodic) as well as the start and end time.
Since the CARESCAPE Gateway cannot collect more than 20 minutes of data from a monitor at a
time, it may be necessary to go back to the monitor more than once to get all the data required. The
collection number (e.g., “”xx”) indicates the collection iteration. This will be seen in cases of back-
collecting trend data from a monitor that has been offline for more than 20 minutes.
Example: Periodic - [ICU|BED4]==> #1 window[2004/07/28 09:06:00 AM - 2004/07/28 09:07:00 AM]”
HL7 for [{unit}|{bed}]... Following this statement will be the exact data retrieved from the bed and formatted as HL7 which is
about to be sent to Cloverleaf. By default it will only show the first 3 lines of the HL7 statement. If
more detail is necessary, set Full HL7 Logging to true via Webmin.
Cloverleaf response... This statement displays the response Cloverleaf after receiving an HL7 message from the
CARESCAPE Gateway Service. It gives the time it took Cloverleaf to respond, average total time as
well as the MSH segment of the HL7 message it is acknowledging. In addition, this log statement
contains the number of devices actively having trend data acquired by the CARESCAPE Gateway.
Also, if the “queue” of HL7 data waiting to be sent to Cloverleaf starts backing up, then the current
count will be displayed.
HL7 process... for [{unit}|{bed}] This statement displays how long it took the CARESCAPE Gateway Service to parse, process and
send the latest HL7 statement for the given unit|bed.
Cannot process ADT request... ADT functionality will be turned off if there is no valid license key available for ADT. To turn it back on,
this service was turned off add a valid license key via Webmin. Contact GE to obtain a valid license key. Verify HIS feed is
working correctly by asking customer.
XML query for ADT request Following this statement will be the XML query formed from the necessary data sent by the bed as a
request for data.
EG XML response for ADT request Following this statement will be the XML query sent from the Enterprise Gateway (EG) as a response
to the ADT request sent from the bed.

Troubleshooting
Message Meaning
IOException in get trend... Trying This occurs when the CARESCAPE Gateway is having trouble communicating with a bed/monitor. It
again is normal for some or all of these errors to occur briefly when a monitor is removed from the network
(e.g., Rover mode) or a patient is discharged from the monitor.
or
If these errors happen for a number of sequential data requests to the monitor, the CARESCAPE
Socket timed out when polling Gateway will stop requesting data from the monitor. Data collection will resume when the monitor is
{unit}|{bed} for PID change put back on the network, or when the patient is readmitted.
or
Socket timed out waiting for time

from device: {unit}|{bed}
or
Device offline (has expired). It has

not responded in [xxs]...
or
cannot validate the trend data from

the device...
or
Failed to get response from

device...
or
Unable to communicate with

device...
or
Attempt xx failed to get response

from device
Canceling data collection for: These events can occur when CARESCAPE Gateway cancels trend data acquisition from a bed/
{unit}|{bed} monitor. This may be because of network communication problems or simply because the monitor
was removed from the network. Acquisition will also be cancelled when the bed is removed from the
or filter/collection list via Webmin.
Scheduling stopped for device...
or
Discharge event processed for

device {unit}|{bed}...
Total queue depth [xxx] exceeds The CARESCAPE Gateway Service maintains an internal queue which holds data acquired from the
the max allowed commands in the various beds being collected from before sending the resultant HL7 messages to Cloverleaf. Under
queue [xxx] normal circumstances, this queue will remain virtually empty as the CARESCAPE Gateway Service
should be able to send the trend data (as HL7) to Cloverleaf as fast as it is added to this internal
or queue. However, if Cloverleaf response time has slowed down to the point where the CARESCAPE
Gateway Service is receiving trend data faster than it can send it out, this queue will begin to build up.
initiating CARESCAPE Gateway When the number of items in this queue reaches a predefined count, the CARESCAPE Gateway
Service shutdown because of
Service will exit with a code of 60. The entire system may be restarted automatically at that point.
command queue overflow with exit
code = 60

Troubleshooting
Message Meaning
Duplicate UNIT|BED detected for This message indicates that another device was found on the network with the same unit/bed name.
{unit}|{bed} Since monitors do not allow this to occur, the only situation where it might arise is when multiple
CARESCAPE Gateway systems are on the same network. The default behavior is to internally
convert the unit/bed name to the IP address to avoid conflicts.
The consequences of having multiple systems on the network at the same time are undefined. If
more than one system has ADT enabled and a request is made, it is indeterminate as to which
CARESCAPE Gateway system will receive and process the request.
Shutting down CARESCAPE Indicates that the CARESCAPE Gateway Service will be shut down for the reason given. Known exit
Gateway Service with Exit Code: codes:
xx
 20 => Unable to make TCP socket connections to Enterprise Gateway (EG) (EG down).
 30 => Unable to make TCP socket connections to Cloverleaf (Cloverleaf down).
 50 => Cloverleaf is in an indeterminate state and unable to communicate with the CARESCAPE
Gateway Service (Cloverleaf down).
 60 => The CARESCAPE Gateway Service is collecting trend data faster than it can send it to
Cloverleaf (Cloverleaf down or slow).
The license key in {licensefile.txt} This could occur if license keys in the license text file were not generated from the MAC address
is INVALID! Available licenses will stored in the macaddress.txt file. The license keys text files are located in \gems-it\ugs\conf\license.
be set to 0. The CARESCAPE Gateway requires that the licenses keys for ADT and HL7 be generated with the
predetermined MAC address stored in the macaddress.txt file. The address is from the network card
used for the CARESCAPE Network connection. This file will be automatically generated and
populated each time CARESCAPE Gateway starts up. Contact GE technical support to obtain license
keys.
Enable Time Manager Services Indicates that the Time Manger services are enabled and CARESCAPE Gateway will begin
managing time synchronization between its OS time and the CARESCAPE Network. This property
can be configured via Webmin.
Disable Time Manager Services Indicates that the Time Manger services are disabled. This property can be configured via Webmin.
Enabling CARESCAPE Gateway Indicates that CARESCAPE Gateway will use its OS time to sync to the CARESCAPE Network. This
as Time Master…… property can be configured via Webmin.
Disabling CARESCAPE Gateway Indicates that CARESCAPE Gateway will use CARESCAPE Network time to sync to its OS time.
as Time Master…… This property can be configured via Webmin.
Got Date from Time Master. This periodic message indicates the device that is providing the Time Master service and what time
[{time}] [{unit|bed}] the device is currently set to.
Sending update time to Time This message indicates that CARESCAPE Gateway is going broadcast its time to the CARESCAPE
Master. [{time}] [{unit|bed}] Network time master.
Apply time master time to OS: This message indicates that CARESCAPE Gateway is going to set its OS time.
{time}
Dates NOT within window This message indicates that CARESCAPE Gateway has determined that either the OS or
[date1:date2:window] CARESCAPE Network time master time is not in sync and will be scheduling an update for the
offending time source. This message can be a normal occurrence as CARESCAPE Gateway
continues to keep both its OS time and CARESCAPE Network time in sync.
Webmin actions log

The Webmin Actions Log provides Webmin action event data sorted by: user,
Webmin module and date/time.
To access the Webmin Actions Log:

Troubleshooting
2. Select Diagnostics > Webmin Actions Log.
3. Select radio button choices to configure the Webmin action log search filter by
user, Webmin module and date/time, as desired. Select desired choices from the
associated drop-down lists and/or enter the desired date parameters as
appropriate.
4. Click Search. The Webmin actions log Search Results display, filtered by the
selected search criteria.

Troubleshooting
Item Name Description
Action Description of the action taken.
Module Webmin module (function) where the action was performed.
User The login username of the user that performed the action.
Client Address IP address of the device where the action initiated.
Date Date of the action.
Time Time of the action.
5. Click an action to display details about that action.
Retrieving iLO log files

If the CARESCAPE Gateway enters a fault condition, iLO has an event logging
feature which contains data about the fault.
1. Login to iLO. See Connecting to iLO on page 2-21.
2. Click iLO Event Log.
3. For more information about iLO, refer to the HP Integrated Lights-Out User
InSite notification events

Hardware related events
The following table lists the hardware and platform related events for InSite Event
Notification.
NOTE
The following hardware events are for the HP ProLiant DL360 G7 server.
Event Description Severity Corrective action
cpqHo2GenericTrap Generic trap Notify No action needed.
cpqHe3FltTolPowerRedundancyLost Power redundancy lost Notify Notify site representative, unless

there is prior knowledge of planned
maintenance.
cpqHe3FltTolPowerSupplyRemoved Power supply removed Notify Reinsert power supply.
cpqHe3FltTolPowerSupplyInserted Power supply inserted Notify Issue resolved.
cpqHe4FltTolPowerSupplyDegraded Power supply degraded Minor Perform visual inspection.

Replacement may be necessary.
cpqHe4FltTolPowerSupplyFailed Power supply failed Minor Perform visual inspection.

cpqHe4FltTolPowerSupplyACpowerloss Power supply AC power loss Minor Notify site representative.

Troubleshooting
cpqHe3FltTolPowerRedundancyRestored Power supply redundancy is restored Notify Issue resolved.
cpqHe4FltTolPowerSupplyOk Power supply transitions from failed Notify Issue resolved.

to OK
cpqHe3FltTolFanDegraded Fan degraded Minor Perform visual inspection.

cpqHe3FltTolFanFailed Fan failed Minor Perform visual inspection.

cpqHe3ThermalSystemFanDegraded System fan degraded Minor Perform visual inspection.

cpqHe3ThermalSystemFanFailed System fan failed Minor Perform visual inspection.

cpqHe3ThermalSystemFanOk System fan transitions from failed to Notify Issue resolved.

OK
cpqHe3ThermalCpuFanFailed CPU fan failed Major Replace fan.
cpqHe3ThermalCpuFanOk CPU fan transitions from failed to OK Notify Issue resolved.
cpqNic3RedundancyReduced Ethernet interface team loses Minor See Troubleshooting network

redundancy problems on page 5-8.
cpqNic3RedundancyIncreased Ethernet interface team's redundancy Notify Issue resolved.

restored
cpqNic3ConnectivityLost Network interface has lost Major See Troubleshooting network

connectivity problems on page 5-8.
cpqNic3ConnectivityRestored Network connectivity restored Notify Issue resolved.
cpqHo2NicStatusFailed NIC has failed Major Perform SmartStart Diagnostics.
cpqHo2NicStatusOk NIC status transitions from failed to Notify Issue resolved.

OK
cpqDa7PhyDrvStatusChange Physical drive status changes Major See System management homepage
on page 5-2. Component
replacement may be necessary.
cpqDa6LogDrvStatusChange Logical drive status changes Major See System management homepage
on page 5-2. Component
replacement may be necessary.
Critical-Process-Restart-Threshold Watchdog fails to restart a process Major Refer to the appropriate

troubleshooting information for the
affected service.
Application related events

The following table lists the application (software) related events for InSite Event
Notification.

Troubleshooting
ADT-Communication-Error-CSG-PDC The CSG application is not Major See ADT troubleshooting on page 5-
communicating with Patient Data 21.
Cache (PDC), resulting in an ADT
failure.
ADT-Communication-Recovered-CSG- The CSG application starts Notify Issue resolved.

PDC communicating with the Patient Data
Cache (PDC), having recovered from
the previous failed state.
HL7-Communication-Error-CSG- The CSG application is not Major See HL7 troubleshooting on page 5-
Cloverleaf communicating with Cloverleaf, 26 and Cloverleaf troubleshooting on
resulting in an HL7 failure. page 5-30.
HL7-Communication-Recovered-CSG- The CSG application starts Notify Issue resolved.

Cloverleaf communicating with Cloverleaf,
having recovered from the previous
failed state.
CIS-Connection-Error The system shall notify when the Minor See HL7 troubleshooting on page 5-
Clinical Information System has been 26.
disconnected for 20 minutes
unexpectedly.
HSDI-Client-Connection-Error A client unexpectedly disconnected Minor See HSDI troubleshooting on page 5-

from the High Speed Data Interface 32.
(HDSI).
Time-Out-of-Sync-Threshold The system is unable to update the Minor See CARESCAPE Gateway time
time master's time for an hour. services troubleshooting on page 5-
20.
Time-Out-of-Sync-Recovered The time update to the time master Notify Issue resolved.
has recovered after a previous error.
Database viewer
The database viewer can be used to search for an order with the CCG local cache or
database. The contents of the local cache or database can be searched and displayed
based of configurable criteria.
Open Database Viewer

In Webmin, select Configuration > Database Viewer.
Searches are available in one of the following three options:
 Query by Patient
 Query by Order (not used by CARESCAPE Gateway)
 Query by Location

Troubleshooting
NOTE
The Database viewer follows the Oracle standards for special characters:
 The % (percent) character is a wildcard that matches zero or more characters

in the string.
 The _ (underscore) character is a wildcard that matches exactly one
character in the string. A match only occurs if there is a character in that
spot.
 The & (ampersand) character is not allowed in any of the search fields.
Query by patient
1. To search for items related to a particular patient, enter the appropriate data into
at least one of the following fields indicated by a * after the field name:
 ID Value: the patient ID.

 Assigning Authority ID: either PE or PI.
 Last Name: the patient’s family name.
 First Name: the patient’s given name.
2. Click Submit.
3. Click the View Details link for the appropriate item from the Query Results list.
Query by location
1. To search for items related to a unit number or bed number, enter the appropriate
data into the Unit and/or Bed field.
2. Click Submit.
3. Click the View Details link for the appropriate item from the Query Results list.
View the results

After clicking View Details, the Patient Details pane will open. By default, the
Patient Tree is expanded to show the Demographics Information table.
Click Expand All to view the complete details for the Patient Tree.
Click the + button to view the details. Continue to click the + buttons to navigate to
the level of details necessary. Detailed information may include visits, orders,
services, and lists of scheduled service steps.
NOTE
When a particular data record is expanded to a given level, the database viewer
will remember the expansion level. For example, if the service details for a
particular order was expanded and then order is closed. The next time that order
is expanded, the service details will also be expanded.

6 Field replaceable units
(FRU)

Field replaceable units (FRU)
Ordering parts
Overview
To order parts, contact GE. Be sure to have information about the CARESCAPE
Gateway ready. See View server configuration on page 7-10.
HP ProLiant DL360 G7 server FRUs
Item Number Item Description
2052606-001 DIMM memory module / 2 GB
2052606-002 Hard drive SPS
2052606-003 Fan module
2052606-004 AC power supply
2052606-005 DVD-ROM SATA optical disk drive
2023245-001 3.0 V internal lithium battery
2013539-005 Whole unit
2056104-001 CSG G7 v1 System Failure Recovery Kit
Field replacement procedures

Overview
NOTE
First complete preparation procedures before performing any other procedure in

this chapter. See Field replacement preparation on page 6-2.
For field replacement procedure information, refer to the HP ProLiant DL360 G7

Field replacement preparation
WARNING
SHOCK HAZARD—Make sure that all power cords and all other
cables are disconnected from the server before removing the cover.
Severe electrical shock could result from not following this
instruction.

CAUTION
ELECTROSTATIC DISCHARGE—Do not touch any internal metal
parts. Place the server on top of a grounded electrostatic discharge
(ESD) pad. Use the disposable antistatic wrist strap supplied with
the server and stick it to the metal base of the server before touching
any of the internal components. The server contains electronic parts
that are extremely sensitive to static electricity. Damage to the server
could result if this instruction is not followed.
Refer to the HP documentation for additional component service information. See

Whenever a system component is to be replaced, shut down the system. Only a

qualified service technician should perform the field replacement procedures.
Observe these safety guidelines before opening the CARESCAPE Gateway case.
1. Label and disconnect everything connected to the I/O connectors or ports and
power cords.
2. Always provide electrostatic discharge (ESD) protection by wearing an antistatic

wrist strap attached to the chassis ground of the system (any unpainted metal
surface) whenever handling CARESCAPE Gateway components.
Hard drive replacement

1. Replace the hard drive. Refer to the appropriate HP Proliant DL360 Server
Maintenance and Service Guide for details.
2. Start up the CARESCAPE Gateway.
3. The new hard drive will start to automatically rebuild due to the mirrored (raid 1)
configuration of the hard drives. The rebuilding operation can be monitored on
the HP System Management page via Webmin. If both hard drives have failed, or
if the second hard drive is replaced before the rebuild is complete, a complete
reload of the system will be required.
License keys and hardware MAC address

HL7, ADT and Cloverleaf license keys are linked to the CARESCAPE Gateway
MAC address values. If hardware affecting MAC address values is replaced, contact
GE to obtain new license keys.
Be sure to be ready with CARESCAPE Gateway configuration information. See

View server configuration on page 7-10.


7 Administration

Administration
CARESCAPE Network MC/IX configuration
WARNING
data loss.
NOTE
Set the CARESCAPE Network IP address using an iLO connection. If Webmin

is used to change the CARESCAPE Network IX IP address with the firewall
enabled, the Webmin connection to the CARESCAPE Gateway will be broken.
NOTE
The Webmin Network Interfaces function displays the CARESCAPE Gateway

network interface information.
To access the Network Interfaces function:
3. Select in the Integrated Remote Console section click Launch. Click in the
remote console window to activate it.
4. Double-click the Webmin icon on the CARESCAPE Gateway desktop in the

remote console window.
5. Log into Webmin. See Service logons on page 2-20.
6. If necessary, configure the CARESCAPE Network MC and IX IP addresses. See

CARESCAPE Network MC, IX and S/5 Network configuration on page 3-14.
iLO management/configuration
Overview
WARNING
LOSS OF CONNECTIVITY—Be extremely careful not to assign
the same IP address to two different devices on the network.
data loss.

Administration
NOTE
IP/netmask/(router/gateway) configuration
If necessary, configure the CARESCAPE Network IX iLO IP address for the
CARESCAPE Gateway. See iLO IP address configuration on page 3-12.
iLO password configuration

3. Select the user requiring a password change from the list.
4. Type the new password.
NOTE

5. Click Save.
iLO reset/reboot
NOTE
Clicking the Reset button resets the CARESCAPE Gateway iLO settings to
factory defaults. Once Reset is clicked, the iLO license will need to be re-entered.
See iLO license key activation on page 7-4.
3. In the Reset Commands section, either click Reset or Restart as necessary.
NOTE
Refer to the label on the CARESCAPE Gateway cover for default iLO
Administrator password settings.

Administration
iLO license key activation

If iLO is reset back to factory defaults, the advanced iLO license will need to be
reapplied. Perform the following steps to reapply the license:
1. Login to iLO.
2. Select Administration > Licensing.
3. Enter the iLO license activation key.
For DL360 G7 servers: Re-enter the license key from the label on the server OR
Contact GE for the advanced iLO license key information.
4. Click Install.
iLO SNMP configuration

The following procedure is necessary to enable InSite event notification.
2. Click the Administration tab and select Management from the menu.
3. Enter the CARESCAPE Gateway’s IX IP address in the SNMP Alert

Destination(s) field.
4. Make sure that the following options are enabled:
 iLO 3 SNMP Alerts

 Forward Insight Manager Agent SNMP alerts
 SNMP Pass-thru
Purge ADT configuration

The purge configuration settings determine the length of time (number of days)
patient record data is retained by the CARESCAPE Gateway. Settings for the in-
patient, out-patient, and discharged patient records purge settings can be configured
independently.
The CARESCAPE Gateway requires the PV1-2 segment to be either an I for

Inpatient or an O for outpatient for purge cycles to delete old records that have not
been discharged. The ADT database purge is based on this field that is stored in the
ADT database. Therefore, if PV1-2 is E for emergency or P for pre-admit, the records
will not be purged because they do not match either I or O. This leads to stale entries

Administration
in the database that do not get deleted. The solution is to create an IF operation
translation that converts the classification code to either I or O in the ADT messages
for the purge cycle to work correctly.
Once you add a translation using the IF operation, set the equation to the following
rule:
 If PV1-2 = I, do nothing.
 Otherwise, set the PV1-2 value to O.
To configure the purge settings:
2. Select Configuration > Purge Configuration.
3. If applicable, change the number of days between in-patient/out-patient/

discharged patient record purges.
4. Click Update to save any purge configuration changes. Click Reset to undo any
purge configuration changes.
Backup and restore

Overview
NOTE

CARESCAPE Gateway configuration is changed to ensure complete system
after CARESCAPE Gateway configuration changes could result in lost licensing,
interface and application configuration data.
Backup contents
Backup/restore is associated with the following:
 Categories
 CSG Properties
 Cloverleaf Sites/Server Files
 CSG License Keys

Administration
 Cloverleaf Key
 CSG Batch Files
The following CARESCAPE Gateway files and directories are impacted by the
backup/restore process:
 /usr/gehc/csg/resources/s5BedList.properties
 /usr/gehc/csg/resources/filterList.properties
 /usr/gehc/csg/resources/rwhat.properties
 /usr/gehc/csg/resources/ugsUser.properties
 /usr/gehc/csg/resources/license/hl7licensekey.txt
 /usr/gehc/csg/resources/license/dacqlicensekey.txt
 /usr/gehc/csg/resources/license/swavlicensekey.txt
 /usr/gehc/csg/resources/license/snumlicensekey.txt
 /usr/gehc/csg/resources/license/cccclicensekey.txt
 /usr/gehc/csg/resources/license/vodlicensekey.txt
 /usr/gehc/csg/resources/unit.properties
 /usr/gehc/csg/resources/unitBed.properties
 /usr/gehc/csg/resources/s5CentralList.properties
 /usr/gehc/csg/resources/device.properties
 /usr/gehc/csg/resources/errorNotification.properties
 /usr/gehc/csg/resources/sapphire.properties
 /usr/gehc/ccg/quovadx/qdx5.7MB/integrator/vers/license.dat
Backup
NOTE
Scheduled tasks are not included in the backup file and will need to be re-created
manually.
NOTE
The system automatically performs a daily backup. The system will retain 90
days of backup files.
To perform the backup procedure:
1. Select Configuration > Backup and Restore > Backup.

Administration
2. Select the appropriate checkboxes and click Backup.
3. Scroll to the bottom of the page and click the Use the Upload and Download
Module to retrieve this archive link.
4. Click Download.
5. Click the Save this file to disk radio button in the File Download window and
click OK.
6. Navigate to the directory where you want to save the backup file. Click Save to
save the file.
NOTE
It is recommended to save a copy of the backup file to storage external to the

CARESCAPE Gateway in case of system failure.
Restore factory defaults

The Restore Factory Defaults function provides a method to erase all accumulated
data from the various data stores maintained by the subsystems of the CARESCAPE
Gateway. This function may be utilized in the event the system is in a state where it
continuously malfunctions and restarting the system does not correct the problem.

Administration
NOTE
To view the Factory Defaults options, all the application subsystems except the
Reload System Firewall must be stopped.
The options listed on the restore factory defaults page are as follows.
 OS Platform Settings — Restores network settings and NTP settings to factory

defaults.
 CCG Patient Data Cache Settings — Using the CCG Patient Data Cache
Settings will restore the ADT database settings to factory defaults.
 CCG Interfaces — A list of all Cloverleaf sites that end with _prod are
displayed, allowing the user to backup the current site, remove it, and then
activate the site from its CARESCAPE Gateway factory default. Since a backup
of the Cloverleaf sites was created after the configuration by GE was completed,
this option should not be needed in troubleshooting a corrupted Cloverleaf site.
However, in the event that a backup is not available (e.g., during product
installation), this allows the factory default version to be restored.
 CARESCAPE Gateway Settings — Restores the CARESCAPE Gateway
settings to the factory defaults (e.g. Picklist query size).
 Reset Patient Data Cache Database — Using the Reset Patient Data Cache
Database will erase all ADT data received from the HIS.
 Reset Historical Statistics Database — Delete all collected statistics from the
Historical Statistics module.
 Clear Device Cache — The device cache is continuously updated as the CSG
subsystem collects data from the CARESCAPE Network monitoring devices.
This information is used when the CSG subsystem is restarted so that it can
reliably collect the appropriate data from the devices while it was not running.
This process is referred to as back collection. The data in this file contains
information regarding the state of a device, patient information, the timestamp of
the last data collected from a device and the timestamp of the last data send to the
Cloverleaf subsystem. Using the Erase the CSG Device Cache option will purge
all of this information so that when started, the CSG subsystem will not have any
information regarding the state of the CARESCAPE Network monitoring devices
when the CSG system was stopped.
 Clean up temporary and log files — Removes all current and archive log files
and clears the /tmp directory.
 Insite — Restores the proxy and other configuration settings for the Insite ExC
Engine.

Administration
Restore configuration backups/factory defaults

NOTE
Scheduled tasks are not included in the backup file and will need to be re-created
manually.
To perform the restore procedure:
1. Shut down the CARESCAPE Gateway application subsystems. See Start/stop

CARESCAPE Gateway using Webmin on page 2-27.
2. Select Configuration > Backup and Restore > Restore.
3. Click the ... button. Using the Choose file window, navigate to and select the
appropriate backed up configuration file. Click OK.
4. Click Continue.
5. Select the appropriate option(s) checkbox(es) and click Restore.
6. Scroll to the bottom of the Restore page and ensure it states Restore complete.
7. If NTP service is being utilized on the CARESCAPE Gateway, perform the

following steps:
a. In Webmin, select Configuration > System Time > NTPD Settings.
b. Verify the IP address is correct and click Save.
8. Restart the CARESCAPE Gateway application subsystems. (In Webmin, select

Configuration > CARESCAPE Gateway > System Manager.

Administration
Password management
The Webmin Users window is used to change the account password and displays
Webmin user profile/access configuration.
To access the Password Management window:
2. Select Configuration > Password Management.
3. Type the new password in the Password and Retype Password text boxes for the
appropriate username.
NOTE

NOTE
It is important to change the factory default customer account passwords.

Using the same password across multiple sites reduces security and allows
potentially unauthorized individuals to access information and configuration
settings.
Some guidelines for creating strong passwords are:
 Avoid using dictionary words, letter or number sequences

 Include numbers and symbols
 Use capital and lower-case letters
 Use a variety of characters
4. Click Change.
View server configuration

NOTE
View Server Configuration provides the CARESCAPE Gateway information

required whenever contacting GE.
The Webmin View Server Configuration function displays the CARESCAPE

Gateway configuration information, such as: serial numbers, operating system
version, hostname, installation hotfixes, software versions, configured interfaces, and
Cloverleaf licenses.

Administration
To access the View Server Configuration function:
2. Select Information > View Server Configuration.

Administration
View Server Configuration Descriptions
Configuration Item Description
Hostname Computer name of the CARESCAPE Gateway.
Customer Name Customer or site name entered on the CARESCAPE

Gateway.
GEMS Serial Number GE serial number used for service tracking and warranty
identification.
HP Device Serial Number Hewlett-Packard serial number used for service tracking and
warranty identification.
Linux Distribution Version Currently installed Linux operating system version.
Software Versions Version numbers of currently installed software packages.
Configured Interfaces Currently configured network connection interfaces.
Routing Table Defines IP routing traffic for the system.
Firewall Rules Current firewall exceptions.
NTP Server IP IP address of NTP time master server.
Current Timezone Setting Currently selected timezone.
InSite ExC Proxy Server Server for InSite callback to GE Enterprise proxy.
SMTP Relay Host Server for email.
ADT ADT license string.
High Speed Data Interface License string.

Client Connection Count
Device Count License string.

Waveforms

Numerics
Unsolicited Hl7 Outbound HL7 license string.

Feed
Vitals On Demand License string.
Cloverleaf License Cloverleaf license information.
ADT workflow configuration
CAUTION
INCORRECT PATIENT DATA — Personnel should have level 2
Cloverleaf training to configure the integration engine.
To edit the workflow properties:

Administration
1. Open the /usr/gehc/ccg/conf/Workflow.properties file.
2. Make the required changes to the file.
NOTE
Refer to the CARESCAPE Gateway HL7 Reference Manual for detailed

information about supported workflow functions for each ADT HL7
message type with respect to the ADT workflow ADMIT_FLAG behavior.
3. Select File > Save to save any changed settings. Close the window to cancel any
changes.
CARESCAPE Network MC bed list

Overview
To view the bedlist in Webmin, perform the following steps.
NOTE
If a device’s name is changed to one that is not on the bedlist, data collection for
that device will stop.
1. Logon to the Webmin application.
2. Select Configuration > CARESCAPE Gateway Configuration >Configuration.
3. Click CARESCAPE Network MC Bed List > Bed List. A variety of bed list
functions are available (add/remove beds, set collection intervals, HIS mapping).

Administration
Add/Remove beds
NOTE
All devices on the CARESCAPE Gateway bed list and the CARESCAPE
Gateway system must reside on the fully-switched CARESCAPE Network.
Units
NOTE
Information displayed reflects RWHAT data.
1. Select Bed List > Network Update.
2. Click Select All, or select individual units in the Units Currently on Network
table.
3. To add all the beds in the selected unit(s), click Add Unit.
NOTE
When adding a unit using the Add Unit button, any HIS mappings defined
for beds in that unit are removed. Only use Add Unit if you do not use HIS
mappings. If you use HIS mappings, follow the Multiple beds procedure
below.
4. To delete all the beds in the selected unit(s), click Remove Unit.
Multiple beds
1. Select Bed List > Network Update.
2. Click Select All, or select individual beds in the Beds Currently on Network
table.

Administration
3. To add all the selected beds, click Add Selected.
4. To delete all the selected beds, click Remove Selected.
Individual beds
NOTE
This procedure is used primarily to add/remove beds which are not on the
network.
1. Select Bed List > Manual Update.

Administration
2. To add non-telemetry unit/beds, type the Unit name, the Bed name and any HIS
Mapping code, if required, into the Add Device By Logical Name fields. Select
the bed data collection frequency from the pull-down list.
3. To add the unit/bed, click Add Device.
4. To delete the bed, click Remove Device.
5. To add telemetry unit/beds, type the Unit name, the Bed name and any HIS
Mapping code, if required, into the Add Telemetry Device fields. Select the bed
data collection frequency from the pull-down list.
6. To add the unit/bed click Add Telemetry Device.
7. To delete the unit/bed, click Remove Selected.
Change collection intervals

The Collection Intervals utility is used to change the interval of an entire unit at once
or individual beds in that unit as desired.

> Setup > CARESCAPE Network MC Bed List >Collection Intervals.
2. Select the unit containing the beds for collection interval modification.
NOTE
The change to the interval will take effect on all online beds. The new interval
will not be applied to offline beds that are within the unit. The offline beds will
need to have the change to the interval manually set.
3. To change the collection interval for an entire unit, select the collection interval
from the list and click Update Unit Intervals.

Administration
4. To change the collection interval for an individual bed (or several beds at once),
select the interval for each bed as required from the Collection Interval list, and
click Update Interval.
HIS mapping
HIS mapping is used to change/add/remove the alias assigned to a particular bed as
seen on the HIS. The name of the CARESCAPE Gateway unit and bed should match
the name of the HIS unit and bed as there is a one to one correspondence. A single
CARESCAPE Gateway unit should not be mapped to multiple HIS units.
NOTE
If the one to one match does not occur, ADT picklist issues will occur, such as
only the first HIS unit will appear even though the mapping may point to
multiple HIS units.
NOTE
This feature maps from the CARESCAPE Network Name to the HIS name.
To change HIS mapping:

> Setup > CARESCAPE Network Bed List > HIS Mapping.
2. In the row containing the unit/bed where mapping should be added or changed,
enter a new unit in the Updated Mapping column and click Update HIS
Mappings.

Administration
S/5 Network bed list

Update iCentral list
2. Select Configuration > CARESCAPE Gateway Configuration >

Configuration.
3. Select S5 Network Bed List > iCentral List
4. Type the iCentral IP/Hostname in the Add an iCentral textbox and click Add new
iCentral.
5. To enable the iCentral click Toggle All, or select individual iCentrals in the
Enable column of the Disabled iCentrals table and click Update iCentral List.
Overview
To view the bed list in Webmin, perform the following steps.
NOTE
If a device’s name is changed to one that is not on the bed list, data collection for
that device will stop.
S/5 Network Bed List


Administration
2. Select Configuration > CARESCAPE Gateway Configuration >

Configuration.
3. Click S5 Network Bed List > Bed List. A variety of bed list functions are
available (add/remove beds, set collection intervals, HIS mapping).
Add/Remove beds
NOTE
All devices on the CARESCAPE Gateway bed list and the CARESCAPE
Gateway system must reside on the fully-switched S/5 Network.
Units
NOTE
Information displayed reflects RWHAT data.
1. Select S5 Network Bed List > Network Update.
2. Click Toggle All, or select individual units in the Connected iCentrals table.
3. To add all the beds in the selected unit(s), click Add All Beds on Selected
iCentrals.
4. To delete all the beds in the selected unit(s), click Remove All Beds on Selected
iCentrals.

Administration
5. To set or change HIS mapping enter the information in the HIS mapping column.
To set or change the collection interval choose the appropriate option from the
dropdown menu in the Interval column. Click Update to apply.
Multiple beds
1. Select S5 Network Bed List > Network Update.
2. Click Toggle All, or select individual beds in the Connected Beds table.
3. To add all the selected beds, click Add Selected Beds.
4. To remove beds from the bedlist on the S/5 Network, select S5 Network Bed List
> Bed List and select Toggle all or select individual bed and click Update Bed
List.
5. To set or change HIS mapping enter the information in the HIS mapping column.
To set or change the collection interval choose the appropriate option from the
dropdown menu in the Interval column. Click Update to apply.
Properties configuration
The Cloverleaf server depends on information entered by the user in the Webmin
properties.
The Webmin Properties page is used to configure certain logging, collection and HL7
PID properties. It is also used for turning the time management service on/off, for
designating the CARESCAPE Gateway as the time manager (NTP) server, and for
forcing a time synchronization of the CARESCAPE Network MC.

> Setup > Properties.
3. Change values in the New Value column on Properties page as required.
4. Click Update Properties at the bottom of the page to save and apply the changes.

Administration
Property Name Additional Description
Allow back-collection for telemetry beds Enables or disables back collection for telemetry beds.
Default VOD HL7 Protocol Version Sets the version of HL7 being used for VoD when the
request message contains an HL7 version other than 2.3,
2.4 (VA) or 2.6 (PCD-01).
Full HL7 Logging If true, complete HL7 messages will be written to the
application log for each acquisition. If false, only the HL7
message headers will be written to the log for each
acquisition.
HL7 Domain Name Unique hospital domain identifier appended to

ADT_Inbound HL7 messages. Restrict this identifier to
three characters.
HL7 Protocol Version Sets the version of HL7 being used for trended data.

Administration
Property Name Additional Description
Integrate ADT data into HL7 PID segment Enabling this feature allows patient demographic
information is retrieved from the on-board ADT database
and inserted in the HL7 messages produced for VoD and
trended data.
Looks up patient data by using the PID from the monitor.
The following patient data is placed in the message when

it is available: patient name, date of birth, gender, and
account number.
Maximum back-collection times (hours) The maximum back-collection time value limits the
number of hours of data that will be back-collected from a
monitor/TRAM when it is reconnected to the network after
a transport. Default value is 8 hours. Can be configured
between 0-8 hours in hour increments.
Also refer to Transport modes and back-collection on

page 2-5.
Maximum persist time in hours Sets the maximum amount of time a device (object) is
tracked for back-collection. If the device is in transport
longer than this setting, it is no longer tracked for back-
collection.
Patient Identifier Type Code Unique patient ID (PID) code appended to ADT_Inbound
HL7 messages.Restrict this identifier to four characters.
Use the standard HL7 definitions for typecode.
Picklist query size Defines the maximum number of responses sent to the
client for a generic picklist query.
Picklist wildcard query Set the ability to allow or deny picklist wildcard query.
Pressure Units of Measure Set the pressure units of measure to mmHg or kPA.
The conversion formula used by the CARESCAPE

Gateway software to convert pressure measurements
from mmHg to kPa is:
Y (kPa) = X (mmHg) * 0.1333224 (kPa/mmHg)
The CARESCAPE Gateway reports the kPa pressure

number with a precision of +/- 0.01 kPa. This level of
precision is used to avoid introducing error due to
conversion and rounding.
Accuracy of the kPa pressure number is limited by the

accuracy of the mmHg pressure number from the monitor.
For example: +/- 0.5 mmHg accuracy from the monitor
corresponds to +/- 0.07 kPa accuracy from the
CARESCAPE Gateway.

Administration
Time synchronization properties configuration
CAUTION
history. Refer to the appropriate monitoring device’s product
changes.
NOTE
Do not allow wireless devices to act as time master. Wireless devices can drop
communication packets which may cause communication problems resulting in
time errors.
The Time Master Properties configuration table is located near the bottom of the
Properties page (select Configuration > CARESCAPE Gateway Configuration >
Configuration > Setup > Properties.)
1. The Allow Time Management services setting determines whether the MC

network time synchronization feature is enabled. Select On to enable the feature;
Off to turn it off.
Allow Time Management
On Off
Select Time Source CARESCAPE CARESCAPE Gateway sends the OS Time —

Gateway updates to the CARESCAPE Network MC.
Unity MC CARESCAPE Gateway listens to time master —

Network on CARESCAPE Network MC and updates its
internal clock.
NOTE
When adding multiple CARESCAPE Gateway systems to the network,

configure only one CARESCAPE Gateway as the time source (Allow Time
Management set to On and Select Time Source set to CARESCAPE
Gateway). All other CARESCAPE Gateway systems should have Select
Time Source set to Unity MC Network or have Allow Time Management
set to Off. If a mix of Aware Gateway and CARESCAPE Gateway systems
exist on the network, only one should be set as the time source.
NOTE
Enabling time synchronization is recommended to ensure consistent time

stamps on data records. If time synchronization is not used it may cause the
system to not trend data.

Administration
2. The Select Time Source value determines if the CARESCAPE Gateway

broadcasts time updates to the CARESCAPE Network MC time master. Select
CARESCAPE Gateway to enable the feature.
NOTE
The CARESCAPE Gateway time source setting has no effect if Allow Time
Management services is set to Off.
NOTE
To disable daylight saving time (DST) on the system, choose the time zone
GMT + or GMT- the appropriate number of hours for the location.
NOTE
The CARESCAPE Gateway should not be configured to synchronize to both

NTP and the MC network at the same time. If the Allow Time Management
services setting is On and the Select Time Source setting is Unity MC
Network , ensure that the system is not synchronized to an NTP server. If it
should be synchronized to the MC network and the NTP server address is
entered, remove the NTP server address so that the CARESCAPE Gateway
does not receive NTP updates. See NTP server computer IP address
NOTE
Time zone and daylight saving time may need to match HIS processing
configuration. Refer to the site survey.
3. Click the Time Synch Request button to force a CARESCAPE Network time
synchronization to the CARESCAPE Gateway time (when the CARESCAPE
Gateway is configured as the time source).

Administration
Display serial number information

NOTE
Do not change the CARESCAPE Gateway serial number. Only the system fail
recovery requires the re-entry of the serial number information.
To display the CARESCAPE Gateway serial number:
2. Select Configuration > Host Asset Settings.
3. If a system fail recovery procedure was performed, re-enter the GE serial number
and click Save.
NOTE
GE serial number is available from the View Server Configuration page and
is also printed on a label on the CARESCAPE Gateway cover. See View
server configuration on page 7-10.
Upload/download files
The Upload and Download page allows files to be transferred to and from a remote
computer that is accessing the CARESCAPE Gateway through Webmin. Follow the
appropriate procedure described in this section to download or upload files as
necessary.
Download
2. Select Diagnostics > Upload and Download.
3. Click the ... button at the right end of the File to Download field.
4. Navigate to the file on the CARESCAPE Gateway you want to download. Select
the file and click Ok.

Administration
5. Click Download in the Upload and Download window.
6. Click OK.
7. Navigate to the directory you want to save the downloaded file and click Save.

Administration
Upload
NOTE
For large file transfers (50 MB or larger) use the Insite File Transfer. Webmin file
upload utility should not be used for the large file transfers.
1. If necessary, Logon to the Webmin application. See Webmin logon on page 2-23.
3. Click a Browse button.
4. Navigate to the file on the remote computer you want to upload to the
CARESCAPE Gateway and click Open.

Administration
5. Repeat the previous step as necessary to upload up to four different files at the
same time.
6. Click Upload.
License configuration
Cloverleaf license
See Cloverleaf license configuration on page 3-21.
CARESCAPE Gateway license configuration

NOTE
License keys are linked to the CARESCAPE Gateway MAC address values. If
hardware affecting MAC address values is replaced, contact GE to obtain new
license keys.
Be sure to be ready with CARESCAPE Gateway configuration information. See

View server configuration on page 7-10.

> Setup > Licensing.
3. Scroll down to the appropriate license key fields.
4. Enter the license keys into the appropriate fields and click Update
<CARESCAPE Gateway feature> License.
5. If the proper license keys were entered, a message displays indicating that the
keys were successfully added.
6. To remove licenses, click Remove <CARESCAPE Gateway feature> License.

Administration
Common Cloverleaf configuration changes

Launch the Cloverleaf engine IDE (integrated development
environment)
1. Start a VNC or iLO session. See Remote desktop utilities on page 2-22 and/or
3. Use the Use the Local Config Server radio button to select the site to modify.
ADT inbound domain/typecode configuration

NOTE
The ADT typecode and domain must match the CARESCAPE Gateway property
settings for the same typecode and domain.
NOTE
GE recommends that you keep the length of the domain name identifier and the
typecode identifier short. Refer to the PID 3 definition in the CARESCAPE
Gateway HL7 Reference Manual for more information.
The following procedure configures the messages to include the PID domain and
typecode set on the CARESCAPE Gateway Patient Identifier Typecode row in the
Properties page in Webmin. See Properties configuration on page 7-20.
2. Select Use the Local Config Server radio button.
3. Select /usr/gehc/ccg/quovadx/qdx5.7MB/integrator/his_prod from the

integration services environment list and click Apply.
4. Double-click NetConfig on the Site Manager panel.

Administration
5. If necessary, click Yes in the pop-up window to break any existing lock on the
file.
6. Select the HIS_Inbound thread icon.
7. Right-click the HIS_Inbound thread icon and select Thread Properties from the
menu.
8. Select the Route Messages tab in the Thread Configuration - HIS_Inbound

window.
9. Select Messages > ADT_A(0[1-9]|1[012345689]|2[0-9]|3[0123789]|4[1-9].* >

xlate_HIS_OB_CCG.
10. Under Detail Properties, select the Xlate radio button and click Properties.
11. In the Xlate Route Details window, enter the appropriate string into the Xlate
field and click OK.

Administration
NOTE
 It is required to add the Xlate which contains the Typecode and Domain
translation at this step.
 If the HIS device uses English measuring units for height and weight,
also add the Xlate that contains the height and weight translation to
convert the English units to metric units. See the CARESCAPE
Gateway HL7 Reference Manual for an example ADT message with
height and weight.
 The PID-3 subcomponent 4 (Domain) and subcomponent 5 (Typecode)
must match the CARESCAPE Gateway properties setting for the ADT
queries to return the correct values in the PID information. The
encoding of PID-18 (account number) and PV1-19 (visit number) also
require the Domain and Typecode subcomponents.
NOTE
Refer to the CARESCAPE Gateway HL7 Reference Manual for
more information on data field requirements.
12. Click OK at the bottom of the Thread Configuration - HIS_Inbound window.
13. Select File > Save.
NOTE
An asterisk (*) appears next to the NetConfig tab at the top of the Cloverleaf
IDE right panel until the NetConfig change is saved.
Data caching parameter configuration

The following procedure sets the parameter for the length of time that data will be
cached between CARESCAPE Gateway and the HIS.
NOTE
The default length of time for caching data between CARESCAPE Gateway and
the HIS is 720 minutes (12 hours).
1. In a text editor, open the purgeMsgsOlderThan12Hours.pl file from the /usr/

gehc/ccg/quovadx/qdx5.7MB/integrator/his_prod/bin directory.

Administration
2. Locate and edit the following two lines by changing where it states “12 hours
ago” to the number of hours desired to be saved:
 #Remove only msgs older than 12 hours from the recovery database
system("hcidbdump -r -d GE_system_OB -E '12 hours ago' -D /tmp/
purgeFile");
 #Remove only messages older than 12 hours from the Outbound Results
error database
system("hcidbdump -e -d GE_system_OB -E '12 hours ago' -D /tmp/
purgeFile");
NOTE
Increasing the number to greater than 12 hours on a fully load system could
cause a Cloverleaf error due to the size of the database over time.
3. Save the changes.
Set up ADT feed forward

The CARESCAPE Gateway can be configured to send a duplicate copy of each ADT
message it receives to another system, e.g., MUSE. To configure this additional data
flow, follow the steps below. When finished, add an additional outgoing port for the
other system in the CARESCAPE Gateway firewall.
1. Double-click the IDE icon on the CARESCAPE Gateway desktop.
2. If prompted click the Use the Local Config Server radio button and select /usr/
gehc/ccg/quovadx/qdx5.7MB/integrator/his_prod from the integration services
environment list and click Apply.
3. Navigate to his_prod > NetConfig.
4. Add a thread by copying and pasting the HIS_OB_CSG thread and name it
forward_output_adt.
5. Edit the TCP properties to set the network address of the other server and the
port number to the port of the ADT inbound process on that server.
6. Right-click the HIS_Inbound icon and select Thread Properties.
7. Select the Route Messages tab.
8. Right-click ADT.* and select Add Route.
9. The route type will default to raw, click Properties.
10. In the Raw Route Details window, click List.
11. Select forward_output_adt from the list and click Apply.
12. In the Raw Route Details window, click Ok.
13. In the Thread Configuration window, click Ok.
14. Right-click on the NetConfig tab and select Save NetConfig.
15. Right-click on the Inbound process and select Control > Stop.

Administration
16. Right-click on the Inbound process and select Control > Start to restart the
process.
17. Select Configuration > CARESCAPE Gateway Configuration > Cloverleaf

thread startup module, and set the new thread to be External.
18. Restart the firewall.
Multiple CIS client support

Refer to the CARESCAPE Gateway HL7 Reference Manual for information on
configuring multiple CIS client support.
Software management
3. Click a Browse button and navigate to the appropriate .rpm or .tar file you want
to upload and click Open.
4. On the Upload and Download window, click Upload.
5. Select Configuration > Software Management.
6. Click the ... button. Using the Choose File window, navigate to and select the
appropriate software package file, and click Ok.
7. If applicable, check the Reinstall existing packages? checkbox.
8. Click Install.
Cloverleaf Webmin utilities

Cloverleaf interface management
NOTE
Interface management is used to add new interfaces to the system or to revert

interfaces to their default configuration.

Administration
2. Double-click on the Webmin icon.
4. Select Configuration > Interface Management.
5. Click Browse and navigate the interface you want to activate or restore from the
Activate an interface list.
6. Click Show Valid interface(s).
7. Select the interface(s) from the Available Interface(s) list.
8. Click Activate selected interface. The Deployment Status box will provide the
status of deployment and activation of the interface(s) process.
Cloverleaf interface backup

The following procedure creates a backup of the Cloverleaf interface configurations.
NOTE
Cloverleaf interfaces should be backed up whenever they are modified or

interface information could be lost with no possibility for recovery.
2. Select Configuration.
3. Select Interface Backup.
4. Select the interfaces you want to back up from the Installed Sites list.
NOTE
Hold down Ctrl and click to select multiple items from the lists.
5. Click Backup selected sites.

Administration
NOTE
For interface restore procedure, See Cloverleaf interface restore on page 7-35.
Cloverleaf interface restore

The following procedure restores previously backed up Cloverleaf interface
configurations.
NOTE
The Cloverleaf interface restore procedure overwrites existing interfaces. Any

configuration unique to the existing interfaces will be lost when this procedure is
performed.
2. Select Configuration.
3. Stop the Cloverleaf engine. See Start/stop CARESCAPE Gateway using

Webmin on page 2-27.
7. Select Configuration > Interface Management.
8. Click Browse and select the sites you want to restore from the list. The list
contains sites previously backed up. See Cloverleaf interface backup on page 7-
34.
NOTE
Hold down Ctrl and click to select multiple items from the list.
9. Click Restore.
10. Select the interfaces you want to restore in the.zip file.
NOTE
Hold down Ctrl and click to select multiple items from the list.
11. Click Restore selected interface(s).
12. Click Continue.
13. Selecting a backup before restoring checkbox will back up the currently selected
interface before restore replaces it.
NOTE
Restoring overwrites the interfaces currently in use. Backing up the

interfaces before restoring allows for undoing the restore, if necessary.
Unchecked items will not be backed up before being overwritten by the

restore process.

Administration
14. Click Backup selected interfaces and Restore all above interface(s).
A message is displayed which indicates if the restore process completed

successfully.
15. Start the Cloverleaf engine. See Start/stop CARESCAPE Gateway using
Webmin on page 2-27.
Cloverleaf license manager

The Cloverleaf license manager displays Cloverleaf license status, and allows editing
the content of the Cloverleaf license.dat file.
2. Select Configuration > Cloverleaf License Management.
3. To edit the Cloverleaf license .dat file:
a. Click Edit.
b. Edit the contents of the textbox as required and click Save.
NOTE
Contact GE to obtain a license key.
Interface monitor
Overview
The interface monitor displays Cloverleaf site thread statistics/information. Open
interface monitor by performing the following:
1. Start a VNC or iLO session (See Remote desktop utilities on page 2-22 and/or
Connecting to iLO on page 2-21.)

Administration
4. Navigate to Configuration > Interface Monitor
The following items are included in the list:
 Site Name - This is the Cloverleaf site name.

 Error count- This is the total number of messages that are in the Cloverleaf site’s
error database. The count is updated every two minutes
NOTE
The his_prod site should not have errors listed. If the error count for the
his_prod site is not zero, contact GE.
 Last update time - This is the time when the number of error messages was last
updated.
Click the appropriate link to view general site statistics or messages in the error
database.
View messages
Error count messages

To view messages in the Cloverleaf error database, click the Error Count link in the
Site Summary table.
The interface monitor will display a list of all the messages in the Cloverleaf error
database for that site. The error messages can be filtered by providing one of the
following values:
 Message ID - the ID generated by the Cloverleaf IDE.

 Message State - where the error occurred in the Cloverleaf data flow. This
information can by used by service to troubleshoot the system.
 Inbound Thread and Outbound Thread - the list of the threads where the message
generated an error.
If an outbound thread is listed, two of the most probably failure causes are:
 The message was rejected by the end system. In this case, contact the site
administrator as the end system may need changes.
 The message failed through the message translation. In this case, contact GE.
If no outbound thread is listed, then no route was configured. Contact GE. Once
the system has been configured correctly, messages can be sent again through
that thread.
 Error description - a short description of the error message. This field is limited
in length; more information about the error is available in the error details view.

Administration
If there is text in this field, the message failed externally, and the message
destination returned an error.
If there is no text in this field, it means the message failed internally. Contact GE
if this occurs.
 Date - the timestamp of when the error occurred, in a <Week Day>:<Month>:dd
hh:mm:ss <Time Zone>yyyy format, where <Week Day>, <Month>, and <Time
Zone> are displayed in text with three characters.
View message details

To view the details of an error for a given message, click the appropriate Message ID
link. The interface monitor will show the details of the selected message.
The items in the detail view include the actual HL7 message in addition to all of the
fields from the error list view. The length of the Error message is limited to 1500
characters in the detail view.
Manage messages with errors
Resend message
Messages can be resent in groups or individually
1. Select the message(s) to be resent:
 To resend a group of messages: select the checkboxes next to the Message

IDs of the applicable messages or click Select All to select all messages
shown
 To resend an individual message: click the Message ID link or select the
checkbox next to the Message ID.
2. Choose the message destination from the Select thread list.
 If the thread failed because it was rejected by the end system, and it is known
that the message text is correct, select the OB (outbound) thread for the end
system.
 If the message failed through the message translation, contact GE. After GE
has adjusted the message translation route, service would select a different
thread destination so the messages would be re-translated.
3. Select the appropriate entry from the TPS dropdown list.
NOTE
TPS is an acronym for TCL Procedure Stack.
 Inbound Pre-TPS — This option may be used if the message fails before it is
translated. This option is rarely used.
 Inbound Post-TPS — This option may be used if the message fails after it is
translated but before it gets to the outbound side. This option may be used
when the error is at CCG patient cache.
 Outbound Pre-TPS — This option may be used if changes have been made
to the TPS on the outbound side. This option is rarely used.
 Outbound Post-TPS — Use this option if the message is known to be correct
and the message does not need to be re-translated. This option will send the
message directly to the outbound thread without any further processing. This

Administration
is the option most commonly used when the message produced an error at
the destination.
4. Click Resend.
Retrieve and resend failed messages

1. In the Cloverleaf IDE, start a terminal window for the site with the failed
message.
2. Using hcidbdump -e retrieve a list of the failed messages in the error database.
3. Identify the number of the message to resend, and save the specific message to a
file using:
hcidbdump -e -m <msgid> <filename>
e.g. hcidbdump -e -m 313145 /tmp/msg-313145
4. Resend the message using hcicmd -p <process name> -c "<destination thread

name> resend <tps> data 5120 <full path to file> nl"
e.g. hcicmd -p outbound -c “GE_system_OB resend ip_pre_tps data 5120 /tmp/

msg-313145 nl”
Delete messages from the error database

1. Select the checkboxes next to the Message IDs for the appropriate messages to
be deleted.
2. Click Delete.
General site statistics
View general site statistics

Select the site name of the interface monitor page.
The columns in the thread statistics listing include:
 Process — This is the process name from the Cloverleaf IDE 5.7MB.
 State — The state of the Cloverleaf thread. Possibilities are running or dead. If
the process is in the running state, it can be stopped using the Stop Process toggle
button. If the process is in the dead state, it can be started by using the Start
Process toggle button.
 Message — This is the timestamp of when the thread was last started or the
process was last stopped manually or was crashed.
 Action — This shows the toggle button according to the state of the process.
Processes are able to be started or stopped using this button.
View thread statistics

To view statistics for a particular thread, click the thread name displayed in the
interface monitor. The Inter-Thread Statistics Page will appear for the selected
thread. The text in the Thread Data Section can be copied from the browser and
pasted into a text editor.

Administration
View site configuration

To view the configuration of a particular site, click the Site Configuration > Thread
Status Show Site Configuration link in the interface monitor.
NOTE
The text in the NetConfig section can be copied from the browser and pasted into
a text editor. The NetConfig listing includes:
 Processes and Connections

 Connection Procedures
 Data Routes
 Reply Routes
Processes and Connections

The list of processes and connections will vary depending on the customer’s
requirements
Connection Procedures
Connection procedures will vary from one installation to another. The following is an
example of part of the connection procedures information.
Data Routes
The following is a sample of a CCG_Inbound route.
Reply Routes
Each installation will have a different list of Data Routes and Reply Routes.
View thread status details

The Thread Status Page is provides details of various threads for a given site. It lists
process name, thread name, state, proto state and When Date information for enlisted
threads.
By default, CCG supports 50 character lengths for Process and Thread names. If any
process/thread name is more than this limit, it will be truncated and only first 50
characters will be displayed. However, CCG provides user the ability to configure this
value in the actual deployment. The process/thread length can be reconfigured by
editing <CCG_INSTALL_DIR>/quovadx/qdx5.7MB/integrator/bin/
ccg_hciconnstatus file.
Open this file in a text editor and locate the following line:
set fmt "%-50.50 %-50.50 %-10.10 %-15.15 %-20.20".
This format defines the length for all values in the above-mentioned page.
The generic format is as described below:
set fmt "%-<XX.XX as process name length> %-<XX.XX as thread name length>
%-
<XX.XX as state> %-<XX.XX as Proto State> %-<XX.XX as When>".

Administration
Make any change in the digit values only in this format and save it. DO NOT
DISTURB the overall format. Under normal conditions, you need to make changes
for process and thread name values only. It is not advisable to change values for State,
Proto State and When.
Similarly, for Process Status Page, it is possible to display process names that are
longer than specified limit. Reconfigure the process length by editing the
<CCG_INSTALL_DIR>/quovadx/qdx5.7MB/integrator/bin/ccg_hciprocstatus file.
Open this file in a text editor and locate the following line:
set fmt "%-50.50 %-8.8 %-50.50".
This format defines the length for all values in the above-mentioned page. The
generic format is as described below:
set fmt "%-<XX.XX as process name length> %-<XX.XX as state> %-<XX.XX as

Message Date>".
Ensure that process name length in <CCG_INSTALL_DIR>/quovadx/qdx5.7MB/

integrator/bin/ccg_hciprocstatus and <CCG_INSTALL_DIR>/quovadx/qdx5.7MB/
integrator/bin/ccg_hciconnstatus match for results to be correctly displayed.
Dashboard
Once the configuration is complete, consult with the CARESCAPE Gateway
Dashboard to identify key parameters that indicate the health of the CARESCAPE
Gateway server and subsystems. Select Configuration > CARESCAPE Gateway
Configuration > Configuration > Dashboard. The following information can be
found on the Dashboard:
Server Information —  Current Date

 Host Name
provides high level information about the CARESCAPE Gateway
server  Host Address
 CARESCAPE Network MC Address
 Total Memory
 Free Memory
Misc —  CARESCAPE Gateway Version

 Started
provides high level information about the CARESCAPE Gateway
software  Uptime
 Devices in Acquisition
NOTE
The devices in acquisition should match the number of
beds from which data is being collected.
 DACQ Licenses (active/assigned/total)
Command Queues —  Total received

 Total waiting
provides information on the state of the queue that contains all the
HL7 trend messages waiting to be sent to Cloverleaf  Total processed

Administration
HL7/Cloverleaf Processing (after 100 processed) —  Total sent to QVDX

 Total Acks from QVDX
provides information on the health of the CSG outbound module
that processes the trends collected from different devices and  Total waiting for QVDX connection
sends them to Cloverleaf in HL7 format.  Total QVDX connection errors
 QVDX connections [initial/current (active/idle)]
 HL7 Average process time
 HL7 process time Range
 QVDX Average response time
 QVDX Average response time (last 25)
 QVDX process time Range
 Quovadx processing threshold violations (15 sec) over past
10 mins
Total Threads and Total Thread Groups —  Parent Group Name

 Thread Group Name
provides information on the total number of threads being used or
currently running and the number of thread groups and their  Thread Count
individual thread counts
Metrics —  Total Requests

 Success
provides information on the ADT request processing
 Failure
 EG Errors
 Timeout Errors
 Invalid Location Errors
Time Bounds —  Min. Process Time

 Max. Process Time
provides information on the CARESCAPE Gateway response time
 Avg Process Time
 Last Process Time
ADT License Information —  MAC Address

 Current License Key
provides information on the ADT license
 Is ADT Available?
 Is License Key Valid?
HL7 License Information —  MAC Address

 Current license key
provides information on the HL7 licenses
 Is license key valid?
Device Cache Summary —  Number of entries in tram transport

 Number of entries in rover
provides information on the current state of the devices according
to the CARESCAPE Gateway device cache  Number of entries in acquisition
 Number of entries in inactive state
 Number of entries in device cache
Device Cache Configuration —  Purging interval time

 Cache entry persist time
provides the purging interval and the maximum persist time of the
entries in the device cache

8 System fail recovery

System fail recovery

A system fail recovery procedure should be performed in case of any failure that
causes the system software to be reloaded. To complete this procedure, you need the
Service kit for the applicable hardware and software version.
NOTE
This procedure will erase any data written to the hard drive since the last time the
CARESCAPE Gateway was installed.
NOTE
If at all possible, perform a system backup and record the server configuration
information before starting the system fail recovery procedure. See View server
configuration on page 7-10 and Backup on page 7-6. Toward the end of the
system fail recovery procedure, the system configuration information can be used
when configuring IP addresses/network settings, and the backed up configuration
file can be used to restore the CARESCAPE Gateway licenses and other settings.
NOTE
After the system recovery procedure is complete, the login passwords will be
reset to the factory defaults. The customer is responsible for reconfiguring the
login passwords.
GE Service personnel performing the System Failure Recovery should inform the
customer to reconfigure the login passwords.
The following procedure assumes the CARESCAPE Gateway is shut down.
1. In case of a system fail, the CARESCAPE Gateway might be powered off. Use a
bent paper clip to open the CD/DVD drawer when the CARESCAPE Gateway is
powered off.
NOTE
Virtual media cannot be used for re-Ghosting the CARESCAPE Gateway.

The Ghost CD/DVD must be physically in the CARESCAPE Gateway CD/
DVD drive during the Ghost process.
2. Insert the CARESCAPE Gateway platform DVD into the drive.
3. Connect and log in to iLO. See Connecting to iLO on page 2-21.

4. Select Remote Console > Remote Console. In the Integrated Remote Console
section, click Launch.
5. Select Power Management > Server Power and click Reset.
6. Click OK.
7. When system resets, press F11 to boot off of the CD-ROM drive.
8. At the prompt to re-image the system, press Enter.
9. When the Complete window displays, remove the DVD from the CARESCAPE
Gateway DVD drive and press Enter to reboot the CARESCAPE Gateway.
10. Log in as the appropriate user (service or biomed).
11. Double-click the Webmin icon on the remote console desktop.
12. Log in to Webmin.
13. Upload backup file from alternate media to the CARESCAPE Gateway. See
Upload on page 7-27.
14. Move backup file from /uploads directory to the /downloads/GEHC Backup
Archives directory using the file browser.
15. Restore the previous settings. See Restore configuration backups/factory defaults
on page 7-9.
NOTE
If a backup is not available, contact GE. The installation process will need to
be re-performed starting from NTP Server Computer IP Address
Configuration. See NTP server computer IP address configuration on page
3-17.
16. Verify VNC connectivity.
a. Start the VNC viewer on the PC/laptop.
b. In the VNC server field, enter the CARESCAPE Gateway CARESCAPE

Network IX IP address and select Connect.
c. Enter your server username and password.
d. Verify that you are connected to the server.
17. Configure the date and time for the CARESCAPE Gateway. See System time/
date configuration on page 3-16.
18. Access Webmin and select Configuration > System Manager.
19. Click Enable Apps.
20. Configure the secure data link (IX network router)/gateway referral settings, if
applicable. See Default router configuration on page 3-15.
22. Click Reboot System.
23. When prompted if you want to reboot the system, click Reboot System.

25. After all appropriate Application Subsystem Status entries display Running,
complete the checkout procedure. See Checkout procedure on page 4-5.

A Scenarios
2052436-002B CARESCAPE™ Gateway A-1

Scenarios
Scenario symbols
The following symbols are used through the case scenario sections.
Symbol Definition
Acquisition device is on-line.
Acquisition device is off-line.
Data is transmitted to the HIS according to the configured

interval.
NOTE
During this time, VOD request will be accepted.
Trended data is retroactively transmitted to the HIS when

acquisition device returns on-line.
Data is not transmitted to the HIS.
Patient is on-line and in a Leads Fail condition.
Patient is admitted.
Patient is discharged.
Patient is discharged from one acquisition device and

admitted to another acquisition device.
Patient is pre-admitted.
A-2 CARESCAPE™ Gateway 2052436-002B

Scenarios
Symbol Definition
Patient is automatically discharged.
A PID is entered.
Acquisition module.
Patient monitor.
Telemetry monitor.
Interface device.
Patient is being transferred.

Scenarios
Symbol Definition
Acquisition module is being transported.
Patient monitor is being transported.
CARESCAPE Network scenarios

Admit/Discharge/New Case scenarios
The following scenarios illustrate system behavior when data is stored during the
normal admit/discharge/new case sequence for a patient. These diagrams are intended
to depict what data can be viewed after all actions have been executed in a specific
scenario.
General guidelines
 The acquisition device's name must be setup for data collection in the
CARESCAPE Gateway’s Bedlist in order for the device's data to be transmitted
to the HIS. If a device’s name is changed to one that is not on the bedlist, data
collection for that device will stop.
 The CARESCAPE Gateway cannot transmit data to the HIS while an acquisition
device is off-line during transport.
 For trended data, the CARESCAPE Gateway (if enabled) will attempt to retrieve
the off-line data collected by the acquisition device once the acquisition device
returns on-line.
 Proper admit/discharge/new case procedures must be followed each time a new
patient is connected to an acquisition device. Refer to the appropriate device
operator’s manual for proper procedures.
 Having a PID and/or patient name entered in the patient monitor may or may not
be necessary for the data to be associated with the correct patient at the HIS. This
depends on your site-specific configuration.
 A PID can be entered at any time between admit and discharge or between admit
and the acquisition device going off-line.

Scenarios
 If the PID field is blank, the CARESCAPE Gateway will transmit the data with a
default PID (999999999).
 Once a PID is entered, the CARESCAPE Gateway will transmit the data tagged
with a PID from that point forward, until the time of discharge or between admit
 For devices that do not use an acquisition module, a PID can be entered while
off-line. For trended data, all off-line data will be transmitted to the HIS with the
new PID when the acquisition device returns on-line.
 For devices that use an acquisition module, a PID must be entered prior to
acquisition module transport, or trended data captured by the acquisition device
during acquisition module transport will not be transmitted to the HIS.
Standard Admit/Discharge
1 The acquisition device is on-line.
2 The patient is admitted without a PID. The CARESCAPE Gateway begins transmitting
the data with the default PID to the HIS.
NOTE
Depending on your site's particular implementation, the data may not be
accepted/acknowledged by the HIS unless a valid non-default PID is entered in
the acquisition device.
3 The CARESCAPE Gateway stops transmitting data to the HIS once the acquisition
device is discharged.

Scenarios
Admit before patient monitor comes on-line
1 The acquisition device is off-line for more than 24 hours or more than the Device
Cache Time limit.
NOTE
For HSDI data, the off-line data will not be transmitted regardless of the time the
acquisition device is off-line.
2 The patient is admitted. This data will not be transmitted.
NOTE
Since the amount of time off-line exceeded the Device Cache Time limit the data
acquired while off-line was not sent.
3 The acquisition device comes on-line. The CARESCAPE Gateway begins transmitting
the data to the HIS.
4 The CARESCAPE Gateway stops collecting once the acquisition device is discharged.
Patient monitor off-line before discharge
2 The patient is admitted. The CARESCAPE Gateway begins transmitting the data to the
HIS.
3 The acquisition device goes off-line. The CARESCAPE Gateway stops transmitting the
data to the HIS.

Scenarios
4 The data collected by the acquisition device while off-line is not transmitted to the HIS.
5 The acquisition device is discharged.
Discharge/Admit while off-line
HIS.
3 The acquisition device goes off-line in order to transport the patient. The CARESCAPE
Gateway stops transmitting data to the HIS.
4 The patient is discharged while the acquisition device is off-line. The data collected by
the acquisition device while off-line is lost, and cannot be transmitted to the HIS.
5 Prior to the acquisition device returning on-line, a new patient is admitted at the
acquisition device.
6 The CARESCAPE Gateway transmits the new patient’s data to the HIS once the
acquisition device comes back on-line.
7 For trended data, the data collected by the acquisition device for the new patient while
off-line is also retrieved and transmitted by the CARESCAPE Gateway to the HIS.
8 The CARESCAPE Gateway stops transmitting the data to the HIS once the acquisition
Patient transport scenarios

The following scenarios illustrate system behavior when data is stored during a
transport from one location to another location on the same acquisition device.
General guidelines
 The acquisition device’s name must be setup for data collection in the
device is off-line during a transport.
 For trended data, the CARESCAPE Gateway will (if enabled) attempt to retrieve
returns on-line.
 Using Rover Mode on the patient monitor (ability to change bed name without
discharging the bed) will not impact the data that is transmitted to the HIS, as

Scenarios
long as all bed names used by the patient monitor are configured for collection at
the CARESCAPE Gateway.
 CARESCAPE Gateway does not affect the acquisition device’s ability to store
patient data (on-line/off-line) via existing storage capabilities (acquisition
modules, internal memory, etc.).
Transport using patient monitor
HIS.
4 The CARESCAPE Gateway resumes transmitting the data to the HIS once the
5 For trended data, the data collected by the acquisition device while off-line is also
retrieved and transmitted by the CARESCAPE Gateway to the HIS.
Transport patient monitor to new unit

Scenarios
1 Acquisition device is on-line and is named, for example, “ICU|BED2”.
HIS.
4 The acquisition device comes on-line in a new care unit, and the clinician changes its
name to “CCU|BED5”.
5 The CARESCAPE Gateway resumes transmitting the data to the HIS once the
6 For trended data, the data collected by the acquisition device for the new patient while
off-line is also retrieved and transmitted by the CARESCAPE Gateway to the HIS. All
data will be sent to the HIS with the current bed name (CCU|BED5).
PID entered or changed during patient monitor transport
HIS.
NOTE
Depending on your site's particular implementation, the data may not be
transmitted to the HIS unless a valid non-default PID is entered in the acquisition
device.
3 The acquisition device goes off-line. The CARESCAPE Gateway stops transmitting
data to the HIS.
4 The PID is entered or changed during transport.
5 The CARESCAPE Gateway resumes transmitting the data once the acquisition device
comes back on-line.

Scenarios
6 For trended data, the data collected by the acquisition device while off-line is also
retrieved by the CARESCAPE Gateway and transmitted to the HIS with the PID
entered during transport.
7 The CARESCAPE Gateway stops collecting data once the acquisition device is
discharged.
Transport using an acquisition module
1 The acquisition device A is on-line with parameter data being acquired by the
acquisition device and the acquisition module.
2 The patient is admitted with a PID. The CARESCAPE Gateway begins transmitting the
data to the HIS.
NOTE
A PID entered in the patient monitor is required before the acquisition module is
transported in order to transmit the data collected by the acquisition module
during transport.
3 The acquisition module is removed from the acquisition device in order to transport the
patient.
4 The CARESCAPE Gateway stops transmitting data to the HIS for all parameters
associated with the acquisition module that has been removed for transport. These
parameters are now considered off-line.
NOTE
The CARESCAPE Gateway will continue to transmit the data to the HIS from any
active parameters until acquisition device A is discharged.

Scenarios
5 The acquisition device A is discharged. The CARESCAPE Gateway stops transmitting

6 The CARESCAPE Gateway begins transmitting data to the HIS once the acquisition
module is connected to acquisition device B that is on-line and admitted with the same
PID.
7 For trended data, the data collected by the TRAM module while it was off-line is also
retrieved and transmitted with a PID by the CARESCAPE Gateway to the HIS.
device B is discharged.
Transport using an acquisition module with a PID
HIS.
3 Prior to acquisition module removal, a PID is entered for the patient.
4 The acquisition module is removed from acquisition device A in order to transport the
patient.
parameters are now considered “off-line”.
NOTE
active parameters until acquisition device A is discharged.
module is re-inserted into the acquisition device that is on-line and admitted with the
same PID.
7 For trended data, the data collected by the acquisition module while it was off-line is
also retrieved and transmitted with a PID by the CARESCAPE Gateway to the HIS.

Scenarios
Transport using acquisition module without a PID
2 The patient is admitted. The CARESCAPE Gateway begins transmitting the data to
the HIS.
3 Prior to acquisition module removal, a PID is not entered for the patient.
NOTE
PID entry prior to acquisition module removal is required to allow the
CARESCAPE Gateway to transmit the transport data to the HIS once the
acquisition module is re-inserted in an acquisition device.
patient.
NOTE
active parameters until the acquisition device is discharged.
module is re-inserted into the acquisition device that is on-line. The data collected by
the acquisition module while it was removed and in transport is lost and cannot be
transmitted to the HIS since no PID was entered prior to the acquisition module
removal.

Scenarios
Transport using an acquisition module to different patient monitor
1 The acquisition device A is on-line with parameter data being acquired via the
acquisition device and the acquisition module.
HIS.
3 Prior to acquisition module removal, a PID is entered for the patient.
patient.
NOTE
active parameters until the acquisition device is discharged.
6 The acquisition device A is discharged.
module is connected to acquisition device B that is on-line and admitted with the same
PID.
8 For trended data, the data collected by the acquisition module while it was off-line is
also retrieved and transmitted with a PID by the CARESCAPE Gateway to the HIS.

Scenarios
Transport using a wireless patient monitor
1 The acquisition device A is on-line.
2 The patient is admitted. The CARESCAPE Gateway begins transmitting data to the
HIS.
3 The acquisition device A is discharged and the patient is admitted to a wireless patient
monitor for transport.
4 The patient is transported using a wireless patient monitor. In this scenario, the
wireless Dash patient monitor stays on-line so that the data is transmitted to the HIS
and the entire monitoring session including transport is transmitted to the HIS.
5 The wireless patient monitor is discharged and the patient is admitted with a PID to
acquisition device B. The CARESCAPE Gateway begins transmitting the data from
acquisition device B to the HIS.
Patient transfer scenarios

transfer from one acquisition device to another acquisition device in either the same
or different care areas.
General guidelines
 The acquisition devices' names must be setup for data collection in the
CARESCAPE Gateway's Bedlist in order for each device's data to be transmitted
device is off-line during a transport.
returns on-line.

Scenarios
Transfer while patient is off-line
HIS.
3 The acquisition device A is discharged and the patient is transferred to a new

acquisition device. The CARESCAPE Gateway stops transmitting the data to the HIS.
4 No data is transmitted to the HIS during an off-line transport.
5 The acquisition device B is on-line.
6 The patient is admitted. The CARESCAPE Gateway continues transmitting data to the
HIS.
Discharge patient after transfer to new acquisition device

Scenarios
HIS.
3 The patient is transferred to acquisition device B without being discharged from

acquisition device A.
4 The acquisition device A remains on-line and in a leads fail condition.
HIS.
7 Since acquisition device A is not discharged and continues to be in a leads fail

condition, the CARESCAPE Gateway will send data from both acquisition devices.
9 The CARESCAPE Gateway stops transmitting data from acquisition device A to the
HIS. The CARESCAPE Gateway continues to transmit data from acquisition device B
to the HIS.
10 The CARESCAPE Gateway stops collecting data once the acquisition device B is
discharged.
Pre-admit patient before transfer
2 The patient is admitted with a PID. The CARESCAPE Gateway begins transmitting
data to the HIS.
4 The patient is pre-admitted with the same PID to acquisition device B prior to being
discharged from acquisition device A. The CARESCAPE Gateway begins transmitting
the data from acquisition device B to the HIS.
5 The acquisition device A remains on-line and the CARESCAPE Gateway continues to
transmit data.

Scenarios
6 The acquisition device B remains on-line and in a leads fail condition.
7 Since acquisition device A is not discharged, the CARESCAPE Gateway will send data
from both acquisition devices.
to the HIS.
10 The patient is transferred to acquisition device B.
11 The CARESCAPE Gateway continues transmitting data from acquisition device B.
12 The CARESCAPE Gateway stops transmitting data once the acquisition device B is
discharged.
Combination Mode scenarios

The following scenarios illustrate system behavior when data is acquired via
telemetry systems but displayed on a networked patient monitor utilizing
Combination monitoring feature of the patient monitor.
General guidelines
 The acquisition devices’ names must be setup for data collection in the
CARESCAPE Gateway’s Bedlist in order for each device’s data to be transmitted
 Prior to entering Combo Mode, if the patient monitor and telemetry transmitter
have different PIDs, any parameters collected from the telemetry transmitter will
be transmitted to the HIS under the patient monitor’s PID. If the patient monitor
is discharged, the telemetry transmitter returns to its original PID.
Switch from telemetry to Combo Mode and back to telemetry

Scenarios
1 The telemetry device A is on-line.
2 The patient is admitted at the central station. The CARESCAPE Gateway begins
transmitting the data to the HIS.
4 The patient is then admitted to a patient monitor device B (without being discharged
from acquisition device A) utilizing the Combo Mode procedure in order to acquire
additional parameters while still collecting the original parameters from acquisition
device A.
5 The Combo Mode data is transmitted by the CARESCAPE Gateway to the HIS.
6 The additional parameters collected via acquisition device B are no longer required so
acquisition device B is discharged.
7 The CARESCAPE Gateway continues transmitting data to the HIS from acquisition
device A.
device A is discharged.
Switch from patient monitor to Combo Mode and back to patient monitor
1 The patient monitor device A is on-line.
HIS.
4 The patient is then admitted to a telemetry device B (without being discharged from
acquisition device A) utilizing the Combo Mode procedure in order to allow patient
mobility while still viewing the collected parameters at device A.
5 The Combo Mode data is transmitted by the CARESCAPE Gateway to the HIS.
6 The telemetry mobility via device B is no longer required so telemetry device B is

removed from Combo Mode monitoring.
7 The CARESCAPE Gateway continues transmitting data from device A.

Scenarios
Third-Party acquisition device scenarios

The following scenarios illustrate collection of data from third-party acquisition
devices connected to Unity Network ID connectivity device. Third-party devices
include ventilators, table-top pulse oximeters, anesthesia machines, and others.
Collected third-party data includes ventilator settings, ventilator measured values,
patient respiration rate, anesthetic agent concentrations and other data. Please consult
the product documentation for the Unity Network ID connectivity device for details
on which third-party devices are supported and what data is transmitted.
Unity Network ID connectivity device may attach to the CARESCAPE Network MC

as standalone devices (called standalone mode). In this mode, these devices send
collected third-party data directly to other devices on the CARESCAPE Network MC
such as CARESCAPE Gateway.
Unity Network ID connectivity device may associate with a Dash or Solar 8000M/i
patient monitor. In this configuration, called Association Mode, the Unity Network
ID connectivity device forwards collected third-party data to the associated patient
monitor. The patient monitor in turn forwards the third-party data to other devices on
the CARESCAPE Network MC such as CARESCAPE Gateway. When in
Association Mode, Unity Network ID connectivity device data becomes merged with
other data collected by a patient monitor.
Unity Network ID connectivity device is configured in one of two ways. The first is
as a standalone enabled device and as a Dash patient monitor associated mode
enabled device. The second is as a Solar 8000M/i patient monitor associated mode
enabled device. The main difference is the first allows movement between standalone
mode and Dash patient monitor Association Mode, while the second is restricted to
Solar 8000M/i patient monitor associated mode.
The CARESCAPE Gateway cannot transmit data to the HIS from a device while that
device is off-line. However, the CARESCAPE Gateway will attempt to collect the
trended data and transmit it to the HIS when the acquisition device returns on-line.
The CARESCAPE Gateway does not collect data from a discharged device.
General guidelines
 When Unity Network ID connectivity device operate on the CARESCAPE
Network MC in standalone mode, these devices have a UNIT and BED name
assigned to them.
CARESCAPE Gateway’s Bedlist in order for the device’s data to be transmitted
 Only Unity Network ID connectivity device supports Association Mode in
conjunction with Dash and Solar 8000M/i patient monitors. Please refer to the
Unity Network ID connectivity device operator’s manual for further information.
 If a Unity Network ID connectivity device is not connected to another patient
monitor via Association Mode, it is viewed by the CARESCAPE Gateway as a
separate device.
 If the patient monitor and Unity Network ID connectivity device were admitted
with different patient demographic data, then there will be two records until the

Scenarios
Unity Network ID connectivity device is connected to the patient monitor via

Association Mode.
Once the Unity Network ID connectivity device is connected to a patient monitor
via Association Mode, any parameters collected from the Unity Network ID
connectivity device will be tagged with the patient monitor’s unit and bed name
and the patient monitor’s patient demographic data. Discharging the patient
monitor will not cancel Association Mode. While the patient monitor is
discharged, CARESCAPE Gateway will not collect Unity Network ID
connectivity device data.
 Association must be explicitly broken by removing the Dash/Unity Network ID
Interconnect Cable joining the Dash patient monitor and the Unity Network ID
connectivity device or the network cable between the Solar 8000M/i patient
monitor and the Unity Network ID connectivity device. After Association Mode
is broken, the Unity Network ID connectivity device will be in a discharged state.
 Unity Network ID connectivity device when used in standalone mode requires an
admit from a central station in order for CARESCAPE Gateway to collect its
data and send it to the HIS. The central station may also be used to enter a PID or
the patient demographic data on the Unity Network ID connectivity device.
These steps are not necessary if the Unity Network ID connectivity device is only
used in Association Mode with other patient monitors.
Patient monitor/Unity Network ID connectivity device

In this scenario CARESCAPE Gateway collects data from a patient monitor and
sends it to a HIS. Later, someone decides to collect additional data from a third-party
device so a Unity Network ID connectivity is associated with the patient monitor. The
patient monitor merges the Unity Network ID connectivity device data into its own
data stream. The CARESCAPE Gateway now collects a combined data stream from
the patient monitor and sends it to the HIS. Later, the additional third-party data is no
longer desired, so the Unity Network ID connectivity device is removed. The patient
monitor now only provides its own data stream. This data is collected by the
CARESCAPE Gateway and sent to the HIS.
1 The patient monitor device A is on-line.
2 The patient is admitted at the patient monitor or central station. The CARESCAPE
Gateway begins collecting patient data and transmitting it to the HIS.

Scenarios
3 The Unity Network ID connectivity device B is online and connected to the patient
monitor using Association Mode.
4 The patient monitor A combines its own data and data from the Unity Network ID
connectivity device (device B) as a single data stream. CARESCAPE Gateway collects
the data stream and sends it to the HIS.
5 The additional parameters acquired via device B are no longer required so device B is
disconnected and association is broken.
6 The CARESCAPE Gateway continues transmitting the data to the HIS from device A.
The CARESCAPE Gateway stops transmitting the data to the HIS once the acquisition
Unity Network ID connectivity device and Dash patient monitor

In this scenario, the Unity Network ID connectivity device begins in stand-alone
mode, CARESCAPE Gateway collects the third-party data and sends it to the HIS.
Later, someone associates a Dash patient monitor to the Unity Network ID
connectivity device. The Dash patient monitor receives Unity Network ID
connectivity device data and merges it into its own data stream. The Unity Network
ID connectivity device stops sending its data to the CARESCAPE Gateway. The
CARESCAPE Gateway now collects a single data stream from the Dash patient
monitor containing both the Dash patient monitor and the Unity Network ID
connectivity device data. The CARESCAPE Gateway sends this data to the HIS.
Much later, the Dash patient monitor is removed and association is broken.
Since association was broken, the Unity Network ID connectivity device goes into a
discharged state. CARESCAPE Gateway will not collect data from a discharged
device. A clinician admits the Unity Network ID connectivity device from a central
station. CARESCAPE Gateway restarts collecting data from the Unity Network ID
connectivity device and sends it to the HIS. Eventually the Unity Network ID
connectivity device is discharged or removed from the network and CARESCAPE
Gateway stops sending Unity Network ID connectivity device data to the HIS.
It is important to understand that when discharging devices, such as the Unity

Network ID connectivity device, and Solar and Dash patient monitors, any stored data
(demographic and parameter data) is deleted from the device. This information must
be reentered so that patient data sent to the HIS can be associated with the patient’s
name and/or identifier.

Scenarios
1 The Unity Network ID connectivity device A is on-line.
2 The patient is admitted to the Unity Network ID connectivity device from the central
station. A PID may or may not be entered. The CARESCAPE Gateway begins
transmitting the data from the Unity Network ID connectivity device to the HIS.
3 The Dash patient monitor device B is on-line.
4 The patient is admitted with the same patient demographic data to the Dash patient
monitor device B.
5 The clinician connects the Dash patient monitor and Unity Network ID connectivity
device together in Association Mode, causing the Unity Network ID connectivity device
to be discharged.
6 The Device A and B data is transmitted from the Dash patient monitor to the
CARESCAPE Gateway and then by the CARESCAPE Gateway to the HIS.
7 The additional parameters collected via the Dash patient monitor device B are no
longer required so the Dash patient monitor is removed. This breaks association with
the Unity Network ID connectivity device and causes it to become discharged.
8 The clinician admits the Unity Network ID connectivity device from the central station
and enters the PID if used. The CARESCAPE Gateway collects third-party data from
the Unity Network ID connectivity device and sends it to the HIS.
S/5 Network scenarios

Admit/Discharge/New Case scenarios
The following scenarios illustrate system behavior when data is stored during the
normal admit/discharge/new case sequence for a patient. These diagrams are intended
to depict what data can be viewed after all actions have been executed in a specific
scenario.
General guidelines
device is off-line during transport.
returns on-line.
 Proper admit/discharge/new case procedures must be followed each time a new
patient is connected to an acquisition device. Refer to the appropriate device
operator’s manual for proper procedures.
 Having a PID and/or patient name entered in the patient monitor may or may not
be necessary for the data to be associated with the correct patient at the HIS. This
depends on your site-specific configuration.

Scenarios
 A PID can be entered at any time between admit and discharge or between admit
 If the PID field is blank, the CARESCAPE Gateway will transmit the data with a
default PID (999999999).
 Once a PID is entered, the CARESCAPE Gateway will transmit the data tagged
with a PID from that point forward, until the time of discharge or between admit
 The B series monitors with TRAM/PDM do not support back collection of data
when used with the S/5 Network or iCentral.
Standard Admit/Discharge
2 The patient is admitted without a PID. The CARESCAPE Gateway begins transmitting
the data with the default PID to the HIS.
NOTE
Depending on your site’s particular implementation, the data may not be
accepted/acknowledged by the HIS unless a valid non-default PID is entered in
the acquisition device.
Admit before patient monitor comes on-line

Scenarios
1 The acquisition device is off-line.
2 The patient is admitted. The trended data will back-collected.
3 The acquisition device comes on-line. The CARESCAPE Gateway begins transmitting
4 The CARESCAPE Gateway stops collecting once the acquisition device is discharged.
Patient monitor off-line before discharge
HIS.
3 The acquisition device goes off-line. The CARESCAPE Gateway stops transmitting the
data to the HIS.
4 The data collected by the acquisition device while off-line is not transmitted to the HIS.
5 The acquisition device is discharged.
Patient transfer scenarios

transfer from one acquisition device to another acquisition device in either the same
or different care areas.
General guidelines
 The acquisition devices’ names must be setup for data collection in the
CARESCAPE Gateway's Bedlist in order for each device’s data to be transmitted
to the HIS. If a device’s name is changed to one that is not on the Bedlist, data
returns on-line.

Scenarios
Transfer while patient is off-line
HIS.
3 The acquisition device A is discharged and the patient is transferred to a new

acquisition device. The CARESCAPE Gateway stops transmitting the data to the HIS.
4 No data is transmitted to the HIS during an off-line transport.
6 The patient is admitted. The CARESCAPE Gateway continues transmitting data to the
HIS.
Discharge patient after transfer to new acquisition device

Scenarios
HIS.
3 The patient is transferred to acquisition device B without being discharged from

acquisition device A.
4 The acquisition device A remains on-line and in a leads fail condition.
HIS.
7 Since acquisition device A is not discharged and continues to be in a leads fail

condition, the CARESCAPE Gateway will send data from both acquisition devices.
to the HIS.
10 The CARESCAPE Gateway stops collecting data once the acquisition device B is
discharged.

B Acknowledgements
2052436-002B CARESCAPE™ Gateway B-1

Acknowledgements
Acknowledgements
The CARESCAPE Gateway includes the following:
 Software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/).
 Cryptographic software written by Eric Young ([email protected]).
 Software developed by the Apache Software Foundation (http://
www.apache.org/).
 Software developed by Jamie Cameron (http://www.webmin.com,
[email protected]).
 Java Powered. Java and all Java based trademarks and logos are trademarks or
registered trademarks of Oracle America, Inc. in the U.S. and other countries.'
 Software developed by Jetty (http://www.mortbay.org/jetty/).
 Software licensed under the GNU GENERAL PUBLIC LICENSE. (http://
www.gnu.org).
 Software licensed under the ARTISTIC LICENSE. (http://www.opensource.org/
licenses/artistic-license.php).
 Software licensed under the GNU Lesser General Public License (http://
www.gnu.org/licenses/lgpl.html).
 This product includes software licensed under the COMMON DEVELOPMENT
AND DISTRIBUTION LICENSE (CDDL) Version 1.0 1 http://
glassfish.java.net/public/CDDLv1.0.html)
 Copyright (c) 2003-2010, Dennis M. Sosnoski.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met:
 Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
 Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation and/
or other materials provided with the distribution.
 Neither the name of JiBX nor the names of its contributors may be used to
endorse or promote products derived from this software without specific
prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
B-2 CARESCAPE™ Gateway 2052436-002B

Acknowledgements
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH

DAMAGE.
 The MX4J License, Version 1.0
Copyright (c) 2001-2004 by the MX4J contributors. All rights reserved.
1. Redistributions of source code must retain the above copyright notice, this
2. Redistributions in binary form must reproduce the above copyright notice,
3. The end-user documentation included with the redistribution, if any, must
include the following acknowledgment: "This product includes software
developed by the MX4J project (http://mx4j.sourceforge.net)." Alternately,
this acknowledgment may appear in the software itself, if and wherever such
third-party acknowledgments normally appear.
4. The name "MX4J" must not be used to endorse or promote products derived
from this software without prior written permission. For written permission,
please contact biorn_steedom [at] users [dot] sourceforge [dot] net
5. Products derived from this software may not be called "MX4J", nor may
"MX4J" appear in their name, without prior written permission of Simone
Bordet.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
MX4J CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
OF THE POSSIBILITY OF SUCH DAMAGE. '
 Indiana University Extreme! Lab Software License
Version 1.1.1
Copyright (c) 2002 Extreme! Lab, Indiana University. All rights reserved.
1. Redistributions of source code must retain the above copyright notice, this
2. Redistributions in binary form must reproduce the above copyright notice,
3. The end-user documentation included with the redistribution, if any, must
include the following acknowledgment:
2052436-002B CARESCAPE™ Gateway B-3

Acknowledgements
"This product includes software developed by the Indiana University

Extreme! Lab (<http://www.extreme.indiana.edu/>)."
Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "Indiana Univeristy" and "Indiana Univeristy Extreme! Lab"
must not be used to endorse or promote products derived from this software
without prior written permission. For written permission, please contact
<http://www.extreme.indiana.edu/>
5. Products derived from this software may not use "Indiana Univeristy" name
nor may "Indiana Univeristy" appear in their name, without prior written
permission of the Indiana University.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
AUTHORS, COPYRIGHT HOLDERS OR ITS CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.'
B-4 CARESCAPE™ Gateway 2052436-002B

C Compatibility
2052436-002B CARESCAPE™ Gateway C-1

Compatibility
Device compatibility
The CARESCAPE Gateway will collect patient data from the following GE
Healthcare monitoring products. Other CARESCAPE Network MC compatible
products will function per design without any interaction with the CARESCAPE
Gateway. Please contact GE if you want to connect a device that is compatible but has
a software version not listed. This list is subject to change without notice.
Supports Supports ADT Supports

Product Version Outbound Vital
Signs Request Admit1 ADT Picklist
3.9 Yes Using central station No

ApexPro
CARESCAPE B650 1.1 Yes No Yes
CARESCAPE B850 1.0 Yes No Yes
CDT-LAN2 6D3 Yes Using central station No
4.0.7 N/A Yes No
4.0.8 N/A Yes No
CIC Pro 4.1.1-2 N/A Yes No
5.1.0 N/A Yes Yes
5.2 N/A Yes Yes
3A Yes Yes No
Dash 2000
3B Yes Yes No
C-2 CARESCAPE™ Gateway 2052436-002B

Compatibility

2B Yes Yes No
2C Yes Yes No
3B Yes Yes No
3C Yes Yes No
3D Yes Yes No
4B Yes Yes No
4C Yes Yes No
5.1 Yes Yes No

Dash 3000/4000/5000
5.2 Yes Yes No
5.3 Yes Yes No
5.4 Yes Yes No
6.3 Yes Yes No
6.4 Yes Yes No
6.5 Yes Yes No
6.6 Yes Yes No
6.7 Yes Yes No
6.8 Yes Yes No
6.9 Yes Yes No
V2 HW, RAH SW Yes Using central station No
V2 HW, RAJ SW Yes Using central station No
V2 HW, RAK SW Yes Using central station No
V3 HW, RAA SW Yes Using central station No
V3 HW, RAB SW Yes Using central station No
Dinamap PRO 1000/1928 Adapter V1 V3 HW, RAC SW Yes Using central station No
V3 HW, RAD SW Yes Using central station No
V3 HW, RAE SW Yes Using central station No
V3 HW, RAF SW Yes Using central station No
V3 HW, 1A SW Yes Using central station No
V3 HW, 1B SW Yes Using central station No
3A3 Yes Using central station No
3B3 Yes Using central station No

Eagle 3000
4A Yes Yes No
4C Yes Yes No

Compatibility

5B3 Yes Using central station No
6A Yes Using central station No
6B Yes Using central station No
6C Yes Using central station No

Eagle 4000
6D Yes Using central station No
6E Yes Using central station No
6F Yes Using central station No
6G Yes Using central station No
LNET05 5.0.3 Yes No No
LNET05 5.1 Yes No No

iCentral45
5B Yes Yes No
Solar 7000/8000 5D Yes Yes No
5E Yes Yes No
6A Yes Yes No
7B Yes Yes No
7C Yes Yes No
1A Yes Yes No
1B Yes Yes No
1C Yes Yes No
2A Yes Yes No
3D Yes Yes No
4C Yes Yes No
Solar 8000M
4D Yes Yes No
4E Yes Yes No
4F Yes Yes No
5.2 Yes Yes No
5.3 Yes Yes No
5.4 Yes Yes No

Compatibility

4E Yes Yes No
4F Yes Yes No
Solar 8000i 5.2 Yes Yes No
5.3 Yes Yes No
5.4 Yes Yes No
3C Yes No No
4A Yes No No
Solar 9000/9500
4B Yes No No
4C Yes No No
17F3 Yes Using central station No
Tramscope 12 17G3 Yes Using central station No
17H3 Yes Using central station No

Unity Network ID
5D Yes Using central station No
1TRAM Module software earlier than v10A does not support storing a PID. When an earlier version of TRAM module is used with an ADT-
capable patient monitor, the PID will not be stored.
2This device is only supported in one-minute collection interval. Using central station indicates that the device does not support ADT
Request Admit directly. However, the transfer of patient demographic information can be performed at the central station.
3
CDT-LAN v6A does not support storing a PID.
4
The iCentral is the only S/5 Network device to which the CARESCAPE Gateway directly communicates. See iCentral documentation for
patient monitor and module compatibility.
5ECG is not supported for S/5 Network devices for any of these cases: monitor's DRI level set to 2002 or earlier, M-NE12STPR..00/01
module is used, and M-NESTPR module is used with a monitor that has software level older that 04.

Compatibility

D Technical
specifications
2052436-002B CARESCAPE™ Gateway D-1

Technical specifications
CARESCAPE Gateway
Medical device compliance specifications
The CARESCAPE Gateway is compliant with the applicable requirements of the
following:
 EN60601-1-4:1996/A1:1999
 Safety and Effectiveness Requirements of Canada’s Medical Device Regulations
(SOR/98-282)
 ISO 14971:2007 Medical Devices - Application of Risk Management to Medical
Devices.
 Annex 1 of the Medical Device Directive 93/42/EEC
Hardware compliance specifications

NOTE
Also refer to the HP documentation for OEM compliance information.
The CARESCAPE Gateway is compliant with the applicable requirements of the

following:
 CNS13438 and CNS14336

 CSA C22.2 No. 60950-1-03 (Canada)
 IEC 60320-1:2007 (the equipment socket/appliance coupler)
 EN 55022:2006/CISPR 22:2005
 EN 55024:1998 +A1:2001 +A2:2003
 EN 60950-1:2006 + A11:2009/ IEC 60950-1:2005
 EN 61000-3-2:2006
 EN 61000-3-3:1995 + A1:2001 + A2:2005
 FCC 47 CFR, Part 15, Subpart B: Class A, Title 47 of the Code of Federal
Regulations, Parts 2 and 15, Subpart B, pertaining to unintentional radiators.
 GB9254:1998
 GB4943-2001
 GB17625.1-2003
 ICES-003 (Class A) Canada
 CE marked to the Low Voltage Directive 2006/95/EC and the EMC Directive
2004/108/EC
 UL 60950-1:2007
 China RoHS Labeling Standard (SJ/T11364-2006)
 RoHS directive 2002/95/EC
D-2 CARESCAPE™ Gateway 2052436-002B

General
Processor Quad core Intel Xeon Processor 2.4 GHZ
Memory 3 x 2GB DDR3 1333 MHz PC3-10600
Storage 2 x 72 GB hot-swap 2.5-inch SAS Dual Port 15K
Software Updates Via Network, CD-ROM drive
Network Six RJ-45
Lights Out Management One RJ-45
Video Output Two ports: one front and one rear
Additional Ports Four USB: one front, two rear and one internal for
security
Max. Number of Beds Supported 512
Environmental specifications
Power Requirements Input Voltage Range (Vrms): 100 to 240 VAC, 200 to
240 VAC
Frequency Range (Nominal): 50/60 Hz
Maximum Rated Volt Amps (VA): 548 at 100 Vrms
Power Consumption 526 Watts at 100 V
Cooling Forced air
Operating Temperature 10 °C to +35 °C (50 °F to 95 °F)
Storage Temperature –40 °C to 70 °C (–40 °F to 158 °F)
(non-operating)
Relative Humidity (operating) 10 to 90% (non-condensing)
Storage Relative Humidity 5 to 95% (non-condensing)
(non-operating)
Altitude (operating) 0 to 3048m (0 to 10,000 ft)
Storage Altitude 0 to 9144m (0 to 30,000 ft).
(non-operating)
Physical specifications
Height 4.32 cm (1.70 in)
Depth 69.53 cm (27.38 in)
2052436-002B CARESCAPE™ Gateway D-3

Width 42.62 cm (16.78 in)
Weight 14.51 kg (32.00 lbs.) minimum
15.97 kg (35.20 lbs.) maximum
Hardware
HP Proliant Server Features
 Dual Hot Plug SAS hard disk drives

 Dual hot plug power supply (optional redundant power supply)
 CD-R / DVD ROM disk drive
 Integrated video controller
 1280 x 1024 x 32 M colors
 6 GB RAM expandable to 48 GB
Default IP address settings

The following settings are configured during manufacturing. The IP addresses are
used for system failure recovery.
CARESCAPE CARESCAPE
S/5 Network
Network IX Network MC
IP Address 172.18.1.1 172.16.1.1 172.20.1.1
Netmask 255 . 255 . 0 . 0 255 . 255 . 0 . 0 255 . 255 . 0 . 0
Default Router 172.18.254.254 N/A N/A
D-4 CARESCAPE™ Gateway 2052436-002B

E Supported parameters
2052436-002B CARESCAPE™ Gateway E-1

Supported parameters
NOTE
Some parameters in this table are only available from certain versions and
configurations of the acquisition source.
NOTE
This list is subject to change without notice.
Acquisition source Feature
CARESCAPE B850 and B650 patient

monitors on CARESCAPE Network
Solar 8000i/m patient monitor
High Speed Data Interface

HL7 Vitals on Demand
Dash patient monitor
connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Parameter name Sub-parameter name Units of measure
Depth of consciousness Bispectral Index BIS Yes Yes Yes Yes Yes Yes Yes Yes —
and sedation (BIS) Signal Quality Index SQI Yes Yes Yes Yes Yes Yes Yes %
Amplitude (Total AMP Yes Yes Yes Yes Yes dB
power)
Electromyograph EMG Yes Yes Yes Yes Yes Yes Yes Yes dB
Spectral Edge SEF Yes Yes Yes Yes Yes hz
Frequency
Suppression Ratio SR Yes Yes Yes Yes Yes Yes Yes Yes %
E-2 CARESCAPE™ Gateway 2052436-002B



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Invasive Blood Pressure Pulmonary Artery PA#-S Yes Yes Yes Yes Yes Yes Yes mm (hg)
(BP) Pressure Systolic
Pulmonary Artery PA#-D Yes Yes Yes Yes Yes Yes Yes mm (hg)
NOTE
Pressure Diastolic
The # in each sub-
Pulmonary Artery PA#-M Yes Yes Yes Yes Yes Yes Yes mm (hg)
parameter’s name
Pressure Mean
is actually the
parameter’s slot Pulmonary Artery PAW Yes Yes Yes Yes* Yes* Yes Yes mm (hg)
number. Valid Wedge
values are “1” Special Pressure SP#-S Yes’ Yes Yes Yes Yes mm (hg)
through “8”. Systolic
Special Pressure SP#-D Yes’ Yes Yes Yes Yes mm (hg)
The ‘ indicates that
Diastolic
real-time data is
supported for the Special Pressure SP# Yes Yes Yes Yes Yes Yes Yes mm (hg)
devices but trends Mean
are not. Special Pressure SP#-R Yes Yes Yes Yes beat/min
Pulse Rate
The * in each
Central Venous CVP#-S Yes’ Yes Yes Yes Yes mm (hg)
subparameter’s
Pressure Systolic
name indicates
that certain Central Venous CVP#-D Yes’ Yes Yes Yes Yes mm (hg)
versions of the Pressure Diastolic
CARESCAPE Central Venous CVP# Yes Yes Yes Yes Yes Yes Yes mm (hg)
B850 patient Pressure Mean
monitor and
Intercranial Pressure ICP#-S Yes Yes Yes Yes mm (hg)
CARESCAPE
Systolic
B650 patient
monitor software, Intercranial Pressure ICP#-D Yes Yes Yes Yes mm(hg)
when connected Diastolic
through an Intracranial Pressure ICP# Yes Yes Yes Yes Yes Yes Yes mm (hg)
iCentral, do not Mean
store pulmonary Cerebral Perfusion CPP# Yes Yes Yes Yes Yes Yes Yes mm (hg)
artery values when
Pressure
the PA Wedge
dialog is displayed. Arterial Pressure AR#-S Yes Yes Yes Yes Yes Yes Yes mm (hg)
Systolic
Arterial Pressure AR#-D Yes Yes Yes Yes Yes Yes Yes mm (hg)
Diastolic
Arterial Pressure AR#-M Yes Yes Yes Yes Yes Yes Yes mm (hg)
Mean
Arterial Pressure AR#-R Yes Yes Yes Yes Yes Yes Yes /min
Pulse Rate



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Invasive Blood Pressure Arterial Blood ABP#-S Yes Yes Yes Yes mm (hg)
(BP) Pressure Systolic
Arterial Blood ABP#-D Yes Yes Yes Yes mm (hg)
NOTE
Pressure Diastolic
The # in each sub-
Arterial Blood ABP#-M Yes Yes Yes Yes mm (hg)
parameter’s name
Pressure Mean
is actually the
parameter’s slot Arterial Blood ABP#-R Yes Yes Yes Yes beat/min
number. Valid Pressure Pulse Rate
values are “1” Femoral Arterial FE#-S Yes Yes Yes Yes Yes Yes Yes mm (hg)
through “8”. Catheter Pressure
Systolic
The ‘ indicates that
Femoral Arterial FE#-D Yes Yes Yes Yes Yes Yes Yes mm (hg)
real-time data is
Catheter Pressure
supported for the
Diastolic
devices but trends
are not. Femoral Arterial FE#-M Yes Yes Yes Yes Yes Yes Yes mm (hg)
Catheter Pressure
The * in each Mean
subparameter’s Femoral Arterial FE#-R Yes Yes Yes Yes Yes Yes Yes /min
name indicates Catheter Pressure
that certain Rate
versions of the
Femoral Vein Blood FEMV#-S Yes Yes Yes Yes mm (hg)
CARESCAPE
B850 patient Pressure Systolic
monitor and Femoral Vein Blood FEMV#-D Yes Yes Yes Yes mm (hg)
CARESCAPE Pressure Diastolic
B650 patient Femoral Vein Blood FEMV#-M Yes Yes Yes Yes mm (hg)
monitor software, Pressure Mean
when connected
Femoral Vein Blood FEMV#-R Yes Yes Yes Yes beat/min
through an
Pressure Pulse Rate
iCentral, do not
store pulmonary Right Atrial Catheter RAP#-S Yes’ Yes Yes Yes Yes mm (hg)
artery values when Pressure Systolic
the PA Wedge Right Atrial Catheter RAP#-D Yes’ Yes Yes Yes Yes mm (hg)
dialog is displayed. Pressure Diastolic
Right Atrial Catheter RA# Yes Yes Yes Yes Yes Yes Yes mm (hg)
Pressure Mean
Right Ventricular RVP#-S Yes Yes Yes Yes mm (hg)
Catheter Pressure
Systolic
Right Ventricular RVP#-D Yes Yes Yes Yes mm (hg)
Catheter Pressure
Diastolic



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Invasive Blood Pressure Right Ventricular RVP#-M Yes Yes Yes Yes mm (hg)
(BP) Catheter Pressure
Mean
NOTE
Left Atrial Pressure LAP#-S Yes’ Yes Yes Yes Yes mm (hg)
The # in each sub- Systolic
parameter’s name
Left Atrial Pressure LAP#-D Yes’ Yes Yes Yes Yes mm (hg)
is actually the Diastolic
parameter’s slot
number. Valid Left Atrial Pressure LA# Yes Yes Yes Yes Yes Yes Yes mm (hg)
values are “1” Mean
through “8”. Umbilical Arterial UA#-S Yes Yes Yes Yes Yes Yes Yes mm (hg)
Catheter Pressure
The ‘ indicates that Systolic
real-time data is
Umbilical Arterial UA#-D Yes Yes Yes Yes Yes Yes Yes mm (hg)
supported for the
Catheter Pressure
devices but trends
Diastolic
are not.
Umbilical Arterial UA#-M Yes Yes Yes Yes Yes Yes Yes mm (hg)
The * in each Catheter Pressure
subparameter’s Mean
name indicates Umbilical Arterial UA#-R Yes Yes Yes Yes Yes Yes Yes /min
that certain Catheter Pressure
versions of the Pulse Rate
CARESCAPE
B850 patient Umbilical Venous UV#-S Yes Yes Yes Yes mm (hg)
Catheter Pressure
monitor and
Systolic
CARESCAPE
B650 patient Umbilical Venous UV#-D Yes Yes Yes Yes mm (hg)
monitor software, Catheter Pressure
when connected Diastolic
through an Umbilical Venous UV# Yes Yes Yes Yes Yes Yes Yes mm (hg)
iCentral, do not Catheter Pressure
store pulmonary Mean
artery values when
Unknown Site Blood P#-S Yes Yes Yes Yes mm (hg)
the PA Wedge
Pressure Systolic
dialog is displayed.
Unknown Site Blood P#-D Yes Yes Yes Yes mm (hg)
Pressure Diastolic
Unknown Site Blood P#-M Yes Yes Yes Yes mm (hg)
Pressure Mean



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Cardiac Calculation Heart Rate HR Yes Yes Yes Yes /min

(Cardiac Calcs)/Hemo Cardiac Output CO Yes Yes Yes Yes l/min
Calcs
Mean Arterial MAP Yes Yes Yes Yes mm (hg)
Pressure
Central Venous CVP Yes Yes Yes Yes mm (hg)
Pressure
Pulmonary Artery PAM Yes Yes Yes Yes mm (hg)
Mean
Pulmonary Artery PAW Yes Yes Yes Yes mm (hg)
Wedge
Body Surface Area BSA Yes Yes Yes Yes m2
Cardiac Index CI Yes Yes Yes Yes l/(min/m2)
Stroke Volume SV Yes Yes Yes Yes ml/beat
Systemic Vascular SVR Yes Yes Yes Yes dyn.sec.cm -5
Resistance
Systemic Vascular SVRI Yes Yes Yes Yes dyn.sec.cm -5.m2
Resistance Index
Pulmonary Vascular PVR Yes Yes Yes Yes dyn.sec.cm -5
Resistance
Pulmonary Vascular PVRI Yes Yes Yes Yes dyn.sec.cm -5.m2
Resistance Index
Left Ventricular LVSWI Yes Yes Yes Yes g.m/m2
Stroke Work Index
Right Ventricular RVSWI Yes Yes Yes Yes g.m/m2
Stroke Work Index
Pulmonary Artery PAD Yes Yes Yes mm (hg)
Diastolic
Left Atrial Pressure LA Yes Yes Yes mm (hg)
Mean
Cardiac Output (CO) Blood Temperature BT Yes Yes Yes Yes Yes Yes Yes cel
Cardiac Output CO Yes Yes Yes Yes Yes Yes l/min
Injectate TP_INJ Yes Yes Yes Yes cel
Temperature
Right Ventricular VEF_REF Yes Yes Yes Yes %
Ejection Fraction
Reference TP_REF Yes Yes Yes Yes Yes cel
Temperature



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
CO2 / O2 (CO2) Expired CO2 CO2-EX Yes Yes Yes Yes Yes Yes Yes mm (hg)
CO2-EX Yes Yes Yes Yes %
Inspired CO2 CO2-IN Yes Yes Yes Yes Yes Yes Yes mm (hg)
CO2-IN Yes Yes Yes Yes %
Expired O2 O2-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired O2 O2-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Barometric Pressure AMB_P Yes Yes Yes Yes Yes mm (hg)
Continuous Cardiac Blood Temperature cBT Yes Yes Yes Yes Yes Yes Yes cel
Output (CCO) Cardiac Index cCI Yes Yes Yes Yes l/(min/m2)
Cardiac Output cCO Yes Yes Yes Yes l/min
Continuous Cardiac cCCO Yes Yes Yes Yes Yes Yes l/min
Output
Continuous Cardiac cCCI Yes Yes Yes Yes Yes l/(min/m2)
Index
Stroke Volume SVV Yes Yes Yes %
Variation
Systemic Vascular cSVR Yes Yes Yes Yes Yes dyn.sec.cm -5
Resistance
Systemic Vascular cSVRI Yes Yes Yes Yes Yes dyn.sec.cm -5.m2
Resistance Index
ECG Heart Rate HR Yes Yes Yes Yes Yes Yes Yes /min
R-to-R Interval R2R_TM Yes Yes Yes Yes ms
Premature PVC Yes Yes Yes Yes Yes Yes Yes #/min
Ventricular Count



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
ECG/ST (ST) ST Segment I ST-I Yes Yes Yes Yes Yes Yes Yes mm
ST Segment II ST-II Yes Yes Yes Yes Yes Yes Yes mm
ST Segment III ST-III Yes Yes Yes Yes Yes Yes Yes mm
ST Segment V (from ST-V Yes Yes mm
CDT-LAN)
ST Segment V1 ST-V1 Yes Yes Yes Yes Yes Yes Yes mm
ST Segment V2 ST-dV2 Yes Yes Yes Yes mm
(derived)
(derived)
(derived)
(derived)
ST Segment AVR ST-AVR Yes Yes Yes Yes Yes Yes Yes mm
ST Segment AVL ST-AVL Yes Yes Yes Yes Yes Yes Yes mm
ST Segment AVF ST-AVF Yes Yes Yes Yes Yes Yes Yes mm



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Electroencephalogram Spectral Edge eSEF# Yes Yes* Yes* Yes Yes* Yes* hz
(EEG) Frequency
Median Frequency eMedF# Yes Yes* Yes* Yes Yes* Yes* hz
NOTE
Suppression Ratio eSR# Yes Yes* Yes* Yes Yes* Yes* %
The # in each sub-
parameter’s name Amplitude eAMP# Yes* Yes* Yes Yes* Yes* dB
is actually the Electromyography eEMG# Yes Yes* Yes Yes* Yes* dB
parameter’s % Power in Delta eDELTA# Yes Yes* Yes* Yes Yes* Yes* %
channel number. Freq Range (.5-
Valid values are 1 3.75hz)
through 4, 12, 34.
% Power in Theta eTHETA# Yes Yes* Yes* Yes Yes* Yes* %
NOTE Freq Range (4.0-
7.75hz)
Yes*: Supported
for channels 1 % Power in Alpha eALPHA# Yes Yes* Yes* Yes Yes* Yes* %
through 4, but not Freq Range (8.0-
12 and 34. 13.75hz)
% Power in Beta eBETA# Yes Yes* Yes* Yes Yes* Yes* %
Freq Range (14.0-
39.0hz)
Signal Quality Index eSQI# Yes Yes* Yes Yes* Yes* %
Entropy Suppression Ratio ENT_BSR Yes Yes Yes Yes %
Response Entropy ENT_RE Yes Yes Yes Yes —
State Entropy ENT_SE Yes Yes Yes Yes —
Estimated Pulmonary Estimated Arterial O2 eCaO2 Yes Yes Yes Yes ml/100 ml
Calculations (est.PC) Content
Estimated O2 eDO2I Yes Yes Yes Yes ml/(min/m2)
Delivery Index
Estimated Mixed eCvO2 Yes Yes Yes Yes ml/100 ml
Venous O2 Content
Estimated Arterial- ea-vO2 Yes Yes Yes Yes ml/100 ml
Venous O2 Content
Difference
Estimated O2 eVO2I Yes Yes Yes Yes ml/(min/m2)
Consumption
Estimated O2 eO2ER Yes Yes Yes Yes %
Extraction Ratio
Estimated Shunt eQs/Qt Yes Yes Yes %
Fraction



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Impedance Heart Rate iHR Yes Yes Yes Yes Yes /min
Cardiography (ICG) Mean Arterial iMAP Yes Yes Yes Yes Yes mm (hg)
Pressure
*This unit of measure is
different from Aware Cardiac Output iCO Yes Yes Yes Yes Yes l/min
Gateway. Cardiac Index iCI Yes Yes Yes Yes Yes l/(min/m2)
Stroke Volume iSV Yes Yes Yes Yes Yes ml
Stroke Index iSI Yes Yes Yes Yes Yes ml/m2
Systemic Vascular iSVR Yes Yes Yes Yes Yes dyn.sec.cm -5
Resistance
Systemic Vascular iSVRI Yes Yes Yes Yes Yes dyn.sec.cm -5 m2
Resistance Index
Thoracic Fluid iTFC Yes Yes Yes Yes Yes l/kohm
Content
Acceleration Index iACI Yes Yes Yes Yes Yes /(100.s2) *
Velocity Index iVI Yes Yes Yes Yes Yes /(1000.s) *
Left Ventricular iLVSWI Yes Yes Yes Yes Yes g.m/m2
Stroke Work Index
Left Cardiac Work iLCWI Yes Yes Yes Yes Yes kg m/m2
Index
Systolic Time Ratio iSTR Yes Yes Yes Yes Yes —
Pre-Ejection Period iPEP Yes Yes Yes Yes Yes ms
Left Ventricular iLVET Yes Yes Yes Yes Yes ms
Ejection Time
Estimated O2 ieDO2I Yes Yes Yes Yes Yes ml/(min/m2)
Delivery Index
Infusion Pump Total Volume IV#-TV Yes Yes Yes ml
Primary Rate IV#-PR Yes Yes Yes ml/h
NOTE
Secondary Rate IV#-SR Yes Yes Yes ml/h
The # in each sub-
parameter’s name
is actually the
parameter’s
infuser number.
Valid values are
one through eight.



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Mass Spectrometer Expired N2 N2-EX Yes Yes Yes Yes Yes Yes %
(GAS) Inspired N2 N2-IN Yes Yes Yes Yes Yes Yes %
Expired N2O N2O-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired N2O N2O-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired Halothane HAL-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired Halothane HAL-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired Isoflurane ISO-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired Isoflurane ISO-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired Enflurane ENF-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired Enflurane ENF-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired Desflurane DES-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired Desflurane DES-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired Sevoflurane SEV-EX Yes Yes Yes Yes Yes Yes Yes Yes %
Inspired Sevoflurane SEV-IN Yes Yes Yes Yes Yes Yes Yes Yes %
Expired - Unknown UNKNOWN Yes Yes Yes Yes %
-EX
Inspired - Unknown UNKNOWN Yes Yes Yes Yes %
-IN
Expired - None NONE-EX Yes Yes Yes Yes %
Inspired - None NONE-IN Yes Yes Yes Yes %
Minimum Alveolar MAC Yes Yes Yes Yes Yes Yes —
Concentration
MAC Sum MAC_SUM Yes Yes Yes Yes —
MAC Sum Age- MAC_AGE_ Yes Yes Yes Yes —
Corrected SUM
Metabolic GE_VO2 Yes Yes Yes Yes ml/min
Consumption of O2
Metabolic Production GE_VCO2 Yes Yes Yes Yes ml/min
of CO2
Energy expended as GE_EE Yes Yes Yes Yes kcal/d
a result of respiration
Respiratory Quotient GE_RQ Yes Yes Yes Yes —
Inspired Balance Gas — Yes Yes %
Expired Balance Gas — Yes Yes %
Fractional Inspired FiO2 Yes Yes Yes Yes Yes Yes Yes %
Oxygen



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Gas Delivery Gas Consumption DES-DLV Yes Yes Yes Yes ml

Desflurane
Gas Consumption ENF-DLV Yes Yes Yes Yes ml
Enflurane
Gas Consumption ISO-DLV Yes Yes Yes Yes ml
Isoflurane
Gas Consumption HAL-DLV Yes Yes Yes Yes ml
Halothane
Gas Consumption SEV-DLV Yes Yes Yes Yes ml
Sevoflurane
Gas Consumption O2 O2-DLV Yes Yes Yes Yes L
Gas Consumption N2O-DLV Yes Yes Yes Yes L
N20
Gas Consumption Air AIR-DLV Yes Yes Yes Yes L
Inspired Oxygen O2set Yes Yes Yes Yes %
Setting
Flow Rate FLW-RT Yes Yes Yes Yes l/min
Arterial Oxygen Arterial Blood SAO2 Yes Yes Yes Yes %
Saturation (SAO2) Oxygen Saturation
Venous Oxygen Venous Blood SvO2 Yes Yes Yes Yes Yes Yes Yes %
Saturation (SVO2) Oxygen Saturation
Non-Invasive Blood Noninvasive BP NBP-S Yes Yes Yes Yes Yes Yes Yes mm (hg)
Pressure (NBP) Systolic
Noninvasive BP NBP-D Yes Yes Yes Yes Yes Yes Yes mm (hg)
Diastolic
Noninvasive BP NBP-M Yes Yes Yes Yes Yes Yes Yes mm (hg)
Mean
Noninvasive BP Cuff — Yes Yes Yes Yes Yes mm (hg)
Pressure
Noninvasive BP Rate NBP-R Yes Yes Yes /min
Non-Invasive Cardiac Cardiac Output nCO Yes Yes Yes Yes l/min
Output (NICO) Pulmonary Capillary nPCBF Yes Yes Yes Yes l/min
Blood Flow
Cardiac Index nCI Yes Yes Yes Yes l/(min/m2)
Stroke Volume nSV Yes Yes Yes Yes ml
Confidence Bar nSQ Yes Yes Yes —
(Signal Quality)



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Point of Care (POC)/ pH pH Yes Yes Yes —

Arterial Blood Gas Partial Pressure pCO2 Yes Yes Yes mm (hg), kPa*
(ABG) Carbon Dioxide
*This unit of measure is Partial Pressure pO2 Yes Yes Yes mm (hg), kPa*
different from Aware Oxygen
Gateway Bicarbonate HCO3 Yes Yes Yes mM
Temperature Temp Yes Yes Yes cel
Base Excess of BEb Yes Yes Yes mM
Blood
Total CO2 TCO2 Yes Yes Yes mM
Base Excess of BEecf Yes Yes mM
Extracellular Fluid
Oxygen Saturation O2sat Yes Yes Yes %
Hematocrit Hct Yes Yes Yes %
Total Hemoglobin tHB(C) Yes Yes Yes g/dL*
Ionized Calcium iCa Yes Yes Yes mM, mEq/l*, mg/
dL*
Potassium K+ Yes Yes Yes mM, mEq/l*
Blood Urea Nitrogen BUN Yes Yes Yes mM*, mg/dL
Sodium Na+ Yes Yes Yes mM, mEq/l*
Chloride Cl- Yes Yes Yes mM*, mEq/l
Glucose Strip Gluc Yes Yes Yes mM*, mg/dL



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Pulmonary Calculation Cardiac Output CO Yes Yes Yes Yes l/min

(PC) / Oxy Calcs (Thermodilution
method)
Body Surface Area BSA Yes Yes Yes Yes m2
Fractional Inspired FiO2 Yes Yes Yes Yes %
Oxygen
Positive End PEEP Yes Yes Yes cm_h2o
Expiratory Pressure
Respiration Rate RR Yes Yes Yes breaths/min
Tidal Volume TV Yes Yes Yes ml
End Inspiratory PIP Yes Yes Yes cm_h2o
Pressure
Barometric Pressure PBAR Yes Yes Yes Yes mm (hg)
Hemoglobin Hb Yes Yes Yes Yes gm/100 ml
Arterial CO2 PaCO2 Yes Yes Yes Yes mm (hg)
Pressure
Arterial Oxygen PaO2 Yes Yes Yes Yes mm (hg)
Pressure
Arterial Oxygen SaO2 Yes Yes Yes Yes %
Saturation
Mixed Venous PvO2 Yes Yes Yes Yes mm (hg)
Oxygen Pressure
Mixed Venous SvO2 Yes Yes Yes Yes %
Oxygen Saturation
Dynamic Compliance Cdyn Yes Yes Yes ml/cm_h20
Minute Volume MV Yes Yes Yes l/min
Alveolar-Arterial O2 AaDO2 Yes Yes Yes Yes mm (hg)
Gradient
Arterial O2 Content CaO2 Yes Yes Yes Yes ml/100 ml
O2 Delivery Index DO2I Yes Yes Yes Yes ml/(min/m2)
Mixed Venous O2 CvO2 Yes Yes Yes Yes ml/100 ml
Content
Arterial-Venous O2 a-vO2 Yes Yes Yes Yes ml/100 ml
Content Difference
O2 Consumption VO2I Yes Yes Yes Yes ml/(min/m2)
Index
O2 Extraction Ratio O2ER Yes Yes Yes Yes %
Oxygenation Ratio PaFiO2 Yes Yes Yes %



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Pulmonary Calculation Shunt Fraction Qs/Qt Yes Yes Yes Yes %

(PC) / Oxy Calcs Fick Cardiac Output FICK CO Yes Yes Yes Yes l/min
Pulse Oximetry (SPO2) Oxygen Saturation SPO2-% Yes Yes Yes Yes Yes Yes Yes %
Pulse Oximetry SPO2-R Yes Yes Yes Yes Yes Yes Yes /min
Peripheral Pulse
Rate
Oxygen Saturation SPO2-AMP Yes Yes Yes Yes %
Amplitude (Percent
Modulation)
Oxygen Saturation SPO2M Yes Yes Yes Yes Yes Yes %
(Module)
Pulse Oximetry SPO2-R Yes Yes Yes Yes Yes Yes /min
Peripheral Pulse
Rate (module)
Oxygen Saturation SPO2-%1 Yes Yes Yes Yes %
(Interface #1)
Pulse Oximetry SPO2-R1 Yes Yes Yes Yes /min
Peripheral Pulse
Rate (Interface #1)
Oxygen Saturation SPO2-%2 Yes Yes Yes Yes %
(Interface #2)
Pulse Oximetry SPO2-R2 Yes Yes Yes Yes /min
Peripheral Pulse
Rate (Interface #2)
Impedance Respiration Respiration Rate RR Yes Yes Yes Yes Yes Yes Yes breaths/min
(RR)



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Respiration (Vent/RM/ Peak Expiratory Flow rPEF Yes Yes Yes Yes Yes l/min
Resp) Ambient Pressure AMB_P Yes Yes Yes Yes mm (hg)
Minute Volume MV Yes Yes Yes Yes l/min
Minute Volume (Exp rMV Yes Yes Yes Yes Yes Yes l/min
Total) MVe Yes Yes Yes Yes l/min
Minute Volume SPO-MV Yes Yes Yes Yes Yes l/min
(Spontaneous)
Minute Volume (Exp rMVs Yes Yes Yes Yes Yes Yes Yes l/min
Spontaneous)
Minute Volume (Exp rMVm Yes Yes Yes Yes Yes l/min
Mechanical)
Minute Volume MVi Yes Yes Yes Yes ml/min
(Inspired)
Tidal Volume TV Yes Yes Yes Yes ml
(Expired)
Tidal Volume Total rTV Yes Yes Yes Yes Yes Yes Yes ml
(Exp Avg Total)
Tidal Volume (Exp rTVs Yes Yes Yes Yes Yes ml
Avg Spontaneous)
Tidal Volume (Exp rTVm Yes Yes Yes Yes Yes ml
Avg Mechanical)
Tidal Volume TV_INSP Yes Yes Yes Yes ml
(Inspired) TV-in Yes Yes Yes Yes ml
Mean Airway MAWP Yes Yes Yes Yes cm_h2o
Pressure rMAWP Yes Yes Yes Yes Yes Yes cm_h2o
Plateau Pressure PPLAT Yes Yes Yes Yes cm_h2o
Static Plateau S_PPLAT Yes Yes Yes Yes cm_h2o
Pressure
Dynamic Plateau D_PPLAT Yes Yes Yes Yes cm_h2o
Pressure
Peak Inspired PIP Yes Yes Yes Yes cm_h2o
Pressure rPIP Yes Yes Yes Yes Yes Yes cm_h2o
Positive End rPEEP Yes Yes Yes Yes Yes Yes cm_h2o
Expiratory Pressure PEEP Yes Yes Yes Yes cm_h2o
Intrinsic Positive End rPEEPi Yes Yes Yes Yes Yes Yes Yes cm_h2o
Expiratory Pressure
Measured PEEP M-PEEP Yes Yes Yes Yes cm_h2o
Intrinsic PEEP I-PEEP Yes Yes Yes Yes cm_h2o



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Respiration (Vent/RM/ Extrinsic PEEP EPEEP Yes Yes Yes Yes cm_h2o
Resp) Static Total PEEP S_PEEPE Yes Yes Yes Yes cm_h2o
Static Intrinsic PEEP S_IPEEP Yes Yes Yes Yes cm_h2o
Static Extrinsic PEEP S_EPEEP Yes Yes Yes Yes cm_h2o
Total PEEP T-PEEP Yes Yes Yes Yes Yes cm_h2o
Auto PEEP Trends: A- Yes Yes Yes Yes cm_h2o
PEEP
VOD: I-
PEEP
Respiration Rate - CO2-RR Yes Yes Yes Yes Yes Yes Yes Yes breaths/min
CO2
Respiratory Rate rRR Yes Yes Yes Yes Yes Yes breaths/min
(total)
Respiratory Rate rRRs Yes Yes Yes Yes Yes breaths/min
(Spontaneous) SPO-RR Yes Yes Yes Yes breaths/min
Respiratory Rate rRRm Yes Yes Yes Yes Yes breaths/min
(Mechanical)
Respiration Rate PT-RR Yes Yes Yes Yes breaths/min
I:E ratio denominator I:E Yes Yes Yes Yes Yes 1:
rI:E Yes Yes Yes Yes Yes Yes 1:
Expiratory Time EXP_TIME Yes Yes Yes Yes ms
Inspiratory Time INSP_TIME Yes Yes Yes Yes Yes ms
Inspiratory Time M_INSP_TI Yes Yes Yes Yes s
(Measured) ME
Work of Breathing rWOBm Yes Yes Yes Yes Yes J/l
(Ventilator)
Compliance COMP Yes Yes Yes Yes ml/cm_h2o
Compliance rCDYN Yes Yes Yes Yes Yes Yes Yes ml/cm_h2o
(Dynamic) D-COMP Yes Yes Yes Yes ml/cm_h2o
Compliance (Static) S_COMPL Yes Yes Yes Yes ml/cm_h2o
S_COMP Yes Yes Yes Yes ml/cm_h2o
Resistance RES Yes Yes Yes Yes cm_h2o/(l/sec)
Resistance RAW Yes Yes Yes Yes cm_h2o/(l/sec)
(Dynamic) D-RES Yes Yes Yes Yes cm_h2o/(l/sec)
Resistance (Static) S-RES Yes Yes Yes Yes cm_h2o/(l/sec)
Resistance (airway) rRAWe Yes Yes Yes Yes Yes Yes cm_h2o/(l/sec)
(expiratory)
Sensitivity SENS Yes Yes Yes Yes cm_h2o



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Respiration (Vent/RM/ Ventilator Rate VNT-RR Yes Yes Yes Yes breaths/min
Resp) Inspiration Hold Time IN-HLD Yes Yes Yes Yes seconds
Positive Pressure PPS Yes Yes Yes Yes cm_h2o
Support
Inspiratory Time INSP Yes Yes Yes Yes seconds
Inspiratory Percent INSP Yes Yes Yes Yes %
High Frequency HF-FLW Yes Yes Yes Yes l/min
Ventilation Flow
Setting
High Frequency HF-RR Yes Yes Yes Yes hz
Ventilation
Respiratory Rate
High Frequency HF-PRS Yes Yes Yes Yes cm_h2o
Ventilation Peak-to-
Peak Pressure
Set Tidal Volume TVset Yes Yes Yes Yes ml
Set PCP PCP Yes Yes Yes Yes cm_h2o
Set I:E I:Eset Yes Yes Yes Yes 1:
Base Flow BS-FLW Yes Yes Yes Yes l/min
Flow Trigger FL-TRG Yes Yes Yes Yes l/min
Ramp (Rise Time) RAMP Yes Yes Yes Yes seconds
APRV Low Pressure Bi-PLo Yes Yes Yes Yes cm_h2o
Setting
APRV High Pressure Bi-PHi Yes Yes Yes Yes cm_h2o
Setting
APRV Time Duration Bi-TLo Yes Yes Yes Yes seconds
at Low Pressure
APRV Time Duration Bi-THi Yes Yes Yes Yes seconds
at High Pressure
Flow Trigger X10 TRIG_X10 Yes Yes Yes Yes l/min



connectivity device
Unity Network ID
HL7 outbound
S/5 monitors
Temperature (TP) Temperature1 TP*-1 Yes Yes Yes Yes Yes Yes Yes cel
Temperature2 TP*-2 Yes Yes Yes Yes Yes Yes Yes cel
NOTE
Airway Temperature TP_AWAY# Yes Yes Yes Yes cel
The # in each sub-
parameter’s name Auxiliary TP_AXIL# Yes’ Yes’ Yes Yes Yes Yes cel
is the parameter’s Temperature
channel number. Bladder Temperature TP_FOLEY Yes’ Yes’ Yes Yes Yes Yes cel
Valid values are “1” #
and “2” for Core Temperature TP_CORE# Yes Yes Yes Yes cel
CARESCAPE
Esophageal TP_ESO# Yes Yes Yes Yes Yes Yes Yes cel
Network devices
and “1” through “4” Temperature
for S/5 Network Myocardial TP_MYO# Yes Yes Yes Yes cel
devices. Temperature
Nasal Temperature TP_NASAL Yes Yes Yes Yes Yes cel
NOTE #
The * in each sub- Nasopharynx TP_NASOP Yes Yes Yes Yes cel
parameter’s name Temperature H#
is the parameter
Rectal Temperature TP_RECT# Yes’ Yes’ Yes Yes Yes Yes Yes cel
sbt number. Valid
values are “1”, “6” Room Temperature TP_ROOM# Yes Yes Yes Yes cel
and “8”. Skin Temperature TP_SKIN# Yes’ Yes’ Yes Yes Yes Yes Yes cel
The ‘ indicates that Surface Temperature TP_BODY# Yes Yes Yes Yes cel
real-time data is Tympanic TP_TYMP# Yes Yes Yes Yes cel
supported for the Temperature
devices but trends
are not.
Transcutaneous pO2/ Transcutaneous TC O2 Yes Yes Yes Yes Yes Yes mm(hg)
pCO2 Oxygen Pressure
Transcutaneous CO2 TC CO2 Yes Yes Yes Yes Yes Yes mm(hg)
Pressure
Sensor Temperature TC TP Yes Yes Yes Yes Yes Yes cel
Total Heater Power TC mW Yes Yes Yes Yes Yes Yes mw
Site timer — Yes Yes Yes —
Urimeter (UO) Volume UR VOL Yes Yes Yes Yes ml*
Temperature UR TMP Yes Yes Yes Yes cel
*This unit of measure is
different from Aware
Gateway.


F Router supported
services
2052436-002B CARESCAPE™ Gateway F-1

Router supported services

The following information for router support and supported services applies to the
CARESCAPE Gateway v1.
Ping service
Ping service Value
Usage type Device servicing
Functional need Function Network troubleshooting
Licensed/optional/required Optional
Network IX network, MC network or S/5 Network
Communication Device/IP address Any device on any of the networks

partner
Network IX network, MC network, S/5 Network or
hospital enterprise network
Protocols Layer 3/4 ICMP
Application protocol n/a
Ports n/a
Direction (relative to the device) Incoming and outgoing
Reflexive Yes
Transmission characterization On-demand, user initiated
Priority Prioritized
Data characterization —
InSite ExC
InSite ExC Value
Functional need Function GE remote service and device health

status notification
Network IX network
Communication Device/IP address InSite ExC server

partner
https://us1-ws.service.gehealthcare.com
Network Internet or GE VPN
Protocols Layer 3/4 TCP
Application protocol HTTPS
F-2 CARESCAPE™ Gateway 2052436-002B

InSite ExC Value
Ports 443
Direction (relative to the device) Outgoing
Reflexive Yes
Transmission characterization Periodic
Priority None
Data characterization 4 Kbytes/minute (continuous) plus any file

transfers (on-demand)
InSite ExC tunnel
InSite ExC tunnel Value
Functional need Function GE remote service
Network IX network
Communication Device/IP address InSite ExC server

partner
https://us1-rd.service.gehealthcare.com
Network Internet or GE VPN
Ports 443
Reflexive Yes
Priority None
Data characterization Remote webmin session and remote

desktop session (on-demand)
HTTP/HTTPS Proxy
HTTP/HTTPS Proxy Value
Usage type Network services
Functional need Function InSite ExC
Network IX network

HTTP/HTTPS Proxy Value
Communication Device/IP address Web proxy server

partner
Network Hospital enterprise network
Ports Customer defined (e.g., 3128)
Reflexive Yes
Priority None
Webmin service
Webmin service Value
Functional need Function GE remote service or hospital biomed

service
Licensed/optional/required Required
Network IX network
Communication Device/IP address PC

partner
Network IX network, hospital enterprise network, or
GE VPN
Ports 8080
Direction (relative to the device) Incoming
Reflexive Yes
Priority None

VNC for GE service and customer
VNC for GE service and customer Value
Functional need Function GE remote service and hospital biomed

service
Network IX network

partner
GE VPN
Application protocol RFB
Ports 5900
Reflexive Yes
Priority Best effort
HP System Management
HP System Management Value

service
Network IX network

partner
GE VPN
Ports 2381
Reflexive Yes

HP System Management Value
Priority None
DHCP client
DHCP client Value
Functional need Function Network IP address discovery
Network IX network
Communication Device/IP address DHCP server

partner
Protocols Layer 3/4 UDP
Application protocol DHCP
Ports 67
Reflexive Yes
Transmission characterization Sporadic
DNS client
DNS client Value
Functional need Function Names network address discovery
Network IX network
Communication Device/IP address DNS server

partner
Application protocol DNS
Ports 53

DNS client Value
Reflexive Yes
E-mail delivery
E-mail delivery Value
Functional need Function Error or alert notifications for ADT and

HSDI
Network IX network
Communication Device/IP address E-mail server

partner
Application protocol SMTP
Ports 25
Reflexive Yes
Trends
Trends Value
Usage type Clinical
Functional need Function Unsolicited HL7 ORU
Licensed/optional/required Licensed
Network IX network
Communication Device/IP address EMR/HIS

partner
Application protocol HL7/MLLP

Trends Value
Ports 12000 (customer defined)
Reflexive Yes
Data characterization After MC network outage: +550 Kbytes per

bed
After EMR outage: +800 Kbytes per bed
Vitals on-demand
Vitals on-demand Value
Usage type Clinical
Functional need Function Vitals
Network IX network
Communication Device/IP address EMR/HIS

partner
Reflexive Yes
Transmission characterization On-demand
ADT for server
ADT for server Value
Usage type Clinical
Functional need Function Transfer of ADT data
Network IX network

ADT for server Value
Communication Device/IP address ADT server

partner
Reflexive Yes
Data characterization After a 12 hour network outage: +3 Kbytes

per bed
ADT for client
ADT for client Value
Usage type Clinical
Functional need Function Transfer of ADT data
Network IX network
Communication Device/IP address ADT client such as MUSE or backup

partner CARESCAPE Gateway
Network Hospital enterprise network or IX network
Ports Client specified
Reflexive Yes
Data characterization After a 12 hour network outage: +3 Kbytes

per bed

HSDI server
HSDI server Value
Usage type Clinical
Functional need Function Near real-time parameters and waveforms
Network IX network
Communication Device/IP address EMR or custom HSDI client

partner
Application protocol HSI v2
Ports 2007
Reflexive Yes
Data characterization For HSDI waveforms, normal usage is 4

Kbytes/second per bed
HSDI spwaned connections
HSDI spwaned connections Value
Usage type Clinical
Functional need Function Near real-time parameters and waveforms
Network IX network
Communication Device/IP address EMR or custom HSDI client

partner
Application protocol HSI v2
Ports Client specified
Reflexive No

HSDI spwaned connections Value

Kbytes/second per bed
NTP client
NTP client Value
Functional need Function Time synchronization
Network IX network
Communication Device/IP address NTP server

partner
Network Hospital enterprise network or Internet
Application protocol NTP
Ports 123
Reflexive Yes
NTP server
NTP server Value
Functional need Function Time synchronization Symmetric (client-

server) mode
Network IX network, MC network, or S/5 Network
Communication Device/IP address iCentral and other NTP clients

partner
Network IX network, MC network, or S/5 Network
Application protocol NTP
Ports 123

NTP server Value
Reflexive Yes
iCentral connections
iCentral connections Value
Usage type Clinical
Functional need Function Real-time and trend data
Network S/5 network
Communication Device/IP address iCentral

partner
Network S/5 Network
Application protocol S/5 TCP protocol
Ports 5554
Reflexive Yes

Kbytes/second per bed; eight hour back
collect event: +150 Kbytes per bed
Unity services
Unity services Value
Usage type Clinical
Functional need Function Real-time and trend data, time-control,

and cached ADT data lookups
Network MC network
Communication Device/IP address Patient monitor

partner
Network MC network

Unity services Value
Application protocol Unity protocol
Ports Various
Direction (relative to the device) Incoming and outgoing
Reflexive No
Transmission characterization Periodic, on-demand
Priority Prioritized, best effort

Kbytes/second per bed; Eight hour back
collect event: +150 Kbytes per bed
ADT picklist
ADT picklist Value
Usage type Clinical
Functional need Function Cached ADT lookups
Network MC network and IX network
Communication Device/IP address CIC Pro center or patient monitor

partner
Network MC network and IX network
Application protocol Picklist XML
Ports 11111
Reflexive Yes
HP iLO web interface
HP iLO web interface Value

service

HP iLO web interface Value
Network IX network (iLO)

partner
GE VPN
Ports 443
Reflexive Yes
Priority None
HP iLO virtual media and remote desktop
HP iLO virtual media and remote desktop Value

service

partner
GE VPN
Application protocol HP proprietary
Ports 17988, 17990
Reflexive Yes
Priority Best effort, None

HP iLO SNMP
HP iLO SNMP Value
Functional need Function Device health status notification
Communication Device/IP address Same device or (optionally) Network

partner management system
Network IX network or Hospital enterprise network
Application protocol SNMP
Ports 162
Reflexive No
SNMP listener
SNMP listener Value
Functional need Function Device health status notification
Network IX network
Communication Device/IP address Same device

partner
Application protocol SNMP
Ports 162
Reflexive No
Transmission characterization —
Priority —

Telnet client
Telnet client Value
Functional need Function Configure router
Network IX network
Communication Device/IP address Router

partner
Network IX network
Application protocol Raw (term window control)
Ports 23
Reflexive Yes

Asia Headquarters
GE Medical Systems GE Medical Systems GE Medical Systems
Information Technologies, Inc. Information Technologies GmbH Information Technologies Asia; GE (China) Co., Ltd.
8200 West Tower Avenue Munzingerstrasse 5 No1 Huatuo Road,
Milwaukee, WI 53223 USA 79111 Freiburg Zhangjiang Hi-tech Park Pudong
Tel: + 1 414 355 5000 Germany Shanghai, P.R.China 201203
1 800 558 5120 (US only) Tel: + 49 761 45 43 - 0 Tel: + 86 21 5257 4650
Fax: + 1 414 355 3790 Fax: + 49 761 45 43 - 233 Fax: + 86 21 5208 2008
GE Medical Systems Information Technologies, Inc., a General Electric Company, going to market as
GE Healthcare.
www.gehealthcare.com

GE Carescape Gateway

Uploaded by

Copyright:

Available Formats

GE Carescape Gateway

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GE Carescape Gateway

Uploaded by

Copyright:

Available Formats

GE Healthcare

CIC PRO is a trademark of GE Medical Systems Information Technologies, Inc.

CARESCAPE is a trademark of GE Healthcare.

T-2 CARESCAPE™ Gateway 2052436-002B

Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Equipment information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

2 Equipment overview . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Theory of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

CARESCAPE Gateway function description. . . . . . . . . . . . . . . . . . . . . . . . . 2-7

2052436-002B CARESCAPE™ Gateway i

Service utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Pre-installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

CARESCAPE Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Initial backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Cloverleaf thread startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

ii CARESCAPE™ Gateway 2052436-002B

Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Checkout procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Maintenance checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

System availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

General fault isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

LED status indicator description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Unit does not boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Cables and connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Network interface test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Troubleshooting network problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Cannot connect to Webmin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Service tools connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Emergency CD/DVD eject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Internal component troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

2052436-002B CARESCAPE™ Gateway iii

Application troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Cloverleaf database failure recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

Event logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37

Database viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

6 Field replaceable units (FRU) . . . . . . . . . . . . . . . . . . 6-1

Field replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

iLO management/configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Purge ADT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

iv CARESCAPE™ Gateway 2052436-002B

Password management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

View server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

ADT workflow configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

CARESCAPE Network MC bed list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

S/5 Network bed list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18

Properties configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

Time synchronization properties configuration . . . . . . . . . . . . . . . . . . . . 7-23

Display serial number information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Upload/download files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

License configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Common Cloverleaf configuration changes . . . . . . . . . . . . . . . . . . . . . . . . 7-29

Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

Cloverleaf Webmin utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33

2052436-002B CARESCAPE™ Gateway v

8 System fail recovery . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

CARESCAPE Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

S/5 Network scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22

D Technical specifications . . . . . . . . . . . . . . . . . . . . . . D-1