GE Healthcare

CARESCAPE Network
Configuration Guide

CARESCAPE Network
English

2026338-002C (paper)
© 2007-2008 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.

Listed below are GE Medical Systems Information Technologies trademarks. All other trademarks contained herein are the
property of their respective owners.

APEX, DASH, SITELINK, and CARESCAPE NETWORK are trademarks of GE Medical Systems Information Technologies
registered in the United States Patent and Trademark Office.

UNITY is a trademark of GE Medical Systems Information Technologies.

T-2 CARESCAPE Network 2000716-005C

23 October 2008
 Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Manufacturer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Safety statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Dangers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

2 Requirements and configuration . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

CARESCAPE Network MC/IX application requirements . . . . . . . . . . . . . . . 2-3

Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Network installation requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Network devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Network equipment protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Quality of Service (QoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Access switch port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Bandwidth calculations for CARESCAPE Network client devices . . . . . . 2-12

2000716-005C CARESCAPE Network i

 3 On-site checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Required tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Design phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Network infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
CARESCAPE Network MC/IX application . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Installation phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Network equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Network equipment configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Network equipment interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Installed network infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Data link (Layer 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
IP connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

CARESCAPE Network MC/IX application . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

MC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
IX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
RX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
CARESCAPE Network performance and reliability . . . . . . . . . . . . . . . . . . 3-8

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

A Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Acronym definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Term definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

B Checkout form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

CARESCAPE Network checkout form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Design phase test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Installation phase test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Installed network infrastructure test results . . . . . . . . . . . . . . . . . . . . . . . . B-4
CARESCAPE Network MC/IX application test results . . . . . . . . . . . . . . . . B-4
CARESCAPE Network performance and reliability test results . . . . . . . . . B-5
Network management test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

ii CARESCAPE Network 2000716-005C

 1 Introduction

2000716-005C CARESCAPE Network 1-1

Introduction

Overview
Intended audience
„ Primary — Network designers and administrators.
„ Secondary — Biomedical engineers.
„ Reference — Field service engineers.

Intended use
This network configuration guide is intended for network designers and
administrators. Its purpose is to aid in the design and configuration of the
CARESCAPE Network. It contains verification procedures used in commissioning
the network.

Ordering manuals
To order additional copies of this manual, contact your local GE representative and
request the part number on the first page of the manual.

Revision history
Each page of this manual has the document part number and revision letter at the
bottom of the page. The revision letter identifies the document’s update level.

Revision Comment

A Initial release of this manual.

B Updated based on feedback and branding.

C Updated for switch limitations.

Related documents
„ CARESCAPE Network as an enterprise VLAN Approved Equipment List

Responsibility
Customer
„ Management of network traffic, bandwidth, security and performance to support
the patient monitor(s).
„ Initial troubleshooting of the network for the patient monitors.
„ Process management to coordinate planned network maintenance and outages
and provision for unplanned outages.

1-2 CARESCAPE Network 2000716-005C

 Introduction

Manufacturer
„ Provide installation and troubleshooting of patient monitoring equipment under
warranty.
„ Provide design and commissioning of the patient monitor network, including
verification, as per contract agreement.
„ Provide other network services, such as cabling, installation and troubleshooting
as per contract agreement.

Safety information
Safety statements
The safety statements presented in this chapter refer to the system in general and, in
most cases, apply to all aspects of the network. There are additional safety statements
in other chapters which are specific to that chapter content.

The terms danger, warning, and caution are used throughout this manual to point out
hazards and to designate a degree or level of seriousness.

The order in which safety statements are presented in no way implies the order of
importance.

Dangers
Danger statements identify an imminent hazard which, if not avoided, will result in
death or serious injury. No danger statements apply to this system.

Warnings
Warning statements identify a potential hazard or unsafe practice which, if not
avoided, could result in death or serious injury.

The following warning statements apply to this system.

WARNING
CARESCAPE NETWORK AS ENTERPRISE VLAN ALLOWED
TRAFFIC — Do NOT allow non-CARESCAPE Network data on
the CARESCAPE Network as enterprise Virtual Local Area
Networks (VLANs) except for limited, specific traffic that is pre-
agreed upon between the hospital and the GE design team.

2000716-005C CARESCAPE Network 1-3

Introduction

WARNING
ELECTRIC SHOCK —To avoid electric shock, the network
equipment and its accessories should not be placed within the patient
environment, which is a volume related to an object (bed, chair,
table, treadmill, etc.) where a patient is intended to be diagnosed,
monitored, or treated.

WARNING
LABELING —Labeling prevents mishandling and misuse of
equipment. The following labeling is required for the applicable
equipment:

„ Network equipment should have a warning label to indicate it is

used for patient monitoring.
„ Power cords for networking equipment should have warning
labels indicating use for patient monitoring.
„ Network cables attached to the network equipment should have
warning labels at both ends of the cable indicating use for
patient monitoring.
„ Wall jacks used to connect patient monitoring devices should be
clearly labeled to identify the MC and IX networks.
„ CARESCAPE Network identification label is attached to IX
network cables connected to all CICs.
Contact your local sales or service representative to order
additional label kits.

WARNING
QUALIFIED EQUIPMENT—Equipment used for network
infrastructure must be qualified by GE. GE has lists of equipment
qualified to work in a topology and configuration tested for
functionality and performance.

WARNING
QUALITY OF SERVICE — The network shall implement a Quality
of Service (QoS) policy that prioritizes data as defined in this
document to meet the latency and jitter requirements of time
sensitive data, limit traffic to a specific bandwidth and, in case of
congestion, determine drop probabilities of data.

This applies only to networks implementing VLANs.

WARNING
SPANNING TREE —Redundant topologies must prevent loops that
cause broadcast storms by the use of Spanning Tree.

1-4 CARESCAPE Network 2000716-005C

 Introduction

WARNING
SWITCH CONFIGURATION CONSTRAINTS —Switch
configuration constraints and bandwidth limits must be followed to
ensure the required performance and reliability of the network.

Cautions
Caution statements identify a potential hazard or unsafe practice which, if not
avoided, could result in minor personal injury or product/property damage.

The following caution statements apply to this system.

CAUTION
NETWORK INSTALLATION REQUIREMENTS — Failure to
comply with the installation requirements as defined in this
document can impact the performance and reliability of the network.

CAUTION
RESTRICTED SALE — U.S. Federal law restricts this device to be
sold by or on the order of a physician.

Notes
Note statements provide application tips or other useful information.

Symbols

Manufacturer name and address.

European authorized representative.

2000716-005C CARESCAPE Network 1-5

Introduction

1-6 CARESCAPE Network 2000716-005C

 2 Requirements and
configuration

2000716-005C CARESCAPE Network 2-1

Requirements and configuration

Introduction
NOTE

The Unity Network has been renamed to the CARESCAPE Network. Not all
references to the Unity Network will be changed immediately; Unity may appear
in some places and CARESCAPE in others. It is important to understand that
while the CARESCAPE Network replaces the Unity Network name, they refer to
the same GE monitoring network.

NOTE

The CARESCAPE Network MC network, protocol and application will be

referred to as the MC network, MC protocol and MC application throughout this
document. Also, The CARESCAPE Network IX network, protocol and
application will be referred to as the IX network, IX protocol and IX application
throughout this document

The CARESCAPE Network is the network infrastructure hosting GE monitoring

devices. These devices are referred to as client devices to differentiate them from
network equipment.

The CARESCAPE Network MC/IX applications are the communication software that
use the MC/IX protocols to exchange data.

The MC/IX protocols are the application layer protocols that define the rules of
communication among GE patient monitors, central stations, data servers and other
supporting devices.

There are two types of CARESCAPE Network application data that are
communicated on separate networks:

„ MC - Mission Critical, consists of real-time clinical traffic that includes:

‹ service discovery (RWhat)
‹ alarm broadcast
‹ alarm configuration
‹ waveform request/update
‹ parameter request/update
‹ time request/response/update
‹ admit/discharge
‹ trends
‹ graphs
„ IX - Information Exchange, consists of non-real-time clinical traffic that
includes:
‹ full disclosure
‹ print data

2-2 CARESCAPE Network 2000716-005C

 Requirements and configuration

CARESCAPE Network MC/IX application

requirements
Connectivity
The MC/IX application requires IP connectivity between CARESCAPE Network
client devices to enable broadcast and unicast messages.

Performance
The MC application requires MC packet latency of less than 250 ms. Packet latency
from the ApexPro Telemetry Server (ATS) or bedside to the CIC Pro Clinical
Information Center (CIC) should be less than 250 ms in order for the system to meet
AAMI EC13 - 2002 Sections 4.2.8.4, 4.2.8.5, 4.2.8.6 Time to Alarm.

Reliability
The MC application requires MC packet loss of less than or equal to 1 packet per
million.

Configuration
IP addressing
The MC and IX networks are assigned their own classful network address. This
prevents confusion on devices that are on both the MC and IX networks as to which
interface port to use.

In addition, all MC client devices that need to communicate with each other are
placed in one classful network. This is because IP broadcasting is used by MC client
devices to make their presence known on the network and to announce alarms.

Private IP addresses are used in cases when the site does not provide the addresses.
Public IP addresses should not be used without proper authorization. Exemptions may
be made for isolated neworks with no connectivity to the internet and enterprise
networks and have no multi-homed clients connected to enterprise networks.

Limit on number of CARESCAPE Network client devices

The MC network should not have more than 1023 client devices. This is a limit
imposed by the size of device (RWhat) table in certain CARESCAPE Network client
devices.

There shall be no more than 48 access ports assigned to MC devices in a single

network device. This is to reduce the clinical impact of the loss of a network device.

2000716-005C CARESCAPE Network 2-3

Requirements and configuration

Network installation requirements

WARNING
ELECTRIC SHOCK —To avoid electric shock, the network
equipment and its accessories should not be placed within the patient
environment, which is a volume related to an object (bed, chair,
table, treadmill, etc.) where a patient is intended to be diagnosed,
monitored, or treated.

The installation requirements define how the network is built and maintained to
achieve the performance and reliability required by the MC/IX application.

Network devices
Overview
Equipment used for network infrastructure should be qualified by GE. GE has lists of
equipment qualified to work in a topology and configuration tested for functionality
and performance.

There are three ways network devices are deployed for the CARESCAPE Network.

„ Dedicated network devices for each network (MC, IX, etc.)

„ Dedicated network devices for GE patient monitoring VLANs
„ Non-dedicated network devices shared with the customer VLANs
A Virtual Local Area Network (VLAN) is a logical network of devices that run on a
physical network infrastructure that could potentially be shared with other VLANs.

Dedicated network devices for each network

This implementation is for small area installations only.

Network devices are dedicated to each of the MC and IX networks. The switches may
be used with the default configuration of VLAN1 assigned to all ports.

There is network equipment that is qualified for use by GE in the dedicated/no

sharing network topology. These devices are tested for basic connectivity, latency and
packet loss.

Dedicated network devices for GE patient monitoring VLANs

This implementation is used for large area network coverage where it is too costly to
have separate dedicated network infrastructure for each VLAN.

The network infrastructure is shared by the CARESCAPE Network MC and IX

VLANs, Telemetry VLAN and Administration VLAN.

„ MC VLAN - Mission Critical, carries real-time clinical traffic

2-4 CARESCAPE Network 2000716-005C

 Requirements and configuration

„ IX VLAN - Information Exchange, carries non-real-time clinical traffic, such as

full disclosure and print data
„ RX - VLAN for real time, unprocessed telemetry data
„ Administration - the network control and management VLAN
Access to and from the hospital network is limited to the IX and/or Administration
VLANs using router; this access is controlled by access control lists.

VLANs in the same physical network behave as separate networks. Client devices in
different VLANs can not send unicast or broadcast to each other without using
routers.

Network devices are qualified by GE for use in the shared network topology.
Qualification tests include basic connectivity within VLANs as well as tests for
advanced functions, such as QoS, access control lists, routing and link aggregation.

Non-dedicated network devices shared with the customer VLANs

The CARESCAPE Network MC and IX VLANs share the network infrastructure
with the customer VLANs. Refer to the CARESCAPE Network as an enterprise
VLAN Configuration Guide for more details.

Topology
The topology designed for a site should follow the topology qualified by GE with the
network devices.

Qualified network topologies use a layered design. The layered design consists of:

„ Distribution switches that interconnect access switches

„ Access switches that connect client devices to the network
Some switches are approved for use at the distribution layer only in a redundant
configuration. Some are approved for use at the access layer only in redundant
configuration satisfied with dual uplinks to a redundant distribution, at a minimum.

Redundancy is required when a switch does not meet reliability requirements, such as
Mean Time Between Failure (MTBF) of 10 years or more. The redundancy
requirement is determined during the equipment qualification process.

There are two ways to achieve hardware redundancy:

„ Use of two independent units in a Root/Broot configuration or in a configuration

that makes two units act like a single unit, as in stacked configurations.
„ Use of a single chassis-based unit with redundant CPU, redundant power supply
and redundant interface modules. A single unit with redundant components is
deployed in the topology like a stacked switch.
The limitations on the use of network equipment as determined during functional
verification should be followed. Refer to the CARESCAPE Network as an enterprise
VLAN Approved Equipment List.

Switches verified as access switches should be used as access switches in a site

installation; switches verified as distribution switches should be used as distribution
switches.

2000716-005C CARESCAPE Network 2-5

Requirements and configuration

In addition, qualified topologies follow the rule that limits the number of switches
between any two end stations to seven, with a maximum depth of four switches below
the main distribution switch, which is the root bridge of the Spanning Tree protocol
(STP).

The following figures represent topologies that are qualified.

011b
Topology with stacked distribution switches

013A
Topology with STP root/backup root distribution switches

The topologies show how access switches are connected to the distribution switches.

Typically, redundancy is not a requirement but a recommendation to maximize

availability of the network. A combination of redundant and non-redundant links may
be used. For example, a network design may use redundant connections between
main distribution and closet distribution switches and non-redundant connections
between access and distribution switches.

The qualified topologies are used as patterns for network design.

The following figure shows site network topology patterned after the qualified
topology.

2-6 CARESCAPE Network 2000716-005C

 Requirements and configuration

012b

Cabling
Cabling should use the following:

„ category 5e or higher, UTP or STP, terminated to an RJ-45 connector

„ stranded copper for copper patch cable
„ plenum-rated solid copper for cabling within walls
„ 62.5/125 or 50/125 micron multi-mode fiber for two Kilometer or shorter
distances; single mode fiber for longer distances
The cabling terminations and installations should meet ANSI/EIA/TIA standards.

Network equipment protection

Network equipment protection is necessary in achieving the close to zero downtime
goal for the CARESCAPE Network. The following security measures are required:

„ Network equipment should be secure in locked closet.

„ Configurable network equipment should be protected with password.
In addition, measures should be taken to protect network equipment from loss of
power. Network equipment should be connected to UPS (Uninterruptible Power
Supply). The recommended UPSs have SNMP v3 or v2 and have an RJ-45 ethernet
connection for remote management.

It is strongly recommended that configurable network equipment display a banner

indicating it is used for patient monitoring to prevent unintentional corruption of
configuration.

It is also recommended that a backup power system (e.g., emergency power supply) is
available for network devices so communication is uninterrupted when power is lost
for longer duration.

It is recommended that N+1 network equipment be deployed per closet, where N is

the required number of units and 1 is the spare. This is another measure to reduce
network downtime.

2000716-005C CARESCAPE Network 2-7

Requirements and configuration

Labeling
Labeling prevents mishandling and misuse of equipment. The following labeling is
required for the applicable equipment:

„ Network equipment should have a warning label to indicate it is used for patient
monitoring.
„ Power cords for networking equipment should have warning labels indicating use
for patient monitoring.
„ Network cables attached to the network equipment should have warning labels at
both ends of the cable indicating use for patient monitoring.
„ Wall jacks used to connect patient monitoring devices should be clearly labeled
to identify the MC and IX networks.
„ CARESCAPE Network identification label is attached to IX network cables
connected to all CICs.
NOTE
Contact your local sales or service representative to order additional label
kits.

Environment
Equipment should be in an environment that meets equipment operating requirements
in terms of temperature, absence of interference (EMI) and other environmental
factors.

Management
„ Network design should have full, updated documentation.
„ Documentation should include:
‹ Documentation of interconnections: spreadsheet and diagrams
‹ Documentation of closets and network equipment
‹ Documentation of cable runs
‹ Documentation of network device configuration including:
VLAN spanning tree root and backup root if redundant
QoS settings
‹ Documentation of network IP addresses
In addition to documentation, the following are recommended for better network
maintenance and troubleshooting:

„ Constant network monitoring using SNMP

„ SNMP with authentication
„ Network equipment time synchronization using NTP
„ Network equipment event logging
SNMP monitoring of the status of the switch and its modules is strongly
recommended in chassis-based network equipment. It enables correction of a non-
catastrophic failure like fan failure before it causes a switch shutdown.

2-8 CARESCAPE Network 2000716-005C

 Requirements and configuration

Configuration
Quality of Service (QoS)
In a shared network infrastructure between the CARESCAPE Network and hospital
enterprise network, QoS is required to give preferential treatment to time sensitive
traffic. It is recommended that messages are marked with priorities as close to the
source as possible.

The network should be designed to recognize the data frame marking at Layer 2
(802.1q/p Class of Service [CoS]) and the packet marking at Layer 3 (IP Type of
Service ToS/DSCP) and use the marking to determine delivery preference for the
data.

CARESCAPE Network client devices that mark the traffic are connected to access
switch ports configured to use the DSCP marking of incoming packets. MC network
devices that do not put DSCP mark are connected to access switch ports with default
CoS marking of 2 applied to all incoming packets.

The CoS marking is used to prioritize packets within the switched domain. The DSCP
marking is used to prioritize packets across routers.

Mappings between CoS and DSCP should be maintained consistently throughout the
network. The following are default mappings used in the standard configuration.

CoS 0 1 2 3 4 5 6 7

DSCP 0 8 16 26 34 46 48 56

DSCP 0 8 10 16 18 24 26 32 34 40 46 48 56

CoS 0 1 1 2 2 3 3 4 4 5 5 6 7

Priority of traffic is defined as follows:

Traffic CoS Priority

Network control data (BPDU, etc.), 7

Administration (telnet, SNMP)

RT Media, VoIP (limited bandwidth) 6 or 5 (depends on device)

RX 4

MC 3 or

2 (default in network hardware)

IX 1 or

0 (default in network hardware)

Hospital 1 or 0

Guest 0

2000716-005C CARESCAPE Network 2-9

Requirements and configuration

The RX data is given preference over MC data because it is unprocessed telemetry

data with a latency requirement of 50 milliseconds or less, a jitter requirement of 10
milliseconds or less and a packet loss requirement of 1 packet or less per million
packets sent.

NOTE

For CARESCAPE Network as an enterprise VLAN, the CoS priorities are

determined by the site, but the overall order of preference must follow the above
table. See the CARESCAPE Network as an enterprise VLAN Configuration
Guide.

Access switch port configuration

Access ports for CARESCAPE Network client devices are configured differently
from the standard configuration with respect to the following settings:

„ VLAN
„ Speed/Duplex
„ QoS

VLAN
A port is assigned a VLAN depending on the type of client device attached to it and
this varies from site to site.

Speed/Duplex
Speed and duplex settings are defaulted to auto-negotiate in the standard switch
configuration. This setting is correct for a majority of CARESCAPE Network client
devices.

Client device configuration Switch configuration Negotiated speed/duplex

AUTO Negotiate (10/100) AUTO Negotiate 100 Mbps/Full Duplex

10 Mbps/Half Duplex AUTO Negotiate 10 Mbps/Half Duplex

100 Mbps/Full Duplex AUTO Negotiate 100 Mbps/Half Duplex

(mismatch)

100 Mbps/Half Duplex AUTO Negotiate 100 Mbps/Half Duplex

The qualified switches are able to negotiate correctly with client devices configured
to auto negotiate.

Qualified switches are also able to default to correct settings with client devices fixed
at 10 Mbps/Half duplex.

However, the switch is unable to negotiate or default to correct duplex setting with
client devices fixed at 100 Mbps/Full Duplex.

2-10 CARESCAPE Network 2000716-005C

 Requirements and configuration

QoS
The QoS setting depends on the type of CARESCAPE Network client device.

Ports connected to network devices with DSCP markings in their packets are
configured to use DSCP marking of incoming packets. Otherwise, ports are
configured to assign a CoS marking to incoming frames; the CoS markings are
converted to DSCP markings applied to the IP header.

The following table shows the CoS markings applied by the switch on frames of
CARESCAPE Network client devices with no DSCP markings.

CARESCAPE Network Client

CoS marking
Device

MC client device 2

IX client device 0

The following table shows the CARESCAPE Network client devices that apply
DSCP markings on the packets.

CARESCAPE Network Client

DSCP on MC VLAN DSCP on IX VLAN
Device

Dash V6 26 0

All other None (default to 0) 0

IP Address
The MC and IX networks are assigned their own classful network address. These
addresses may come from the customer. If GE assigns the addresses, these addresses
will be private addresses. An isolated MC network may be left at the default IP
address setting configured on the client devices.

The IP address allocations and assignments must be documented. The documentation

serves as reference for used and available IP addresses.

Different IP addresses used at the site changes entries in the template configuration:

„ Administration VLAN IP address

„ Default gateway IP address
„ NTP server IP address
„ SNMP server IP address

Routing
Routing capability of the distribution switches is turned off when the CARESCAPE
Network is isolated from the other networks and inter-VLAN routing is not needed.

The following are cases when routing is enabled on distribution switches:

2000716-005C CARESCAPE Network 2-11

Requirements and configuration

„ If the site is responsible for monitoring the CARESCAPE Network, then the site
is given controlled access to the Administration VLAN through the router port on
the distribution switch. All other CARESCAPE Network as an enterprise VLAN
virtual interfaces are shutdown except for the CARESCAPE Network
administration VLAN. Access control lists are used to limit access.
„ If there is a resource, such as an NTP server or printer, shared by CARESCAPE
Network client devices on different VLANs, then controlled inter-VLAN routing
is enabled. CARESCAPE Network as an enterprise VLAN virtual interfaces are
shut down except for CARESCAPE Network administration VLAN and
CARESCAPE Network as enterprise VLANs with devices that share the
resource. Access control lists are used to limit access.
„ If there are CARESCAPE Network client devices that want to access the hospital
network, then controlled access is permitted by connecting the site network to the
routed port on the distribution switch and virtual interfaces of VLANs with
devices that want to access the hospital network are enabled. Access control lists
are used to limit access.
Multi-homed devices with direct connection to the mission-critical network are
connected to the hospital network via non-mission critical CARESCAPE
Network as an enterprise VLAN that has a routed connection to the hospital
network.

Bandwidth calculations for CARESCAPE Network client devices

Bandwidth calculations are used when determining the number and type of devices
that could share network equipment and link.

The following table can be used for estimating bandwidth utilization.

Incoming Outgoing

RWhat broadcasts per 107.2 bps

device (CIC, bedside,
telemetry bed, etc.)

Alarm broadcast per patient 520 bps

monitor

Patient monitor 50 Kbps 100 Kbps

Telemetry server (ATS) 3.4 Kbps 1600 Kbps

CIC MC 1.65 Mbps 5.4 Kbps

CIC IX 2 Mbsp max 2 Mbps max

Bandwidth utilization details

CARESCAPE Network RWhat broadcast

The frequency of RWhat packets depends on the number of bedside monitors
connected in the CARESCAPE Network as an enterprise VLAN.

2-12 CARESCAPE Network 2000716-005C

 Requirements and configuration

Number of CARESCAPE RWhat packet per second

Bits per second per device
Network client devices (134 bytes/packet)

1-99 1 per 10 sec 107.2

100 - 149 1 per 15 sec 71.47

150 - 249 1 per 25 sec 42.88

250 and greater 1 per 28 sec 38.29

The bandwidth of RWhat broadcast for 1023 devices: 1023 devices* 38.29 bps per
device = 39170 bps, 39 Kbps RWhat.

CARESCAPE Network alarm broadcast

The frequency of alarm broadcast packets is one packet every two seconds. The size
of an alarm broadcast is 130 bytes.

NOTE

Even if there are two alarms active in a bedside monitor, only one Alarm
Broadcast packet is sent.

The bandwidth of alarm broadcast for 1023 devices: 1023 devices * 130 bytes/2 sec
per device = 66495 bytes per sec = 531960 bps = 532 Kbps.

Bandwidth of bedside GE patient monitors

A typical patient monitor has one waveform stream (referred to as patient view in this
document) required for display on the CIC and one waveform stream required for Full
Disclosure. For each patient view, 40 Kbps is required. This amounts to 80 Kbps
waveform traffic per patient monitor.

To account for the rest of CARESCAPE Network traffic (alarms, RWhats, graphing,
histories, trends, etc.), assume that the waveform traffic is 80% of the total, and add
25% to the calculated waveform usage.

The remaining traffic will amount to approximately 20 Kbps, totaling 100 Kbps per
bed.

Bandwidth of ATS
The ApexPro Telemetry (ATS) server outgoing traffic on the MC VLAN is calculated
as follows:

16 patients * 100 Kbps = 1600 Kbps

The ATS server incoming traffic on the MC VLAN is calculated as follows:

((16 patients * 108 bytes parameter requests/10 sec) + (16 patients * 108 bytes
waveform request/10 sec)) * 125% for rest of traffic = 3.4 Kbps.

CIC bandwidth
The bandwidth of CIC incoming MC traffic is 1.65 Mbps; outgoing on MC is 5.4
Kbps; outgoing/incoming on IX during transmission of Full Disclosure is up to 2
Mbps.

2000716-005C CARESCAPE Network 2-13

Requirements and configuration

Bandwidth calculation for a device is based on maximum utilization.

CIC incoming traffic on MC VLAN is calculated as follows:

((16 patients view + 16 patients being full disclosed + single viewer open) * 40 Kbps/
view * 125% for the rest of traffic including graph, histories, trends) = 1.65 Mbps.

CIC outgoing traffic on MC VLAN is calculated as follows:

((17 patient view * 108 bytes parameter request/10 sec) + (33 patient view * 108
bytes waveform request /10 sec)) * 125% for the rest of traffic = 5.4 Kbps.

NOTE

Do not include both CIC incoming and patient monitoring outgoing. It is the
same network traffic.

Calculation of switch uplink bandwidth

Access switches are connected to the distribution switch using at least 100 Mbps, full
duplex link. This means the access switch has 100 Mbps input and 100 Mbps output
bandwidth. The following are estimated bandwidth usages on an access switch uplink
port.

SCENARIO 1

A typical use of a 24-port access switch is to connect 16 patient monitors and 2 CICs.

For calculation purposes, assume there are 1023 client devices in the network and
100% have alarms amounting to approximately 571 Kbps broadcast.

„ 1 CIC gets data from patient monitors in the same switch.

„ 1 CIC gets data from patient monitors across the network.
„ 16 patient monitors report data to 1 CIC in the same switch and to another CIC
across the network.
„ No full disclosure actively exchanged between CICs.

Total
Uplink port 16
Broadcast CIC-1 CIC-2 (average
traffic monitors
traffic)

Incoming 562 Kbps negligible 1.65 640 Kbps 2.6 Mbps

Mbps

Outgoing 9 Kbps negligible 5 Kbps 1600 Kbps 1.6 Mbps

The switch trunk port with 100 Mbps bandwidth, full duplex, could easily handle an
additional full disclosure traffic averaging 2 Mbps on IX network.

NOTE

Mixing patient monitors with CICs in the same switch is a good way to utilize
available uplink bandwidth; CICs use incoming link; patient monitors use
outgoing link.

SCENARIO 2

2-14 CARESCAPE Network 2000716-005C

 Requirements and configuration

Another typical use of a 24-port access switch is to host CICs in a monitoring center.
Assuming there are 8 CICs getting data from across the network, 8 CICs occupy 8
MC ports and 8 IX ports in a 24-port switch; 8 ports are Admin and spares. The
following is the estimated bandwidth usage on the switch uplink trunk port.

Total (average
Uplink port traffic Broadcast 8 CICs
traffic)

Incoming 566 Kbps 1.65 x 8 = 13.8 Mbps

13.2 Mbps

Outgoing 5 Kbps 5x8= 45 Kbps

40 Kbps

2000716-005C CARESCAPE Network 2-15

Requirements and configuration

2-16 CARESCAPE Network 2000716-005C

 3 On-site checkout

2000716-005C CARESCAPE Network 3-1

On-site checkout

Required tools
„ Network Sniffer, such as Omnipeek 4.0
„ Traffic metrics/traffic generation tool, such as IX Chariot 6.30
„ Two laptop PCs used as client devices
„ One PC hosting tool

Design phase
These on-site checkout procedures are done during the design phase of the network.

Documentation
Verify that the network design and configuration are fully documented prior to
installation. Documentation to include:

„ Documentation of interconnections: spreadsheet and diagrams

„ Documentation of closets and network equipment
„ Documentation of cable runs
„ Documentation of network device configuration including:
‹ VLAN spanning tree root and backup root if redundant
‹ QoS settings
„ Documentation of network IP addresses

Network infrastructure

WARNING
SWITCH CONFIGURATION CONSTRAINTS —Switch
configuration constraints and bandwidth limits must be followed to
ensure the required performance and reliability of the network.

1. Verify that the network devices are qualified for what they will be used for:
dedicated to a network, dedicated to patient monitoring VLANs or shared with
hospital VLANs.

2. Verify that switches used as access switches and distribution switches are
qualified for those roles.

3. Verify redundancy on switches approved for use in redundant configuration only.

4. Verify that the limitations identified in the CARESCAPE Network as an

enterprise VLAN Approved Equipment List are followed.

5. Verify that the topology designed for the site is patterned after the topology
qualified with the selected network devices. See Topology on page 2-5.

6. In the topology design, verify that there are no more than seven switches in the
path between two client devices in a switched domain.

3-2 CARESCAPE Network 2000716-005C

 On-site checkout

7. Verify that the documented configuration of network devices is patterned after

the configuration used in qualifying the network devices. See Configuration on
page 2-9.

CARESCAPE Network MC/IX application

1. Verify that all CARESCAPE Network client devices that want to communicate
with each other are in one classful network.

2. Verify that MC network devices are assigned a classful IP network address and
IX devices are assigned a separate classful IP network address.

3. Verify that MC and IX IP addresses are private addresses, if the addresses were
not provided by the customer, isolated networks are exempt.

4. Verify that if public IP addresses are used, proper authorization is obtained,

isolated networks are exempt.

5. For a shared network, verify VLANs are defined for each functional group of
devices.

6. Verify that there are no more than 1023 CARESCAPE Network client devices
planned to be on an MC network.

7. Verify that there are no more than 48 MC access ports in a switch.

8. For a shared network, verify QoS is configured.

„ Verify that CARESCAPE Network client devices that put DSCP markings
on the packets are attached to access switch ports that use the incoming
packet DSCP marking; these ports have a default CoS of 0.
„ Verify that MC client devices that do not apply DSCP markings are attached
to MC ports that apply CoS markings on incoming packets; the access port is
the closest device to mark packets from the source.
„ Verify that MC, IX, RX and other data are assigned the correct priorities. See
Quality of Service (QoS) on page 2-9.
„ Verify that unused ports have a default CoS of 0.
„ Verify that CoS to DSCP mappings and vice versa are consistent in all
switches and routers.

Installation phase
These on-site checkout procedures are done during the installation phase of the
network.

Cables
Cable procedures 1 through 2 are for a network dedicated to GE patient monitoring.
Hospital networks may have their own cabling requirements.

1. Verify that cables used are:

2000716-005C CARESCAPE Network 3-3

On-site checkout

„ category 5e or higher, UTP or STP terminated to an RJ-45 connector

according to the T568B pin/pair assignment and wiring scheme
„ 62.5/125 micron or 50/125 micron multi-mode fiber, or single mode fiber
„ stranded copper for copper patch cables
„ plenum-rated solid copper run within walls
This can be based on data furnished by the installer or site IT department.

2. Verify cabling meets post-installation termination testing requirements as

specified by ANSI/EIA/TIA standards for the given cable type. This can be
verified based on the cable testing performed by the installers or other qualified
individuals.

3. Verify that the network cables and power cables for network equipment have the
appropriate Warning labels.

4. Verify that wall jacks are clearly labeled for the intended use.

5. Verify that a CARESCAPE Network identification label is attached to IX

network cables connected to all CICs.

Network equipment
1. Verify that the network equipment is secure in locked closet.

2. Verify that the network equipment is connected to UPS.

3. Verify that there is a backup power supply (e.g., emergency power system)
available in case of power outage.

4. Verify that N+1 network equipment is installed per closet.

5. Verify that the network equipment environment meets the equipment operating
requirements:

„ ambient temperature range is between +0° C to +45° C (32° F to 113° F)

„ atmosphere up to 85% relative humidity
6. Verify that the network equipment has the appropriate Warning label.

7. Verify that the network equipment power cord has the appropriate Warning label.

8. Verify that the network equipment environment meets equipment operating

requirements.

Network equipment configuration

1. Verify that the network equipment “running configuration” and the “stored
configuration” are the same.

Display network equipment “running configuration” and compare to documented

configuration. If they are not the same, then update either the running
configuration or the documentation, whichever is the latest, correct
configuration; store the running configuration to non-volatile memory.

2. Verify the configurable network equipment is password protected.

3-4 CARESCAPE Network 2000716-005C

 On-site checkout

„ Login to each switch using console terminal. The switch should ask for a
password.
„ Login to each switch using telnet. The switch should ask for a password.
3. Verify the configurable network equipment displays a banner indicating use for
patient monitoring at the start of login.

4. Verify the network equipment logs events, such as port status change.

5. Verify that configurable network equipment is time synchronized.

Network equipment interconnection

Verify the network equipment is interconnected as topology diagram or spreadsheet
specifies.

„ observe the link light for indication of link up or down, speed and duplex settings
„ or display interface status on the network equipment

Installed network infrastructure

These on-site checkout procedures are to be executed on the installed network
infrastructure.

Data link (Layer 2)

1. Verify the spanning tree root switch, backup root switch (for redundant topology)
and root port of all switches are as documented.

Query the switch for its root switch and root port for each of the VLANs: MC,
IX, Administration and RX (if present).

In a redundant topology, determine the backup root switch by turning off or

totally disconnecting the root switch and query the other switches for their new
root switch and root port.

2. Verify the absence of looping and potential for broadcast storm on

Administration network.

a. Configure a PC with administration IP address.

b. Connect the PC to the administration port of an access switch.

c. Using the PC, continuously ping another administration IP address that is not
on the network. ARP layer 2 broadcasts are sent repeatedly.

d. Use sniffer to determine if the ARP broadcasts are recirculated on the

Administration network. Or, observe an Administration port status for steady
increase in output bandwidth usage.

3. Verify the absence of looping and potential for broadcast storm on the MC
network. The test is similar to step 2, except MC IP address and ports are used.

4. Verify absence of looping and potential for broadcast storm on the IX network.
The test is similar to step 2, except IX IP address and ports are used.

2000716-005C CARESCAPE Network 3-5

On-site checkout

5. Verify absence of looping and potential for broadcast storm on the RX network,
if present. The test is similar to step 2, except RX IP address and ports are used

IP connectivity
1. Verify IP connectivity on the administration network.

Configure a PC with an Administration VLAN IP address. Connect to an

Administration port. Ping the IP addresses of all the switches from the PC.

2. Verify the IP connectivity on the MC network.

Configure two PCs with MC IP addresses. Connect PCs to MC ports of different

access switches. Verify the PCs are able to ping each other. Test other access
switches by moving PCs to different access switches and repeat ping.

3. Verify the IP connectivity on the IX network.

Configure two PCs with IX IP addresses. Connect PCs to IX ports of different

access switches. Verify the PCs are able to ping each other. Test other access
switches by moving PCs to different access switches and repeat ping.

4. Verify the IP connectivity on the RX network, if present.

Configure two PCs with RX IP addresses. Connect PCs to RX ports of different

access switches. Verify the PCs are able to ping each other. Test other access
switches by moving PCs to different access switches and repeat ping.

5. Verify there is no IP connectivity across different networks unless allowed by

design.

„ Configure two PCs, one with IX IP address and the other with MC IP
address. Connect PCs to corresponding VLAN ports at different access
switches. Verify the PCs are NOT able to ping each other.
„ Verify the PCs are not able to ping the switches in the Administration
VLAN.
„ If RX network is present, configure one of the PCs with an RX IP address
and connect to the RX VLAN port. Verify the PC is not able to ping the other
PC and the switches in the Administration VLAN.
6. Verify limited connectivity to CARESCAPE Network as enterprise VLANs as
allowed by Access Control Lists.

„ Test that only packets that need to go into the MC VLAN are allowed in and
the rest are blocked. This test depends on what parameters are used by ACLs
to filter data. If data is filtered using source IP, then ping an MC client device
from an allowed IP source; this ping should get through. Pings from an IP
source that is not permitted should not go through.
„ Test that only packets that need to go into the IX VLAN are allowed in and
the rest are blocked. This test depends on what parameters are used by ACLs
to filter data.
7. Verify network services are operational, specifically NTP. Verify network
equipment time is synchronized using NTP.

Query network equipment for its time and its NTP time master. Compare
equipment time to that of time master.

3-6 CARESCAPE Network 2000716-005C

 On-site checkout

CARESCAPE Network MC/IX application

MC
Description
These procedures verify that CARESCAPE Network client devices on MC network
have the required IP connectivity across the network. It requires at least two
CARESCAPE Network bedside monitors (bedside-1 and bedside-2) and one CIC on
the MC network and I/O simulators.

Procedures
1. Verify that bedside-1 is able to view bedside-2.

2. Verify that the CIC is able to view both monitors.

3. Verify that the alarms, parameters and waveforms from bedside-2 show on the
CIC and bedside-1.

4. Move bedside-2 to different access switches. Repeat steps 1 through 3 for each
move.

IX
Description
These procedures verify that CARESCAPE Network client devices on IX network
have the required IP connectivity across the network. It requires at least one GE
bedside patient monitor with I/O simulators on the MC network and either:

„ two CICs on both the MC and IX network

or
„ one CIC and one printer on the IX network

Procedures
Verify CIC is able to print to a printer on IX network.

OR

1. Configure CIC-1 to collect full disclosure data from a bedside monitor.

2. Verify that CIC-2 is able to display full disclosure, which comes from CIC-1 over
IX network.

2000716-005C CARESCAPE Network 3-7

On-site checkout

RX
NOTE

The RX procedures apply to ApexPro FH only.

Description
These procedures verify that devices on RX network have the required IP
connectivity across the network. It requires at least one ATS, one FH-AP and PC with
OpenNet Expert Tool.

Procedures
1. Verify that the OpenNet Expert tool is able to connect to the AP and configure
the AP.

2. Verify that the ATS is able to communicate to AP using multicast. On the ATS,
open a Webmin session and select AP Statistics. Make sure the AP is present in
the list that is displayed.

CARESCAPE Network performance and reliability

Description
This test measures latency and packet loss of UPD/IP packets to verify they meet MC/
IX application requirements of less than 250 msec packet latency and less than 1
packet drop per million packets sent. Use a traffic generator tool to generate packets
and measure latency and packet loss of UDP/IP conversation between two nodes
called endpoints; endpoint-1 generates 1.65 Mbps traffic directed to endpoint-2 that
simulates a CIC receiving data at full load.

Procedures
1. Verify that latency on the MC network for UPD/IP packet with priority of CoS 2
or 3 is less than 250 msec and the packet drop is less than or equal to 1 per
1,000,000 packets sent.

Select endpoint locations connected by the longest and/or most congested path on
the network. Generate 1.65 Mbps, 970 byte size UDP/IP packets with CoS 2
marking on the MC network from endpoint-1 to endpoint-2. Run the test long
enough so there are at least 1,000,000 packets sent by endpoint-1. Measure
latency and packet loss.

2. If an access switch has a redundant connection to the distribution switch, then

repeat step 1 with the primary link taken down.

3. If RX network is present, determine and record the latency, jitter and packet loss
on the RX network for UPD/IP packet with priority of CoS 4. The test procedure
is similar to the MC performance test. The expected result is that latency is 50
msec or less, jitter is 10 msec or less, and packet loss is less than or equal to one
per million sent.

3-8 CARESCAPE Network 2000716-005C

 On-site checkout

Generate 1.65 Mbps, 970 byte size UDP/IP packets with CoS 4 markings on the
RX network from endpoint-1 to endpoint-2. Run the test long enough so there are
at least 1,000,000 packets sent by endpoint-1. Measure latency, jitter and packet
loss.

4. If an access switch has a redundant connection to the distribution switch, then

repeat step 3 with the primary link taken down.

Network Management
1. Verify that the customer is notified that monitoring the network using SNMP
with authentication is highly recommended.

2. Verify that the customer is notified that SNMP monitoring of the status of a
chassis-based switch and its component modules is highly recommended.

2000716-005C CARESCAPE Network 3-9

On-site checkout

3-10 CARESCAPE Network 2000716-005C

 A Definitions

2000716-005C CARESCAPE Network A-1

Definitions

Acronym definitions

Acronym Definition

AAMI American Association for the Advancement of Medical

Instrumentation

ACL Access Control List

AGS Aware Gateway Server

ANSI American National Standards Institute

ARP Address Resolution Protocol

ATS ApexPro Telemetry Server

BDPU Bridge Protocol Data Unit

CIC CIC Pro Clinical Information Center

CoS Class of Service

DSCP Differentiated Services Code Point

DHCP Dynamic Host Configuration Protocol

EIA Electronic Industries Alliance

HSRP Hot Standby Router Protocol

IOS Internetwork Operating System

IP Internet Protocol

IX Information Exchange

Kbps Kilobits per second

LAN Local Area Network

MAC Media Access Control

Mbps Megabits per second

MC Mission Critical

msec millisecond

ND & I Network Design and Implementation team

NETBIOS Network Basic Input Output System

NTFS NT File System

NTP Network Time Protocol

OSPF Open Shortest Path First

PDS Patient Data Server

PV Patient Viewer

QoS Quality of Service

RIP Routing Information Protocol

A-2 CARESCAPE Network 2000716-005C

 Definitions

Acronym Definition

RX real-time, unprocessed telemetry data

SNMP Simple Network Management Protocol

STP Spanning Tree Protocol

STP Shielded Twisted Pair

TACACS Terminal Access Controller Access Control System

TFTP Trivial File Transfer Protocol

TIA Telecommunications Industry Association

UDP User Datagram Protocol

UTP Unshielded Twisted Pair

VLAN Virtual Local Area Network

VOIP Voice over IP

VRRP Virtual Redundant Router Protocol

WAN Wide Area Network

Wi-Fi Wireless Fidelity

Term definitions

Term Definition

CARESCAPE The network infrastructure hosting devices running the

Network CARESCAPE Network application.

CARESCAPE The communication software that uses the MC/IX protocol to

Network MC/IX exchange data.
application

MC/IX protocol The application layer protocol that defines the rules of
communication among GE patient monitors, central stations, data
servers and other supporting devices.

Classful IP network Network portion of an IP address is based on the first few high-
address significant bits of the first octet of the IP address.

Classless IP network A subnet mask is used to identify network portion of the IP address.
address

Data Link (Layer 2) Layer two of the seven-layer OSI network model.

Information Exchange Non-real-time clinical data.

Mission Critical Real-time clinical data.

Unity Network The Unity Network has been renamed to the CARESCAPE
Network. Not all references to the Unity Network will be changed
immediately; Unity may appear in some places and CARESCAPE
in others. It is important to understand that while the CARESCAPE
Network replaces the Unity Network name, they refer to the same
GE monitoring network.

2000716-005C CARESCAPE Network A-3

Definitions

A-4 CARESCAPE Network 2000716-005C

 B Checkout form

2000716-005C CARESCAPE Network B-1

Checkout form

CARESCAPE Network checkout form

This form should be complete through the installation and verification of
CARESCAPE Network. See Chapter 3.

General information
Site: ________________________________________________________________

Date: _______________________________________________________________

GE Representative: ____________________________________________________

Site Representative: ___________________________________________________

Design phase test results

Documentation and network infrastructure

Numerical Results
Category Test Description Pass/Fail
(if applicable)

Documentation of interconnections
Documentation of closets and equipment
Documentation Documentation of cable runs
Documentation of network device configurations
Documentation of IP addressing
Qualified devices
Access/Distribution switch roles
Redundancy, if applicable on switch
Network infrastructure Limitations are followed
Qualified topology
No more than seven switches in a single path
Qualified configuration

B-2 CARESCAPE Network 2000716-005C

 Checkout form

CARESCAPE Network MC/IX application

Numerical Results
Category Test Description Pass/Fail
(if applicable)

MC devices in one classful network

MC and IX are separate classful networks
MC and IX have private IP addresses, isolated network
exempt
If public IP addresses, proper authorization, isolated network
exempt
Functional group VLANs defined (shared network only)
No more than 1023 devices
CARESCAPE Network
MC/IX application Limit of 48 MC ports per switch
QoS (for shared network only) - use application DSCP
marking when present
QoS (for shared network only)- apply CoS marking, if none
applied, at port closest to source
QoS (for shared network only)- correct priorities
QoS (for shared network only)- default CoS marking is 0
QoS (for shared network only) - consistent CoS to DSCP
mappings

Installation phase test results

Numerical Results
Category Test Description Pass/Fail
(if applicable)

Appropriate cables used

Termination requirements
Cables Cable warning labels
Wall jack warning labels
CARESCAPE Network identification labels
Secure locked closet
Connected to UPS
Backup power supply*
N+1 network equipment*
Network equipment
Environmental requirements
Equipment warning labels
Power cord warning labels
Operating requirements

2000716-005C CARESCAPE Network B-3

Checkout form

Numerical Results
Category Test Description Pass/Fail
(if applicable)

Installed configuration is the same as documentation

Password protection
Network equipment
Banner display*
configuration
Event logging*
Time synchronized*
Equipment interconnection Interconnected as specified
*Recommended

Installed network infrastructure test results

Numerical Results
Category Test Description Pass/Fail
(if applicable)
Roots of switches
Absence of looping and broadcast storm on Administrator network
Data link (Layer 2) Absence of looping and broadcast storm on MC network
Absence of looping and broadcast storm on IX network
Absence of looping and broadcast storm on RX network, if present
IP connectivity on Administrator network
IP connectivity on MC network
IP connectivity on IX network
IP connectivity IP connectivity on RX network, if present
No IP connectivity across different networks
Access control lists
Network services

CARESCAPE Network MC/IX application test results

Numerical Results
Category Test Description Pass/Fail
(if applicable)
Bedside1 can view bedside 2
MC CIC can view both bedsides
Alarms, parameters and waveforms
Full disclosure collection
IX
Full disclosure retrieval or network printing
RX OpenNet Expert tool is able to configure AP

B-4 CARESCAPE Network 2000716-005C

 Checkout form

CARESCAPE Network performance and reliability test results

Numerical Results
Category Test Description Pass/Fail
(applicable)
MC Latency
MC Packet Loss
MC Latency with primary link down
Performance and
RX Latency
reliability
RX Jitter
RX Packet Loss
RX Latency with primary link down

Network management test results

Numerical Results
Category Test Description Pass/Fail
(if applicable)

Network SNMP with authentication*

management Monitoring chassis-based switches and component modules*

*Recommended

All testing and results are subject to the terms and conditions set forth in the
agreement between the parties with respect to these services.

„ Completion of the above tests with passing results confirms that CARESCAPE
Network, as currently configured, is suitable for carrying CARESCAPE Network
traffic.
„ The testing performed, as specified in this document, does not constitute a
guarantee of CARESCAPE Network, the equipment on the network, the network
itself, or the performance of the network. The site understands and agrees that
many factors can affect both the equipment, as well as the performance of the
network.
„ The site understands and agrees that the confirmation is for the CARESCAPE
Network configuration and usage at the time of the test, and does not guarantee
future performance of CARESCAPE Network. Among other things, changes to
the configuration of CARESCAPE Network or additional traffic volume could
negatively impact the performance of CARESCAPE Network, possibly resulting
in lost data.
„ The site understands and agrees that it is responsible for maintaining the
CARESCAPE Network configuration, the equipment on the network and the
network itself.
Signatures

GE representative:_____________________________________________________

Site representative:_____________________________________________________

2000716-005C CARESCAPE Network B-5

Checkout form

B-6 CARESCAPE Network 2000716-005C

 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 Munzinger Straße 3-5 24th Floor, Shanghai MAXDO Center,
Milwaukee, WI 53223 USA D-79111 Freiburg 8 Xing Yi Road, Hong Qiao Development Zone
Tel: + 1 414 355 5000 Germany Shanghai 200336, P.R. China
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, a General Electric Company, going to market as

GE Healthcare.
www.gehealthcare.com