Aisys™ CS² Network Configuration Guide

Software Revision 11
User responsibility
This product will perform in conformity with the description thereof
contained in this User’s Reference manual and accompanying labels
and/or inserts, when assembled, operated, maintained, and repaired
in accordance with the instruction provided.
This product must be checked periodically. A defective product
should not be used. Parts that are broken, missing, plainly worn,
distorted, or contaminated should be replaced immediately. Should
repair or replacement become necessary, the manufacturer
recommends that a telephonic or written request for service advice
be made to the nearest manufacturer Customer Service Center. This
product or any of its parts should not be repaired other than in
accordance with written instructions provided by the manufacturer
and by the manufacturer trained personnel. The product must not be
altered without the prior written approval of the manufacturer. The
user of this product shall have the sole responsibility for any
malfunction which results from improper use, faulty maintenance,
improper repair, damage, or alteration by anyone other than the
manufacturer.
CAUTION U.S. Federal law restricts this device to sale by or on the
order of a licensed medical practitioner. Outside the
U.S.A., check the local laws for any restriction that may
apply.
 Table of Contents

1 Introduction

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Customer/network installer . . . . . . . . . . . . . . . . . . . . . . . 1-3
Manufacturer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Safety statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

2 Network configuration overview

Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Client devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Network communication . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Data output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Network specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Network interface technical specifications . . . . . . . . . . . 2-4
Network interface flow . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

3 HL7 integration

Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Network cable disconnection . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

DOC1949974 i
Aisys™ CS² Network Configuration Guide

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

4 Sapphire integration

Aisys CS2 Sapphire conformance . . . . . . . . . . . . . . . . . . . . 4-2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Sapphire communication . . . . . . . . . . . . . . . . . . . . . . . . .4-4
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

5 Pre-installation Network Checklist

6 Privacy and Security

Privacy and Security Overview . . . . . . . . . . . . . . . . . . . . . . . 6-2

Privacy and Security Environment . . . . . . . . . . . . . . . . . 6-2
Privacy and Security Capabilities . . . . . . . . . . . . . . . . . . . . . 6-3
Access Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3
Privacy and Security Audit Logging and Accountability
Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Information Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Network Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Serial Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Removable Media Security . . . . . . . . . . . . . . . . . . . . . . . 6-6
Data at Rest Security . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7
Data Integrity Capabilities . . . . . . . . . . . . . . . . . . . . . . . . 6-7
De-identification Capabilities . . . . . . . . . . . . . . . . . . . . . . 6-7
Business Continuity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
System Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Malicious Software Protection Customer
Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Antivirus Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

ii DOC1949974
 Table of Contents

System (Product) Change Management . . . . . . . . . . . . . . .6-11

Personal Information Collected/Disclosed by the Product
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Optional Patient Identification Capabilities . . . . . . . . . . 6-12
Additional Privacy and Security Considerations . . . . . . 6-13
Index

DOC1949974 iii
Aisys™ CS² Network Configuration Guide

iv DOC1949974
 1 Introduction

Introduction

In this section Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Responsibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Safety information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

DOC1949974 1-1
Aisys™ CS² Network Configuration Guide

Overview

Intended audience

• Primary - Hospital IT departments and network administrators /

designers.
• Secondary - Biomedical engineers.
• Reference - GE Healthcare field service engineers

Intended use
This network manual is intended for hospital IT departments and
network administrators and designers. Its purpose is to aid the
hospital or hospital assigned entity in the design and configuration of
the Network to which Aisys CS² anesthesia machines and clients are
connected. Use this manual to achieve the GE recommended
network reliability, security, and performance that is required for
connectivity between the anesthesia machine and intended clients.

Ordering manuals
Contact your local GE representative for additional ordering
information.

Revision history
The part number, revision level and date code of this manual are
located on the back cover (lower-right corner) of this manual.
Example:
Part number: 2098870-001
Date code: 08 2016
Revision level: A

1-2 DOC1949974
 1 Introduction

Responsibility

Customer/network installer

• Management of the network traffic, bandwidth, security and

performance to support Aisys CS² anesthesia machine.
• Management of network that ensures bandwidth and
performance required for network connectivity is met.
• Maintenance and troubleshooting of the network.
• Process management to coordinate planned network
maintenance and outages and provision for unplanned outages.
• Design and configure network connectivity for the anesthesia
machine network addressing network related issues.
• In addition to these responsibilities, GE recommends following
the responsibilities outlined in IEC 80001-1:2010 "Application of
risk management for IT-networks incorporating medical devices."

Manufacturer

• Provide installation and troubleshooting of the anesthesia

machine equipment under warranty or extended service
contract.
• Provide guidelines in designing and integrating the anesthesia
machine with a hospital enterprise network, or designing a
segregated anesthesia machine network, addressing the
connectivity needs of the anesthesia machine.
• Provide consultation services during initial configuration and
verification per contract agreement.

DOC1949974 1-3
Aisys™ CS² Network Configuration Guide

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 sections which are
specific to that section's content.
The terms 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.

Warnings

Warning statements identify a potential hazard or unsafe practice

which, if not avoided, could result in death or serious injury.

WARNING Loss of confidentiality: The network communication is not

encrypted. If the patient information is enabled in the
system, then the patient information is transferred to
clients, in plain text format. Enable Patient Information
only if the anesthesia device network is segregated and
secured from unintended disclosures.
WARNING Loss of connectivity: The network design should provide
resources for the anesthesia network clients; bandwidth,
equipment CPU and memory should be available, not
only during normal network activity, but also during
periods of traffic bursts, compromised states of network
and presence of unplanned traffic.
WARNING Loss of connectivity: The anesthesia machine network
should extend only to hospital areas that require
anesthesia machine network traffic. The anesthesia
machine network should be defined only on network
switches that host anesthesia devices or are providing
connectivity to anesthesia devices.
WARNING Loss of connectivity: Do not allow non-anesthesia
network data into the anesthesia device network except
for limited, specific traffic that is required for the operation
of the anesthesia devices and the maintenance of
network equipment.
WARNING Electrical shock: To avoid electric shock, the network
equipment and its accessories should not be placed
within the patient environment, which is volume related to
an object (examples: bed, chair, table, treadmill) where a

1-4 DOC1949974
 1 Introduction

patient is intended to be diagnosed, monitored, or

treated.
WARNING Loss of connectivity: 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 the Anesthesia Device Network.
• Power cords for networking equipment should have
warning labels indicating use for Anesthesia Device
Network.
• Network cables attached to the network equipment
should have warning labels at both ends of the cable
indicating use for Anesthesia Device Network.
• Network cables used to connect anesthesia devices
should be clearly labeled to identify the anesthesia
device network connection and the bed-side device
connection.

WARNING Loss of connectivity: The network should prevent

intended or unintended communication loops by the use
of a Spanning Tree protocol or other equally effective
technology.

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.

Symbols

Symbol Definition
Manufacturer name and address

DOC1949974 1-5
1-6 DOC1949974
 2 Network configuration overview

Network configuration overview

In this section Network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Network specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

DOC1949974 2-1
Aisys™ CS² Network Configuration Guide

Network architecture
The network architecture allows the anesthesia machine to share
hospital network resources. These resources include access
switches, distribution switches, routers, copper cabling and fiber
optic links for hospital-wide connectivity as well as network services
and security servers for unified network management.
The anesthesia machine network should extend only to hospital
areas that require anesthesia machine network traffic. The
anesthesia machine network should be routed to the hospital
network so that data may be sent to the EMR interface. Ensure the
router between the anesthesia machine network and the EMR does
not block any of the flows for Port 2.
This disclosure is intended to satisfy the requirements of
IEC60601-1:2005, clause 14.13 and IEC/ISO 80001-1:2010, clause
3.5 for disclosure of network-related specifications, requirements,
and residual risks in order to facilitate the responsible organization’s
risk management activities (pursuant of 80001-1) for their networks
incorporating Aisys CS² anesthesia machine.

Router EMR
Port 2 OR Network
Hospital Network
(example: GE IX Network)

Port 1

Bedside Device

AC.25.086
Figure 2-1 • Network configuration example

Client devices

Bedside monitors, gateways, and servers are referred to as client

devices to differentiate them from network equipment.

Network communication

If the Aisys CS² anesthesia machine detects excessive CPU or

network utilization, it will close any open connections and shut down
the networking functionality until the anesthesia machine is restarted.

2-2 DOC1949974
 2 Network configuration overview

Network communication

If the Aisys CS² anesthesia machine detects excessive CPU or

network utilization, it will close any open connections and shut down
the networking functionality until the anesthesia machine is restarted.
The network monitoring strategy is heavily weighted towards
protecting the therapy functions of the anesthesia machine. In the
case of a transient issue, the device will favor shutting down
communications over allowing the networking system to continue to
use system resources.
Adherence to the guidelines set out in this manual can help reduce,
but not eliminate, the chance of a communication shutdown.

Data output
The network configuration of the anesthesia machine allows users to
obtain the following information:
Measurements, configurations, and patient and system information

• Ventilation measurements (waveforms, parameters, status)

• Gas and agent measurements (waveforms, parameters, status)
• Alarms and events
• Ventilation, gas, and system configurations

Service information

• Service logs

Network management

• Network configurations
• Request for co-ordinated time

DOC1949974 2-3
Aisys™ CS² Network Configuration Guide

Network specifications

Network interface technical specifications

The Aisys CS² anesthesia machine software version 11 has two
interfaces that connect to the bedside device and the network. See
specifications in the tables below which support the configurations
for these two interfaces. Note: The system is capable of detecting
duplicate IP addresses using ARP, but only if the ARP reply is
directed.

Connection Name Port 1 (connection to bedside

device)
Physical network connection type: IEEE 802.3-1998 10/100 BaseT
Ethernet
Speed and duplex modes supported: 10 Mbps half and full duplex 100
Mbps half and full duplex auto
negotiate.
Default IP address (from factory): None
IP addressing: IPv4 (static)
• Subnet mask is entered
manually.

QoS support: No markings

Connection Name Port 2 (connection to network)

Physical network connection type: IEEE 802.3-1998 10/100 BaseT
Ethernet
Speed and duplex modes supported: 10 Mbps half and full duplex 100
Mbps half and full duplex auto
negotiate.
Default IP address (from factory): None
IP addressing: IPv4 (static and DHCP)
• Subnet mask is entered
manually or configured through
DHCP server.

QoS support: No markings

Network interface flow

Flow Name: Sapphire Communication

Network connection on device: Port 1

2-4 DOC1949974
 2 Network configuration overview

Flow Name: Sapphire Communication

Usage type/function/purpose: Publishing waveforms, parameters,
configurations, alarms, events.
patient demographics, and system
information to client.
Communication partner device/IP Compatible Sapphire client
address/network:
Middle layer protocols: TCP- unicast
Application layer protocol and Sapphire Binary Exchange (SBX) -
encoding: proprietary.
Ports: Remote: User configured
Local: Ephemeral
Encrypted: No
Traffic characterization: Periodic streaming of data to client,
connection initiated from the
anesthesia device.
Bandwidth requirements: ~100 Kbps
Latency max: 250 ms

Flow Name: Sapphire Communication

Network connection on device: Port 2
Usage type/function/purpose: Publishing waveforms, parameters,
configurations, alarms, events.
patient demographics, and system
information to client.
Communication partner device/IP Compatible Sapphire client
address/network:
Middle layer protocols: TCP- unicast
Application layer protocol and Sapphire Binary Exchange (SBX) -
encoding: proprietary.
Ports: Remote: User configured
Local: Ephemeral
Encrypted: No
Traffic characterization: Periodic streaming of data to client,
connection initiated from the
anesthesia device.
Bandwidth requirements: ~100 Kbps per client configured.
Latency max: 250 ms

Flow Name: HL7 Communication

Network connection on device: Port 2
Usage type/function/purpose: Publishing, parameters,
configurations and system
information to client.
Communication partner device/IP Compatible HL7 client
address/network:

DOC1949974 2-5
Aisys™ CS² Network Configuration Guide

Flow Name: HL7 Communication

Middle layer protocols: TCP- unicast
Application layer protocol and HL7
encoding:
Ports: Remote: User configured
Local: Ephemeral
Encrypted: No
Traffic characterization: Periodic streaming of data to client,
connection initiated from the
anesthesia device.
Bandwidth requirements: ~100 Kbps per client configured.
Latency max: 250 ms

Flow Name: Time Server Communication

Network connection on device: Port 2
Usage type/function/purpose: Synchronization of system time with
Time Server.
Communication partner device/IP Timer Server, supporting SNTP.
address/network:
Middle layer protocols: UDP - unicast
Application layer protocol and SNTP
encoding:
Ports: Remote: 123
Local: 123
Encrypted: No
Traffic characterization: Periodic synchronization of time
initiated from anesthesia device.
Bandwidth requirements: 1 Kbps
Latency max: 250 ms

Flow Name: Service Log Transfer

Communication
Network connection on device: Port 2
Usage type/function/purpose: Transferring the service logs to FTP
server.
Communication partner device/IP FTP server, supporting Passive
address/network: Mode.
Middle layer protocols: TCP- unicast
Application layer protocol and FTP
encoding:

2-6 DOC1949974
 2 Network configuration overview

Flow Name: Service Log Transfer

Communication
Ports: Control Communication:
• Remote: 21
• Local: Ephemeral
Data Communication:
• Remote: Range of ports
specified by the FTP server.
• Local: Ephemeral

Encrypted: No
Traffic characterization: Periodic transfer of service logs and
upon user request or system failure
initiated from anesthesia device.
Bandwidth requirements: 1 Kbps
Latency max: 250 ms

Flow Name: Port 2 Dynamic Host

Configuration
Network connection on device: Port 2
Usage type/function/purpose: Network services
Communication partner device/IP Hospital DHCP server, supporting
address/network: host configuration for IP address,
subnet mask, default gateway and
DNS server.
Middle layer protocols: UDP- broadcast, UDP - unicast
Application layer protocol and DHCP
encoding:
Ports: Remote: 67
Local: 68
Encrypted: No
Traffic characterization: Initiated by anesthesia device,
sporadically as required.
Bandwidth requirements: 1 Kbps
Latency max: 250 ms

Flow Name: DNS Name Resolution

Network connection on device: Port 2
Usage type/function/purpose: Network services
Communication partner device/IP Hospital DNS server
address/network:
Middle layer protocols: UDP- unicast
Application layer protocol and DNS
encoding:
Ports: Remote: 53
Local: Ephemeral

DOC1949974 2-7
Aisys™ CS² Network Configuration Guide

Flow Name: DNS Name Resolution

Encrypted: No
Traffic characterization: Initiated by anesthesia device,
sporadically as required.
Bandwidth requirements: 1 Kbps
Latency max: 250 ms

Flow Name: PING

Network connection on device: Port 1 and Port 2
Usage type/function/purpose: Network troubleshooting
Licensed/optional/required: Required
Communication partner device/IP Any device to which the PING
address/network diagnostic may be executed.
Middle layer protocols: ICMP
Application layer protocol and Not applicable
encoding:
Ports: Not applicable
Encrypted: No
Traffic characterization: On demand, user initiated,
unidirectional to remote client.
Latency max: 250 ms

Note: Use the Connectivity Test to check the status of each connected device with a network ping
command. Any device connected to Port 1 and Port 2 must be turned on before starting the test. The
acceptance of Ping commands initiated from external devices to the Aisys CS2 has been disabled for
security purposes.

2-8 DOC1949974
 3 HL7 integration

HL7 integration

In this section Intended use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Network cable disconnection. . . . . . . . . . . . . . . . . . . . . . . . 3-3
Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

DOC1949974 3-1
Aisys™ CS² Network Configuration Guide

Intended use
Anesthesia machines can be configured to send data to external
devices, including Electronic Medical Record systems and other
Hospital Information Systems using the Health Level Seven (HL7)
protocol.
This section is intended to be a technical reference for GE customers
integrating the Aisys CS² anesthesia machine HL7 output with an
external system. It is specifically intended for HL7 integration
engineers who are responsible for configuring hospital information
technology systems to interface together. This document is not
intended to provide background information on the HL7 standard.
For detailed information regarding the HL7 standard, refer to HL7
Version 2.6 or above documentation at "www.hl7.org".

Overview
The HL7 standard defines a high level specification for exchanging
data between healthcare systems. HL7 includes a great deal of
flexibility which can make it very difficult to integrate specific
systems. Integrating systems with HL7 often requires developing
specific integration guidelines before sending and receiving systems
can exchange messages.
The Aisys CS² systems address this issue by conforming to the HL7
message content and communication protocol guidelines as defined
by the IHE PCD-01 Data Enterprise Communication profile. The
Aisys CS² anesthesia machine implements the Device Observation
Reporter (DOR) actor role in a PCD-01 compliant system.
It is assumed that the users of this document have a basic
understanding of the "PCD Technical Framework Volume 2, Revision
5".

3-2 DOC1949974
 3 HL7 integration

Network cable disconnection

If the HL7 cable is disconnected/pulled from the anesthesia system;
the network status for the HL7 will not display immediately. This
disconnection results in a delay of the network to recognize the client
is unavailable.
The delay in realizing that the client is unavailable does not affect the
way HL7 messages are sent. The only impact is that the HL7 client
device connection status is delayed and displayed after the set send
interval.
The network status delay is due to the client socket not closing
properly. When the network cable is removed from the client system
improperly, it causes packets sent from the anesthesia machine to
be lost. The socket can only determine that the client is unavailable
after a minute or two after a packet is sent. For example, if the HL7
message send interval is 5 minutes, the anesthesia machine realizes
the client is unavailable 1 to 2 minutes after the message is sent.
The client disconnection is realized after approximately 6 minutes. If
the HL7 send interval is 15 minutes then the worst case would be
approximately 16-17 minutes.
See "Network communication "in the "Network requirements"
section.

DOC1949974 3-3
Aisys™ CS² Network Configuration Guide

Protocol
Messages are sent using HL7 MLLP (Minimal Lower Layer Protocol)
as identified in the PCD (Patient Care Device) Technical Framework.
Messages are sent over a single persistent TCP/IP connection for
each device. The connection is left open as long as the client
continues to read messages from the network. The Aisys CS²
system will not try to re-send data if the data is not acknowledged by
the receiving system. The protocol does not require the client to send
an acknowledgement, therefore there is no way to check if the client
is HL7.
Connections are initiated by the Aisys CS² anesthesia machine as
configured by the user. Refer to the Aisys CS² Software Revision 11
User’s Reference manual for detailed information. If a connection
cannot be made to an external client, the anesthesia machine may
attempt communication in less than 30 seconds, but could take
longer between connection attempts.
The anesthesia machine monitors the connection to the remote client
to determine if the remote client is operating properly. If the remote
client is not responding, the Aisys CS² system will close the
connection and attempt to reconnect. The amount of time it takes to
detect a failure depends on the type of problem and the frequency
for sending messages set by the user.
Activity is monitored by the anesthesia machine. If the Aisys CS²
system detects excessive CPU or network utilization it will close any
open connections and shut down the networking functionality until
the anesthesia machine is restarted.
The network monitoring strategy uses a very conservative approach
to protect the therapy functions of the anesthesia machine. It is
possible that a temporary issue may shut down communications for
extended periods in order to protect system resources.
Adherence to the configuration guidelines and using validated HL7
clients can help reduce, but not eliminate the chance of a
communication shutdown.

3-4 DOC1949974
 3 HL7 integration

Messages
Aisys CS² anesthesia machine conforms to the message format
defined by the HL7 specification version 2.6 and with additional
guidelines given in the PCD-01 profile.
Nomenclature for the parameters is taken from the Ammended ISO
Nomenclature: IEEE standard 11073-10101a. Observation sub-IDs
use the virtual device numeric codes from IEEE 11073. Units of
measure for the parameters are given using the Unified Code for
Units of Measure.
Messages are always sent with UTF-8 character encoding.
The sending application namespace is GE_ANES_SYS and
universal ID type is EUI-64. GE Healthcare is sent as the sending
facility name.
Times are transmitted in universal coordinated time with a local time
zone offset.
When the message sending frequency is once every 10 seconds or
1 minute, the value sent is the median of the last 10 seconds of
sampled data. If the message sending frequency is lower, the value
sent is the median of the last 60 seconds of sampled data.
Each message contains the following parameters:
.

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_CO2_RESP_RATE 151594 Respiration rate
• RRCO2

MDC_COMPL_LUNG_DYN 151692 Thoracic compliance

• Compliance
• Static compliance

MDC_CONC_AWAY_CO2_ET 151708 End tidal carbon dioxide

• etCO2
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_CO2_INSP 151716 Inspiratory carbon dioxide
• FiCO2
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_DESFL_ET 152084 End tidal desflurane
• etAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_DESFL_ET_SET 16929300 End tidal desflurane
• et DES %
TING concentration (or partial
pressure) in airway gas setting
MDC_CONC_AWAY DESFL_INSP 152168 Inspiratory desflurane
• FIAA
concentration (or partial
pressure) in airway gas

DOC1949974 3-5
Aisys™ CS² Network Configuration Guide

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_CONC_AWAY_ENFL_ET 152088 End tidal enflurane concentration
• etAA
(or partial pressure) in airway
gas
MDC_CONC_AWAY_ENFL_ET_SETTI 16929304 End tidal enflurane concentration
• et ENFL %
NG (or partial pressure) in airway
gas setting
MDC_CONC_AWAY_ENFL_INSP 152172 Inspiratory enflurance
• FiAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_HALOTH_ET 152092 End tidal halothane
• etAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_HALOTH_ET_SE 16929308 End tidal halothane
• et HALOTH %
TTING concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_HALOTH_INSP 152176 Inspiratory halothane
• FiAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_ISOFL_ET 152100 End tidal isoflurane
• etAA
concentration (or partial
pressure) in airway gas.
MDC_CONC_AWAY_ISOFL_ET_SETTI 16929316 End tidal isoflurane
• et ISOFL %
NG concentration (or partial
pressure) in airway gas setting
MDC_CONC_AWAY_ISOFL_INSP 152184 Inspiratory isoflurane
• FiAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_N2O__ET 152108 End tidal nitrous oxide
• etN2O
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_N2O_INSP 152192 Inspiratory nitrous oxide
• FiN2O
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_O2_ET 152440 End tidal oxygen concentration
• etO2
(or partial pressure) in airway
gas
MDC_CONC_AWAY_O2_ET_SETTING 16929656 End tidal oxygen concentration
• Set Target etO2
(or partial pressure) in airway
gas setting
MDC_CONC_AWAY_O2_INSP 152196 Inspiratory oxygen concentration
• FiO2 (MGAS)
(or partial pressure) in airway
• FiO2-etO2
gas

3-6 DOC1949974
 3 HL7 integration

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_CONC_AWAY_SEVOFL_ET 152096 End tidal sevoflurane
• etAA
concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_SEVOFL_ET_SE 16929312 End tidal sevoflurane
• et SEVOFL %
TTING concentration (or partial
pressure) in airway gas
MDC_CONC_AWAY_SEVOFL_INSP 152180 Inspiratory sevoflurane
• FiAA
concentration (or partial
pressure) in airway gas
MDC_CONC_GASDLV_DESFL_INSP_ 16929416 Inspiratory desflurane
• Set FG DES %
SETTING concentration (or partial
pressure) delivery setting
MDC_CONC_GASDLV_ENFL_INSP_ 16929420 Inspiratory enflurane
• Set FG ENFL %
SETTING concentration (or partial
pressure) delivery setting
MDC_CONC_GASDLV_HALOTH_INS 169292424 Inspiratory halothane
• Set FG HALOTH
P_SETTING concentration (or partial
%
pressure) delivery setting
MDC_CONC_GASDLV_SEVOFL_INSP 16929428 Inspiratory sevoflurane
• Set FG SEVOFL
_SETTING concentration (or partial
%
pressure) delivery setting
MDC_CONC_GASDLV_ISOFL_INSP_ 169294232 Inspiratory isoflurane
• Set FG ISOFL %
SETTING concentration (or partial
pressure) delivery setting
MDC_CONC_GASDLV_O2_INSP 153144 Concentration airway oxygen
• Circuit O2
inspiratory (gas delivery system
(internal)
or circuit) setting
MDC_CONC_GASDLV_O2_INSP_SET 16930360 Concentration airway oxygen
• Set FiO2
TING inspiratory (gas delivery system
or circuit) setting
MDC_CONC_MAC_SUM_AGE_CORR 152868 MAC age-corrected sum
• MAC

MDC_FLOW_AIR_FG 152876 Fresh air flow

• Air meas flow
• Air supp pres

MDC_FLOW_CO2_PROD_RESP 151776 CO2 Production

• VCO2

MDC_FLOW_N2O_FG 153092 Fresh gas nitrous oxide flow

• N2O meas flow
• N2O supp pres

MDC_FLOW_O2_CONSUMP 152420 O2 Consumption

• VO2/kg
• VO2/m2

DOC1949974 3-7
Aisys™ CS² Network Configuration Guide

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_FLOW_O2_FG 153156 Fresh gas oxygen flow
• O2 meas flow
• O2 supp pres

MDC_PRESS_AIR_AMBIENT 152836 Ambient pressure

• Ambient pres

MDC_PRESS_AWAY 151792 Airway pressure

• Pmean

MDC_PRESS_AWAY_END_EXP_POS 152788 PEEPe+i

• PEEPe+i
_TOTAL
MDC_PRESS_AWAY_END_EXP_POS 151808 Intrinsic PEEP (Auto PEEP)
• PEEPi
_INTRINSIC
MDC_PRESS_RESP_PLAT_DYNAMIC 152776 Dynamic Plateau Pressure
• Paw source

MDC_PRESS_RESP_PLAT_STATIC 151784 Static Plateau Pressure

• Static Pplat

MDC_QUO_RESP 151828 Respiratory quotient

• RQ

MDC_RATIO _IE 151832 Ratio inspiration expiration time

• I:E (1:xx.xx)

MDC_RATIO _IE_SETTING 16929048 Ratio inspiration expiration time

• Set I:E (1:xxx.x)
setting
MDC_RES_AWAY 151840 Airway resistance
• Raw

MDC_RESP_EXPENDED_ENERGY 152812 Expended energy

• EE

MDC_RESP_RATE 151562 Respiration rate

• RRtotal

MDC_RESP_SPONT_RATE 151666 Spontaneous respiration rate

• RR spont
(legacy devices and systems)
MDC_VENT_RESP_RATE_AVG_SETT 16928805 Spontaneous respiration rate
• Set RR spont
ING (legacy devices and systems)
MDC_TIME_PD_APNEA_SETTING 16929072 Apnea alarm duration setting
• Set apnea delay

MDC_TIME_PD_EXP 152612 Expiratory time

• Exp time

MDC_TIME_PD_INSP 152608 Inspiratory time

• Insp time

MDC_VENT_FLOW_CONTINUOUS 16929872 Ventilation flow setting

• Set FG total flow
_SETTING
MDC_VENT_MODE 184352 Respiration mode
• Set vent mode

3-8 DOC1949974
 3 HL7 integration

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_PRESS_AWAY_MAX 151972 Inspiratory airway pressure
• Pmax

MDC_VENT_PRESS_AWAY_END_EX 16929192 Set PEEP

• Set PEEP
P_POS_SETTING
MDC_PRESS_AWAY_MAX 151793 Maximum ventilation pressure
• Ppeak

MDC_VENT_RESP_RATE 151586 Ventilation rate

• RRtotal

MDC_VENT_RESP_RATE_SETTING 16928802 Set inflation rate

• Set RR

MDC_VENT_TIME_PD_INSP_PAUSE_ 16929844 Maximum inspiratory time setting

• Set Insp Pause %
PERCENT_SETTING
MDC_VENT_VOL_MINUTE_AWAY_IN 152016 Inspiratory minute volume
• MVinsp
SP
MDC_VENT_VOL_TIDAL_SETTING 16929196 Tidal volume setting
• Set TV

MDC_VOL_AWAY_TIDAL_EXP 152664 Expired Tidal Volume

• TVexp

MDC_VOL_DELIV_AIR_CASE 152880 Air delivered during a case

• Air consump case
• Air cyl pres

MDC_VOL_DELIV_DESFL_LIQUID_C 152900 Desflurane liquid delivered

• Des consump
ASE during a case
case
• Des meas flow

MDC_VOL_DELIV_ENFL_LIQUID_CA 152916 Enflurane liquid delivered during

• Enf consump case
SE a case
MDC_VOL_DELIV_HALOTH_LIQUID_ 152932 Halothane liquid delivered during
• Hal consump case
CASE a case
• Hal meas flow

MDC_VOL_DELIV_ISOFL_LIQUID 152948 Isoflurane liquid delivered during

• Iso consump case
_CASE a case
• Iso meas flow

MDC_VOL_DELIV_N2O_CASE 152960 Nitrous oxide gas delivered

• N2O consump
during a case
case

• N2O cyl pres

MDC_VOL_DELIV_O2_CASE 153148 Oxygen gas delivered during a

• O2 consump case
case
• O2 cyl pres

DOC1949974 3-9
Aisys™ CS² Network Configuration Guide

Reference ID Context free Display name Description

code
(OhmedaCom
identifier)
MDC_VOL_DELIV_SEVOFL_LIQUID 152980 Sevoflurane liquid delivered
• Sevo consump
during a case
case

• Sevo meas flow

MDC_VOL_MINUTE_AWAY_EXP 151884 Expired minute volume

• MVexp

MDC_VOL_MINUTE_AWAY_INSP 151888 Inspiratory minute volume

• MVinsp

3-10 DOC1949974
Appendix 1 HL7
MSH|^~\&|GE_ANES_SYS^080019FFFE000000^EUI-64|GE Healthcare|||20160503150814-0600||ORU^R01^ORU_R01|2289C295_7ABC_47CD_8796_286099914FAB|P|2.6|||AL|NE||UNICODE
UTF-8|||IHE_PCD_001^IHE PCD^1.3.6.1.4.1.19376.1.6.1.1.1^ISO
PID|||^^^^PI||^^^^^^U
PV1||U
OBR|1|080019FFFE00000020160503150814^GE_ANES_SYS^080019FFFE000000^EUI-64|080019FFFE00000020160503150814^GE_ANES_SYS^080019FFFE000000^EUI-64|70040^MDC_DEV_SYS
_ANESTH^MDC|||20160503150814-0600
OBX|1|CWE|184352^MDC_VENT_MODE^MDC|1.29.0.26|^vent-mode-spont|{unitless}^{unitless}^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|2|NM|16929196^MDC_VENT_VOL_TIDAL_SETTING^MDC|1.29.0.21||mL^mL^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|3|NM|16928802^MDC_VENT_RESP_RATE_SETTING^MDC|1.29.0.22||{breath}/min^{breath}/min^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|4|NM|16929048^MDC_RATIO_IE_SETTING^MDC|1.29.0.23||{unitless}^{unitless}^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|5|NM|16929856^MDC_RATIO_INSP_SETTING^MDC|1.29.0.42||{unitless}^{unitless}^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|6|NM|16929192^MDC_VENT_PRESS_AWAY_END_EXP_POS_SETTING^MDC|1.29.0.25||cm[H2O]^cm[H2O]^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|7|NM|16929844^MDC_VENT_TIME_PD_INSP_PAUSE_PERCENT_SETTING^MDC|1.29.0.24||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|8|NM|16928882^MDC_RESP_SPONT_RATE_SETTING^MDC|1.29.0.30||{breath}/min^{breath}/min^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|9|NM|16930360^MDC_CONC_GASDLV_O2_INSP_SETTING^MDC|1.29.0.27|100.00|%^%^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|10|NM|16929872^MDC_VENT_FLOW_CONTINUOUS_SETTING^MDC|1.29.0.31|6.00|L/min^L/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|11|NM|16929656^MDC_CONC_AWAY_O2_ET_SETTING^MDC|1.29.0.28||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|12|NM|16929072^MDC_TIME_PD_APNEA_SETTING^MDC|1.29.0.29|30.00|s^s^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|13|NM|16929416^MDC_CONC_GASDLV_DESFL_INSP_SETTING^MDC|1.29.0.32|-1.00|%^%^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|14|NM|16929420^MDC_CONC_GASDLV_ENFL_INSP_SETTING^MDC|1.29.0.33||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|15|NM|16929424^MDC_CONC_GASDLV_HALOTH_INSP_SETTING^MDC|1.29.0.34||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|16|NM|16929428^MDC_CONC_GASDLV_SEVOFL_INSP_SETTING^MDC|1.29.0.36||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|17|NM|16929432^MDC_CONC_GASDLV_ISOFL_INSP_SETTING^MDC|1.29.0.35||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|18|NM|16929300^MDC_CONC_AWAY_DESFL_ET_SETTING^MDC|1.29.0.37||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|19|NM|16929304^MDC_CONC_AWAY_ENFL_ET_SETTING^MDC|1.29.0.38||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|20|NM|16929308^MDC_CONC_AWAY_HALOTH_ET_SETTING^MDC|1.29.0.39||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|21|NM|16929312^MDC_CONC_AWAY_SEVOFL_ET_SETTING^MDC|1.29.0.41||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|22|NM|16929316^MDC_CONC_AWAY_ISOFL_ET_SETTING^MDC|1.29.0.40||%^%^UCUM||OFF|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|23|NM|151793^MDC_PRESS_AWAY_MAX^MDC|1.29.0.1|60.00|cm[H2O]^cm[H2O]^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|24|NM|151972^MDC_VENT_PRESS_AWAY^MDC|1.29.0.2||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|25|NM|152016^MDC_VENT_VOL_MINUTE_AWAY_INSP^MDC|1.29.0.3|14.30|L/min^L/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|26|NM|152664^MDC_VOL_AWAY_TIDAL_EXP^MDC|1.29.0.5|600.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|27|NM|153144^MDC_CONC_GASDLV_O2_INSP^MDC|1.29.0.4|60.00|%^%^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|28|NM|151586^MDC_VENT_RESP_RATE^MDC|1.29.0.6|60.00|{breath}/min^{breath}/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|29|NM|151666^MDC_RESP_SPONT_RATE^MDC|1.29.0.7|60.00|{breath}/min^{breath}/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|30|NM|152776^MDC_PRESS_RESP_PLAT_DYNAMIC^MDC|1.20.0.2||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|31|NM|151792^MDC_PRESS_AWAY^MDC|1.20.0.1||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|32|NM|151804^MDC_PRESS_AWAY_END_EXP_POS^MDC|1.20.0.12||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|33|NM|151808^MDC_PRESS_AWAY_END_EXP_POS_INTRINSIC^MDC|1.20.0.11||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|34|NM|151692^MDC_COMPL_LUNG_DYN^MDC|1.20.0.10||mL/cm[H2O]^mL/cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|35|NM|152664^MDC_VOL_AWAY_TIDAL_EXP^MDC|1.20.0.6||mL^mL^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|36|NM|151888^MDC_VOL_MINUTE_AWAY_INSP^MDC|1.20.0.3||L/min^L/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|37|NM|151884^MDC_VOL_MINUTE_AWAY_EXP^MDC|1.20.0.5||L/min^L/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|38|NM|151840^MDC_RES_AWAY^MDC|1.20.0.9||cm[H2O]/(L/s)^cm[H2O]/(L/s)^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|39|NM|151784^MDC_PRESS_RESP_PLAT_STATIC^MDC|1.20.0.4||cm[H2O]^cm[H2O]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|40|NM|151562^MDC_RESP_RATE^MDC|1.20.0.7||{breath}/min^{breath}/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|41|NM|151832^MDC_RATIO_IE^MDC|1.20.0.14||{unitless}^{unitless}^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|42|NM|152608^MDC_TIME_PD_INSP^MDC|1.20.0.15||s^s^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|43|NM|152612^MDC_TIME_PD_EXP^MDC|1.20.0.16||s^s^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|44|NM|152836^MDC_PRESS_AIR_AMBIENT^MDC|1.20.0.13||mm[Hg]^mm[Hg]^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS

DOC1949974 3-11
OBX|45|NM|152420^MDC_FLOW_O2_CONSUMP^MDC|1.20.0.18||mL/min^mL/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|46|NM|151776^MDC_FLOW_CO2_PROD_RESP^MDC|1.20.0.19||mL/min^mL/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|47|NM|152812^MDC_RESP_EXPENDED_ENERGY^MDC|1.20.0.24||kcal/d^kcal/d^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|48|NM|151828^MDC_QUO_RESP^MDC|1.20.0.25||{unitless}^{unitless}^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|49|NM|151594^MDC_CO2_RESP_RATE^MDC|1.20.0.17||{breath}/min^{breath}/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|50|NM|152196^MDC_CONC_AWAY_O2_INSP^MDC|1.20.0.20||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|51|NM|152440^MDC_CONC_AWAY_O2_ET^MDC|1.20.0.22||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|52|NM|152192^MDC_CONC_AWAY_N2O_INSP^MDC|1.30.0.1||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|53|NM|152108^MDC_CONC_AWAY_N2O_ET^MDC|1.30.0.2||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|54|NM|151716^MDC_CONC_AWAY_CO2_INSP^MDC|1.20.0.21||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|55|NM|151708^MDC_CONC_AWAY_CO2_ET^MDC|1.20.0.23||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|56|NM|152168^MDC_CONC_AWAY_DESFL_INSP^MDC|1.30.0.3||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|57|NM|152084^MDC_CONC_AWAY_DESFL_ET^MDC|1.30.0.8||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|58|NM|152172^MDC_CONC_AWAY_ENFL_INSP^MDC|1.30.0.4||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|59|NM|152088^MDC_CONC_AWAY_ENFL_ET^MDC|1.30.0.9||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|60|NM|152176^MDC_CONC_AWAY_HALOTH_INSP^MDC|1.30.0.5||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|61|NM|152092^MDC_CONC_AWAY_HALOTH_ET^MDC|1.30.0.10||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|62|NM|152180^MDC_CONC_AWAY_SEVOFL_INSP^MDC|1.30.0.6||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|63|NM|152096^MDC_CONC_AWAY_SEVOFL_ET^MDC|1.30.0.11||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|64|NM|152184^MDC_CONC_AWAY_ISOFL_INSP^MDC|1.30.0.7||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|65|NM|152100^MDC_CONC_AWAY_ISOFL_ET^MDC|1.30.0.12||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|66|NM|152168^MDC_CONC_AWAY_DESFL_INSP^MDC|1.30.0.3||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|67|NM|152084^MDC_CONC_AWAY_DESFL_ET^MDC|1.30.0.8||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|68|NM|152172^MDC_CONC_AWAY_ENFL_INSP^MDC|1.30.0.4||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|69|NM|152088^MDC_CONC_AWAY_ENFL_ET^MDC|1.30.0.9||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|70|NM|152176^MDC_CONC_AWAY_HALOTH_INSP^MDC|1.30.0.5||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|71|NM|152092^MDC_CONC_AWAY_HALOTH_ET^MDC|1.30.0.10||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|72|NM|152180^MDC_CONC_AWAY_SEVOFL_INSP^MDC|1.30.0.6||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|73|NM|152096^MDC_CONC_AWAY_SEVOFL_ET^MDC|1.30.0.11||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|74|NM|152184^MDC_CONC_AWAY_ISOFL_INSP^MDC|1.30.0.7||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|75|NM|152100^MDC_CONC_AWAY_ISOFL_ET^MDC|1.30.0.12||%^%^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|76|NM|152864^MDC_CONC_MAC_SUM^MDC|1.10.0.1||{unitless}^{unitless}^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|77|NM|153156^MDC_FLOW_O2_FG^MDC|1.10.0.10|2.40|L/min^L/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|78|NM|152876^MDC_FLOW_AIR_FG^MDC|1.10.0.11|2.90|L/min^L/min^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|79|NM|153092^MDC_FLOW_N2O_FG^MDC|1.10.0.12||L/min^L/min^UCUM||NAV|||X|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|80|NM|153148^MDC_VOL_DELIV_O2_CASE^MDC|1.10.0.2|22.92|L^L^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|81|NM|152880^MDC_VOL_DELIV_AIR_CASE^MDC|1.10.0.4|0.00|L^L^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|82|NM|152960^MDC_VOL_DELIV_N2O_CASE^MDC|1.10.0.3|0.00|L^L^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|83|NM|152900^MDC_VOL_DELIV_DESFL_LIQUID_CASE^MDC|1.10.0.5|0.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|84|NM|152932^MDC_VOL_DELIV_HALOTH_LIQUID_CASE^MDC|1.10.0.8|0.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|85|NM|152948^MDC_VOL_DELIV_ISOFL_LIQUID_CASE^MDC|1.10.0.7|0.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|86|NM|152916^MDC_VOL_DELIV_ENFL_LIQUID_CASE^MDC|1.10.0.6|0.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS
OBX|87|NM|152980^MDC_VOL_DELIV_SEVOFL_LIQUID_CASE^MDC|1.10.0.9|0.00|mL^mL^UCUM|||||F|||20160503150814-0600||||080019FFFE000000^GE_ANES_SYS

DOC1949974 3-12
 4 Sapphire integration

Sapphire integration

In this section Aisys CS2 Sapphire conformance. . . . . . . . . . . . . . . . . . . . 4-2

Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

DOC1949974 4-1
Aisys™ CS² Network Configuration Guide

Aisys CS2 Sapphire conformance

Introduction

An Aisys CS² anesthesia machine with System Software 11 or

greater complies with the Sapphire Binary Exchange protocol (SBX)
also known as Sapphire communications protocol (both terms are
used interchangeably in this documentation). SBX is the binary
representation of the Sapphire protocol as it is transmitted between
systems.
A compliant anesthesia machine uses Sapphire to send data to
remote systems using a push model. The anesthesia machine
controls the transfer of data by sending a data transfer request to a
remote peer when it connects.

Protocol

A compliant anesthesia machine conforms to Sapphire protocol

version 3.3.

Profile

A compliant anesthesia machine conforms to the Sapphire Binary

TCP Profile defined in the “Binary TCP Profile” section of the
Sapphire Interface User's Reference Manual.

Interactions

The table below summarizes the anesthesia machine's support for

Sapphire interactions as defined in detail in the “Message
Interaction” section of the Sapphire Interface User's Reference
Manual. The anesthesia machine primarily supports interactions
needed to push data. The table lists the interaction, the type of
support provided, and any special constraints.
The support for an interaction is given as one of four types:

• None - does not generate requests or responses. Messages of

these types are ignored.
• Response - the implementation can generate a response as a
result of a request.
• Request - the implementation can initiate an interaction with a
request and process the response.

4-2 DOC1949974
 4 Sapphire integration

• Both - the implementation can generate requests and process

received requests.

Interaction Support Special constraints

Get Descriptor Both
Put Descriptor Both
Hello Request
Get System None
Information
Put System Request
Information
Get Patient None
Information
Put Patient Both
Information
Sub Stream None
Pub Stream Request Requires select element to be one of:
cfg, evt, num, or wav.
End Stream Response
Keep Alive Both
Get Time Response

Data model

A compliant anesthesia machine produces a limited set of patient

information data from the set given in the Sapphire Interface User's
Reference Manual:

• name/given
• name/family
• identifier/type
• identifier/id
• identifier/authority
• gender
• visit/assignedLocation/bedName
• visit/patientData/patientAge
• visit/patientData/initialHeight
• visit/patientData/initialBodySurfaceArea
• visit/patientData/initialIdealBodyWeight

The anesthesia machine may receive any data, but only processes a
small subset needed to support anesthesia machine operation.
The anesthesia machine supports a subset of the parameters given
in the Sapphire Interface User's Reference Manual. The specific

DOC1949974 4-3
Aisys™ CS² Network Configuration Guide

parameters supported by the anesthesia machine are given in the

XML Message Definitions in Appendices 1 through 4.

Sapphire communication

Connections are initiated by the anesthesia machine as configured

by the user. Refer to the Aisys CS² (Software Revision 11) User’s
Reference Manual for details. If a connection cannot be made to a
system, the anesthesia machine may retry in as little as 30 seconds,
but may take longer between connection attempts depending on the
state of the anesthesia machine and the networking subsystem.
The anesthesia machine monitors the connection to determine if the
remote peer is operating properly. If the anesthesia machine
receives a NAK, an incompatible SBX version, or does not receive
from the remote peer a response to the initial connection within 5
minutes, it closes the connection and will not attempt to re-establish
the communication until the anesthesia machine is restarted.
If the anesthesia machine detects a communication error during a
normal data transfer, it will close the connection and attempt to
reconnect. If the remote peer and network are operating as
expected, reconnection should occur within 30 seconds; but if the
remote peer is unreachable on the first attempt, recovery could take
longer.
See "Network communication" in the "Network configuration" section.
Refer to "Open Interface Commitment" for additional SBX (Sapphire
Binary Exchange) information. http://www3.gehealthcare.com/en/
products/categories/anesthesia_delivery

4-4 DOC1949974
Appendix 1 Configuration Settings
<params>
<gasDeliv>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<cfg>
<gasControlMode BT="xs:unsignedByte" enum="0=unspecified, 1=freshGas, 2=e
mergencyAir, 3=O2ByPass, 4=expiredGas, 5=monitoringOnly"/>
<ecoFlow>
<fiO2Guard BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</ecoFlow>
<respGas card="0,10">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=Air,2=Ar,3=Balance,4=CO2,5=He,6=HeO2,7=N2,8=N2O,9=O2"/>
<freshGasConc BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<endTidalConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</respGas>
<aaGas card="0,6">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=DES, 2=ENF, 3=HAL, 4=ISO, 5=SEV, 6=None"/>
<freshGasConc BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<endTidalConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</aaGas>
<totalGas>
<freshGasFlow BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
<freshGasFlowMin BT="xs:float" inv="NaN, -Inf=na" U="L/min" min="300"
/>
</totalGas>
<driveGas BT="xs:unsignedByte" enum="0=Unspecified, 1=Air, 2=O2"/>
</cfg>
</gasDeliv>
<gasMon>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<cfg>
<numLimit>
<respGas card="0,10">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecif
ied,1=Air,2=Ar,3=Balance,4=CO2,5=He,6=HeO2,7=N2,8=N2O,9=O2"/>
<fractionalInspiredConc>
<high BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<low BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
</fractionalInspiredConc>
<endTidalConc>
<high BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<low BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
</endTidalConc>
</respGas>
<aaGas card="0,10">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecif
ied, 1=DES, 2=ENF, 3=HAL, 4=ISO, 5=SEV"/>
<fractionalInspiredConc>

2098870-001 4-5
 <high BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<low BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
</fractionalInspiredConc>
<endTidalConc>
<high BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
<low BT="xs:float" inv="NaN, -Inf=na, -1.0=Off" U="%"/>
</endTidalConc>
</aaGas>
<macSumAgeCorrected>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="{unitless}"/>
<low BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="{unitless}"/>
</macSumAgeCorrected>
</numLimit>
</cfg>
</gasMon>
<resp>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<cfg>
<balanceGas BT="xs:unsignedByte" enum="0=unspecified, 1=air, 2=N2O"/>
<systemState BT="xs:unsignedByte" enum="0=Unspecified, 1=Off, 2=POST, 3=C
heckout, 4=StartCase, 5=General, 6=CalibrationProcedure, 7=CalibrationNoProcedure, 8=
Therapy, 9=SuperUser, 10=Service, 11=SoftwareUpdate, 12=Failed, 13=StandByShutdown, 1
4=StandBy, 15=MonitoringOnly"/>
<tidalVolume BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
<respRate BT="xs:float" inv="NaN, -Inf=na" U="/min"/>
<mechRespRate BT="xs:float" inv="NaN, -Inf=na" U="/min"/>
<cardiacBypassMode BT="xs:unsignedByte" enum="0=Unspecified, 1=Off, 2=Pas
sive, 3=VCV"/>
<ventMode>
<type BT="xs:unsignedByte" card="1" enum="0=Unspecified, 1=CMV, 2=IMV
, 3=CSV"/>
<support BT="xs:unsignedByte" card="1" enum="0=Unspecified, 1=Pressur
e, 2=Volume"/>
<option BT="xs:unsignedByte" card="0,3" enum="0=Unspecified, 1=Assist
ed, 2=Supported, 3=VolumeTargeted"/>
</ventMode>
<IERatio>
<IERatioInsp BT="xs:float" inv="NaN, -Inf=na" U="{unitless}"/>
<IERatioExp BT="xs:float" inv="NaN, -Inf=na" U="{unitless}"/>
</IERatio>
<inspiratoryTime BT="xs:float" inv="NaN, -Inf=na" U="s"/>
<time>
<high BT="xs:float" inv="NaN, -Inf=na" U="ms"/>
<low BT="xs:float" inv="NaN, -Inf=na" U="ms"/>
</time>
<pause>
<inspiratoryTime BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</pause>
<circuit>
<type BT="xs:unsignedByte" enum="0=Unspecified, 1=circle, 2=nonCircle
ACGO, 3=nonCircleSCGO"/>
</circuit>
<flowSensorType BT="xs:unsignedByte" enum="0=unspecified, 1=delite, 2=ped

4-6 2098870-001
ilite, 3=internal"/>
<patientType BT="xs:unsignedByte" enum="0=unspecified, 1=adult, 2=pediatr
ic"/>
<inspiredPressure BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<supportPressure BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<PEEP BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<biasFlow BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
<riseRate BT="xs:unsignedByte" enum="0=unspecified, 1=1, 2=2, 3=3, 4=4, 5
=5, 6=6, 7=7, 8=8, 9=9, 10=10, 11=auto"/>
<PSV>
<riseTime BT="xs:float" inv="NaN, -Inf=na" U="ms"/>
<riseRate BT="xs:unsignedByte" enum="0=unspecified, 1=1, 2=2, 3=3, 4=
4, 5=5, 6=6, 7=7, 8=8, 9=9, 10=10, 11=auto"/>
</PSV>
<trigger>
<flow BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
<pressure BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<window BT="xs:float" inv="NaN, -Inf=na" U="%{breath period}"/>
</trigger>
<endInspiratoryCycle>
<flow BT="xs:float" inv="NaN, -Inf=na" U="%{peak inspiratory flow}"/>
</endInspiratoryCycle>
<supportBackupDelayTime BT="xs:float" inv="NaN, -Inf=na" U="s"/>
<numLimit>
<airwayPressure>
<low BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="s"/>
</airwayPressure>
<apneaDelayTime>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="s"/>
</apneaDelayTime>
<expiredMinuteVolume>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="L/min"/>
<low BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="L/min"/>
</expiredMinuteVolume>
<expiredTidalVolume>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="mL"/>
<low BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="mL"/>
</expiredTidalVolume>
<pressure>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="cm[H2O]"/>
</pressure>
<respRate>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="/min"/>
<low BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="/min"/>
</respRate>
<peakPressure>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="cm[H2O]"/>
</peakPressure>
<circuitLeak>
<high BT="xs:float" inv="NaN, -Inf=na, 0.0=Off" U="L/min"/>
</circuitLeak>
</numLimit>
</cfg>
</resp>
<system>

2098870-001 4-7
 <source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<cfg>
<language BT="xs:unsignedByte" enum="0=Unspecified, 1=English, 2=French,
3=German, 4=Spanish, 5=Italian, 6=Japanese, 7=Portuguese, 8=Dutch, 9=Chinese, 10=Fin
nish, 11=Norwegian, 12=Danish, 13=Polish, 14=Greek, 15=Czech, 16=Turkish, 17=Russian,
18=Swedish, 19=Hungarian"/>
<alarmVolume BT="xs:unsignedByte" U="%" S="10"/>
<altitude BT="xs:short" inv="-32768" U="m"/>
<configuration BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=Clinica
l, 2=Bench"/>
<ge_anesthesiaDevice>
<display>
<CO2>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=%,
2=kPa, 3=mm[Hg]"/>
</CO2>
<altitude>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=ft,
2=m"/>
</altitude>
<flow>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=L/m
in, 2=L/s, 3=mL/s"/>
</flow>
<gasSupply>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=psi
, 2=kPa, 3=bar"/>
</gasSupply>
<height>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=in,
2=cm"/>
</height>
<pressure>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=mba
r, 2=cm[H2O], 3=kPa, 4=hPa, 5=mm[Hg]"/>
</pressure>
<weight>
<units BT="xs:byte" U="{unitless}" enum="0=Unspecified, 1=lb,
2=kg"/>
</weight>
<spirometry>
<dataSource BT="xs:unsignedByte" enum="0=unspecified, 1=Vent,
2=ge_MGas"/>
</spirometry>
</display>
</ge_anesthesiaDevice>
</cfg>
</system>
</params>

4-8 2098870-001
Appendix 2 Events
<types card="0">
<baseEvt typeid="baseEvt">
<evtSN BT="xs:unsignedInt" inv="0" card="1"/>
<transitionSN BT="xs:unsignedByte" inv="0" card="1"/>
<transitionType BT="xs:unsignedByte" card="1" enum="0=unknown, 1=start, 2=upd
ate, 3=end, 4=tpoint, 5=continue, 6=reset"/>
<dttm BT="xb:NTP-64" inv="0" card="1"/>
<evtType BT="xs:unsignedByte" card="1" enum="0=unknown, 1=limitLow, 2=limitHi
gh, 3=rhythm, 4=technical, 5=measurement"/>
</baseEvt>
<alarmEvt typeref="baseEvt" typeid="alarmEvt">
<sysAlmInactState BT="xs:unsignedByte" card="1" enum="0=unknown, 1=enabled, 2
=audioPaused, 3=audioOff, 4=alarmPaused, 5=alarmOff"/>
<almInactState BT="xs:unsignedByte" card="1" enum="0=unknown, 1=enabled, 2=au
dioPaused, 3=audioOff, 4=alarmPaused, 5=alarmOff"/>
<alState BT="xs:unsignedByte" card="1" enum="0=unknown, 1=inactive, 2=active,
3=latched, 4=off"/>
<priority BT="xs:unsignedByte" card="1" enum="0=unknown, 1=high, 2=medium, 3=
low, 4=none, 5=notInAlarm, 6=info, 7=notAssigned"/>
<physioTech BT="xs:unsignedByte" card="1" enum="0=unknown, 1=physiological, 2
=technical, 3=technicalPhysiological"/>
<audioPriority BT="xs:unsignedByte" enum="0=unknown, 1=high, 2=medium, 3=low,
4=none, 5=notInAlarm, 6=info, 7=notAssigned"/>
<audioPhysioTech BT="xs:unsignedByte" enum="0=unknown, 1=physiological, 2=tec
hnical, 3=technicalPhysiological"/>
</alarmEvt>
<respAlarm typeref="alarmEvt" typeid="respAlarm">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,1=Air,2=
Ar,3=Balance,4=CO2,5=He,6=HeO2,7=N2,8=N2O,9=O2"/>
</respAlarm>
<aaAlarm typeref="alarmEvt" typeid="aaAlarm">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified, 1=DES,
2=ENF, 3=HAL, 4=ISO, 5=SEV"/>
</aaAlarm>
<deviceTestAlarm typeref="alarmEvt" typeid="deviceTestAlarm">
<result BT="xs:unsignedByte" card="1" enum="0=unspecified, 1=pass, 2=fail"/>
</deviceTestAlarm>
<respCylinderAlarm typeref="respAlarm" typeid="respCylinderAlarm">
<index BT="xs:unsignedByte" card="1" isattr="true"/>
</respCylinderAlarm>
</types>
<params>
<gasDeliv>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<evt>
<tech>
<agentLevelLost typeref="alarmEvt"/>
<airOnly typeref="alarmEvt"/>
<airPipeInvalid typeref="alarmEvt"/>
<alternateO2 typeref="alarmEvt"/>
<cassettePressureError typeref="alarmEvt"/>

2098870-001 4-9
 <expiredGasControlExited typeref="alarmEvt"/>
<expiredGasControlSampleLineLeak typeref="alarmEvt"/>
<expiredGasControlSuspended typeref="alarmEvt"/>
<highEtO2Egc typeref="alarmEvt"/>
<inflowOutflowCrossCheckFailRecoverable typeref="alarmEvt"/>
<lowSupplyPressureAir typeref="alarmEvt"/>
<lowSupplyPressureN2O typeref="alarmEvt"/>
<lowSupplyPressureO2 typeref="alarmEvt"/>
<manifoldOverTemp typeref="alarmEvt"/>
<mixerRamFail typeref="alarmEvt"/>
<noVaporizorCassette typeref="alarmEvt"/>
<o2CellCalibrationError typeref="alarmEvt"/>
<o2PipeInvalid typeref="alarmEvt"/>
<outflowLimitReached typeref="alarmEvt"/>
<replaceO2Cell typeref="alarmEvt"/>
<vaporizorCassetteFailure typeref="alarmEvt"/>
<vaporizorCassetteLevelLow typeref="alarmEvt"/>
<vaporizorFailure typeref="alarmEvt"/>
</tech>
<numLimit>
<circuitO2 typeref="alarmEvt" card="0,8"/>
</numLimit>
<measure>
<agentDeliveryTest typeref="deviceTestAlarm"/>
<mixerTest typeref="deviceTestAlarm"/>
</measure>
</evt>
</gasDeliv>
<gasMon>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<evt>
<tech>
<co2MonitoringNotConnected typeref="alarmEvt"/>
<aaMonitoringNotConnected typeref="alarmEvt"/>
<o2SensorFailure typeref="alarmEvt"/>
<mGasSensorInop typeref="alarmEvt"/>
<mGasAneWarmingUp typeref="alarmEvt"/>
<mGasWarmingUp typeref="alarmEvt"/>
<mGasFailure typeref="alarmEvt"/>
<mGasOutletOccluded typeref="alarmEvt"/>
<mGasFilterBlocked typeref="alarmEvt"/>
<mGasSampleLineBlocked typeref="alarmEvt"/>
<mGasNoSampleLine typeref="alarmEvt"/>
<moduleNotCompatible typeref="alarmEvt"/>
<mGasSampleFlowDeviation typeref="alarmEvt"/>
<gasZeroing typeref="alarmEvt"/>
<spirometryZeroing typeref="alarmEvt"/>
<gasZeroError typeref="alarmEvt"/>
<spirometryZeroError typeref="alarmEvt"/>
</tech>
<numLimit>
<respGas>
<fractionalInspiredConc typeref="respAlarm" card="0,8"/>

4-10 2098870-001
 <endTidalConc typeref="respAlarm" card="0,8"/>
</respGas>
<aaGas>
<fractionalInspiredConc typeref="aaAlarm" card="0,8"/>
<endTidalConc typeref="aaAlarm" card="0,8"/>
</aaGas>
<agentMixture>
<lowerThanMAC typeref="alarmEvt" card="0,8"/>
<greaterThanEqMAC typeref="alarmEvt" card="0,8"/>
</agentMixture>
<macSumAgeCorrected typeref="alarmEvt" card="0,8"/>
</numLimit>
<CO2Apnea typeref="alarmEvt" card="0,8"/>
<mGasAPNEA typeref="alarmEvt" card="0,8"/>
</evt>
</gasMon>
<resp>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<evt>
<tech>
<apneaDetectOn typeref="alarmEvt"/>
<auxOutletFail typeref="alarmEvt"/>
<backupVentilationMode typeref="alarmEvt"/>
<bagVentSwitchWrongPosition typeref="alarmEvt"/>
<bellowsEmpty typeref="alarmEvt"/>
<breathingSystemNotLatched typeref="alarmEvt"/>
<checkFlowSensors typeref="alarmEvt"/>
<controlSettingsFailure typeref="alarmEvt"/>
<deliveredVolumeMismatch typeref="alarmEvt"/>
<driveGasLost typeref="alarmEvt"/>
<expFlowSensorNotConnected typeref="alarmEvt"/>
<expFlowWithNonCircle typeref="alarmEvt"/>
<fanFailure typeref="alarmEvt"/>
<fiveVoltHourAmpsGasSupplyTransducers typeref="alarmEvt"/>
<flowSensorCalDataCorrupt typeref="alarmEvt"/>
<gasInletValve typeref="alarmEvt"/>
<inspFlowSensorNotConnected typeref="alarmEvt"/>
<inspirationStopped typeref="alarmEvt"/>
<mechanicalVentDisabled typeref="alarmEvt"/>
<mechanicalVentilationOn typeref="alarmEvt"/>
<mixerFailure typeref="alarmEvt"/>
<noPressureControlPeep typeref="alarmEvt"/>
<nonCircleSelected typeref="alarmEvt"/>
<o2FlushFailure typeref="alarmEvt"/>
<o2SensorNotConnected typeref="alarmEvt"/>
<onStandbySwitchToStandby typeref="alarmEvt"/>
<patientCircuitLeak typeref="alarmEvt"/>
<patientCircuitLeakSilenced typeref="alarmEvt"/>
<patientDisconnected typeref="alarmEvt"/>
<patientVolumeMismatchOccurred typeref="alarmEvt"/>
<peepPcvNotAvailable typeref="alarmEvt"/>
<powerControllerDcFail typeref="alarmEvt"/>
<powerSupply75C typeref="alarmEvt"/>

2098870-001 4-11
 <powerSupplyFailure typeref="alarmEvt"/>
<reverseExpiratoryFlow typeref="alarmEvt"/>
<serviceCalibrationsDue typeref="alarmEvt"/>
<standbyPatientDetected typeref="alarmEvt"/>
<standbyPatientDetectionMOMode typeref="alarmEvt"/>
<subAtmosphericAirwayPressure typeref="alarmEvt"/>
<sustainedAirwayPressure typeref="alarmEvt"/>
<therapyComputerFailure typeref="alarmEvt"/>
<twelveVoltHourAmpsMgas typeref="alarmEvt"/>
<twelveVoltHourAmpsVentSiBoard typeref="alarmEvt"/>
<ventFailure typeref="alarmEvt"/>
<verifyLowVeLimit typeref="alarmEvt"/>
<volumeCompensationLocked typeref="alarmEvt"/>
<vteGreaterThanInspVte typeref="alarmEvt"/>
</tech>
<numLimit>
<airwayPressure typeref="alarmEvt" card="0,8"/>
<peakPressure typeref="alarmEvt" card="0,8"/>
<respRate typeref="alarmEvt" card="0,8"/>
<expiredTidalVolume typeref="alarmEvt" card="0,8"/>
<expiredMinuteVolume typeref="alarmEvt" card="0,8"/>
</numLimit>
<measure>
<complianceTest typeref="deviceTestAlarm"/>
<ventTest typeref="deviceTestAlarm"/>
</measure>
<expFlowWithNonCircle typeref="alarmEvt" card="0,8"/>
<pLimitReached typeref="alarmEvt"/>
<pressureSupplyAdjustMVAlarmLimit typeref="alarmEvt" card="0,8"/>
<reverseInspiratoryFlow typeref="alarmEvt" card="0,8"/>
<tidalVolumeNotAchieved typeref="alarmEvt" card="0,8"/>
<volumeApnea typeref="alarmEvt" card="0,8"/>
<volumeApneaMoreThanTwoMin typeref="alarmEvt" card="0,8"/>
<ge_anesthesiaDevice>
<systemApnea typeref="alarmEvt" card="0,8"/>
</ge_anesthesiaDevice>
</evt>
</resp>
<system>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<evt>
<tech>
<batteryChargeFailure typeref="alarmEvt"/>
<batteryFailure typeref="alarmEvt"/>
<caseFanSpeedFail typeref="alarmEvt"/>
<co2Absorber typeref="alarmEvt"/>
<cpuFanSpeedFail typeref="alarmEvt"/>
<cpuOverheat typeref="alarmEvt"/>
<lowBattery typeref="alarmEvt"/>
<lowBatteryCharge typeref="alarmEvt"/>
<noBattery typeref="alarmEvt"/>
<onBattery typeref="alarmEvt"/>
<screenLocked typeref="alarmEvt"/>
<standbySwitchToStandby typeref="alarmEvt"/>

4-12 2098870-001
 <touchscreenFail typeref="alarmEvt"/>
</tech>
<ge_anesthesiaDevice>
<tech>
<aaCassetteToContinueEgc typeref="alarmEvt"/>
<acb4_096VoltAdcRef typeref="alarmEvt"/>
<acbAdcFail typeref="alarmEvt"/>
<acbClockSpeed typeref="alarmEvt"/>
<acbComFailure typeref="alarmEvt"/>
<acbDcbComFailure typeref="alarmEvt"/>
<acbProcedureComFail typeref="alarmEvt"/>
<acbSoftwareError typeref="alarmEvt"/>
<acbUnexpectedReset typeref="alarmEvt"/>
<airPressLowDuring21PercentO2 typeref="alarmEvt"/>
<bagVentSwitchWrongAcgo typeref="alarmEvt"/>
<bagVentSwitchWrongPosition typeref="alarmEvt"/>
<batteryReversedConnections typeref="alarmEvt"/>
<cardiacBypass typeref="alarmEvt"/>
<carrierBoardOverheat typeref="alarmEvt"/>
<cycling typeref="alarmEvt"/>
<cyclingAborted typeref="alarmEvt"/>
<dcbProcedureComFail typeref="alarmEvt"/>
<displayComputerRestarted typeref="alarmEvt"/>
<eepromFailure typeref="alarmEvt"/>
<flowPaused typeref="alarmEvt"/>
<monitoringOnly typeref="alarmEvt"/>
<passwordReset typeref="alarmEvt"/>
<pleaseDoCheckout typeref="alarmEvt"/>
<powerControllerComFail typeref="alarmEvt"/>
<standbyPatientDetection typeref="alarmEvt"/>
<systemPowerCycleOverdue typeref="alarmEvt"/>
<twelveHourTest typeref="alarmEvt"/>
<twelveVoltsToAcb typeref="alarmEvt"/>
<vitalCapacity typeref="alarmEvt"/>
</tech>
<measure>
<quickCheckTest typeref="deviceTestAlarm"/>
</measure>
</ge_anesthesiaDevice>
</evt>
</system>
</params>

2098870-001 4-13
Appendix 3 Numerical Measurements
<params>
<gasDeliv>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<num>
<respGas card="0,9">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=Air,2=Ar,3=Balance,4=CO2,5=He,6=HeO2,7=N2,8=N2O,9=O2"/>
<flow BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
<caseConsumption BT="xs:float" inv="NaN, -Inf=na" U="L"/>
<totalConsumption BT="xs:float" inv="NaN, -Inf=na" U="L"/>
<pipelinePressure BT="xs:float" inv="NaN, -Inf=na" U="kPa"/>
<cylinder card="0,2">
<index BT="xs:unsignedByte" card="1" isattr="true"/>
<pressure BT="xs:float" inv="NaN, -Inf=na" U="kPa"/>
</cylinder>
</respGas>
<aaGas card="0,5">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=DES, 2=ENF, 3=HAL, 4=ISO, 5=SEV"/>
<flow BT="xs:float" inv="NaN, -Inf=na" U="mL/h"/>
<caseConsumption BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
<totalConsumption BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
</aaGas>
<ecoFlow>
<recommendedO2Flow BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
</ecoFlow>
</num>
</gasDeliv>
<gasMon>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<num>
<respGas card="0,9">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=Air,2=Ar,3=Balance,4=CO2,5=He,6=HeO2,7=N2,8=N2O,9=O2"/>
<fractionalInspiredConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
<endTidalConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
<inspiredEndTidalDifference BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</respGas>
<aaGas card="0,5">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=DES, 2=ENF, 3=HAL, 4=ISO, 5=SEV"/>
<fractionalInspiredConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
<endTidalConc BT="xs:float" inv="NaN, -Inf=na" U="%"/>
</aaGas>
<metabolicConsumption>
<volO2 BT="xs:float" inv="NaN, -Inf=na" U="mL/min"/>
<volO2PerBodyWeight BT="xs:float" inv="NaN, -Inf=na" U="mL/min/kg"/>
<volO2PerBSA BT="xs:float" inv="NaN, -Inf=na" U="mL/min/m2"/>
</metabolicConsumption>

4-14 2098870-001
 <metabolicProduction>
<volCO2 BT="xs:float" inv="NaN, -Inf=na" U="mL/min"/>
<volCO2PerBodyWeight BT="xs:float" inv="NaN, -Inf=na" U="mL/min/kg"/>
<volCO2PerBSA BT="xs:float" inv="NaN, -Inf=na" U="mL/min/m2"/>
</metabolicProduction>
<expendedEnergy BT="xs:float" inv="NaN, -Inf=na" U="kcal/day"/>
<respiratoryQuotient BT="xs:float" inv="NaN, -Inf=na" U="{unitless}"/>
<macSum BT="xs:float" inv="NaN, -Inf=na" U="{unitless}"/>
<macSumAgeCorrected BT="xs:float" inv="NaN, -Inf=na" U="{unitless}"/>
</num>
</gasMon>
<resp>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<num>
<circuitO2 BT="xs:float" inv="NaN, -Inf=na" U="%"/>
<inspiredTidalVolume>
<total BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
<breathTrigger BT="xs:unsignedByte" enum="0=unspecified, 1=vent, 2=pa
tient"/>
</inspiredTidalVolume>
<expiredTidalVolume>
<total BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
<spontaneous BT="xs:float" inv="NaN, -Inf=na" U="mL"/>
</expiredTidalVolume>
<inspiredMinuteVolume>
<total BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
</inspiredMinuteVolume>
<expiredMinuteVolume>
<total BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
<spontaneous BT="xs:float" inv="NaN, -Inf=na" U="L/min"/>
</expiredMinuteVolume>
<respRate>
<total BT="xs:float" inv="NaN, -Inf=na" U="{breath}/min"/>
<spontaneous BT="xs:float" inv="NaN, -Inf=na" U="{breath}/min"/>
</respRate>
<respRateCO2 BT="xs:float" inv="NaN, -Inf=na" U="/min"/>
<airwayPressure BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<peakPressure>
<measured BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
</peakPressure>
<plateauPressure>
<static BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<measured BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
</plateauPressure>
<PEEP>
<dynamic>
<total BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<extrinsic BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<intrinsic BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
</dynamic>
<static>
<intrinsic BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>
<extrinsic BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]"/>

2098870-001 4-15
 </static>
</PEEP>
<ambientPressure BT="xs:float" inv="NaN, -Inf=na" U="mm[Hg]"/>
<resistance>
<dynamic BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]/L/s"/>
</resistance>
<compliance>
<static BT="xs:float" inv="NaN, -Inf=na" U="mL/cm[H2O]"/>
<dynamic BT="xs:float" inv="NaN, -Inf=na" U="mL/cm[H2O]"/>
</compliance>
<inspiratoryTime BT="xs:float" inv="NaN, -Inf=na" U="s"/>
<expiratoryTime BT="xs:float" inv="NaN, -Inf=na" U="s"/>
<IERatio>
<IERatioExp BT="xs:float" inv="NaN, -Inf=na" U="{unitless}" S="100.0"
/>
<IERatioInsp BT="xs:float" inv="NaN, -Inf=na" U="{unitless}" S="10.0"
/>
</IERatio>
</num>
</resp>
</params>

4-16 2098870-001
Appendix 4 Waveforms
<params>
<gasMon>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<wav>
<respGas card="0,10">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=Air, 2=Ar, 3=Balance, 4=CO2, 5=He, 6=HeO2, 7=N2, 8=N2O, 9=O2"/>
<conc BT="xs:float" inv="NaN, -Inf=na" U="%" vsizeBT="10"/>
</respGas>
<aaGas card="0,6">
<gas BT="xs:unsignedByte" card="1" isattr="true" enum="0=Unspecified,
1=DES, 2=ENF, 3=HAL, 4=ISO, 5=SEV"/>
<conc BT="xs:float" inv="NaN, -Inf=na" U="%" vsizeBT="10"/>
</aaGas>
<inspExpMarker BT="xs:unsignedByte" vsizeBT="10" enum="0=none, 1=breath"/
>
</wav>
</gasMon>
<resp>
<source BT="xs:unsignedByte" card="1" enum="0=unknown, 9=ge_anesthesiaDevice,
10=ge_gasAnalyzer, 13=ge_ventilator"/>
<index BT="xs:unsignedByte"/>
<wav>
<flow BT="xs:float" inv="NaN, -Inf=na" U="L/min" vsizeBT="10"/>
<volume BT="xs:float" inv="NaN, -Inf=na" U="L" vsizeBT="10"/>
<pressure BT="xs:float" inv="NaN, -Inf=na" U="cm[H2O]" vsizeBT="10"/>
<inspExpMarker BT="xs:unsignedByte" vsizeBT="10" enum="0=none, 1=insp, 2=
exp"/>
</wav>
</resp>
</params>

2098870-001 4-17
4-18 2098870-001
 5 Pre-installation Network Checklist

Pre-installation Network Checklist

DOC1949974 5-1
Aisys and Aisys CS2™
Pre-installation Network Checklist

Network connections
Machines with System Software 11 can be set up to directly connect
to one device through Port 1 and up to three devices through Port 2
using the hospital network.

2 1 1

AC.25.091

1. Port 1 (Direct Device/Static IP. Single connection.)

2. Port 2 (Dynamic IP. Multiple connections.)

• Device 1 - HL7 and SBX outbound

• Device 2 - HL7 and SBX outbound
• Device 3 - HL7 and SBX outbound
• Clock Sync. (Network Time Server)
• Log transfer (Service Logs)

Figure 1 • Port 1 and Port 2 Network location and functions

1
Pre-installation Network Checklist
This form is intended to be filled out by Hospital IT personnel. This
information is to be used by an authorized GE representative during
system installation and setup.
.

IT information provided by:

Hospital Name:
System ID or Serial Number: Location (Room #):

Port 1 connection information

.

Port 1 (Direct) Configuration settings

Enable or Disable (circle): Enable / Disable
IP Address: __ __ __.__ __ __.__ __ __.__ __ __
Subnet Mask: __ __ __.__ __ __.__ __ __.__ __ __
Speed and Duplex (check):
□ Auto negotiate

□ 100 MB Full

□ 100 MB Half

□ 10 MB Full

□ 10 MB Half

Direct Device Configuration Settings

Display name:
IP address: __ __ __.__ __ __.__ __ __.__ __ __
Port:
Communication Protocol (circle): Sapphire / HL7
HL7 transfer rate (check):
□ 10 secs

□ 1 min

□ 5 min

□ 15 min

2 DOC1949974 Rev A 09 2017

 Port 2 connection information
.

Configuration Settings for Port 2

Port 2 Configuration Settings

Enable or Disable (circle): Enable / Disable
DHCP: Enable / Disable

• When enabled, go to Speed and Duplex setting.

• When disabled, enter IP address, Subnet Mask.
Default Gateway and DNS server (if required).

IP address: __ __ __.__ __ __.__ __ __.__ __ __

Subnet Mask: __ __ __.__ __ __.__ __ __.__ __ __
Default Gateway: __ __ __.__ __ __.__ __ __.__ __ __
DNS Server: __ __ __.__ __ __.__ __ __.__ __ __
Speed and Duplex (check):
□ Auto negotiate

□ 100 MB Full

□ 100 MB Half

□ 10 MB Full

□ 10 MB Half

Configuration Settings for Port 2, Device 1

Port 2, Device 1 Configuration Settings

Enable or Disable (circle): Enable / Disable
Display Name (enter device name):
Network ID Method (circle): DNS Name / IP Address
DNS Name or IP Address (enter name or IP Address):
Port (enter Port number):
Communication Protocol (circle): Sapphire / HL7

DOC1949974 Rev A 09 2017 3

Port 2, Device 1 Configuration Settings
HL7 Transfer rate (check):
□ 10 secs

□ 1 min

□ 5 min

□ 15 min

Configuration Settings for Port 2, Device 2

Port 2, Device 2 Configuration Settings

Enable or Disable (circle): Enable / Disable
Display Name (enter device name):
Network ID Method (circle): DNS Name / IP Address
DNS Name or IP Address (enter name or IP Address):
Port (enter Port number):
Communication Protocol (circle): Sapphire / HL7
HL7 Transfer rate (check):
□ 10 secs

□ 1 min

□ 5 min

□ 15 min

Configuration Settings for Port 2, Device 3

Port 2, Device 3 Configuration Settings

Enable or Disable (circle): Enable / Disable
Display Name (enter device name):
Network ID Method (circle): DNS Name / IP Address
DNS Name or IP Address (enter name or IP Address):
Port (enter Port number):
Communication Protocol (circle): Sapphire / HL7
HL7 Transfer rate (check):
□ 10 secs

□ 1 min

□ 5 min

□ 15 min

4 DOC1949974 Rev A 09 2017

 Clock Sync.
Connect and enable Port 1 to synchronize the system clock with the
clock of the Direct Device (requires Sapphire protocol). Connect and
enable Port 2 to synchronize the system clock with a Network Time
Server.
.

Configuration Settings for Clock Synchronization

Clock Synchronization Configuration Settings

Clock Sync. Method: (circle): None / Direct Device / Network Time Server
Network ID Method: (circle): DNS Name / IP Address
DNS Name or IP address:

Log Transfer
.

Configuration Settings for Log Transfer

Log Transfer (Port 2) Configuration Settings

Enable or Disable (circle): Enable / Disable
Transfer Time (enter time, 24 hr clock - ex. 14:00): __ __:__ __
Network ID Method (circle): IP Address / DNS Name
IP Address or DNS Name (enter IP address or DNS
name):
Folder Path (enter folder path of FTP location where
transferred logs are to be archived):
User name (as required):
Password (as required):

DOC1949974 Rev A 09 2017 5

 6 Privacy and Security

Privacy and Security

In this section Privacy and Security Overview. . . . . . . . . . . . . . . . . . . . . . .6-2

Privacy and Security Capabilities. . . . . . . . . . . . . . . . . . . . . 6-3
Information Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-6
System Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
System (Product) Change Management. . . . . . . . . . . . . . 6-11
Personal Information Collected/Disclosed by the Product. . 6-
12

DOC1949974 6-1
Aisys™ CS² Network Configuration Guide

Privacy and Security Overview

This document describes privacy and security considerations for the
use of Aisys CS2 11.00 anesthesia machines (Aisys CS2 11.00
refers to Aisys CS2 machines that run System Software 11.00). This
manual describes the expected intended use, the privacy and
security capabilities included, and how they are configured and used.
The information is provided to assist the user in using the system in
a manner that protects patient privacy and security, and to work in
accordance with local and federal regulatory requirements. This
information also addresses expectations for the environment where
Aisys CS2 11.00 anesthesia machines will be used, and contains
information regarding security upgrade procedures.
This document assumes that the reader understands the concepts of
privacy and security. Privacy refers to protecting patient information.
Security refers to protecting both the system and its information from
risks to confidentiality, integrity, and availability. Security protects
privacy but also protects against these risks. Privacy requires
security.
The healthcare provider organization is encouraged to use risk
management procedures to assess and prioritize privacy, security,
and safety risks. Using risk management, one can determine how to
best leverage the capabilities provided in the GE Healthcare Aisys
CS2 11.00. In healthcare, one must balance privacy, security, and
safety. Most of the time there is not a conflict between these three
domains of risk. In cases where security mitigation conflicts with
patient safety, patient safety should be considered a higher priority.

Privacy and Security Environment

The Aisys CS2 11.00 is to be used in a controlled environment such

as an operating room with physical access controls so that only
authorized personnel are allowed access.

6-2 DOC1949974
 6 Privacy and Security

Privacy and Security Capabilities

The Aisys CS2 11.00 incorporates a broad assortment of capabilities
to enable privacy and security. This section describes the nature and
use of these capabilities.

Access Controls

The Aisys CS2 11.00 supports access control mechanisms to protect

access to privileged modes and sensitive information.

User Accounts and Authentication

The Aisys CS2 11.00 supports the following shared user accounts.
These user accounts are fixed and the system does not support
creation or deletion of user accounts.

User accounts and authentication

User Capabilities Authentication

Normal User Considering the low
• Start and End
barrier access
case.
requirements of the
• Perform checkouts.
product; Normal User is
• Modify system
not authenticated.
settings to deliver
care to patient.

Super User Password.

• Facility
configuration. • The Default
• Copy service logs. Passwords and
• Reset system to procedure to
factory defaults. change them can
• Network be found in the
Configuration. User's Reference
Manual,
2093496-001.

DOC1949974 6-3
Aisys™ CS² Network Configuration Guide

User Capabilities Authentication

Service Password.
• Service the
machine. • The Default
• Calibration of the Passwords and
sensors. procedure to
• Modify system change them can
hardware be found in the
configurations. Technical
• Copy and delete Reference Manual,
service logs. 2069137-001 Rev
• Connect to PC C.
Service App.

Note The factory default Super User password and Service passwords
can be changed. Users are advised to change the passwords after
installation and to share the passwords with authorized and trained
personnel only.

Patient Privacy Consent Management

The Aisys CS2 11.00 collects, uses, and discloses only the Patient
Information listed in "Personal Information Collected/Disclosed by the
Product" and does not support any Patient Privacy Consent
Management.
Hospitals are advised to adopt the Patient Privacy consent
management as applicable by the authority of law.

Privacy and Security Audit Logging and Accountability Controls

Privacy and Security Audit Logging and Accountability Controls

support security surveillance and privacy investigations and
reporting.
• The Aisys CS2 11.00 supports service logs. The events logged
are pre-defined and are not configurable by the user.
• The system logs can be used for audit purposes.
• The Aisys CS2 11.00 logs the following types of logs:
• Alarm Log: Technical and parameter alarms.
• Key-Press Log: User interface interactions.
• Event Log: System events based on procedures carried
out.
• Error Log: Captures subsystem reported errors

• Each log entry contains:

• A time stamp of when the event occurred, with a resolution
of 1 second. Timestamps show the local date and time of
the system.

6-4 DOC1949974
 6 Privacy and Security

• A brief description about the event.

• The system logs are stored in battery backed up non-volatile

memory and are retained during system reboot.
• When the number of log entries reaches the allowed maximum
entries, the oldest entry in the log database is overwritten.
• Alarm Log: 4000 maximum log entries.
• Contains alarm information.

Key-Press Log: 4000 maximum log entries.

• Checkout, Procedures
• Agent changes
• Module connect/disconnect
• User mode changes
• Reset of logs

• Event Log: 1000 maximum log entries.

• User menu-button actions. Add password changes to
appropriate log.

• Error Log: 1000 maximum entries.

• Captures subsystem reported errors.

• The system logs can be erased in Service mode.

• The system logs are access protected and cannot be modified.
• The Aisys CS2 11.00 supports transferring the logs to a USB
removable media, which can be performed in Super User or
Service modes.
• The Aisys CS2 11.00 supports transferring the logs to a pre-
defined FTP log server on the hospital network. Log transfer can
only be configured only in Super User mode.

DOC1949974 6-5
Aisys™ CS² Network Configuration Guide

Information Protection
This section focuses on privacy and security operations and contains
information to guide in the preparation of a secure environment for
the Aisys CS2 11.00
Security operations are best implemented as part of an overall
“defense in depth” information assurance strategy and are used
throughout an Information Technology system that addresses
personnel, physical security, and technology. The layered approach
of “defense in depth” limits the risk that the failure of a single
security safeguard will allow compromise of the system.

Network Security

GE strongly recommends that medical information systems are

operated in a secure network environment that is protected from
unauthorized intrusion. There are many effective techniques for
isolating and protecting medical information systems, including
implementing firewall protection, Virtual Local Area Networks
(VLANs) and network enclaves. To assist in secure network design,
the following network profile outlines the required network services
for the Aisys CS2 Anesthesia Machine.

Serial Communication

The Aisys CS2 11.00 communicates with a bedside device through

the serial port. The destination of the information is not authenticated
and the information is not encrypted due to the proximity of the client
and the intended use environment of the system.

Removable Media Security

The Aisys CS2 11.00 supports USB removable media for the
following operations:
• System software upgrade.
• Import and export of system settings.
• Password reset to factory default.
• Exporting of system logs.
The Aisys CS2 11.00 supports booting from a USB portable
media, which is a specially configured tool available only to
Service users. This tool is used for system software upgrades.

6-6 DOC1949974
 6 Privacy and Security

The Aisys CS2 11.00 does not encrypt the removable media, as
only the PHI of patient age and weight is captured in the log
files.

Data at Rest Security

The Aisys CS2 11.00 does not encrypt its storage, as only service
logs are captured in the log files.
The Aisys CS2 11.00 does not encrypt its storage memory, as the
system must be disassembled to access the storage memory (Flash
Card).

Data Integrity Capabilities

The Aisys CS2 11.00 contains capabilities to assure that data is not
inappropriately modified accidently or maliciously.
• System software and settings are integrity checked on every
boot using CRC. If the system integrity check fails on boot the
system enters a failed state.
• System software and settings are monitored for their integrity
using CRC over run-time every 30 seconds. If the system
software integrity fails over run-time, the system enters a failed
state.
• System software upgrade employs an integrity check
mechanism of the new software before loading it on the system.
If the integrity check of the new software fails, the system
software upgrade is aborted.
• System settings are integrity checked before being loaded on
the system. System settings are also validated for the ranges
before being loaded on the system.

De-identification Capabilities

The Aisys CS2 11.00 does not store any data on its system that can
be used to identify an individual. The Personal Information listed in
"Personal Information Collected/Disclosed by the Product" cannot be
used to identify an individual without other information.
The Personal Identification Information listed in the "Optional Patient
Identification Capabilities" can be used to identify an individual.
However, it is disabled by default and it is at the discretion of the
customer to enable Patient Identification capabilities in the system.
If the customer wants to de-identify the information sent over
network, the optional Patient Identification Information can be

DOC1949974 6-7
Aisys™ CS² Network Configuration Guide

disabled in Super User mode. Refer to the "Aisys CS2 Version 11

Users Reference Manual" for additional information.

Business Continuity

The Aisys CS2 11.00 supports the following mechanism for disaster
recovery and business continuity planning:
• System supports exporting and importing of the facility
configuration of the system.

• System supports software upgrade to install/re-install the system

software.

6-8 DOC1949974
 6 Privacy and Security

System Protection
The Aisys CS2 11.00 must be configured and maintained in a way
that continually protects privacy and security.

Malicious Software Protection Customer Responsibilities

In addition to the threat mitigations built into the Aisys CS2 11.00
anesthesia machine, the customer plays a significant role in ensuring
the safe and effective operation of the device. A holistic security
defense includes the following components:

• Device connected to Network designed as recommended

• Device not subjected to unintended network traffic
• Physical access controls to the machine
• User training

The customer is responsible to ensure that only approved devices

are installed on the Medical Device Network where Aisys CS2 11.00
anesthesia machine is connected. The Medical Device Network shall
be isolated from the customer’s enterprise network, via physical or
virtual isolation (VLANs). The Medical Device Network may be
connected to the hospital enterprise network; however, the Medical
Device Network router/firewall, or an equivalent firewall, must bridge
the Medical Device Network and hospital enterprise network to only
allow known network traffic from the hospital enterprise network into
the Medical Device Network.
The customer is also responsible to ensure that the Aisys CS2 11.00
anesthesia machine is installed in a location where unauthorized
users are prevented from physical access to the device.
Care should also be taken to ensure that any physical displays are
only visible to the intended users so that protected healthcare
information is not seen by unauthorized users.
Lastly, the customer is responsible to ensure that any users of the
Aisys CS2 11.00 anesthesia machine are trained on the use of the
product, including acceptable use.

Antivirus Programs

Commercial anti-virus software is commonly used on general

purpose computers to detect the presence of malicious software, as
they typically cannot be sufficiently hardened against the attack
vectors used by malicious software.
Medical devices are single purpose (dedicated) devices that have
controlled intended use, and thus can be well hardened. For medical
devices, the patient safety risk introduced by using commercial anti-
virus software outweighs any security benefit. Such risks include:

DOC1949974 6-9
Aisys™ CS² Network Configuration Guide

• Real-time scanning affecting system performance.

• Introducing false positives.
• Quarantining of clinical data that randomly appear to match a
virus signature.
• The anti-virus software itself is another popular attack vector.
• Support of the anti-virus software throughout the life cycle of the
medical device (Operating System support and virus signatures/
libraries).

Due to the cited risks, the use of anti-virus software is not part of this
product security strategy.

6-10 DOC1949974
 6 Privacy and Security

System (Product) Change Management

Security patches to the Aisys CS2 11.00 can only be applied as part
of a system software upgrade. Aisys CS2 11.00 software upgrade
must be performed by GE Healthcare authorized service personnel
and with only GE Healthcare authorized service tools. Any
modification of system software or installation of third party software
on the Aisys CS2 11.00 is prohibited.

DOC1949974 6-11
Aisys™ CS² Network Configuration Guide

Personal Information Collected/Disclosed by the Product

One of the core privacy principles incorporated into the design of GE
Healthcare products is that of transparency, the principle that
patients must be informed that their data is being collected and how
it will be used. To meet this requirement, GE Healthcare provides the
customer with a listing of the information the Aisys CS2 11.00
product collects, the purpose for which data is collected, and how it
is used. GE Healthcare also specifies how the patient data is
protected and how long it will be retained.
The Aisys CS2 11.00 collects the following types of information for
monitoring and delivering care to the patient:
• Patient demographic information
• Patient Age
• Ideal Weight

• Personal or protected health information

• Start Date Time of Case
• End Date Time of Case
• Anesthetic Agent
• Physiological Information like Respiration, Gas Monitoring
and Gas Delivery Information

• Machine data (pre-configured, not collected)

• Machine Serial Number

Optional Patient Identification Capabilities

In addition to the Patient Information, the following identifiers which

are disabled by default can be entered in the system for network
disclosure purposes:

• Patient First Name

• Patient Last Name
• Medical Record Number (MRN), if entered by user, else pseudo
generated ID
• Case ID
• Bed Location
• IP Address
• System Logs, Breath Logs

6-12 DOC1949974
 6 Privacy and Security

Note This Patient Information is sent unencrypted (plain text) over

network. Please enable this feature only if the network is secure
enough to protect the confidentiality of the patient information.

Additional Privacy and Security Considerations

The Aisys CS2 11.00 has been designed with privacy and security
functionality integrated into the core design. However, privacy and
security residual risks exist that must be mitigated once the Aisys
CS2 11.00 is integrated into the intended use environment. This
section contains some risks that should be imported into the Risk
Assessment of the deployment of the Aisys CS2 11.00 for proper
mitigation.

Residual Risk Recommended Mitigation

Access to Normal user mode by
• System should only be used by
unauthorized personnel.
authorized users in an area with
physical access controls.

Access to Super User mode by

• System should only be used by
unauthorized personnel using the
authorized users in an areas
shared password.
with physical access controls.
• Super User password use is
limited to authorized personnel
who are trained and qualified.
Do not share the password with
unauthorized personnel.

Access to Super User mode by

• System should only be used by
unauthorized personnel when system
authorized users in an area with
is left unattended in Super User
physical access controls.
mode.
• Do not leave the machine
unattended in Super User
mode.
• Exit Super User mode after task
completion.

Access to Service User mode by

• System should only be used by
unauthorized personnel using the
authorized user in an area with
shared password.
physical access controls.
• Service password use is limited
to authorized personnel. Do not
share the password with
unauthorized personnel.

DOC1949974 6-13
Aisys™ CS² Network Configuration Guide

Residual Risk Recommended Mitigation

Access to Service mode by
• System should only be used by
unauthorized personnel when system
authorized users in an area with
is left unattended in Service mode.
physical access controls.
• Do not leave the machine
unattended in Service mode.
• Exit Service mode after task
completion.

The physical data when associated

• System should only be used by
with Patient information will disclose
authorized users in an area with
the activity performed on the
physical access controls.
individual.
Information transmitted to Network
• Network and Patient information
Client is unencrypted.
collection is disabled by default
in the system.
• Enable Patient Information, only
when device is connected to
secure, protected network.

6-14 DOC1949974
 Index

A Network specifications
network interface flow 2-4
Access controls 6-3 network interface techncial specifications
Additional privacy and security considerations 2-4
6-13
Antivirus programs 6-9
Appendix
O
sample code 3-11, 4-5 Optional patient identification capabilities 6-12
Audit logging; Accountability 6-4 Overview
HL7 3-2
B intended audience 1-2
intended use 1-2
Business continutiy 6-8
P
D
Patient privacy consent management 6-4
Data at rest security 6-7 Personal information collected/disclosed by
Data integrity capabilities 6-7 the product 6-12
De-identification capabilities 6-7 Pre-installation network checklist 5-1
Privacy and security capabilities 6-3
H Privacy and security environment 6-2
HL7 integration 3-1 Privacy and security overview 6-2
HL7 intended use 3-2 Protocol 3-4

I R
Information protection 6-6 Removable media security 6-6
Intended audience 1-2
intended use 1-2 S
Introduction 6-1 Safety information
Cautions 1-4
M safety statements 1-4
Malicious software protection customer Warnings 1-4
responsibilities 6-9 Safety statements 1-4
Messages 3-5 Serial communication 6-6
status delay 3-3
N Symbols 1-5
System (Product) change management 6-11
network cable disconnection 3-3 System protection 6-9
network communication 2-3
Network configuration U
client devices 1-3
data output 1-3 User accounts and authentication 6-3
overview 2-2
Network security 6-6

DOC1949974 I-1
Aisys™ CS² Network Configuration Guide

I-2 DOC1949974
Aisys™ CS² Network Configuration Guide
User's Reference Manual
English
DOC1949974
10 2017 Rev B