Instructions for Use

Infinity® Gateway Suite

WARNING Protocol Handbook

To properly use this medical device,
read and comply with these Software VF9.0
instructions for use.
 General Information

General Information

Trademarks

The Dräger name and logo are registered trademarks of Dräger.

Pick and Go®, Infinity®, and Infinity® PatientWatch® (Europe not US) are registered trademarks of Dräger.
Windows®, Microsoft®, Internet Explorer®, and SQL Server® are registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
HL7® is a registered trademark of Health Level Seven International.

Open-source software

Dräger devices that use software may use open-source software, depending on their setup. Open-source
software may be subject to different terms of license. Additional information regarding the open-source
software used in this device is available at the following web page:
www.draeger.com/opensource

User group requirements

The term "user group" describes the personnel responsible who have been assigned by the operating or-
ganization to perform a particular task on a product.

Duties of the operating organization

The operating organization must ensure the following:

– Every user group has the required qualifications (e.g., has undergone specialist training or acquired
specialist knowledge through experience).
– Every user group has been trained to perform the task.
– Every user group has read and understood the relevant chapters in this document.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 3

General Information

User groups

Clinical users
This user group operates the product in accordance with the intended use.
Users have medical specialist knowledge in the application of the product.

Service personnel
This user group installs the product and performs the service activities.
Service personnel have specialist knowledge in software systems and applications. Service personnel
also have experience in the servicing of medical devices.
Where product specific knowledge or tools are required, the service activities must be carried out by spe-
cialized service personnel. The specialized service personnel was trained by Dräger for these service ac-
tivities on this product.

Operating characteristics

Classification

Classification Medical Device Europe Class IIa

4 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 General Information

Symbols

The following table lists the Infinity Gateway symbols. Additional information about the symbols is avail-
able on the following web page: www.draeger.com/md-symbols

Symbol Description
Read accompanying IFU for specific safety information.

WEEE (Waste Electrical and Electronic Equipment)

Do not dispose of at municipal collection points for waste electrical and electronic
equipment. Dräger has authorized a company to collect and dispose of this
device.

Rx only Caution: Federal law restricts this device to sale by or on the order of a
physician

European Union Representative

Device part number and revision

Manufacturer

Date of manufacture

Complies with the European Medical Device Regulation (EU) 2017/745

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 5

General Information

Symbol Description
Complies with applicable EU regulations and directives

Quantity

China RoHS mark

Unique Device Identifier, barcode

Lot/batch number

Medical device

Importer

Importer

Revision index

6 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Safety

Safety

Mandatory reporting of adverse events

Serious adverse events with this product must be reported to Dräger and the responsible authorities.

Follow instructions for use

WARNING
Strictly follow these instructions for use. Any use of the software requires a full understanding
and strict observation of all portions of these instructions. The software is only to be used for the
purpose specified under "Intended use" on page 9 and in conjunction with appropriate patient
monitoring. Observe all WARNING and CAUTION statements as rendered throughout this
manual, and all statements on device labels.

Definitions

Certain paragraphs within these instructions are highlighted as WARNING, CAUTION or NOTE as follows:

WARNING
A WARNING statement provides important information about a potentially hazardous situation
which, if not avoided, could result in death or serious injury.

CAUTION
A CAUTION statement provides important information about a potentially hazardous situation which, if
not avoided, may result in minor or moderate injury to the user or patient or in damage to the equipment
or other property.

NOTE
A NOTE provides additional information intended to avoid inconvenience during operation.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 7

Safety

Connecting to the network

Dräger provides patient monitoring, therapy, and IT products that may exchange information both with
each other and other non-Dräger devices in the clinical environment over information technology networks
(IT networks). Each data interface is an IT network in terms of the relevant communications standard (e.g.
printer interface, ISB interface, etc.).
Transmission of patient and device data across the IT network enables patient data and equipment data
to be monitored, stored, transferred, printed, or shared through the use of direct wired and wireless tech-
nologies, facilitating the following operations:
– Waveform and parameter data display
– Alarm notification
– Network recordings and printing
– Remote control (for example, alarm management)
– Patient archive data review (trends, events, charting information)
– Service access (device and component status data; log file access)
Connecting Dräger devices to a shared IT network with other devices, or subsequent changes to the
shared IT network, can lead to previously unidentified risks for patients, users, and third parties. These
risks must be identified, analyzed, evaluated, and controlled before placing the medical device into the IT
network. Before a device can be in service on the Infinity Network, a valid and unique IP address must be
entered.

Security recommendations

Dräger makes the following security recommendations:

– Physical security of the patient monitors is recommended and is the responsibility of the operating
organization.
– Physical security of the telecommunications closet is recommended and is the responsibility of the
operating organization.
– Dräger recommends that operating organizations restrict physical access to unused Ethernet ports on
the Gateway.
– Dräger recommends that operating organizations restrict physical access to unused USB and serial
ports on the Gateway.
– Dräger relies on the medical device isolation mechanism of the VLANs and the proper configuration,
implementation, and use of the operating organization's security measures to prevent the introduction
of malware onto the Infinity network.

CAUTION
Dräger recommends that all documents opened for viewing from the hospital LAN are from a secure
source.

8 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Intended purpose

Intended purpose

Intended use

The Infinity Gateway software applications are intended to provide clinicians with the capability of viewing
patient data remotely via the Infinity network and for data exchange of select clinical and administrative
information between the Infinity network and the hospital network.

Indications

The Infinity Gateway software applications are intended to provide clinicians with the capability of viewing
patient data remotely via the Infinity network and for data exchange of select clinical and administrative
information between the Infinity network and the hospital network.

Contraindications

There are no known contraindications for the Infinity Gateway software applications.

Environments of use

The Infinity Gateway software applications are intended for use in a healthcare environment.

Patient population

The Infinity Gateway software applications are applicable to all patient populations.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 9

Intended purpose

Intended application

The intended application of the Infinity Gateway software applications is data exchange between the Infin-
ity network and the hospital network. This device is an active, reusable, and non-implantable medical
device. It does not come into direct contact with the patient’s body.

10 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Service-oriented device connectivity (SDC)

Service-oriented device connectivity (SDC)

Service-oriented device connectivity (SDC) defines a communication architecture to establish distributed

systems of medical devices in clinical environments, for example, high-acuity environments. The protocol
is built on the principles of service-oriented medical device architecture (SOMDA) and is modeled after
ISO/IEEE 11073. SDC-enabled devices facilitate interoperability across Dräger SDC-compatible products
by allowing the request of unidirectional data and/or the remote control of predetermined medical device
functionality in a safe manner.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 11

 This page has been left blank intentionally.

12 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Table of Contents

Table of Contents

General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Intended purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Service-oriented device connectivity (SDC) . . . . . . . . . . . . . . . . . 11

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Infinity Gateway Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

File Access Developer’s Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

WinAccess API Developer’s Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 27

HL7 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Unsolicited Vital Signs Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Unsolicited IEEE 11073 Vital Signs Export . . . . . . . . . . . . . . . . . . 61

Solicited Vital Signs Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Unsolicited ADT Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

IHE Unsolicited ADT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Solicited ADT Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Lab Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Lab Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Alarm Communication Management Interface . . . . . . . . . . . . . . 215

ASTM Stat Lab Interface Option . . . . . . . . . . . . . . . . . . . . . . . . . . 243

PatientWatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Appendix A: Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Appendix B: Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix C: Special Display Values. . . . . . . . . . . . . . . . . . . . . . . 281

Appendix D: Alarm States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 13

Table of Contents

Appendix E: Alarm Grades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Appendix F: Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Appendix G: Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Appendix H: 12-Lead ECG Output Format. . . . . . . . . . . . . . . . . . 291

Appendix I: Troubleshooting Gateway M300 Connections . . . . 295

Appendix J: Relationship table. . . . . . . . . . . . . . . . . . . . . . . . . . . 299

14 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Preface

Preface

A customized version of the Protocol Handbook accompanies each copy of the Infinity Gateway server
software to convey the following:
 High-level information about the software development capabilities of the server.
 Information about interfacing the SERVER within a hospital environment using specific protocols.
 Specific information with regards to data fields, values, and formats.

CAUTION
Updates to this information will be issued and packaged with each subsequent release of this product.
It is strongly recommended that you read the accompanying document each time you receive an
updated version of the software so that you will be aware of any changes in the product or the associated
documentation.

This document does not contain installation instructions. To install software or any of its optional
applications, or other related components, consult the Installation Guide and/or hard copy instructions
included with the installation media of the server.
Questions about the Protocol Handbook Documentation
If you have questions relating to this document, please contact your local field service representative.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 15

 This page has been left blank intentionally.

16 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Infinity Gateway Server

Infinity Gateway Server

The Infinity Gateway Server facilitates the exchange of important clinical information between the Infin-
ity/SDC protocol and your existing hospital and patient care systems. The Infinity Gateway Server is
designed to provide developers with maximum flexibility by using common healthcare protocols and data
format standards for managing communications between multiple disparate systems. Select one or more
Infinity Gateway Developer’s Tools and Interface Options to create a seamless flow of information tailored
to support your unique clinical work flow.
Infinity Gateway Developer’s Tools and Interface Options are licensed, or “unlocked”, by using option
passwords. An option password is the electronic proof of purchase for the appropriate Infinity Gateway
software. During the setup procedure, you will be asked for an option password, which will trigger the
“unlocking” of the appropriate Infinity Gateway Developer’s Tools and Interface Options.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 17

Infinity Gateway Server

Infinity Gateway Developer’s Tools Interface Type Description

and Interface Options
File Access Developer’s Tool Shared Files A utility for accessing patient
directory information and monitoring
data (parameters and alarms) from
Infinity patient monitors and
exporting that data in UTF-16 text
format.
WinAccess API Developers Tool DLL/socket An API developer’s tool utilizing
WvAPI.DLL for access to a wide
range of information, including
demographic data, parameters,
alarms, and waveforms. Some
methods are also accessible via a
socket interface for non-Windows
applications.
HL7/ASTM Interface Option HL7 and ASTM A service for:
 exporting HL7 vital signs data
(parameters) in an unsolic-
ited or solicited HL7 inter-
face,
 importing ADT data in an
unsolicited or solicited Hl7
interface,
 exporting HL7 laboratory
data,
 importing HL7 laboratory
data, and
 importing ASTM laboratory
data from a device attached
to a serial port on the Infinity
Gateway Server
 exporting HL7 alarm data in
an unsolicited HL7 interface
ASTM Stat Lab Interface Option ASTM A service for importing ASTM
laboratory data from a device
attached to a serial port on the
Infinity Gateway PC or via a terminal
server.
Pager ESPA/TAP A service for exporting alarms via
serial or TCP connections using
ESPA or TAP protocols.

18 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Infinity Gateway Server

WARNING
The Infinity Gateway Suite and Interface Options are information transfer technology. They are
intended to make information from the Infinity and SDC Networks available to third party
applications. The Gateway Suite and Interface Options are not intended as a replacement for the
primary alarm notification system and/or clinical decision making systems. The delivery of pages
cannot be guaranteed or verified.

CAUTION
The use of an anti-virus program is strongly recommended for the Infinity Gateway Server and all client
PCs. Dräger has tested compatibility of the Infinity Gateway Suite with Trend Micro Deep Security Agent.
Prior to installing any Microsoft Hot Fixes and Microsoft product Service Packs, please contact your local
Dräger Service Representative to ensure compatibility with Dräger IT products.

Interpret Patient ID as Setting

This setting on the Server specifies how to interpret the patient identifier entered on patient monitors.
This identifier is referred to throughout this document as the primary identifier. The alternate identifier
(i.e. whichever of these two is not configured as the primary) is never used by the patient monitor, but it
may be used by HL7 interfaces.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 19

 This page has been left blank intentionally.

20 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 File Access Developer’s Tool

File Access Developer’s Tool

The Infinity Gateway File Access Developer’s Tool is a utility for accessing patient directory information
and monitoring data (parameters and alarms) from Infinity patient monitors and exporting that data in a
UTF-16 text format. The File Access Developer’s Tool does not support devices that are only on the SDC
Network.
The File Access Developer’s Tool creates the following data files:
 "Patient Directory" on page 21 file containing a list of current patients, additional system demographic
data detailed in Section 4.1, and the corresponding "Vital Signs Files" on page 22 file name.
 "Vital Signs Files" on page 22 file containing the latest parameter and alarm data.
The Patient Directory and Vital Signs files are UTF-16 files with variable size fields, and field delimiters
that allow simple methods of file navigation and parsing. The Infinity Gateway server setup program allows
you to specify the directory in which these files are created and the frequency at which they will be updated
(between 15 and 6,000 seconds).

Patient Directory

The Patient Directory file lists the patients whose information is currently being acquired by the Infinity
Gateway server.The Patient Directory will be updated dynamically whenever a change occurs in the Infin-
ity monitors. A typical Patient Directory is as follows:
##################################################################################
#
# Patient Directory (patient monitors currently being monitored by Infinity Gateway Vital Signs Server)
#
# Patient Directory Entry:
#
# Patient Name|Patient ID|Bed Label|Care Unit|File Name|IP Address|Multicast IP Address|Device
Type|Device Status
#
##################################################################################
Eugene Gray|502334|Bed01|CU2|00218100|191.1.2.181|224.0.2.181|SC9000B|Monitoring
Dennis Grunewald|250440|Bed01|CU3|00316500|191.1.3.165|224.0.3.165|SC9000|Monitoring
Cynthia Haber|520201|V3-8|V3|00309000|191.1.3.90|224.0.3.90|SC9000|Monitoring
Terrence Huxley|582822|TELAPOL|CU5|00515600|191.1.5.156|224.0.5.156|SC7000|Monitoring

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 21

File Access Developer’s Tool

Martin Inonu|522877|Bed01|CU1|00118300|191.1.1.183|224.0.1.183|SC7000|Monitoring
[End List]
Each Patient Directory file line contains the following information for each patient:

Field Description
Patient Name The patient name as it is entered on the Infinity monitor.
Patient ID The identifier as it is entered on the Infinity monitor.
Bed Label Identifies monitor or telemetry transmitter for the patient.
Care Unit Identifies care unit for the patient.
File Name Name of the Vital Signs file that contains monitoring data for patient.
IP Address IP Address of the Infinity monitor or Infinity CentralStation.
Multicast Address Multicast IP address on which patient data is broadcast. This address is
unique for a patient monitor or telemetry patients.
Device Type Model of source monitor.
Device Status Current status of the monitor: Monitoring, Standby, Discharged

NOTE
Future Infinity Gateway File Access Developer’s Option revisions may include additional information in
the Patient Directory file, which will always be added to the end of the record. The file format displays one
line per patient. The lines for individual patients contains nine data fields each separated by a delimiter,
or the “|” character. Lines beginning with a ‘#’ character are comment lines. The end of the Patient
Directory file is marked by an “[End List]” line.

Vital Signs Files

The Vital Signs file is created for each patient listed in the Patient Directory file. Each Vital Signs file con-
tains the last reading of the parameter and alarm data for a patient. The Vital Signs file has three main
sections:
 Patient Directory
 Current Alarm
 Patient Vital Signs

22 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 File Access Developer’s Tool

A typical Vital Signs file looks like this:

##################################################################################
#
# Patient Directory Entry:
#
# Patient Name|Patient ID|Bed Label|Care Unit|File Name|IP Address|Multicast IP Address|Device
Type|Device Status
#
##################################################################################
Bob White|552077|Bed01|CU2|00218100|191.1.2.181|224.0.2.181|SC9000B|Monitoring
##################################################################################
#
# Current Alarm Information:
#
# State|Grade|Message|Timestamp
#
##################################################################################
INACTIVE|SER||1992/02/13 02:54:24
##################################################################################
#
# Patient Vital Signs:
#
# Label|Value|Time|Draeger Code|HL7/LOINC Code|MIB/CEN Code|Draeger Status (= parameter's cur-
rent Alarm Grade)|HL7/LOINC Status|MIB/CEN Status|Draeger Units|HL7/LOINC Units|MIB/CEN
Units|Instance
#
##################################################################################
HR|83|2009/11/18 20:20:06|01001|8867-4|16770|NONE|||bpm|/min|2528|1
ARR| |2009/11/18 20:20:06|01003||03266|NONE|||bpm|/min|2528|1
PVC/min|0|2009/11/18 20:20:06|01004|||NONE|||bpm|/min|2528|1
PA S|33|2009/11/18 20:20:06|04008|8440-0|18973|NONE|||mmHg|mm(hg)|3872|1
PA D|14|2009/11/18 20:20:06|04007|8385-7|18974|SER|||mmHg|mm(hg)|3872|1
PA M|21|2009/11/18 20:20:06|04009|8414-5|18975|SER|||mmHg|mm(hg)|3872|1

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 23

File Access Developer’s Tool

CVP|15|2009/11/18 20:20:06|06009|8591-0|19012|NONE|||mmHg|mm(hg)|3872|1
RA|15|2009/11/18 20:20:06|08009|8400-4|18996|SER|||mmHg|mm(hg)|3872|1
ART S|167|2009/11/18 20:20:06|03008|8480-6|18961|SER|||mmHg|mm(hg)|3872|1
ART D|69|2009/11/18 20:20:06|03007|8462-4|18962|NONE|||mmHg|mm(hg)|3872|1
ART M|106|2009/11/18 20:20:06|03009|8478-0|18963|NONE|||mmHg|mm(hg)|3872|1
mib MVe|0.3|2009/11/18 20:20:06|36039||20812|NONE|||L/min|L/min|3072|1
mib TVe|15|2009/11/18 20:20:06|36040|||NONE|||ml|mL|1714|1
mib RRv|20|2009/11/18 20:20:06|36006|9279-1|20514|NONE|||1/min|/min|2784|3
mib PIP|60|2009/11/18 20:20:06|36036||20885|NONE|||cmH2O|cm_h2O|3904|1
mib PEEP|0|2009/11/18 20:20:06|36037||20732|NONE|||cmH2O|cm_h2O|3904|1
mib MAP|20|2009/11/18 20:20:06|36038||20720|NONE|||cmH2O|cm_h2O|3904|1
iO2|35|2009/11/18 20:20:06|38044|3150-0|21124|NONE|||%|%|544|2[End Vital Signs]
The information on each line is separated into a number of fields by a delimited, or the “|” character, in
each of the three sections. Lines beginning with a ‘#’ character are comment lines. The end of the Vital
Signs file is marked by an “[End Vital Signs]” line.

NOTE
Calculated parameters and ventilator settings are now available from certain patient monitors, but are
only output by the patient monitor once per minute, so they will not appear in the output file immediately
on startup of the Gateway.

24 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 File Access Developer’s Tool

Patient Directory

The single line in this section contains the same information listed in the patient’s line in the Patient Direc-
tory file.

Current Alarm

The Current Alarm section contains a single line of a patient’s current alarm state and grade. In the event
there is an alarm, the alarm timestamp and alarm message will appear.

Field Description
State Current alarm state, representing the most serious alarm state across all param-
eters currently monitored for a patient. Possible values are listed in Appendix D:
Alarm States.
Grade Current alarm grade, representing the most serious alarm grade across all the
parameters currently being monitored for the patient. Possible values are listed
in Appendix E: Alarm Grades.
Message Text describing the alarm condition.
Timestamp Timestamp identifying when the alarm condition was detected, in the format:
YYYY/MM/DD HH:MM:SS.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 25

File Access Developer’s Tool

Patient Vital Signs

The Patient Vital Signs section contains a series of parameter records listed below:

Fields Description
Label Infinity parameter label. Possible labels are listed in Appendix A: Parameters.
Value Infinity parameter value. Some parameters can take on non-numeric values.
Possible non-numeric parameter values are listed in Appendix C: Special Dis-
play Values.
Time Timestamp identifying when the parameter value was reported. The format for
the timestamp is YYYY/MM/DD HH:MM:SS.
Dräger Code Numeric code used to identify the parameter. Possible codes are listed in
Appendix A: Parameters.
HL7/LOINC Code Code used to identify the parameter in the HL7/LOINC standard. Possible
codes are listed in Appendix A: Parameters.
MIB/CEN Code Code used to identify the parameter in the MIB/CEN standard. Possible codes
are listed in Appendix A: Parameters.
Dräger Status Corresponds to the parameter’s alarm grade. Possible values are listed in
Appendix E: Alarm Grades.
HL7/LOINC Sta- Unused
tus
MIB/CEN Status Unused
Dräger Units Units of measure as defined on the INFINITY Network. Possible values are listed
in Appendix B: Units of Measure.
HL7/LOINC Units Units of measure as defined by the HL7/LOINC standard. Possible values are
listed in Appendix B: Units of Measure.
MIB/CEN Units Units of measure as defined by the MIB/CEN standard. Possible values are
listed in Appendix B: Units of Measure.
Instance Additional identifier used to distinguish parameters in the HL7/LOINC stan-
dard.

26 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 WinAccess API Developer’s Tool

WinAccess API Developer’s Tool

The WinAccess API Developer’s Tool provides access to an API (Application Programming Interface), a
powerful tool used to integrate data from the Infinity and SDC networks with custom applications. The
WinAccess API is designed for experienced developers with an understanding of API programming. This
section is intended to provide a high-level introduction to the use of the API only.
The WinAccess API is implemented as a Windows DLL (Dynamic Link Library), and makes the data
available through a set of functions callable from C or C++ programs. Access to the functionality is also
provided for non-Windows custom applications via a socket connection.

CAUTION
It is the responsibility of the customer to validate the functionality of any custom application developed
with WinAccess API Developer’s tool.

CAUTION
Custom applications that use WinAccess API should be developed such that all Gateway structures are
treated with 1-byte alignment.

CAUTION
Infinity Gateway supports filtering of alarms by alarm grade only. Filtering via other fields such as alarm
messages (strings) is not supported and must not be used.

A custom application can use the WinAccess API functions to obtain patient data from the Infinity Gateway
server. This application can request the WinAccess API to make a connection to a patient record. If the
connection is successful, the WinAccess API returns a connection ID that is unique on the Gateway server
for as long as the application is running and the connection is active. The application then uses this
connection ID to request other specific data for the patient, such as parameter values, alarm information,
waveform samples, trended data and demographic data. It can also use this connection ID to modify
demographic data at the monitor under certain limited circumstances.

CAUTION
Each connection should be used by only one thread.

The application can open multiple connections at once. Each Infinity or SDC connection counts as “client”
for purposes of controlling the number of simultaneous client connections at the Infinity Gateway server.
If a device is disconnected from the network (for example, during a “Pick and Go”, when the patient is
transported to another location), the connection ID for that patient will no longer be valid. The WinAccess
API does not provide asynchronous notification to the application that the connection has been lost. The
application should use the WinAccess API to check periodically with the Infinity Gateway server to test
which devices are still available.
In addition, the WinAccess API can also be configured to create 12-Lead Rest ECG output files for use by
a custom application. Please refer to Appendix H: 12-Lead ECG Output Format for more details.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 27

WinAccess API Developer’s Tool

NOTE
Further details about the functions, structures, and constants used in the DLL are not described this
document. However, extensive comments in the WvAPI.h file and the WvAPI.DLL file are provided.
These files can be found on the Infinity Gateway Server distribution CD, in the folder called “WinAccess
Option”.

CAUTION
Each version of the Infinity Gateway comes with a new version of the WvAPI DLL. Custom applications
accessing a given gateway must use a compatible version of the DLL to do so, and hence may need to
be re-compiled in order to support a new version of software.

WinAccess for Platforms other than Windows®

As of VF5, WinAccess has built in the capability to access functionality via a socket connection. A new
service, InfExp, is now installed on the server. Whenever the “make available via TCP/IP” option is
enabled (only supports Infinity), this service listens to a well known port for a connection from the custom
application. It accepts messages from the custom application and translates that into a function call into
the WvAPI DLL. When the function call returns, a response message is sent back to the custom
application. By default, the Gateway server listens on port 9101 for this connection, but the port is
configurable in the “Configure WinAccess” dialog.
The InfExp service can also be configured to accept and send messages in different byte-orders. If the
“Byte swap” option is enabled (default), then the service will expect that all incoming messages be in the
Big Endian order and will output all messages using that order. If the “Byte swap” option is not enabled,
then the service will expect that all incoming messages be in the Little Endian order.
The InfExp service can only support devices on the Infinity network, it does not support any devices that
are only present on the SDC network.

NOTE
Big Endian byte order means that the high-order byte of the number is stored in memory at the lowest
address, and the low-order byte at the highest address. This byte order is used by Motorola processors
and is the natural byte order of any network.
Little Endian byte order means that the low-order byte of the number is stored in memory at the lowest
address. This byte order is used by Intel processors.

28 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 WinAccess API Developer’s Tool

Software Developer’s Kit

Software developer resources to facilitate the use of the WinAccess API are provided in the Infinity
Gateway Software Developer’s Kit (SDK).
The SDK includes:
 API DLL (WvAPI.dll, WvAPI.h, and WvAPI.lib)
 WvSvc.dll, IGAcsMsg.dll and Wvresources_**.dll (Strings for each language supported), - other dlls
used by the WvAPI.dll
 WvAPITest, a test program that exercises all the functions in the WvAPI.dll
 RemTst, a DLL that can be used for testing the socket interface.
 Source code for the WvAPITest program and the RemTst DLL(these are complete Microsoft Visual
C++ projects).
The SDK can be found on Infinity Gateway Server distribution CD, in a folder called “WinAccess Option”.

CAUTION
As of VF6, WinAccess has been updated to support Unicode (UTF-16) strings, while still supporting
ANSI strings for backwards compatibility. The h-file is setup to export methods and structures in Unicode
format whenever the _UNICODE define is declared, and to export methods and structures in ANSI
format whenever the _UNICODE define is not declared.

The WvAPITest program has 8 build configurations as follows:

Build Configuration Debug/ Unicode/ Local/ Exe name
Name Release ANSI Remote
Win32 Debug Debug ANSI Local WvAPITest
Win32 Release Release ANSI Local WvAPITest
Win32 Unicode Debug Debug Unicode Local WvUAPITest
Win32 Unicode Release Release Unicode Local WvUAPITest
Win32 Remote Debug Debug ANSI Remote RemoteWvAPITest
Win32 Remote Release Release ANSI Remote RemoteWvAPITest
Win32 Remote Unicode Debug Unicode Remote RemoteWvUAPITest
Debug
Win32 Remote Unicode Release Unicode Remote RemoteWvUAPITest
Release

When any of the remote configurations are built and run, instead of using the WvAPI.DLL directly, it uses
the RemTst.DLL. This DLL in turn translates the function calls into socket messages which it sends to the
InfExp service. This setup allows the user to test the socket interface of WinAccess. There is one caveat,
however, this setup will only work if run on the same PC that the InfExp service is running on. This is due
to the fact that the local host address is hardwired into the source code of RemTst, i.e. “127.0.0.1”.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 29

WinAccess API Developer’s Tool

By default, RemTst is configured to build a DLL which WILL swap bytes and which will use port 9101 to
communicate with InfExp. These settings correspond to the default settings for InfExp.
To change this behavior, follow these instructions:
1 Open the developer studio project for RemTst.
2 Select menu Project\settings.
3 Select the C/C++ tab.
4 Select the “General” category from the pick list.
5 In the preprocessor definitions box, note that there are two entries, as follows:
USE_PORT=9101
DO_SWAP=1
6 If you want the software to use a port other than 9101 to communicate with InfExp, change the 9101
to the port that you want to use.
7 If you want the software to NOT do byte swapping, i.e. send messages in Little Endian order, then
change the DO_SWAP value to 0.
8 After making the changes, rebuild the DLL.

NOTE
In order for the Remote versions of WvAPITest to work with the Infinity Export Server (InfExp), the settings
for USE_PORT and DO_SWAP in the RemTst DLL must match the settings on InfExp that are set in the
“Configure WinAccess” dialog of the Infinity Gateway Setup. Also, unless the customer manually changes
the IP address in the code, the Remote version of WvAPITest will only work properly when run on the
same PC that InfExp is running on.

Functions

WvAPI.DLL Function Description

WvStart Performs necessary initializations.
WvStop Performs necessary cleanup.
WvListBeds Fills in a list of devices currently online at the INFINITY GATEWAY SERVER.
This may include Infinity devices, SDC devices or devices that are both
SDC and Infinity (such as an IACS).
WvConnect Opens a connection to an Infinity device. This function is not supported
on an SDC-only device.
WvConnectEx Opens a connection to a device on Infinity or SDC networks.

30 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 WinAccess API Developer’s Tool

WvAPI.DLL Function Description

WvTrendConnect Opens a connection to the device that is only to be used for requesting
Trends, Demographics, and Alarm data. The waveform and parameter
functions will not work. This function is not supported on an SDC-only
device.
WvDisconnect Closes a connection to a device.
WvListConnections Lists devices that are currently connected.
WvGetHighest- Returns information about the highest grade, currently active alarm (if
GradeAlarm any).
WvGetHighestGrade- Returns information about the highest grade, currently active ventilator
VentAlarm alarm (if any). This call is for Infinity devices only. To retrieve vent
highest grade alarm for SDC device use WvGetHighestGradeAlarm.
WvListParameters Fills in a list of parameters currently available from the device.
WvDescribeParameter Fills in a structure with data for a given parameter.
WvGetParameterValue Returns the current value (in text format) for a given parameter.
WvListAvailableWave- Fills in a list of all available waveforms from a device.
forms
WvDescribeWaveform Fills in a structure with data for a given waveform.
WvGetWaveformSam- Fills a buffer with samples for the specified waveform.
ples
WvSetFilter Instructs the Infinity Gateway Server to filter the list of waveforms from
a bed to those in the filter list.
WvListWaveforms Fills in a list of waveforms that are currently being acquired from the
device.
WvGetVitalSignsReport Creates a monitoring data report for the specified device.
WvGetLastWinsockError Returns the last error code encountered in a failed Winsock call.
WvLocalTime Provides thread-safe conversion from time_t to struct tm format.
WvGetTrendData Fills a buffer of trend data from the connected Infinity patient monitor
based on the list of parameters and amount of trend hours requested.
Note that SDC-only devices do not support this call.
WvGetTrendMinData Fills a buffer of Trend Data from the connected Infinity patient monitor
based on the list of parameters and amount of trend minutes requested.
Note that SDC-only devices do not support this call.
WVGetAvailableTrends Fills in a list of available trends from the device. This function is not sup-
ported on an SDC-only device.
WvGetGWOptions Returns the options enabled for the server.
WvGetDemographics Fills in the demographic information from device. Note that this function
is not supported on an SDC-only device.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 31

WinAccess API Developer’s Tool

WvAPI.DLL Function Description

WvSetDemographics Modifies the demographic information at the patient monitor, under
certain conditions. Note that this function is not available on SDC-only
devices. In general, the interface will not allow the custom application
to change the primary identification (if any) of the patient.
If the Patient ID field and patient name fields at the bed are blank, then
any of the data can be changed.
If the Patient ID field at the patient monitor is populated, then it cannot
be changed, but all other fields can be changed.
If the Patient ID field at the patient monitor is blank but the Patient
Name is populated, then the Patient Name field cannot be changed, but
all other fields can be.
WvGetVentType Fills in the Vent Type from an Infinity device (if any). This function is not
available on SDC-only devices.
WvGetVentSettings Retrieves Ventilator Parameters, settings, and vent type from the
bedside.
WvGetAllAlarms Returns information for all active or transitioning alarms. This function
is not available for Infinity-only devices.

NOTE
Unless otherwise specified all function calls are valid for Infinity and SDC devices.

Many of the above methods actually have 2 implementations: one that supports ANSI strings and one that
supports Unicode strings. For example, there are two WvListBeds methods supported in the DLL:
WvListBeds_W (supports wide characters or Unicode) and WvListBeds_A (supports single byte ANSI
characters). For compatibility, the definition of WvListBeds is actually mapped to one of those two
methods. The method that WvListBeds is mapped to is driven by whether or not the _UNICODE symbol
is defined or not, If it is defined then WvListBeds represents WvListBeds_W; if the _UNICODE symbol is
not defined, then WvListBeds is equivalent to WvListBeds_A.
The same is true with the structures that are defined in WvAPI.h. For example, WV_BED_LIST can
represent either the WV_BED_LIST_A structure or the WV_BED_LIST_W; again, the decision is made
strictly based on the presence or absence of the _UNICODE define.

32 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 WinAccess API Developer’s Tool

Usage Guidelines

The following usage guidelines apply whether the interface is being used in ANSI or UNICODE mode.
The WvAPI DLL will not work properly if the instructions below are not followed.

NOTE
The interface file WvAPI.h, which is distributed in the WinAccess Option folder on the Infinity Gateway
CD, contains detailed usage guidelines for each method.

 Call WvStart before calling any of the functions to WvAPI DLL. If not, the WV_NOT_INITIALIZED error
return code will appear.
 Call WvStop before exiting from any application that uses WvAPI DLL. Not calling WvStop will cause
memory leaks by leaving a process resident in memory.
 Track open connections to all applications using WvAPI DLL. There is no asynchronous notification
when a connection is lost, and the connection ID for that connection will no longer be valid.
 All the API functions return WV_SUCCESS, if successful, or another return code if not successful.
The following is the correct calling sequence for using the DLL functions when retrieving
waveform, parameter, and trend data:
1 WvStart
2 WvListBeds (repeat periodically to get updated list)
3 Repeat for all the beds you are interested in:
 WvConnect (if not already connected). At this point, a variety of functions can be performed:
 To get alarm data: WvGetHighestGradeAlarm
 To get Ventilator Alarm data: WvGetHighestGradeVentAlarm
 To get parameter data: WvListParameters
 Repeat for all the parameters you are interested in:
- WvDescribeParameter
- WvGetParameterValue
 To get waveform data:
- WvListAvailableWaveforms
- WvSetFilter (set filter according to the waveforms needed)
- Repeat for all the waveforms you are interested in:
- WvDescribeWaveform
- WvGetWaveformSamples

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 33

WinAccess API Developer’s Tool

 To generate vital signs report:

- WvGetVitalSignsReport
Note: Vitals signs report contains patient demographics, monitoring device information, and
parameters data.
 To get trend data:
- WVGetAvailableTrends (optional if not all trends are desired)
- For hour resolution trend Data: WvGetTrendData
- For minute resolution trend data: WvGetTrendMinData
4 WvDisconnect
Note: This should only be called once data no longer needs to be collected from a bedside monitor. It
is recommended that the connection remain open while collecting data continuously from a bedside.
5 WvStop

The following is the correct calling sequence for using the DLL functions when connecting to a
bed to retrieve trends only:
1 WvStart
2 WvListBeds (repeat periodically to get updated list)
3 Repeat for all the beds you are interested in:
 WvTrendConnect (if not already connected). At this point only the request for trends is available:
 WVGetAvailableTrends (optional if not all trends are desired)
- For hour resolution trend Data: WvGetTrendData
- For minute resolution trend data: WvGetTrendMinData
4 WvDisconnect
Note: This should only be called once data no longer needs to be collected from a bedside monitor. It
is recommended that the connection remain open while collecting data continuously from a bedside.
5 WvStop

12-Lead Rest ECG Output

The WinAccess API Developer’s Tool can be utilized to create 12-Lead Rest ECG output files data from
the Infinity CentralStation to a custom application. The location of the file, called 12Lead.ekg, is user
configured. The 12Lead.ekg file format is defined in Appendix H: 12-Lead ECG Output Format.

34 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 HL7 Interfaces

HL7 Interfaces

In the following section “HL7 server” refers to the Infinity Gateway server on which the HL7 service is
installed.

Dräger HL7 Overview

All Infinity HL7 interfaces utilize HL7 Version 2.3, unless otherwise noted, implemented on TCP/IP
connection-oriented sockets, using MLLP as the lower layer message blocking protocol, although some
of the interfaces also accept other versions. All interfaces configured for Unicode also use an extension
of MLLP that uses double byte characters. Refer to the individual interface for more details.
For the purposes of this document, a message consists of an MSH (message segment header) followed
by one or more other segments, depending on the interface being implemented. Only one MSH segment
is contained in each message.

WARNING
The Gateway data access options are information transfer technology. They are intended to make
information from the network available to third party applications. The Gateway data access
options are not intended to be used for alarm monitoring functions.

WARNING
Risk from unauthorized SDC devices.
Other SDC devices in the same IT network can communicate with the device. Access by means
of unauthorized devices must be prevented.
 Establish alternative options (e.g., MAC address filters).

WARNING
When data is used from devices that are not certified by Dräger, this data is considered to be for
informational purposes only. Do not use this data as the sole basis for diagnostic or therapeutic
decisions. Do not use this data for patient monitoring or device monitoring.

HL7 sockets
Two systems are always involved in an HL7 interface. One system is the master and initiates the
connection. The other system is the slave and accepts the connection. Each Infinity interface specifies
whether the Dräger HL7 Server will be the master or slave of the connection. Typically for unsolicited
interfaces, the master is the source of the data being transferred. For a solicited interface, the slave is the
source of the data.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 35

HL7 Interfaces

A connection is opened by specifying the IP address of the Dräger HL7 Server and the port number for
which the interface is configured. There is no restriction on the port to be used. However, the port number
must be supported by the PC platform software and cannot be used by another application. Port 2150 is
reserved by the HL7 server for internal use and is not configurable. Whenever possible, the software
should be configured using the default port settings:

Default Port HL7 Interface

2250 ADT solicited/unsolicited
2350 Stat Lab (ASTM Access)
2450 Lab Import
2550 Vital Signs solicited/unsolicited
2650 Lab Export
3551 Alarm Communication Management

In all Infinity HL7 interfaces, the master sends a message to the slave. After acting upon the message, the
slave responds with an acknowledgment on the same socket. If the acknowledgment code used is AE,
the master resends the message, using the same message control ID for the message. If the message
control ID in the MSA segment of the acknowledgment message does not match the message control ID
of the sent message, the acknowledgment is not recognized as a valid response for that message.

Character Sets Supported

Dräger HL7 interfaces can support either 8-bit characters from the ISO 8859-1 character set or 16-bit
characters from the Unicode (UTF-16) character set. On every supported HL7 interface, there is a setting
(called Messages are in Unicode) which is used to configure which character set to use on that interface.
By default, the character set for each interface is ISO 8859-1.
When the Messages are in Unicode setting is enabled, all messages received on the interface in question
are interpreted as double-byte Unicode UTF-16 strings, including the MLLP blocking characters. When
the setting is disabled, all messages received on the interface are interpreted as single-byte ISO 8859-1
character strings, including the MLLP blocking characters.

CAUTION
– Given the disparity of character length between these two character sets, it is imperative that both
sides of the interface be configured to use the same character set, otherwise, no communication will
ever be successfully established.
– On a Unicode interface, all characters are treated as double byte characters including the ones
defined in MLLP.

36 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 HL7 Interfaces

ISO 8859-1
The characters defined in this coding scheme consist of the (7-bit) ASCII character set as well as the
following character codes:

Unicode (UTF-16)
Although the Gateway supports the entire Unicode character set, the patient monitors only support the
characters that are relevant to the current language setting, so at a given site, the use of characters within
the Unicode set should be limited to those characters that apply to the language that is currently being
used at the patient monitors.

MSH Delimiter Characters

The Dräger implementation of HL7 includes an escape character definition required in every MSH
segment. Although the repeat character is recognized, the HL7 Server only uses the first instance of a
field or component, except where noted.

Minimal Lower Layer Protocol (MLLP)

MLLP is a very simple protocol, consisting of a single character indicating the start of a message, and two
characters indicating the end of the message. A message is always started with the VT character, code
0x0B. A message is always ended with the ASCII FS character, code 0x1C, followed by a carriage return.
A carriage return character is also used to terminate a segment.

Start of Message Message End of Message

0x0B MSH 0x0D segment 0x0D … segment 0x0D 0x1C 0x0D

segment

NOTE
Depending on whether the messages are in Unicode setting, each character may be either one (setting
off) or two (setting on) bytes in length.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 37

HL7 Interfaces

Escape Sequences

Dräger HL7 interfaces support and implement the following escape sequences:

\F\ field separator

\S\ component separator
\T\ subcomponent
separator
\R\ repetition separator
\E\ escape character

\H\, \N\ and \Xddddd\ sequences are not currently supported.

38 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 HL7 Interfaces

Database Usage

HL7 makes use of several database tables for different interfaces/features, as follows:
Interface/Feature Description Tables Consumer of
Data via HL7
Unsolicited ADT Patient demographic t_adt ICS and certain
data patient monitors
t_allergies
t_diagnosis
t_doctor
t_insurance
t_nok
t_picklist
Vitals Signs Patient parameter data *Refer to Parame-
ters Feature
t_acceptableunits
t_itemconversions
t_picklist
t_units
ADT configuration ADT mapping tables for t_Picklist Gateway
race, religion,
nationality, primary
language and ethnicity
HL7 Lab Import/ Parameter Priority and t_lab_group Gateway and
ASTM Lab Import Grouping patient monitors
t_lab_param
Calculator mapping

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 39

HL7 Interfaces

Interface/Feature Description Tables Consumer of

Data via HL7
Parameters Parameter definitions t_params Gateway
t_VmdRefIds
t_ChannelRefIds
t_MetricRefIds
t_wvresources_br
t_wvresources_da
t_wvresources_de
t_wvresources_en
t_wvresources_es
t_wvresources_fi
t_wvresources_fr
t_wvresources_it
t_wvresources_nl
t_wvresources_no
t_wvresources_pl
t_wvresources_ru
t_wvresources_sv
Character Mapping User-defined Unicode t_charmap Gateway
to single byte charac-
t_charmap_list
ter maps used in HL7
Lab Import and Pager

HL7 accesses the databases using ADO. These databases are stored in SQL Server 2017 Standard data-
bases, however SQL Server 2017 Express, SQL Server 2019 Express, and SQL Server 2019 Standard
are also supported.

Interface Customization

All of the Dräger interfaces allow customization by manipulating fields in incoming and outgoing
messages. For more details, please refer to the on-line help of the HL7Sim application.

40 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

Unsolicited Vital Signs Export

The HL7/ASTM Interface Option enables the export of vital signs data in an unsolicited Observation
Results message (ORU).One ORU message is sent for each patient at a fixed configurable update rate.
If the “HL7 Vital Signs Interface - High Speed” locked option is enabled, the interval range is 5 - 6000
seconds. If the “HL7 Vital Signs Interface - Standard” locked option is enabled, the allowed interval range
is 60 - 6000 seconds.
Upon receipt of an ORU message, the receiving system should acknowledge receipt with an ACK
message. Refer to "Dräger HL7 Overview" on page 35 for details on HL7 interfaces.
For the Unsolicited Vital Signs Export interface, Dräger initiates the connection.

NOTE
The solicited and unsolicited Vitals Interfaces are mutually exclusive.

ORU - Unsolicited Observation Report

ORU messages follow the format below. The curved brackets ‘{and}’ indicate segments which may be
repeated.

Segments Description
MSH MSH Segment - Message Header
PID PID Segment - Patient Identification
PV1 PV1 Segment - Patient Visit
OBR OBR Segment - Observation Request
{OBX} OBX Segment - Observation/Result

See ACK – Acknowledgment for a description of the acknowledgment message expected from the
receiving application. If no acknowledgment is received within the Response Timeout configured in the
HL7 Vital Signs Interface Configuration screen, the message will be retransmitted up to Retry Count times.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 41

Unsolicited Vital Signs Export

MSH Segment - Message Header

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00001 Field R ST 1 “|”. R 1
Separator
2 00002 Encoding R ST 4 “^~\&” R 4
Characters
3 00003 Sending O HD 180 “Infinity” O 16
Application
4 00004 Sending O HD 180 <not used>
Facility
5 00005 Receiving O HD 180 “NUR” by O 180
Application default. Field is
configurable.
6 00006 Receiving O HD 180 “” by default. O 180
Facility Field is
configurable.
7 00007 Date/Time of O TS 26 YYYYMMDDH O 12
Message Hmmss
<offset>
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ORU^R01^OR R 7
U_R01”
10 00010 Message R ST 20 A number R 20
Control ID uniquely
identifying the
message. The
receiving
system echoes
this ID back to
the sending
system in the
message
acknowledgme
nt segment
(MSA).
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer

42 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

MSH Segment - Message Header (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
15 00015 Accept O ID 2 “AL” R 2
Acknowledgm
ent Type
16 00016 Application O ID 2 “NE” R 2
Acknowledgm
ent
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal O CD 60 <not used>
Language Of
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 43

Unsolicited Vital Signs Export

PID Segment - Patient Identification

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00104 Set ID - O SI 4 <not used>
Patient ID
2 00105 Patient ID O CX 20 <not used>
(External ID)
3 00106 Patient ID R CX 20 See Patient Identifiers R 12
(Internal ID)
4 00107 Alternate O CX 20 <not used>
Patient ID -
PID
5 00108 Patient Name R XPN 48 See Patient Name O 32
6 00109 Mother’s O XPN 48 *"Last^First^ Middle^ " O 250
Maiden Name
7 00110 Date/Time of O TS 26 *YYYYMMDDhhmmss O 24
Birth
8 00111 Sex O IS 1 *"Code^Text" O 705
Taken from ADT
Configuration
Information.
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 26 *"Code^Text" O 705
Taken from ADT
Configuration
Information.
11 00114 Patient O XAD 1 *"Street1^Street2^City O 250
Address ^State^Zip
Code^Country^M"
12 00115 County Code B IS 48 <not used>
13 00116 Phone O XTN 1 <not used>
Number -
Home
14 00117 Phone O XTN 106 <not used>
Number -
Business
15 00118 Primary O CE 4 *"Code^Text"
Language
Taken from ADT
Configuration
Information.

44 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

PID Segment - Patient Identification (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
16 00119 Marital Status O IS 40 *"Code^Text" O 40
Taken from ADT
Configuration
Information.
17 00120 Religion O IS 40 *"Code^Text" O 40
Taken from ADT
Configuration
Information.
18 00121 Patient O CX 60 See Patient Identifiers O 12
Account
Number
19 00122 SSN Number - O ST 16 *National ID O 16
Patient
20 00123 Driver's O CM 25 <not used>
License
Number -
Patient
21 00124 Mother's O CX 20 <not used>
Identifier
22 00125 Ethnic Group O IS 3 *"Code^Text" O 3
Taken from ADT
Configuration
Information.
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth O ID 2 <not used>
Indicator
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans O CE 60 <not used>
Military Status
28 00131 Nationality O CE 80 *"Code^Text" O 80
Taken from ADT
Configuration
Information.
29 00132 Patient Death O TS 26 <not used>
Date and Time
30 00133 Patient Death O ID 1 <not used>
Indicator

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 45

Unsolicited Vital Signs Export

NOTE
All items with an asterisk * are only sent out when the “ADT Data in Message” option is enabled for unso-
licited vitals, and data is found for the patient.Otherwise the fields are <not used>.

Patient Identifiers
Depending on the configuration of the primary identifier, the Patient ID field that appears in the Patient
Admit screen of Infinity patient monitors and at the Infinity CentralStation, is interpreted as either a Medical
Record number or a Patient Account number (i.e. visit number).
If the "ADT Data in Message" option is enabled and then a search of the ADT records will be performed
to find a record that contains the primary identifier. If the record is found and it contains a secondary ID
and/or the corresponding assigning authority then this information will be used in the message. Otherwise
the assigning authority and secondary ID fields will be blank. Field 3 and field 18 of the outgoing
message’s PID segment will be populated as follows:

InterpretPatient Field 3 contents Field 18 contents

ID asSetting
MRN <MRN>^^^<Assigning Authority>^MR "<Patient Account#>"
Patient Account # If "ADT Data in Message" is enabled and "<Patient Account#>"
there is a record in the database for the
patient that contains an MRN then the field
contains
<MRN>^^^<Assigning Authority>^MR
otherwise the field contains
<Patient Account#>^^^^AN

Patient Name
Patient Name is in the format “Last^First^Middle”. For proper parsing, users of an Infinity patient monitor
should be instructed to enter the Patient Name in the “<Last>,<First> <Middle>” format. If no Patient Name
is entered on the Admit screen, this field will contain “UNKNOWN”.

PV1 Segment - Patient Visit

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 O SI 4 <not used>
2 00132 Patient Class R IS 1 *Patient Class

46 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

PV1 Segment - Patient Visit (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
3 00133 Assigned O PL 80 Location of the R 18
Patient patient, in format
Location <Care Unit
Label>^^<Bed
Label>^<hospital>.
Fields are as
defined during
monitor
configuration.
4 00134 Admission O IS 2 <not used>
Type
5 00135 Preadmit O CX 20 <not used>
Number
6 00136 Prior Patient O PL 80 <not used>
Location
7 00137 Attending O XCN 60 *"^Last Name ^First O 60
Doctor Name ^Middle Name
^Suffix^Prefix
^Degree"
8 00138 Referring O XCN 60 *"^Last Name ^First O 60
Doctor Name ^Middle Name
^Suffix^Prefix
^Degree"
9 00139 Consulting O XCN 60 *"^Last Name ^First O 60
Doctor Name ^Middle Name
^Suffix^Prefix
^Degree"
10 00140 Hospital O IS 3 <not used>
Service
11 00141 Temporary O PL 80 <not used>
Location
12 00142 Preadmit Test O IS 2 <not used>
Indicator
13 00143 Readmission O IS 2 <not used>
Indicator
14 00144 Admit Source O IS 3 <not used>
15 00145 Ambulatory O IS 2 <not used>
Status
16 00146 VIP Indicator O IS 2 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 47

Unsolicited Vital Signs Export

PV1 Segment - Patient Visit (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
17 00147 Admitting O XCN 60 *"^Last Name ^First O 60
Doctor Name ^Middle Name
^Suffix^Prefix
^Degree"
18 00148 Patient Type O IS 2 <not used>
19 00149 Visit Number O CX 20 <not used>
20 00150 Financial Class O CM 50 <not used>
21 00151 Charge Price O IS 2 <not used>
Indicator
22 00152 Courtesy Code O IS 2 <not used>
23 00153 Credit Rating O IS 2 <not used>
24 00154 Contract Code O IS 2 <not used>
25 00155 Contract O DT 8 <not used>
Effective Date
26 00156 Contract O NM 12 <not used>
Amount
27 00157 Contract Period O NM 3 <not used>
28 00158 Interest Code O IS 2 <not used>
29 00159 Transfer to Bad O IS 1 <not used>
Debt Code
30 00160 Transfer to Bad O DT 8 <not used>
Debt Date
31 00161 Bad Debt O IS 10 <not used>
Agency Code
32 00162 Bad Debt O NM 12 <not used>
Transfer
Amount
33 00163 Bad Debt O NM 12 <not used>
Recovery
Amount
34 00164 Delete Account O IS 1 <not used>
Indicator
35 00165 Delete Account O DT 8 <not used>
Date
36 00166 Discharge O IS 3 <not used>
Disposition
37 00167 Discharged to O CM 25 <not used>
Location
38 00168 Diet Type O IS 2 <not used>

48 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

PV1 Segment - Patient Visit (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
39 00169 Servicing O IS 2 <not used>
Facility
40 00170 Bed Status B IS 1 <not used>
41 00171 Account Status O IS 2 <not used>
42 00172 Pending O PL 80 <not used>
Location
43 00173 Prior O PL 80 <not used>
Temporary
Location
44 00174 Admit O TS 26 *YYYYMMDDhhm O 24
Date/Time mss
45 00175 Discharge O TS 26 <not used>
Date/Time
46 00176 Current Patient O NM 12 <not used>
Balance
47 00177 Total Charges O NM 12 <not used>
48 00178 Total O NM 12 <not used>
Adjustments
49 00179 Total Payments O NM 12 <not used>
50 00180 Alternate Visit O CX 20 <not used>
ID
51 01226 Visit Indicator O IS 1 <not used>
52 01224 Other O XCN 60 <not used>
Healthcare
Provider

NOTE
All items with an asterisk * are only sent out when the “ADT Data in Message” option is enabled for unso-
licited vitals and data is found for the patient. Otherwise the fields are <not used>.

OBR Segment - Observation Request

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00237 Set ID - OBR C SI 4 <not used>
2 00216 Placer Order C EI 75 <not used>
Number
3 00217 Filler Order C EI 75 <not used>
Number +

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 49

Unsolicited Vital Signs Export

OBR Segment - Observation Request (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
4 00238 Universal Service R CE 200 <not used>
ID
5 00239 Priority B ID 2 <not used>
6 00240 Requested B TS 26 <not used>
Date/time
7 00241 Observation C TS 26 Date/time the R 14
Date/Time # observation is
obtained from the
Infinity Network,
in format
YYYYMMDDHH
mmss.
8 00242 Observation End O TS 26 <not used>
Date/Time
9 00243 Collection O CQ 20 <not used>
Volume
10 00244 Collector O XCN 60 <not used>
Identifier
11 00245 Specimen Action O ID 1 <not used>
Code
12 00246 Danger Code O CE 60 <not used>
13 00247 Relevant Clinical O ST 300 <not used>
Info.
14 00248 Specimen C TS 26 <not used>
Received
Date/Time
15 00249 Specimen Source O CM 300 <not used>
16 00226 Ordering O XCN 80 <not used>
Provider
17 00250 Order Callback O XTN 40 <not used>
Phone Number
18 00251 Placer field 1 O ST 60 <not used>
19 00252 Placer field 2 O ST 60 <not used>
20 00253 Filler Field 1 + O ST 60 <not used>
21 00254 Filler Field 2 + O ST 60 <not used>
22 00255 Results C TS 26 <not used>
Report/Status
Change
Date/Time +

50 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

OBR Segment - Observation Request (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
23 00256 Charge to O CM 40 <not used>
Practice +
24 00257 Diagnostic O ID 10 <not used>
Service Section
ID
25 00258 Result Status + C ID 1 <not used>
26 00259 Parent Result + O CM 400 <not used>
27 00221 Quantity/Timing O TQ 200 <not used>
28 00260 Result Copies To O XCN 150 <not used>
29 00261 Parent O CM 150 <not used>
30 00262 Transportation O ID 20 <not used>
Mode
31 00263 Reason for Study O CE 300 <not used>
32 00264 Principal Result O CM 200 <not used>
Interpreter +
33 00265 Assistant Result O CM 200 <not used>
Interpreter +
34 00266 Technician + O CM 200 <not used>
35 00267 Transcriptionist + O CM 200 <not used>
36 00268 Scheduled O TS 26 <not used>
Date/Time +
37 01028 Number of O NM 4 <not used>
Sample
Containers
38 01029 Transport O CE 60 <not used>
Logistics of
Collected Sample
39 01030 Collector's O CE 200 <not used>
Comment
40 01031 Transport O CE 60 <not used>
Arrangement
Responsibility
41 01032 Transport O ID 30 <not used>
Arranged
42 01033 Escort Required O ID 1 <not used>
43 01034 Planned Patient O CE 200 <not used>
Transport
Comment

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 51

Unsolicited Vital Signs Export

OBX Segment - Observation/Result

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00569 Set ID – OBX O SI 10 <not used>
2 00570 Value Type C ID 2 “SN” (structured R 2
numeric) if the
parameter value
reported by the
device is numeric,
otherwise “ST”
(string).
3 00571 Observation R CE 590 See Observation R
Identifier Identifier
4 00572 Observation C ST 20 <not used>
Sub-ID
5 00573 Observation C * 6553 See Observation R 30
Value 6 Value
6 00574 Units O CE 60 Uniquely identifies O 30
the units in which
the parameter is
being reported, in
the format
<identifier>^^ISO
+. The identifier is
the HL7 code as
shown in
Appendix B: Units
of Measure.
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal O ID 5 <not used>
Flags
9 00577 Probability O NM 5 <not used>
10 00578 Nature of O ID 2 <not used>
Abnormal Test
11 00579 Observation R ID 1 “R” R 1
Result Status
12 00580 Date Last O TS 26 <not used>
Observation
Normal Values
13 00581 User Defined O ST 20 <not used>
Access
Checks
14 00582 Date/Time of O TS 26 YYYYMMDDHHm O 12
the mss
Observation

52 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

OBX Segment - Observation/Result (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method
18 01479 Equipment O EI 427 <Unique
Instance ID>^<model>^<m
Identifier anufacturer
url>^<universal id
type>
If a serial number
is received, then a
unique ID will be
the serial number;
otherwise it will be
the unique
identifier of the
device.

Observation Identifier
Uniquely identifies the parameter being reported, in the format:
<identifier1^^local^<<identifier2>&<instance >>^^<coding system >

identifier1 Dräger label for the parameter (for example HR)

identifier2 LOINC or MIB/CEN code for the parameter
instance instance of usage for the LOINC or MIB/CEN code
coding system “LOINC” if identifier2 is a LOINC code
“MIB/CEN” if identifier2 is an MIB/CEN code

MIB/CEN codes are only sent when there is no LOINC code that denotes the parameter. Refer to
Appendix A: Parameters for a list of parameters available on the Infinity Network, including LOINC and
MIB/CEN codes.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 53

Unsolicited Vital Signs Export

Observation Value
The parameter value as reported by the device. The format of this field varies according to the Value Type
field.

Value Type Observation Value Field Format Comments

ST <value> See Appendix C: Special Display Values for
special value strings
SN <comparator>^<value> comparator is “=”

ACK – Acknowledgment

After transmission of an ORU message, an acknowledgment is expected:

Segment Description
MSH MSH Segment - Message Header
MSA MSA Segment – Message Acknowledgment

See ORU - Unsolicited Observation Report for a description of the ORU message being acknowledged.

54 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

MSH Segment - Message Header

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 Recommended R 1
value is “|”
2 00002 Encoding R ST 4 Four characters R 4
Characters in the following
order: the
component
separator, the
repetition
separator, the
escape
character, and
the
subcomponent
separator.
Recommended
values are
“^~\&”.
3 00003 Sending O HD 180 A string O 16
Application identifying the
sending
application.
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of O TS 26 YYYYMMDDHH O 12
Message mm
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ACK^R01” R 7
10 00010 Message Control R ST 20 A number or R 20
ID other identifier
uniquely
identifying the
message.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointe

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 55

Unsolicited Vital Signs Export

MSH Segment - Message Header (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
15 00015 Accept O ID 2 <not used>
Acknowledgment
Type
16 00016 Application O ID 2 <not used>
Acknowledgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal O CE 60 <not used>
Language Of
Message

56 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

MSA Segment – Message Acknowledgment

HL7 HL7 Dräger
Seq Item # Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 See R 1
Code Acknowledgment
Codes
2 00010 Message Control R ST 20 The message R 4
ID control ID of the
message it is
acknowledging.
3 00020 Text Message O ST 80 An error or status O 80
string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledgment
Type
6 00023 Error Condition O CE 100 <not used>

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
AE Original mode: Application Error
AR Original mode: Application Reject
CA Enhanced mode: Commit Accept
CE Enhanced mode: Commit Error
CR Enhanced mode: Commit Reject

Sample ORU Message

MSH|^~\&|Infinity||NUR||200212021207||ORU^R01|02110212073000458038|P|2.3
PID|||999-99-9999^AN||Smith^John^L|||||||||||||999-99-9999
PV1|||CU1^^BED1||||^^^|||||||||||||||||||||||||||||||||||||
OBR|||||||20021202120235
OBX||SN|STIII^^local^10123-8&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235
OBX||SN|STaVR^^local^10120-4&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235
OBX||SN|STaVF^^local^10118-8&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 57

Unsolicited Vital Signs Export

OBX||SN|STaVL^^local^10119-6&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235
OBX||SN|STV^^local^14692&1^^MIB/CEN||=^0.01|mv^^ISO+|||||R|||20021202120235
OBX||ST|PPR^^local^8893-0&1^^LOINC|| |mm(hg)^^ISO+|||||R|||20021202120235
OBX||SN|PA D^^local^8385-7&1^^LOINC||=^1.8|kpa^^ISO+|||||R|||20021202120235
OBX||SN|PA S^^local^8440-0&1^^LOINC||=^4.4|kpa^^ISO+|||||R|||20021202120235
OBX||SN|PA M^^local^8414-5&1^^LOINC||=^2.8|kpa^^ISO+|||||R|||20021202120235
OBX||ST|PWP^^local^8587-8&1^^LOINC|| |kpa^^ISO+|||||R|||20021202120235
OBX||SN|CVP^^local^8591-0&1^^LOINC||=^2.0|kpa^^ISO+|||||R|||20021202120235
OBX||SN|RA^^local^8400-4&1^^LOINC||=^2.0|kpa^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Med^^local^22912&1^^MIB/CEN||=^10.0|hz^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 SEF^^local^22920&1^^MIB/CEN||=^12.5|hz^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 BSR^^local^&1^^MIB/CEN||=^30|%^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Power^^local^22968&1^^MIB/CEN||=^67|dB^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Beta^^local^23000&1^^MIB/CEN||=^30|%^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Alpha^^local^22996&1^^MIB/CEN||=^20|%^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Theta^^local^23008&1^^MIB/CEN||=^25|%^^ISO+|||||R|||20021202120235
OBX||SN|EEG1 Delta^^local^23004&1^^MIB/CEN||=^25|%^^ISO+|||||R|||20021202120235
OBX||SN|etCO2*^^local^20824&2^^MIB/CEN||=^5.0|%^^ISO+|||||R|||20021202120235
OBX||SN|iCO2*^^local^20644&2^^MIB/CEN||=^0.0|%^^ISO+|||||R|||20021202120235
OBX||SN|RRc*^^local^9279-1&4^^LOINC||=^20|/min^^ISO+|||||R|||20021202120235
OBX||SN|etO2^^local^20844&2^^MIB/CEN||=^33|%^^ISO+|||||R|||20021202120235
OBX||SN|iO2^^local^3150-0&2^^LOINC||=^35|%^^ISO+|||||R|||20021202120235
OBX||SN|etN2O^^local^21036&2^^MIB/CEN||=^58|%^^ISO+|||||R|||20021202120235
OBX||SN|iN2O^^local^21120&2^^MIB/CEN||=^60|%^^ISO+|||||R|||20021202120235
OBX||SN|etHAL^^local^21020&2^^MIB/CEN||=^0.9|%^^ISO+|||||R|||20021202120235
OBX||SN|iHAL^^local^21104&2^^MIB/CEN||=^1.1|%^^ISO+|||||R|||20021202120235
OBX||SN|et ISO^^local^21028&2^^MIB/CEN||=^1.3|%^^ISO+|||||R|||20021202120235
OBX||SN|i ISO^^local^21112&2^^MIB/CEN||=^1.5|%^^ISO+|||||R|||20021202120235
OBX||SN|etENF^^local^21016&2^^MIB/CEN||=^1.8|%^^ISO+|||||R|||20021202120235
OBX||SN|iENF^^local^21100&2^^MIB/CEN||=^2.0|%^^ISO+|||||R|||20021202120235
OBX||SN|etSEV^^local^21024&2^^MIB/CEN||=^1.9|%^^ISO+|||||R|||20021202120235
OBX||ST|NBP S^^local^8508-4&1^^LOINC|| |kpa^^ISO+|||||R|||20021202120235

58 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited Vital Signs Export

OBX||ST|NBP D^^local^8496-2&1^^LOINC|| |kpa^^ISO+|||||R|||20021202120235

OBX||ST|NBP M^^local^8502-7&1^^LOINC|| |kpa^^ISO+|||||R|||20021202120235
OBX||SN|SpO2^^local^2710-2&1^^LOINC||=^97|%^^ISO+|||||R|||20021202120235
OBX||SN|PLS^^local^8889-8&1^^LOINC||=^83|/min^^ISO+|||||R|||20021202120235
OBX||SN|etDES^^local^21012&2^^MIB/CEN||=^6.9|%^^ISO+|||||R|||20021202120235
OBX||SN|iDES^^local^21096&2^^MIB/CEN||=^7.1|%^^ISO+|||||R|||20021202120235
OBX||SN|iSEV^^local^21108&2^^MIB/CEN||=^2.1|%^^ISO+|||||R|||20021202120235
OBX||SN|ART S^^local^8480-6&1^^LOINC||=^22.2|kpa^^ISO+|||||R|||20021202120235
OBX||SN|ART D^^local^8462-4&1^^LOINC||=^9.2|kpa^^ISO+|||||R|||20021202120235
OBX||SN|ART M^^local^8478-0&1^^LOINC||=^14.1|kpa^^ISO+|||||R|||20021202120235
OBX||SN|mib PIP^^local^20885&1^^MIB/CEN||=^60|cmh2O^^ISO+|||||R|||20021202120235
OBX||SN|mib MAP^^local^20720&1^^MIB/CEN||=^20|cmh2O^^ISO+|||||R|||20021202120235
OBX||SN|mib PEEP^^local^20732&1^^MIB/CEN||=^0|cmh2O^^ISO+|||||R|||20021202120235
OBX||SN|HR^^local^8867-4&1^^LOINC||=^83|/min^^ISO+|||||R|||20021202120235
OBX||ST|%PACED^^local^&1^^MIB/CEN|| |%^^ISO+|||||R|||20021202120235
OBX||ST|ARR^^local^03266&1^^MIB/CEN|| |/min^^ISO+|||||R|||20021202120235
OBX||SN|PVC/min^^local^&1^^MIB/CEN||=^0|/min^^ISO+|||||R|||20021202120235
OBX||SN|STI^^local^10121-2&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235
OBX||SN|STII^^local^10122-0&1^^LOINC||=^0.01|mv^^ISO+|||||R|||20021202120235

Sample Acknowledgment

MSH|^~\&|NUR||Infinity||200212021207||ACK^R01|99011716090716963683|P|2.3
MSA|AA|02110212073000458038|

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 59

 This page has been left blank intentionally.

60 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

Unsolicited IEEE 11073 Vital Signs Export

The HL7/ASTM Interface Option enables the export of vital signs data in an unsolicited Observation
Results message (ORU) supporting HL7 version V2.6. The data is sent using IEEE nomenclature. Some
messages may not contain all data or too much data to be considered compliant with the IHE PCD DEC
profile. The interface can be configured to be IHE PCD DEC compliant. One ORU message is sent for
each patient at a fixed configurable update rate.
If the “HL7 Vital Signs Interface - High Speed” locked option is enabled, the interval range is 5 - 6000
seconds. If the “HL7 Vital Signs Interface - Standard” locked option is enabled, the interval range allowed
is 60 - 6000 seconds.
Upon receipt of an ORU message, the receiving system should acknowledge receipt with an ACK
message. Refer to Dräger HL7 Overview for details on HL7 interfaces.
For the Unsolicited Vital Signs Export interface, Dräger initiates the connection.

ORU - Unsolicited Observation Report

ORU messages follow the format below. The curved brackets ‘{‘ and ‘}’ indicate segments which may be
repeated.

Segments Description
MSH MSH Segment – Message Header
PID PID Segment - Patient Identification
PV1 PV1 Segment - Patient Visit
OBR OBR Segment - Observation Request
{OBX} OBX Segment - Observation/Result

See ACK – Acknowledgment for a description of the acknowledgment message expected from the
receiving application. If no acknowledgment is received within the Response Timeout configured in the
HL7 Vital Signs Interface Configuration screen, the message will be retransmitted up to Retry Count times.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 61

Unsolicited IEEE 11073 Vital Signs Export

MSH Segment – Message Header

HL7 Dräger
HL7
Seq
Item #
Description Req Type Len Contents Req Len

1 00001 Field Separator R ST 1 “|” R 1

2 00002 Encoding Charac- R ST 4 “^~\&” R 4
ters
3 00003 Sending Application R HD 227 "INFO_S- R 16
RC_DRAE-
GER^0030E6000
0000001^EUI-64"
4 00004 Sending Facility RE HD 227 "Draeger" R 16
5 00005 Receiving Applica- RE HD 227 Configurable in R 227
tion Infinity Gateway
Configuration
6 00006 Receiving Facility RE HD 227 Configurable in R 227
Infinity Gateway
Configuration
7 00007 Date/Time of Mes- R DTM 24 YYYYMMD- O 12
sage DHHmmss+/-
ZZZZ
8 00008 Security X ST 40 <not used>
9 00009 Message Type R MSG 15 “ORU R 7
^R01^ORU_R01”
10 00010 Message Control ID R ST 199 A number or R 20
other identifier
uniquely
identifying the
message.
The receiving
system
echoes this ID
back to the
sending system
in the
message
acknowledgment
segment
(MSA).
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R VID 60 “2.6” R 8
13 00013 Sequence Number RE NM 15 <not used>
14 00014 Continuation X ST 180 <not used>
Pointer

62 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

MSH Segment – Message Header (Continued)

HL7 Dräger
HL7
Seq
Item #
Description Req Type Len Contents Req Len

15 00015 Accept Acknowl- R ID 2 "AL"

edgment Type
16 00016 Application R ID 2 "NE" R 2
Acknowledgment
Type
17 00017 Country Code RE ID 3 <not used>
18 00692 Character Set RE ID 16 8859/1
19 00693 Principal Language RE CWE 705 "en^English^ISO6
Of Message 39"
20 Alternate Charac- X ID 20 <not used>
ter Set Handling
Scheme
21 Message Profile O EI 427 "IHE_PC- R 427
Identifier D_001^IHE
PCD^1.3.6.1.4.1.
19376.1.6.1.1.1^I
SO"
22 Sending Responsi- X XON 567 <not used>
ble Organization
23 Receiving Respon- X XON 567 <not used>
sible Organization
24 Sending Network X HD 227 <not used>
Address
25 Receiving Network X HD 227 <not used>
Address

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 63

Unsolicited IEEE 11073 Vital Signs Export

PID Segment - Patient Identification

Seq HL7 Dräger

Description Req Type Len Contents Req Len
1 Set ID - PID X SI 4 <not used>
2 Patient ID X CX 20 <not used>
3 Patient List C CX 250 This field may contain an MRN and/or R 12
a Patient Account number, as it is a
repeat field. When the MRN is
available, the format is:
<MRN>^^^<Assigning Authority>^MR
When the patient account number is
available, it will appear in the format:
<Patient Account#>^^^^AN
4 Alternate Patient ID - X CX 20 <not used>
PID
5 Patient Name C XPN 250 "Last^First^Middle^^^^<Type>" Type R 250
is either U or L if the last name is not
blank
6 Mother’s Maiden Name RE XPN 250 *"Last^First^Middle^^^^<Type>" Type R 250
is either U or L if the last name is not
blank
7 Date/Time of Birth RE DTM 24 *YYYYMMDDhhmmss R 24
8 Administrative Sex RE IS 705 For Non IHE Compliant: R 705
*"Code^Text" Taken from ADT
Configuration Information.

For IHE Compliant:

*"Code" Taken from ADT Configura-
tion Information.
9 Patient Alias X XPN 250 <not used>
10 Race RE CWE 705 *"Code^Text" Taken from ADT Con- R 705
figuration Information.
11 Patient Address RE XAD 250 *"Street1^Street2^City^State^Zip R 250
Code^Country^M"
12 County Code RE IS 4 <not used>
13 Phone Number - Home RE XTN 250 <not used> R
14 Phone Number - Busi- X XTN 250 <not used>
ness
15 Primary Language RE CWE 705 *"Code^Text" Taken from ADT Con-
figuration Information.
16 Marital Status RE CWE 705 *"Code^Text" Taken from ADT Con- R 705
figuration Information.

64 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

PID Segment - Patient Identification (Continued)

Seq HL7 Dräger

Description Req Type Len Contents Req Len
17 Religion RE CWE 705 *"Code^Text" Taken from ADT Con- R 705
figuration Information.
18 Patient Account Num- RE CX 705 <Patient Account #> R 12
ber
19 SSN Number - Patient X ST 16 If IHE compliant, <not used>, R 16
else "*National ID"
20 Driver's License Num- RE DLN 25 <not used>
ber - Patient
21 Mother’s Identifier RE CX 705 <not used>
22 Ethnic Group RE CWE 705 *"Code^Text" Taken from ADT Con-
figuration Information.
23 Birth Place RE ST 705 <not used>
24 Multiple Birth Indicator RE ID 1 <not used>
25 Birth Order RE NM 2 <not used>
26 Citizenship RE CWE 705 <not used>
27 Veterans Military Status RE CWE 705 <not used>
28 Nationality RE CWE 705 *"Code^Text" Taken from ADT Con-
figuration Information.
29 Patient Death Date and RE DTM 24 <not used>
Time
30 Patient Death RE ID 1 <not used>
Indicator
31 Identity Unknown Indi- RE ID 1 <not used>
cator
32 Identity Reliability Code RE IS 20 <not used>
33 Last Update Date/Time RE DTM 24 <not used>
34 Last Update Facility RE HD 241 <not used>
35 Species Code RE CWE 705 <not used>
36 Breed Code C CWE 250 <not used>
37 Strain C ST 80 <not used>
38 Production Class Code RE CWE 705 <not used>
39 Tribal Citizenship RE CWE 705 <not used>

NOTE
All items with an asterisk * are only sent out when the “ADT Data in Message” option is enabled for unso-
licited vitals, and data is found for the patient.Otherwise the fields are <not used>.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 65

Unsolicited IEEE 11073 Vital Signs Export

PV1 Segment - Patient Visit

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 X SI 4 <not used>
2 00132 Patient Class R IS 1 *Patient Class R 1
3 00133 Assigned RE PL 80 <Care Unit
Patient Loca- Label>^^<Bed
tion Label>^<Hospi-
tal/Facility>
4 00134 Admission X IS 2 <not used> R 18
Type
5 00135 Preadmit Num- X CX 250 <not used>
ber
6 00136 Prior Patient X PL 80 <not used>
Location
7 00137 Attending Doc- X XCN 250 If IHE Compliant O 250
tor <not used>, other-
wise *"^Last
Name^First
Name^Middle
Name^Suffic^Pre-
fix^Degree"
8 00138 Referring Doc- X XCN 250 If IHE cCompliant O 250
tor <Nnot used>, oth-
erwise *"^Last
Name^First
Name^Middle
Name^Suffic^Pre-
fix^Degree"
9 00139 Consulting X XCN 250 If IHE Compliant O 250
Doctor <not used>, other-
wise *"^Last
Name^First
Name^Middle
Name^Suffix^Pre-
fix^Degree"
10 00140 Hospital Ser- X IS 3 <not used>
vice
11 00141 Temporary X PL 80 <not used>
Location
12 00142 Preadmit Test X IS 2 <not used>
Indicator
13 00143 Readmission X IS 2 <not used>
Indicator
14 00144 Admit Source X IS 6 <not used>

66 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
15 00145 Ambulatory X IS 2 <not used>
Status
16 00146 VIP Indicator X IS 2 <not used>
17 00147 Admitting Doc- X XCN 250 If IHE Compliant O 250
tor <not used>, oth-
erwise *"^Last
Name^First
Name^Middle
Name^Suffic^Pre-
fix^Degree"
18 00148 Patient Type X IS 2 <not used>
19 00149 Visit Number RE CX 250 <not used>
20 00150 Financial Class X FC 50 <not used>
21 00151 Charge Price X IS 2 <not used>
Indicator
22 00152 Courtesy Code X IS 2 <not used>
23 00153 Credit Rating X IS 2 <not used>
24 00154 Contract Code X IS 2 <not used>
25 00155 Contract Effec- X DT 8 <not used>
tive Date
26 00156 Contract X NM 12 <not used>
Amount
27 00157 Contract Period X NM 3 <not used>
28 00158 Interest Code X IS 2 <not used>
29 00159 Transfer to Bad X IS 4 <not used>
Debt Code
30 00160 Transfer to Bad X DT 8 <not used>
Debt Date
31 00161 Bad Debt X IS 10 <not used>
Agency Code
32 00162 Bad Debt X NM 12 <not used>
Transfer
Amount
33 00163 Bad Debt X NM 12 <not used>
Recovery
Amount
34 00164 Delete Account X IS 1 <not used>
Indicator
35 00165 Delete Account X DT 8 <not used>
Date

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 67

Unsolicited IEEE 11073 Vital Signs Export

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
36 00166 Discharge Dis- X IS 3 <not used>
position
37 00167 Discharged to X DLD 47 <not used>
Location
38 00168 Diet Type X CWE 705 <not used>
39 00169 Servicing Facil- X IS 2 <not used>
ity
40 00170 Bed Status X IS 1 <not used>
41 00171 Account Status X IS 2 <not used>
42 00172 Pending Loca- X PL 80 <not used>
tion
43 00173 Prior Tempo- X PL 80 <not used>
rary Location
44 00174 Admit RE DTM 24 YYYYMMD- R 24
Date/Time Dhhmmss
45 00175 Discharge X DTM 24 <not used>
Date/Time
46 00176 Current Patient X NM 12 <not used>
Balance
47 00177 Total Charges X NM 12 <not used>
48 00178 Total Adjust- X NM 12 <not used>
ments
49 00179 Total Payments X NM 12 <not used>
50 00180 Alternate Visit X CX 250 <not used>
ID
51 01226 Visit Indicator RE IS 1 <not used>

NOTE
All items with an asterisk * are only sent out when the “ADT Data in Message" option is enabled, and
data is found for the patient. Otherwise the fields are <not used>.

68 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

OBR Segment - Observation Request

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00104 Set ID OBR R SI 4 Observation Set Number R 4
2 00105 Placer Order Num- C EI 427 <not used>
ber
3 00106 Filler Order Num- R EI 427 <OrderNumber>^ <Order R 427
ber Application>
^0030E60000000001^EU
I-64
4 00107 Universal Service R CWE 705 "182777000^monitoring R 40
Identifier of patient^SCT"
5 00108 Priority - OBR X ID 2 <not used>
6 00109 Requested X DTM 24 <not used>
Date/Time
7 00110 Observation RE DTM 24 YYYYMMDDhhmmss R 24
Date/Time
8 00111 Observation End RE DTM 24 <not used>
Date / Time
9 00112 Collection Volume X CQ 722 <not used>
10 00113 Collection Identi- R2 XCN 3220 <not used>
fier

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 69

Unsolicited IEEE 11073 Vital Signs Export

OBX Segment - Observation/Result

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – OBX R SI 4 Numeric Set ID R 4
2 00002 Value Type C ID 3 “NM” (Numeric) if the parameter R 2
value reported by the device is
numeric, otherwise “ST” (string).
3 00003 Observation R CWE 705 For IHE Compliant R 20
Identifier Setting: <CF_Code10>^<Refer-
ence ID>^MDC For IHE non-com-
pliant setting:
<CF_Code10>^<Reference
ID>^MDC^<Draeger Label>^^Local
4 00004 Observation R ST 20 <Device Identifier>.<VMD_In- R
Sub- stance>.<Channel_In-
stance>.<CF_Code10>.<Metric_In
stance>
5 00005 OID C Varies 99999 See Observation Value
bservation
Value
6 00006 Units C CWE 705 For IHE Compliant Setting:
<UOM CFCODE>^<UOM
MDC>^MDC

For IHE Non Compliant Setting:

<UOM CFCODE>^<UOM
MDC>^MDC^<Alternate
ID>^^<Code System>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal Flags CE IS 5 <not used>
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal Test
11 00011 Observation R ID 1 “R”
Result Status
12 00012 Effective Date of X DTM 24 <not used>
Reference
Range
13 00013 User Defined X ST 20 <not used>
Access Checks
14 00014 Date/Time of RE DTM 24 YYYYMMDDhhmmss
the Observation
15 00015 Producer’s ID RE CWE 705 <not used>

70 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

OBX Segment - Observation/Result (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
16 00016 Responsible RE XCN 3220 <not used>
Observer
17 00017 Observation RE CWE 705 <not used>
Method
18 00692 Equipment RE EI 427 <UniqueID>^<model>^<manufac-
Instance Identi- turer url>^<universal id type>
fier If serial number is received then
unique id will be serial number, oth-
erwise it will be the IP address of
the device.
19 00693 Date/Time of CE DTM 24 <not used>
the Analysis
20 Observation RE CWE 705 <not used>
Site

Observation Value

The parameter value as reported by the device. The format of this field varies according to the Value Type
field.

Value Type Observation Value Filed Format Comments

ST <value> See Appendix C for special value strings
NM <numeric value>

ACK - Acknowledgment

After receipt of an ORU message, the HL7 server will send an acknowledgment:

Segment Description
MSH MSH Segment – Message Header
MSA MSA Segment – Message Acknowledgment

See ORU - Unsolicited Observation Report for a description of the ORU message being acknowledged.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 71

Unsolicited IEEE 11073 Vital Signs Export

MSH Segment - Message Header

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 Recommended R 1
value is “|”
2 00002 Encoding R ST 4 Four characters R 4
Characters in the following
order: the
component
separator, the
repetition
separator, the
escape
character, and
the
subcomponent
separator.
Recommended
values are
“^~\&”.
3 00003 Sending O HD 180 A string O 16
Application identifying the
sending
application.
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of O TS 26 YYYYMMDDHH O 12
Message mm
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ACK^R01” R 7
10 00010 Message Control R ST 20 A number or R 20
ID other identifier
uniquely
identifying the
message.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.5” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer

72 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

MSH Segment - Message Header (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
15 00015 Accept O ID 2 <not used>
Acknowledgment
Type
16 00016 Application O ID 2 <not used>
Acknowledgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal O CE 60 <not used>
Language Of
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 73

Unsolicited IEEE 11073 Vital Signs Export

MSA Segment – Message Acknowledgment

HL7 HL7 Dräger
Seq Item # Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 See R 1
Code Acknowledgment
Codes
2 00010 Message Control R ST 20 The message R 4
ID control ID of the
message it is
acknowledging.
3 00020 Text Message O ST 80 An error or status O 80
string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledgment
Type
6 00023 Error Condition O CE 100 <not used>

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
AE Original mode: Application Error
AR Original mode: Application Reject
CA Enhanced mode: Commit Accept
CE Enhanced mode: Commit Error
CR Enhanced mode: Commit Reject

74 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

Sample ORU Message

MSH|^~\&|INFO_SRC_DRAEGER^0030E60000000001^EUI-64|Draeger|NUR|Rec-
Fac|20180926150437-
0500||ORU^R01^ORU_R01|18092615043700515606|P|2.6|||AL|NE||8859/1|en^English^ISO639||IHE_P
CD_001^IHE PCD^1.3.6.1.4.1.19376.1.6.1.1.1^ISO
PID|||111-11-
1111^^^^MR||Smith^Wally^L.^^^^L|Joose^Judy^K^^^^L|19420430142000|M^Male||U^Unknown|13 Beer
St.^#123^Beersteinville^VA^12345-6785^USA^M||||spa^Spanish|M^Married|JEW^Jewish|1001|012-34-
5678|||N^Not Hispanic or Latino||||||USA^United States
PV1||E|CU1^^GOWDA12^BGS||||^Munster^Florence^S^II^Mr.^M.D.||||||||||^Carr^Mary^Jones^II^Mrs.^M.
D.|||||||||||||||||||||||||||19980430043020
OBR|1||0826145634032227^DSUBAND^0030E60000000001^EUI-64|182777000^monitoring of
patient^SCT|||20180926150437
OBX|1|NM|131841^MDC_ECG_AMPL_ST_I^MDC^STI^^local|2.1.1.131841001|0.0|266418^MDC_DIM
_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|2|NM|131842^MDC_ECG_AMPL_ST_II^MDC^STII^^local|2.1.1.131842001|0.0|266418^MDC_DI
M_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|3|NM|131843^MDC_ECG_AMPL_ST_V1^MDC^STV1^^local|2.1.1.131843001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|4|NM|131844^MDC_ECG_AMPL_ST_V2^MDC^STV2^^local|2.1.1.131844001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|5|NM|131845^MDC_ECG_AMPL_ST_V3^MDC^STV3^^local|2.1.1.131845001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|6|NM|131846^MDC_ECG_AMPL_ST_V4^MDC^STV4^^local|2.1.1.131846001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|7|NM|131847^MDC_ECG_AMPL_ST_V5^MDC^STV5^^local|2.1.1.131847001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|8|NM|131848^MDC_ECG_AMPL_ST_V6^MDC^STV6^^local|2.1.1.131848001|0.0|266418^MDC_
DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|9|NM|131901^MDC_ECG_AMPL_ST_III^MDC^STIII^^local|2.1.1.131901001|0.0|266418^MDC_DI
M_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 75

Unsolicited IEEE 11073 Vital Signs Export

OBX|10|NM|131902^MDC_ECG_AMPL_ST_AVR^MDC^STaVR^^local|2.1.1.131902001|0.0|266418^M
DC_DIM_MILLI_-
VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|11|NM|131903^MDC_ECG_AMPL_ST_AVL^MDC^STaVL^^local|2.1.1.131903001|0.0|266418^MD
C_DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|12|NM|131904^MDC_ECG_AMPL_ST_AVF^MDC^STaVF^^local|2.1.1.131904001|0.0|266418^M
DC_DIM_MILLI_-
VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|13|NM|192805^MDC_ECG_AMPL_ST_CVM^MDC^STCVM^^local|2.1.1.192805001|0.0|266418^
MDC_DIM_MILLI_-
VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|14|NM|192806^MDC_ECG_AMPL_ST_VM^MDC^STVM^^local|2.1.1.192806001|0.0|266418^MD
C_DIM_MILLI_VOLT^MDC^mv^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|15|NM|147842^MDC_ECG_CARD_BEAT_RATE^MDC^HR^^local|2.1.2.147842001|86.0|264864^
MDC_DIM_BEAT_PER_MIN^MDC^/min^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://w
ww.draeger.com/^DNS
OBX|16|NM|148066^MDC_ECG_V_P_C_RATE^MDC^PVC/min^^local|2.1.2.148066001|0.0|264864^M
DC_DIM_BEAT_PER_MIN^MDC^/min^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www
.draeger.com/^DNS
OBX|17|ST|148496^MDC_ECG_ARRHY^MDC^ARR^^local|2.1.2.148496001|
|262656^MDC_DIM_DIM-
LESS^MDC^^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|18|NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC^PLS^^local|2.13.1.149530001|86.0|26486
4^MDC_DIM_BEAT_PER_MIN^MDC^/min^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS
OBX|19|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC^SpO2^^local|2.13.1.150456001|97.0|262688^
MDC_DIM_PERCENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|20|NM|150488^MDC_BLD_PERF_INDEX^MDC^PI^^local|2.13.1.150488001|3.52|262688^MDC_
DIM_PERCENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|21|ST|150301^MDC_PRESS_CUFF_SYS^MDC^NBP S^^local|2.16.1.150301001|
|266016^MDC_DIM_MMHG^MDC^mm(hg)^^ISO+|||||R|||20180923145607||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS
OBX|22|ST|150302^MDC_PRESS_CUFF_DIA^MDC^NBP D^^local|2.16.1.150302001|
|266016^MDC_DIM_MMHG^MDC^mm(hg)^^ISO+|||||R|||20180923145607||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS
OBX|23|ST|150303^MDC_PRESS_CUFF_MEAN^MDC^NBP M^^local|2.16.1.150303001|
|266016^MDC_DIM_MMHG^MDC^mm(hg)^^ISO+|||||R|||20180923145607||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS

76 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited IEEE 11073 Vital Signs Export

OBX|24|ST|159764^MDC_CONC_HB_ART^MDC^Hgb^^local|2.31.1.159764001|
|264256^MDC_DIM_G_PER_DL^MDC^g/dL^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http:
//www.draeger.com/^DNS
OBX|25|ST|160064^MDC_CONC_PCO2_GEN^MDC^PCO2^^local|2.31.1.160064001|
|266016^MDC_DIM_MMHG^MDC^mm(hg)^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS
OBX|26|ST|160116^MDC_CONC_PO2_GEN^MDC^PO2^^local|2.31.1.160116001|
|266016^MDC_DIM_MMHG^MDC^mm(hg)^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://
www.draeger.com/^DNS
OBX|27|ST|160132^MDC_CONC_HCT_GEN^MDC^Hct^^local|2.31.1.160132001|
|262688^MDC_DIM_PER-
CENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|28|NM|192557^MDC_NMT_TEMP^MDC^NMT-
Temp^^local|2.32.1.192557001|20.0|268192^MDC_DIM_DEGC^MDC^cel^^ISO+|||||R|||2018092615043
7||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|29|ST|192605^MDC_NMT_TOF_RATIO^MDC^TOF-Ratio^^local|2.32.1.192605001|
|262688^MDC_DIM_PER-
CENT^MDC^%^^ISO+|||||R|||20180923145607||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|30|NM|160280^MDC_PULS_OXIM_CONC_HB_O2_ART_CALC^MDC^SpOC^^local|2.39.1.16028
0001|33.0|268562^MDC_DIM_-
MILLI_L_PER_DL^MDC^mL/dL^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|31|NM|160284^MDC_PULS_OXIM_HB_CO_ART^MDC^SpCO^^local|2.39.1.160284001|2.0|2626
88^MDC_DIM_PER-
CENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|32|NM|160288^MDC_PULS_OXIM_HB_MET_ART^MDC^SpMet^^local|2.39.1.160288001|0.7|262
688^MDC_DIM_PER-
CENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|33|NM|192790^MDC_PULS_OXIM_PVI^MDC^PVI^^local|2.39.1.192790001|1.0|262688^MDC_DI
M_PERCENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|34|NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC^PLS*^^local|2.41.1.149530001|50.0|2648
64^MDC_DIM_BEAT_PER_MIN^MDC^/min^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http:/
/www.draeger.com/^DNS
OBX|35|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC^SpO2*^^local|2.41.1.150456001|96.0|262688^
MDC_DIM_PERCENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|36|NM|150468^MDC_PULS_OXIM_SAT_O2_DIFF^MDC^Delta^^local|2.41.1.150468001|1.0|2626
88^MDC_DIM_PER-
CENT^MDC^%^^ISO+|||||R|||20180926150437||||0060E9EEBC^IACS^http://www.draeger.com/^DNS

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 77

Unsolicited IEEE 11073 Vital Signs Export

Sample Acknowledgment
MSH|^~\&|NUR||Infinity|MEDAT-18|20180926150437||ACK^R01|99011716090716963683|P|2.3
MSA|AA|18092615043700515606|[999-99-9999]Message Delivered

78 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

Solicited Vital Signs Export

The HL7/ASTM Interface Option for exporting solicited vital signs supports external system requests of
vital signs data from the Infinity and SDC Networks. This option is available only on an Infinity Gateway
server. The request is made in a QRY message. A message can be used to request data from one or
multiple patients. Patients are specified by their location within the Infinity and SDC Networks by a
combination of care unit label and bed label. Upon receipt of this message, the Infinity Gateway server
exports all vital signs data received from the specified patient monitor(s), in an ORF message.
Discrete parameters vital signs, such as non-invasive blood pressure, are sent repeatedly by the device,
even when no new measurement has been taken. By default, these vital signs parameters will
continuously be output to the requesting system. The requesting system can determine whether a vital
signs parameter measurement represents a new measurement by examining the associated timestamp.
An option does exist to filter the repeated output of these discrete parameters vital signs. If this filter is
enabled, the interface will output these parameter measurements only once, however, if the system is
restarted, the parameter vital sign may be transmitted once more.
See Dräger HL7 Overview for details on how Dräger implements HL7 interfaces.
For the Solicited Vital Signs Export interface, the external system (the Clinical Information System or CIS)
initiates the connection.

QRY – Vital Signs Query

Vital Signs Query messages follow the format below.

Segment Description
MSH MSH Segment - Message Header
QRD Acknowledgment Codes
QRF QRF - Query Filter

See ORF – Observational Report for a description of the response message sent by the Infinity Gateway
server.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 79

Solicited Vital Signs Export

MSH Segment - Message Header

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00001 Field Sep- R ST 1 The separator R 1
arator between the
segment ID and
the first real
field, encoding
characters. As
such it serves
as the separa-
tor and defines
the character to
be used as a
separator for
the rest of the
message. Rec-
ommended
value is “|”.
2 00002 Encoding R ST 4 The four char- R 4
Characters acters in the fol-
lowing order:
the component
separator, the
repetition sep-
arator, the
escape charac-
ter, and the
subcomponent
separator. Rec-
ommended val-
ues are “^~\&”.
3 00003 Sending O HD 180 <not used>
Application
4 00004 Sending O HD 180 <not used>
Facility
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMD- O 12
Message DHHmmss
8 00008 Security O ST 40 <not used>
9 00009 Message R CM 7 “QRY^R02” R 7
Type

80 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

MSH Segment - Message Header (Continued)

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
10 00010 Message R ST 20 A number or R 20
Control ID other identifier
that uniquely
identifies the
message. The
Infinity
Gateway
echoes this ID
back to the
sending system
in the Message
acknowledgme
nt segment
(MSA).
11 00011 Processing R PT 3 “P” R 3
ID
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continua- O ST 180 <not used>
tion Pointer
15 00015 Accept O ID 2 <not used>
Acknowledg-
ment Type
16 00016 Application O ID 2 <not used>
Acknowledg-
ment
17 00017 Country O ID 2 <not used>
Code
18 00692 Character O ID 6 <not used>
Set
19 00693 Principal O CE 60 <not used>
Language Of
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 81

Solicited Vital Signs Export

QRD Segment - Original Type Query Definition

HL7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00025 Query R TS 26 YYYYMMD- O 26
Date/Time Dhhmmss
2 00026 Query Format R ID 1 “R” R 1
Code
3 00027 Query Priority R ID 1 “I” R 1
4 00028 Query ID R ST 10 This field R 10
should contain
a unique identi-
fier for the
query. It is
returned intact
by the Infinity
application.
5 00029 Deferred O ID 1 <not used>
Response Type
6 00030 Deferred O TS 26 <not used>
Response
Date/Time
7 00031 Quantity Lim- R CQ 10 <not used>
ited Request
8 00032 Who Subject R XCN 60 <not used>
Filter
9 00033 What Subject R CE 60 “RES” R 60
Filter
10 00034 What Depart- R CE 60 <not used>
ment Data
Code
11 00035 What Data O ST 20 <not used>
Code Value
Qual.
12 00036 Query Results O ID 1 <not used>
Level

82 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

QRF - Query Filter

Hl7 HL7 Dräger

Seq Item # Description Req Type Len Contents Req Len
1 00037 Where Subject R ST 20 “MONITOR” 20
Filter
2 00038 When Data O TS 26 <not used> R
Start
Date/Time
3 00039 When Data O TS 26 <not used>
End Date/Time
4 00040 What User O ST 60 <not used>
Qualifier
5 00041 Other QRY O ST 60 Specifies 999
Subject Filter which patient
monitor(s) the
query applies
to, in format:
<Care Unit
Label>^^<Bed
Label>
Multiple
patient moni-
tors can be
specified
using the rep-
etition delim-
iter.
6 00042 Which O ID 12 <not used> R
Date/Time
Qualifier
7 00043 Which O ID 12 <not used>
Date/Time Sta-
tus Qualifier
8 00044 Date/Time O ID 12 <not used>
Selection Qual-
ifier
9 00694 When Quan- O TQ 60 <not used>
tity/Timing
Qualifier

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 83

Solicited Vital Signs Export

ORF – Observational Report

Upon receiving a QRY message, a message will be sent by the responding system in the following format.
Square brackets ‘[‘ and ‘]’ indicate optional segments. Curved brackets, ‘{‘ and ‘}’, indicate segments which
may be repeated.

Seqment Description
MSH MSH Segment - Message Header
MSA MSA Segment - Message Acknowledgment
QRD Acknowledgment Codes
QRF QRF Segment – Query Filter
PID PID Segment - Patient Identification
PV1 PV1 Segment - Patient Visit
OBR OBR Segment - Observation Request
{[OBX]} OBX Segment - Observation/Result

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00001 Field Separa- R ST 1 “|” R 1
tor
2 00002 Encoding R ST 4 “^~\&” R 4
Characters
3 00003 Sending O HD 180 “INFINITY” O 1
Application
4 00004 Sending Facil- O HD 180 <not used>
ity
5 00005 Receiving O HD 180 The string O
Application identifying
the Send-
ing Applica-
tion in the
of the QRY
message
being
acknowl-
edged.
6 00006 Receiving O HD 180 <not used>
Application

84 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
7 00007 Date/Time of O TS 26 YYYYM- O 12
Message MDDhhmm
ss
8 00008 Security O ST 40 <not used>
9 00009 Message R CM 7 “ORF^R04” R 7
Type
10 00010 Message R ST 20 A number R 20
Control ID or other
identifier
that
uniquely
identifies
the mes-
sage.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Acknowledg- O ID 2 "AL" R 2
ment Type
16 00016 Application O ID 2 "NE" R 2
Acknowledg-
ment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal Lan- O CE 60 <not used>
guage Of
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 85

Solicited Vital Signs Export

MSA Segment - Message Acknowledgment

Seq HL7 HL Dräger

Item #8
Description Req Type Len Contents Req Len

1 00018 Acknowledg- R ID 2 See R 1

ment Code Acknowledg-
ment Codes
2 00010 Message Control R ST 20 The Mes- R 4
ID sage Control
ID of the
message it is
acknowledg-
ing.
3 00020 Text Message O ST 80 An error or O 80
status string
4 00021 Expected O NM 15 <not used>
Sequence Num-
ber
5 00022 Delayed B ID 1 <not used>
Acknowledg-
ment Type
6 00023 Error Condition O CE 100 <not used>

86 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment: Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment: Error
AR Original mode: Application Reject
Enhanced mode: Application acknowledgment: Reject

QRD Segment – Original Type Query Definition

The QRD segment in the request (refer to Acknowledgment Codes) is echoed back to the requestor.

QRF Segment – Query Filter

The QRF segment in the request (refer to ORF – Observational Report) is echoed back to the requestor.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 87

Solicited Vital Signs Export

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00104 Set ID - Patient O SI 4 <not used>
ID
2 00105 Patient ID O CX 20 <not used>
(External ID)
3 00106 Patient ID R CX 20 See Patient
(Internal ID) Identifiers
4 00107 Alternate O CX 20 <not used>
Patient ID - PID
5 00108 Patient Name R XPN 48 See Patient O 32
Name.
6 00109 Mother’s O XPN 48 <not used>
Maiden Name
7 00110 Date/Time of O IS 26 <not used>
Birth
8 00111 Sex O IS 1 <not used>
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 26 <not used>
11 00114 Patient O XAD 1 <not used>
Address
12 00115 County Code B IS 48 <not used>
13 00116 Phone Number O XTN 1 <not used>
- Home
14 00117 Phone Number O XTN 106 <not used>
- Business
15 00118 Primary Lan- O CE 4 <not used>
guage
16 00119 Marital Status O IS 40 <not used>
17 00120 Religion O IS 40 <not used>
18 00121 Patient O CX 60 See Patient O 12
Account Num- Identifiers
ber
19 00122 SSN Number - O ST 1 <not used>
Patient
20 00123 Driver's O CM 25 <not used>
License Num-
ber - Patient

88 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
21 00124 Mother's Identi- O CX 20 <not used>
fier
22 00125 Ethnic Group O IS 3 <not used>
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth O ID 2 <not used>
Indicator
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Mili- O CE 60 <not used>
tary Status
28 00131 Nationality O CE 80 <not used>
29 00132 Patient Death O TS 26 <not used>
Date and Time
30 00133 Patient Death O ID 1 <not used>
Indicator

Patient Identifiers
Depending on the on the configuration of the primary identifier, the Patient ID field that appears in the
Patient Admit screen of Infinity patient monitors and at the Infinity Central Station, is interpreted as either
a Medical Record number or a Patient Account number (i.e. visit number).

Interpret Patient Field 3 contents Field 18 contents

ID as Setting
MRN <Patient ID> blank
Patient Account # <Patient ID> <Patient ID>

Patient Name
Patient Name entered in the Admit screen of the device in the format “Last^First^Middle”. For proper pars-
ing, users of the device should be instructed to enter the Patient Name in the “<Last>,<First> <Middle>”
format. If no Patient Name is entered on the Admit screen, this field will contain “UNKNOWN”.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 89

Solicited Vital Signs Export

PV1 Segment - Patient Visit

HL7 Dräger
Seq Item # Description Req Type Len Contents Req Len

1 00131 Set ID - PV1 O SI 4 <not used>

2 00132 Patient Class R IS 1 <not used>
3 00133 Assigned O PL 80 In the format: R 18
Patient Loca- <Care Unit
tion Label>^^<Bed
Label>. The loca-
tion is defined at
the device.
4 00134 Admission O IS 2 <not used>
Type
5 00135 Preadmit O CX 20 <not used>
Number
6 00136 Prior Patient O PL 80 <not used>
Location
7 00137 Attending O XCN 60 <not used>
Doctor
8 00138 Referring O XCN 60 <not used>
Doctor
9 00139 Consulting O XCN 60 <not used>
Doctor
10 00140 Hospital Ser- O IS 3 <not used>
vice
11 00141 Temporary O PL 80 <not used>
Location
12 00142 Preadmit Test O IS 2 <not used>
Indicator
13 00143 Readmission O IS 2 <not used>
Indicator
14 00144 Admit Source O IS 3 <not used>
15 00145 Ambulatory O IS 2 <not used>
Status
16 00146 VIP Indicator O IS 2 <not used>
17 00147 Admitting O XCN 60 <not used>
Doctor
18 00148 Patient Type O IS 2 <not used>
19 00149 Visit Number O CX 20 <not used>
20 00150 Financial O CM 50 <not used>
Class

90 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

PV1 Segment - Patient Visit (Continued)

HL7 Dräger
Seq Item # Description Req Type Len Contents Req Len

21 00151 Charge Price O IS 2 <not used>

Indicator
22 00152 Courtesy O IS 2 <not used>
Code
23 00153 Credit Rating O IS 2 <not used>
24 00154 Contract O IS 2 <not used>
Code
25 00155 Contract O DT 8 <not used>
Effective Date
26 00156 Contract O NM 12 <not used>
Amount
27 00157 Contract O NM 3 <not used>
Period
28 00158 Interest Code O IS 2 <not used>
29 00159 Transfer to O IS 1 <not used>
Bad Debt
Code
30 00160 Transfer to O DT 8 <not used>
Bad Debt
Date
31 00161 Bad Debt O IS 10 <not used>
Agency Code
32 00162 Bad Debt O NM 12 <not used>
Transfer
Amount
33 00163 Bad Debt O NM 12 <not used>
Recovery
Amount
34 00164 Delete O IS 1 <not used>
Account Indi-
cator
35 00165 Delete O DT 8 <not used>
Account Date
36 00166 Discharge O IS 3 <not used>
Disposition
37 00167 Discharged to O CM 25 <not used>
Location
38 00168 Diet Type O IS 2 <not used>
39 00169 Servicing O IS 2 <not used>
Facility

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 91

Solicited Vital Signs Export

PV1 Segment - Patient Visit (Continued)

HL7 Dräger
Seq Item # Description Req Type Len Contents Req Len

40 00170 Bed Status B IS 1 <not used>

41 00171 Account Sta- O IS 2 <not used>
tus
42 00172 Pending O PL 80 <not used>
Location
43 00173 Prior Tempo- O PL 80 <not used>
rary Location
44 00174 Admit O TS 26 <not used>
Date/Time
45 00175 Discharge O TS 26 <not used>
Date/Time
46 00176 Current O NM 12 <not used>
Patient Bal-
ance
47 00177 Total Charges O NM 12 <not used>
48 00178 Total Adjust- O NM 12 <not used>
ments
49 00178 Total Pay- O NM 12 <not used>
ments
50 00180 Alternate Visit O CX 20 <not used>
ID
51 01226 Visit Indicator O IS 1 <not used>
52 01224 Other Health- O XCN 60 <not used>
care Provider

92 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

OBR Segment - Observation Request

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00237 Set ID - OBR C SI 4 <not used>
2 00216 Placer Order Num- C EI 75 <not used>
ber
3 00217 Filler Order Number C EI 75 <not used>
+
4 00238 Universal Service ID R CE 200 <not used>
5 00239 Priority B ID 2 <not used>
6 00240 Requested B TS 26 <not used>
Date/time
7 00241 Observation C TS 26 The date the R 14
Date/Time # observation
was measured
on the device.
Format is
YYYYMMD-
DHHmmss.
8 00242 Observation End O TS 26 <not used>
Date/Time
9 00243 Collection Volume O CQ 20 <not used>
10 00244 Collector Identifier O XCN 60 <not used>
11 00245 Specimen Action O ID 1 <not used>
Code
12 00246 Danger Code O CE 60 <not used>
13 00247 Relevant Clinical O ST 300 <not used>
Info
14 00248 Specimen Received O TS 26 <not used>
Date/Time
15 00249 Specimen Source O CM 300 <not used>
16 00226 Ordering Provider O XCN 80 <not used>
17 00250 Order Callback O XTN 40 <not used>
Phone Number
18 00251 Placer field 1 O ST 60 <not used>
19 00252 Placer field 2 O ST 60 <not used>
20 00253 Filler Field 1 + O ST 60 <not used>
21 00254 Filler Field 2 + O ST 60 <not used>
22 00255 Results Rpt/Status O TS 26 <not used>
Chng - Date/Time +
23 00256 Charge to Practice + O CM 40 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 93

Solicited Vital Signs Export

OBR Segment - Observation Request (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
24 00257 Diagnostic Serv Sect O ID 10 <not used>
ID
25 00258 Result Status + O ID 1 <not used>
26 00259 Parent Result + O CM 400 <not used>
27 00221 Quantity/Timing O TQ 200 <not used>
28 00260 Result Copies To O XCN 150 <not used>
29 00261 Parent O CM 150 <not used>
30 00262 Transportation Mode O ID 20 <not used>
31 00263 Reason for Study O CE 300 <not used>
32 00264 Principal Result O CM 200 <not used>
Interpreter +
33 00265 Assistant Result O CM 200 <not used>
Interpreter +
34 00266 Technician + O CM 200 <not used>
35 00267 Transcriptionist + O CM 200 <not used>
36 00268 Scheduled O TS 26 <not used>
Date/Time +
37 01028 Number of Sample O NM 4 <not used>
Containers
38 01029 Transport Logistics O CE 60 <not used>
of Collected Sample
39 01030 Collector's Comment O CE 200 <not used>
40 01031 Transport Arrange- O CE 60 <not used>
ment Responsibility
41 01032 Transport Arranged O ID 30 <not used>
42 01033 Escort Required O ID 1 <not used>
43 01034 Planned Patient O CE 200 <not used>
Transport Comment

94 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

OBX Segment - Observation/Result

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00569 Set ID – O SI 10 <not used>
OBX
2 00570 Value Type C ID 2 “SN” (structured R 2
numeric) iIf the
parameter value
being reported
by the device is
numeric, other-
wise
“ST”(string).
3 00571 Observation R CE 590 See Observa- R
Identifier tion Identifier
4 00572 Observation C ST 20 <not used>
Sub-Identi-
fier
5 00573 Observation C * 6553 See Observa- R 30
Value 6 tion Value
6 00574 Units O CE 60 Uniquely identi- O 30
fies the units in
which the
parameter is
being reported,
in the format
“<identi-
fier>^^ISO+”.
The identifier is
the HL7 code,
as shown in
Appendix 21.
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal O ID 5 <not used>
Flags
9 00577 Probability O NM 5 <not used>
10 00578 Nature of ID 2 <not used>
Abnormal
Test
11 00579 Observation R ID 1 “R” R 1
Result Sta-
tus

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 95

Solicited Vital Signs Export

OBX Segment - Observation/Result (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
12 00580 Date Last O TS 26 <not used>
Observation
Normal Val-
ues
13 00581 User Defined O ST 20 <not used>
Access
Checks
14 00582 Date/Time of O TS 26 YYYYMMD- O 12
the Observa- DHHmmss
tion
15 00583 Producer's O CE 60 <not used>
ID
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

Observation Identifier
Uniquely identifies the parameter being reported, in the format:
<identifier1^^local^<<identifier2>&<instance >>^^<coding system >

identifier1 Dräger’s label for the parameter (for example HR)

identifier2 LOINC or MIB/CEN code for the parameter
instance instance of usage for the LOINC or MIB/CEN code
coding system “LOINC” if identifier2 is a LOINC code
“MIB/CEN” if identifier2 is an MIB/CEN code

MIB/CEN codes are only sent when there is no LOINC code that denotes the parameter. Refer to
Appendix A: Parameters for a list of parameters available on the Infinity Network, including LOINC and
MIB/CEN codes.

96 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Solicited Vital Signs Export

Observation Value
The parameter value as reported by the Infinity Network. The format of this field varies according to the
Value Type field.
Value Type Observation Value Field Format Comments
ST <value> See Appendix C: Special Dis-
play Values for special value
strings.
SN <comparator>^<value> comparator is “=”

Sample

QRY Messages
MSH|^~\&|Infinity||HIS||199903221322||QRY^R02|99022213222303883455|P|2.3
QRD|19990322160000|R|I|9999999999|||||RES
QRF|MONITOR||||CU50^^Bed2

ORF Message
SH|^~\&|Infinity||Infinity||20170424084700||ORF^R04|17042408470029637450|P|2.3|||AL|NE
MSA|AA|17042408470000053922|[CU50,Bed2]Bed found
QRD|19990322160000|R|I|9999999999|||||RES
QRF|MONITOR||||CU50^^Bed2
PID|||8888^^^^AN||Data^Simulated^Patient|||||||||||||8888
PV1|||CU50^^Bed2
OBR|||||||20170425185117
OBX||SN|HR^^local^8867-4&1^^LOINC||=^84|/min^^ISO+|||||R|||20170425185116
OBX||SN|%PACED^^local^ &1^^LOINC||=^0|%^^ISO+|||||R|||20170425185116
OBX||ST|ARR^^local^ &1^^LOINC|| |^^ISO+|||||R|||20170425185116
OBX||SN|PVC/min^^local^ &1^^LOINC||=^0|/min^^ISO+|||||R|||20170425185116
OBX||SN|STI^^local^10121-2&1^^LOINC||=^0.2|mm^^ISO+|||||R|||20170425185116
OBX||SN|STII^^local^10122-0&1^^LOINC||=^0.3|mm^^ISO+|||||R|||20170425185116
OBX||SN|STIII^^local^10123-8&1^^LOINC||=^0.2|mm^^ISO+|||||R|||20170425185116

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 97

 This page has been left blank intentionally.

98 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0

 Unsolicited ADT Import

Unsolicited ADT Import

The unsolicited ADT interface accepts ADT messages from the transmitting system and maintains a
database of patient admission information. Data imported through this interface is used on Infinity patient
monitors by request. Admission data is requested directly from some models of Dräger patient monitors
or from an Infinity Central Station (ICS) during a patient admission.
The Dräger HL7 server acknowledges the receipt of these messages with an ACK message to the sending
system. When ADT data requests for a particular patient, based on primary identifier, are made from the
Infinity Network, the latest data for that patient is sent to the requesting device.
When data is requested from a Infinity Central Station or a Dräger patient monitor, the Patient ID in the
request is interpreted according to the Interpret Patient ID as setting on the HL7 server. Available values
for this setting are MRN or Patient Account number.
The lower layer protocol used for this interface is Minimal Lower Layer Protocol (MLLP). See Dräger HL7
Overview for details on how Dräger implements HL7 interfaces.

NOTE
The solicited and unsolicited ADT Interfaces are mutually exclusive.

For the Unsolicited ADT interface, the external system (the hospital information system or HIS) initiates
the connection.

NOTE
The Unsolicited ADT interface has been validated with up to 60 transactions per minute and a total of
100,000 patient records.

The following table indicates the data imported, the HL7 segment from which it is extracted, and the screen
where it appears on the destination Infinity monitor or Infinity Central Station (ICS).

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 99

Unsolicited ADT Import

Field Usage by Platform

Data Destination Monitor HL7 Segment

Imported
Application Modular Configured Telemetry
Screen Monitors Monitors
Medical Admit Screen Sometimes Sometimes Sometimes See Patient
Record Identifier
Number
Visit Number Admit Screen Sometimes Sometimes Sometimes See Patient
Identifier
Patient Admit Screen Yes Yes Yes See Patient
Name Name
Birth Admit Screen Yes Yes Yes See
Date/Time Date/Time of
Birth
Admit Date Admit Screen Yes Yes Yes See Admit
Date/Time
Attending Admit Screen Yes Yes Yes See Attend-
Doctor ing Doctor
Height Admit Screen Yes Yes Yes See
Observation
Identifier
Weight Admit Screen Yes Yes Yes See
Observation
Identifier
Sex ECG Report Yes No No See Sex
Setup
Race ECG Report Yes No No See Race
Setup
Religion N/A No No No See Religion
Prior MRN N/A No No No See Prior
Internal ID
Prior Visit N/A No No No See Prior
Number Patient
Account Num-
ber
Marital Sta- N/A No No No See Marital
tus Status
Nationality N/A No No No See National-
ity
Primary Lan- N/A No No No Refer to ADT-
guage Config Tool
Patient N/A No No No See Patient
Address Address

100 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

Field Usage by Platform (Continued)

Data Destination Monitor HL7 Segment

Imported
Application Modular Configured Telemetry
Screen Monitors Monitors
Admitting N/A No No No See Admitting
Doctor Doctor
Consulting N/A No No No See Consult-
Doctor ing Doctor
Referring N/A No No No See Referring
Doctor Doctor
National ID / N/A No No No See National
Social Secu- ID/ Social
rity Security Num-
ber
Patient N/A No No No See Patient
Location Location
Prior Loca- N/A No No No See Prior
tion Patient Loca-
tion
Discharge N/A No No No See Dis-
Date charge Date
Event Date N/A No No No See Event
Occurred
Ethnic N/A No No No See Ethnic
Group Group

ADT data received from the hospital information system (HIS) is stored in a database on the Dräger HL7
SERVER. When a request for data is received from an Infinity device, a database lookup is done based
on information provided by the requesting device. The Patient ID received from the requesting device is
interpreted according to the Interpret Patient ID as setting on the HL7 server.

Bedside Auto Update

This Bedside Auto Update option to Unsolicited ADT causes demographic data changes received by the
HL7 server to be forwarded to a patient monitor where the corresponding patient has already been
admitted, if applicable.
This feature is intended only to solve the following problem:
1 The nurse admits a patient to a patient monitor using the “Get From HIS” button on the Infinity Central
Station.
2 Someone at the admissions system notices an error in the demographic data for the patient and
corrects it.
3 The admissions systems automatically sends an update to the HL7 server.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 101
Unsolicited ADT Import

In this situation, if the ADT Auto Update option is not enabled, the patient monitor will never be updated
with the correction unless the nurse manually requests the data from the Admissions System again by
pressing the “Get From HIS” button at the Infinity Central Station.
With this feature enabled, all changes (a patient record must already exist at the HL7 server) received
from the HIS, excluding height and weight, that are normally sent to the patient monitor when the “Get
From HIS” button is pushed, will automatically be sent to the patient monitor where the patient is admitted.
Note that if the primary identifier is entered at more than one patient monitor, the changes will not be sent
to any patient monitor. In the event of a merge where the patient identifier has changes the patient
identifier will be updated at the patient monitor.

Configuration

The unsolicited ADT interface allows the user to define which Event Types the interface will accept, and
the actions to be taken for each configured event. Any Event Type that has not been configured will be
acknowledged, but no action will be taken.
The following table outlines the Event Types and associated actions constituting the default configuration
for the Unsolicited ADT interface.

Default Unsolicited ADT Configuration

Event Type Description Action

A01 Admit a patient Admit
A03 Discharge a patient Discharge
A06 Out to In Admit
A07 In to Out Discharge
A08 Update patient data Change
A11 Cancel admit Discharge
A13 Cancel discharge Admit
A18 Merge patient data Merge
A35 Merge patient account Merge
A36 Merge patient data Merge

The following actions are available for configuration:

Admit
If an ADT record exists in the database that corresponds to the Patient Account Number field of the PID
segment of the incoming message, then that record is deleted, and a new record is created.

102 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

Discharge
If an ADT record exists in the database for the Patient Account Number in the PID segment, it will be
deleted.

Cancel Discharge
If a discharged patient record exists in the database, mark the patient as admitted and then update the
record with changes from the incoming message.

Change
If an ADT record exists in the database that corresponds to the Patient Account Number field of the PID
segment of the incoming message, then the fields of that record are changed with any relevant data in the
incoming message. This action, however, will never modify the Patient Account Number of the patient. If
no record exists, no action is taken.
If Bedside Auto Update is enabled, the changes (excluding height and weight) will be sent to the patient
monitor where the patient is admitted, if only one exists.

Update
This action is identical to a CHANGE action, however, if the ADT record does not already exist, a new
record will be created.
If Bedside Auto Update is enabled and the ADT record already existed for this patient on the HL7 Server,
then the changes (excluding height and weight) will be sent to the patient monitor where the patient is
admitted, if only one exists.

Merge
If an ADT record exists in the database corresponding to the new identifiers, it will be deleted. If an ADT
record exists in the database corresponding to the “prior” identifiers, that record will be updated with the
new identifiers and data.
If Bedside Auto Update is enabled, and one and only patient monitor exists that contains an identifier that
corresponds to the contents of the old record, then any changes applicable to the monitor, excluding
height and weight, between the old record and the newly modified record are sent to the patient monitor.

Ignore
This action is a do nothing action. The incoming message will be acknowledged, but there will be no effect
whatsoever to the database, patient monitors, or ICS.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 103
Unsolicited ADT Import

ADT – Admit, Discharge, and Transfer

ADT messages formats are indicated below. Square brackets, ‘[‘ and ‘]’, indicate optional segments.
Curved brackets, ‘{‘ and ‘}’, indicate segments which may be repeated.

Segment Description
MSH MSH Segment - Message Header
[EVN] EVN Segment - Event Type
PID PID Segment - Patient Identification
{[AL1]} AL1 Segment - Patient Allergy
{[IN1]} IN1 Segment – Patient Insurance
{[DG1]} DG1 Segment – Patient Diagnosis
[NK1] NK1 Segment - Next of Kin
[PV1] PV1 Segment - Patient Visit
[MRG] MRG Segment - Merge Patient Information
{[OBX]} OBX Segment - Observation/Result

Any other segments received will be ignored.

See ACK – Acknowledgment for a description of the acknowledgment sent by the Infinity application.

104 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00001 Field Sep- R ST 1 The separator R 1
arator between the seg-
ment ID and the
first real field,
encoding charac-
ters. It serves as
the separator and
defines the charac-
ter to be used as a
separator for the
rest of the mes-
sage. Recom-
mended value is “|”.
2 00002 Encoding R ST 4 Four characters in R 4
Characters the following order:
the component sep-
arator, the repeti-
tion separator, the
escape character,
and the subcompo-
nent separator.
Recommended val-
ues are “^~\&”.
3 00003 Sending O HD 180 Text identifying the
Application sending applica-
tion.
4 00004 Sending O HD 180 <not used>
Facility
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 <not used>
Message
8 00008 Security O ST 40 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 105
Unsolicited ADT Import

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
9 00009 Message R CM 7 This field has the R 7
Type format:
ADT^<event type>
Event type is one of
the events that the
application has
been configured for.
For more details
refer to Configura-
tion.
10 00010 Message R ST 20 A number or other R 20
Control ID identifier that
uniquely identifies
the message.
11 00011 Processing R PT 3 “P” R 3
ID
12 00012 Version ID R ID 8 “2.2” ,“2.3” or R 8
“2.3.1”
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continua- O ST 180 <not used>
tion Pointer
15 00015 Accept O ID 2 <not used>
Acknowl-
edgment
Type
16 00016 Application O ID 2 <not used>
Acknowl-
edgment
17 00017 Country O ID 2 <not used>
Code
18 00692 Character O ID 6 <not used>
Set
19 00693 Principal O CE 60 <not used>
Language
Of Message

106 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

EVN Segment - Event Type

Seq HL7 HL7 Dräger

Item # Descrip- Req Type Len Contents Req Len
tion
1 00099 Event B ID 3 This field has been R 3
Type retained for back-
Code ward compatibility
only. It is recom-
mended using the
second component
(Event Type) of the
message type field of
the MSH Segment -
Message Header to
transmit event type
code information.
2 00100 Recorded R TS 26 <not used>
Date/Time
3 00101 Date/Time O TS 26 <not used>
Planned
Event
4 00102 Event O IS 3 <not used>
Reason
Code
5 00103 Operator O XCN 60 <not used>
ID
6 00278 Event O TS 26 See Event Occurred O 14
Occurred

Event Occurred
The date and time that the ADT event took place, in the format:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 107
Unsolicited ADT Import

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item Description Req Type Len Contents Req Len
#
1 00104 Set ID - Patient O SI 40 <not used>
ID
2 00105 Patient ID (Exter- O CX 20 <not used>
nal ID)
3 00106 Patient ID R CX 200 See Patient R/O
Identifier
4 00107 Alternate Patient O CX 20 <not used>
ID - PID
5 00108 Patient Name R XPN 48 See Patient O
Name
6 00109 Mother’s Maiden O XPN 48 <Last>^<First>^
Name <Middle>
7 00110 Date/Time of O TS 26 See Date/Time O 26
Birth of Birth
8 00111 Sex O IS 1 See Sex O 1
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 1 See Race O 26
11 00114 Patient Address O XAD 106 See Patient O
Address
12 00115 Country Code B IS 4 <not used>
13 00116 Phone Number - O XTN 40 <not used>
Home
14 00117 Phone Number - O XTN 40 <not used>
Business
15 00118 Primary Lan- O CE 60 Refer to ADT- O 4
guage Config Tool
16 00119 Marital Status O IS 1 See Marital Sta- O 1
tus
17 00120 Religion O IS 3 See Religion O 4
18 00121 Patient Account O CX 20 See Patient R/O 20
Number Identifier
19 00122 SSN Number - O ST 16 See National ID/ O 16
Patient Social Security
Number
20 00123 Driver’s License O CM 25 <not used>
Number - Patient

108 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item Description Req Type Len Contents Req Len
#
21 00124 Mother's Identi- O CX 20 <not used>
fier
22 00125 Ethnic Group O IS 3 See Ethnic O 4
Group
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth O ID 2 <not used>
Indicator
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Military O CE 60 <not used>
Status
28 00131 Nationality O CE 80 See Nationality O 4
29 00132 Patient Death O TS 26 <not used>
Date and Time
30 00133 Patient Death O ID 1 <not used>
Indicator

Religion

This field contains a code, up to 10 characters long, that indicates the religion of the patient. Refer to
ADTConfig for the default configuration of this field.

Patient Identifier
Depending on the HL7 configuration screen, the Patient ID field that appears in the Patient Admit screen
of the device is interpreted as either a Medical Record number, retrieved from PID segment Seq#3, or a
Patient Account number (i.e. visit number), retrieved from Seq#18 of the PID segment.
The format of either field is:
<ID>^<check digit>^<check digit scheme>^<assigning authority>^<identifier type>^<assigning facility>
The ID component and assigning authority are used for the MRN (seq#3), but only the ID component is
used in the Patient Account number (seq#18).

NOTE
Draeger device can support only an ID of up to 12 characters long.
The Assigning Authority component can only be up to 10 characters long.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 109
Unsolicited ADT Import

Patient Name
Contains the patient name to be entered in the Admit screen of the device upon the request of the ADT
data. The format is:
<Last>^<First>^<Middle>
When the device requests ADT data, the Patient Name will appear in the following format on the Patient
Admit screen: <Last Name>,<First Name> <Middle Initial/Name>
with a comma between the last and first name, and a single space between the first and middle names.
The name is truncated to 26 characters. If this field contains the string “UNKNOWN”, a blank will appear
on the Admit screen for this patient.

Date/Time of Birth
The format is:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Birth Date field of the Patient Admit Screen on the device
when ADT data is requested.

Sex
Contains a single character denoting the sex of the patient. The results of this field will be entered in the
Sex field of the ECG Report Setup Screen, if one exists, when requested during Admit by the device.
In Field On Device
F Female
M Male
All other Unknown

Race
Contains a string denoting the race of the patient. On the device the results of this field will be entered in
the Race field of the ECG Report Setup Screen, if one exists, when requested during Admit. When a
message is received from the HIS, the HIS code is compared to the list of acceptable values, and then
translated into an internal Infinity numeric code, which is then used to communicate with all of the devices.
Infinity codes 1-7 have a fixed interpretation on the device. The HIS codes, however can be configured.
Additional entries may also be added; however, any new entries will be reflected on the Infinity patient
monitors as “Unknown”. The utility used to configure these entries is ADTConfig.exe.
In Field Infinity On Device
(HIS code) Code
2106-3 2 Caucasian
2028-9 3 Asian
2054-5 4 Black or African
American

110 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

In Field Infinity On Device

(HIS code) Code
2131-1 5 Other
1002-5 6 American Indian or
Alaska Native
2076-8 7 Native Hawaiian or
Other Pacific
Islander
All others 1 Unknown

Patient Address
This field contains the mailing address of the patient. Although HL7 supports repetition of this field, Dräger
does not, and only the first instance with address type of M (mailing) will be used. If no address is marked
as mailing, and there is an address that is unmarked for type, then it will be used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>^<address type>
The component lengths supported are as follows:
Component Max Length
street1 40
street2 40
city 25
state/province 25
postal code 10
country 15
address type 1

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 111
Unsolicited ADT Import

Marital Status
The following table denotes the acceptable HIS codes that can be accepted along with their associated
meaning. Unlike many of the other codes accepted on this interface, this list is not configurable.
In Field On Device
A Separated
B Unmarried
C Common law
D Divorced
E Legally Separated
G Living together
I Interlocutory
M Married
N Annulled
O Other
P Domestic partner
R Registered
domestic partner
S Single
T Unreported
W Widowed
All Other Unknown

National ID/ Social Security Number

This field contains a national identifier (such as the Social Security number in the United States).

Ethnic Group
This field contains a code, up to 4 characters long, that indicates the patient’s ethnic group. The default
configuration is detailed in the table below.
HIS Code Ethnic Group
H Hispanic or Latino
N Not Hispanic or Latino
All other Unknown

112 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

Nationality
This field contains a code, up to 4 characters long, that indicates the nationality of the patient. Refer to
ADTConfig for the default configuration of this field.

AL1 Segment - Patient Allergy

NOTE
All allergies must be included in every message, otherwise the associated allergy that is not included will
be deleted from the patient record.

AL1 Segment - Patient Allergy

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00203 Set ID - AL1 R SI 4 <not used>
2 00204 Allergy Type O IS 2 See Allergy Types O 2
3 00205 Allergy R CE 60 See Allergies R 44
Code/Mne-
monic/Descrip-
tion
4 00206 Allergy Severity O IS 2 ‘SV’ severe O 2
‘MO’ moderate
‘MI’ mild
5 00207 Allergy Reaction O ST 15 A string describing O 15
the reaction that
the patient has
when exposed to
the allergy
6 00208 Identification O DT 8 <not used>
Date

Allergy Types
The following table lists the allergy types accepted by HL7:
Code Description
DA Drug Allergy
FA Food Allergy
MA Miscellaneous Allergy
MC Miscellaneous Contraindication

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 113
Unsolicited ADT Import

Allergies
This field has the format <Allergy Code>^<Allergy Description>
The Allergy Code portion of this field must match the HIS code from the pre-configured list of available
Allergy codes. The Allergy code is limited to 4 characters.
The Allergy Description portion of this field is optional and is limited to 40 characters. If the description is
provided, it supersedes the description provided in the default allergy table.

IN1 Segment – Patient Insurance

NOTE
All IN1 segments must be included in every message, otherwise the associated insurance information
that is not included will be deleted from the patient record.

114 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

IN1 Segment - Patient Insurance

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00203 Set ID - IN1 R SI 4 <not used>
2 00368 Insurance Plan R CE 60 A unique identifier R 20
ID for the insurance
plan
3 00428 Insurance Com- R CX 59 <not used>
pany ID
4 00429 Insurance Com- O XON 130 The name of the R 40
pany Name insurance com-
pany
5 00430 Insurance Com- O XAD 106 See Address O 172
pany Address
6 00431 Insurance Co. O XPN 48 <not used>
Contact Person
7 00432 Insurance Co O XTN 40 The string contact O 25
Phone Number number for the
insurance com-
pany.
8 00433 Group Number O ST 12 Identifies the O 12
group within the
insurance plan
9 00434 Group Name O XON 130 The name of the O 40
group within the
insurance plan
10 00435 Insured’s Group O CX 12 <not used>
Emp ID
11 00436 Insured’s Group O XON 130 <not used>
Emp Name
12 00437 Plan Effective O DT 8 <not used>
Date
13 00438 Plan Expiration O DT 8 <not used>
Date
14 00439 Authorization O CM 55 <not used>
Information
15 00440 Plan Type O IS 3 <not used>
16 00441 Name Of O XPN 48 See Name of O 72
Insured Insured
17 00442 Insured’s Rela- O IS 2 See Appendix J: O 3
tionship To Relationship table
Patient

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 115
Unsolicited ADT Import

IN1 Segment - Patient Insurance (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
18 00443 Insured’s Date O TS 26 Date of birth of the O 8
Of Birth primary insurance
holder in the for-
mat
YYYYMMDD
19 00444 Insured’s O XAD 106 See Address O 172
Address
20 00445 Assignment Of O IS 2 <not used>
Benefits
21 00446 Coordination Of O IS 2 <not used>
Benefits
22 00447 Coord Of Ben. O ST 2 <not used>
Priority
23 00448 Notice Of O ID 2 <not used>
Admission Flag
24 00449 Notice Of O DT 8 <not used>
Admission Date
25 00450 Report Of Eligi- O ID 2 <not used>
bility Flag
26 00451 Report Of Eligi- O DT 8 <not used>
bility Date
27 00452 Release Infor- O IS 2 <not used>
mation Code
28 00453 Pre-Admit Cert O ST 15 <not used>
(PAC)
29 00454 Verification O TS 26 <not used>
Date/Time
30 00455 Verification By O XCN 60 <not used>
31 00456 Type Of Agree- O IS 2 <not used>
ment Code
32 00457 Billing Status O IS 2 <not used>
33 00458 Lifetime O NM 4 <not used>
Reserve Days
34 00459 Delay Before O NM 4 <not used>
L.R. Day
35 00460 Company Plan O IS 8 <not used>
Code
36 00461 Policy Number O ST 15 The policy number O 15
37 00462 Policy Deduct- O CP 12 <not used>
ible

116 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

IN1 Segment - Patient Insurance (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
38 00463 Policy Limit - B CP 12 <not used>
Amount
39 00464 Policy Limit - O NM 4 <not used>
Days
40 00465 Room Rate - B CP 12 <not used>
Semi-Private
41 00466 Room Rate - Pri- B CP 12 <not used>
vate
42 00467 Insured’s O CE 60 <not used>
Employment
Status
43 00468 Insured’s Sex O IS 1 <not used>
44 00469 Insured’s O XAD 106 <not used>
Employer
Address
45 00470 Verification Sta- O ST 2 <not used>
tus
46 00471 Prior Insurance O IS 8 <not used>
Plan ID
47 01227 Coverage Type O IS 3 <not used>
48 00753 Handicap O IS 2 <not used>
49 01230 Insured’s ID O CX 12 <not used>
Number

Address
Repetition is not supported for this field, and only the first instance will be used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>
The component lengths supported are as follows:

Component Max Length

street1 40
street2 40
city 25
state/province 25
postal code 10
country 15

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 117
Unsolicited ADT Import

Name of Insured
Contains the name of the primary insured person, The format is:
<Last Name>^<First Name>^<Middle name>
The maximum component lengths are as follows. If a component exceeds the maximum length, it will be
truncated.

Component Max Length

Last 30
First 20
Middle 20

DG1 Segment – Patient Diagnosis

NOTE
All DG1 segments must be included in every message, otherwise the associated diagnosis information
that is not included will be deleted from the patient record.

Diagnosis
This field is of the format:
<ID>^<Text>
Where
ID - contains the code that identifies the diagnosis (up to 8 characters)
Text - description of the diagnosis (up to 42 characters)

Name
Contains the name of the next of kin/associated party. The format is: <Last Name>^<First Name>
The maximum component lengths are as follows. If a component exceeds the maximum length, it is
truncated.
Component Max Length
Last 30
First 20

118 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

Address
This field contains the mailing address of the next of kin/associated party. Although HL7 supports
repetition of this field, Dräger does not, and only the first instance is used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>
The component lengths supported are as follows:

Component Max Length

street1 40
street2 40
city 25
state/province 25
postal code 10
country 15

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 119
Unsolicited ADT Import

DG1 Segment - Patient Diagnostics

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00375 Set ID - DG1 R SI 4 <not used>
2 00376 Diagnosis (B) R ID 2 <not used>
Coding
Method
3 00377 Diagnosis O CE 60 See Diagnosis R 51
Code
4 00378 Diagnosis B ST 40 The description O 42
Description of the diagnosis.
Note that this
field is only
used if compo-
nent 2 of field 3
above is not
populated.
5 00379 Diagnosis O TS 26 <not used>
Date/Time
6 00380 Diagnosis R IS 2 Valid values O 1
Type are:
‘A’: Admitting
‘W’: Working
(default)
‘F’: Final
7 00381 Major Diag- B CE 60 <not used>
nostic Cate-
gory
8 00382 Diagnostic B IS 4 <not used> O 4
Related
Group
9 00383 DRG B ID 2 <not used>
Approval Indi-
cator
10 00384 DRG Grouper B IS 2 <not used>
Review Code
11 00385 Outlier Type B CE 60 <not used>
12 00386 Outlier Days B NM 3 <not used>
13 00387 Outlier Cost B NM 12 <not used>

120 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

DG1 Segment - Patient Diagnostics (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
14 00388 Grouper Ver- B ST 4 <not used>
sion And
Type
15 00389 Diagnosis B NM 2 <not used>
Priority
16 00390 Diagnosing O XCN 60 <not used>
Clinician
17 00766 Diagnosis O IS 3 <not used>
Classification
18 00767 Confidential O ID 1 <not used>
Indicator
19 00768 Attestation O TS 26 <not used>
Date/Time

NK1 Segment - Next of Kin

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00190 Set ID – NK1 R SI 4 <not used>
2 00191 Name O XPN 48 See *Patient O
Class
3 00192 Relationship O CE 60 See Appendix J: O 3
Relationship
table
4 00193 Address O XAD 106 See Address O 106
5 00194 Phone Num- O XTN 40 A string contact O 25
ber number.
6 00195 Business O XTN 40 A string contact O 25
Phone Num- number.
ber
7 00196 Contact Role O CE 60 <not used>
8 00197 Start Date O DT 8 <not used>
9 00198 End Date O DT 8 <not used>
10 00199 Job Title O ST 60 <not used>
11 00200 Job O CM 20 <not used>
Code/Class

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 121
Unsolicited ADT Import

NK1 Segment - Next of Kin (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
12 00201 Employee O CX 20 <not used>
Number
13 00202 Organiza- O XON 60 <not used>
tion Name
14 00119 Marital Sta- O IS 2 <not used>
tus
15 00111 Sex O IS 1 <not used>
16 00110 Date/Time of O TS 26 <not used>
Birth
17 00755 Living O IS 2 <not used>
Dependency
18 00145 Ambulatory O IS 2 <not used>
Status
19 00129 Citizenship O IS 4 <not used>
20 00118 Primary Lan- O CE 60 <not used>
guage
21 00742 Living O IS 2 <not used>
Arrangement
22 00743 Publicity O IS 1 <not used>
Indicator
23 00744 Protection O ID 1 <not used>
Indicator
24 00745 Student Indi- O IS 2 <not used>
cator
25 00120 Religion O IS 3 <not used>
26 00746 Mother’s O XPN 48 <not used>
Maiden
Name
27 00739 Nationality O CE 80 <not used>
28 00125 Ethnic Group O IS 3 <not used>
29 00747 Contact O CE 80 <not used>
Reason
30 00748 Contact Per- O XPN 48 <not used>
son’s Name

122 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

NK1 Segment - Next of Kin (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
31 00749 Contact Per- O XTN 40 <not used>
son’s Tele-
phone
Number
32 00750 Contact Per- O XAD 106 <not used>
son’s
Address
33 00751 Identifiers O CX 32 <not used>
34 00752 Job Status O IS 2 <not used>
35 00113 Race O IS 1 <not used>
36 00753 Handicap O IS 2 <not used>
37 00754 Contact Per- O ST 16 <not used>
son’s Social
Security
Number

PV1 Segment - Patient Visit

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 O SI 4 <not used>
2 00132 Patient Class R IS 1 *Patient
Class
3 00133 Assigned Patient O PL 80 See Patient
Location Location
4 00134 Admission Type O IS 2 <not used>
5 00135 Preadmit Number O CX 20 <not used>
6 00136 Prior Patient O PL 80 See Prior
Location Patient
Location
7 00137 Attending Doctor O XCN 60 See Attend- O
ing Doctor
8 00138 Referring Doctor O XCN 60 See Refer-
ring Doctor
9 00139 Consulting Doctor O XCN 60 See Con-
sulting Doc-
tor

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 123
Unsolicited ADT Import

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
10 00140 Hospital Service O IS 3 <not used>
11 00141 Temporary Loca- O PL 80 <not used>
tion
12 00142 Preadmit Test O IS 2 <not used>
Indicator
13 00143 Readmission Indi- O IS 2 <not used>
cator
14 00144 Admit Source O IS 3 <not used>
15 00145 Ambulatory Status O IS 2 <not used>
16 00146 VIP Indicator O IS 2 <not used>
17 00147 Admitting Doctor O XCN 60 See Admit-
ting Doctor
18 00148 Patient Type O IS 2 <not used>
19 00149 Visit Number O CX 20 <not used>
20 00150 Financial Class O CM 50 <not used>
21 00151 Charge Price Indi- O IS 2 <not used>
cator
22 00152 Courtesy Code O IS 2 <not used>
23 00153 Credit Rating O IS 2 <not used>
24 00154 Contract Code O IS 2 <not used>
25 00155 Contract Effective O DT 8 <not used>
Date
26 00156 Contract Amount O NM 12 <not used>
27 00157 Contract Period O NM 3 <not used>
28 00158 Interest Code O IS 2 <not used>
29 00159 Transfer to Bad O IS 1 <not used>
Debt Code
30 00160 Transfer to Bad O DT 8 <not used>
Debt Date
31 00161 Bad Debt Agency O IS 10 <not used>
Code
32 00162 Bad Debt Transfer O NM 12 <not used>
Amount
33 00163 Bad Debt Recov- O NM 12 <not used>
ery Amount

124 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
34 00164 Delete Account O IS 1 <not used>
Indicator
35 00165 Delete Account O DT 8 <not used>
Date
36 00166 Discharge Dispo- O IS 3 <not used>
sition
37 00167 Discharged to O CM 25 <not used>
Location
38 00168 Diet Type O IS 2 <not used>
39 00169 Servicing Facility O IS 2 <not used>
40 00170 Bed Status B IS 1 <not used>
41 00171 Account Status O IS 2 <not used>
42 00172 Pending Location O PL 80 <not used>
43 00173 Prior Temporary O PL 80 <not used>
Location
44 00174 Admit Date/Time O TS 26 See Admit O 26
Date/Time
45 00175 Discharge O TS 26 See Dis- O 26
Date/Time charge Date
46 00176 Current Patient O NM 12 <not used>
Balance
47 00177 Total Charges O NM 12 <not used>
48 00178 Total Adjustments O NM 12 <not used>
49 00179 Total Payments O NM 12 <not used>
50 00180 Alternate Visit ID O CX 20 <not used>
51 01226 Visit Indicator O IS 1 <not used>
52 01224 Other Healthcare O XCN 60 <not used>
Provider

Patient Location
This field contains the location of the patient. It is in the format:
<Care Unit>^<Room>^<Bed>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 125
Unsolicited ADT Import

Prior Patient Location

This field contains the location of the patient to be transferred.
<Care Unit>^<Room>^<Bed>

Attending Doctor
Contains the attending physician information in the format:
<not used>^<last>^<first>^<middle>^<suffix>^<prefix>^<degree>
The data from this field will appear in the Physician field of the Patient Admit Screen of the device if ADT
data is requested for the device. In this instance, the format will be:
<last>,<first> <middle>
With a comma between the last and first name, and a single space between the first and middle names.
The name is truncated to 12 characters.

Admitting Doctor
Contains the admitting physician information in the format:
<not used>^<last>^<first>^<middle>^<suffix>^<prefix>^<degree>
Refer to Attending Doctor for details on field lengths and display formats.

Consulting Doctor
Contains the consulting physician information in the format:
<not used>^<last>^<first>^<middle>^<suffix>^<prefix>^<degree>
Refer to Attending Doctor for details on field lengths and display formats.

Referring Doctor
Contains the referring physician information in the format:
<not used>^<last>^<first>^<middle>^<suffix>^<prefix>^<degree>
Refer to Attending Doctor for details on field lengths and display formats.

Admit Date/Time
Contains the admission date in the format:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Admit Date field of the Patient Admit screen on the
device.

126 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

Discharge Date
Contains the date that the patient was discharged. It is in the format:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 127
Unsolicited ADT Import

MRG Segment - Merge Patient Information

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00211 Prior Patient ID - R CX 20 See Prior 20
Internal Internal
ID
2 00212 Prior Alternate O CX 16 <not
Patient ID used>
3 00213 Prior Patient O CX 20 See Prior 20
Account Number Patient
Account
Number
4 00214 Prior Patient ID - O CX 16 <not
External used>
5 01279 Prior Visit Number O CX 15 <not
used>
6 01280 Prior Alternate Visit O CX 20 <not
ID used>
7 01281 Prior Patient Name O XPN 48 <not
used>

Prior Internal ID
If this MRG segment is contained in a message type (based on event type) that is configured for the Merge
action, and the first component of this field is populated, it is interpreted as a request to change the MRN
(Medical Record number) of the patient from the contents of this field to that contained in the Internal ID
field of the PID segment.
If this segment is contained in a message type (based on event type) that is not configured for the “Merge”
action, then this field is ignored.

Prior Patient Account Number

If this MRG segment is contained in a message type (based on event type) that is configured for the Merge
action, and the first component of this field is populated, it is interpreted as a request to change the Patient
Account number of the patient from the contents of this field to that contained in the Patient Account Num-
ber field of the PID segment.
If this segment is contained in a message type (based on event type) that is not configured for the “Merge”
action, then this field is ignored.

128 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

OBX Segment - Observation/Result

HL7 Dräger
HL7
Seq
Item #
Description Req Type Len Contents Req Len

1 00569 Set ID – OBX O SI 10 <not used>

2 00570 Value Type C ID 2 NM, SN or R
ST(ASA only)
3 00571 Observation R CE 590 See Observa- R 2
Identifier tion Identifier
4 00572 Observation C ST 20 <not used>
Sub - ID
5 00573 Observation C * 6553 The parame- R 30
Value 6 ter value.
6 00574 Units O CE 60 See Units O 30
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal Flags O ID 5 <not used>
9 00577 Probability O NM 5 <not used>
10 00578 Nature of Abnor- O ID 2 <not used>
mal Test
11 00579 Observation R ID 1 <not used>
Result Status
12 00580 Date Last O TS 26 <not used>
Observation
Normal Values
13 00581 User Defined O ST 20 <not used>
Access Checks
14 00582 Date/Time of the O TS 26 YYYYMMD- O 12
Observation DHHmm
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 129
Unsolicited ADT Import

Observation Identifier
Uniquely identifies the parameter being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2>^<description>^<coding system >
identifier1 label for the parameter
description parameter description
identifier2 an alternate label for the parameter
coding system name of the coding system

The ADT Interface supports only “height” and “weight” for the identifier1 component. Other identifiers are
not used.

Units
Uniquely identifies the units in which the parameter is being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2>^<description>^<coding system >
identifier1 unit identifier
description unit description
identifier2 an alternate label for the unit
coding system name of the coding system

The ADT interface uses the primary identifier, identifier1, and only supports the “iso+” coding system. All
other components are not used. ASA does not have any units. The following units are supported for patient
height and weight:
Supported Height Units Supported Weight Units
Unit Description Unit Description
cm centimeters kg kilograms
m meters g grams
in inches lb pounds
ft feet oz ounces

ACK – Acknowledgment

After reception of an ADT message, an acknowledgment of the following form will be sent:
Segment Description
MSH MSH Segment - Message Header
MSA MSA Segment - Message Acknowledgment

See ADT – Admit, Discharge, and Transfer for a description of the ADT message being acknowledged.

130 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding Char- R ST 4 “^~\&” R 4
acters
3 00003 Sending Appli- O HD 180 “Infinity” O 16
cation
4 00004 Sending Facil- O HD 180 <not used>
ity
5 00005 Receiving O HD 180 The string O
Application received in the
Sending
Application
field of the
MSH segment
of the ADT
message
received.
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMD- O 12
Message DHHmmss
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 ACK^<Trig- R 7
ger Event
code>
10 00010 Message Con- R ST 20 A number or R 20
trol ID other identifier
that uniquely
identifies the
message
Sending
Application
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 131
Unsolicited ADT Import

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
15 00015 Accept O ID 2 "AL" R 2
Acknowledg-
ment Type
16 00016 Application O ID 2 "NE" R 2
Acknowledg-
ment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal Lan- O CE 60 <not used>
guage Of Mes-
sage

132 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Unsolicited ADT Import

MSA Segment - Message Acknowledgment

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00018 Acknowledg- R ID 2 See Acknowl- R 2
ment Code edgment
Codes
2 00010 Message Con- R ST 20 This field con- R 20
trol ID tains the Mes-
sage Control
ID of the mes-
sage it is
acknowledg-
ing. Refer to
MSH Seg-
ment - Mes-
sage Header
3 00020 Text Message O ST 80 An error or sta- O 80
tus string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledg-
ment Type
6 00023 Error Condition O CE 100 <not used>

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment: Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment: Error
AR Original mode: Application Reject
Enhanced mode: Application acknowledgment: Reject

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 133
Unsolicited ADT Import

ADT Message
MSH|^~\&|HIS||Infinity||199903291650||ADT|99022916500500050122|P|2.3
EVN|A01
PID|||222-22-2222||Smith^Jane||1990062659|F||A|||||||B|2002
PV1|||CCU1^201^B||||^Dixon^Glen|||||||||||||||||||||||||||||||||||||20001130
OBX||NM|height^^^^^||68|in^^ISO+|||||R|||20001126
OBX||SN|weight^^^^^||=^135|lb^^ISO+|||||R|||20001126

ACK Message
MSH|^~\&|Infinity||HIS||200105011304||ACK^R01|01040113043900414846|P|2.3
MSA|AA|99022916500500050122|[2002]ADT: Admit successful.

134 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

IHE Unsolicited ADT

The IHE unsolicited ADT interface accepts ADT messages from the transmitting system and maintains a
database of patient admission information. Data imported through this interface is used on devices by
request. Admission data is requested directly from some models of Dräger patient monitors or from an
Infinity Central Station (ICS) during a patient admission.
The Dräger HL7 server acknowledges the receipt of these messages with an ACK message to the sending
system. When ADT data requests for a particular patient, based on patient identifier, are made from the
Infinity Network, the latest data for that patient is sent to the requesting device.
When data is requested from a Infinity Central Station or a Dräger patient monitor, the patient identifier in
the request is interpreted according to the Interpret Patient ID as setting on the HL7 server. Available
values for this setting are MRN or Patient Account number.
The lower layer protocol used for this interface is Minimal Lower Layer Protocol (MLLP). See Dräger HL7
Overview for details on HL7 interfaces.

NOTE
The IHE Unsolicited and unsolicited ADT Interfaces are mutually exclusive.

For the IHE Unsolicited ADT interface, the external system (the hospital information system or HIS)
initiates the connection.
The following table indicates the data imported, the HL7 segment from which it is extracted, and the screen
where it appears on the destination Infinity monitor or Infinity Central Station (ICS).

Data Destination Monitor HL7 Segment

Imported
Application Modular Configured Telemetry
Screen Monitors Monitors
Medical Admit Some-times Some times Some times See Patient
Record Identifier
Screen
Number
Visit Number Admit Some-times Some times Some times See Patient
Identifier
Screen
Patient Name Admit Yes Yes Yes See Patient
Screen Name

Birth Date/ Admit Yes Yes Yes See Date/Time

Time of Birth
Screen
Admit Date Admit Yes Yes Yes See Admit
Date/Time
Screen
Height Admit Yes Yes Yes See
Screen Observation
Identifier

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 135
IHE Unsolicited ADT

Data Destination Monitor HL7 Segment

Imported
Application Modular Configured Telemetry
Screen Monitors Monitors
Weight Admit Yes Yes Yes See
Screen Observation
Identifier
Sex ECG Report Yes No No See Sex
Setup
Race ECG Report Yes No No See Race
Setup
Religion N/A No No No See Religion
Marital Status N/A No No No See Marital
Status
Nationality N/A No No No See National
ID/ Social
Security
Number
Primary N/A No No No See ADT
Language Config Tool for
supported
languages
Patient N/A No No No See Patient
Address Address
Admitting N/A No No No See Admitting
Doctor Doctor
Consulting N/A No No No See Consulting
Doctor Doctor
Referring N/A No No No See Referring
Doctor Doctor
National ID / N/A No No No See National
Social ID/ Social
Security Security
Number
Ethnic Group N/A No No No See Ethnic
Group

ADT data received from the hospital information system (HIS) is stored in a database on the Dräger HL7
SERVER. When a request for data is received from an Infinity device, a database lookup is done based
on Patient identifier provided by the requesting device. The patient identifier received from the requesting
device is interpreted according to the Interpret Patient ID as setting on the HL7 server.

136 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

Bedside Auto Update

This Bedside Auto Update option on the IHE Unsolicited ADT interface causes demographic data changes
received by the HL7 server to be forwarded to a patient monitor where the corresponding patient has
already been admitted, if applicable.
This feature is intended only to solve the following problem:
1 The nurse admits a patient to a patient monitor using the “Get From HIS” button on the Infinity Central
Station.
2 Someone at the admissions system notices an error in the demographic data for the patient and
corrects it.
3 The admissions systems automatically sends an update to the HL7 server.
In this situation, if the ADT Auto Update option is not enabled, the patient monitor will never be updated
with the correction unless the nurse manually requests the data from the Admissions System again by
pressing the “Get From HIS” button at the Infinity Central Station. With this feature enabled, all changes
(a patient record must already exist at the HL7 server) received from the HIS, excluding height and weight,
that are normally sent to the patient monitor when the “Get From HIS” button is pushed, will automatically
be sent to the patient monitor where the patient is admitted. Note that if the primary patient identifier is
entered at more than one patient monitor, the changes will not be sent to any patient monitor.

ADT – Admit, Discharge, and Transfer

ADT messages formats are indicated below. Square brackets, ‘[‘ and ‘]’, indicate optional segments.
Curved brackets, ‘{‘ and ‘}’, indicate segments which may be repeated.
Segment Description
MSH MSH Segment - Message Header
[EVN] EVN Segment - Event Type
PID PID Segment - Patient Identification
{[AL1]} AL1 Segment -Patient Allergy
{[IN1]} IN1 Segment – Patient Insurance
{[DG1]} DG1 Segment – Patient Diagnosis
[NK1] NK1 Segment - Next of Kin
[PV1] PV1 Segment - Patient Visit
[MRG] MRG Segment - Merge Patient Information
{[OBX]} OBX Segment - Observation/Result

Any other segments received will be ignored.

See ACK – Acknowledgment for a description of the acknowledgment sent by the Infinity application.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 137
IHE Unsolicited ADT

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00001 Field Separa- R ST 1 The separator R 1
tor between the seg-
ment ID and the
first real field,
encoding charac-
ters. It serves as
the separator and
defines the char-
acter to be used
as a separator for
the rest of the
message. Rec-
ommended value
is “|”.
2 00002 Encoding R ST 4 Four characters R 4
Characters in the following
order:
the component
separator, the
repetition separa-
tor, the escape
character, and
the subcompo-
nent separator.
Recommended
values are “^~\&”.
3 00003 Sending O HD 180 Text identifying
Application the sending appli-
cation.
4 00004 Sending O HD 180 <not used>
Facility
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 <not used>
Message
8 00008 Security O ST 40 <not used>

138 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
9 00009 Message R CM 7 This field has the R 7
Type format:
ADT^<event
type>
Supported events
are as follows:
A28 - Add person
information
A31 - Update
person
information
A40 - Merge
patient - patient
identifier list
A47 - Change
patient identifier
list
10 00010 Message R ST 20 A number or other R 20
Control ID identifier that
uniquely identi-
fies the message.
11 00011 Processing R PT 3 “P” R 3
ID
12 00012 Version ID R ID 8 "2.5" R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept O ID 2 <not used>
Acknowledg-
ment Type
16 00016 Application O ID 2 <not used>
Acknowledg-
ment
17 00017 Country O ID 2 <not used>
Code

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 139
IHE Unsolicited ADT

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
18 00692 Character O ID 6 <not used>
Set
19 00693 Principal O CE 60 <not used>
Language Of
Message

140 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

EVN Segment - Event Type

Seq HL7 HL7 Dräger

Item # Descrip- Req Type Len Contents Req Len
tion
1 00099 Event B ID 3 This field has been R 3
Type retained for backward
Code compatibility only. It is
recommended using
the second compo-
nent (Event Type) of
the message type
field of the MSH Seg-
ment - Message
Header to transmit
event type code infor-
mation.
2 00100 Recorded R TS 26 <not used>
Date/Time
3 00101 Date/Time O TS 26 <not used>
Planned
Event
4 00102 Event O IS 3 <not used>
Reason
Code
5 00103 Operator O XCN 60 <not used>
ID
6 00278 Event O TS 26 See Event Occurred O 14
Occurred

Event Occurred
The date and time that the ADT event took place, in the format:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 141
IHE Unsolicited ADT

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00104 Set ID - Patient ID O SI 40 <not used>
2 00105 Patient ID (External O CX 20 <not used>
ID)
3 00106 Patient Identifier R CX 200 See Patient Iden- R/O
tifier
4 00107 Alternate Patient ID - O CX 20 <not used> O 20
PID
5 00108 Patient Name R XPN 48 See Patient Name O
6 00109 Mother’s Maiden O XPN 48 <not used>
Name
7 00110 Date/Time of Birth O TS 26 See Date/Time of O 26
Birth
8 00111 Sex O IS 1 See Sex O 1
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 1 See Race O 26
11 00114 Patient Address O XAD 106 See Patient O
Address
12 00115 Country Code B IS 4 <not used>
13 00116 Phone Number - O XTN 40 <not used>
Home
14 00117 Phone Number - O XTN 40 <not used>
Business
15 00118 Primary Language O CE 60 See ADT Config O 4
Tool for supported
languages
16 00119 Marital Status O IS 1 See Marital Status O 1
17 00120 Religion O IS 3 See Religion O 4
18 00121 Patient Account O CX 20 See Patient Iden- R/O 20
Number tifier
19 00122 SSN Number - O ST 16 See National ID/ O 16
Patient Social Security
Number
20 00123 Driver’s License O CM 25 <not used>
Number - Patient
21 00124 Mother's Identifier O CX 20 <not used>
22 00125 Ethnic Group O IS 3 See Ethnic Group O 4

142 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth Indica- O ID 2 <not used>
tor
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Military Sta- O CE 60 <not used>
tus
28 00131 Nationality O CE 80 See Nationality O 4
29 00132 Patient Death Date O TS 26 <not used>
and Time
30 00133 Patient Death Indica- O ID 1 <not used>
tor

Patient Identifier
Depending on the Infinity Network Users setting in the HL7 configuration screen, the Patient ID field that
appears in the Patient Admit screen of the device is interpreted as either a Medical Record number or a
Patient Account number (i.e., visit number). The Identifiers in the identifier list will override any identifiers
present in seq 4, seq 18, or seq 19.
The format of either field is:
<ID>^<check digit>^<check digit scheme>^<assigning authority>^<identifier type>^<assigning facility>
The following identifiers are accepted by HL7:
– MR - MRN
– AN - Account/Visit Number
– SS - Social Security Number
– PI - Alternate Patient Identifier

NOTE
Infinity and SDC devices can support only an ID of up to 12 characters long.
The Assigning Authority component can only be up to 10 characters long.

Patient Name
Contains the patient name to be entered in the Admit screen of the device upon the request. The format is:
<Last>^<First>^<Middle>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 143
IHE Unsolicited ADT

When the device requests ADT data, the Patient Name will appear in the following format on the Patient
Admit screen: <Last Name>,<First Name> <Middle Initial/Name>
with a comma between the last and first name, and a single space between the first and middle names.
The name is truncated to 26 characters. If this field contains the string “UNKNOWN”, a blank will appear
on the Admit screen for this patient.

Date/Time of Birth
The format is:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Birth Date field of the Patient Admit Screen on the device
when ADT data is requested.

Sex
Contains a single character denoting the sex of the patient. The results of this field will be entered in the
Sex field of the ECG Report Setup Screen, if one exists, when requested during Admit by the device.
In Field On Device
F Female
M Male
All other Unknown

Race
Contains a string denoting the race of the patient. On the device the results of this field will be entered in
the Race field of the ECG Report Setup Screen, if one exists, when requested during Admit. When a
message is received from the HIS, the HIS code is compared to the list of acceptable values, and then
translated into an internal Infinity numeric code, which is then used to communicate with all of the devices.
Infinity codes 1-7 have a fixed interpretation on the device. The HIS codes, however can be configured.
Additional entries may also be added; however, any new entries will be reflected on the devices as
“Unknown”. The utility used to configure these entries is ADTConfig.exe.

In Field Infinity On Device

(HIS code) Code
2106-3 2 Caucasian
2028-9 3 Asian
2054-5 4 Black or African
American
2131-1 5 Other
1002-5 6 American Indian or
Alaska Native

144 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

In Field Infinity On Device

(HIS code) Code
2076-8 7 Native Hawaiian or
Other Pacific
Islander
All others 1 Unknown

Patient Address
This field contains the mailing address of the patient. Although HL7 supports repetition of this field, Dräger
does not, and only the first instance with address type of M (mailing) will be used. If no address is marked
as mailing, and there is an address that is unmarked for type, then it will be used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>
The component lengths supported are as follows:
Component Max Length
street1 40
street2 40
city 25
state/province 25
postal code 10
country 15
address type 1

Marital Status
The following table denotes the acceptable HIS codes that can be accepted along with their associated
meaning. Unlike many of the other codes accepted on this interface, this list is not configurable.
In Field On Device
A Separated
B Unmarried
C Common law
D Divorced
E Legally Separated
G Living together
I Interlocutory
M Married
N Annulled
O Other
P Domestic partner

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 145
IHE Unsolicited ADT

In Field On Device
R Registered domestic partner
S Single
T Unreported
W Widowed
All Other Unknown

National ID/ Social Security Number

This field contains a national identifier (such as the Social Security number in the United States).

Ethnic Group
This field contains a code, up to 4 characters long, that indicates the patient’s ethnic group. The default
configuration is detailed in the table below.
HIS Code Ethnic Group
H Hispanic or Latino
N Not Hispanic or Latino
All other Unknown

AL1 Segment -Patient Allergy

NOTE
All allergies must be included in every message, otherwise the associated allergy that is not included will
be deleted from the patient record.

AL1 Segment - Patient Allergy

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00203 Set ID - AL1 R SI 4 <not used>
2 00204 Allergy Type O IS 2 See Allergy Types O 2
3 00205 Allergy R CE 60 See Allergies R 44
Code/Mne-
monic/Descrip-
tion
4 00206 Allergy Severity O IS 2 ‘SV’ severe O 2
‘MO’ moderate
‘MI’ mild

146 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

AL1 Segment - Patient Allergy (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
5 00207 Allergy Reaction O ST 15 A string describing O 15
the reaction that
the patient has
when exposed to
the allergy
6 00208 Identification O DT 8 <not used>
Date

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 147
IHE Unsolicited ADT

Allergy Types
The following table lists the allergy types accepted by HL7:

Code Description
DA Drug Allergy
FA Food Allergy
MA Miscellaneous Allergy
MC Miscellaneous Contraindication

Allergies
This field has the format <Allergy Code>^<Allergy Description>
The Allergy Code portion of this field must match the HIS code from the pre-configured list of available
Allergy codes. The Allergy code is limited to 4 characters.
The Allergy Description portion of this field is optional and is limited to 40 characters. If the description is
provided, it supercedes the description provided in the default allergy table.

IN1 Segment – Patient Insurance

NOTE
All IN1 segments must be included in every message, otherwise the associated insurance information
that is not included will be deleted from the patient record.

148 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

IN1 Segment - Patient Insurance

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00203 Set ID - IN1 R SI 4 <not used>
2 00368 Insurance Plan R CE 60 A unique identifier R 20
ID for the insurance
plan
3 00428 Insurance Com- R CX 59 <not used>
pany ID
4 00429 Insurance Com- O XON 130 The name of the R 40
pany Name insurance com-
pany
5 00430 Insurance Com- O XAD 106 See Address O 172
pany Address
6 00431 Insurance Co. O XPN 48 <not used>
Contact Person
7 00432 Insurance Co O XTN 40 The string contact O 25
Phone Number number for the
insurance com-
pany.
8 00433 Group Number O ST 12 Identifies the O 12
group within the
insurance plan
9 00434 Group Name O XON 130 The name of the O 40
group within the
insurance plan
10 00435 Insured’s Group O CX 12 <not used>
Emp ID
11 00436 Insured’s Group O XON 130 <not used>
Emp Name
12 00437 Plan Effective O DT 8 <not used>
Date
13 00438 Plan Expiration O DT 8 <not used>
Date
14 00439 Authorization O CM 55 <not used>
Information
15 00440 Plan Type O IS 3 <not used>
16 00441 Name Of O XPN 48 See Name of O 72
Insured Insured
17 00442 Insured’s Rela- O IS 2 See Appendix J: O 3
tionship To Relationship table
Patient

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 149
IHE Unsolicited ADT

IN1 Segment - Patient Insurance (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
18 00443 Insured’s Date O TS 26 Date of birth of the O 8
Of Birth primary insurance
holder in the for-
mat
YYYYMMDD
19 00444 Insured’s O XAD 106 See Address O 172
Address
20 00445 Assignment Of O IS 2 <not used>
Benefits
21 00446 Coordination Of O IS 2 <not used>
Benefits
22 00447 Coord Of Ben. O ST 2 <not used>
Priority
23 00448 Notice Of O ID 2 <not used>
Admission Flag
24 00449 Notice Of O DT 8 <not used>
Admission Date
25 00450 Report Of Eligi- O ID 2 <not used>
bility Flag
26 00451 Report Of Eligi- O DT 8 <not used>
bility Date
27 00452 Release Infor- O IS 2 <not used>
mation Code
28 00453 Pre-Admit Cert O ST 15 <not used>
(PAC)
29 00454 Verification O TS 26 <not used>
Date/Time
30 00455 Verification By O XCN 60 <not used>
31 00456 Type Of Agree- O IS 2 <not used>
ment Code
32 00457 Billing Status O IS 2 <not used>
33 00458 Lifetime O NM 4 <not used>
Reserve Days
34 00459 Delay Before O NM 4 <not used>
L.R. Day
35 00460 Company Plan O IS 8 <not used>
Code
36 00461 Policy Number O ST 15 The policy number O 15
37 00462 Policy Deduct- O CP 12 <not used>
ible

150 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

IN1 Segment - Patient Insurance (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
38 00463 Policy Limit - B CP 12 <not used>
Amount
39 00464 Policy Limit - O NM 4 <not used>
Days
40 00465 Room Rate - B CP 12 <not used>
Semi-Private
41 00466 Room Rate - Pri- B CP 12 <not used>
vate
42 00467 Insured’s O CE 60 <not used>
Employment
Status
43 00468 Insured’s Sex O IS 1 <not used>
44 00469 Insured’s O XAD 106 <not used>
Employer
Address
45 00470 Verification Sta- O ST 2 <not used>
tus
46 00471 Prior Insurance O IS 8 <not used>
Plan ID
47 01227 Coverage Type O IS 3 <not used>
48 00753 Handicap O IS 2 <not used>
49 01230 Insured’s ID O CX 12 <not used>
Number

Address
Repetition is not supported for this field, and only the first instance will be used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>
The component lengths supported are as follows:

Component Max Length

street1 40
street2 40
city 25
state/province 25
postal code 10
country 15

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 151
IHE Unsolicited ADT

Name of Insured
Contains the name of the primary insured person, The format is:
<Last Name>^<First Name>^<Middle name>
The maximum component lengths are as follows. If a component exceeds the maximum length, it will be
truncated.
Component Max Length
Last 30
First 20
Middle 20

DG1 Segment – Patient Diagnosis

NOTE
All DG1 segments must be included in every message, otherwise the associated diagnosis information
that is not included will be deleted from the patient record.

152 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

DG1 Segment - Patient Diagnostics

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00375 Set ID - DG1 R SI 4 <not used>
2 00376 Diagnosis (B) R ID 2 <not used>
Coding
Method
3 00377 Diagnosis O CE 60 See Diagno- R 51
Code sis
4 00378 Diagnosis B ST 40 The descrip- O 42
Description tion of the
diagnosis.
Note that this
field is only
used if com-
ponent 2 of
field 3 above
is not popu-
lated
5 00379 Diagnosis O TS 26 <not used>
Date/Time
6 00380 Diagnosis R IS 2 Valid values O 1
Type are:
‘A’: Admitting
‘W’: Working
(default)
‘F’: Final
7 00381 Major Diag- B CE 60 <not used>
nostic Cate-
gory
8 00382 Diagnostic B IS 4 <not used> O 4
Related
Group
9 00383 DRG B ID 2 <not used>
Approval Indi-
cator
10 00384 DRG Grouper B IS 2 <not used>
Review Code
11 00385 Outlier Type B CE 60 <not used>
12 00386 Outlier Days B NM 3 <not used>
13 00387 Outlier Cost B NM 12 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 153
IHE Unsolicited ADT

DG1 Segment - Patient Diagnostics (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
14 00388 Grouper Ver- B ST 4 <not used>
sion And
Type
15 00389 Diagnosis B NM 2 <not used>
Priority
16 00390 Diagnosing O XCN 60 <not used>
Clinician
17 00766 Diagnosis O IS 3 <not used>
Classification
18 00767 Confidential O ID 1 <not used>
Indicator
19 00768 Attestation O TS 26 <not used>
Date/Time

Diagnosis
This field is of the format:
<ID>^<Text>
Where
ID - contains the code that identifies the diagnosis (up to 8 characters)
Text - description of the diagnosis (up to 42 characters)

154 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

NK1 Segment - Next of Kin

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00190 Set ID – NK1 R SI 4 <not used>
2 00191 Name O XPN 48 See Name O
3 00192 Relationship O CE 60 See Appen- O 3
dix J: Rela-
tionship
table
4 00193 Address O XAD 106 See O 106
Address
5 00194 Phone Num- O XTN 40 A string O 25
ber contact
number
6 00195 Business O XTN 40 A string O 25
Phone Num- contact
ber number
7 00196 Contact Role O CE 60 <not used>
8 00197 Start Date O DT 8 <not used>
9 00198 End Date O DT 8 <not used>
10 00199 Job Title O ST 60 <not used>
11 00200 Job O CM 20 <not used>
Code/Class
12 00201 Employee O CX 20 <not used>
Number
13 00202 Organiza- O XON 60 <not used>
tion Name
14 00119 Marital Sta- O IS 2 <not used>
tus
15 00111 Sex O IS 1 <not used>
16 00110 Date/Time of O TS 26 <not used>
Birth
17 00755 Living O IS 2 <not used>
Dependency
18 00145 Ambulatory O IS 2 <not used>
Status
19 00129 Citizenship O IS 4 <not used>
20 00118 Primary Lan- O CE 60 <not used>
guage

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 155
IHE Unsolicited ADT

NK1 Segment - Next of Kin (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
21 00742 Living O IS 2 <not used>
Arrangement
22 00743 Publicity O IS 1 <not used>
Indicator
23 00744 Protection O ID 1 <not used>
Indicator
24 00745 Student Indi- O IS 2 <not used>
cator
25 00120 Religion O IS 3 <not used>
26 00746 Mother’s O XPN 48 <not used>
Maiden
Name
27 00739 Nationality O CE 80 <not used>
28 00125 Ethnic Group O IS 3 <not used>
29 00747 Contact O CE 80 <not used>
Reason
30 00748 Contact Per- O XPN 48 <not used>
son’s Name
31 00749 Contact Per- O XTN 40 <not used>
son’s Tele-
phone
Number
32 00750 Contact Per- O XAD 106 <not used>
son’s
Address
33 00751 Identifiers O CX 32 <not used>
34 00752 Job Status O IS 2 <not used>
35 00113 Race O IS 1 <not used>
36 00753 Handicap O IS 2 <not used>
37 00754 Contact Per- O ST 16 <not used>
son’s Social
Security
Number

156 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

Name
Contains the name of the next of kin/associated party. The format is: <Last Name>^<First Name>
The maximum component lengths are as follows. If a component exceeds the maximum length, it will be
truncated.
Component Max Length
Last 30
First 20

Address
This field contains the mailing address of the next of kin/associated party. Although HL7 supports
repetition of this field, Dräger does not, and only the first instance will be used.
<street1>^<street2>^<city>^<state/province>^<postal code>^<country>
The component lengths supported are as follows:
Component Max Length
street1 40
street2 40
city 25
state/province 25
postal code 10
country 15

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 157
IHE Unsolicited ADT

PV1 Segment - Patient Visit

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 O SI 4 <not used>
2 00132 Patient Class R IS 1 Patient Class
3 00133 Assigned Patient O PL 80 See Patient
Location Location
4 00134 Admission Type O IS 2 <not used>
5 00135 Preadmit Number O CX 20 <not used>
6 00136 Prior Patient Loca- O PL 80 See Prior
tion Patient Location
7 00137 Attending Doctor O XCN 60 If IHE O
Compliant:
<not used>
If IHE non
Compliant:
"^Last
Name^First
Name ^Middle
Name ^Suf-
fix^Pre-
fix^Degree"
8 00138 Referring Doctor O XCN 60 If IHE
Compliant:
<Not used>
If IHE non
Compliant:
"^Last
Name^First
Name ^Middle
Name ^Suf-
fix^Pre-
fix^Degree"

158 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
9 00139 Consulting Doctor O XCN 60 If IHE
Compliant:
<not used>
If IHE non
Compliant:
"^Last
Name^First
Name ^Middle
Name ^Suf-
fix^Pre-
fix^Degree"
10 00140 Hospital Service O IS 3 <not used>
11 00141 Temporary Location O PL 80 <not used>
12 00142 Preadmit Test Indi- O IS 2 <not used>
cator
13 00143 Readmission Indica- O IS 2 <not used>
tor
14 00144 Admit Source O IS 3 <not used>
15 00145 Ambulatory Status O IS 2 <not used>
16 00146 VIP Indicator O IS 2 <not used>
17 00147 Admitting Doctor O XCN 60 If IHE
Compliant:
<not used>

If IHE non
Compliant:
"^Last
Name^First
Name ^Middle
Name ^Suf-
fix^Pre-
fix^Degree"
18 00148 Patient Type O IS 2 <not used>
19 00149 Visit Number O CX 20 <not used>
20 00150 Financial Class O CM 50 <not used>
21 00151 Charge Price Indica- O IS 2 <not used>
tor

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 159
IHE Unsolicited ADT

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
22 00152 Courtesy Code O IS 2 <not used>
23 00153 Credit Rating O IS 2 <not used>
24 00154 Contract Code O IS 2 <not used>
25 00155 Contract Effective O DT 8 <not used>
Date
26 00156 Contract Amount O NM 12 <not used>
27 00157 Contract Period O NM 3 <not used>
28 00158 Interest Code O IS 2 <not used>
29 00159 Transfer to Bad Debt O IS 1 <not used>
Code
30 00160 Transfer to Bad Debt O DT 8 <not used>
Date
31 00161 Bad Debt Agency O IS 10 <not used>
Code
32 00162 Bad Debt Transfer O NM 12 <not used>
Amount
33 00163 Bad Debt Recovery O NM 12 <not used>
Amount
34 00164 Delete Account Indi- O IS 1 <not used>
cator
35 00165 Delete Account Date O DT 8 <not used>
36 00166 Discharge Disposi- O IS 3 <not used>
tion
37 00167 Discharged to Loca- O CM 25 <not used>
tion
38 00168 Diet Type O IS 2 <not used>
39 00169 Servicing Facility O IS 2 <not used>
40 00170 Bed Status B IS 1 <not used>
41 00171 Account Status O IS 2 <not used>
42 00172 Pending Location O PL 80 <not used>
43 00173 Prior Temporary O PL 80 <not used>
Location

160 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
44 00174 Admit Date/Time O TS 26 See Admit O 26
Date/Time
45 00175 Discharge O TS 26 See Discharge O 26
Date/Time Date

Patient Location
This field contains the location of the patient (destination location in a ADT – Admit, Discharge, and
Transfer). It is in the format:
<Care Unit>^<Room>^<Bed>

Prior Patient Location

This field contains the location of the patient to be transferred.
<Care Unit>^<Room>^<Bed>

Admit Date/Time
Contains the admission date in the format:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Admit Date field of the Patient Admit screen on the
device.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 161
IHE Unsolicited ADT

MRG Segment - Merge Patient Information

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00211 Prior Patient Identi- R CX 20 See Prior 20
fier List Patient
Identifier
List
2 00212 Prior Alternate O CX 16 <not
Patient ID used>
3 00213 Prior Patient O CX 20 <not 20
Account Number used>
4 00214 Prior Patient ID - O CX 16 <not
External used>
5 01279 Prior Visit Number O CX 15 <not
used>
6 01280 Prior Alternate Visit O CX 20 <not
ID used>
7 01281 Prior Patient Name O XPN 48 <not
used>

Prior Patient Identifier List

If this MRG segment is contained in an A40 message that is configured for the ADT – Admit, Discharge,
and Transfer action, then the identifiers in this list will be interpreted as a request to change Identifiers of
the patient from the contents of this field to the those contained in the Patient Identifier List of the PID
segment. The Identifiers in this field will overwrite any identifiers in SEQ 3 of the PID segment.
The following identifiers are accepted by HL7:
– MR - MRN
– AN - Account/Visit Number
If this segment is contained in a message of typeA28, A31, or A47, then this field is ignored.

Prior Patient Account Number

If this MRG segment is contained in an A40 message that is configured for the ADT – Admit, Discharge,
and Transfer action, and the first component of this field is populated, it is interpreted as a request to
change the Patient Account number of the patient from the contents of this field to that contained in the
Patient Account Number field of the PID segment.
If this segment is contained in a message type (based on event type) that is not configured for the “Merge”
action, then this field is ignored.

162 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

OBX Segment - Observation/Result

HL7 Dräger
HL7
Seq
Item #
Description Req Type Len Contents Req Len

1 00569 Set ID – OBX O SI 10 <not used>

2 00570 Value Type C ID 2 NM or SN R
3 00571 Observation R CE 590 See Observa- R 2
Identifier tion Identifier
4 00572 Observation C ST 20 <not used>
Sub - ID
5 00573 Observation C * 6553 The parame- R 30
Value 6 ter value.
6 00574 Units O CE 60 See Units O 30
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal Flags O ID 5 <not used>
9 00577 Probability O NM 5 <not used>
10 00578 Nature of Abnor- O ID 2 <not used>
mal Test
11 00579 Observation R ID 1 <not used>
Result Status
12 00580 Date Last O TS 26 <not used>
Observation
Normal Values
13 00581 User Defined O ST 20 <not used>
Access Checks
14 00582 Date/Time of the O TS 26 YYYYMMD- O 12
Observation DHHmm
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

Observation Identifier
Uniquely identifies the parameter being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2>^<description>^<coding system >
identifier1 label for the parameter
description parameter description
identifier2 an alternate label for the parameter
coding system name of the coding system

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 163
IHE Unsolicited ADT

The IHE ADT interface supports only the LOINC codes for Height ("8303-0"), and Weight ("3142-7").
Other identifiers are not used.

Units
Uniquely identifies the units in which the parameter is being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2>^<description>^<coding system >
identifier1 unit identifier
description unit description
identifier2 an alternate label for the unit
coding system name of the coding system

The ADT interface uses the primary identifier, identifier1, and only supports the “iso+” coding system. All
other components are not used. The following units are supported for patient height and weight:

Supported Height Units Supported Weight Units

Unit Description Unit Description
cm centimeters kg kilograms
m meters g grams
in inches lb pounds
ft feet oz ounces

ACK – Acknowledgment

After reception of an ADT message, an acknowledgment of the following form will be sent:
Seqment Description
MSH MSH Segment - Message Header
MSA MSA Segment - Message Acknowledgment

See ADT – Admit, Discharge, and Transfer for a description of the ADT message being acknowledged.

164 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding Char- R ST 4 “^~\&” R 4
acters
3 00003 Sending Appli- O HD 180 INFO_S- O 16
cation RC_DRAE-
GER^0030E6
0000000001^
EUI-64
4 00004 Sending Facil- O HD 180 <not used>
ity
5 00005 Receiving O HD 180 The string O
Application received in the
Sending
Application
field of the
MSH segment
of the ADT
message
received.
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMD- O 12
Message DHHmmss+/-
ZZZZ
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 ACK^<Event R 7
type>^ACK
10 00010 Message Con- R ST 20 A number that R 20
trol ID uniquely iden-
tifies the mes-
sage Sending
Application
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.5” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 165
IHE Unsolicited ADT

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
15 00015 Accept O ID 2 <not used> R 2
Acknowledg-
ment Type
16 00016 Application O ID 2 <not used> R 2
Acknowledg-
ment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 8859/1
19 00693 Principal Lan- O CE 60 en^English^IS
guage Of Mes- O639
sage

166 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 IHE Unsolicited ADT

MSA Segment - Message Acknowledgment

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 See Acknowledg- R 2
Code ment Codes
2 00010 Message Control R ST 20 This field con- R 20
ID tains the Mes-
sage Control ID
of the message it
is acknowledg-
ing. Refer to MSH
Segment - Mes-
sage Header
3 00020 Text Message O ST 80 An error or status O 80
string
4 00021 Expected O NM 15 <not used>
Sequence Num-
ber
5 00022 Delayed Acknowl- B ID 1 <not used>
edgment Type
6 00023 Error Condition O CE 100 <not used>

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
IHE mode: Application acknowledgment: Accept
AE Original mode: Application Error
IHE mode: Application acknowledgment: Error
AR Original mode: Application Reject
IHE mode: Application acknowledgment: Reject

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 167
IHE Unsolicited ADT

Sample ADT Message

MSH|^~\&|?|HIS|?|Infinity|20050530082015||ADT^A28^ADT_A05|99022916500500050122|P|2.5E
VN||20050530082000||||PID||123456|555-55-5555^^^MRN-AA^MR~987-65-4321^^^SS-
AA^SS~5005^^^Visit-AA^AN||Schmidt^Roberta^K.|Adams|2000062800|W||O|12 Blackrock
Lane^^Wakefield^MA^12345-6785^USA||212 397-
1486||USA|S|JEW|||||NHIS||||||USAPV1|N||||||OBX||NM|3142-7^BODY WEIGHT
(STATED)^LN||58|kg|||||FOBX||NM|8303-0^BODY HEIGHT^LN||1.25|m|||||F

Sample ACK Message

MSH|^~\&|Infinity||?|HIS|20160506113933||ACK^A28|16050611393300091753|P|2.5|||AL|NEMSA|
AA|16050611393300014707|[5005]ADT: Admit successful

168 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

Solicited ADT Import

The HL7 Access option can be used for the import of ADT data. The ADT system responds by transmitting
the latest data for that patient to the HL7 server. This data is then forwarded to the requesting device. The
responding system has 27 seconds to respond to an ADT Query message.
Refer to Dräger HL7 Overview for details on HL7 interfaces.

NOTE
The solicited and unsolicited ADT Interfaces are mutually exclusive.

For the Solicited ADT interface, Dräger initiates the connection.

The Solicited ADT import interface is used to import demographic data into a device, if the data is
requested from the device. The requester must supply an identifier of the type defined in the "Interpret
Patient ID as " setting.
Data Imported Destination Monitor HL7 Segment
Application Modular Configured Telemetry
Screen Monitors Monitors
Medical Record Admit Sometimes Sometimes Sometimes See Patient
Number Identifier
Screen
Visit Number Admit Sometimes Sometimes Sometimes See Patient
Screen Identifier

Patient Name Admit Yes Yes Yes See Patient

Name
Screen
Birth Date/Time Admit Yes Yes Yes See Date of
Birth
Screen
Admit Date Admit Yes Yes Yes See Admit
Screen Date

Attending Admit Yes Yes Yes See Attending

doctor Doctor
Screen
Height Admit Yes Yes Yes See
Observation
Screen
Identifier
Weight Admit Yes Yes Yes See
Screen Observation
Identifier
Sex ECG Report Yes No No See Sex
Setup
Race ECG Report Yes No No See Race
Setup

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 169
Solicited ADT Import

QRY – Patient Query

ADT Query messages are of the following format:

Seqment Description
MSH MSH Segment - Message Header Query
QRD QRD Segment - Original Type Query Definition

See ADR – Query Response for a description of the response message expected from the responding
application.
MSH Segment - Message Header Query

HL7 Dräger
HL7
Seq Item #
Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding R ST 4 “^~\&” R 4
Characters
3 00003 Sending O HD 180 “INFINITY” O 16
Application
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving O HD 180 “NUR” O
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMDDhh O 12
Message mmss
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “QRY^A19” R 7
10 00010 Message Control R ST 20 A number or R 20
ID other identifier
uniquely identi-
fying the mes-
sage. The
responding
system echoes
this ID back to
the sending
system in the
Message
Acknowledg-
ment segment
(MSA).
11 00011 Processing ID R PT 3 “P” R 3

170 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

MSH Segment - Message Header Query (Continued)

HL7 Dräger
HL7
Seq Item #
Description Req Type Len Contents Req Len
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept O ID 2 "AL" R 2
acknowledgment
Type
16 00016 Application O ID 2 "NE" R 2
acknowledgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal O CE 60 <not used>
Language Of
Message

QRD Segment - Original Type Query Definition

Seq HL7 HL7 Dräger

Item Description Req Type Len Contents Req Len
#
1 00025 Query R TS 26 YYYYMMDDhhm R 26
Date/Time mss
2 00026 Query R ID 1 “R” R 1
Format Code
3 00027 Query R ID 1 “I” R 1
Priority
4 00028 Query ID R ST 10 A unique identifier R 10
for the query. It is
returned intact by
the responding
application.
5 00029 Deferred O ID 1 <not used>
Response
Type
6 00030 Deferred O TS 26 <not used>
Response
Date/Time

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 171
Solicited ADT Import

QRD Segment - Original Type Query Definition (Continued)

Seq HL7 HL7 Dräger

Item Description Req Type Len Contents Req Len
#
7 00031 Quantity R CQ 10 "1^RD" R 10
Limited
Request
8 00032 Who Subject R XCN 60 See Who Subject R 60
Filter Filter
9 00033 What R CE 60 See What Subject R 60
Subject Filter Filter
10 00034 What R CE 60 <not used>
Department
Data Code
11 00035 What Data O ST 20 <not used>
Code Value
Qual.
12 00036 Query O TS 1 <not used>
Results
Level

172 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

What Subject Filter

A string which denotes how the Who Subject Filter field is to be interpreted, as follows:
Field Contents Identifier Type
APA Patient Account number
APM Medical Record Number

Who Subject Filter

The Patient identifier of the patient for whom data is being requested, in the form:
<ID> ^ ^ ^ ^ ^ ^ ^ ^ <assigning authority>
For an APA query (patient account number), the ID component contains the Patient Account number and
the assigning authority component is not valued.
For an APM query (medical record number), the ID component contains the MRN and the assigning
authority component is optionally valued.

ADR – Query Response

Upon receiving a QRY message, the following message will be sent by the responding system. Square
brackets, ‘[‘ and ‘]’ indicate optional segments. Curved brackets ‘{‘ and ‘}’ indicate segments that can be
repeated.
Seqment Description
MSH MSH Segment - Message Header
MSA MSA Segment - Message Acknowledgment
QRD QRD Segment - Original Type Query Definition
PID PID Segment - Patient Identification
[PV1] PV1 Segment - Patient Visit
[{OBX}] OBX Segment - Observation/Result

Refer to QRY – Patient Query for a description of the QRY message being responded to.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 173
Solicited ADT Import

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 The separator R 1
between the
segment ID and the
first real field,
encoding
characters. Serves
as the separator and
defines the
character to be used
as a separator for
the rest of the
message.
Recommended
value is “|”.
2 00002 Encoding R ST 4 Four characters in R 4
Characters the following order:
the component
separator, the
repetition separator,
the escape
character, and the
subcomponent
separator.
Recommended
values are ^~\&.
3 00003 Sending O HD 180 A string identifying O 16
Application the Sending
Application.
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving O HD 180 <not used>
Application
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of O TS 26 YYYYMMDDhhmm O 12
Message ss
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ADR^A19” R 7
10 00010 Message Control R ST 20 A number or other R 20
ID identifier uniquely
identifying the
message.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8

174 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept O ID 2 <not used>
acknowledgment
Type
16 00016 Application O ID 2 <not used>
acknowledgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal O CE 60 <not used>
Language Of
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 175
Solicited ADT Import

MSA Segment - Message Acknowledgment

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 R 2
Code
2 00010 Message Control R ST 20 The message R 20
ID control ID of the
message it is
acknowledging.
Refer to MSH
Segment -
Message
Header
3 00020 Text Message O ST 80 An error or O 80
status string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledgment
Type
6 00023 Error Condition O CE 100 <not used>

176 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment: Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment: Error
AR Original mode: Application Reject
Enhanced mode: Application acknowledgment: Reject

QRD Segment – Original Type Query Definition

The QRD segment in the request (see Acknowledgment Codes) is echoed back to the requester.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 177
Solicited ADT Import

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00104 Set ID - Patient O SI 4 <not used>
ID
2 00105 Patient ID O CX 20 <not used>
(External ID)
3 00106 Patient ID R CX 20 See Patient R/O
(Internal ID) Identifier
4 00107 Alternate Patient O CX 20 <not used>
ID - PID
5 00108 Patient Name R XPN 48 See Patient O
Name
6 00109 Mother’s Maiden O XPN 48 <not used>
Name
7 00110 Date/Time of O TS 26 See Date of O 26
Birth Birth
8 00111 Sex O IS 1 See Sex O 1
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 1 See Race O 26
11 00114 Patient Address O XAD 106 <not used> O
12 00115 County Code B IS 4 <not used>
13 00116 Phone Number - O XTN 40 <not used>
Home
14 00117 Phone Number - O XTN 40 <not used>
Business
15 00118 Primary O CE 60 <not used> O 4
Language
16 00119 Marital Status O IS 1 <not used> O 1
17 00120 Religion O IS 3 See ADTConfig O 4
tool for
supported
religions.
18 00121 Patient Account O CX 20 See Patient R/O
Number Identifier
19 00122 SSN Number - O ST 16 <not used> O 16
Patient
20 00123 Driver's License O CM 25 <not used>
Number – Patient
21 00124 Mother's Identifier O CX 20 <not used>
22 00125 Ethnic Group O IS 3 <not used> O 4
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth O ID 2 <not used>
Indicator

178 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Military O CE 60 <not used>
Status
28 00131 Nationality O CE 80 <not used> O 4
29 00132 Patient Death O TS 26 <not used>
Date and Time
30 00133 Patient Death O ID 1 <not used>
Indicator

Patient Identifier
Depending on the in the HL7 configuration screen, the Patient ID field that appears in the Patient Admit
screen of devices is interpreted as either a Medical Record number, retrieved from PID segment Seq#3,
or a Patient Account number (i.e. visit number), retrieved from Seq#18 of the PID segment.
The format of either field is:
<ID>^<Text digit>^<check digit scheme>^<assigning authority>^<identifier type>^<assigning facility>
The ID component and assigning authority are used for the MRN (seq#3), but only the ID component is
used in the Patient Account number (seq#18).

CAUTION
Infinity and SDC devices can support only an ID of up to 12 characters long.
The Assigning Authority component can only be up to 10 characters long.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 179
Solicited ADT Import

Patient Name
Contains the patient name to be entered in the Admit screen of the device upon request. The format is:
<Last>^<First>^<Middle>
When the device requests ADT data, the patient name will appear in the following format on the Patient
Admit screen: <Last Name>,<First Name> <Middle Initial/Name>
with a comma between the last and first name, and a single space between the first and middle names.
The name is truncated to 26 characters. If this field contains the string “UNKNOWN”, a blank will appear
on the Admit screen for this patient.
Date of Birth
The format is:
YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Birth Date field of the Patient Admit screen on the device
when ADT data is requested.
Sex
Contains a single character denoting the sex of the patient. The results of this field will be entered in the
Sex field of the ECG Report Setup screen, if one exists, when requested during admit by the device.
In Field On Device
F Female
M Male
All other Unknown

Race
Contains a string denoting the race of the patient. The results of this field will be entered in the Race field
of the ECG Report Setup Screen, if one exists, when requested during admit.

In Field On Device
(HIS code)
2106-3 Caucasian
2028-9 Asian
2054-5 Black or African
American
2131-1 Other
1002-5 American Indian or
Alaska Native
2076-8 Native Hawaiian or
Other Pacific
Islander
All others Unknown

180 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

PV1 Segment - Patient Visit

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 O SI 4 <not used>
2 00132 Patient Class R IS 1 <not used>
3 00133 Assigned Patient O PL 80 <not used>
Location
4 00134 Admission Type O IS 2 <not used>
5 00135 Preadmit Number O CX 20 <not used>
6 00136 Prior Patient O PL 80 <not used>
Location
7 00137 Attending Doctor O XCN 60 See Attending O 60
Doctor
8 00138 Referring Doctor O XCN 60 <not used>
9 00139 Consulting Doctor O XCN 60 <not used>
10 00140 Hospital Service O IS 3 <not used>
11 00141 Temporary O PL 80 <not used>
Location
12 00142 Preadmit Test O IS 2 <not used>
Indicator
13 00143 Readmission O IS 2 <not used>
Indicator
14 00144 Admit Source O IS 3 <not used>
15 00145 Ambulatory Status O IS 2 <not used>
16 00146 VIP Indicator O IS 2 <not used>
17 00147 Admitting Doctor O XCN 60 <not used>
18 00148 Patient Type O IS 2 <not used>
19 00149 Visit Number O CX 20 <not used>
20 00150 Financial Class O CM 50 <not used>
21 00151 Charge Price O IS 2 <not used>
Indicator
22 00152 Courtesy Code O IS 2 <not used>
23 00153 Credit Rating O IS 2 <not used>
24 00154 Contract Code O IS 2 <not used>
25 00155 Contract Effective O DT 8 <not used>
Date
26 00156 Contract Amount O NM 12 <not used>
27 00157 Contract Period O NM 3 <not used>
28 00158 Interest Code O IS 2 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 181
Solicited ADT Import

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
29 00159 Transfer to Bad O IS 1 <not used>
Debt Code
30 00160 Transfer to Bad O DT 8 <not used>
Debt Date
31 00161 Bad Debt Agency O IS 10 <not used>
Code
32 00162 Bad Debt Transfer O NM 12 <not used>
Amount
33 00163 Bad Debt O NM 12 <not used>
Recovery Amount
34 00164 Delete Account O IS 1 <not used>
Indicator
35 00165 Delete Account O DT 8 <not used>
Date
36 00166 Discharge O IS 3 <not used>
Disposition
37 00167 Discharged to O CM 25 <not used>
Location
38 00168 Diet Type O IS 2 <not used>
39 00169 Servicing Facility O IS 2 <not used>
40 00170 Bed Status B IS 1 <not used>
41 00171 Account Status O IS 2 <not used>
42 00172 Pending Location O PL 80 <not used>
43 00173 Prior Temporary O PL 80 <not used>
Location
44 00174 Admit Date/Time O TS 26 See Admit Date O 26
45 00175 Discharge O TS 26 <not used>
Date/Time
46 00176 Current Patient O NM 12 <not used>
Balance
47 00177 Total Charges O NM 12 <not used>
48 00178 Total Adjustments O NM 12 <not used>
49 00179 Total Payments O NM 12 <not used>
50 00180 Alternate Visit ID O CX 20 <not used>
51 01226 Visit Indicator O IS 1 <not used>
52 01224 Other Healthcare O XCN 60 <not used>
Provider

182 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

Attending Doctor
Contains the attending physician information in the format:
<not used>^<last>^<first>^<middle>^<suffix>^<prefix>^<degree>
The data from this field will appear in the Physician field of the Patient Admit Screen of the device if ADT
data is requested for the device. In this instance, the format will be:
<last>,<first> <middle>
With a comma between the last and first name, and a single space between the first and middle names.
The name is truncated to twelve characters.
Admit Date
Contains the admission date in the format: YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ]
The date portion of this field will be entered in the Admit Date field of the Patient Admit screen on the
device that ADT is requested from.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 183
Solicited ADT Import

OBX Segment - Observation/Result

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00569 Set ID – OBX O SI 10 <not used>
2 00570 Value Type C ID 2 NM or SN R 2
3 00571 Observation R CE 590 See Observation R
Identifier Identifier
4 00572 Observation Sub- C ST 20 <not used>
ID
5 00573 Observation C * 655 See Observation R 30
Value 36 Value
6 00574 Units O CE 60 See Units O 30
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal Flags O ID 5 <not used>
9 00577 Probability O NM 5 <not used>
10 00578 Nature of O ID 2 <not used>
Abnormal Test
11 00579 Observ Result R ID 1 <not used> 1
Status
12 00580 Date Last Obs O TS 26 <not used>
Normal Values
13 00581 User Defined O ST 20 <not used>
Access Checks
14 00582 Date/Time of the O TS 26 YYYYMMDDhhm O 12
Observation mss
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

184 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

Observation Identifier
Uniquely identifies the parameter being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2 >^<description>^<coding system >
identifier1 label for the parameter
description parameter description
identifier2 an alternate label for the parameter
coding system name of the coding system

The ADT Interface supports only “height,” and “weight,” for the identifier1 component. Other identifiers are
not used.
Observation Value
The Observation Value field contains the parameter value. The format of this field varies according to the
Value Type field as follows:
Value Type Observation Value Field Format
NM <value>
SN <comparator>^<value>

For values of type SN, the comparator must be equal to “=” or blank; otherwise the data will not be
imported into the HL7 server.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 185
Solicited ADT Import

Units
The Units field uniquely identifies the units in which the parameter is being reported, in the format:
<identifier1 >^<description>^<coding system>^<identifier2 >^<description>^<coding system >
identifier1 unit identifier
description unit description
identifier2 an alternate identifier for the unit
coding system name of the coding system

The ADT interface uses the primary identifier, identifier1, and only supports the “iso+” coding system. All
other components are not used.
The following units are supported for patient height and weight:

Supported Height Units Supported Weight Units

Unit Description Unit Description
cm centimeters kg kilograms
m meters g grams
in inches lb pounds
ft feet oz ounces

186 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Solicited ADT Import

Sample

QRY Message
MSH|^~\&|Infinity||NUR||200301152306||QRY^A19|03001523064500052645|P|2.3
QRD|200301152306|R|I|4500052655|||1^RD|1001|APA|

ADR Message
MSH|^~\&|HIS||Infinity||199903291650||ADR^A19|99022916500500050122|P|2.3
MSA|AA|03001523064500052645|Patient found
QRD|19990322160000|R|I|4500052655|||1^RD|1001|APA
PID|||1001||Smith^Wally^L.||194204301420|M||W|||978 907-7333||||Ch|1001
PV1|||CCU1^200^A||||021-55-1366^Munster^F.^S|||||||||||||||||||||||||||||||||||||199804300430
OBX||NM|height^^^^^||182.9|cm^^ISO+|||||R|||19990329165005
OBX||SN|weight^^^^^||=^29.3|kg^^ISO+|||||R|||19990329165005

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 187
 This page has been left blank intentionally.

188 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

Lab Import

In the Lab Import interface, the HL7 server will accept laboratory data in an Unsolicited Observation
Results message (ORU). It will acknowledge receipt of an ORU message with an ACK message. It will
then attempt to find a patient monitor on the Infinity network with the corresponding identifier. If one, and
only one such patient monitor is found, and the monitor is a Modular monitor, then the data is forwarded
to the patient monitor.

CAUTION
– Lab data transmitted to all patient monitors is in ANSI characters. If the incoming lab data contains
Unicode (non-ANSI characters), then a character mapping must be configured or all characters in
the non-ANSI range will get removed from the message.
– Lab data is not supported on SDC-only devices.

By default, the identifier used to locate the patient on the Infinity network is the primary identifier in the
incoming message. If, however, the external system (LIS) does not have this identifier available, the
alternate identifier can be provided instead, provided that the Unsolicited ADT interface is also enabled,
and the “Allow patient to be identified by Alternate Identifier” option is enabled on this interface.
For the Lab Import interface, the external system (the Laboratory Information System or LIS) initiates the
connection. Refer to Dräger HL7 Overview for details on HL7 interfaces.
Although the incoming message format is different, the functionality of the HL7 Lab Import and the ASTM
Lab import are virtually identical.

Organizing the data

HL7/ASTM provides a mechanism by which the customer can organize incoming lab data and control how
the data is represented on the destination device (i.e. or patient monitor). The user can:
 Define any number of parameter groups and the associated group label to be used when displaying
them.
 Define each parameter that can be expected to be received from the central laboratory, assign a group
to each parameter and a priority within the group for the parameter.
This setup information is stored in the Lab Import database. When a message is received by the HL7
service, the data is reorganized according to this configuration. Groups with lower numbered priorities
appear nearest to the top of the message. Parameters are placed into the group to which they have been
assigned, with lower numbered priorities appearing first. Grouping labels are also embedded before the
data is forwarded to the destination device. If a defined group has no associated parameters in the
message, then the group label is not included in the message.
If none of the parameters received are defined as part of a group then no reorganization occurs. If,
however, at least one parameter is defined as part of a group, the message is reformatted with grouping
information. Note that any parameter received that is not defined as being a member of a group will
automatically be assigned to the group “Other”, which has the highest numbered priority and therefore
goes at the bottom of the message.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 189
Lab Import

NOTE
To configure the databases for importing HL7 laboratory data, a device ID of “HL7” is used.

Please refer to the on-line help for the HL7 setup program for more details on how to perform the
configuration.

Lab data on the patient monitor

Alert message
When lab data is received on a patient monitor, a message is displayed in the message area indicating
that new lab data has been received. Once the newly received lab data has been reviewed, this message
is cleared from the message area.

Lab data display

The patient monitor’s lab data review screen is of the following format:
<Time Label> <Date and Time>
<Group Label>
<param> <value> <units>
<param> <value> <units>
<Group Label>
<param> <value> <units>
<param> <value> <units>

The group labels and order of appearance of parameters on the screen is defined by the group and priority
settings in the Lab Import database setup.
The date and time that is displayed on the screen is the date and time associated with the first OBX-14
that appears in the reorganized message, if that field is populated. In this case the Time Label used is
“Test Time” (or a translation if English is not being used).
If no date/time appears in OBX-14 of the first parameter, then the time displayed will be the time that the
message arrived at the patient monitor, and the Time Label will be “Arrival Time” (or a translation).

Hemo/Oxy/Vent Calculator
Under certain conditions, the patient monitor will also allow the user to import parameter data received into
the Hemo/Oxy/Vent Calculator, if this option is enabled at the monitor. In order to import the data, HL7 also
needs additional configuration information that maps the parameter labels to be received from the central
laboratory into known parameters at the patient monitor. This calculator mapping is also performed in the
HL7 setup application.
Parameters that can be imported into the calculator are:
 SaO2

190 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

 PAO2
 PACO2
 HgB
 pH
 HCO3
 HCT
 SVO2
 PVO2
Note that the patient monitor also requires that the parameter be a recent measurement. Please refer to
the instructions for use for the specific patient monitor for more details.

Parameter time stamp

The time stamp for each parameter will be determined in the following priority order:
 OBX-14 relating to the parameter
 OBX-14 relating to the first time-stamped parameter in the message
 Time the message was received

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 191
Lab Import

ORU - Unsolicited Observation Report

The Lab Import interface will accept ORU messages. Square brackets [and] indicate optional segments.
Curved brackets {and} indicate segments that may be repeated.
Segment Description
MSH MSH Segment - Message Header
{
PID PID Segment - Patient Identification
[PV1] PV1 Segment – Patient Visit
[ORC] ORC Segment – Common Order
[OBR] OBR Segment - Observation Request
[
{
OBX OBX Segment - Observation/Result
}
]
}

Refer to ACK - Acknowledgment for a description of the acknowledgments.

192 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00001 Field Separa- R ST 1 The separator R 1
tor between the seg-
ment ID and the
first real field,
encoding charac-
ters. As such it
serves as the sep-
arator and defines
the character to be
used as a separa-
tor for the rest of
the message. Rec-
ommended value
is “|”.
2 00002 Encoding R ST 4 The four charac- R 4
Characters ters in the follow-
ing order: the
component sep-
arator, the repeti-
tion separator, the
escape character,
and the subcom-
ponent separator.
Recommended
values are ^~\&.
3 00003 Sending O HD 180 A site-specific O 16
Application value used for cus-
tomization.
4 00004 Sending Facil- O HD 180 <not used>
ity
5 00005 Receiving O HD 180 <not used> O
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMD- O 12
Message DHHmmss. See
Bedside Lab data
display and
Parameter time
stamp for details
on how time
stamps are used
on the destination
device.
8 00008 Security O ST 40 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 193
Lab Import

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
9 00009 Message R CM 7 “ORU ^R01” R 7
Type
10 00010 Message R ST 20 A number or other R 20
Control ID identifier uniquely
identifying the
message. The
Infinity Gateway
sends send this ID
back to the send-
ing system in the
Message acknowl-
edgment segment
(MSA).
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” or “2.3.1” R 8
13 00013 Sequence O NM 15 This numeric field O 15
Number is incremented by
one for each sub-
sequent value, if
sequencing is
enabled.
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept O ID 2 <not used>
Acknowledg-
ment Type
16 00016 Application O ID 2 <not used>
Acknowledg-
ment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal Lan- O CE 60 <not used>
guage Of
Message

194 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00104 Set ID - Patient ID O SI 4 <not used>
2 00105 Patient ID (Exter- O CX 20 <not used>
nal ID)
3 00106 Patient ID (Inter- R CX 20 Medical Record
nal ID) Number of the
patient. See PID
Segment – Identi-
fier Mapping
4 00107 Alternate Patient O CX 20 <not used>
ID - PID
5 00108 Patient Name R XPN 48 <not used>
6 00109 Mother’s Maiden O XPN 48 <not used>
Name
7 00110 Date/Time of Birth O TS 26 <not used>
8 00111 Sex O IS 1 <not used>
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 26 <not used>
11 00114 Patient Address O XAD 1 <not used>
12 00115 County Code B IS 48 <not used>
13 00116 Phone Number - O XTN 1 <not used>
Home
14 00117 Phone Number - O XTN 106 <not used>
Business
15 00118 Primary Language O CE 4 <not used>
16 00119 Marital Status O IS 40 <not used>
17 00120 Religion O IS 40 <not used>
18 00121 Patient Account O CX 60 The ID of the R 12
Number patient to whom
this data belongs.
19 00122 SSN Number - O ST 1 <not used>
Patient
20 00123 Driver's License O CM 25 <not used>
Number - Patient
21 00124 Mother's Identifier O CX 20 <not used>
22 00125 Ethnic Group O IS 3 <not used>
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth Indi- O ID 2 <not used>
cator

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 195
Lab Import

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Military O CE 60 <not used>
Status
28 00131 Nationality O CE 80 <not used>
29 00132 Patient Death O TS 26 <not used>
Date and Time
30 00133 Patient Death O ID 1 <not used>
Indicator

PID Segment – Identifier Mapping

The primary identifier is used to locate the patient on the Infinity network. The primary identifier is driven
by the “Interpret Patient ID as” setting. If, however, the external system (LIS) does not have a the primary
identifier available, the secondary identifier can be provided instead provided that the Unsolicited ADT
interface is also enabled, and the “Allow patient to be identified by Alternate Identifier” option is enabled
on this interface.

PV1 Segment – Patient Visit

This segment is not used by this application.

ORC Segment – Common Order

This segment is not used by this application.

196 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

OBR Segment - Observation Request

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00237 Set ID - OBR C SI 4 <not used>
2 00216 Placer Order Number C EI 75 <not used>
3 00217 Filler Order Number + C EI 75 <not used>
4 00238 Universal Service ID R CE 200 <not used>
5 00239 Priority B ID 2 <not used>
6 00240 Requested Date/time B TS 26 <not used>
7 00241 Observation Date/Time C TS 26 See Observation R 14
# Date/Time
8 00242 Observation End O TS 26 <not used>
Date/Time
9 00243 Collection Volume O CQ 20 <not used>
10 00244 Collector Identifier O XCN 60 <not used>
11 00245 Specimen Action Code O ID 1 <not used>
12 00246 Danger Code O CE 60 <not used>
13 00247 Relevant Clinical Info. O ST 300 <not used>
14 00248 Specimen Received C TS 26 <not used>
Date/Time
15 00249 Specimen Source O CM 300 <not used>
16 00226 Ordering Provider O XCN 80 <not used>
17 00250 Order Callback Phone O XTN 40 <not used>
Number
18 00251 Placer field 1 O ST 60 <not used>
19 00252 Placer field 2 O ST 60 <not used>
20 00253 Filler Field 1 + O ST 60 <not used>
21 00254 Filler Field 2 + O ST 60 <not used>
22 00255 Results Report/Status C TS 26 <not used>
Date/Time
23 00256 Charge to Practice + O CM 40 <not used>
24 00257 Diagnostic Service O ID 10 <not used>
Section ID
25 00258 Result Status + C ID 1 <not used>
26 00259 Parent Result + O CM 400 <not used>
27 00221 Quantity/Timing O TQ 200 <not used>
28 00260 Result Copies To O XCN 150 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 197
Lab Import

OBR Segment - Observation Request (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
29 00261 Parent O CM 150 <not used>
30 00262 Transportation Mode O ID 20 <not used>
31 00263 Reason for Study O CE 300 <not used>
32 00264 Principal Result Inter- O CM 200 <not used>
preter +
33 00265 Assistant Result Inter- O CM 200 <not used>
preter +
34 00266 Technician + O CM 200 <not used>
35 00267 Transcriptionist + O CM 200 <not used>
36 00268 Scheduled Date/Time + O TS 26 <not used>
37 01028 Number of Sample O NM 4 <not used>
Containers
38 01029 Transport Log of Col- O CE 60 <not used>
lected Sample
39 01030 Collector's Comment O CE 200 <not used>
40 01031 Transport Arrange. O CE 60 <not used>
Responsibility
41 01032 Transport Arranged O ID 30 <not used>
42 01033 Escort Required O ID 1 <not used>
43 01034 Planned Patient Trans- O CE 200 <not used>
port Comment

Observation Date/Time
If any of the OBX segments that follow the OBR do not contain a timestamp in OBX-14, then this field is
used by as the time of that associated parameter.

198 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

OBX Segment - Observation/Result

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len Repeatable
1 00569 Set ID – OBX O SI 10 <not used>
2 00570 Value Type C ID 2 SN,NM or ST R 2
3 00571 Observation R CE 590 In the first component, R
Identifier the label to be displayed
on the Infinity monitor.
4 00572 Observation C ST 20 <not used>
Sub-ID
5 00573 Observation C * 65536 See Observation Value R 30
Value
6 00574 Units O CE 60 Uniquely identifies the O 30
units in which the param-
eter will be reported. The
first component of this
field will be displayed on
the Infinity patient
monitor.
7 00575 Reference O ST 10 <not used>
Range
8 00576 Abnormal O ID 5 <not used>
Flags
9 00577 Probability O NM 5 <not used>
10 00578 Nature of O ID 2 <not used>
Abnormal Test
11 00579 Observe Result R ID 1 Reflects the current com- R 1
Status pletion status of the
results for one Observa-
tion Identifier. If this field
contains an ‘F’ (final), ‘C’
(corrected) or ‘S’ (partial),
then the corresponding
parameter data will be
displayed on destination
system. If any other value
appears in this field, the
corresponding parameter
data will be ignored.
12 00580 Date Last Obs O TS 26 <not used>
Normal Values
13 00581 User Defined O ST 20 <not used>
Access Checks

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 199
Lab Import

OBX Segment - Observation/Result (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len Repeatable
14 00582 Date/Time of O TS 26 YYYYMMDDHHmmss. O 14
the Observa- See Bedside Lab data
tion display and Parameter
time stamp for details on
how time stamps are
used on the destination
device.
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

Observation Value
Contains the parameter value to be displayed on the Infinity monitor. The format of this field varies
according to the Value Type field, as follows:
Value Observation Value Field Format
ST <value>
NM <value>
SN <comparator>^<value>

For SN value types, the comparator must be equal to “=” or blank; otherwise the data will not be imported
into the INFINITY Network.

ACK - Acknowledgment

After receipt of an ORU message, the HL7 server will send an acknowledgment:
Segment Description
MSH MSH Segment - Message Header
MSA MSA Segment – Message Acknowledgment

See ORU - Unsolicited Observation Report for a description of the ORU message being acknowledged.

200 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

MSH Segment - Message Header

Seq HL7 Item # HL7 Dräger

Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding Characters R ST 4 “^~\&” R 4
3 00003 Sending Application O HD 180 “INFINITY” O 16
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving Application O HD 180 The string identifying O
the Sending Applica-
tion in the ORU mes-
sage being
acknowledged.
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of Mes- O TS 26 YYYYMMDDHHmm O 12
sage
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ACK^R01” R 7
10 00010 Message Control ID R ST 20 A number or other R 20
identifier uniquely
identifying the mes-
sage.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence Number O NM 15 <not used>
14 00014 Continuation Pointer O ST 180 <not used>
15 00015 Accept acknowledg- O ID 2 “AL” R 2
ment Type
16 00016 Application acknowl- O ID 2 “NE” R 2
edgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal Language Of O CE 60 <not used>
Message

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 201
Lab Import

MSA Segment – Message Acknowledgment

Seq HL7 Item # HL7 Dräger
Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 See Acknowledg- R 2
Code ment Codes
2 00019 Message Control ID R ST 20 The message con- R 20
trol ID of the mes-
sage it is
acknowledging.
3 00020 Text Message O ST 80 An error or status O 80
string
4 00021 Expected Sequence O NM 15 <not used>
Number
5 00022 Delayed Acknowl- B ID 1 <not used>
edgment Type
6 00023 Error Condition O CE 100 <not used>

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment: Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment: Error
AR Original mode: Application Reject
Enhanced mode: Application acknowledgment: Reject

202 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Import

Sample

This sample assumes that the setting is set to MRN.

ORU Message
MSH|^~\&|LIS||Infinity||20050426113505||ORU^R01|05042611350503887179|P|2.3
PID|||9009|||||||||||||||999-99-9999
OBR|1||||||200501191400
OBX|1|ST|K.||6.5|mmol/l|||||F
OBX|1|SN|PO2||=^100|mmHg|||||F
OBX|1|NM|PCO2||40|mmHg|||||F

ACK Message
MSH|^~\&|Infinity||LIS||20050426113509||ACK^R01|99022518340103894120|P|2.3
MSA|AA|17042411075600136436|[9009]Message Delivered

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 203
 This page has been left blank intentionally.

204 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Export

Lab Export

Using the Lab Export Interface, MIB Blood Gas results can be exported from an MIB-compliant device
connected to an Infinity monitor via a serial link. This data will be transmitted by the HL7 server in an Unso-
licited Observation Results message (ORU). Upon receipt of an ORU message, the receiving system
should acknowledge receipt with an ACK message. MIB Blood Gas results can be exported from Infinity
Modular monitors. See Dräger HL7 Overview or details on how Dräger implements HL7 interfaces.
For the Lab Export interface, Dräger initiates the connection.

NOTE
The Lab Export interface is not available for SDC-only devices.

ORU - Unsolicited Observation Report

The Lab Export interface will generate ORU messages listed below. Square brackets, [and], indicate
optional segments. Curved brackets, {‘ and ‘} indicate segments which may be repeated.
Segment Description
MSH MSH Segment - Message Header
PID PID Segment - Patient Identification
OBR OBR Segment - Observation Request
[{OBX}] OBX Segment - Observation/Result

See ACK - Acknowledgment for a description of the acknowledgment expected by the HL7 server.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 205
Lab Export

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|”. R 1
2 00002 Encoding Characters R ST 4 “^~\&” R 4
3 00003 Sending Application O HD 180 “Infinity” O 16
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving Application O HD 180 “NUR” O
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of Message O TS 26 YYYYMMDDHHmm O 12
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ORU ^R01” R 7
10 00010 Message Control ID R ST 20 A number that R 20
uniquely identifies
the message.
Dräger expects this
ID to be sent back in
the Message
acknowledgment
segment (MSA).
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence Number O NM 15 This numeric field is O 15
incremented by one
for each subsequent
value, if sequencing
is enabled.
14 00014 Continuation Pointer O ST 180 <not used>
15 00015 Accept Acknowledg- O ID 2 "AL" R 2
ment Type
16 00016 Application Acknowledg- O ID 2 "NE" R 2
ment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 <not used>
19 00693 Principal Language Of O CE 60 <not used>
Message

206 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Export

PID Segment - Patient Identification

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00104 Set ID - Patient ID O SI 4 <not used>
2 00105 Patient ID (External ID) O CX 20 <not used>
3 00106 Patient ID (Internal ID) R CX 20 Medical Record Number R 12
unless unavailable. Then
it contains duplicate of
Patient Account Number
field, HL7 Item # 00121,
with an “AN” in the sec-
ond component.
4 00107 Alternate Patient ID – PID O CX 20 <not used>
5 00108 Patient Name R XPN 48 UNKNOWN R 12
6 00109 Mother’s Maiden Name O XPN 48 <not used>
7 00110 Date/Time of Birth O TS 26 <not used>
8 00111 Sex O IS 1 <not used>
9 00112 Patient Alias O XPN 48 <not used>
10 00113 Race O IS 26 <not used>
11 00114 Patient Address O XAD 1 <not used>
12 00115 County Code B IS 48 <not used>
13 00116 Phone Number – Home O XTN 1 <not used>
14 00117 Phone Number – Business O XTN 106 <not used>
15 00118 Primary Language O CE 4 <not used>
16 00119 Marital Status O IS 40 <not used>
17 00120 Religion O IS 40 <not used>
18 00121 Patient Account Number O CX 60 Patient Account number R 12
19 00122 SSN Number – Patient O ST 1 <not used>
20 00123 Driver's License Number - O CM 25 <not used>
Patient
21 00124 Mother's Identifier O CX 20 <not used>
22 00125 Ethnic Group O IS 3 <not used>
23 00126 Birth Place O ST 60 <not used>
24 00127 Multiple Birth Indicator O ID 2 <not used>
25 00128 Birth Order O NM 2 <not used>
26 00129 Citizenship O IS 4 <not used>
27 00130 Veterans Military Status O CE 60 <not used>
28 00131 Nationality O CE 80 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 207
Lab Export

PID Segment - Patient Identification (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
29 00132 Patient Death Date and O TS 26 <not used>
Time
30 00133 Patient Death Indicator O ID 1 <not used>

OBR Segment - Observation Request

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00237 Set ID - OBR C SI 4 <not used>
2 00216 Placer Order Number C EI 75 <not used>
3 00217 Filler Order Number + C EI 75 <not used>
4 00238 Universal Service ID R CE 200 <not used>
5 00239 Priority B ID 2 <not used>
6 00240 Requested Date/time B TS 26 <not used>
7 00241 Observation Date/Time # C TS 26 Date the observation R 14
was obtained from the
Infinity Network, in the
format YYYYMMD-
DHHmmss.
8 00242 Observation End O TS 26 <not used>
Date/Time
9 00243 Collection Volume O CQ 20 <not used>
10 00244 Collector Identifier O XCN 60 <not used>
11 00245 Specimen Action Code O ID 1 <not used>
12 00246 Danger Code O CE 60 <not used>
13 00247 Relevant Clinical Info. O ST 300 <not used>
14 00248 Specimen Received C TS 26 <not used>
Date/Time
15 00249 Specimen Source O CM 300 <not used>
16 00226 Ordering Provider O XCN 80 <not used>
17 00250 Order Callback Phone O XTN 40 <not used>
Number
18 00251 Placer field 1 O ST 60 <not used>
19 00252 Placer field 2 O ST 60 <not used>
20 00253 Filler Field 1 + O ST 60 <not used>
21 00254 Filler Field 2 + O ST 60 <not used>
22 00255 Results Rpt/Status Chng - C TS 26 <not used>
Date/Time +

208 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Export

OBR Segment - Observation Request (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
23 00256 Charge to Practice + O CM 40 <not used>
24 00257 Diagnostic Serv Sect ID O ID 10 <not used>
25 00258 Result Status + C ID 1 <not used>
26 00259 Parent Result + O CM 400 <not used>
27 00221 Quantity/Timing O TQ 200 <not used>
28 00260 Result Copies To O XCN 150 <not used>
29 00261 Parent O CM 150 <not used>
30 00262 Transportation Mode O ID 20 <not used>
31 00263 Reason for Study O CE 300 <not used>
32 00264 Principal Result Inter- O CM 200 <not used>
preter +
33 00265 Assistant Result Inter- O CM 200 <not used>
preter +
34 00266 Technician + O CM 200 <not used>
35 00267 Transcriptionist + O CM 200 <not used>
36 00268 Scheduled Date/Time + O TS 26 <not used>
37 01028 Number of Sample Con- O NM 4 <not used>
tainers
38 01029 Transport Logistics of Col- O CE 60 <not used>
lected Sample
39 01030 Collector's Comment O CE 200 <not used>
40 01031 Transport Arrangement O CE 60 <not used>
Responsibility
41 01032 Transport Arranged O ID 30 <not used>
42 01033 Escort Required O ID 1 <not used>
43 01034 Planned Patient Transport O CE 200 <not used>
Comment

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 209
Lab Export

OBX Segment - Observation/Result

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00569 Set ID – OBX O SI 10 <not used>
2 00570 Value Type C ID 2 “SN” (structured R 2
numeric) if the
parameter value
reported is numeric,
otherwise “ST”
(string).
3 00571 Observation R CE 590 This field contains, in R
Identifier the first component,
the label that is dis-
played on the patient
monitor.
4 00572 Observation C ST 20 <not used>
Sub-ID
5 00573 Observation C * 655 See Observation R 30
Value 36 Value
6 00574 Units O CE 60 This first component O 30
of this field contains
the units string that is
displayed on the
patient monitor.
7 00575 References O ST 10 <not used>
Range
8 00576 Abnormal O ID 5 <not used>
Flags
9 00577 Probability O NM 5 <not used>
10 00578 Nature of O ID 2 <not used>
Abnormal Test
11 00579 Observation R ID 1 The flag ‘R’ indicat- R 1
Result Status ing that the results
have not been veri-
fied.
12 00580 Date Last O TS 26 <not used>
Observation
Normal Values
13 00581 User Defined O ST 20 <not used>
Access
Checks

210 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Export

OBX Segment - Observation/Result (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
14 00582 Date/Time of O TS 26 The date and time for O 14
the Observa- this observation as
tion reported in the
"Date/Time Test
Started” field of the
corresponding ASTM
results record.
15 00583 Producer's ID O CE 60 <not used>
16 00584 Responsible O XCN 80 <not used>
Observer
17 00936 Observation O CE 60 <not used>
Method

Observation Value
The parameter value as reported by the point-of-care laboratory device. The format of this field varies
according to the Value Type field.
Value Type Observation Value Field Format Comments
ST <value>
SN <comparator>^<value> comparator is “=”

ACK - Acknowledgment

After transmission of an ORU message, an acknowledgment of the following format is expected:

Segment Description
MSH MSH Segment - Message Header
MSA MSA Segment – Message Acknowledgment

See Section ORU - Unsolicited Observation Report for a description of the ORU message being acknowl-
edged.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 211
Lab Export

MSH Segment – Message Header

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding Char- R ST 4 “^~\&” R 4
acters
3 00003 Sending Applica- O HD 180 INFO_SRC_DRAE- O 16
tion GER^0030E6000000
0001^EUI-64
4 00004 Sending Facility O HD 180 <not used>
5 00005 Receiving Appli- O HD 180 <not used> O
cation
6 00006 Receiving Facility O HD 180 <not used>
7 00007 Date/Time of O TS 26 YYYYMMDDHHmm O 12
Message
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 “ACK^R01” R 7
10 00010 Message Control R ST 20 Must contain a num- R 20
ID ber that uniquely
identifies the mes-
sage.
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.3” R 8
13 00013 Sequence Num- O NM 15 <not used>
ber
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept Acknowl- O ID 2 <not used>
edgment Type
16 00016 Application O ID 2 <not used>
Acknowledgment
17 00017 Country Code O ID 2 <not used>
18 00692 Character Set O ID 6 8859/1
19 00693 Principal Lan- O CE 60 <not used>
guage Of Mes-
sage

212 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Lab Export

MSA Segment – Message Acknowledgment

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00018 Acknowledgment R ID 2 MSA Segment – R 2
Code Message
Acknowledgment
2 00010 Message Control R ST 20 This field must R 20
ID contain the
message control ID
of the message it is
acknowledging.
3 00020 Text Message O ST 80 An error or status O 80
string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledgment
Type
6 00023 Error Condition O CD 10 <not used>

Acknowledgment Codes
Value Description
AA Original mode: Application Accept
Enhanced mode: Application acknowledgment: Accept
AE Original mode: Application Error
Enhanced mode: Application acknowledgment: Error
AR Original mode: Application Reject
Enhanced mode: Application acknowledgment: Reject

If an acknowledgment code of AE is received from the destination device, the HL7 server will attempt to
retransmit the message as many times as this interface is configured in the HL7 setup program.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 213
Lab Export

Sample

ORU Message
MSH|^~\&|Infinity||NUR||200011201019||ORU^R01||P|2.3
PID|||999-99-9999||UNKNOWN^^||||||||||||999-99-9999
OBR|1||||||20001120101911
OBX||ST|pH^^^^^||7.35|^^|||||R
OBX||ST|PO2^^^^^||10.4|mmHg|||||R
OBX||ST|Hct^^^^^||31.5|%|||||R

ACK Message
MSH|^~\&|Infinity||MEDAT-18||199903251834||ACK^R01|99022518340103894120|P|2.3
MSA|AA|17042411161900020570|[999-99-9999]Message Delivered

214 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Alarm Communication Management Interface

The HL7/ASTM Interface Option enables the export of alarm data in an unsolicited Observation Results
message (ORU) using HL7 version V2.6. The data is sent using IHE compliant nomenclatures. The
interface can be configured to be IHE PC D ACM compliant, or by default may contain additional or omitted
data causing it to be non-compliant. One ORU message is sent for each alarm update.
Upon receipt of an ORU message, the receiving system should acknowledge receipt with an ACK
message. Refer to Dräger HL7 Overview for details on HL7 interfaces.
For the Alarm Communication Management interface, Dräger initiates the connection.
The measured value of a parameter in an HL7 ACM profile may be a value sampled immediately before
or after occurrence of the alarm, and may not match the value that actually generated the alarm.

NOTE
The Alarm Communication Management interface is only available for SDC devices.

ORU - Unsolicited Observation Report

ORU messages follow the format below. The curved brackets {‘ and ‘} indicate segments which may be
repeated.
Segments Description
MSH MSH Segment – Message Header
PID PID Segment - Patient Identification
PV1 PV1 Segment - Patient Visit
OBR OBR Segment - Observation Request
{OBX} OBX Segment - Observation/Result

Patient Demographic Data

If patient demographic data is found in the Infinity Gateway, then the fields indicated above will be
populated in the following format: <Code>^<Text>. To locate the possible values for these fields look at
the corresponding tab in the ADT Config tool. If the patient demographic data is not found then these fields
are not used.
See ACK – Acknowledgment for a description of the acknowledgment message expected from the receiv-
ing application. If no acknowledgment is received within the Response Timeout configured in the HL7
ACM Interface Configuration screen, the message is retransmitted up to Retry Count times.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 215
Alarm Communication Management Interface

MSH Segment – Message Header

HL7 Dräger
HL7
Seq Item
# Le
Description Req Type Len Contents Req n

1 00001 Field Separator R ST 1 “|” R 1

2 00002 Encoding Charac- R ST 4 “^~\&” R 4
ters
3 00003 Sending Applica- R HD 227 "INFO_S- R 16
tion RC_DRAE-
GER^0030E60000
000001^EUI-64"
4 00004 Sending Facility RE HD 227 “Draeger” R 16
5 00005 Receiving Applica- RE HD 227 Configurable in R 227
tion Infinity Gateway
Configuration
6 00006 Receiving Facility RE HD 227 Configurable in R 227
Infinity Gateway
Configuration
7 00007 Date/Time of Mes- R DTM 24 YYYYMMD- O 12
sage DHHmmSS <Off-
Set>
8 00008 Security X ST 40 <not used>
9 00009 Message Type R MSG 15 “ORU^R40^ORU_ R 7
R40”
10 00010 Message Control R ST 199 A number R 20
ID uniquely
identifying the
message.
The receiving
system
echoes this ID
back to the
sending system
in the
message
acknowledgment
segment
(MSA).
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R VID 60 “2.6” R 8
13 00013 Sequence Number RE NM 15 <not used>
14 00014 Continuation X ST 180 <not used>
Pointer

216 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

MSH Segment – Message Header (Continued)

HL7 Dräger
HL7
Seq Item
# Le
Description Req Type Len Contents Req n

15 00015 Accept Acknowl- R ID 2 “AL”

edgment Type
16 00016 Application R ID 2 “NE”
Acknowledgment
Type
17 00017 Country Code RE ID 3 <not used>
18 00692 Character Set RE ID 16 "8859/1"
19 00693 Principal Lan- RE CWE 705 “en^English^ISO6
guage Of Message 39”
20 Alternate Character X ID 20 <not used>
Set Handling
Scheme
21 Message Profile O EI 427 “IHE_PCD_AC-
Identifier M_001^IHE
PCD^1.3.6.1.4.1.1
9376.1.6.4.4^ISO"
22 Sending Responsi- X XON 567 <not used>
ble Organization
23 Receiving Respon- X XON 567 <not used>
sible Organization
24 Sending Network X HD 227 <not used>
Address
25 Receiving Network X HD 227 <not used>
Address

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 217
Alarm Communication Management Interface

PID Segment - Patient Identification

Seq HL7 Dräger

Description Req Type Len Contents Req Len
1 Set ID - PID X SI 4 <not used>
2 Patient ID X CX 20 <not used>
3 List C CX 250 See Patient Identi- R 12
fier List
4 Alternate Patient ID - PID X CX 20 <not used>
5 Patient Name C XPN 250 See Name R 250
6 Mother’s Maiden Name RE XPN 250 See Name R 250
7 Date/Time of Birth RE DTM 24 YYYYMMD- R 24
Dhhmmss
8 Administrative Sex RE IS 705 For Non IHE Compli- R 705
ant:
*"Code^Text"
Taken from ADT
Configuration Infor-
mation.

For IHE Compliant:

*"Code"
Taken from ADT
Configuration Infor-
mation.
9 Patient Alias X XPN 250 <not used>
10 Race RE CWE 705 *”Code^Text” R 705
Taken from ADT
Configuration Infor-
mation.
11 Patient Address RE XAD 250 *”Street1^Street2^Ci R 250
ty^State^Zip
Code^Country"^M
12 County Code RE IS 4 <not used>
13 Phone Number - Home RE XTN 250 <not used> R
14 Phone Number - Business X XTN 250 <not used>
15 Primary Language RE CWE 705 *"Code^Text"
Taken from ADT
Configuration Infor-
mation.

218 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

PID Segment - Patient Identification (Continued)

Seq HL7 Dräger

Description Req Type Len Contents Req Len
16 Marital Status RE CWE 705 *”Code^Text" R 705
Taken from ADT
Configuration Infor-
mation.
17 Religion RE CWE 705 *"Code^Text" Taken R 705
from ADT Configura-
tion Information.
18 Patient Account Number RE CX 705 <not used> R 12
19 SSN Number - Patient X ST 16 <not used> R 16
20 Driver's License Number - RE DLN 25 <not used>
Patient
21 Mother’s Identifier RE CX 705 <not used>
22 Ethnic Group RE CWE 705 *"Code^Text"
Taken from ADT
Configuration Infor-
mation.
23 Birth Place RE ST 705 <not used>
24 Multiple Birth Indicator RE ID 1 <not used>
25 Birth Order RE NM 2 <not used>
26 Citizenship RE CWE 705 <not used>
27 Veterans Military Status RE CWE 705 <not used>
28 Nationality RE CWE 705 *"Code^Text"
Taken from ADT
Configuration Infor-
mation.
29 Patient Death Date and RE DTM 24 <not used>
Time
30 Patient Death Indicator RE ID 1 <not used>
31 Identity Unknown Indicator RE ID 1 <not used>
32 Identity Reliability Code RE IS 20 <not used>
33 Last Update Date/Time RE DTM 24 <not used>
34 Last Update Facility RE HD 241 <not used>
35 Species Code RE CWE 705 <not used>
36 Breed Code C CWE 250 <not used>
37 Strain C ST 80 <not used>
38 Production Class Code RE CWE 705 <not used>
39 Tribal Citizenship RE CWE 705 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 219
Alarm Communication Management Interface

Patient Identifier List

Depending on the configuration of the primary identifier, the Patient ID field that appears in the Patient
Admit screen of SDC devices, is interpreted as either a Medical Record number or a Patient Account num-
ber (i.e. visit number).
The primary identifier will appear in the following format: <Primary ID>^^^< Assigning Authority>^<ID
Type>.
If the ADT information is located for the patient then the secondary ID will be displayed in the same format
in a second repetition of the list as follows: <Primary ID>^^^<Assigning Authority>^<ID Type>~
<Secondary ID>^^^<ID Assigning Authority>^<ID Type>. Note, however, that the Assigning Authority is
only available for an MRN, not for Patient Account Number.

Name
The patient name will be in the following format: <Last> ^>First> ^<Middle> ^^^^<Type>.
If at least the last name is known then the Type will be “L”. If the name is not know then the Type will be “U”.

NOTE
All items with an asterisk * are only sent out when the “ADT Data in Message” option is enabled for ACM,
and data is found for the patient. Otherwise the fields are <not used>.

PV1 Segment - Patient Visit

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
1 00131 Set ID - PV1 X SI 4 <not used>
2 00132 Patient Class R IS 1 *Patient Class R 1
3 00133 Assigned RE PL 80 <Care Unit
Patient Loca-
Label>^^<Bed
tion
Label>^<Hospi-
tal/Facility>
4 00134 Admission X IS 2 <not used> R 18
Type
5 00135 Preadmit Num- X CX 250 <not used>
ber
6 00136 Prior Patient X PL 80 <not used>
Location
7 00137 Attending Doc- X XCN 250 See Doctor’s O 250
tor Name
8 00138 Referring Doc- X XCN 250 See Doctor’s O 250
tor Name
9 00139 Consulting X XCN 250 See Doctor’s O 250
Doctor Name

220 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
10 00140 Hospital Ser- X IS 3 <not used>
vice
11 00141 Temporary X PL 80 <not used>
Location
12 00142 Preadmit Test X IS 2 <not used>
Indicator
13 00143 Readmission X IS 2 <not used>
Indicator
14 00144 Admit Source X IS 6 <not used>
15 00145 Ambulatory X IS 2 <not used>
Status
16 00146 VIP Indicator X IS 2 <not used>
17 00147 Admitting Doc- X XCN 250 See Doctor’s O 250
tor Name
18 00148 Patient Type X IS 2 <not used>
19 00149 Visit Number RE CX 250 <not used>
20 00150 Financial Class X FC 50 <not used>
21 00151 Charge Price X IS 2 <not used>
Indicator
22 00152 Courtesy Code X IS 2 <not used>
23 00153 Credit Rating X IS 2 <not used>
24 00154 Contract Code X IS 2 <not used>
25 00155 Contract Effec- X DT 8 <not used>
tive Date
26 00156 Contract X NM 12 <not used>
Amount
27 00157 Contract Period X NM 3 <not used>
28 00158 Interest Code X IS 2 <not used>
29 00159 Transfer to Bad X IS 4 <not used>
Debt Code
30 00160 Transfer to Bad X DT 8 <not used>
Debt Date
31 00161 Bad Debt X IS 10 <not used>
Agency Code
32 00162 Bad Debt X NM 12 <not used>
Transfer
Amount

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 221
Alarm Communication Management Interface

PV1 Segment - Patient Visit (Continued)

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
33 00163 Bad Debt X NM 12 <not used>
Recovery
Amount
34 00164 Delete Account X IS 1 <not used>
Indicator
35 00165 Delete Account X DT 8 <not used>
Date
36 00166 Discharge Dis- X IS 3 <not used>
position
37 00167 Discharged to X DLD 47 <not used>
Location
38 00168 Diet Type X CWE 705 <not used>
39 00169 Servicing Facil- X IS 2 <not used>
ity
40 00170 Bed Status X IS 1 <not used>
41 00171 Account Status X IS 2 <not used>
42 00172 Pending Loca- X PL 80 <not used>
tion
43 00173 Prior Tempo- X PL 80 <not used>
rary Location
44 00174 Admit RE DTM 24 <not used> R 24
Date/Time
45 00175 Discharge X DTM 24 <not used>
Date/Time
46 00176 Current Patient X NM 12 <not used>
Balance
47 00177 Total Charges X NM 12 <not used>
48 00178 Total Adjust- X NM 12 <not used>
ments
49 00179 Total Payments X NM 12 <not used>
50 00180 Alternate Visit X CX 250 <not used>
ID
51 01226 Visit Indicator RE IS 1 <not used>

Doctor’s Name
If the interface is configured to be IHE compliant then this field is not used. If the interface is not configured to be IHE
compliant then the format will be as follows: ^<Last Name>^<First Name>^<Middle Name>^<Suffix>^<Prefix>^
<Degree>.

222 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

OBR Segment - Observation Request

Seq HL7 HL7 Dräger

Item #
Description Re Typ Len Contents Req Len
q e
1 00104 Set ID OBR R SI 4 Observation Set R 4
Number
2 00105 Placer Order C EI 427 <not used>
Number
3 00106 Filler Order R EI 427 <OrderNumber>^ R 427
Number <Order Application>
4 00107 Universal Ser- R CW 705 “196616^MDC_EVT_ R 40
vice Identifier E ALARM^MDC”
5 00108 Priority - OBR X ID 2 <not used>
6 00109 Requested X DT 24 <not used>
Date/Time M
7 00110 Observation RE DT 24 YYYYMMD- R 24
Date/Time M Dhhmmss+/-ZZZZ
8 00111 Observation RE DT 24 <not used>
End Date / M
Time
9 00112 Collection Vol- X CQ 722 <not used>
ume
10 00113 Collection R2 XC 3220 <not used>
Identifier N

OBX Segment - Observation/Result

For the Alarm Management interface there are up to 7 OBX segments sent.
The following OBX segments are sent:
OBX 1: MDS information
Seq HL7 HL7 Dräger
Item # Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “1” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observation R CWE 705 <CF_Code10>^<R R 20
Identifier eference ID>^MDC
4 00004 Observation R ST 20 "1.0.0.0" R 20
Sub-
5 00005 Observation C Varies 99999 <not used> R
Value

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 223
Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observation R ID 1 “F” R 1
Result Sta-
tus
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used> O 24
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observation RE CWE 705 <not used>
Method
18 00692 Equipment RE EI 427 <UniqueID>^<mod R 427
Instance el>^<manufac-
Identifier turer url>^<univer-
sal id type>
If serial number is
received then
unique id will be
serial number, oth-
erwise it will be the
IP/MAC address of
the device.

224 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observation RE CWE 705 <not used>
Site

OBX 2: Alarm Identification

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “2” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observation R CWE 705 <CF_Code10>^<R R 20
Identifier eference ID>^MDC
4 00004 Observation R ST 20 1.<VMD_In- R 20
Sub- stance>.<Chan-
nel_Instance>.<C
F_Code10>.<Met-
ric_Instance>.“2”
5 00005 Observation C Varies 99999 Alarm Message R
Value
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observation R ID 1 “F” R 1
Result Sta-
tus
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 225
Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
14 00014 Date/Time RE DTM 24 <not used> O 24
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observation RE CWE 705 <not used>
Method
18 00692 Equipment RE EI 427 <UniqueID>^<mod R 427
Instance el>^<manufac-
Identifier turer url>^<univer-
sal id type>
If serial number is
received then
unique id will be
serial number, oth-
erwise it will be the
IP/MAC address of
the device.
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observation RE CWE 705 <not used>
Site

OBX 3: Alarm Source

Seq HL7 HL7 Dräger
Item #
Descrip- Req Type Len Contents Req Len
tion
1 00001 Set ID – R SI 4 “3” R 4
OBX
2 00002 Value C ID 3 “NM” (numeric) if a R 2
Type numeric parameter is
the source, otherwise,
“ST” (string).
3 00003 Observa- R CWE 705 See Alarm Source R 20
tion Identi- Observation Identifier
fier

226 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Descrip- Req Type Len Contents Req Len
tion
4 00004 Observa- R ST 20 1.<VMD_In- R 20
tion Sub- stance>.<Chan-
ID nel_Instance>.<CF_C
ode10>.<Metric_In-
stance>.“3”
5 00005 Observa- C Varies 9999 Value of the alarm R
tion Value 9 source.
6 00006 Units C CWE 705 If the source is a R
parameter then the
unit will be displayed
as:
<UOM
CFCODE>^<UOM
MDC>^MDC
otherwise this field is
not used.
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observa- R ID 1 “F” R 1
tion Result
Status
12 00012 Effective X DTM 24 <not used>
Date of
Reference
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used> O 24
of the
Observa-
tion
15 00015 Pro- RE CWE 705 <not used>
ducer’s ID

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 227
Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Descrip- Req Type Len Contents Req Len
tion
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observa- RE CWE 705 <not used>
tion
Method
18 00692 Equip- RE EI 427 <UniqueID>^<model> R 427
ment ^<manufacturer
Instance url>^<universal id
Identifier type>
If serial number is
received then unique
id will be serial num-
ber, otherwise it will be
the IP/MAC address
of the device.
19 00693 Date/Time CE DTM 24 <not used>
of the
Analysis
20 Observa- RE CWE 705 <not used>
tion Site

Alarm Source Observation Identifier

If the alarm is a technical alarm then the field will be “68480^MDC_ATTR_ALERT_SOURCE^MDC”.

If the alarm is not a technical alarm then the field will contain the identity of the source in the following format:
<Code>^<Reference ID>^MDC
where <Code> is the 11073 code for the source parameter or MDS and <Reference ID> is the
corresponding reference ID

228 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

OBX 4: Alarm Event Phase

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – OBX R SI 4 “4” R 4
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observation R CWE 705 “68481^MDC_AT- R 20
Identifier TR_EVENT_PHASE
^MDC”
4 00004 Observation R ST 20 1.<VMD_In- R 20
Sub-ID stance>.<Chan-
nel_Instance>.<CF_
Code10>.<Metric_In-
stance>.“4”
5 00005 Observation C Varies 9999 Even Phase: “start”, R 20
Value 9 “update”, “stop”, or
“end”.
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observation R ID 1 “F” R 1
Result Status
12 00012 Effective Date X DTM 24 <not used>
of Reference
Range
13 00013 User Defined X ST 20 <not used>
Access
Checks
14 00014 Date/Time of RE DTM 24 <not used>
the Observa-
tion
15 00015 Producer’s ID RE CWE 705 <not used>
16 00016 Responsible RE XCN 3220 <not used>
Observer
17 00017 Observation RE CWE 705 <not used>
Method

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 229
Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
18 00692 Equipment RE EI 427 <UniqueID>^<model R 427
Instance >^<manufacturer
Identifier url>^<universal id
type>
If serial number is
received then unique
id will be serial num-
ber, otherwise it will
be the IP/MAC
address of the
device.
19 00693 Date/Time of CE DTM 24 <not used>
the Analysis
20 Observation RE CWE 705 <not used>
Site

OBX 5: Alarm State

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “5” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observa- R CWE 705 “68482^MDC_AT- R 20
tion Identi- TR_ALARM_STATE^M
fier DC”
4 00004 Observa- R ST 20 1.<VMD_In- R 20
tion Sub-ID stance>.<Channel_In-
stance>.<CF_Code10>
.<Metric_Instance>.“5”
5 00005 Observa- C Varies 9999 Contains “inactive”, R 20
tion Value 9 “active”, or “latched”.
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test

230 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
11 00011 Observa- R ID 1 “F” R 1
tion Result
Status
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used>
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observa- RE CWE 705 <not used>
tion Method
18 00692 Equipment RE EI 427 <UniqueID>^<model>^ R 427
Instance <manufacturer
Identifier url>^<universal id type>
If serial number is
received then unique id
will be serial number,
otherwise it will be the
IP/MAC address of the
device.
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observa- RE CWE 705 <not used>
tion Site

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 231
Alarm Communication Management Interface

OBX 6: Alarm Inactivation State

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “6” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observa- R CWE 705 “68483^MDC_AT- R 20
tion Identi- TR_ALARM_INAC-
fier TIVATION_STATE^
MDC”
4 00004 Observa- R ST 20 1.<VMD_In- R 20
tion Sub-ID stance>.<Chan-
nel_Instance>.<CF_
Code10>.<Met-
ric_Instance>.“6”
5 00005 Observa- C Varies 9999 Alarm Inactivation R 20
tion Value 9 State: "enabled"
“alarm-off” or alarm-
paused"
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observa- R ID 1 “F” R 1
tion Result
Status
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used>
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID

232 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observa- RE CWE 705 <not used>
tion Method
18 00692 Equipment RE EI 427 <UniqueID>^<model R 427
Instance >^<manufacturer
Identifier url>^<universal id
type>
If serial number is
received then unique
id will be serial num-
ber, otherwise it will
be the IP/MAC
address of the
device.
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observa- RE CWE 705 <not used>
tion Site

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 233
Alarm Communication Management Interface

OBX 7: Alarm Priority

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “7” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observa- R CWE 705 “68484^MDC_AT- R 20
tion Identi- TR_ALARM_PRIOR-
fier ITY^MDC”
4 00004 Observa- R ST 20 1.<VMD_In- R 20
tion Sub-ID stance>.<Channel_In-
stance>.<CF_Code10>
.<Metric_Instances>.“7”
5 00005 Observa- C Varies 9999 Alarm Priority: "PN", R 20
tion Value 9 "PL", “PM”, or “PH”
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observa- R ID 1 “F” R 1
tion Result
Status
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used>
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer
17 00017 Observa- RE CWE 705 <not used>
tion Method

234 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
18 00692 Equipment RE EI 427 <UniqueID>^<model>^ R 427
Instance <manufacturer
Identifier url>^<universal id type>
If serial number is
received then unique id
will be serial number,
otherwise it will be the
IP/MAC address of the
device.
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observa- RE CWE 705 <not used>
tion Site

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 235
Alarm Communication Management Interface

OBX 8: Alarm Type

Seq HL7 HL7 Dräger
Item #
Description Req Type Len Contents Req Len
1 00001 Set ID – R SI 4 “8” R 4
OBX
2 00002 Value Type C ID 3 “ST” R 2
3 00003 Observa- R CWE 705 “68485^MDC_AT- R 20
tion Identi- TR_ALERT_-
fier TYPE^MDC”
4 00004 Observa- R ST 20 1.<VMD_In- R 20
tion Sub-ID stance>.<Channel_In-
stance>.<CF_Code10>
.<Metric_Instances>.“8”
5 00005 Observa- C Varies 9999 Alarm Type: R 20
tion Value 9
“SP” - Physiological
“ST” - Technical
6 00006 Units C CWE 705 <not used>
7 00007 Reference CE ST 60 <not used>
Range
8 00008 Abnormal CE IS 5 <not used>
Flags
9 00009 Probability X NM 5 <not used>
10 00010 Nature of CE ID 2 <not used>
Abnormal
Test
11 00011 Observa- R ID 1 “F” R 1
tion Result
Status
12 00012 Effective X DTM 24 <not used>
Date of Ref-
erence
Range
13 00013 User X ST 20 <not used>
Defined
Access
Checks
14 00014 Date/Time RE DTM 24 <not used>
of the
Observation
15 00015 Producer’s RE CWE 705 <not used>
ID
16 00016 Responsi- RE XCN 3220 <not used>
ble
Observer

236 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Seq HL7 HL7 Dräger

Item #
Description Req Type Len Contents Req Len
17 00017 Observa- RE CWE 705 <not used>
tion Method
18 00692 Equipment RE EI 427 <UniqueID>^<model>^ R 427
Instance <manufacturer
Identifier url>^<universal id type>
If serial number is
received then unique id
will be serial number,
otherwise it will be the
IP/MAC address of the
device.
19 00693 Date/Time CE DTM 24 <not used>
of the Analy-
sis
20 Observa- RE CWE 705 <not used>
tion Site

ACK – Acknowledgment

After reception of an ADT message, an acknowledgment of the following form is sent:

Segment Description
MSH MSH Segment - Message Header
MSA MSA Segment - Message Acknowledgment

See ORU - Unsolicited Observation Report for a description of the ACM message being acknowledged.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 237
Alarm Communication Management Interface

MSH Segment - Message Header

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
1 00001 Field Separator R ST 1 “|” R 1
2 00002 Encoding Char- R ST 4 “^~\&” R 4
acters
3 00003 Sending Appli- O HD 180 <not used> O 16
cation
4 00004 Sending Facil- O HD 180 <not used>
ity
5 00005 Receiving O HD 180 <not used> O
Application
6 00006 Receiving O HD 180 <not used>
Facility
7 00007 Date/Time of O TS 26 YYYYMMD- O 12
Message DHHmmss-
ZZZZ
8 00008 Security O ST 40 <not used>
9 00009 Message Type R CM 7 ACK^<Event R 7
type>^ACK
10 00010 Message Con- R ST 20 A number that R 20
trol ID uniquely iden-
tifies the mes-
sage Sending
Application
11 00011 Processing ID R PT 3 “P” R 3
12 00012 Version ID R ID 8 “2.6” R 8
13 00013 Sequence O NM 15 <not used>
Number
14 00014 Continuation O ST 180 <not used>
Pointer
15 00015 Accept O ID 2 <not used> R 2
Acknowledg-
ment Type
16 00016 Application O ID 2 <not used> R 2
Acknowledg-
ment
17 00017 Country Code O ID 2 <not used>

238 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

MSH Segment - Message Header (Continued)

Seq HL7 HL7 Dräger

Item # Description Req Type Len Contents Req Len
18 00692 Character Set O ID 6 8859/1
19 00693 Principal Lan- O CE 60 <not used>
guage Of Mes-
sage

MSA Segment - Message Acknowledgment

Se HL7 HL7 Dräger

q Item # Description Req Type Len Contents Req Len
1 00018 Acknowledg- R ID 2 See Acknowl- R 2
ment Code edgment
Codes
2 00010 Message Con- R ST 20 This field con- R 20
trol ID tains the Mes-
sage Control
ID of the mes-
sage it is
acknowledg-
ing. Refer to
Message Con-
trol ID
3 00020 Text Message O ST 80 An error or sta- O 80
tus string
4 00021 Expected O NM 15 <not used>
Sequence
Number
5 00022 Delayed B ID 1 <not used>
Acknowledg-
ment Type
6 00023 Error Condition O CE 100 <not used>

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 239
Alarm Communication Management Interface

Acknowledgment Codes

Value Description
AA Original mode: Application Accept
AE Original mode: Application Error
AR Original mode: Application Reject
CA Enhanced mode: Commit Accept
CE Enhanced mode: Commit Error
CR Enhanced mode: Commit Reject

Sample Acknowledgment message

NAME=ACK
MSG:#
MSH|^~\&|NUR|DRAEGER|INFO_SRC_DRAEGER^0030E60000000001^EUI-64|Drae-
ger|20170125135441-
0500||ACK^R40^ACK|18092115514903462867|P|2.6|||AL|NE||8859/1|EN^ENGLISH^ISO639||IHE_PC-
D_ACM_001^IHE PCD^1.3.6.1.4.1.19376.1.6.4.4^ISO
MSA|CA|18092115514900035708|

240 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Alarm Communication Management Interface

Sample ORU message

NAME=ORU(3/11/2019 14:33:29)
MSG:
MSH|^~\&|INFO_SRC_DRAEGER^0030E60000000001^EUI-64|Draeger|NUR|REC-
FAC|20190311143329-
0500||ORU^R40^ORU_R40|19031114332900039875|P|2.6|||AL|NE||8859/1|en^English^ISO639||IHE_P
CD_ACM_001^IHE PCD^1.3.6.1.4.1.19376.1.6.4.4^ISO
PID|||111-11-
1111^^^Auth1^MR~1001^^^^AN||Smith^Wally^L.^^^^L|Joosse\S\K\S\Judy^^^^^^L|19420430142000|M^
Male||U^Unknown|Smith13 Beer St.^#123Wally^Beersteinville^VA^12345-6785^USA^M||||spa^Span-
ish|M^Married|JEW^Jewish||012-34-5678|||N^Not Hispanic or Latino||||||USA^United States
PV1|||CU2^^GOWDA23^BGS1||||^Munster^Florence^S^II^Mr.^M.D.|^Kaite^William^M^Mr^II^MD|^Kuma
r^Sri^L^Mr^III^MBBS||||||||^Carr^Mary^Jones^II^Mrs.^M.D.
OBR|1||1^356fdbd9-b939-47c7-acf2-151bc323819819667220190311143329^0030E60000000001^EUI-
64|196616^MDC_EVT_ALARM^MDC|||20190311143329-0500
OBX|1|ST|69837^MDC_DEV_METER_PHYSIO_MUL-
TI_PARAM_MDS^MDC|1.0.0.0|||||||F|||||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|2|ST|196672^MDC_EVT_LO_LT_LIM^MDC|1.1.2.147842.1.2|HR < low
limit||||||F|||||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|3|NM|147842^MDC_ECG_CARD_BEAT_RATE^MDC|1.1.2.147842.1.3|89.000000|264864^MDC_
DIM_BEAT_PER_MIN^MDC|||||F|||||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|4|ST|68481^MDC_AT-
TR_EVENT_PHASE^MDC|1.1.2.147842.1.4|start||||||F|||||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|5|ST|68482^MDC_AT-
TR_ALARM_STATE^MDC|1.1.2.147842.1.5|active||||||F|||||||0060E9EEBC^IACS^http://www.drae-
ger.com/^DNS
OBX|6|ST|68483^MDC_ATTR_ALARM_INACTIVATION_STATE^MDC|1.1.2.147842.1.6|enabled||||||F||||
|||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|7|ST|68484^MDC_ATTR_ALARM_PRIOR-
ITY^MDC|1.1.2.147842.1.7|PM||||||F|||||||0060E9EEBC^IACS^http://www.draeger.com/^DNS
OBX|8|ST|68485^MDC_ATTR_ALERT_-
TYPE^MDC|1.1.2.147842.1.8|SP||||||F|||||||0060E9EEBC^IACS^http://www.draeger.com/^DNS

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 241
 This page has been left blank intentionally.

242 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

ASTM Stat Lab Interface Option

The ASTM Stat Lab interface allows the HL7 server to accept laboratory data using a serial
communication link from a “stat” laboratory device and transmit the data to Infinity Modular monitors.
If the Lab Interface option is enabled then upon receipt of the ASTM message, it will then attempt to find
a patient monitor on the network with the corresponding ID. If one, and only one such patient monitor is
found, and the monitor is a Modular monitor, then the data is forwarded to the patient monitor. On the
modular monitor, laboratory data is displayed in the Blood Chemistry screen, and may be imported into
the Calculator. Please refer to the instructions for use of the appropriate Infinity patient monitor for more
details.
In the HL7/ASTM setup program, the user configures the stat labs that data is to be accepted from. On
each of these device configurations, the “LAB ID” setting controls which field the identifier is extracted from
in the message. Refer to the ASTM (Practice Assigned Patient ID/Laboratory Assigned Patient ID) section
for more details.
The identifier extracted from the ASTM message is interpreted as being either an MRN or a Patient
Account number according to the global uses setting defined in the HL7 setup program.
The ASTM Stat Lab Interface Option conforms to the ASTM 1381-91 and ASTM 1394-91 protocols with
the following exceptions:
 Hexadecimal data escape sequences are not supported
 Local (manufacturer defined) escape sequences are not supported
 Start and end highlighting escape sequences will be ignored

NOTE
- Refer to Message Structure for details on the individual records used by the Infinity devices.
- Lab data cannot be transmitted to SDC-only devices.

Organizing the data

HL7/ASTM provides a mechanism by which the customer can organize incoming lab data and control how
the data is represented on the destination device (i.e. or patient monitor). The user can:
 Define any number of parameter groups and the associated group label to be used when displaying
them.
 Define each parameter that can be expected to be received from the central laboratory, assign a group
to each parameter and a priority within the group for the parameter.
This setup information is stored in the Parameter Grouping/Priority database. When a message by HL7,
the data is reorganized according to this configuration. Groups with lower numbered priorities appear
nearest to the top of the message. Parameters are placed into the group to which they have been

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 243
ASTM Stat Lab Interface Option

assigned, with lower numbered priorities appearing first. Grouping labels are also embedded before the
data is forwarded to the destination device. If a defined group has no associated parameters in the
message, then the group label is not included in the message.
If none of the parameters received are defined as part of a group then no reorganization occurs. If,
however, at least one parameter is defined as part of a group, the message is reformatted with grouping
information. Note that any parameter received that is not defined as being a member of a group will
automatically be assigned to the group “Other”, which has the highest numbered priority and therefore
goes at the bottom of the message.
See Sender Name or ID and Universal Test ID sections for more details on configuring databases for a
particular ASTM device.
Please refer to the on-line help for the HL7 setup program for more details on how to perform the
configuration.

Lab data on the patient monitor

Notification message

When lab data is received on a patient monitor, a message is displayed in the message area indicating
that new lab data has been received. Once the newly received lab data has been reviewed, this message
is cleared from the message area.

Lab data display

The patient monitor lab data review screen is of the following format:
<Time Label> <Date and time>

<Group Label >

<param> <value> <units>
<param> <value> <units>

<Group Label >

<param> <value> <units>
<param> <value> <units>
The group labels and order of appearance of parameters on the screen is defined by the HL7 Parameter
Grouping/Priority setup.
The date and time that is displayed on the screen is the date and time associated with the first result record
that appears in the reorganized message, if field 12 is populated. In this case the Time Label used is “Test
Time” (or a translation if English is not being used).
If no date/time appears in field 12 of the first result record, then the time displayed will be the time that the
message arrived at the patient monitor, and the Time Label will be “Arrival Time” (or a translation).

244 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

Hemo/Oxy/Vent Calculator

Under certain conditions, the patient monitor will also allow the user to import parameter data received into
the Hemo/Oxy/Vent Calculator, if this option is enabled at the monitor. In order to import the data, the
HL7/ASTM server also needs additional configuration information that maps the parameter labels to be
received from the central laboratory into known parameters at the patient monitor. This calculator mapping
is also performed in the HL7 setup application.
Parameters that can be imported into the calculator are:
 SaO2
 PAO2
 PACO2
 HgB
 pH
 HCO3
 HCT
 SVO2
 PVO2

NOTE
The patient monitor also requires that the parameter be a recent measurement. Please refer to the
instructions for use for the specific patient monitor for more details.

Parameter time stamp

Unlike the patient monitor, maintains a time stamp for each individual result received. The time stamp for
an individual parameter may be extracted from the following 3 fields in the following priority order:
 Field 12 of the result (‘R’) record relating to the parameter
 Field 8 of the order (“O”) record preceding the parameter
 Field 14 of the header (“H”) record

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 245
ASTM Stat Lab Interface Option

Message Structure

The message accepted from the external system must conform to ASTM 1381-91 for the data link layer.
Each record must be transmitted in one or more frames and the record must be terminated with a <CR>.
If more than one record is contained in a frame, then a record cannot end on the frame boundary.
Continuation frames are only allowed after full-length frames.
In the ASTM interface, there is no acknowledgment message, but rather each frame transmitted is
acknowledged.
The following structure shows the contents of the message after all records have been extracted from the
frame(s) in which they were transmitted. Sections of the message that appear within {and} brackets may
be repeated. Records shown within [and] brackets are optional. Additional unused records may appear in
the message, but are ignored.

Record Description
H Message Header
Record
{
P Patient Information
Record
[C] Comment Record
[O] Order Record
{
R Result Record
}
}
L Terminator Record

Message Header Record

Seq ASTM Dräger
Description Contents Req Repeat
1 Record Type ID “H” R N
2 Delimiter Definition Four characters in the following order: R N
field delimiter, usually “|”
repeat delimiter, usually ‘\’
component delimiter, usually ‘^’
escape character, usually ‘&’
Unlike other fields, no field delimiter
precedes this field.

246 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

Seq ASTM Dräger

Description Contents Req Repeat
3 Message Control ID <not used>
4 Access Password <not used>
5 Sender Name or ID See Sender Name or ID O N
6 Sender Street <not used>
Address
7 Message Control ID <not used>
8 Reserved Field <not used>
9 Sender Telephone <not used>
Number
10 Characteristics of <not used>
Sender
11 Receiver ID <not used>
12 Comment or Special <not used>
Instructions
13 Processing ID If this field is not blank and contains a value R N
other than ‘P’, the data is not production level
and therefore will not be forwarded to the
patient monitor.
14 Version No. <not used>
15 Date and Time of See Date/Time of Message O N
Message

Sender Name or ID
This field contains the name of the device sending the laboratory data. The first word of this field is used
by the HL7 Server, as a Device Identifier, for database table lookups, which determine how to:
 map parameters which are to be imported into the calculator (Calculator Mapping Database Table)
 group and order parameters on the Blood Chemistry screen of the Infinity monitor (Parameter
Grouping/Priority Database Table)
If this field is not populated, or if no corresponding entry appears in the database tables mentioned above,
then no parameters will be imported into the calculator, and the parameters will appear on the patient
monitor in the order they appear in the message.

Date/Time of Message
This field contains the data and time the message was sent, in the format: YYYYMMDDhhmmss
This field may also contain a time zone indicator, not used by the HL7/ASTM server. Refer to Lab data
display and Parameter time stamp sections for more details on how the time stamps are used on the
destination device.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 247
ASTM Stat Lab Interface Option

Patient Information Record

Seq ASTM Dräger

Description Contents Req Repeat
1 Record Type “P” R N
2 Sequence Number A sequential number indicating the R N
number of the patient within the message.
The first Patient Information Record has a
sequence number of 1; the second has a
sequence number of 2, and so on.
3 Practice Assigned See Practice Assigned Patient R N
Patient ID ID/Laboratory Assigned Patient ID
4 Laboratory Assigned See Practice Assigned Patient R N
Patient ID ID/Laboratory Assigned Patient ID
5 Patient ID No. 3 <not used>
6 Patient Name <not used>
7 Mother’s Maiden <not used>
Name
8 Birthdate <not used>
9 Patient Sex <not used>
10 Patient Race – <not used>
Ethnic Origin
11 Patient Address <not used>
12 Reserved Field <not used>
13 Patient Telephone <not used>
Number
14 Attending Physician <not used>
ID
15 Special Field 1 <not used>
16 Special Field 2 <not used>
17 Patient Height <not used>
18 Patient Weight <not used>
19 Patient’s Known or <not used>
Suspected
Diagnosis
20 Patient Active <not used>
Medications
21 Patient’s Diet <not used>
22 Practice Field No. 1 <not used>

248 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

Seq ASTM Dräger

Description Contents Req Repeat
23 Practice Field No. 2 <not used>
24 Admission and <not used>
Discharge Dates
25 Admission Status <not used>
26 Location <not used>
27 Nature of Alternative <not used>
Diagnosis
28 Alternative <not used>
Diagnostic Code
29 Patient Religion <not used>
30 Marital Status <not used>
31 Isolation Status <not used>
32 Language <not used>
33 Hospital Service <not used>
34 Hospital Institution <not used>
35 Dosage Category <not used>

Practice Assigned Patient ID/Laboratory Assigned Patient ID

The HL7/ASTM server is configured to accept the Patient ID from either the Practice Assigned Patient ID
or the Laboratory Assigned Patient ID via the “Lab ID” setting in the HL7 Setup program. The HL7/ASTM
server default is configured to accept the Patient ID from the Practice Assigned Patient ID field.
All laboratory data is routed to an Infinity monitor that has a corresponding ID entered as the Patient ID in
the Admit screen of the Infinity monitor. If multiple patient monitors with the same Patient ID exist on the
Infinity Network, the laboratory data is rejected.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 249
ASTM Stat Lab Interface Option

Order Record

Seq ASTM Dräger

Description Contents Req Repeat
1 Record Type “O” R N
2 Sequence Number A sequential number indicating the R N
number of the order for this patient
in the message. The first Order
Record for the patient has a
sequence number of 1, the second
has a sequence number of 2, and
so on.
3 Specimen ID <not used>
4 Instrument Specimen ID <not used>
5 Universal Test ID <not used>
6 Priority <not used>
7 Requested/Ordered Date <not used>
and Time
8 Specimen Collection Date See Date/Time of Message O N
and Time
9 Collection End Time <not used>
10 Collection Volume <not used>
11 Collector ID <not used>
12 Action Code <not used>
13 Danger Code <not used>
14 Relevant Clinical <not used>
Information
15 Date/Time Specimen <not used>
Received
16 Specimen Descriptor <not used>
17 Ordering Physician <not used>
18 Physician 's Telephone <not used>
Number
19 Users Field No. 1 <not used>
20 Users Field No. 2 <not used>
21 Laboratory Field No. 1 <not used>
22 Laboratory Field No. 2 <not used>
23 Date/Time Results <not used>
Reported or Last Modified

250 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

Seq ASTM Dräger

Description Contents Req Repeat
24 Instrument Charge to <not used>
Computer System
25 Instrument Section ID <not used>
26 Report Types <not used>
27 Reserved Field <not used>
28 Location or Ward of <not used>
Specimen Collection
29 Nosocomial Injection Flag <not used>
30 Specimen Service <not used>
31 Specimen Institution <not used>

Date/Time of Message
This field contains the data and time the group of parameters to follow were collected, in the format:
YYYYMMDDhhmmss
This field may also contain a time zone indicator, not used by the HL7/ASTM server. Refer to Lab data
display and Parameter time stamp sections for more details on how the time stamps are used on the
destination device.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 251
ASTM Stat Lab Interface Option

Result Record

Seq ASTM Dräger

Description Contents Req Repeat
1 Record Type “R” R N
2 Sequence Number The sequential number of the result R N
within this order, this patient and this
message. The first Result Record for the
order has a sequence number of 1, the
second has a sequence number of 2, and
so on.
3 Universal Test ID See Universal Test ID O N
4 Data or The value of the results of the test. O N
Measurement Value
5 Units The units of the result. O N
6 Reference Ranges See Reference Range O N
7 Result Abnormal See Abnormal Flag O Y
Flags
8 Nature of The nature of the Abnormality O Y
Abnormality Testing
9 Result Status <not used>
10 Date of Change in <not used>
Instrument
Normative Values or
Units
11 Operator <not used>
Identification
12 Date/Time Test See Date/Time of Message O N
Started
13 Date/Time Test <not used>
Completed
14 Instrument <not used>
identification

Universal Test ID
This field uniquely identifies the laboratory test being reported, according to the ASTM protocol. The
format is:
<universal identifier >^< test name>^< test ID type >^< local code>^...
universal identifier: currently unused component
test name: test or battery name

252 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

test ID type: indicates coding scheme used in first two components

local code: code defined by the manufacturer
The standard also allows for extensions or qualifiers to the local code in subsequent component fields
must be defined and documented by the manufacturer. The HL7/ASTM server needs to extract from this
field a Parameter Label. Because different external devices use this field differently, the Parameter Label
is extracted from Component 4, if it exists; otherwise it is extracted from Component 1 of this field.

Reference Range

Contains the parameter value to be displayed on in the Labs Review tab. The reference ranges of the
following formats are accepted:
1 lower limit – upper limit
2 >lower limit
3 <upper limit

Abnormal Flag

This field indicates the normalcy status of the result, and is used by Innovian only. The field can be
repeated to combine the following Abnormal values. Only flags that appear in the following table are
flagged within Innovian as abnormal. Innovian’s flag turns the beaker on the lab message red and
parameter value red.

Value Description
L Below low normal
H Above high normal
LL Below lower panic limits
HH Above upper panic limits
< Below absolute low-off instrument scale
> Above absolute high-off instrument
scale
A Abnormal
AA Very abnormal

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 253
ASTM Stat Lab Interface Option

Comment Record

Seq ASTM Dräger

Description Contents Req Repeat
1 Record Type “C” R N
2 Sequence Number A sequential number indicating the R N
number of the comment at the same
“level”.
The first comment record at a particular
hierarchical; level has a sequence
number of 1; the second has a sequence
number of 2, and so on.
3 Universal Test ID <not used> O N
4 Data or The text to be displayed in a Lab notes O N
Measurement Value
5 Units <not used> O N

Date/Time of Message
This field contains the data and time the test was started, in the format: YYYYMMDDhhmmss
This field may also contain a time zone indicator, not used by the HL7/ASTM server. Refer to Lab data
display and Parameter time stamp sections for more details on how the time stamps are used on the
destination device.

254 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 ASTM Stat Lab Interface Option

Terminator Record

Seq ASTM Dräger

Description Contents Req Repeat
1 Record Type “L” R
2 Sequence Number 1 R
3 Termination Code <not used>

Sample ASTM Message

The following sample does not include the control characters and checksum required to transmit this
ASTM message, but does include the frame number. See ASTM 1381-91 for more details.

0H|\^&|||AVL OMNI Ser.# :1693||||||QC|P|2.2|19990126140833

1P|1|999-99-9999|
2O|1||QC^8109|||||20000808000000|||||||COMBI-TROL^1
3C|1|I||G
4R|1|^^^pH^M^^|7.392||0.000 to 9.000|N||F||||19990126140700
5R|2|^^^PCO2^M^^|46.4|mmHg| 0.0 to 99.0|N||F
6R|3|^^^PO2^M^^|---|mmHg| 0.0 to 200.0|A||F
7R|4|^^^Na^M^^|141.9|mmol/l| 0.0 to 200.0|N||F
0C|1||Diet should be changed
1R|5|^^^K^M^^|4.89|mmol/l|0.00 to 10.00|N||F
2R|6|^^^Cl^M^^|99.4|mmol/l| 0.0 to 200.0|N||F
3R|7|^^^iCa^M^^|---|mmol/l|0.000 to 9.000|A||F
4R|8|^^^Hct^M^^|1.0|%|0.0 to 99.0|N||F
5R|9|^^^ctHb^M^^|13.4|g/dl|0.0 to 99.0|N||F
6R|10|^^^O2Hb^M^^|-13.9|%| 0.0 to 100.0|A||F
7R|11|^^^COHb^M^^|104.4|%| 0.0 to 100.0|A||F
0R|12|^^^MetHb^M^^|-9.3|%| 0.0 to 100.0|A||F
1R|13|^^^HHb^M^^|18.6|%| 0.0 to 100.0|N||F
2R|14|^^^SulfHb^M^^| 0.2|%| 0.0 to 100.0|N||F
3R|15|^^^Glu^M^^|110.7|mg/dl| 0.0 to 1801.8|N||F
4R|16|^^^Lac^M^^|---|mmol/l|0.00 to 9.99|A||F
5L|1|N

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 255
 This page has been left blank intentionally.

256 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

PatientWatch

An Infinity PatientWatch server can be run on Windows Server 2016 or 2019.

All client connections to PatientWatch must run in Internet Explorer 11 or Microsoft Edge in IE Mode.

NOTE
PatientWatch can be used to view both SDC and Infinity devices, however, certain functionality, such as
trends, is only available on Infinity devices.

WinViewActiveX Control

The WinViewActiveX control is an ActiveX component of the Infinity PatientWatch application.

PatientWatch includes HTML files, ASP files, DLLs, cabinet files, Component Services file, and this
ActiveX control. PatientWatch can be deployed with its standard functions and features, or it can be
customized to support a unique interface or need. Developers can choose, for example, to create custom
HTML pages for PatientWatch. You can also limit user access by patient in PatientWatch using the ActiveX
control. This section specifies the methods inherent in the ActiveX control.

Methods

NOTE
Not all error codes are used by all methods.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 257
PatientWatch

AddServers()

Purpose: This method adds a list of Gateway servers to the Network Setup list of
servers.
Arguments: ServerList - The names or IP addresses of the gateway server(s) to add,
separated by “&”
Return Value: 0: SUCCESS
1: FAIL – Unknown cause
2: FAIL – Gateway Server not found
9: FAIL – Error finding server because list is empty
Description: This method adds a Gateway Server to the Network Setup list of servers on
the client machine. If the gateway server is already present, it will not be added
again. If any server in the list provided is not valid, an error will occur, but will
not prevent the valid ones from being added. Otherwise a SUCCESS code will
be returned.

258 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

SelectGSMBedMCAddr()

Purpose: This method allows the Global Session Manager (GSM) user to connect to an
Infinity monitor specified by the Multicast address of the patient admitted to
that bed. This method cannot be used to connect to an SDC-only device.
Arguments: GWServer – The name of the gateway server to log on to
GSMSessionID – The session identification for GSM
GSMServer – The GSM server name
UserName – The user name to be used to log on to the server
BedMCAddr – The multi-cast address that identifies the bed
Return Value: 0: SUCCESS – The user is logged in to the server with a valid GSM session,
and the Infinity monitor specified has been connected.
2: FAIL – Gateway Server not found
3: FAIL – Error logging in to the server
4: FAIL – Error obtaining directory
8: FAIL – Error connecting to bed
11: FAIL – GSM Server not found
12: FAIL – GSM session is invalid
13: FAIL – Error found an empty Address String
Description: This method will allow the user to view a bed at a specified multicast address.
The current bed, if any, will be disconnected. The software will attempt to log
on to the gateway server specified. If log on to the server is not successful, an
error code will be returned. The software will then attempt to locate an Infinity
monitor whose multicast address corresponds to that supplied by the user. If
no Infinity monitor contains the specified multicast address, an error code will
be returned. If the GSM session has expired or is invalid, an error code will be
returned.Otherwise a SUCCESS code will be returned.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 259
PatientWatch

SelectGSMPatient()

Purpose: This method allows the Global Session Manager user to select a device from
a list of available devices using a Patient identifier. This method will work with
both Infinity and SDC devices.
Arguments: GWServer – The name of the gateway server to log on to
GSMSessionID – The GSM session identification string
GSMServer – The name of the GSM servers to connect to verify a valid GSM
session
UserName – The user name to be used to log on to the server
PatientId – The identifier for the patient at the patient monitor
Return Value: 0: SUCCESS
1: FAILURE – unknown cause
2: FAILURE – Server not found
3: FAILURE – Invalid log on
4: FAILURE – Failed to get directory
6: FAILURE – Patient not found in active directory
7: FAILURE – Duplicate patients found
8: FAILURE – Failed to connect to bed
9: FAILURE – Empty Server String
10: FAILURE – Duplicate bed found. Has same patient ID
11: FAILURE – Invalid GSM Server
12: FAILURE – Invalid GSM session or session has timed out
13: FAILURE – Empty address string. Cannot find a valid IP address for Server
Condition None
Description: The current bed, if any, will be disconnected. The software will attempt to log
on to the server specified. If log on to the server is not successful, an error
code will be returned. The software will then attempt to locate an device whose
patient ID corresponds to that supplied by the user. If no device contains the
specified, or more than one device contains it, an error code will be returned.
If the GSM session has expired or is invalid, an error code will be
returned.Otherwise a SUCCESS code will be returned.

260 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

SelectPatient()

Purpose: This method allows the user to select a device from a list of available Care Units.
This method can be used to select both Infinity and SDC devices.
Arguments: None
Return Value: 0: SUCCESS
1: FAILURE
Condition: None
Description: This method will display a disclaimer on the first invocation within a newly
instantiated ActiveX control. If the user has not yet logged on a server, a log on
dialog will be displayed. The patient selection dialog will then appear.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 261
PatientWatch

SelectServerandBed()

Purpose: This method allows the user to programmatically log on to a server and
connect to a device specified by its Care Unit label and Bed label. If more than
one bed exists with the same labels (as can happen with seamless viewing
wireless beds), the non-wireless bed is selected. This method cannot be used
to connect to an SDC-only device.
Arguments: ServerName – The name or IP address of the server to log on to
UserName – The user name to be used to log on to the server
Password – The password to be used to log on to the server
Domain – The domain name of the user to be used to log on to the server
CareUnit label – The care unit label of the device to be connected
Bed label – The bed label of the patient monitor
Return Value: 0: SUCCESS – The user is logged on to the server, and the Infinity patient
monitor specified has been connected.
2: FAIL – Server not found
3: FAIL – Error logging in to the server
4: FAIL – Error obtaining directory
5: FAIL –Patient monitor specified does not exist on the server
8: FAIL – Error connecting to bed
10: FAIL – Duplicate bed
Description: This method will display a disclaimer, on the first invocation within a newly
instantiated ActiveX control. The software will attempt to log on to the server
specified. If log on is not successful, an error code will be returned. The current
bed, if any, will be disconnected. The software will then attempt to connect to
the specified Infinity monitor on that server. If connection to the Infinity
monitor cannot be made, an error code will be returned. Otherwise a
SUCCESS code will be returned.

262 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

SelectServerandBedMCAddress()

Purpose: This method allows the user to programmatically log on to a server and
connect to an Infinity monitor specified by the multicast IP address of the
patient monitor. Note that this method does not work with SDC-only devices.
Arguments: ServerName – The name of the server to log on to the server
UserName – The user name to be used to log on to the server
Password –The password to be used to log on to the server
Domain – The domain name to be used to log on to the server
MCAddress – A string containing the multicast IP address of the patient
monitor
Return Value: 0: SUCCESS – The user is logged on to the server, and the Infinity monitor
specified has been connected.
2: FAIL – Server not found
3: FAIL – Error logging in to the server
4: FAIL – Error obtaining directory
5: FAIL – Patient monitor specified does not exist on the server
8: FAIL – Error connecting to bed
Description: This method will display a disclaimer, on the first invocation within a newly
instantiated ActiveX control. The software will attempt to log on to the server
specified. If log on is not successful, an error code will be returned. The current
bed, if any, will be disconnected. The software will then attempt to locate an
Infinity monitor whose patient ID corresponds to that supplied by the user. If
no Infinity monitor contains the specified, or more than one monitor contains
it, an error code will be returned. Otherwise a SUCCESS code will be returned.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 263
PatientWatch

SelectServerandPatientID()

Purpose: This method allows the user to programmatically log on to a server and connect
to an device specified by the of the patient admitted to that bed. This method
cannot be used to connect to an SDC-only device.
Arguments: ServerName –The name of the server to log on to
UserName –The user name to be used to log on to the server
Password – The password to be used to log on to the server
Domain –- The domain name to be used to log on to the server
PatientID – The identifier for the patient at the patient monitor
Return Value: 0: SUCCESS – The user is logged on to the server, and the device specified has
been connected.
2: FAIL – Server not found
3: FAIL – Error logging in to the server
4: FAIL – Error obtaining directory
6: FAIL – Specified does not exist on the server
7: FAIL – More than one patient monitor contains the same
8: FAIL – Error connecting to bed
Description: This method will display a disclaimer, on the first invocation within a newly
instantiated ActiveX control. The software will attempt to log on to the server
specified. If log on is not successful, an error code will be returned. The current
bed, if any, will be disconnected. The software will then attempt to locate whose
patient ID corresponds to that supplied by the user. If no device contains the
specified identifier, or more than one monitor contains it, an error code will be
returned. Otherwise a SUCCESS code will be returned.

264 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

Properties

The WinViewActivex control has the following properties:

DisableAsyncBoxes (BOOL)

When this property is set to TRUE, any message dialogs that would normally pop up asynchronously are
disabled. For example, if the patient monitor that is currently being viewed disappears from the network,
a popup would normally appear; with this option enabled, the popup dialog will no longer be displayed.

SinglePatientMode (BOOL)

When this property is set to TRUE and the web page subsequently invokes one of the methods that
automatically selects a patient, then the control goes into single patient mode. In this mode, the “Select
Patient” and the “Log Off” buttons are disabled.
Note, however, that if the SelectPatient method of the ActiveXcontrol is called, this setting is temporarily
overridden until one of the other patient selection methods are called.

SingleSignonMultiPatientMode

When this property is set to TRUE and the web page subsequently invokes one of the methods that
automatically selects a patient, then the control goes into single sign-on, multi-patient mode. In this mode,
the “Select Patient” button is disabled ONLY WHEN the user is not logged in, thereby forcing the user to
log on through the parent website.

Events

The Infinity PatientWatch ActiveX control will trigger the following events listed below.

Error Event

This event is triggered whenever a serious unrecoverable error is encountered within the ActiveX Control.

Select Event

This event is triggered whenever the mouse is clicked on the ActiveX control. No click event will be
triggered when a mouse click occurs within a dialog box.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 265
PatientWatch

Activity Event

This event is triggered whenever any mouse click or other activity occurs and is available so that the web
page containing the control can reset any active timeouts.

Change Patient Event

This event is triggered when the ActiveX control is in Multi-patient mode and the user selects a different
patient to view. The event contains the patient ID of the newly selected patient.

Logoff Event

This event is triggered when the user presses the Logoff button. The next time the user attempts to select
a patient, he/she will be prompted for user name and password.

Abort Event

This event is triggered more than 4 copies of the WinViewActiveX control are placed on a page or a
shortcut to a page containing one control is invoked more than 4 times. In the standard WebViewer.asp
page, this event triggers a redirection to a page reporting an error.

Map2Server Control

Map2Server is a server side asp object. This patient–to-server mapping mechanism allows custom web
applications to determine whether a patient, identified by Patient ID or Patient name, is available for
viewing through PatientWatch, and if so, the name of the Infinity Gateway Server through which the view
can be accessed.
It also can provide a global list of patients available on the network, across multiple Infinity Gateway
Servers for a specific user. Finally, it can authenticate a user name, password and domain on one server.

266 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

Methods

GetErrorNum()

Purpose: This method returns the error number as a result of any other method calls.
Arguments: None
Return Value: 20: SUCCESS
21: FAILURE
22: FAILURE – Duplicate Patient Identification Number is on the network
23: FAILURE – Invalid user name or password
24: FAILURE – No Gateway servers are available
25: FAILURE – No Gateway servers are configured from the Configure
Servers
26: FAILURE – Invalid Patient ID
27: FAILURE – Patient ID not found on the network
28: FAILURE – Server List is not properly configured
29: FAILURE – Server List contains invalid or unavailable Gateway IP address
Description: This method will return a value which in return can be used to get the Error
String. The value returned can be determined by calling GetErrorString().

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 267
PatientWatch

GetErrorString()

Purpose: This method returns the message of a particular error code.

Arguments: None
Return Value: String describing the last error, if any.
Description: This method returns the latest error, in string format.

GetPatientList()

Purpose: This method returns all the available patient monitors in all of the properly
configured Gateways. The logon method must be called first and return
SUCCESS.
Arguments: None
Return Value: 20: SUCCESS
21: FAILURE – User had not logged on
Description: This method will display in a pick list, all the active patient monitors. Only the
Gateway’s that are configured on the ServerList (Config. Servers) will be
searched. Also, only the patient monitors that the user has permissions for will
be returned.

GetServerForBedMCAddr()

Purpose: This method returns the specific Gateway server that a select patient monitor
with specified multicast address is connected to.
Arguments: Multicast address
Return Value: 20: SUCCESS
21: FAILURE – User has not logged on
22: FAILURE – Duplicate multicast address
24: FAILURE – No servers available for selected multicast address
26: FAILURE – Invalid multicast address
Description: This method is used to connect to a Gateway server that monitors a specific
patient monitor’s multicast address.

268 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

GetServerForPatient()

Purpose: This method receives and returns the Gateway Server in which this is found.
If this patient is being monitored by more than one Gateway then the first
Gateway on the list is selected.
Arguments:
Return Value: 20: SUCCESS
21: FAILURE – User had not logged on to a Gateway server
22: FAILURE – Duplicate on the network
24: FAILURE – No Servers Available for selected Patient Id
26: FAILURE – Invalid Patient Id
27: FAILURE – Patient Id not found on any servers
Description: This method will return the first available Gateway server that has user
permissions to view a patient monitor with the selected. If the is not found or if
other errors occur this method will fail.

GSMLogon()

Purpose: This method logons on a user with the requirement of a valid GSM(Global
Session Manager) Session string and a valid GSM Server.
Arguments: GSMSession, GSMServer, Username
Return Value: 20: SUCCESS
23: FAILURE – Invalid Logon
24: FAILURE – No Servers Available to that user
25: FAILURE – No Servers have been configured
Description: This method will logon a user using a valid GSM Session and GSM Server. If
either are invalid and error will occur.

Logon()

Purpose: This method will logon a user to the first available Gateway Server on the list.
The logon will occur if the user is on the domain or a local user on the current
Gateway Server.
Arguments: Username, Password, Domain
Return Value: 20: SUCCESS
23: FAILURE – Invalid Logon
24: FAILURE – No Servers Available to that user
25: FAILURE – No Servers have been configured
Description: This method will logon a user using a valid GSM Session and GSM Server, if
either are invalid and error will occur.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 269
PatientWatch

SetServers()

Purpose: This method will add all servers in the list to map2server.
Arguments: Servers
Return Value: 20: SUCCESS
25: FAILURE – No servers have been configured
28: FAILURE – Invalid server list format
29: FAILURE – Invalid Server IP Address
Description: This method will display a disclaimer on the first invocation within a newly
instantiated ActiveX control. If the user has not yet logged on a server, a log
on dialog will be displayed. The patient selection dialog will then appear.

ValidateUser()

Purpose: This method verifies that a user attempting to logon to a Gateway Server is
using a valid user name and password. Also, that the user has valid
permissions.
Arguments: User, Password, Server
Return Value: 0: SUCCESS
1: FAILURE – Invalid user name or password
24: FAILURE – Selected Server is not available
Description: This method verifies that all arguments are valid then validates the user name
and password with the given Gateway server. If any of the arguments are
invalid or if the user doesnot have permissions a failure is returned.

PatientWatch File Structure

If a default page was chosen upon installation of PatientWatch then either an Index.htm or default.htm file
is created in the top level folder for the Web server. This installed HTML file redirects to the Infinity
Gateway version of PatientWatch.
The PatientWatch file structure contains one main folder, Webviewer. This folder contains:
 All the required asp (Active Server Page) include files.
 Serverlist.inc, configurable from the Configure PatientWatch Servers (Start->Programs menu) and
upon install. This serverlist.inc file contains a list all available Infinity Gateway Servers.
 A sample Sample Parent Page that invoke PatientWatch in different ways.
 Two folders, Gateway and Explorer, each containing:
 Frameset.asp, the page that should be invoked from any external application. When one patient is to
be displayed on the page.

270 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

 Frameset4.asp, the page that should be invoked from any external application. When four patients are
to be displayed on the page only in Explorer folder.
 Webviewer.asp, this main PatientWatch page displays the WinViewActiveX WinViewActiveX Control
and the buttons and tabs.

NOTE
The Gateway folder contains a version of PatientWatch that can be resized dynamically. The Explorer
folder contains a version that cannot and also supports a 2x2 view.

GSM (Global Session Manager) Support

Siemens Global Session Manager is supported but must be obtained from Siemens and installed
separately. This program allows users to move between multiple applications without having to logon to
each one it can also provide a patient context between the applications.
PatientWatch can run with or without GSM. With GSM, PatientWatch is running as a child of a parent page,
either Infinity Explorer or another parent such as NetAccess, Dashboard The parent page sets and
controls the timeout time of the child (PatientWatch) page.
If the GSM timeout expires, a redirection to a logon page provided by the parent will occur. However, if a
session cannot be validated, PatientWatch will be redirected to a log-off page.
GSM timer is reset upon any activity on the PatientWatch. Activity is deemed as pressing any tab or button
on the PatientWatch web page (i.e. not pressing a button within a dialog).

Sample Parent Page

Included in the PatientWatch installation is a sample page that uses our proprietary parent-child
mechanism; this parent-child mechanism is the same one used by our Symphony product and does not
employ GSM. The sample page, TestDSMParentBase.htm, can be used to drive PatientWatch and is
provided so that our customers can model this mechanism on their own custom pages.
Before the page can be used, however, there are some dotnet trust configurations that are required. This
can be accomplished by running the cfgTestDSM.bat batch file included in
C:\inetpub\wwwroot\webviewer. It requires as an argument the name of the web server PC that is hosting
the TestDSMParentBase web page.
Once you start TestDSMParentBase.htm, the first thing that will appear is a logon page where you are
required to enter your user name, password, and domain. Note that the domain field is not required; if left
blank, the server-side control, Map2Server Control, will search for the first domain (starting with the local
server domain) for which the user name is valid. It will then validate the user name and password within
that domain.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 271
PatientWatch

Once the user name, password, and domain are validated successfully, a list of available patients for the
user is retrieved using another method in the Map2Server Control and presented to the user. Note that
only patients that have patient IDs entered will appear in the list.
This page has the following controls:

Control Control Type Description

Patient ID: pick list A list of patients that are available to the user
that is logged in. The list is compiled from all
the servers that are currently configured.
Note that if a particular patient monitor does
not have a patient ID entered, it will not be
represented in the list.
Single Patient toggle true/false When set to true, PatientWatch is invoked in
Mode single patient mode; when set to false,
PatientWatch is invoked in
SingleSignonMultiPatient mode.
URL field Contains the URL to the PatientWatch being
invoked. By default contains the URL on the
same server as the sample page, but can be
modified to point to another server.
Launch Embedded button When pressed, the page invokes
Child PatientWatch in the selected mode and with
the selected patient ID. The PatientWatch
control is placed in the existing page.
Launch Child in button When pressed, the page invokes
New Window PatientWatch in the selected mode and with
the selected patient ID. The PatientWatch
control is placed in a new window.

NOTE
In addition to the web page TestDSMParentBase.htm, this page requires the following support files:
– DraegerEncryption.dll to encode/decode URL parameters
– FetchPatientList.asp – retrieves the patient list from the server-side object Map2Server
– DSMParentBase.js – javascripts that are needed by the page to interface with DraegerEncryption.dll

NOTE
This sample page is provided to assist the customer in modeling their own implementation of invoking the
PatientWatch application from their hospital website. There are many ways to invoke the control and the
customer may choose to implement differently, however, the customer is responsible for the testing of any
custom web pages.

272 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

URL arguments

PatientWatch can accept a variety of variables on the URL. When using these arguments, it is best to
encrypt them as they include sensitive information such as the identifier of the patient whose information
is to be viewed.
NOTE
This section does NOT address the mechanism that must be used in order to provide encrypted
arguments. Please refer to the source and description of the Sample Parent Page for more details.

In the PatientWatch URL, all the variables are in the form of 'variable=value' and each variable is
separated by an '&'.
Example (by patient ID):
//yourgatewaycomputer.com/Webviewer/Gateway/frameset.asp?Login=youruser&Pwd=yourpassword&
PatID=yourpatientID

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 273
PatientWatch

List of available arguments

Arguments Description Comment

Serv Server Name This argument is required only when
trying to access the patient by
providing the bed label and care unit
label. If it is omitted and the patient ID
or MC address are included, then the
server is determined via the
Map2Server Control on the Web
Server.
Login User Name The user name and password
arguments are required in order for
any argument to have any effect.
Pwd Password The user name and password
arguments are required in order for
any argument to have any effect.
Domain Domain name The domain name can be used to
qualify the user name and password
although it is not required.
CU Care Unit The patient monitor can be specified
by providing both the care unit and
bed label.
Bed Bed Label The patient monitor can be specified
by providing both the care unit and
bed label.
PatID The patient monitor can be specified
by providing the identifier of the
patient that is being monitored.
MC Multicast address of The patient monitor can be specified
a specific bed by providing the multicast address of
the patient monitor.
File Settings File The PatientWatch client settings can
read from a file by passing in the
location of the settings file. If the file
does not exist in the location
provided then a new settings file is
generated.

274 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 PatientWatch

Use of Arguments

Arguments Comment Access to User Server Used

Patient must
Selection log on
None Invokes PatientWatch in the YES YES First server in
same way as the default Map2Server list.
PatientWatch page.
Serv Automatically selects the YES YES Server in
current server. argument.
Login, Pwd Automatically logs in to the YES NO First server in
first server found for the user Map2Server list.
in Map2Server.
Serv, Login, Automatically logs in to the YES NO Server in
Pwd named server. argument.
Login, Pwd, Automatically determines NO NO First available
PatID which server should be used server that
to access the specified provides access
patient, logs into that server to Patient selected
and selects the patient by patient ID.
monitor.
Serv, Login, Automatically logs into the NO NO Server in
Pwd, PatID named server and selects argument.
the patient monitor with the
PatientIdentifier provided.
The patient monitor must be
available on server
specified.
Login, Pwd, CU, Automatically determines NO NO Not Supported.
Bed which server should be used When selecting a
to access the specified patient by care
patient monitor, logs into that unit and bed label,
server and selects the the server name is
patient monitor. required.
Serv, Login, Automatically logs into the NO NO Server in
Pwd, CU, Bed named server and selects argument.
the patient monitor specified.
The patient monitor must be
available on named server.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 275
PatientWatch

Arguments Comment Access to User Server Used

Patient must
Selection log on
Login, Pwd, MC Automatically determines NO NO First available
which server should be used server that
to access the specified provides access
patient monitor, logs into that to the patient
server and selects the monitor selected
patient monitor. by multicast
address.
Serv, Login, Automatically logs into the NO NO Server in
Pwd, MC named server and selects argument.
the patient monitor specified.
The patient monitor must be
available on named server.
File Invokes PatientWatch in the YES YES First server in
same way as the default Map2Server list.
PatientWatch page. All
Client settings are read from
the file in the location
provided. If no file is present
then a new one is created.

276 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix A: Parameters

Appendix A: Parameters

CAUTION
The parameter tables map Dräger’s parameter labels and codes to corresponding HL7/LOINC and
MIB/CEN codes, when applicable. Most often, no HL7/LOINC and/or MIB/CEN codes exist which
approximate a description of the supported parameter. Otherwise, a similar, but not exact, HL7/LOINC
or MIB/CEN code is used to approximate a description of the parameter in question.
Review the codes below before use. Potential sources of the parameters are identified as Monitor, Mon-
itor/POD, Monitor/Ext, Monitor/MGM or ANESTH. “Monitor” or “patient monitor” refers to all Infinity mon-
itoring devices and may include Configured (Vista, Gamma/GammaXL), Modular (VistaXL, GammaXXL,
Delta/DeltaXL, Kappa, or KappaXLT) or Infinity Telemetry monitoring devices. ‘Monitor/POD’ refers to
modular monitors using a specific Infinity Pod. ‘Monitor/Ext’ refers to any Modular monitor connected to
a 3rd party device via MIB protocol converter or external Device Connection ‘Monitor/MGM’ refers to the
Scio MultiGas Module which connects to the network via a Modular Monitor. ‘ANESTH’ refers to a Dräger
LSS anesthesia workstation that also connects to the Infinity Network via a modular monitor.
The parameter tables are not intended to specify which parameters are available at a particular customer
site as this will vary depending on the specific patient monitors being used, the versions of software
installed on those patient monitors, the types and versions of pods being used, and the options pur-
chased for the patient monitors.
Reference the patient monitor’s instructions for use or contact a service representative for the necessary
configurations to generate certain parameters.

NOTE
The Parameter table has been moved to an Excel document. The Excel document, “Protocol Handbook
Appendices.xlsx”, which contains the Parameter table can be found in the Infinity Gateway installation
location or on the installation CD.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 277
 This page has been left blank intentionally.

278 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix B: Units of Measure

Appendix B: Units of Measure

NOTE
The Unit of Measure table has been moved to an Excel document. The Excel document, "Protocol
Handbook Appendices.xlsx", which contains the Unit of Measure table can be found in the Infinity
Gateway installation location or on the installation CD.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 279
 This page has been left blank intentionally.

280 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix C: Special Display Values

Appendix C: Special Display Values

Special Display Value Description

Invalid
+++ Out of range (positive)
--- Out of range (negative)
*** Technical condition
ASY Asystole
VF Ventricular fibrillation
VT Ventricular tachycardia
RUN Run of ventricular tachycardia
IVR Ideoventricular Rate
SVT Supraventricular Tachycardia
CPT Couplet
CPT Couplet
BGM Bigeminy
TAC Tachycardia
BRA Bradycardia
EPV Epvc
PNC Pacemaker Non Capture
PAU Pause
RON R on T
ART Artifact
IRR Irregular beat
LRN Arrhythmia or ST learning
APN Apnea
AIVR Accelerated idioventricular rate
STB Standby
TST System test
< Low clip
> High clip
ON Powerup
CHG ST measure
*A* Artifact

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 281
Appendix C: Special Display Values

Special Display Value Description

*F* Fault
*I* Interference
*L* Lead off
*N* No Signal
*U* Unplugged
OFF OFF

282 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix D: Alarm States

Appendix D: Alarm States

# Alarm State Alarm State Description

Value
1 WV_ALARM_STATE_NOT_AC- INACTIVE No currently active alarms.
TIVE
2 WV_ALARM_STATE_ACTIVE ACTIVE There is currently an active
alarm.
3 WV_ALARM_STATE_SILENCED SILENCED There is currently an alarm con-
dition, but it has been acknowl-
edged.
4 WV_ALARM_STATE_REACTIVE REACTIVE An alarm condition that had
been silenced, is now re-active
since the silence time period
expired.
5 WV_ALARM_STATE_LATCHED LATCHED An alarm condition that was
active has gone away, but the
original alarm condition has not
yet been acknowledged.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 283
 This page has been left blank intentionally.

284 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix E: Alarm Grades

Appendix E: Alarm Grades

# Alarm Grade Alarm Grade Value Description

1 WV_ALARM_GRADE_NONE NONE No alarm
2 WV_ALARM_GRADE_ADV ADV Low-priority (Advisory) alarm
(such as lead-off)
3 WV_ALARM_GRADE_SER SER Medium-priority (Serious) alarm
(such as HR out of limits)
4 WV_ALARM_GRADE_LT L-T High-priority (Life-Threatening)
alarm (such as asystole)

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 285
 This page has been left blank intentionally.

286 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix F: Waveforms

Appendix F: Waveforms

NOTE
The Waveforms table has been moved to an Excel document. The Excel document, “Protocol Handbook
Appendices.xlsx”, which contains the Waveforms table can be found in the Infinity Gateway installation
location or on the installation CD.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 287
 This page has been left blank intentionally.

288 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix G: Operation Modes

Appendix G: Operation Modes

# Operation Mode Operation Description

Mode Value
1 WV_OPERATING_MODE_MONITORING Monitoring Monitoring
2 WV_OPERATING_MODE_STANDBY Standby Standby
3 WV_OPERATING_MODE_READY Ready Ready
4 WV_OPERATING_MODE_BUSY Busy Busy
5 WV_OPERATING_MODE_PAPEROUT Paper Out Paper Out
6 WV_OPERATING_MODE_DOOR_OPEN Door Open Door Open
7 WV_OPERATING_MODE_COMM_FAILURE Comm Failure Communication Failure
8 WV_OPERATING_MODE_DEVICE_FAILURE Device Fail- Device Failure
ure
9 WV_OPERATING_MODE_NA N/A Not available

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 289
 This page has been left blank intentionally.

290 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix H: 12-Lead ECG Output Format

Appendix H: 12-Lead ECG Output Format

NOTE
12 lead ECG output is only supported by Infinity devices.

#ifndef __FORMAT_H__
#define __FORMAT_H__

// specify byte alignment (using default)

// #pragma pack(4)

// data types
typedef unsigned char uchar;
typedef unsigned short ushort;
typedef unsigned long ulong;

// ECG Info
#define LEADCOUNT 15
#define LEADSIZ 5120
#define LEADSAMPLES (LEADCOUNT * LEADSIZ)
#define STMTCOUNT 50
#define STMTLEN 128
#define DESTBUFSIZ 100000

// Lead Definitions
#define LEAD_NOTPRESENT 0
#define LEAD_I 1
#define LEAD_II 2
#define LEAD_III 3
#define LEAD_AVR 4
#define LEAD_AVL 5
#define LEAD_AVF 6
#define LEAD_V1 7
#define LEAD_V2 8
#define LEAD_V3 9
#define LEAD_V4 10
#define LEAD_V5 11
#define LEAD_V6 12
#define LEAD_X 13
#define LEAD_Y 14
#define LEAD_Z 15
#define LEAD_C1 16
#define LEAD_C2 17
#define LEAD_C3 18
#define LEAD_C4 19
#define LEAD_C5 20
#define LEAD_C6 21
#define LEAD_CM5 22
#define LEAD_CC5 23
#define LEAD_V1R 24

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 291
Appendix H: 12-Lead ECG Output Format

#define LEAD_V2R 25
#define LEAD_V3R 26
#define LEAD_V4R 27
#define LEAD_V7 28
#define LEAD_V8 29
#define LEAD_V9 30
#define LEAD_USER1 31
#define LEAD_USER2 32
#define LEAD_USER3 33

// ecg format constants

#define ECGFORMAT_3X4 0
#define ECGFORMAT_3X4_1R 1
#define ECGFORMAT_3X4_3R 2
#define ECGFORMAT_6X2 3

// age units constants

#define AGEUNIT_NONE -1
#define AGEUNIT_HOURS 0
#define AGEUNIT_DAYS 1
#define AGEUNIT_WEEKS 2
#define AGEUNIT_MONTHS 3
#define AGEUNIT_YEARS 4

// lsb values
#define LSB_1_00 0
#define LSB_2_44 1
#define LSB_2_50 2
#define LSB_4_88 3
#define LSB_5_00 4

// sample rate values

#define SAMPLE_RATE_250 0
#define SAMPLE_RATE_500 1

// hi/lo pass filter constants

#define LOPASS_0_05 0
#define LOPASS_0_15 1
#define LOPASS_0_50 2
#define HIPASS_150 0
#define HIPASS_100 1
#define HIPASS_40 2

// field lengths
#define PID_LEN 16
#define DATE_LEN 8
#define TIME_LEN 6
#define FNAME_LEN 20
#define LNAME_LEN 22
#define NAME_LEN 42
#define ROOM_LEN 8
#define DEPT_LEN 8
#define TECH_LEN 4

292 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix H: 12-Lead ECG Output Format

#define USER_LEN 18
#define MANUF_LEN 8
#define MODEL_LEN 8
#define SERNBR_LEN 16
#define VER_LEN 8
#define REQNBR_LEN 12

// structures
typedef struct
{
char Pid[PID_LEN + 1]; // Patient ID
char AcqDate[DATE_LEN + 1]; // ECG Acquisition Date (MMDDYYYY)
char AcqTime[TIME_LEN + 1]; // ECG Acquisition Time (HHMMSS)
long ECGFormat; // ECG Format (presentation)
long Institution; // Location/Institution
long StatFlag; // Status Flag
char FName[FNAME_LEN + 1]; // Patient First Name
char LName[LNAME_LEN + 1]; // Patient Last Name
long AgeUnits; // Age Units
long AgeValue; // Number of <units> for Age
long Height; // Height
long UnitsHeight; // Imperial/Metric Units for Height
long Weight; // Weight
long UnitsWeight; // Imperial/Metric Units for Weight
long Sex; // Sex (0 = male, 1 = female)
long Race; // Race Code
long Systolic; // Systolic Blood Pressure
long Diastolic; // Diastolic Blood Pressure
char Room[ROOM_LEN + 1]; // Room Number – the Bed Label from the INFINITY monitor
char Dept[DEPT_LEN + 1]; // Department
char Tech[TECH_LEN + 1]; // Technician/Operator
long Drugs; // Drug Code
long Diag; // Diagnosis Code
char ReqDoctor[NAME_LEN + 1]; // Requesting Doctor's Name - last first
char ConfDoctor[NAME_LEN + 1]; // Confirming Doctor's Name - last first
long Confirmed; // Confirmed Flag (0 = unconfirmed, 1 = confirmed)
char ConfDate[DATE_LEN + 1]; // (MMDDYYYY)
char ConfTime[TIME_LEN + 1]; // (HHMMSS)
char ConfEditor[NAME_LEN + 1]; //
char UserA[USER_LEN + 1]; // User Field A
char UserB[USER_LEN + 1]; // User Field B
char ManufID[MANUF_LEN + 1]; // Manufacturer's ID
char CartModel[MODEL_LEN + 1]; // ECG Cart – Model #, the Infinity bed label with an X on the end.
char CartSerNbr[SERNBR_LEN + 1]; // ECG Cart - – Serial #
char CartVersion[VER_LEN + 1]; // ECG Cart - – Analysis Version # - This is the bedside monitor software
version
char ReqNbr[REQNBR_LEN + 1]; // Requisition #
long SampleRate; // Sample Rate (0 = 250, 1 = 500)
long LSBValue; // LSB value (see constant definitions)
long ArtFilter; // Artifact Filter
long BaseFilter; // Baseline Wander Filter
long ACFilter; // AC Filter
long LoPassFilter; // Front End Filter - – Low-pass filter
long HiPassFilter; // Front End Filter - – High-pass filter
long VLeadAmpl; // V-Lead Amplitude

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 293
Appendix H: 12-Lead ECG Output Format

long TraceSens; // Overall Trace Sensitivity

long VRate; // Ventricular Rate
long PRInt; // PR Interval
long QRSDur; // QR Duration
long QTInt; // QT Interval
long PAxis; // P Axis
long QRSAxis; // QRS Axis
long TAxis; // T Axis
long QTC; // QTC - (Rate-Corrected QT Interval)
long PDuration; // p_duration
long POnset; // p_onset
long POffset; // p_offset
long QOnset; // q_onset
long QOffset; // q_offset
long TOffset; // t_offset
long NbrStmts; // Number of Statements
} ECGHEADER; // 508 bytes
// NOTES:
// 1. All alpha fields are Left Justified, NULL Filled, and NULL
// Terminated unless otherwise marked.
// 2. If a numeric value is not present, it will be set to -1 (0xffffffff)
// 3. If a character field is not present, it will just be all NULLs
// 4. If an axis field (PAxis, QRSAxis, TAxis) is not present, it will be set to 0x00007fff

typedef struct
{
char StmtText[STMTCOUNT][STMTLEN]; // Diagnosis Statements – Notes from Bedside
} ECGSTMTS; // 6400 bytes
typedef struct
{
long LeadID[LEADCOUNT]; // identifies each lead and whether present
short Lead[LEADCOUNT][LEADSIZ]; // 12 bit signed ECG data, Intel format
} ECGLEADS; // 153660 bytes

#endif
// end of file

294 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix I: Troubleshooting Gateway M300 Connections

Appendix I: Troubleshooting Gateway M300 Connections

The Infinity Gateway communicates directly with the Infinity OneNet network. This allows trends from
attached and configured beds to be available to the Infinity Gateway. However, due to requirements of
M300 devices related to battery life, these devices must be installed on a separate network, usually on a
separate VLAN. As a result, the subnet may not be available and it may be necessary to configure
additional routing on the server for the Infinity Gateway product to access the separate M300 network.
Four network interfaces and configurations that allow Infinity Gateway to collect trends from an M300 are
as follows:

1. Infinity Gateway Server (2 NICs) and Infinity Central Station (1 NIC)

The first network interface includes the Infinity Gateway server with one NIC for the hospital and one NIC
for the Infinity Gateway. The Infinity Central Station includes one NIC for Infinity Gateway.

In this setup, the M300 VLan is connected to the Infinity Network through a wireless router, and the Infinity
Gateway is configured for both the Infinity and Hospital Networks. The ICS is configured to access the
M300 subnet through a router which can be used in the same manner for Infinity Gateway. To add the
router to the Infinity Gateway, open a command prompt as administrator and enter:
route –p add <M300 subnet> mask <subnet mask> <Router IP>
The command instructs the server to use the router to access the M300 subnet.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 295
Appendix I: Troubleshooting Gateway M300 Connections

2. Infinity Gateway Server (2 NICs) and Infinity Central Station (2 NICs)

The second network interface includes the Infinity Gateway server with one NIC for the hospital and one
NIC for the Infinity Gateway. There is also an Infinity Central Station with one NIC and the M300 with one
NIC.
With dual NICs, this network interface on the ICS directly communicates with the M300 subnet. There is
no stand-alone router device on the Infinity network. However the Infinity Central Station acts as a router
between the Infinity Network and the M300 subnet.
To add the router to the Infinity Gateway, an administrator opens a command prompt and enters the
following:
route –p add <M300 Subnet> mask <subnet mask> <IP of 1st NIC>
For example, the Infinity network’s first NIC has an IP address of 192.168.10.50 with a subnet of /24 or
255.255.255.0, and a second NIC IP address of 192.168.20.50 with a subnet of /24. In this case, all
M300s would have the second NIC IP address as the default Gateway, or 192.168.20.50. The command
to run on the Infinity Gateway is:
route –p add 192.168.20.0 mask 255.255.255.0 192.168.10.50

296 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix I: Troubleshooting Gateway M300 Connections

3. Infinity Gateway Server (1 NIC) and Infinity Central Station (2 NICs)

The third network interface includes the Infinity Gateway server and one NIC, the Infinity Central Station
and one NIC, and the M300 and one NIC.
With dual NICs, a network interface on the ICS is used to communicate with the M300 subnet directly.
Therefore, there is no stand-alone router device on the Infinity network. However, the Infinity Central
Station acts as a router between the Infinity Network and the M300 subnet.
To add the router to the Infinity Gateway, open a command prompt as an administrator and type the
following:
route –p add <M300 Subnet> mask <subnet mask> <IP of 1st NIC>

For example, the Infinity Network’s first NIC has an IP address of 192.168.10.50 with a subnet of /24, or
255.255.255.0. The second NIC has an IP address of 192.168.20.50 and a subnet of /24. In this case, all
M300s would have the second NICs IP address as their default Gateway, or 192.168.20.50. Type the
following on the Infinity Gateway:
route –p add 192.168.20.0 mask 255.255.255.0 192.168.10.50

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 297
Appendix I: Troubleshooting Gateway M300 Connections

4. Infinity Gateway Server (1 NIC) and Infinity Central Station (1 NIC)

The forth network interface includes the Infinity Gateway server with one NIC and the Infinity Central
Station with one NIC. No action is required in this setup since the default router lets you communicate with
the M300 subnet.
To test whether the routing was successful, from the Gateway server open a command prompt and ping
the IP address of an M300. A successful ping indicates that the router was added successfully.

298 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
 Appendix J: Relationship table

Appendix J: Relationship table

NOTE
The Relationship table has been moved to an Excel document. The Excel document, "Protocol Handbook
Appendices.xlsx", which contains the Relationship table, can be found in the Infinity Gateway installation
location or on the installation CD.

Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0 299
 This page has been left blank intentionally.

300 Instructions for use – Infinity® Gateway Suite – Protocol Handbook – VF9.0
These instructions for use only apply to
Infinity Gateway Suite
Protocol Handbook VF9.0
with the Serial No.:
If no Serial No. has been filled in by Dräger,
these instructions for use are provided for
general information only and are not intended for
use with any specific machine or unit.

Distributed in USA by

Draeger Medical Systems, Inc. Draeger, Inc.

3135 Quarry Road 3135 Quarry Road
Telford, PA 18969-1042 Telford, PA 18969-1042
U.S.A. U.S.A.
(215) 721-5400 (215) 721-5400
(800) 4DRAGER (800) 4DRAGER
(800 437-2437) (800 437-2437)
FAX (215) 723-5935 FAX (215) 723-5935
http://www.draeger.com http://www.draeger.com

Drägerwerk AG & Co. KGaA

Moislinger Allee 53 – 55
D-23542 Lübeck
Germany
+49 451 8 82-0
FAX +49 451 8 82-20 80
http://www.draeger.com

3703522 – RI 03 en
© Drägerwerk AG & Co. KGaA
Edition: 4 – 2023-02
(Edition: 1 – 2019-03)

Dräger reserves the right to make modifications

to the equipment without prior notice.