Infinity Gateway Suite Protocol Handbook - Draeger

Instructions for Use

Infinity® Gateway Suite

Protocol HandbookSoftware VF9.n

WARNINGFor a full understanding of the performance characteristics of this software, the user should carefully read this manual before use.

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

General Information

General Information

Repairs/Modifications

Modifications of this software should be performed by Dräger-authorized service personnel, its authorized service organizations or properly trained technicians. Information about repairs can be obtained from Dräger or authorized service organizations.

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.

Safety

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

Safety

Follow instructions for use

Definitions

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

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 6 and in conjunction with appropriate patient monitoring. Observe all WARNING and CAUTION statements as rendered throughout this manual, and all statements on device labels.

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.


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 technologies, 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.

Intended use


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.

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.

CAUTION

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


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.


This page has been left blank intentionally.


Table of Contents

Table of Contents

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

Safety. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Intended use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

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

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Infinity Gateway Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

File Access Developer’s Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

WinAccess API Developer’s Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 23

HL7 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Unsolicited Vital Signs Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Unsolicited IEEE 11073 Vital Signs Export . . . . . . . . . . . . . . . . . . 59

Solicited Vital Signs Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Unsolicited ADT Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

IHE Unsolicited ADT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Solicited ADT Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Lab Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

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

Alarm Communication Management Interface . . . . . . . . . . . . . . 217

ASTM Stat Lab Interface Option . . . . . . . . . . . . . . . . . . . . . . . . . . 245

PatientWatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Appendix A: Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Appendix B: Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

Appendix C: Special Display Values. . . . . . . . . . . . . . . . . . . . . . . 283

Appendix D: Alarm States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Table of Contents


Appendix E: Alarm Grades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

Appendix F: Waveforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Appendix G: Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

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

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

Appendix J: Relationship table . . . . . . . . . . . . . . . . . . . . . . . . . . . 301


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.

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.

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.



Preface


Infinity Gateway Server


The Infinity Gateway Server facilitates the exchange of important clinical information between the Infinity/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.



Infinity Gateway Developer’s Tools and Interface Options

Interface Type Description

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.



Interpret Patient ID as Setting

This setting on the Server specifies how to interpret the patient identifier entered on patient monitors.

Thisidentifier 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.

WARNING

The Infinity Gateway Developers Tools 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 Infinity Gateway Developers Tools and Interface Options are not intended to develop a replacement for the primary alarm notification system. The delivery of pages cannot be guaranteed or verified. Applications developed with the Infinity Gateway’s Developers Tools should not be intended or designed to replace monitoring personnel or good clinical judgment, or to be used in place of bedside or remote alarm notifications provided by the monitoring system.

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, version 10.3.128. 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.


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 17 file containing a list of current patients, additional system demographic data detailed in Section 4.1, and the corresponding "Vital Signs Files" on page 18 file name.

"Vital Signs Files" on page 18 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 Infinity 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



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:

Vital Signs Files

The Vital Signs file is created for each patient listed in the Patient Directory file. Each Vital Signs file contains 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

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.



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 current 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



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.



Patient Directory

The single line in this section contains the same information listed in the patient’s line in the Patient Directory 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 parameters 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.



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 Display 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 Status

Unused

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 standard.


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.

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.

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

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

CAUTION

Each connection should be used by only one thread.



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.

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

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.



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”

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

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:

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”.

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.

Build Configuration Name

Debug/ Release

Unicode/ ANSI

Local/ Remote

Exe name

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

Debug Unicode Remote RemoteWvUAPITest

Win32 Remote Unicode Release

Release Unicode Remote RemoteWvUAPITest



Functions

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.

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 either Infinity or SDC networks.

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-GradeAlarm

Returns information about the highest grade, currently active alarm (if any).

WvGetHighestGrade-VentAlarm

Returns information about the highest grade, currently active ventilator 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-forms

Fills in a list of all available waveforms from a device.

WvDescribeWaveform Fills in a structure with data for a given waveform.

WvGetWaveformSam-ples

Fills a buffer with samples for the specified waveform.

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 available for an SDC-only device.

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 an SDC-only 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.

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.




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.

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

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.



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.


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 Interfaces


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.

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:

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.

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


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.

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.

HL7 Interfaces


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

Escape Sequences

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

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

0x0B MSH segment

0x0D segment 0x0D … segment 0x0D 0x1C 0x0D

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

\F\ field separator

\S\ component separator

\T\ subcomponent separator

\R\ repetition separator

\E\ escape character


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 data

t_adt

t_allergies

t_diagnosis

t_doctor

t_insurance

t_nok

t_picklist

ICS and certain patient monitors

Vitals Signs Patient parameter data *Refer to Parame-ters Feature

t_acceptableunits

t_itemconversions

t_picklist

t_units

ADT configuration ADT mapping tables for race, religion, nationality, primary language and ethnicity

t_Picklist Gateway

HL7 Lab Import/ ASTM Lab Import

Parameter Priority and Grouping

Calculator mapping

t_lab_group,

t_lab_param

Gateway and patient monitors

HL7 Interfaces


HL7 accesses the databases using ADO. These databases are stored in SQL Server 2008 R2 databases, however SQL Server 2008 R2 Express is 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.

Parameters Parameter definitions t_params

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

Gateway

Character Mapping User-defined Unicode to single byte charac-ter maps used in HL7 Lab Import and Pager

t_charmap

t_charmap_list

Gateway

Interface/Feature Description Tables Consumer of Data via HL7


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 33 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.

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.

NOTE

The solicited and unsolicited Vitals Interfaces are mutually exclusive.

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



MSH Segment - Message Header

HL7 HL7 Dräger

Seq 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” by default. Field is configurable.

O 180

6 00006 Receiving Facility

O HD 180 “” by default. Field is configurable.

O 180

7 00007 Date/Time of Message

O TS 26 YYYYMMDDHHmmss <offset>

O 12

8 00008 Security O ST 40 <not used>

9 00009 Message Type R CM 7 “ORU^R01^ORU_R01”

R 7

10 00010 Message Control ID

R ST 20 A number uniquely identifying the message. The receiving system echoes this ID back to the sending system in the message acknowledgment segment (MSA).

R 20

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 Acknowledgment Type

O ID 2 “AL” R 2

16 00016 Application Acknowledgment

O ID 2 “NE” R 2

17 00017 Country Code O ID 2 <not used>

18 00692 Character Set O ID 6 <not used>

19 00693 Principal Language Of Message

O CD 60 <not used>

MSH Segment - Message Header (Continued)

HL7 HL7 Dräger




PID Segment - Patient Identification

HL7 HL7 Dräger


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 See Patient Identifiers R 12

4 00107 Alternate Patient ID - PID

O CX 20 <not used>

5 00108 Patient Name R XPN 48 See Patient Name O 32

6 00109 Mother’s Maiden Name

O XPN 48 *"Last^First^ Middle^ " O 250

7 00110 Date/Time of Birth

O TS 26 *YYYYMMDDhhmmss O 24

8 00111 Sex O IS 1 *"Code^Text"

Taken from ADT Configuration Information.

O 705

9 00112 Patient Alias O XPN 48 <not used>

10 00113 Race O IS 26 *"Code^Text" Taken from ADT Configuration Information.

O 705

11 00114 Patient Address

O XAD 1 *"Street1^Street2^City^State^Zip Code^Country^M"

O 250

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 *"Code^Text"




16 00119 Marital Status O IS 40 *"Code^Text" Taken from ADT Configuration Information.

O 40

17 00120 Religion O IS 40 *"Code^Text"


O 40

18 00121 Patient Account Number

O CX 60 See Patient Identifiers O 12

19 00122 SSN Number - Patient

O ST 16 *National ID O 16

20 00123 Driver's License Number - Patient

O CM 25 <not used>

21 00124 Mother's Identifier

O CX 20 <not used>

22 00125 Ethnic Group O IS 3 *"Code^Text"


O 3

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 *"Code^Text"


O 80

29 00132 Patient Death Date and Time

O TS 26 <not used>

30 00133 Patient Death Indicator

O ID 1 <not used>

PID Segment - Patient Identification (Continued)

HL7 HL7 Dräger




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:

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”.

NOTE

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

InterpretPatient ID asSetting

Field 3 contents Field 18 contents

MRN <MRN>^^^<Assigning Authority>^MR

"<Patient Account#>"

Patient Account #

If "ADT Data in Message" is enabled and there is a record in the database for the patient that contains an MRN then the field contains <MRN>^^^<Assigning Authority>^MRotherwise the field contains

<Patient Account#>^^^^AN

"<Patient Account#>"



PV1 Segment - Patient Visit

HL7 HL7 Dräger


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

2 00132 Patient Class R IS 1 *Patient Class

3 00133 Assigned Patient Location

O PL 80 Location of the patient, in format <Care Unit Label>^^<Bed Label>^<hospital>. Fields are as defined during monitor configuration.

R 18

4 00134 Admission Type

O IS 2 <not used>

5 00135 Preadmit Number

O CX 20 <not used>

6 00136 Prior Patient Location

O PL 80 <not used>

7 00137 Attending Doctor

O XCN 60 *"^Last Name ^First Name ̂ Middle Name ^Suffix^Prefix ^Degree"

O 60

8 00138 Referring Doctor


O 60

9 00139 Consulting Doctor


O 60

10 00140 Hospital Service

O IS 3 <not used>

11 00141 Temporary Location

O PL 80 <not used>

12 00142 Preadmit Test Indicator

O IS 2 <not used>

13 00143 Readmission Indicator

O IS 2 <not used>

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 *"^Last Name ^First Name ^Middle Name ^Suffix^Prefix ^Degree"

O 60

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 Indicator

O IS 2 <not used>

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 Date

O DT 8 <not used>

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 Code

O IS 1 <not used>

30 00160 Transfer to Bad Debt Date

O DT 8 <not used>

31 00161 Bad Debt Agency Code

O IS 10 <not used>

32 00162 Bad Debt Transfer Amount

O NM 12 <not used>

33 00163 Bad Debt Recovery Amount

O NM 12 <not used>

34 00164 Delete Account Indicator

O IS 1 <not used>

35 00165 Delete Account Date

O DT 8 <not used>

36 00166 Discharge Disposition

O IS 3 <not used>

37 00167 Discharged to Location

O CM 25 <not used>

PV1 Segment - Patient Visit (Continued)

HL7 HL7 Dräger




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 Location

O PL 80 <not used>

44 00174 Admit Date/Time

O TS 26 *YYYYMMDDhhmmss

O 24

45 00175 Discharge Date/Time

O TS 26 <not used>

46 00176 Current Patient Balance

O NM 12 <not used>

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 Provider

O XCN 60 <not used>

NOTE

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


HL7 HL7 Dräger




OBR Segment - Observation Request

HL7 HL7 Dräger


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/time the observation is obtained from the Infinity Network, in format YYYYMMDDHHmmss.

R 14

8 00242 Observation End Date/Time

O TS 26 <not used>

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 Date/Time

C TS 26 <not used>

15 00249 Specimen Source

O CM 300 <not used>

16 00226 Ordering Provider

O XCN 80 <not used>

17 00250 Order Callback Phone Number

O XTN 40 <not used>

18 00251 Placer field 1 O ST 60 <not used>




20 00253 Filler Field 1 + O ST 60 <not used>


22 00255 Results Report/Status Change Date/Time +

C TS 26 <not used>

23 00256 Charge to Practice +

O CM 40 <not used>

24 00257 Diagnostic Service Section 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 Interpreter +

O CM 200 <not used>

33 00265 Assistant Result Interpreter +

O CM 200 <not used>

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 Containers

O NM 4 <not used>

38 01029 Transport Logistics of Collected Sample

O CE 60 <not used>

OBR Segment - Observation Request (Continued)

HL7 HL7 Dräger




39 01030 Collector's Comment

O CE 200 <not used>

40 01031 Transport Arrangement Responsibility

O CE 60 <not used>

41 01032 Transport Arranged

O ID 30 <not used>

42 01033 Escort Required

O ID 1 <not used>

43 01034 Planned Patient Transport Comment

O CE 200 <not used>


HL7 HL7 Dräger




OBX Segment - Observation/Result

HL7 HL7 Dräger


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

2 00570 Value Type C ID 2 “SN” (structured numeric) if the parameter value reported by the device is numeric, otherwise “ST” (string).

R 2

3 00571 Observation Identifier

R CE 590 See Observation Identifier

R

4 00572 Observation Sub-ID

C ST 20 <not used>

5 00573 Observation Value

C * 65536

See Observation Value

R 30

6 00574 Units O CE 60 Uniquely identifies 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.

O 30

7 00575 References Range

O ST 10 <not used>

8 00576 Abnormal Flags

O ID 5 <not used>

9 00577 Probability O NM 5 <not used>

10 00578 Nature of Abnormal Test

O ID 2 <not used>

11 00579 Observation Result Status

R ID 1 “R” R 1

12 00580 Date Last Observation Normal Values

O TS 26 <not used>

13 00581 User Defined Access Checks

O ST 20 <not used>



Observation Identifier

Uniquely identifies the parameter being reported, in the format:

<identifier1^^local^<<identifier2>&<instance >>^^<coding system >

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.

Observation Value

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

14 00582 Date/Time of the Observation

O TS 26 YYYYMMDDHHmmss

O 12

15 00583 Producer's ID O CE 60 <not used>

16 00584 Responsible Observer

O XCN 80 <not used>

17 00936 Observation Method

O CE 60 <not used>

18 01479 Equipment Instance Identifier

O EI 427 <Unique ID>^<model>^<manufacturer 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.

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

OBX Segment - Observation/Result (Continued)

HL7 HL7 Dräger




ACK – Acknowledgment

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

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

Value Type Observation Value Field Format Comments

ST <value> See Appendix C: Special Display Values for special value strings

SN <comparator>^<value> comparator is “=”

Segment Description


MSA MSA Segment – Message Acknowledgment




HL7 HL7 Dräger


1 00001 Field Separator R ST 1 Recommended value is “|”

R 1


R ST 4 Four characters in the following order: the component separator, the repetition separator, the escape character, and the subcomponent separator. Recommended values are “^~\&”.

R 4


O HD 180 A string identifying the sending application.

O 16


O HD 180 <not used>


O HD 180 <not used>


O HD 180 <not used>


O TS 26 YYYYMMDDHHmm

O 12


9 00009 Message Type R CM 7 “ACK^R01” R 7


R ST 20 A number or other identifier uniquely identifying the message.

R 20


12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>



14 00014 Continuation Pointe

O ST 180 <not used>


O ID 2 <not used>


O ID 2 <not used>




O CE 60 <not used>


HL7 HL7 Dräger




MSA Segment – Message Acknowledgment

Acknowledgment Codes

Sample ORU Message

MSH|^~\&|Infinity||NUR||200212021207||ORU^R01|02110212073000458038|P|2.3

PID|||999-99-9999ÂN||Smith^John^L|||||||||||||999-99-9999

PV1|||CU1^^BED1||||^^^|||||||||||||||||||||||||||||||||||||

OBR|||||||20021202120235

OBX||SN|STIII^^local^10123-8&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

OBX||SN|STaVR^^local^10120-4&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

OBX||SN|STaVF^^local^10118-8&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

HL7 HL7 Dräger


1 00018 Acknowledgment Code

R ID 2 See Acknowledgment Codes

R 1


R ST 20 The message control ID of the message it is acknowledging.

R 4

3 00020 Text Message O ST 80 An error or status string

O 80

4 00021 Expected Sequence Number

O NM 15 <not used>

5 00022 Delayed Acknowledgment Type

B ID 1 <not used>

6 00023 Error Condition O CE 100 <not used>

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



OBX||SN|STaVL^^local^10119-6&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

OBX||SN|STV^^local^14692&1^^MIB/CEN||=^0.01|mv^ÎSO+|||||R|||20021202120235

OBX||ST|PPR^^local^8893-0&1^^LOINC|| |mm(hg)^ÎSO+|||||R|||20021202120235

OBX||SN|PA D^^local^8385-7&1^^LOINC||=^1.8|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|PA S^^local^8440-0&1^^LOINC||=^4.4|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|PA M^^local^8414-5&1^^LOINC||=^2.8|kpa^ÎSO+|||||R|||20021202120235

OBX||ST|PWP^^local^8587-8&1^^LOINC|| |kpa^ÎSO+|||||R|||20021202120235

OBX||SN|CVP^^local^8591-0&1^^LOINC||=^2.0|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|RA^^local^8400-4&1^^LOINC||=^2.0|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Med^^local^22912&1^^MIB/CEN||=^10.0|hz^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 SEF^^local^22920&1^^MIB/CEN||=^12.5|hz^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 BSR^^local^&1^^MIB/CEN||=^30|%^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Power^^local^22968&1^^MIB/CEN||=^67|dB^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Beta^^local^23000&1^^MIB/CEN||=^30|%^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Alpha^^local^22996&1^^MIB/CEN||=^20|%^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Theta^^local^23008&1^^MIB/CEN||=^25|%^ÎSO+|||||R|||20021202120235

OBX||SN|EEG1 Delta^^local^23004&1^^MIB/CEN||=^25|%^ÎSO+|||||R|||20021202120235

OBX||SN|etCO2*^^local^20824&2^^MIB/CEN||=^5.0|%^ÎSO+|||||R|||20021202120235

OBX||SN|iCO2*^^local^20644&2^^MIB/CEN||=^0.0|%^ÎSO+|||||R|||20021202120235

OBX||SN|RRc*^^local^9279-1&4^^LOINC||=^20|/min^ÎSO+|||||R|||20021202120235

OBX||SN|etO2^^local^20844&2^^MIB/CEN||=^33|%^ÎSO+|||||R|||20021202120235

OBX||SN|iO2^^local^3150-0&2^^LOINC||=^35|%^ÎSO+|||||R|||20021202120235

OBX||SN|etN2O^^local^21036&2^^MIB/CEN||=^58|%^ÎSO+|||||R|||20021202120235

OBX||SN|iN2O^^local^21120&2^^MIB/CEN||=^60|%^ÎSO+|||||R|||20021202120235

OBX||SN|etHAL^^local^21020&2^^MIB/CEN||=^0.9|%^ÎSO+|||||R|||20021202120235

OBX||SN|iHAL^^local^21104&2^^MIB/CEN||=^1.1|%^ÎSO+|||||R|||20021202120235

OBX||SN|et ISO^^local^21028&2^^MIB/CEN||=^1.3|%^ÎSO+|||||R|||20021202120235

OBX||SN|i ISO^^local^21112&2^^MIB/CEN||=^1.5|%^ÎSO+|||||R|||20021202120235

OBX||SN|etENF^^local^21016&2^^MIB/CEN||=^1.8|%^ÎSO+|||||R|||20021202120235

OBX||SN|iENF^^local^21100&2^^MIB/CEN||=^2.0|%^ÎSO+|||||R|||20021202120235

OBX||SN|etSEV^^local^21024&2^^MIB/CEN||=^1.9|%^ÎSO+|||||R|||20021202120235

OBX||ST|NBP S^^local^8508-4&1^^LOINC|| |kpa^ÎSO+|||||R|||20021202120235



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

OBX||ST|NBP M^^local^8502-7&1^^LOINC|| |kpa^ÎSO+|||||R|||20021202120235

OBX||SN|SpO2^^local^2710-2&1^^LOINC||=^97|%^ÎSO+|||||R|||20021202120235

OBX||SN|PLS^^local^8889-8&1^^LOINC||=^83|/min^ÎSO+|||||R|||20021202120235

OBX||SN|etDES^^local^21012&2^^MIB/CEN||=^6.9|%^ÎSO+|||||R|||20021202120235

OBX||SN|iDES^^local^21096&2^^MIB/CEN||=^7.1|%^ÎSO+|||||R|||20021202120235

OBX||SN|iSEV^^local^21108&2^^MIB/CEN||=^2.1|%^ÎSO+|||||R|||20021202120235

OBX||SN|ART S^^local^8480-6&1^^LOINC||=^22.2|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|ART D^^local^8462-4&1^^LOINC||=^9.2|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|ART M^^local^8478-0&1^^LOINC||=^14.1|kpa^ÎSO+|||||R|||20021202120235

OBX||SN|mib PIP^^local^20885&1^^MIB/CEN||=^60|cmh2O^ÎSO+|||||R|||20021202120235

OBX||SN|mib MAP^^local^20720&1^^MIB/CEN||=^20|cmh2O^ÎSO+|||||R|||20021202120235

OBX||SN|mib PEEP^^local^20732&1^^MIB/CEN||=^0|cmh2O^ÎSO+|||||R|||20021202120235

OBX||SN|HR^^local^8867-4&1^^LOINC||=^83|/min^ÎSO+|||||R|||20021202120235

OBX||ST|%PACED^^local^&1^^MIB/CEN|| |%^ÎSO+|||||R|||20021202120235

OBX||ST|ARR^^local^03266&1^^MIB/CEN|| |/min^ÎSO+|||||R|||20021202120235

OBX||SN|PVC/min^^local^&1^^MIB/CEN||=^0|/min^ÎSO+|||||R|||20021202120235

OBX||SN|STI^^local^10121-2&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

OBX||SN|STII^^local^10122-0&1^^LOINC||=^0.01|mv^ÎSO+|||||R|||20021202120235

Sample Acknowledgment

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

MSA|AA|02110212073000458038|


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 messages follow the format below. The curved brackets ‘{‘ and ‘}’ indicate segments which may be repeated.

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.


MSH MSH Segment – Message Header







MSH Segment – Message Header

SeqHL7Item #

HL7 Dräger

Description Req Type Len Contents Req Len

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

2 00002 Encoding Charac-ters

R ST 4 “^~\&” R 4

3 00003 Sending Application R HD 227 "INFO_S-RC_DRAE-GER^0030E60000000001^EUI-64"

R 16

4 00004 Sending Facility RE HD 227 "Draeger" R 16

5 00005 Receiving Applica-tion

RE HD 227 Configurable in Infinity Gateway Configuration

R 227

6 00006 Receiving Facility RE HD 227 Configurable in Infinity Gateway Configuration

R 227

7 00007 Date/Time of Mes-sage

R DTM 24 YYYYMMD-DHHmmss+/-ZZZZ

O 12

8 00008 Security X ST 40 <not used>

9 00009 Message Type R MSG 15 “ORU ^R01^ORU_R01”

R 7

10 00010 Message Control ID R ST 199 A number orother identifieruniquelyidentifying themessage.

The receivingsystemechoes this ID

back to thesending systemin themessageacknowledgmentsegment(MSA).

R 20


12 00012 Version ID R VID 60 “2.6” R 8

13 00013 Sequence Number RE NM 15 <not used>


X ST 180 <not used>



15 00015 Accept Acknowl-edgment Type

R ID 2 "AL"

16 00016 Application Acknowledgment Type

R ID 2 "NE" R 2

17 00017 Country Code RE ID 3 <not used>

18 00692 Character Set RE ID 16 8859/1


RE CWE 705 "enÊnglishÎSO639"

20 Alternate Charac-ter Set Handling Scheme

X ID 20 <not used>

21 Message Profile Identifier

O EI 427 "IHE_PC-D_001ÎHE PCD^1.3.6.1.4.1.19376.1.6.1.1.1ÎSO"

R 427

22 Sending Responsi-ble Organization

X XON 567 <not used>

23 Receiving Respon-sible Organization


24 Sending Network Address

X HD 227 <not used>

25 Receiving Network Address

X HD 227 <not used>

MSH Segment – Message Header (Continued)

SeqHL7Item #

HL7 Dräger





Seq HL7 Dräger


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 a Patient Account number, as it is a repeat field. When the MRN is available, the format is: <MRN>^^^<Assigning Authority>^MRWhen the patient account number is available, it will appear in the format:

<Patient Account#>^^^^AN

R 12

4 Alternate Patient ID - PID

X CX 20 <not used>

5 Patient Name C XPN 250 "Last^First^Middle^^^^<Type>" Type is either U or L if the last name is not blank

R 250

6 Mother’s Maiden Name RE XPN 250 *"Last^First^Middle^^^^<Type>" Type is either U or L if the last name is not blank

R 250

7 Date/Time of Birth RE DTM 24 *YYYYMMDDhhmmss R 24

8 Administrative Sex RE IS 705 For Non IHE Compliant:*"Code^Text" Taken from ADT Configuration Information.

For IHE Compliant:

*"Code" Taken from ADT Configura-tion Information.

R 705

9 Patient Alias X XPN 250 <not used>

10 Race RE CWE 705 *"Code^Text" Taken from ADT Con-figuration Information.

R 705

11 Patient Address RE XAD 250 *"Street1^Street2^City^State^Zip Code^Country^M"

R 250

12 County Code RE IS 4 <not used>

13 Phone Number - Home RE XTN 250 <not used> R

14 Phone Number - Busi-ness

X XTN 250 <not used>

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-figuration Information.

R 705



17 Religion RE CWE 705 *"Code^Text" Taken from ADT Con-figuration Information.

R 705

18 Patient Account Num-ber

RE CX 705 <Patient Account #> R 12

19 SSN Number - Patient X ST 16 If IHE compliant, <not used>,

else "*National ID"

R 16

20 Driver's License Num-ber - Patient

RE DLN 25 <not used>

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 Time

RE DTM 24 <not used>

30 Patient Death Indicator

RE ID 1 <not used>

31 Identity Unknown Indi-cator

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>


Seq HL7 Dräger



NOTE

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


Seq HL7Item #

HL7 Dräger


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

2 00132 Patient Class R IS 1 *Patient Class R 1

3 00133 Assigned Patient Loca-tion

RE PL 80 <Care Unit Label>^^<Bed Label>^<Hospi-tal/Facility>


X IS 2 <not used> R 18

5 00135 Preadmit Num-ber

X CX 250 <not used>


X PL 80 <not used>

7 00137 Attending Doc-tor

X XCN 250 If IHE Compliant <not used>, other-wise *"^Last Name^First Name^Middle Name^Suffic^Pre-fix^Degree"

O 250

8 00138 Referring Doc-tor

X XCN 250 If IHE cCompliant <Nnot used>, oth-erwise *"^Last Name^First Name^Middle Name^Suffic^Pre-fix^Degree"

O 250


X XCN 250 If IHE Compliant <not used>, other-wise *"^Last Name^First Name^Middle Name^Suffix^Pre-fix^Degree"

O 250

10 00140 Hospital Ser-vice

X IS 3 <not used>




X PL 80 <not used>


X IS 2 <not used>


X IS 2 <not used>

14 00144 Admit Source X IS 6 <not used>


X IS 2 <not used>

16 00146 VIP Indicator X IS 2 <not used>

17 00147 Admitting Doc-tor

X XCN 250 If IHE Compliant <not used>, oth-erwise *"^Last Name^First Name^Middle Name^Suffic^Pre-fix^Degree"

O 250

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>


X IS 2 <not used>

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-tive Date

X DT 8 <not used>


X NM 12 <not used>

27 00157 Contract Period X NM 3 <not used>

28 00158 Interest Code X IS 2 <not used>


X IS 4 <not used>


X DT 8 <not used>


X IS 10 <not used>


X NM 12 <not used>


Seq HL7Item #

HL7 Dräger





X NM 12 <not used>


X IS 1 <not used>


X DT 8 <not used>

36 00166 Discharge Dis-position

X IS 3 <not used>


X DLD 47 <not used>

38 00168 Diet Type X CWE 705 <not used>

39 00169 Servicing Facil-ity

X IS 2 <not used>

40 00170 Bed Status X IS 1 <not used>

41 00171 Account Status X IS 2 <not used>

42 00172 Pending Loca-tion

X PL 80 <not used>

43 00173 Prior Tempo-rary Location

X PL 80 <not used>


RE DTM 24 YYYYMMD-Dhhmmss

R 24


X DTM 24 <not used>


X NM 12 <not used>

47 00177 Total Charges X NM 12 <not used>

48 00178 Total Adjust-ments

X NM 12 <not used>

49 00179 Total Payments X NM 12 <not used>


X CX 250 <not used>

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>.


Seq HL7Item #

HL7 Dräger





Seq HL7 Item #

HL7 Dräger


1 00104 Set ID OBR R SI 4 Observation Set Number R 4

2 00105 Placer Order Num-ber

C EI 427 <not used>

3 00106 Filler Order Num-ber

R EI 427 <OrderNumber>^ <Order Application> ^0030E60000000001^EUI-64

R 427

4 00107 Universal Service Identifier

R CWE 705 "182777000^monitoring of patient^SCT"

R 40

5 00108 Priority - OBR X ID 2 <not used>

6 00109 Requested Date/Time

X DTM 24 <not used>

7 00110 Observation Date/Time

RE DTM 24 YYYYMMDDhhmmss R 24

8 00111 Observation End Date / Time


9 00112 Collection Volume X CQ 722 <not used>

10 00113 Collection Identi-fier

R2 XCN 3220 <not used>




Seq HL7Item #

HL7 Dräger


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 value reported

by the device is numeric, otherwise

“ST” (string).

R 2


R CWE 705 For IHE Compliant Setting: <CF_Code10>^<Refer-ence ID>^MDC For IHE non-com-pliant setting: <CF_Code10>^<Reference ID>^MDC^<Draeger Label>^^Local

R 20

4 00004 Observation Sub-

R ST 20 <Device Identifier>.<VMD_In-stance>.<Channel_In-stance>.<CF_Code10>.<Metric_Instance>

R

5 00005 OID

bservation Value

C Varies 99999 See Observation 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 Range

CE ST 60 <not used>

8 00008 Abnormal Flags CE IS 5 <not used>

9 00009 Probability X NM 5 <not used>


CE ID 2 <not used>


R ID 1 “R”

12 00012 Effective Date of Reference Range

X DTM 24 <not used>


X ST 20 <not used>



Observation Value

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

ACK - Acknowledgment

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



RE DTM 24 YYYYMMDDhhmmss

15 00015 Producer’s ID RE CWE 705 <not used>


RE XCN 3220 <not used>


RE CWE 705 <not used>

18 00692 Equipment Instance Identi-fier

RE EI 427 <UniqueID>^<model>^<manufac-turer url>^<universal id type>

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 the Analysis

CE DTM 24 <not used>

20 Observation Site


Value Type Observation Value Filed Format Comments

ST <value> See Appendix C for special value strings

NM <numeric value>

Segment Description




Seq HL7Item #

HL7 Dräger





HL7 HL7 Dräger


1 00001 Field Separator R ST 1 Recommended value is “|”

R 1


R ST 4 Four characters in the following order: the component separator, the repetition separator, the escape character, and the subcomponent separator. Recommended values are “^~\&”.

R 4


O HD 180 A string identifying the sending application.

O 16

4 00004 Sending Facility O HD 180 <not used>


O HD 180 <not used>

6 00006 Receiving Facility O HD 180 <not used>


O TS 26 YYYYMMDDHHmm

O 12





R 20


12 00012 Version ID R ID 8 “2.5” R 8


O NM 15 <not used>

14 00014 Continuation Pointe

O ST 180 <not used>




O ID 2 <not used>


O ID 2 <not used>




O CE 60 <not used>


HL7 HL7 Dräger






HL7 HL7 Dräger



R ID 2 See Acknowledgment Codes

R 1



R 4


O 80


O NM 15 <not used>


B ID 1 <not used>


Value Description









Sample ORU Message

MSH|^~\&|INFO_SRC_DRAEGER^0030E60000000001ÊUI-64|Draeger|NUR|Rec-Fac|20180926150437-0500||ORU^R01ÔRU_R01|18092615043700515606|P|2.6|||AL|NE||8859/1|enÊnglishÎSO639||IHE_PCD_001ÎHE PCD^1.3.6.1.4.1.19376.1.6.1.1.1ÎSO

PID|||111-11-1111^^^^MR||Smith^Wally^L.^^^^L|Joose^Judy^K^^^^L|19420430142000|M^Male||UÛnknown|13 Beer St.^#123^Beersteinville^VA^12345-6785ÛSA^M||||spa^Spanish|M^Married|JEW^Jewish|1001|012-34-5678|||N^Not Hispanic or Latino||||||USAÛnited States

PV1||E|CU1^^GOWDA12^BGS||||^Munster^Florence^SÎI^Mr.^M.D.||||||||||^Carr^Mary^JonesÎI^Mrs.^M.D.|||||||||||||||||||||||||||19980430043020

OBR|1||0826145634032227^DSUBAND^0030E60000000001ÊUI-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^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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_DIM_MILLI_VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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_DIM_MILLI_VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.drae-ger.com/^DNS



OBX|10|NM|131902^MDC_ECG_AMPL_ST_AVR^MDC^STaVR^^local|2.1.1.131902001|0.0|266418^MDC_DIM_MILLI_-VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|11|NM|131903^MDC_ECG_AMPL_ST_AVL^MDC^STaVL^^local|2.1.1.131903001|0.0|266418^MDC_DIM_MILLI_-VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|12|NM|131904^MDC_ECG_AMPL_ST_AVF^MDC^STaVF^^local|2.1.1.131904001|0.0|266418^MDC_DIM_MILLI_-VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|14|NM|192806^MDC_ECG_AMPL_ST_VM^MDC^STVM^^local|2.1.1.192806001|0.0|266418^MDC_DIM_MILLI_VOLT^MDC^mv^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|16|NM|148066^MDC_ECG_V_P_C_RATE^MDC^PVC/min^^local|2.1.2.148066001|0.0|264864^MDC_DIM_BEAT_PER_MIN^MDC^/min^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|17|ST|148496^MDC_ECG_ARRHY^MDCÂRR^^local|2.1.2.148496001| |262656^MDC_DIM_DIM-LESS^MDC^^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|18|NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC^PLS^^local|2.13.1.149530001|86.0|264864^MDC_DIM_BEAT_PER_MIN^MDC^/min^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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)^ÎSO+|||||R|||20180923145607||||0060E9EEBCÎACS^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)^ÎSO+|||||R|||20180923145607||||0060E9EEBCÎACS^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)^ÎSO+|||||R|||20180923145607||||0060E9EEBCÎACS^http://www.draeger.com/^DNS



OBX|24|ST|159764^MDC_CONC_HB_ART^MDC^Hgb^^local|2.31.1.159764001| |264256^MDC_DIM_G_PER_DL^MDC^g/dL^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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)^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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)^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^%^ÎSO+|||||R|||20180923145607||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|30|NM|160280^MDC_PULS_OXIM_CONC_HB_O2_ART_CALC^MDC^SpOC^^local|2.39.1.160280001|33.0|268562^MDC_DIM_-MILLI_L_PER_DL^MDC^mL/dL^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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|262688^MDC_DIM_PER-CENT^MDC^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|32|NM|160288^MDC_PULS_OXIM_HB_MET_ART^MDC^SpMet^^local|2.39.1.160288001|0.7|262688^MDC_DIM_PER-CENT^MDC^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|33|NM|192790^MDC_PULS_OXIM_PVI^MDC^PVI^^local|2.39.1.192790001|1.0|262688^MDC_DIM_PERCENT^MDC^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.drae-ger.com/^DNS

OBX|34|NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC^PLS*^^local|2.41.1.149530001|50.0|264864^MDC_DIM_BEAT_PER_MIN^MDC^/min^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^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|262688^MDC_DIM_PER-CENT^MDC^%^ÎSO+|||||R|||20180926150437||||0060E9EEBCÎACS^http://www.draeger.com/^DNS


Sample Acknowledgment

MSH|^~\&|NUR||Infinity|MEDAT-18|20180926150437||ACK^R01|99011716090716963683|P|2.3

MSA|AA|18092615043700515606|[999-99-9999]Message Delivered


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.

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

Segment Description


QRD Acknowledgment Codes

QRF QRF - Query Filter




HL7 HL7 Dräger


1 00001 Field Sep-arator

R ST 1 The separator 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 “|”.

R 1


R ST 4 The four char-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 “^~\&”.

R 4


O HD 180 <not used>


O HD 180 <not used>


O HD 180 <not used>


O HD 180 <not used>


O TS 26 YYYYMMD-DHHmmss

O 12


9 00009 Message Type

R CM 7 “QRY^R02” R 7




R ST 20 A number or other identifier that uniquely identifies the message. The Infinity Gateway echoes this ID back to the sending system in the Message acknowledgment segment (MSA).

R 20

11 00011 Processing ID

R PT 3 “P” R 3

12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>

14 00014 Continua-tion Pointer

O ST 180 <not used>

15 00015 Accept Acknowledg-ment Type

O ID 2 <not used>

16 00016 Application Acknowledg-ment

O ID 2 <not used>

17 00017 Country Code

O ID 2 <not used>

18 00692 Character Set

O ID 6 <not used>


O CE 60 <not used>


HL7 HL7 Dräger




QRD Segment - Original Type Query Definition

HL7 HL7 Dräger


1 00025 Query Date/Time

R TS 26 YYYYMMD-Dhhmmss

O 26

2 00026 Query Format Code

R ID 1 “R” R 1

3 00027 Query Priority R ID 1 “I” R 1

4 00028 Query ID R ST 10 This field should contain a unique identi-fier for the query. It is returned intact by the Infinity application.

R 10

5 00029 Deferred Response Type

O ID 1 <not used>

6 00030 Deferred Response Date/Time

O TS 26 <not used>

7 00031 Quantity Lim-ited Request

R CQ 10 <not used>

8 00032 Who Subject Filter

R XCN 60 <not used>

9 00033 What Subject Filter

R CE 60 “RES” R 60

10 00034 What Depart-ment Data Code

R CE 60 <not used>

11 00035 What Data Code Value Qual.

O ST 20 <not used>

12 00036 Query Results Level

O ID 1 <not used>



QRF - Query Filter

Hl7 HL7 Dräger


1 00037 Where Subject Filter

R ST 20 “MONITOR” 20

2 00038 When Data Start Date/Time

O TS 26 <not used> R

3 00039 When Data End Date/Time

O TS 26 <not used>

4 00040 What User Qualifier

O ST 60 <not used>

5 00041 Other QRY Subject Filter

O ST 60 Specifies 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.

999

6 00042 Which Date/Time Qualifier

O ID 12 <not used> R

7 00043 Which Date/Time Sta-tus Qualifier

O ID 12 <not used>

8 00044 Date/Time Selection Qual-ifier

O ID 12 <not used>

9 00694 When Quan-tity/Timing Qualifier

O TQ 60 <not used>



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


MSA MSA Segment - Message Acknowledgment

QRD Acknowledgment Codes

QRF QRF Segment – Query Filter




{[OBX]} OBX Segment - Observation/Result


Seq HL7 Item #

HL7 Dräger


1 00001 Field Separa-tor

R ST 1 “|” R 1


R ST 4 “^~\&” R 4


O HD 180 “INFINITY” O 1

4 00004 Sending Facil-ity

O HD 180 <not used>


O HD 180 The string identifying the Send-ing Applica-tion in the of the QRY message being acknowl-edged.

O


O HD 180 <not used>




O TS 26 YYYYM-MDDhhmmss

O 12



R CM 7 “ORF^R04” R 7


R ST 20 A number or other identifier that uniquely identifies the mes-sage.

R 20


12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>


O ST 180 <not used>

15 00015 Acknowledg-ment Type

O ID 2 "AL" R 2


O ID 2 "NE" R 2



19 00693 Principal Lan-guage Of Message

O CE 60 <not used>


Seq HL7 Item #

HL7 Dräger




MSA Segment - Message Acknowledgment

Seq HL7 Item #8

HL Dräger


1 00018 Acknowledg-ment Code

R ID 2 See Acknowledg-ment Codes

R 1


R ST 20 The Mes-sage Control ID of the message it is acknowledg-ing.

R 4


O 80

4 00021 Expected Sequence Num-ber

O NM 15 <not used>

5 00022 Delayed Acknowledg-ment Type

B ID 1 <not used>





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.

Value Description


Enhanced mode: Application acknowledgment: Accept


Enhanced mode: Application acknowledgment: Error


Enhanced mode: Application acknowledgment: Reject




Seq HL7 Item #

HL7 Dräger



O SI 4 <not used>


O CX 20 <not used>


R CX 20 See Patient Identifiers


O CX 20 <not used>

5 00108 Patient Name R XPN 48 See Patient Name.

O 32


O XPN 48 <not used>


O IS 26 <not used>

8 00111 Sex O IS 1 <not used>


10 00113 Race O IS 26 <not used>

11 00114 Patient Address

O XAD 1 <not used>



O XTN 1 <not used>



15 00118 Primary Lan-guage

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 Num-ber

O CX 60 See Patient Identifiers

O 12


O ST 1 <not used>



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).

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”

20 00123 Driver's License Num-ber - Patient

O CM 25 <not used>

21 00124 Mother's Identi-fier

O CX 20 <not used>

22 00125 Ethnic Group O IS 3 <not used>



O ID 2 <not used>



27 00130 Veterans Mili-tary Status

O CE 60 <not used>

28 00131 Nationality O CE 80 <not used>


O TS 26 <not used>


O ID 1 <not used>

Interpret Patient ID as Setting

Field 3 contents Field 18 contents

MRN <Patient ID> blank

Patient Account # <Patient ID> <Patient ID>


Seq HL7 Item #

HL7 Dräger





HL7 Dräger



2 00132 Patient Class R IS 1 <not used>


O PL 80 In the format: <Care Unit Label>^^<Bed Label>. The loca-tion is defined at the device.

R 18


O IS 2 <not used>

5 00135 Preadmit Number

O CX 20 <not used>


O PL 80 <not used>

7 00137 Attending Doctor

O XCN 60 <not used>

8 00138 Referring Doctor

O XCN 60 <not used>


O XCN 60 <not used>


O IS 3 <not used>


O PL 80 <not used>


O IS 2 <not used>


O IS 2 <not used>



O IS 2 <not used>


17 00147 Admitting Doctor

O XCN 60 <not used>



20 00150 Financial Class

O CM 50 <not used>




O IS 2 <not used>

22 00152 Courtesy Code

O IS 2 <not used>


24 00154 Contract Code

O IS 2 <not used>


O DT 8 <not used>


O NM 12 <not used>

27 00157 Contract Period

O NM 3 <not used>



O IS 1 <not used>


O DT 8 <not used>


O IS 10 <not used>


O NM 12 <not used>


O NM 12 <not used>

34 00164 Delete Account Indi-cator

O IS 1 <not used>


O DT 8 <not used>


O IS 3 <not used>


O CM 25 <not used>


39 00169 Servicing Facility

O IS 2 <not used>


HL7 Dräger





41 00171 Account Sta-tus

O IS 2 <not used>

42 00172 Pending Location

O PL 80 <not used>


O PL 80 <not used>


O TS 26 <not used>


O TS 26 <not used>

46 00176 Current Patient Bal-ance

O NM 12 <not used>



O NM 12 <not used>

49 00178 Total Pay-ments

O NM 12 <not used>


O CX 20 <not used>


52 01224 Other Health-care Provider

O XCN 60 <not used>


HL7 Dräger





Seq HL7 Item #

HL7 Dräger



2 00216 Placer Order Num-ber

C EI 75 <not used>

3 00217 Filler Order Num-ber +

C EI 75 <not used>

4 00238 Universal Service ID

R CE 200 <not used>



B TS 26 <not used>


C TS 26 The date the observation was measured on the device. Format is YYYYMMD-DHHmmss.

R 14


O TS 26 <not used>

9 00243 Collection Volume O CQ 20 <not used>

10 00244 Collector Identifier O XCN 60 <not used>


O ID 1 <not used>


13 00247 Relevant Clinical Info

O ST 300 <not used>


O TS 26 <not used>

15 00249 Specimen Source O CM 300 <not used>

16 00226 Ordering Provider O XCN 80 <not used>


O XTN 40 <not used>







22 00255 Results Rpt/Status Chng - Date/Time +

O TS 26 <not used>

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 + 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>



O ID 20 <not used>

31 00263 Reason for Study O CE 300 <not used>


O CM 200 <not used>


O CM 200 <not used>


35 00267 Transcriptionist + O CM 200 <not used>


O TS 26 <not used>


O NM 4 <not used>

38 01029 Transport Logis-tics of Collected Sample

O CE 60 <not used>

39 01030 Collector's Com-ment

O CE 200 <not used>

40 01031 Transport Arrange-ment Responsibil-ity

O CE 60 <not used>


O ID 30 <not used>

42 01033 Escort Required O ID 1 <not used>

43 01034 Planned Patient Transport Com-ment

O CE 200 <not used>


Seq HL7 Item #

HL7 Dräger





Seq HL7 Item #

HL7 Dräger


1 00569 Set ID – OBX

O SI 10 <not used>

2 00570 Value Type C ID 2 “SN” (structured numeric) iIf the parameter value being reported by the device is numeric, other-wise “ST”(string).

R 2


R CE 590 See Observa-tion Identifier

R

4 00572 Observation Sub-Identi-fier

C ST 20 <not used>


C * 65536

See Observa-tion Value

R 30

6 00574 Units O CE 60 Uniquely identi-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.

O 30


O ST 10 <not used>


O ID 5 <not used>



ID 2 <not used>

11 00579 Observation Result Sta-tus

R ID 1 “R” R 1





<identifier1^^local^<<identifier2>&<instance >>^^<coding system >

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.

12 00580 Date Last Observation Normal Val-ues

O TS 26 <not used>


O ST 20 <not used>

14 00582 Date/Time of the Observa-tion


O 12

15 00583 Producer's ID

O CE 60 <not used>


O XCN 80 <not used>


O CE 60 <not used>

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


Seq HL7 Item #

HL7 Dräger




Observation Value

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

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^^^ÂN||Data^Simulated^Patient|||||||||||||8888

PV1|||CU50^^Bed2

OBR|||||||20170425185117

OBX||SN|HR^^local^8867-4&1^^LOINC||=^84|/min^ÎSO+|||||R|||20170425185116

OBX||SN|%PACED^^local^ &1^^LOINC||=^0|%^ÎSO+|||||R|||20170425185116

OBX||ST|ARR^^local^ &1^^LOINC|| |^ÎSO+|||||R|||20170425185116

OBX||SN|PVC/min^^local^ &1^^LOINC||=^0|/min^ÎSO+|||||R|||20170425185116

OBX||SN|STI^^local^10121-2&1^^LOINC||=^0.2|mm^ÎSO+|||||R|||20170425185116

OBX||SN|STII^^local^10122-0&1^^LOINC||=^0.3|mm^ÎSO+|||||R|||20170425185116

OBX||SN|STIII^^local^10123-8&1^^LOINC||=^0.2|mm^ÎSO+|||||R|||20170425185116


ST <value> See Appendix C: Special Dis-play Values for special value strings



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.

For the 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).

NOTE

The solicited and unsolicited ADT Interfaces are mutually exclusive.

NOTE

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



Field Usage by Platform

Data Imported

Destination Monitor HL7 Segment

Application Screen

Modular Monitors

Configured Monitors

Telemetry

Medical Record Number

Admit Screen Sometimes Sometimes Sometimes See Patient Identifier

Visit Num-ber

Admit Screen Sometimes Sometimes Sometimes See Patient Identifier

Patient Name

Admit Screen Yes Yes Yes See Patient Name

Birth Date/Time

Admit Screen Yes Yes Yes See Date/Time of Birth

Admit Date Admit Screen Yes Yes Yes See Admit Date/Time

Attending Doctor

Admit Screen Yes Yes Yes See Attend-ing Doctor

Height Admit Screen Yes Yes Yes See


Weight Admit Screen Yes Yes Yes See


Sex ECG Report Setup

Yes No No See Sex

Race ECG Report Setup

Yes No No See Race

Religion N/A No No No See Religion

Prior MRN N/A No No No See Prior Internal ID

Prior Visit Number

N/A No No No See Prior Patient Account Num-ber

Marital Status

N/A No No No See Marital Status

Nationality N/A No No No See National-ity

Primary Language

N/A No No No Refer to ADT-Config Tool



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.

Patient Address

N/A No No No See Patient Address

Admitting Doctor

N/A No No No See Admitting Doctor

Consulting Doctor

N/A No No No See Consult-ing Doctor

Referring Doctor

N/A No No No See Referring Doctor

National ID / Social Security

N/A No No No See National ID/ Social Security Num-ber

Patient Location

N/A No No No See Patient Location

Prior Loca-tion

N/A No No No See Prior Patient Loca-tion

Discharge Date

N/A No No No See Dis-charge Date

Event Date N/A No No No See Event Occurred

Ethnic Group

N/A No No No See Ethnic Group

Field Usage by Platform (Continued)

Data Imported


Application Screen

Modular Monitors

Configured Monitors

Telemetry



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 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

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.

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



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.



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.

Any other segments received will be ignored.

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

Segment Description


[EVN] EVN Segment - Event Type


{[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 Informa-tion





Seq HL7Item #

HL7 Dräger


1 00001 Field Sep-arator

R ST 1 The separator 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 “|”.

R 1


R ST 4 Four characters in the following order:

the component sep-arator, the repeti-tion separator, the escape character, and the subcompo-nent separator. Recommended val-ues are “^~\&”.

R 4


O HD 180 Text identifying the sending applica-tion.


O HD 180 <not used>


O HD 180 <not used>


O HD 180 <not used>


O TS 26 <not used>





R CM 7 This field has the 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

R 7


R ST 20 A number or other identifier that uniquely identifies the message.

R 20


R PT 3 “P” R 3

12 00012 Version ID R ID 8 “2.2” ,“2.3” or “2.3.1”

R 8


O NM 15 <not used>

14 00014 Continua-tion Pointer

O ST 180 <not used>


O ID 2 <not used>

16 00016 Application Acknowl-edgment

O ID 2 <not used>


O ID 2 <not used>


O ID 6 <not used>


O CE 60 <not used>


Seq HL7Item #

HL7 Dräger




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]

EVN Segment - Event Type

Seq HL7Item #

HL7 Dräger

Descrip-tion

Req Type Len Contents Req Len

1 00099 Event Type Code

B ID 3 This field has been retained for back-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.

R 3

2 00100 Recorded Date/Time

R TS 26 <not used>

3 00101 Date/Time Planned Event

O TS 26 <not used>

4 00102 Event Reason Code

O IS 3 <not used>

5 00103 Operator ID

O XCN 60 <not used>

6 00278 Event Occurred

O TS 26 See Event Occurred O 14




Seq HL7Item #

HL7 Dräger



O SI 40 <not used>

2 00105 Patient ID (Exter-nal ID)

O CX 20 <not used>

3 00106 Patient ID R CX 200 See Patient Identifier

R/O


O CX 20 <not used>

5 00108 Patient Name R XPN 48 See Patient Name

O


O XPN 48 <Last>^<First>^<Middle>


O TS 26 See Date/Time of Birth

O 26

8 00111 Sex O IS 1 See Sex O 1


10 00113 Race O IS 1 See Race O 26

11 00114 Patient Address O XAD 106 See Patient Address

O

12 00115 Country Code B IS 4 <not used>


O XTN 40 <not used>


O XTN 40 <not used>


O CE 60 Refer to ADT-Config Tool

O 4

16 00119 Marital Status O IS 1 See Marital Sta-tus

O 1

17 00120 Religion O IS 3 See Religion O 4


O CX 20 See Patient Identifier

R/O 20


O ST 16 See National ID/ Social Security Number

O 16



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 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, 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)

20 00123 Driver’s License Number - Patient

O CM 25 <not used>


O CX 20 <not used>

22 00125 Ethnic Group O IS 3 See Ethnic Group

O 4



O ID 2 <not used>




O CE 60 <not used>

28 00131 Nationality O CE 80 See Nationality O 4


O TS 26 <not used>


O ID 1 <not used>


Seq HL7Item #

HL7 Dräger




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:


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.

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.

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.

In Field On Device

F Female

M Male

All other Unknown



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.

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:

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(HIS code)

Infinity Code

On Device

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

2076-8 7 Native Hawaiian or Other Pacific Islander

All others 1 Unknown

Component Max Length

street1 40

street2 40

city 25

state/province 25

postal code 10

country 15

address type 1

In Field On Device

A Separated

B Unmarried



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.

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.

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

HIS Code Ethnic Group

H Hispanic or Latino

N Not Hispanic or Latino

All other Unknown

In Field On Device



AL1 Segment - Patient Allergy

Allergy Types

The following table lists the allergy types accepted by HL7:

Allergies

This field has the format <Allergy Code>^<Allergy Description>

NOTE

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


Seq HL7Item #

HL7 Dräger


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 Code/Mne-monic/Descrip-tion

R CE 60 See Allergies R 44

4 00206 Allergy Severity O IS 2 ‘SV’ severe

‘MO’ moderate

‘MI’ mild

O 2

5 00207 Allergy Reaction O ST 15 A string describing the reaction that the patient has when exposed to the allergy

O 15

6 00208 Identification Date

O DT 8 <not used>

Code Description

DA Drug Allergy

FA Food Allergy

MA Miscellaneous Allergy

MC Miscellaneous Contraindica-tion



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 mes-sage, otherwise the associated insurance informa-tion that is not included will be deleted from the patient record



IN1 Segment - Patient Insurance

Seq HL7Item #

HL7 Dräger


1 00203 Set ID - IN1 R SI 4 <not used>

2 00368 Insurance Plan ID

R CE 60 A unique identifier for the insurance plan

R 20

3 00428 Insurance Com-pany ID

R CX 59 <not used>

4 00429 Insurance Com-pany Name

O XON 130 The name of the insurance com-pany

R 40

5 00430 Insurance Com-pany Address

O XAD 106 See Address O 172

6 00431 Insurance Co. Contact Person

O XPN 48 <not used>

7 00432 Insurance Co Phone Number

O XTN 40 The string contact number for the insurance com-pany.

O 25

8 00433 Group Number O ST 12 Identifies the group within the insurance plan

O 12

9 00434 Group Name O XON 130 The name of the group within the insurance plan

O 40

10 00435 Insured’s Group Emp ID

O CX 12 <not used>

11 00436 Insured’s Group Emp Name

O XON 130 <not used>

12 00437 Plan Effective Date

O DT 8 <not used>

13 00438 Plan Expiration Date

O DT 8 <not used>

14 00439 Authorization Information

O CM 55 <not used>

15 00440 Plan Type O IS 3 <not used>

16 00441 Name Of Insured

O XPN 48 See Name of Insured

O 72

17 00442 Insured’s Rela-tionship To Patient

O IS 2 See Appendix J: Relationship table

O 3



18 00443 Insured’s Date Of Birth

O TS 26 Date of birth of the primary insurance holder in the for-mat

YYYYMMDD

O 8

19 00444 Insured’s Address


20 00445 Assignment Of Benefits

O IS 2 <not used>

21 00446 Coordination Of Benefits

O IS 2 <not used>

22 00447 Coord Of Ben. Priority

O ST 2 <not used>

23 00448 Notice Of Admission Flag

O ID 2 <not used>

24 00449 Notice Of Admission Date

O DT 8 <not used>

25 00450 Report Of Eligi-bility Flag

O ID 2 <not used>

26 00451 Report Of Eligi-bility Date

O DT 8 <not used>

27 00452 Release Infor-mation Code

O IS 2 <not used>

28 00453 Pre-Admit Cert (PAC)

O ST 15 <not used>

29 00454 Verification Date/Time

O TS 26 <not used>

30 00455 Verification By O XCN 60 <not used>

31 00456 Type Of Agree-ment Code

O IS 2 <not used>

32 00457 Billing Status O IS 2 <not used>

33 00458 Lifetime Reserve Days

O NM 4 <not used>

34 00459 Delay Before L.R. Day

O NM 4 <not used>

35 00460 Company Plan Code

O IS 8 <not used>

36 00461 Policy Number O ST 15 The policy number O 15

37 00462 Policy Deduct-ible

O CP 12 <not used>

IN1 Segment - Patient Insurance (Continued)

Seq HL7Item #

HL7 Dräger




Address

Repetition is not supported for this field, and only the first instance will be used.

<street1>^<street2>^<city>^<state/province>^<postal code>^<country>


38 00463 Policy Limit - Amount

B CP 12 <not used>

39 00464 Policy Limit - Days

O NM 4 <not used>

40 00465 Room Rate - Semi-Private

B CP 12 <not used>

41 00466 Room Rate - Pri-vate

B CP 12 <not used>

42 00467 Insured’s Employment Status

O CE 60 <not used>

43 00468 Insured’s Sex O IS 1 <not used>

44 00469 Insured’s Employer Address

O XAD 106 <not used>

45 00470 Verification Sta-tus

O ST 2 <not used>

46 00471 Prior Insurance Plan ID

O IS 8 <not used>

47 01227 Coverage Type O IS 3 <not used>

48 00753 Handicap O IS 2 <not used>

49 01230 Insured’s ID Number

O CX 12 <not used>


street1 40

street2 40

city 25

state/province 25

postal code 10

country 15


Seq HL7Item #

HL7 Dräger




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.

DG1 Segment – Patient Diagnosis

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.


Last 30

First 20

Middle 20

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


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 is used.




street1 40

street2 40

city 25

state/province 25

postal code 10

country 15



DG1 Segment - Patient Diagnostics

Seq HL7Item #

HL7 Dräger


1 00375 Set ID - DG1 R SI 4 <not used>

2 00376 Diagnosis Coding Method

(B) R ID 2 <not used>

3 00377 Diagnosis Code

O CE 60 See R 51

4 00378 Diagnosis Description

B ST 40 The description of the diagnosis. Note that this field is only used if compo-nent 2 of field 3 above is not populated

O 42

5 00379 Diagnosis Date/Time

O TS 26 <not used>

6 00380 Diagnosis Type

R IS 2 Valid values are:

‘A’: Admitting

‘W’: Working (default)

‘F’: Final

O 1

7 00381 Major Diag-nostic Cate-gory

B CE 60 <not used>

8 00382 Diagnostic Related Group

B IS 4 <not used> O 4

9 00383 DRG Approval Indi-cator

B ID 2 <not used>

10 00384 DRG Grouper Review Code

B IS 2 <not used>

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>



14 00388 Grouper Ver-sion And Type

B ST 4 <not used>

15 00389 Diagnosis Priority

B NM 2 <not used>

16 00390 Diagnosing Clinician

O XCN 60 <not used>

17 00766 Diagnosis Classification

O IS 3 <not used>

18 00767 Confidential Indicator

O ID 1 <not used>

19 00768 Attestation Date/Time

O TS 26 <not used>

NK1 Segment - Next of Kin

Seq HL7Item #

HL7 Dräger


1 00190 Set ID – NK1 R SI 4 <not used>

2 00191 Name O XPN 48 See *Patient Class

O

3 00192 Relationship O CE 60 See Appendix J: Relationship table

O 3

4 00193 Address O XAD 106 See Address O 106

5 00194 Phone Num-ber

O XTN 40 A string contact number.

O 25

6 00195 Business Phone Num-ber

O XTN 40 A string contact number.

O 25

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 Code/Class

O CM 20 <not used>

DG1 Segment - Patient Diagnostics (Continued)

Seq HL7Item #

HL7 Dräger




12 00201 Employee Number

O CX 20 <not used>

13 00202 Organiza-tion Name

O XON 60 <not used>

14 00119 Marital Sta-tus

O IS 2 <not used>



O TS 26 <not used>

17 00755 Living Dependency

O IS 2 <not used>


O IS 2 <not used>



O CE 60 <not used>

21 00742 Living Arrangement

O IS 2 <not used>

22 00743 Publicity Indicator

O IS 1 <not used>

23 00744 Protection Indicator

O ID 1 <not used>

24 00745 Student Indi-cator

O IS 2 <not used>



O XPN 48 <not used>



29 00747 Contact Reason

O CE 80 <not used>

30 00748 Contact Per-son’s Name

O XPN 48 <not used>

NK1 Segment - Next of Kin (Continued)

Seq HL7Item #

HL7 Dräger




31 00749 Contact Per-son’s Tele-phone Number

O XTN 40 <not used>

32 00750 Contact Per-son’s Address


33 00751 Identifiers O CX 32 <not used>

34 00752 Job Status O IS 2 <not used>



37 00754 Contact Per-son’s Social Security Number

O ST 16 <not used>


Seq HL7Item #

HL7 Dräger





Seq HL7Item #

HL7 Dräger



2 00132 Patient Class R IS 1 *Patient Class


O PL 80 See Patient Location

4 00134 Admission Type O IS 2 <not used>

5 00135 Preadmit Number O CX 20 <not used>


O PL 80 See Prior Patient Location

7 00137 Attending Doctor O XCN 60 See Attend-ing Doctor

O

8 00138 Referring Doctor O XCN 60 See Refer-ring Doctor

9 00139 Consulting Doctor O XCN 60 See Con-sulting Doc-tor

10 00140 Hospital Service O IS 3 <not used>

11 00141 Temporary Loca-tion

O PL 80 <not used>


O IS 2 <not used>

13 00143 Readmission Indi-cator

O IS 2 <not used>


15 00145 Ambulatory Status O IS 2 <not used>


17 00147 Admitting Doctor O XCN 60 See Admit-ting Doctor




21 00151 Charge Price Indi-cator

O IS 2 <not used>







O DT 8 <not used>

26 00156 Contract Amount O NM 12 <not used>




O IS 1 <not used>


O DT 8 <not used>


O IS 10 <not used>


O NM 12 <not used>

33 00163 Bad Debt Recov-ery Amount

O NM 12 <not used>


O IS 1 <not used>


O DT 8 <not used>

36 00166 Discharge Dispo-sition

O IS 3 <not used>


O CM 25 <not used>


39 00169 Servicing Facility O IS 2 <not used>



42 00172 Pending Location O PL 80 <not used>


O PL 80 <not used>

44 00174 Admit Date/Time O TS 26 See Admit Date/Time

O 26


Seq HL7Item #

HL7 Dräger




Patient Location

This field contains the location of the patient. It is in the format

<Care Unit>^<Room>^<Bed>

Prior Patient Location

This field contains the location of the patient to be transferred.


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.


O TS 26 See Dis-charge Date

O 26


O NM 12 <not used>


48 00178 Total Adjustments O NM 12 <not used>


50 00180 Alternate Visit ID O CX 20 <not used>



O XCN 60 <not used>


Seq HL7Item #

HL7 Dräger




Admitting Doctor

Contains the admitting physician information in the format:


Refer to Attending Doctor for details on field lengths and display formats

Consulting Doctor

Contains the consulting physician information in the format:


Refer to Attending Doctor for details on field lengths and display formats.

Referring Doctor

Contains the referring physician information in the format:


Refer to Attending Doctor for details on field lengths and display formats.

Admit Date/Time

Contains the admission date in the format:


The date portion of this field will be entered in the Admit Date field of the Patient Admit screen on the device.

Discharge Date

Contains the date that the patient was discharged. It is in the format:




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.


MRG Segment - Merge Patient Information

Seq HL7Item #

HL7 Dräger


1 00211 Prior Patient ID - Internal

R CX 20 See Prior Internal ID

20

2 00212 Prior Alternate Patient ID

O CX 16 <not used>

3 00213 Prior Patient Account Number

O CX 20 See Prior Patient Account Number

20

4 00214 Prior Patient ID - External

O CX 16 <not used>

5 01279 Prior Visit Number O CX 15 <not used>

6 01280 Prior Alternate Visit ID

O CX 20 <not used>

7 01281 Prior Patient Name O XPN 48 <not used>





<identifier1 >^<description>^<coding system>^<identifier2>^<description>^<coding system >


SeqHL7Item #

HL7 Dräger



2 00570 Value Type C ID 2 NM, SN or ST(ASA only)

R



R 2

4 00572 Observation Sub - ID

C ST 20 <not used>


C * 65536

The parame-ter value.

R 30

6 00574 Units O CE 60 See Units O 30


O ST 10 <not used>

8 00576 Abnormal Flags O ID 5 <not used>


10 00578 Nature of Abnor-mal Test

O ID 2 <not used>


R ID 1 <not used>


O TS 26 <not used>


O ST 20 <not used>


O TS 26 YYYYMMD-DHHmm

O 12



O XCN 80 <not used>


O CE 60 <not used>

identifier1 label for the parameter

description parameter description



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:


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:


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

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

identifier2 an alternate label for the parameter

coding system name of the coding system

identifier1 unit identifier

description unit description

identifier2 an alternate label for the unit


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

Segment Description






Seq HL7Item #

HL7 Dräger



2 00002 Encoding Char-acters

R ST 4 “^~\&” R 4

3 00003 Sending Appli-cation



O HD 180 <not used>


O HD 180 The string received in the Sending Application field of the MSH segment of the ADT message received.

O


O HD 180 <not used>



O 12


9 00009 Message Type R CM 7 ACK^<Trig-ger Event code>

R 7

10 00010 Message Con-trol ID

R ST 20 A number or other identifier that uniquely identifies the message Sending Application

R 20


12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>


O ST 180 <not used>




O ID 2 "AL" R 2


O ID 2 "NE" R 2



19 00693 Principal Lan-guage Of Mes-sage

O CE 60 <not used>


Seq HL7Item #

HL7 Dräger






Seq HL7Item #

HL7 Dräger



R ID 2 See Acknowl-edgment Codes

R 2


R ST 20 This field con-tains the Mes-sage Control ID of the mes-sage it is acknowledg-ing. Refer to MSH Seg-ment - Mes-sage Header

R 20

3 00020 Text Message O ST 80 An error or sta-tus string

O 80


O NM 15 <not used>


B ID 1 <not used>


Value Description









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.

Instructions for use – Infinity® Gateway Solution Suite – Protocol Handbook – VF9.n 133

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.

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).

NOTE

The IHE Unsolicited and unsolicited ADT Interfaces are mutually exclusive.

Data Imported


Application Screen

Modular Monitors

Configured Monitors

Telemetry


Admit

Screen

Some-times Some times Some times See Patient Identifier

Visit Number Admit

Screen

Some-times Some times Some times See Patient Identifier

Patient Name Admit

Screen

Yes Yes Yes See Patient Name

Birth Date/Time

Admit

Screen

Yes Yes Yes See Date/Time of Birth

Admit Date Admit

Screen

Yes Yes Yes See Admit Date/Time

Height Admit

Screen

Yes Yes Yes See Observation Identifier

IHE Unsolicited ADT


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.

Weight Admit

Screen



Yes No No See Sex


Yes No No See Race

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 Language

N/A No No No See ADT Config Tool for supported languages

Patient Address

N/A No No No See Patient Address

Admitting Doctor

N/A No No No See Admitting Doctor

Consulting Doctor

N/A No No No See Consulting Doctor

Referring Doctor

N/A No No No See Referring Doctor

National ID / Social Security

N/A No No No See National ID/ Social Security Number

Ethnic Group N/A No No No See Ethnic Group

Data Imported


Application Screen

Modular Monitors

Configured Monitors

Telemetry


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.

Any other segments received will be ignored.

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

Segment Description


[EVN] EVN Segment - Event Type


{[AL1]} AL1 Segment -Patient Allergy

{[IN1]} IN1 Segment – Patient Insurance

{[DG1]} DG1 Segment – Patient Diagnosis

[NK1] NK1 Segment - Next of Kin


[MRG] MRG Segment - Merge Patient Informa-tion


IHE Unsolicited ADT



Seq HL7Item #

HL7 Dräger



R ST 1 The separator 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 “|”.

R 1


R ST 4 Four characters in the following order:

the component separator, the repetition separa-tor, the escape character, and the subcompo-nent separator. Recommended values are “^~\&”.

R 4


O HD 180 Text identifying the sending appli-cation.


O HD 180 <not used>


O HD 180 <not used>


O HD 180 <not used>


O TS 26 <not used>



IHE Unsolicited ADT


R CM 7 This field has the format:

ADT^<event type>

Supported events are as follows:A28 - Add person informationA31 - Update person informationA40 - Merge patient - patient identifier list

A47 - Change patient identifier list

R 7


R ST 20 A number or other identifier that uniquely identi-fies the message.

R 20


R PT 3 “P” R 3

12 00012 Version ID R ID 8 "2.5" R 8


O NM 15 <not used>


O ST 180 <not used>


O ID 2 <not used>


O ID 2 <not used>


O ID 2 <not used>


Seq HL7Item #

HL7 Dräger


IHE Unsolicited ADT



O ID 6 <not used>


O CE 60 <not used>


Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT

Event Occurred

The date and time that the ADT event took place, in the format:


EVN Segment - Event Type

Seq HL7Item #

HL7 Dräger

Descrip-tion


1 00099 Event Type Code

B ID 3 This field has been retained for backward 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.

R 3

2 00100 Recorded Date/Time

R TS 26 <not used>

3 00101 Date/Time Planned Event

O TS 26 <not used>

4 00102 Event Reason Code

O IS 3 <not used>

5 00103 Operator ID

O XCN 60 <not used>

6 00278 Event Occurred

O TS 26 See Event Occurred O 14

IHE Unsolicited ADT



Seq HL7Item #

HL7 Dräger



O SI 40 <not used>


O CX 20 <not used>

3 00106 Patient Identifier R CX 200 See Patient Identifier

R/O


O CX 20 <not used> O 20


O


O XPN 48 <not used>


O TS 26 See Date/Time of Birth

O 26




11 00114 Patient Address O XAD 106 See Patient Address

O

12 00115 Country Code B IS 4 <not used>


O XTN 40 <not used>


O XTN 40 <not used>


O CE 60 See ADT Con-fig Tool for sup-ported languages

O 4

16 00119 Marital Status O IS 1 See Marital Status

O 1

17 00120 Religion O IS 3 See Religion O 4



R/O 20


IHE Unsolicited ADT

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.


<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


O ST 16 See National ID/ Social Security Num-ber

O 16

20 00123 Driver’s License Number - Patient

O CM 25 <not used>


O CX 20 <not used>

22 00125 Ethnic Group O IS 3 See Ethnic Group

O 4



O ID 2 <not used>




O CE 60 <not used>

28 00131 Nationality O CE 80 See Nationality O 4


O TS 26 <not used>


O ID 1 <not used>


Seq HL7Item #

HL7 Dräger


IHE Unsolicited ADT


Patient Name

Contains the patient name to be entered in the Admit screen of the device upon the request. The format is:


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>


Date/Time of Birth

The format is:


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.

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.

NOTE

Infinity and SDC devices can support only an ID of up to 12 characters long.


In Field On Device

F Female

M Male

All other Unknown


IHE Unsolicited ADT

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 instancewith 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.



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(HIS code)

Infinity Code

On Device

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

2076-8 7 Native Hawaiian or Other Pacific Islander

All others 1 Unknown


street1 40

street2 40

city 25

state/province 25

postal code 10

country 15

address type 1

In Field On Device

A Separated

B Unmarried

C Common law

IHE Unsolicited ADT


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.

AL1 Segment -Patient Allergy

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

HIS Code Ethnic Group

H Hispanic or Latino

N Not Hispanic or Latino

All other Unknown

NOTE

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

In Field On Device


IHE Unsolicited ADT


Seq HL7Item #

HL7 Dräger


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 Code/Mne-monic/Descrip-tion

R CE 60 See Allergies R 44

4 00206 Allergy Severity O IS 2 ‘SV’ severe

‘MO’ moderate

‘MI’ mild

O 2

5 00207 Allergy Reaction O ST 15 A string describing the reaction that the patient has when exposed to the allergy

O 15

6 00208 Identification Date

O DT 8 <not used>

IHE Unsolicited ADT


Allergy Types

The following table lists the allergy types accepted by HL7:

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

Code Description

DA Drug Allergy

FA Food Allergy

MA Miscellaneous Allergy

MC Miscellaneous Contraindica-tion

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


IHE Unsolicited ADT

IN1 Segment - Patient Insurance

Seq HL7Item #

HL7 Dräger


1 00203 Set ID - IN1 R SI 4 <not used>

2 00368 Insurance Plan ID

R CE 60 A unique identifier for the insurance plan

R 20

3 00428 Insurance Com-pany ID

R CX 59 <not used>

4 00429 Insurance Com-pany Name

O XON 130 The name of the insurance com-pany

R 40

5 00430 Insurance Com-pany Address


6 00431 Insurance Co. Contact Person

O XPN 48 <not used>

7 00432 Insurance Co Phone Number

O XTN 40 The string contact number for the insurance com-pany.

O 25

8 00433 Group Number O ST 12 Identifies the group within the insurance plan

O 12

9 00434 Group Name O XON 130 The name of the group within the insurance plan

O 40

10 00435 Insured’s Group Emp ID

O CX 12 <not used>

11 00436 Insured’s Group Emp Name

O XON 130 <not used>

12 00437 Plan Effective Date

O DT 8 <not used>

13 00438 Plan Expiration Date

O DT 8 <not used>

14 00439 Authorization Information

O CM 55 <not used>

15 00440 Plan Type O IS 3 <not used>

16 00441 Name Of Insured

O XPN 48 See Name of Insured

O 72

17 00442 Insured’s Rela-tionship To Patient

O IS 2 See Appendix J: Relationship table

O 3

IHE Unsolicited ADT


18 00443 Insured’s Date Of Birth

O TS 26 Date of birth of the primary insurance holder in the for-mat

YYYYMMDD

O 8

19 00444 Insured’s Address


20 00445 Assignment Of Benefits

O IS 2 <not used>

21 00446 Coordination Of Benefits

O IS 2 <not used>

22 00447 Coord Of Ben. Priority

O ST 2 <not used>

23 00448 Notice Of Admission Flag

O ID 2 <not used>

24 00449 Notice Of Admission Date

O DT 8 <not used>

25 00450 Report Of Eligi-bility Flag

O ID 2 <not used>

26 00451 Report Of Eligi-bility Date

O DT 8 <not used>

27 00452 Release Infor-mation Code

O IS 2 <not used>

28 00453 Pre-Admit Cert (PAC)

O ST 15 <not used>

29 00454 Verification Date/Time

O TS 26 <not used>

30 00455 Verification By O XCN 60 <not used>

31 00456 Type Of Agree-ment Code

O IS 2 <not used>

32 00457 Billing Status O IS 2 <not used>

33 00458 Lifetime Reserve Days

O NM 4 <not used>

34 00459 Delay Before L.R. Day

O NM 4 <not used>

35 00460 Company Plan Code

O IS 8 <not used>

36 00461 Policy Number O ST 15 The policy number O 15

37 00462 Policy Deduct-ible

O CP 12 <not used>


Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT

Address

Repetition is not supported for this field, and only the first instance will be used.



38 00463 Policy Limit - Amount

B CP 12 <not used>

39 00464 Policy Limit - Days

O NM 4 <not used>

40 00465 Room Rate - Semi-Private

B CP 12 <not used>

41 00466 Room Rate - Pri-vate

B CP 12 <not used>

42 00467 Insured’s Employment Status

O CE 60 <not used>

43 00468 Insured’s Sex O IS 1 <not used>

44 00469 Insured’s Employer Address


45 00470 Verification Sta-tus

O ST 2 <not used>

46 00471 Prior Insurance Plan ID

O IS 8 <not used>

47 01227 Coverage Type O IS 3 <not used>


49 01230 Insured’s ID Number

O CX 12 <not used>


street1 40

street2 40

city 25

state/province 25

postal code 10

country 15


Seq HL7Item #

HL7 Dräger


IHE Unsolicited ADT


Name of Insured

Contains the name of the primary insured person, The format is:

<Last Name>^<First Name>^<Middle name>


DG1 Segment – Patient Diagnosis


Last 30

First 20

Middle 20

WARNING

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.


IHE Unsolicited ADT

DG1 Segment - Patient Diagnostics

Seq HL7Item #

HL7 Dräger


1 00375 Set ID - DG1 R SI 4 <not used>

2 00376 Diagnosis Coding Method

(B) R ID 2 <not used>

3 00377 Diagnosis Code

O CE 60 See Diagno-sis

R 51

4 00378 Diagnosis Description

B ST 40 The descrip-tion of the diagnosis. Note that this field is only used if com-ponent 2 of field 3 above is not popu-lated

O 42

5 00379 Diagnosis Date/Time

O TS 26 <not used>

6 00380 Diagnosis Type

R IS 2 Valid values are:

‘A’: Admitting

‘W’: Working (default)

‘F’: Final

O 1

7 00381 Major Diag-nostic Cate-gory

B CE 60 <not used>

8 00382 Diagnostic Related Group

B IS 4 <not used> O 4

9 00383 DRG Approval Indi-cator

B ID 2 <not used>

10 00384 DRG Grouper Review Code

B IS 2 <not used>

11 00385 Outlier Type B CE 60 <not used>

IHE Unsolicited ADT


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)

12 00386 Outlier Days B NM 3 <not used>

13 00387 Outlier Cost B NM 12 <not used>

14 00388 Grouper Ver-sion And Type

B ST 4 <not used>

15 00389 Diagnosis Priority

B NM 2 <not used>

16 00390 Diagnosing Clinician

O XCN 60 <not used>

17 00766 Diagnosis Classification

O IS 3 <not used>

18 00767 Confidential Indicator

O ID 1 <not used>

19 00768 Attestation Date/Time

O TS 26 <not used>

DG1 Segment - Patient Diagnostics (Continued)

Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT

NK1 Segment - Next of Kin

Seq HL7Item #

HL7 Dräger


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-dix J: Rela-tionship table

O 3

4 00193 Address O XAD 106 See Address

O 106

5 00194 Phone Num-ber

O XTN 40 A string contact number

O 25

6 00195 Business Phone Num-ber

O XTN 40 A string contact number

O 25

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 Code/Class

O CM 20 <not used>

12 00201 Employee Number

O CX 20 <not used>

13 00202 Organiza-tion Name

O XON 60 <not used>

14 00119 Marital Sta-tus

O IS 2 <not used>



O TS 26 <not used>

17 00755 Living Dependency

O IS 2 <not used>


O IS 2 <not used>


IHE Unsolicited ADT



O CE 60 <not used>

21 00742 Living Arrangement

O IS 2 <not used>

22 00743 Publicity Indicator

O IS 1 <not used>

23 00744 Protection Indicator

O ID 1 <not used>

24 00745 Student Indi-cator

O IS 2 <not used>



O XPN 48 <not used>



29 00747 Contact Reason

O CE 80 <not used>

30 00748 Contact Per-son’s Name

O XPN 48 <not used>

31 00749 Contact Per-son’s Tele-phone Number

O XTN 40 <not used>

32 00750 Contact Per-son’s Address


33 00751 Identifiers O CX 32 <not used>

34 00752 Job Status O IS 2 <not used>



37 00754 Contact Per-son’s Social Security Number

O ST 16 <not used>


Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT

Name

Contains the name of the next of kin/associated party. The format is: <Last Name>^<First Name>


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.




Last 30

First 20


street1 40

street2 40

city 25

state/province 25

postal code 10

country 15

IHE Unsolicited ADT



Seq HL7Item #

HL7 Dräger



2 00132 Patient Class R IS 1 Patient Class


O PL 80 See Patient Location




O PL 80 See Prior Patient Loca-tion

7 00137 Attending Doctor O XCN 60 If IHE Compliant:<not used>If IHE non Compliant:

"^Last Name^First Name ^Mid-dle Name ^Suffix^Pre-fix^Degree"

O

8 00138 Referring Doctor O XCN 60 If IHE Compliant:<Not used>If IHE non Compliant:



IHE Unsolicited ADT

9 00139 Consulting Doctor O XCN 60 If IHE Compliant:<not used>If IHE non Compliant:



11 00141 Temporary Loca-tion

O PL 80 <not used>


O IS 2 <not used>

13 00143 Readmission Indi-cator

O IS 2 <not used>




17 00147 Admitting Doctor O XCN 60 If IHE Compliant:<not used>

If IHE non Compliant:






Seq HL7Item #

HL7 Dräger


IHE Unsolicited ADT


21 00151 Charge Price Indi-cator

O IS 2 <not used>





O DT 8 <not used>





O IS 1 <not used>


O DT 8 <not used>


O IS 10 <not used>


O NM 12 <not used>

33 00163 Bad Debt Recov-ery Amount

O NM 12 <not used>


O IS 1 <not used>


O DT 8 <not used>

36 00166 Discharge Dispo-sition

O IS 3 <not used>


O CM 25 <not used>







O PL 80 <not used>


Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT

Patient Location

This field contains the location of the patient (destination location in a ADT – Admit, Discharge, and Transfer). It is in the format


Prior Patient Location

This field contains the location of the patient to be transferred.


Admit Date/Time

Contains the admission date in the format:


The date portion of this field will be entered in the Admit Date field of the Patient Admit screen on the device.

44 00174 Admit Date/Time O TS 26 See Admit Date/Time

O 26


O TS 26 See Dis-charge Date

O 26


Seq HL7Item #

HL7 Dräger


IHE Unsolicited ADT


Prior Patient Identifier List

If this MRG segment is contained inan 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.


MRG Segment - Merge Patient Information

Seq HL7Item #

HL7 Dräger


1 00211 Prior Patient Identi-fier List

R CX 20 See Prior Patient Identifier List

20

2 00212 Prior Alternate Patient ID

O CX 16 <not used>

3 00213 Prior Patient Account Number

O CX 20 <not used>

20

4 00214 Prior Patient ID - External

O CX 16 <not used>

5 01279 Prior Visit Number O CX 15 <not used>

6 01280 Prior Alternate Visit ID

O CX 20 <not used>

7 01281 Prior Patient Name O XPN 48 <not used>


IHE Unsolicited ADT





SeqHL7Item #

HL7 Dräger



2 00570 Value Type C ID 2 NM or SN R



R 2

4 00572 Observation Sub - ID

C ST 20 <not used>


C * 65536

The parame-ter value.

R 30



O ST 10 <not used>



10 00578 Nature of Abnor-mal Test

O ID 2 <not used>


R ID 1 <not used>


O TS 26 <not used>


O ST 20 <not used>



O 12



O XCN 80 <not used>


O CE 60 <not used>



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:


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:


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

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





identifier2 an alternate label for the unit





m meters g grams

in inches lb pounds

ft feet oz ounces

Seqment Description




IHE Unsolicited ADT


Seq HL7Item #

HL7 Dräger




R ST 4 “^~\&” R 4


O HD 180 INFO_S-RC_DRAE-GER^0030E60000000001^EUI-64

O 16


O HD 180 <not used>


O HD 180 The string received in the Sending Application field of the MSH segment of the ADT message received.

O


O HD 180 <not used>


O TS 26 YYYYMMD-DHHmmss+/-ZZZZ

O 12


9 00009 Message Type R CM 7

ACK^<Event type>^ACK

R 7


R ST 20 A number that uniquely iden-tifies the mes-sage Sending Application

R 20


12 00012 Version ID R ID 8 “2.5” R 8


O NM 15 <not used>

IHE Unsolicited ADT



O ST 180 <not used>


O ID 2 <not used> R 2




18 00692 Character Set O ID 6 8859/1


O CE 60 en^English^ISO639


Seq HL7Item #

HL7 Dräger



IHE Unsolicited ADT



Seq HL7Item #

HL7 Dräger




R 2


R ST 20 This field con-tains the Mes-sage Control ID of the mes-sage it is acknowledg-ing. Refer to MSH Seg-ment - Mes-sage Header

R 20


O 80


O NM 15 <not used>


B ID 1 <not used>


Value Description


IHE mode: Application acknowledgment: Accept


IHE mode: Application acknowledgment: Error


IHE mode: Application acknowledgment: Reject

IHE Unsolicited ADT


Sample ADT Message

MSH|^~\&|?|HIS|?|Infinity|20050530082015||ADTÂ28ÂDT_A05|99022916500500050122|P|2.5EVN||20050530082000||||PID||123456|555-55-5555^^^MRN-AA^MR~987-65-4321^^^SS-AA^SS~5005^^^Visit-AAÂN||Schmidt^Roberta^K.|Adams|2000062800|W||O|12 Blackrock Lane^^Wakefield^MA^12345-6785ÛSA||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Â28|16050611393300091753|P|2.5|||AL|NEMSA|AA|16050611393300014707|[5005]ADT: Admit successful


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

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.

NOTE

The solicited and unsolicited ADT Interfaces are mutually exclusive.

Data Imported

Destination Monitor HL7 Seg-mentApplication

ScreenModular Monitors

Configured Monitors

Telemetry


Admit

Screen

Sometimes Sometimes Sometimes See Patient Identifier

Visit Number Admit

Screen

Sometimes Sometimes Sometimes See Patient Identifier

Patient Name Admit

Screen

Yes Yes Yes See Patient Name

Birth Date/Time

Admit

Screen

Yes Yes Yes See Date of Birth

Admit Date Admit

Screen

Yes Yes Yes See Admit Date

Attending doctor

Admit

Screen

Yes Yes Yes See Attending Doctor

Height Admit

Screen


Weight Admit

Screen





Yes No No See Sex


Yes No No See Race

Data Imported

Destination Monitor HL7 Seg-mentApplication

ScreenModular Monitors

Configured Monitors

Telemetry



QRY – Patient Query

ADT Query messages are of the following format:

See ADR – Query Response for a description of the response message expected from the responding application.

Seqment Description

MSH MSH Segment - Message Header Query

QRD QRD Segment - Original Type Query Definition

MSH Segment - Message Header Query

Seq HL7 Item #

HL7 Dräger


1 00001 Field Separator

R ST 1 “|” R 1


R ST 4 “^~\&” R 4




O HD 180 <not used>


O HD 180 “NUR” O


O HD 180 <not used>


O TS 26 YYYYMMDDhhmmss

O 12


9 00009 Message Type R CM 7 “QRY^A19” R 7




R ST 20 A number or other identifier uniquely identifying the message. The responding system echoes this ID back to the sending system in the Message Acknowledgment segment (MSA).

R 20


12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>


O ST 180 <not used>

15 00015 Accept acknowledgment Type

O ID 2 "AL" R 2

16 00016 Application acknowledgment

O ID 2 "NE" R 2




O CE 60 <not used>

MSH Segment - Message Header (Continued)Query

Seq HL7 Item #

HL7 Dräger




QRD Segment - Original Type Query Definition

Seq HL7 Item #

HL7 Dräger


1 00025 Query Date/Time

R TS 26 YYYYMMDDhhmmss

R 26

2 00026 Query Format Code

R ID 1 “R” R 1

3 00027 Query Priority

R ID 1 “I” R 1

4 00028 Query ID R ST 10 A unique identifier for the query. It is returned intact by the responding application.

R 10

5 00029 Deferred Response Type

O ID 1 <not used>

6 00030 Deferred Response Date/Time

O TS 26 <not used>

7 00031 Quantity Limited Request

R CQ 10 "1^RD" R 10

8 00032 Who Subject Filter

R XCN 60 See Who Subject Filter

R 60

9 00033 What Subject Filter

R CE 60 See What Subject Filter

R 60

10 00034 What Department Data Code

R CE 60 <not used>

11 00035 What Data Code Value Qual.

O ST 20 <not used>

12 00036 Query Results Level

O TS 1 <not used>



What Subject Filter

A string which denotes how the Who Subject Filter field is to be interpreted, as follows:

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.

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

Field Contents Identifier Type

APA Patient Account number

APM Medical Record Number

Seqment Description



QRD QRD Segment - Original Type Query Definition



[{OBX}] OBX Segment - Observation/Result




Seq HL7 Item #

HL7 Dräger


1 00001 Field Separator R ST 1 The separator 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 “|”.

R 1


R ST 4 Four characters in the following order: the component separator, the repetition separator, the escape character, and the subcomponent separator. Recommended values are ^~\&.

R 4


O HD 180 A string identifying the Sending Application.

O 16



O HD 180 <not used>


O HD 180 <not used>



O 12


9 00009 Message Type R CM 7 “ADR^A19” R 7



R 20




12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 <not used>


O ST 180 <not used>

15 00015 Accept acknowledgment Type

O ID 2 <not used>


O ID 2 <not used>




O CE 60 <not used>


Seq HL7 Item #

HL7 Dräger





Seq HL7 Item #

HL7 Dräger



R ID 2 R 2


R ST 20 The message control ID of the message it is acknowledging. Refer to

R 20


O 80


O NM 15 <not used>


B ID 1 <not used>





QRD Segment – Original Type Query Definition

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

Value Description










Seq HL7 Item #

HL7 Dräger



O SI 4 <not used>


O CX 20 <not used>


R CX 20 See Patient Identifier

R/O


O CX 20 <not used>


O


O XPN 48 <not used>


O TS 26 See Date of Birth

O 26




11 00114 Patient Address O XAD 106 <not used> O



O XTN 40 <not used>


O XTN 40 <not used>

15 00118 Primary Language

O CE 60 <not used> O 4

16 00119 Marital Status O IS 1 <not used> O 1

17 00120 Religion O IS 3 See ADTConfig tool for supported religions.

O 4



R/O


O ST 16 <not used> O 16

20 00123 Driver's License Number – Patient

O CM 25 <not used>

21 00124 Mother's Identifier O CX 20 <not used>

22 00125 Ethnic Group O IS 3 <not used> O 4




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.


<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).


O ID 2 <not used>




O CE 60 <not used>

28 00131 Nationality O CE 80 <not used> O 4


O TS 26 <not used>


O ID 1 <not used>

CAUTION

Infinity and SDC devices can support only an ID of up to 12 characters long.



Seq HL7 Item #

HL7 Dräger




Patient Name

Contains the patient name to be entered in the Admit screen of the device upon request. The format is:


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>


Date of Birth

The format is:


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.

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

F Female

M Male

All other Unknown

In Field(HIS code)

On Device

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




Seq HL7 Item #

HL7 Dräger



2 00132 Patient Class R IS 1 <not used>


O PL 80 <not used>




O PL 80 <not used>

7 00137 Attending Doctor O XCN 60 See Attending Doctor

O 60

8 00138 Referring Doctor O XCN 60 <not used>

9 00139 Consulting Doctor O XCN 60 <not used>



O PL 80 <not used>


O IS 2 <not used>


O IS 2 <not used>




17 00147 Admitting Doctor O XCN 60 <not used>





O IS 2 <not used>





O DT 8 <not used>







O IS 1 <not used>


O DT 8 <not used>


O IS 10 <not used>


O NM 12 <not used>


O NM 12 <not used>


O IS 1 <not used>


O DT 8 <not used>


O IS 3 <not used>


O CM 25 <not used>







O PL 80 <not used>

44 00174 Admit Date/Time O TS 26 See Admit Date O 26


O TS 26 <not used>


O NM 12 <not used>


48 00178 Total Adjustments O NM 12 <not used>


50 00180 Alternate Visit ID O CX 20 <not used>



O XCN 60 <not used>


Seq HL7 Item #

HL7 Dräger




Attending Doctor

Contains the attending physician information in the format:


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.




Seq HL7 Item #

HL7 Dräger



2 00570 Value Type C ID 2 NM or SN R 2


R CE 590 See Observation Identifier

R


C ST 20 <not used>


C * 65536


R 30



O ST 10 <not used>




O ID 2 <not used>

11 00579 Observ Result Status

R ID 1 <not used> 1

12 00580 Date Last Obs Normal Values

O TS 26 <not used>


O ST 20 <not used>



O 12



O XCN 80 <not used>


O CE 60 <not used>





<identifier1 >^<description>^<coding system>^<identifier2 >^<description>^<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:

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





Value Type Observation Value Field Format

NM <value>

SN <comparator>^<value>



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 >

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:



identifier2 an alternate identifier for the unit





m meters g grams

in inches lb pounds

ft feet oz ounces



Sample

QRY Message

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

ADR Message

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


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.

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.

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.

Lab Import


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.

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:

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).

NOTE

To configure the databases for importing HL7 lab-oratory data, a device ID of “HL7” is used.

<Time Label> <Date and Time>

<Group Label>

<param> <value> <units>


<Group Label>




Lab Import

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

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

Lab Import



The Lab Import interface will accept ORU messages. Square brackets [and] indicate optional segments. Curved brackets {and} indicate segments that may be repeated.

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

Segment Description


{


[PV1] PV1 Segment – Patient Visit

[ORC] ORC Segment – Common Order

[OBR] OBR Segment - Observation Request

[

{

OBX OBX Segment - Observation/Result

}

]

}


Lab Import


Seq HL7 Item #

HL7 Dräger



R ST 1 The separator 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 “|”.

R 1


R ST 4 The four charac-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 ^~\&.

R 4


O HD 180 A site-specific value used for cus-tomization.

O 16


O HD 180 <not used>


O HD 180 <not used> O


O HD 180 <not used>

Lab Import



O TS 26 YYYYMMD-DHHmmss. See Bedside Lab data display and Parameter time stamp for details on how time stamps are used on the destination device.

O 12



R CM 7 “ORU ^R01” R 7


R ST 20 A number or other 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).

R 20


12 00012 Version ID R ID 8 “2.3” or “2.3.1” R 8


O NM 15 This numeric field is incremented by one for each sub-sequent value, if sequencing is enabled.

O 15


O ST 180 <not used>


O ID 2 <not used>


O ID 2 <not used>



Seq HL7 Item #

HL7 Dräger



Lab Import


19 00693 Principal Lan-guage Of Message

O CE 60 <not used>


Seq HL7 Item #

HL7 Dräger


Lab Import



Seq HL7 Item #

HL7 Dräger


1 00104 Set ID - Patient ID O SI 4 <not used>


O CX 20 <not used>

3 00106 Patient ID (Inter-nal ID)

R CX 20 Medical Record Number of the patient. See PID Segment – Identi-fier Mapping


O CX 20 <not used>

5 00108 Patient Name R XPN 48 <not used>


O XPN 48 <not used>

7 00110 Date/Time of Birth O TS 26 <not used>




11 00114 Patient Address O XAD 1 <not used>



O XTN 1 <not used>



15 00118 Primary Language O CE 4 <not used>




O CX 60 The ID of the patient to whom this data belongs.

R 12


O ST 1 <not used>


O CM 25 <not used>





Lab Import

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.

24 00127 Multiple Birth Indi-cator

O ID 2 <not used>




O CE 60 <not used>



O TS 26 <not used>


O ID 1 <not used>


Seq HL7 Item #

HL7 Dräger


Lab Import



Seq HL7 Item #

HL7 Dräger




C EI 75 <not used>


C EI 75 <not used>

4 00238 Universal Ser-vice ID

R CE 200 <not used>



B TS 26 <not used>


C TS 26 See Observa-tion Date/Time

R 14


O TS 26 <not used>

9 00243 Collection Vol-ume

O CQ 20 <not used>

10 00244 Collector Identi-fier

O XCN 60 <not used>


O ID 1 <not used>


13 00247 Relevant Clini-cal Info.

O ST 300 <not used>


C TS 26 <not used>

15 00249 Specimen Source

O CM 300 <not used>

16 00226 Ordering Pro-vider

O XCN 80 <not used>


O XTN 40 <not used>





Lab Import


22 00255 Results Report/Status Date/Time

C TS 26 <not used>

23 00256 Charge to Prac-tice +

O CM 40 <not used>

24 00257 Diagnostic Ser-vice Section ID

O ID 10 <not used>




28 00260 Result Copies To

O XCN 150 <not used>



O ID 20 <not used>

31 00263 Reason for Study

O CE 300 <not used>


O CM 200 <not used>


O CM 200 <not used>


35 00267 Transcriptionist +

O CM 200 <not used>


O TS 26 <not used>

37 01028 Number of Sam-ple Containers

O NM 4 <not used>

38 01029 Transport Log of Collected Sam-ple

O CE 60 <not used>

39 01030 Collector's Comment

O CE 200 <not used>


Seq HL7 Item #

HL7 Dräger


Lab Import


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.

40 01031 Transport Arrange. Responsibility

O CE 60 <not used>


O ID 30 <not used>


43 01034 Planned Patient Transport Com-ment

O CE 200 <not used>


Seq HL7 Item #

HL7 Dräger



Lab Import


Seq HL7 Item #

HL7 Dräger

Description Req Type Len Contents Req Len Repeatable


2 00570 Value Type C ID 2 SN,NM or ST R 2


R CE 590 In the first component, the label to be displayed on the Infinity monitor.

R


C ST 20 <not used>


C * 65536 See Observation Value R 30

6 00574 Units O CE 60 Uniquely identifies the units in which the param-eter will be reported. The first component of this field will be displayed on the Infinity patient monitor.

O 30


O ST 10 <not used>


O ID 5 <not used>



O ID 2 <not used>

11 00579 Observe Result Status

R ID 1 Reflects the current com-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.

R 1

12 00580 Date Last Obs Normal Values

O TS 26 <not used>


O ST 20 <not used>

Lab Import


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:

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


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



O TS 26 YYYYMMDDHHmmss. See Bedside Lab data display and Parameter time stamp for details on how time stamps are used on the destination device.

O 14



O XCN 80 <not used>


O CE 60 <not used>

Value Observation Value Field Format

ST <value>

NM <value>

SN <comparator>^<value>

Segment Description




Seq HL7 Item #

HL7 Dräger

Description Req Type Len Contents Req Len Repeatable


Lab Import


Seq HL7 Item #

HL7 Dräger




R ST 4 “^~\&” R 4

3 00003 Sending Applica-tion



5 00005 Receiving Appli-cation

O HD 180 The string identify-ing the Sending Application in the ORU message being acknowl-edged.

O

6 00006 Receiving Facil-ity

O HD 180 <not used>



O 12





R 20


12 00012 Version ID R ID 8 “2.3” R 8

13 00013 Sequence Num-ber

O NM 15 <not used>


O ST 180 <not used>

15 00015 Accept acknowl-edgment Type

O ID 2 “AL” R 2


O ID 2 “NE” R 2




O CE 60 <not used>

Lab Import




Seq HL7 Item #

HL7 Dräger




R 2



R 20


O 80

4 00021 Expected Sequence Num-ber

O NM 15 <not used>


B ID 1 <not used>


Value Description








Lab Import

Sample

This sample assumes that the 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


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.


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.

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

NOTE

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

Segment Description




[{OBX}] OBX Segment - Observation/Result

Lab Export



Seq HL7 Item #

HL7 Dräger



R ST 1 “|”. R 1


R ST 4 “^~\&” R 4




O HD 180 <not used>


O HD 180 “NUR” O


O HD 180 <not used>



O 12


9 00009 Message Type R CM 7 “ORU ^R01” R 7


R ST 20 A number that uniquely identi-fies the message. Dräger expects this ID to be sent back in the Mes-sage acknowl-edgment segment (MSA).

R 20


12 00012 Version ID R ID 8 “2.3” R 8


O NM 15 This numeric field is incremented by one for each sub-sequent value, if sequencing is enabled.

O 15


O ST 180 <not used>


O ID 2 "AL" R 2


O ID 2 "NE" R 2


Lab Export




O CE 60 <not used>


Seq HL7 Item #

HL7 Dräger


Lab Export



Seq HL7 Item #

HL7 Dräger


1 00104 Set ID - Patient ID O SI 4 <not used>


O CX 20 <not used>


R CX 20 Medical Record Number unless unavailable. Then it contains duplicate of Patient Account Number field, HL7 Item # 00121, with an “AN” in the sec-ond component.

R 12

4 00107 Alternate Patient ID – PID

O CX 20 <not used>

5 00108 Patient Name R XPN 48 UNKNOWN R 12


O XPN 48 <not used>

7 00110 Date/Time of Birth O TS 26 <not used>




11 00114 Patient Address O XAD 1 <not used>


13 00116 Phone Number – Home

O XTN 1 <not used>

14 00117 Phone Number – Business


15 00118 Primary Language O CE 4 <not used>




O CX 60 Patient Account number R 12

19 00122 SSN Number – Patient

O ST 1 <not used>


O CM 25 <not used>





Lab Export

24 00127 Multiple Birth Indi-cator

O ID 2 <not used>




O CE 60 <not used>



O TS 26 <not used>

30 00133 Patient Death Indi-cator

O ID 1 <not used>


Seq HL7 Item #

HL7 Dräger



2 00216 Placer Order Number C EI 75 <not used>


C EI 75 <not used>

4 00238 Universal Service ID R CE 200 <not used>


6 00240 Requested Date/time B TS 26 <not used>


C TS 26 Date the observation was obtained from the Infinity Network, in the format YYYYMMD-DHHmmss.

R 14


O TS 26 <not used>

9 00243 Collection Volume O CQ 20 <not used>

10 00244 Collector Identifier O XCN 60 <not used>


O ID 1 <not used>



Seq HL7 Item #

HL7 Dräger


Lab Export


13 00247 Relevant Clinical Info.

O ST 300 <not used>


C TS 26 <not used>

15 00249 Specimen Source O CM 300 <not used>

16 00226 Ordering Provider O XCN 80 <not used>


O XTN 40 <not used>





22 00255 Results Rpt/Status Chng - Date/Time +

C TS 26 <not used>

23 00256 Charge to Practice + O CM 40 <not used>

24 00257 Diagnostic Serv Sect ID

O ID 10 <not used>




28 00260 Result Copies To O XCN 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-preter +

O CM 200 <not used>


O CM 200 <not used>


35 00267 Transcriptionist + O CM 200 <not used>


O TS 26 <not used>


O NM 4 <not used>

38 01029 Transport Logistics of Collected Sample

O CE 60 <not used>

39 01030 Collector's Comment O CE 200 <not used>


Seq HL7 Item #

HL7 Dräger



Lab Export

40 01031 Transport Arrange-ment Responsibility

O CE 60 <not used>

41 01032 Transport Arranged O ID 30 <not used>


43 01034 Planned Patient Transport Comment

O CE 200 <not used>


Seq HL7 Item #

HL7 Dräger


Lab Export



Seq HL7 Item #

HL7 Dräger



2 00570 Value Type C ID 2 “SN” (structured numeric) if the parameter value reported is numeric, otherwise “ST” (string).

R 2


R CE 590 This field contains, in the first component, the label that is dis-played on the patient monitor.

R


C ST 20 <not used>


C * 65536


R 30

6 00574 Units O CE 60 This first component of this field contains the units string that is displayed on the patient monitor.

O 30


O ST 10 <not used>


O ID 5 <not used>



O ID 2 <not used>


R ID 1 The flag ‘R’ indicat-ing that the results have not been veri-fied.

R 1


O TS 26 <not used>


O ST 20 <not used>


Lab Export

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.


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

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


O TS 26 The date and time for this observation as reported in the "Date/Time Test Started” field of the corresponding ASTM results record.

O 14



O XCN 80 <not used>


O CE 60 <not used>


ST <value>


Segment Description




Seq HL7 Item #

HL7 Dräger


Lab Export



Seq HL7 Item #

HL7 Dräger




R ST 4 “^~\&” R 4

3 00003 Sending Applica-tion

O HD 180 INFO_SRC_DRAE-GER^0030E60000000001^EUI-64

O 16


5 00005 Receiving Appli-cation


6 00006 Receiving Facility O HD 180 <not used>


O TS 26 YYYYMMDDHHmm O 12




R ST 20 Must contain a num-ber that uniquely identifies the mes-sage.

R 20


12 00012 Version ID R ID 8 “2.3” R 8

13 00013 Sequence Num-ber

O NM 15 <not used>


O ST 180 <not used>


O ID 2 <not used>


O ID 2 <not used>




O CE 60 <not used>


Lab Export



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.

Seq HL7 Item #

HL7 Dräger



R ID 2 MSA Segment – Message Acknowledgment

R 2


R ST 20 This field must contain the message control ID of the message it is acknowledging.

R 20


O 80


O NM 15 <not used>


B ID 1 <not used>

6 00023 Error Condition O CD 10 <not used>

Value Description







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


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.


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

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.

NOTE

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










SeqHL7Item #

HL7 Dräger



2 00002 Encoding Charac-ters

R ST 4 “^~\&” R 4

3 00003 Sending Application R HD 227 "INFO_S-RC_DRAE-GER^0030E60000000001^EUI-64"

R 16

4 00004 Sending Facility RE HD 227 “Draeger” R 16

5 00005 Receiving Applica-tion

RE HD 227 Configurable in Infinity Gateway Configuration

R 227

6 00006 Receiving Facility RE HD 227 Configurable in Infinity Gateway Configuration

R 227

7 00007 Date/Time of Mes-sage

R DTM 24 YYYYMMD-DHHmmSS <Off-Set>

O 12

8 00008 Security X ST 40 <not used>

9 00009 Message Type R MSG 15 “ORU^R40^ORU_R40”

R 7

10 00010 Message Control ID R ST 199 A numberuniquelyidentifying themessage.

The receivingsystemechoes this ID back to thesending systemin themessageacknowledgmentsegment(MSA).

R 20


12 00012 Version ID R VID 60 “2.6” R 8

13 00013 Sequence Number RE NM 15 <not used>


X ST 180 <not used>




R ID 2 “AL”

16 00016 Application Acknowledgment Type

R ID 2 “NE”

17 00017 Country Code RE ID 3 <not used>

18 00692 Character Set RE ID 16 "8859/1"


RE CWE 705 “enÊnglishÎSO639”

20 Alternate Charac-ter Set Handling Scheme

X ID 20 <not used>

21 Message Profile Identifier

O EI 427 “IHE_PCD_AC-M_001ÎHE PCD^1.3.6.1.4.1.19376.1.6.4.4ÎSO"

22 Sending Responsi-ble Organization


23 Receiving Respon-sible Organization


24 Sending Network Address

X HD 227 <not used>

25 Receiving Network Address

X HD 227 <not used>

MSH Segment – Message Header (Continued)

SeqHL7Item #

HL7 Dräger





Seq HL7 Dräger


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-fier List

R 12

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-Dhhmmss

R 24

8 Administrative Sex RE IS 705 For Non IHE Compli-ant:

*"Code^Text"

Taken from ADT Configuration Infor-mation.

For IHE Compliant:

*"Code"


R 705

9 Patient Alias X XPN 250 <not used>

10 Race RE CWE 705 *”Code^Text”


R 705

11 Patient Address RE XAD 250 *”Street1^Street2^City^State^Zip Code^Country"^M

R 250

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"




16 Marital Status RE CWE 705 *”Code^Text"


R 705

17 Religion RE CWE 705 *"Code^Text" Taken from ADT Configura-tion Information.

R 705

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 - Patient

RE DLN 25 <not used>

21 Mother’s Identifier RE CX 705 <not used>

22 Ethnic Group RE CWE 705 *"Code^Text"


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"


29 Patient Death Date and 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>


Seq HL7 Dräger




Patient Identifier List

Depending on the 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 number (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>.


Seq HL7Item #

HL7 Dräger


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

2 00132 Patient Class R IS 1 *Patient Class R 1


RE PL 80 <Care Unit

Label>^^<Bed

Label>^<Hospi-tal/Facility>.


X IS 2 <not used> R 18

5 00135 Preadmit Num-ber

X CX 250 <not used>


X PL 80 <not used>

7 00137 Attending Doc-tor

X XCN 250 See Doctor’s Name

O 250



8 00138 Referring Doc-tor


O 250



O 250


X IS 3 <not used>


X PL 80 <not used>


X IS 2 <not used>


X IS 2 <not used>

14 00144 Admit Source X IS 6 <not used>


X IS 2 <not used>

16 00146 VIP Indicator X IS 2 <not used>

17 00147 Admitting Doc-tor


O 250

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>


X IS 2 <not used>

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-tive Date

X DT 8 <not used>


X NM 12 <not used>

27 00157 Contract Period X NM 3 <not used>

28 00158 Interest Code X IS 2 <not used>


X IS 4 <not used>


X DT 8 <not used>


X IS 10 <not used>


Seq HL7Item #

HL7 Dräger





X NM 12 <not used>


X NM 12 <not used>


X IS 1 <not used>


X DT 8 <not used>

36 00166 Discharge Dis-position

X IS 3 <not used>


X DLD 47 <not used>

38 00168 Diet Type X CWE 705 <not used>

39 00169 Servicing Facil-ity

X IS 2 <not used>

40 00170 Bed Status X IS 1 <not used>

41 00171 Account Status X IS 2 <not used>

42 00172 Pending Loca-tion

X PL 80 <not used>


X PL 80 <not used>


RE DTM 24 <not used> R 24


X DTM 24 <not used>


X NM 12 <not used>

47 00177 Total Charges X NM 12 <not used>


X NM 12 <not used>

49 00179 Total Payments X NM 12 <not used>


X CX 250 <not used>

51 01226 Visit Indicator RE IS 1 <not used>


Seq HL7Item #

HL7 Dräger




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>.


For the Alarm Management interface there are up to 7 OBX segments sent.

The following OBX segments are sent:OBX 1: MDS information


Seq HL7Item #

HL7 Dräger

Description Req

Type

Len Contents Req Len

1 00104 Set ID OBR R SI 4 Observation Set Num-ber

R 4


C EI 427 <not used>

3 00106 Filler Order Number

R EI 427 <OrderNumber>^ <Order Application>

R 427

4 00107 Universal Ser-vice Identifier

R CWE

705 “196616^MDC_EVT_ALARM^MDC”

R 40

5 00108 Priority - OBR X ID 2 <not used>

6 00109 Requested Date/Time

X DTM

24 <not used>

7 00110 Observation Date/Time

RE DTM

24 YYYYMMD-Dhhmmss+/-ZZZZ

R 24

8 00111 Observation End Date / Time

RE DTM

24 <not used>

9 00112 Collection Vol-ume

X CQ 722 <not used>

10 00113 Collection Identifier

R2 XCN

3220 <not used>

Seq HL7Item #

HL7 Dräger



R SI 4 “1” R 4

2 00002 Value Type C ID 3 “ST” R 2



3 00003 Observa-tion Identi-fier

R CWE 705 <CF_Code10>^<Reference ID>^MDC

R 20

4 00004 Observa-tion Sub-

R ST 20 "1.0.0.0" R 20

5 00005 Observa-tion Value

C Varies 99999 <not used> R

6 00006 Units C CWE 705 <not used>


CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>

11 00011 Observa-tion Result Status

R ID 1 “F” R 1

12 00012 Effective Date of Ref-erence Range

X DTM 24 <not used>


X ST 20 <not used>


RE DTM 24 <not used> O 24

15 00015 Producer’s ID


16 00016 Responsi-ble Observer


17 00017 Observa-tion Method


Seq HL7Item #

HL7 Dräger




OBX 2: Alarm Identification


RE EI 427 <UniqueID>^<model>^<manufac-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.

R 427

19 00693 Date/Time of the Analy-sis


20 Observa-tion Site


Seq HL7Item #

HL7 Dräger



R SI 4 “2” R 4



R CWE 705 <CF_Code10>^<Reference ID>^MDC

R 20

4 00004 Observa-tion Sub-

R ST 20 1.<VMD_In-stance>.<Chan-nel_Instance>.<CF_Code10>.<Met-ric_Instance>.“2”

R 20


C Varies 99999 Alarm Message R



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>

Seq HL7Item #

HL7 Dräger





R ID 1 “F” R 1


X DTM 24 <not used>


X ST 20 <not used>










RE EI 427 <UniqueID>^<model>^<manufac-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.

R 427





Seq HL7Item #

HL7 Dräger




OBX 3: Alarm SourceSeq HL7

Item #HL7 Dräger

Descrip-tion



R SI 4 “3” R 4

2 00002 Value Type C ID 3 “NM” (numeric) if

a numeric parameter is the source, other-wise, otherwise

“ST” (string).

R 2


R CWE 705 See Alarm Source Observation Identifier

R 20

4 00004 Observa-tion Sub-ID

R ST 20 1.<VMD_In-stance>.<Channel_In-stance>.<CF_Code10>.<Metric_In-stance>.“3”

R 20


C Varies 99999

Value of the alarm source.

R

6 00006 Units C CWE 705 If the source is a parameter then the unit will be displayed as:

<UOM CFCODE>^<UOM MDC>^MDC

otherwise this field is not used.

R


CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1



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


X DTM 24 <not used>


X ST 20 <not used>



15 00015 Pro-ducer’s ID






18 00692 Equip-ment Instance Identifier

RE EI 427 <UniqueID>^<model>^<manufacturer 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.

R 427





Seq HL7Item #

HL7 Dräger

Descrip-tion




OBX 4: Alarm Event PhaseSeq HL7

Item #HL7 Dräger


1 00001 Set ID – OBX R SI 4 “4” R 4



R CWE 705 “68481^MDC_AT-TR_EVENT_PHASE^MDC”

R 20


R ST 20 1.<VMD_In-stance>.<Chan-nel_Instance>.<CF_Code10>.<Metric_In-stance>.“4”

R 20


C Varies 99999

Even Phase: “start”, “update”, “stop”, or “end”.

R 20



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1


X DTM 24 <not used>


X ST 20 <not used>



15 00015 Producer’s ID RE CWE 705 <not used>







OBX 5: Alarm State

18 00692 Equipment Instance Iden-tifier



R 427



20 Observation Site


Seq HL7Item #

HL7 Dräger



R SI 4 “5” R 4



R CWE 705 “68482^MDC_AT-TR_ALARM_STATE^MDC”

R 20


R ST 20 1.<VMD_In-stance>.<Channel_In-stance>.<CF_Code10>.<Metric_Instance>.“5”

R 20


C Varies 99999

Contains “inactive”, “active”, or “latched”.

R 20



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1

Seq HL7Item #

HL7 Dräger





X DTM 24 <not used>


X ST 20 <not used>











If serial number is received then unique id will be serial number, otherwise it will be the IP/MAC address of the device.

R 427





Seq HL7Item #

HL7 Dräger




OBX 6: Alarm Inactivation StateSeq HL7

Item #HL7 Dräger



R SI 4 “6” R 4



R CWE 705 “68483^MDC_AT-TR_ALARM_INAC-TIVATION_STATE^MDC”

R 20


R ST 20 1.<VMD_In-stance>.<Chan-nel_Instance>.<CF_Code10>.<Met-ric_Instance>.“6”

R 20

5 00005

Observa-tion Value

C Varies 99999

Alarm Inactivation State: "enabled" “alarm-off” or alarm-paused"

R 20



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1


X DTM 24 <not used>


X ST 20 <not used>














R 427





Seq HL7Item #

HL7 Dräger




OBX 7: Alarm PrioritySeq HL7

Item #HL7 Dräger



R SI 4 “7” R 4



R CWE 705 “68484^MDC_AT-TR_ALARM_PRIOR-ITY^MDC”

R 20


R ST 20 1.<VMD_In-stance>.<Channel_In-stance>.<CF_Code10>.<Metric_Instances>.“7”

R 20

5 00005

Observa-tion Value

C Varies 99999

Alarm Priority: "PN", "PL", “PM”, or “PH”

R 20



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1


X DTM 24 <not used>


X ST 20 <not used>














R 427





Seq HL7Item #

HL7 Dräger




OBX 8: Alarm TypeSeq HL7

Item #HL7 Dräger



R SI 4 “8” R 4



R CWE 705 “68485^MDC_AT-TR_ALERT_-TYPE^MDC”

R 20


R ST 20 1.<VMD_In-stance>.<Channel_In-stance>.<CF_Code10>.<Metric_Instances>.“8”

R 20

5 00005

Observa-tion Value

C Varies 99999

Alarm Type:

“SP” - Physiological

“ST” - Technical

R 20



CE ST 60 <not used>


CE IS 5 <not used>



CE ID 2 <not used>


R ID 1 “F” R 1


X DTM 24 <not used>


X ST 20 <not used>










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

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






R 427





Segment Description



Seq HL7Item #

HL7 Dräger





Seq HL7Item #

HL7 Dräger




R ST 4 “^~\&” R 4


O HD 180 <not used> O 16


O HD 180 <not used>




O HD 180 <not used>


O TS 26 YYYYMMD-DHHmmss-ZZZZ

O 12


9 00009 Message Type R CM 7 ACK^<Event type>^ACK

R 7


R ST 20 A number that uniquely iden-tifies the mes-sage Sending Application

R 20


12 00012 Version ID R ID 8 “2.6” R 8


O NM 15 <not used>


O ST 180 <not used>










O CE 60 <not used>


Seq HL7Item #

HL7 Dräger




R 2


R ST 20 This field con-tains the Mes-sage Control ID of the mes-sage it is acknowledg-ing. Refer to Message Con-trol ID

R 20


O 80


O NM 15 <not used>


B ID 1 <not used>



Seq HL7Item #

HL7 Dräger





Sample Acknowledgement message

NAME=ACK

MSG:#

MSH|^~\&|NUR|DRAEGER|INFO_SRC_DRAEGER^0030E60000000001ÊUI-64|Drae-ger|20170125135441-0500||ACK^R40ÂCK|18092115514903462867|P|2.6|||AL|NE||8859/1|ENÊNGLISHÎSO639||IHE_PC-D_ACM_001ÎHE PCD^1.3.6.1.4.1.19376.1.6.4.4ÎSO

MSA|CA|18092115514900035708|

Value Description









Sample ORU message

NAME=ORU(3/11/2019 14:33:29)

MSG:

MSH|^~\&|INFO_SRC_DRAEGER^0030E60000000001ÊUI-64|Draeger|NUR|REC-FAC|20190311143329-0500||ORU^R40ÔRU_R40|19031114332900039875|P|2.6|||AL|NE||8859/1|enÊnglishÎSO639||IHE_PCD_ACM_001ÎHE PCD^1.3.6.1.4.1.19376.1.6.4.4ÎSO

PID|||111-11-1111^^Âuth1^MR~1001^^^ÂN||Smith^Wally^L.^^^^L|Joosse\S\K\S\Judy^^^^^^L|19420430142000|M^Male||UÛnknown|Smith13 Beer St.^#123Wally^Beersteinville^VA^12345-6785ÛSA^M||||spa^Span-ish|M^Married|JEW^Jewish||012-34-5678|||N^Not Hispanic or Latino||||||USAÛnited States

PV1|||CU2^^GOWDA23^BGS1||||^Munster^Florence^SÎI^Mr.^M.D.|^Kaite^William^M^MrÎI^MD|^Kumar^Sri^L^MrÎII^MBBS||||||||^Carr^Mary^JonesÎI^Mrs.^M.D.

OBR|1||1^356fdbd9-b939-47c7-acf2-151bc323819819667220190311143329^0030E60000000001ÊUI-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ÎACS^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ÎACS^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ÎACS^http://www.draeger.com/^DNS

OBX|4|ST|68481^MDC_AT-TR_EVENT_PHASE^MDC|1.1.2.147842.1.4|start||||||F|||||||0060E9EEBCÎACS^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ÎACS^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ÎACS^http://www.draeger.com/^DNS

OBX|7|ST|68484^MDC_ATTR_ALARM_PRIOR-ITY^MDC|1.1.2.147842.1.7|PM||||||F|||||||0060E9EEBCÎACS^http://www.draeger.com/^DNS

OBX|8|ST|68485^MDC_ATTR_ALERT_-TYPE^MDC|1.1.2.147842.1.8|SP||||||F|||||||0060E9EEBCÎACS^http://www.draeger.com/^DNS


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

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.

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.



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 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 ab 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).

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

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

NOTE

The patient monitor also requires that the parame-ter be a recent measurement. Please refer to the instructions for use for the specific patient monitor for more details.



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.

Message Header Record

Record Description

H Message Header Record

{

P Patient Information Record

[C] Comment Record

[O] Order Record

{

R Result Record

}

}

L Terminator Record

Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type ID “H” R N

2 Delimiter Definition Four characters in the following order:

field delimiter, usually “|”

repeat delimiter, usually ‘\’

component delimiter, usually ‘^’

escape character, usually ‘&’

Unlike other fields, no field delimiter precedes this field.

R N



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.

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 Address

<not used>

7 Message Control ID <not used>

8 Reserved Field <not used>

9 Sender Telephone Number

<not used>

10 Characteristics of Sender

<not used>

11 Receiver ID <not used>

12 Comment or Special Instructions

<not used>

13 Processing ID If this field is not blank and contains a value other than ‘P’, the data is not production level and therefore will not be forwarded to the patient monitor.

R N

14 Version No. <not used>

15 Date and Time of Message

See Date/Time of Message O N

Seq ASTMDescription

Dräger

Contents Req Repeat



Patient Information Record

Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type “P” R N

2 Sequence Number A sequential number indicating the 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.

R N

3 Practice Assigned Patient ID

See Practice Assigned Patient ID/Laboratory Assigned Patient ID

R N

4 Laboratory Assigned Patient ID

See Practice Assigned Patient ID/Laboratory Assigned Patient ID

R N

5 Patient ID No. 3 <not used>

6 Patient Name <not used>

7 Mother’s Maiden Name

<not used>

8 Birthdate <not used>

9 Patient Sex <not used>

10 Patient Race – Ethnic Origin

<not used>

11 Patient Address <not used>


13 Patient Telephone Number

<not used>

14 Attending Physician ID

<not used>

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 Suspected Diagnosis

<not used>

20 Patient Active Medications

<not used>

21 Patient’s Diet <not used>

22 Practice Field No. 1 <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.

23 Practice Field No. 2 <not used>

24 Admission and Discharge Dates

<not used>

25 Admission Status <not used>

26 Location <not used>

27 Nature of Alternative Diagnosis

<not used>

28 Alternative Diagnostic Code

<not used>

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>

Seq ASTMDescription

Dräger

Contents Req Repeat



Order Record

Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type “O” R N

2 Sequence Number A sequential number indicating the 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.

R N

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 and Time

<not used>

8 Specimen Collection Date 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 Information

<not used>

15 Date/Time Specimen Received

<not used>

16 Specimen Descriptor <not used>

17 Ordering Physician <not used>

18 Physician 's Telephone Number

<not used>

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>




This field contains the data and time the group of parameters to follow were collected, in the format: YYYYMMDDhhmmss


23 Date/Time Results Reported or Last Modified

<not used>

24 Instrument Charge to Computer System

<not used>

25 Instrument Section ID <not used>

26 Report Types <not used>


28 Location or Ward of Specimen Collection

<not used>

29 Nosocomial Injection Flag <not used>

30 Specimen Service <not used>

31 Specimen Institution <not used>

Seq ASTMDescription

Dräger

Contents Req Repeat



Result Record

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

Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type “R” R N

2 Sequence Number The sequential number of the result 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.

R N

3 Universal Test ID See Universal Test ID O N

4 Data or Measurement Value

The value of the results of the test. O N

5 Units The units of the result. O N

6 Reference Ranges See Reference Range O N

7 Result Abnormal Flags

See Abnormal Flag O Y

8 Nature of Abnormality Testing

The nature of the Abnormality O Y

9 Result Status <not used>

10 Date of Change in Instrument Normative Values or Units

<not used>

11 Operator Identification

<not used>

12 Date/Time Test Started


13 Date/Time Test Completed

<not used>

14 Instrument identification

<not used>



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 thefollowing formats are accepted:1 lower limit – upper limit2 >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



Comment Record


This field contains the data and time the test was started, in the format: YYYYMMDDhhmmss


Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type “C” R N

2 Sequence Number A sequential number indicating the numberof the comment at the same “level”.The first comment record at a particularhierarchical; level has a sequence numberof 1; the second has a sequence number

of 2, and so on.

R N

3 Universal Test ID <not used> O N

4 Data or Measurement Value

The text to be displayed in a Lab notes O N

5 Units <not used> O N



Terminator Record

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

Seq ASTMDescription

Dräger

Contents Req Repeat

1 Record Type “L” R

2 Sequence Number 1 R

3 Termination Code <not used>


PatientWatch

PatientWatch

An Infinity PatientWatch server can be run on Windows Server 2008 R2 or Windows Server 2012.

The PatientWatch includes:

An ActiveX control called WinViewActiveX Control.

A server-side ATL component called a Map2Server Control that is used to provide a uniform interface across multiple Infinity Gateway Server(s).

Some html and asp files and DLLs.

All client connections to PatientWatch must run in Microsoft Explorer 11.

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

PatientWatch can be used to view both SDC and Infinity devices, however, certain functionality, such as trends, is only available on Infinity devices.

NOTE

Not all error codes are used by all methods.

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.


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.

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.


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.


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


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.

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


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



5: FAIL –Patient monitor specified does not exist on the server


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.


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


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




5: FAIL – Patient monitor specified does not exist on the server


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.

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.




6: FAIL – specified does not exist on the server

7: FAIL – More than one patient monitor contains the same


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.


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.

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.


PatientWatch

Methods

GetErrorNum()

Purpose: This method returns the error number as a result of any other method calls.

Arguments: None


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().

PatientWatch


GetErrorString()

GetPatientList()

GetServerForBedMCAddr()

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.

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


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.

Purpose: This method returns the specific Gateway server that a select patient monitor with specified multicast address is connected to.

Arguments: Multicast address


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.


PatientWatch

GetServerForPatient()

GSMLogon()

Logon()

Purpose: This method receives a 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:


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.

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


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.

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


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.

PatientWatch


SetServers()

ValidateUser()

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.

Purpose: This method will add all servers in the list to map2server

Arguments: Servers


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.

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


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 does not have permissions a failure is returned.


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.

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.

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.

PatientWatch


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.

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 Mode

toggle true/false When set to true, PatientWatch is invoked in 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 Child

button When pressed, the page invokes PatientWatch in the selected mode and with the selected patient ID. The PatientWatch control is placed in the existing page.

Launch Child in New Window

button When pressed, the page invokes PatientWatch in the selected mode and with the selected patient ID. The PatientWatch control is placed in a new window.


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.

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

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 Drae-gerEncryption.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.

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.

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 a specific bed

The patient monitor can be specified 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.


PatientWatch

Use of Arguments

Arguments Comment Access to Patient Selection

User must log on

Server Used

None Invokes PatientWatch in the same way as the default PatientWatch page.

YES YES First server in Map2Server list.

Serv Automatically selects the current server.

YES YES Server in argument.

Login, Pwd Automatically logs in to the first server found for the user in Map2Server

YES NO First server in Map2Server list.

Serv, Login, Pwd

Automatically logs in to the named server

YES NO Server in argument.

Login, Pwd, PatID

Automatically determines which server should be used to access the specified patient, logs into that server and selects the patient monitor

NO NO First available server that provides access to Patient selected by patient ID.

Serv, Login, Pwd, PatID

Automatically logs into the named server and selects the patient monitor with the PatientIdentifier provided. The patient monitor must be available on server specified.

NO NO Server in argument.

Login, Pwd, CU, Bed

Automatically determines which server should be used to access the specified patient monitor, logs into that server and selects the patient monitor

NO NO Not Supported. When selecting a patient by care unit and bed label, the server name is required.

Serv, Login, Pwd, CU, Bed

Automatically logs into the named server and selects the patient monitor specified. The patient monitor must be available on named server.


PatientWatch


Login, Pwd, MC Automatically determines which server should be used to access the specified patient monitor, logs into that server and selects the patient monitor

NO NO First available server that provides access to the patient monitor selected by multicast address.

Serv, Login, Pwd, MC

Automatically logs into the named server and selects the patient monitor specified. The patient monitor must be available on named server.


File Invokes PatientWatch in the same way as the default 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.

YES YES First server in Map2Server list.

Arguments Comment Access to Patient Selection

User must log on

Server Used


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, Monitor/POD, Monitor/Ext, Monitor/MGM or ANESTH. “Monitor” or “patient monitor” refers to all Infinity monitoring 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 purchased 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.


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.


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



*F* Fault

*I* Interference

*L* Lead off

*N* No Signal

*U* Unplugged

OFF OFF

Special Display Value Description


Appendix D: Alarm States

Appendix D: Alarm States

# Alarm State Alarm State Value

Description

1 WV_ALARM_STATE_NOT_AC-TIVE

INACTIVE No currently active alarms.

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.


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)


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.


Appendix G: Operation Modes

Appendix G: Operation Modes

# Operation Mode Operation Mode Value

Description

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 Failure Device Failure

9 WV_OPERATING_MODE_NA N/A Not available


Appendix H: 12-Lead ECG Output Format


#ifndef __FORMAT_H__#define __FORMAT_H__

// specify byte alignment (using default)// #pragma pack(4)

// data typestypedef 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

NOTE

12 lead ECG output is only supported by Infinity devices.



#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



#define USER_LEN 18#define MANUF_LEN 8#define MODEL_LEN 8#define SERNBR_LEN 16#define VER_LEN 8#define REQNBR_LEN 12

// structurestypedef 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



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 bytestypedef 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


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 Gateway 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.

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



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



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.


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.

These instructions for use only apply to Infinity Gateway Suite Protocol Handbook VF9.nwith 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.This document is provided for customer information only, and will not be updated or exchanged without customer request.

Directive 93/42/EECconcerning Medical Devices

Draeger Medical Systems, Inc.3135 Quarry RoadTelford, PA 18969-1042U.S.A.(215) 721-5400(800) 4DRAGER(800 437-2437)

FAX (215) 723-5935http://www.draeger.com

Distributed in US by

Draeger, Inc.3135 Quarry RoadTelford, PA 18969-1042U.S.A.(215) 721-5400(800) 4DRAGER(800 437-2437)

FAX (215) 723-5935http://www.draeger.com

In Europe, Middle East, Africa, Latin America, Asia Pacific distributed by

Drägerwerk AG & Co. KGaAMoislinger Allee 53 – 55D-23542 LübeckGermany+49 451 8 82-0

FAX +49 451 8 82-20 80http://www.draeger.com

3703522 – RI 00 en© Drägerwerk AG & Co. KGaAEdition: 1 – 2019-03

Dräger reserves the right to make modifications to the equipment without prior notice.

Infinity Gateway Suite Protocol Handbook - Draeger

Documents

Transcript of Infinity Gateway Suite Protocol Handbook - Draeger