0% found this document useful (0 votes)
20 views56 pages

B40, B105, B125 HL7 Ref MNL 2062665-001 H

Uploaded by

Salvador Agati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views56 pages

B40, B105, B125 HL7 Ref MNL 2062665-001 H

Uploaded by

Salvador Agati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 56

GE Healthcare

HL7 Reference Manual

HL7 Reference Manual


English
2062665-001 H (paper)
© 2014, 2017 General Electric Company.
All Rights Reserved.
NOTE: Due to continuing product innovation, specifications in this manual are subject to change without notice.

NOTE: For technical documentation purposes, the abbreviation GE is used for the legal entity name, GE Healthcare
Finland Oy.

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

UNITY NETWORK are trademarks of GE Medical Systems Information Technologies registered in the United States Patent
and Trademark Office.

January 13, 2017


Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Manual Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Manual Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Manual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Ordering Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Safety message signal words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2 HL7 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
HL7 Standard Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Multiple Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Data Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
HL7 Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Observation results interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

3 Observation results interface . . . . . . . . . . . . . . . . . . . . 8


General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Trended data outbound Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Low Level Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supported Numeric Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supported Numeric Data Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Client/Server Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
HL7 Outbound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
HIS Disconnection or Network Outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2062665-001 H 1
4 PCD-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
PCD-01 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IHE Patient Care Device Domain >
Device Enterprise Communication (DEC) Profile > PCD-01 Transaction . 13
OBX-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Physiological Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Containment tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
VMD Reference IDs, MDC Codes, and Containment Trees . . . . . . . . . 16

5 Sample Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HL7 minimal lower layer protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Interface data content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Transactions from the monitor HL7 interface . . . . . . . . . . . . . . . . . . . . . . . 18
Result reporting messages (ORU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Result Message Composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Result Message Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Application High Level Acknowledgment Messages . . . . . . . . . . . . . . . . . . 24
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Acknowledgment Message Composition . . . . . . . . . . . . . . . . . . . . . . . . 24
Acknowledgment Message Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6 HL7 Data Segment Definitions . . . . . . . . . . . . . . . . . 27


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Data Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MSH — Message Header Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
MSA — Message Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
PID — Patient Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
PV1 — Patient Visit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
OBR — Observation Request (To Host) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
OBX — Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

A Supported parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Supported parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
HL7 Supported Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

2 2062665-001 H
B Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

2062665-001 H 3
4 2062665-001 H
Introduction:

1 Introduction

2062665-001 H 1
Introduction: Manual Information

Manual Information
Revision History
Each page of the document has the document part number and revision letter
at the bottom of the page. The revision letter changes whenever the document is
updated.

Revision Comments
A Initial release of document
B MR release
C ECO release
D ECO release
E ECO release
F ECO release
G ECO release
H ECO release

Manual Purpose
The device can be connected to hospital information systems (HIS) by the Health
Level Seven standard interface (HL7).

This document:

 Intended to be a technical reference to GE customers implementing the HL7


outbound interface.
 Not intended to provide instructions for implementing and using the HL7
standard. Details of the HL7 standard can be found in Health Level Seven
Version 2.6.
 Contains data formats for the transmission of data and describes the
requirements for interfacing to the GE system using the HL7 standard.
 Not describe how transactions are processed by the GE system or the
clinical impact of using some of the features described here.

Intended Audience
This manual is intended for HL7 integration engineers who configure hospital
information technology systems so they interface together.

2 2062665-001 H
Introduction: Service Information

Manual Conventions
This manual uses the following styles to emphasize text or indicate action.

Item Description
bold Indicates hardware terms.
bold italic Indicates software terms.
italic Indicates terms for emphasis.

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

Service Information
Responsibility
The hospital and their third-party developer have responsibility for HL7 standard
system and environment’s integration development and testing.

Service Requirements
Follow the service requirements listed below.

 For GE’s products, refer service to GE authorized service personnel only.


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

Warranty
Please refer to the documentation delivered with your system for your warranty
information.

2062665-001 H 3
Introduction: Service Information

Safety message signal words


Safety message signal words designate the severity of a potential hazard.

WARNING indicates a hazardous situation that, if not avoided, could result in


death or serious injury.

CAUTION indicates a hazardous situation that, if not avoided, could result in


minor or moderate injury.

NOTICE indicates a hazardous situation not related to personal injury that, if not
avoided, could result in property damage.

The order in which safety messages are presented in no way implies the order of
importance. The following safety messages apply to the system. Safety
messages specific to parts of the system are found in the relevant section.

4 2062665-001 H
HL7 Interface: Service Information

2 HL7 Interface

2062665-001 H 5
HL7 Interface: HL7 Standard Background

HL7 Standard Background


Overview
The Health Level Seven (HL7) standard is used to exchange data between
computer systems. It does not require a specific computer operating system,
programming language, or communication protocol for its implementation.

The goal of the HL7 standard is to harmonize message content and usage, while
allowing user-specific variations within the standard. To accomplish this, the HL7
standard specifies encoding rules used to create the message format. Based on
these rules, the messages generally consist of data fields and data segments.

Multiple Segments
A message is comprised of multiple segments. While some of the segments are
required to create a message, others are optional. Each segment within the HL7
message is separated by special segment separator characters.

Segment 1

Data 1 Data 2 Data n Segment 2 Segment m

Message

Data Elements
Each segment contains various data elements. The data elements may be of
varying lengths. Like the segments, they are separated from each other by
special separator characters. Certain data elements and their separators are
logically grouped together to create a data segment such as the message
header segment or the patient identification segment. With the exception of the
segment separator characters, the data contained in HL7 messages typically
consists of displayable ASCII characters.

Each data segment begins with a three character value, for example “MSH” for
the message header segment. These three characters uniquely identify the
segment within a given message. Segments are identified as either required or
optional, and some may be repeated. Similar to data fields, data segments are
separated from each other by segment separator characters.

Based on the HL7 encoding rules, each message within the HL7 protocol has a
known structure. The data segments and data fields that comprise a given
message are always the same. As a result, an individual data field can be found
within a message simply by knowing its configured position in a segment.

6 2062665-001 H
HL7 Interface: HL7 Standard Background

HL7 Communication
HL7 messages are passed between computer systems whenever a valid
transaction occurs. For example, receiving a completed test result on the
monitor system would cause an HL7 message to be generated and sent. After a
message is sent, the receiving system processes the message. When processing
is complete, the receiving system is designed to generate an application level
acknowledgment that is returned to the sending system.

Since the HL7 standard provides flexibility in message content and format, and
in communication protocol options, its implementation requires mutual
agreement between the sending and receiving computer systems on the
following items:

 message formats
 acknowledgment protocol
 communication protocol
 data handling
Communication between HIS personnel and GE interface personnel is essential
to determine the customer-specific use of the HL7 standard.

NOTE: This document is not intended to provide instructions for implementing


and using the HL7 standard. Details of the HL7 standard can be found in
Health Level Seven Version 2.6.

Observation results interfaces


The HL7 observation results reporting interface for this device is for unsolicited
trended data. ORU messages are sent unsolicited to the host at a user-
configured time interval. The monitor HL7 outbound interface pauses to wait for
an application level acknowledgment form the host. The HIS typically uses the
trended result message content in either of the following ways:

 To make test results available for access on the hospital computer system.
 To generate charges for completed tests.

2062665-001 H 7
Observation results interface: HL7 Standard Background

3 Observation results
interface

8 2062665-001 H
Observation results interface: General Description

General Description
Introduction
The HL7 standard interface is used to connect a hospital’s information system
(HIS) to the monitor for the transfer of data. Using the HL7 outbound interface,
the monitor can return result messages to the HIS.

The Patient Monitor Outbound implementation of the HL7 outbound interface


protocol provides result messages. The HL7 result reporting interface transmits
the result messages to the host system.

Trended data outbound Overview


The process to create ORU message is displayed in the following diagram.

CARESCAPE Network

1. HL7 outbound from monitor though CNI V2 switch, need ‘Unity and HL7’
license

2062665-001 H 9
Observation results interface: Low Level Communications

Hospital Network

2. HL7 outbound from monitor though hospital switch, need ‘HL7’ license

NOTES

 This switch should support intervlan routing function.


 The hospital or the third party can choose GE offered switch or other types.
If you need to use GE offered switch, please contact to GE ND&I Team to
setup CARESCAPE Network Infrastucture version 2.
 If hospital or the third party design networks by themselves, the hospital or
the third party has full responsibility for the function and the risk of their
network.

Low Level Communications


The GE HL7 interface uses TCP/IP sockets for all outbound messages and
conforms to the IEEE 802.3 Ethernet standard. The HL7 interface assumes that
the low level communication protocol ensures that the data arrives error free. As
a result, no data integrity checking is done at the application level.

Supported Numeric Options


The monitor transfers trended patient vital signs data to the hospital's
information system(s). Proper transfer of this data from the monitor to the HIS
systems is dependent on a custom configuration of the interface between the
monitor and the hospital's information system.

The monitor will send data at the configured time intervals of 1, 2, 3, 4, 5, 10, 15,
30, 45, and 60 minutes.

10 2062665-001 H
Observation results interface: Supported Numeric Data Categories

Supported Numeric Data Categories


Support for the following data categories includes:

 Invasive Blood Pressure (BP)


 Gas
 ECG
 ECG/ST (ST)
 Non-invasive Blood Pressure (NBP)
 Pulse Oximetry (SPO2)
 Respiration (RR)
 Temperature (TP)
 Entropy

Client/Server Connections
HL7 Outbound
Any HIS that communicates with the HL7 Outbound application with monitor
must act as the server. The monitor tries to open a connection on a
preconfigured specific IP address and port.

The monitor will connect with the server once the server port is established. The
monitor continuously tries to connect to the HIS on a regular periodic interval
using the auto connection feature. The monitor transfers the HL7 messages to
the HIS server by TCP/IP socket connection and will retry the message up to
three times.

When monitor already has admitted patient but no valid measurement data, the
monitor will not send out HL7 message to the EMR system.

HIS Disconnection or Network Outage


If the device or the HIS server connection is interrupted from the network (e.g.,
disconnected, in transport, etc.), the trended data for that time period will be lost.

NOTE: GE recommends that you enabling the HL7 acknowledgment option in


monitor’s service menu. Disabling this option may miss some data, if
the HL7 receiver system has the feature of sending acknowledge
message.

2062665-001 H 11
PCD-01: HIS Disconnection or Network Outage

4 PCD-01

12 2062665-001 H
PCD-01: PCD-01 description

PCD-01 description
IHE Patient Care Device Domain > Device Enterprise Communication
(DEC) Profile > PCD-01 Transaction
IHE PCD-01 is an Integration Profile that simplifies and adds semantic meaning
to HL7 V2.6 messaging. The device conforms to PCD-01 as a Device Observation
Report (DOR) actor using:

 ISO/IEEE 11073-10101 nomenclature in OBX-3 (Observation Identifier).


 Virtual medical device containment tree in OBX-4 (Observation Sub-ID).
 The originating medical device in OBX-18 (equipment instance identifier).
The value of this identifier is composed of two components. Component #1
is an EUI-64 identifier that starts with the GE Healthcare company code, plus
the EUI-64 separator, followed by the last 3 octects of the system's MAC
address in hex upper-case with no separators., plus a string that identifies
the monitoring equipment. For example, “080019FFFEAABBCCxxxxxxxx”.
Component #2 is “B40_GE”.

NOTE: The OBX-4 Observation Sub-ID follows PCD observation results


guidelines for relationships and elements in a hierarchical tree shown in
the following diagram.
Medical Device System (MDS) 0..*

1 1

Virtual Medical Device (VMD)

Channel (Chan)

* Enumeration

1
Metric

*
Numeric

2062665-001 H 13
PCD-01: PCD-01 description

OBX-4
Condition predicate:

This field is used to distinguish between multiple OBX segments by providing an


unambiguous mapping from observation contained in the OBX segment to the
IEEE 11073 containment tree for the Medical Device System sourcing of the
observation. For device related data, this field groups devices hierarchically.

For metric related data, this field associates metrics to devices hierarchically and
is used as a sequence number within the hierarchical representation. The dotted
notation provided for in the object diagram is:

<MDS>.<VMD>.<Channel>.<Metric> for the PCD-01 transaction, where the


Metric is a sequence number.

NOTE: Numeric and Enumeration are not used for PCD-01 transactions as
shown in the object diagram.

Physiological Monitor
Containment tree
Physiological monitors are comprised of a number of different Virtual Medical
Devices (VMDs) as indicated in the following example containment tree:

Physiological Monitor Containment tree Reference IDs

MDS: Physiological Monitor MDC_DEV_METER_PHYSIO_MULTI_PARAM_MDS (1::4301)

VMD: Blood Pressure MDC_DEV_METER_PRESS_BLD_VMD (1::4318)

Channel: Invasive BP MDC_DEV_METER_PRESS_BLD_CHAN (1::4319)

Channel: Non-Invasive BP MDC_DEV_PRESS_BLD_NONINV_CHAN (1::5151)

VMD: Temperature MDC_DEV_METER_TEMP_VMD (1::4366)

VMD: Pulse Oximeter MDC_DEV_ANALY_SAT_O2_VMD (1::4106)

VMD: ECG Monitor MDC_DEV_ECG_VMD (1::4262)

VMD: Entropy MDC_DEV_EEG_ENTROPY_VMD

The first OBX following the OBR segment is always set to:

OBX|1||69965^MDC_DEV_MON_PHYSIO_MULTI_PARAM_MDS^MDC|1
.0.0.0|||||||X

This is the standard device reference used for a monitor or monitor system.

The second OBX following OBX(1) is a Virtual Medical Device (VMD) Header, e.g.,

OBX|10||69798^MDC_DEV_ECG_VMD^MDC|1.5.0.0|||||||X

14 2062665-001 H
PCD-01: PCD-01 description

This is a logical grouping of semantically related observations and numeric


categories. The OBXs that follow are the actual results for the VMD.

OBX|11|NM|147842^MDC_ECG_HEART_RATE^MDC|1.5.1.1|80|26
4864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|12|NM|148066^MDC_ECG_V_P_C_RATE^MDC|1.5.1.2|0|264
864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

Invasive/Non Invasive Blood Pressure also have an explicit channel OBX as


shown in the example below.

NOTE: Regarding the third dot in the OBX-4 notation, which indicates the
channel that corresponds to the Channel Header, all observations
below contain the same channel number.

The message contains first the VMD OBX headers, followed by the Channel OBX
header, and then the discrete observations.

OBX|2||69854^MDC_DEV_METER_PRESS_BLD_VMD^MDC|1.13.0.0
|||||||X

OBX|3||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13.1.
0|||||||X

OBX|4|NM|150033^MDC_PRESS_BLD_ART_SYS^MDC|1.13.1.1|11
2|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|5|NM|150034^MDC_PRESS_BLD_ART_DIA^MDC|1.13.1.2|76
|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B4020
^B40_GE

OBX|6|NM|150035^MDC_PRESS_BLD_ART_MEAN^MDC|1.13.1.3|9
5|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|7|NM|149522^MDC_BLD_PULS_RATE_INV^MDC|1.13.1.4|80
|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FF
FE0B4020^B40_GE

NOTE: If a second Invasion Channel were to be used, the following channel


OBX header would be included in the message with the channel in OBX-
4 equal to 2. This would then be followed by the observations related to
channel 2 (e.g., PA pressure).

OBX|8||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13
.2.0|||||||X

All observations have the OBX-4 channel set to the channel number coming
from monitor.

2062665-001 H 15
PCD-01: PCD-01 description

VMD Reference IDs, MDC Codes, and Containment Trees


The following table lists all of the defined VMD and Channel related to each
numeric category.

Parameter VMD Reference ID VMD MDC Containment


Code
ECG MDC_DEV_ECG_VMD 69798 1.5.0.0
ECG RESP MDC_DEV_ECG_RESP_VMD 70666 1.6.0.0
Gas Mon MDC_DEV_GEN_CONC_AWAY_VMD 69766 1.11.0.0
IP MDC_DEV_METER_PRESS_BLD_VMD 69854 1.13.0.0
IP MDC_DEV_METER_PRESS_BLD_CHAN 69855 1.13.x.0 where "x" is
the slot number
NIBP MDC_DEV_PRESS_BLD_NONINV_VMD 70686 1.16.0.0
NIBP MDC_DEV_PRESS_BLD_NONINV_CHAN 70687 1.16.x.0 where "x" is
the slot number
Respiration MDC_DEV_ANALY_AWAY_MULTI_PARAM_VMD 69682 1.20.0.0
SpO2 MDC_DEV_ANALY_SAT_O2_VMD 69642 1.22.0.0
Temperature MDC_DEV_METER_TEMP_VMD 69902 1.26.0.0
Entropy MDC_DEV_EEG_ENTROPY_VMD 0 1.8.0.0

16 2062665-001 H
Sample Messages: PCD-01 description

5 Sample Messages

2062665-001 H 17
Sample Messages: HL7 minimal lower layer protocol

HL7 minimal lower layer protocol


HL7 Outbound messages are framed using the HL7 Minimal Lower Layer
Protocol. This protocol is documented in the HL7 2.6 specification. All HL7
messages begin with one start block character. The framing is completed by an
end character and a carriage return character at the end of the message. The
general format is as follows:

<SB> <HL7 message> <EB> <CR>


Where:
<SB> = Start Block character (0x0B)
<EB> = End Block character (0x1C)
<CR> = Carriage Return Character (0x0D)
<HL7 messages> use UTF-8 character encoding.

Interface data content


For HL7 Outbound messages, the trended data of monitor is mapped to data
field positions in the HL7 segment structures to create result messages.

The following pages provide the general format of the various HL7 data
messages recognized by the monitor for outbound interface. This document
describes only the data fields and segments that are provided by monitor. Fields
and segments not listed here are not sent by monitor.

Transactions from the monitor HL7 interface


Result reporting messages (ORU)
Overview
The HL7 results message type supported by the monitor HL7 outbound interface
for result reporting is described below.

 Result Message (ORU) — This message indicates that data has been
acquired.

Result Message Composition


All ORU messages have the same basic composition using the following HL7
segment types:

 MSH — Message header segment


 PID — Patient identification segment
 PV1 — Patient visit segment

18 2062665-001 H
Sample Messages: Transactions from the monitor HL7 interface

 OBR — Observation request segment


 OBX — Observation result segment(s)
The structure of an ORU message looks like this:

MSH
PID
PV1
{
OBR
{OBX}
}
 All message segments are terminated using a segment separator character,
which defaults to a carriage return.
 The open and closed braces { } represent segments and segment groups.
 Segments enclosed in square brackets [ ] are optional.
 Trailing data fields for a segment are truncated if empty.

Result Message Examples


Following are several examples of the many possible HL7-formatted result
messages.

The monitor HL7 outbound interface can generate countless variations of these
examples.

Example 1
This example has one OBR segment followed by the corresponding OBX
segments collected at a user-configured time interval. The OBX segments
contain periodic vital sign data for heart rate, PVC, temperature, and invasive
blood pressures.

MSH|^~\&|VSP^080019FFFE134535^EUI-64|GE
Healthcare|||20130122134100||ORU^R01^ORU_R01|00409713
4535|P|2.6|||NE|AL||UNICODE UTF-8|||PCD_DEC_001^IHE
PCD^1.3.6.1.4.1.19376.1.6.1.1.1^ISO

PID|||HED12^^^PID^MR||LAZY^KITTY^^^^^L|||

PV1||R|SURGERY^^V2

OBR|1|080019FFFE13453520130122134100^VSP^080019FFFE13
4535^EUI-
64|080019FFFE13453520130122134100^VSP^080019FFFE13453
5^EUI-64|182777000^monitoring of
patient^SCT|||20130122134100

OBX|1||69965^MDC_DEV_MON_PHYSIO_MULTI_PARAM_MDS^MDC|1
.0.0.0|||||||X

2062665-001 H 19
Sample Messages: Transactions from the monitor HL7 interface

OBX|2||69854^MDC_DEV_METER_PRESS_BLD_VMD^MDC|1.13.0.0
|||||||X

OBX|3||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13.1.
0|||||||X

OBX|4|NM|150033^MDC_PRESS_BLD_ART_SYS^MDC|1.13.1.1|38
|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE134535
^B40_GE

OBX|5|NM|150034^MDC_PRESS_BLD_ART_DIA^MDC|1.13.1.2|19
|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE134535
^B40_GE

OBX|6|NM|150035^MDC_PRESS_BLD_ART_MEAN^MDC|1.13.1.3|2
7|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE13453
5^B40_GE

OBX|7|NM|149522^MDC_BLD_PULS_RATE_INV^MDC|1.13.1.4|17
|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FF
FE134535^B40_GE

OBX|8||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13.2.
0|||||||X

OBX|9|NM|150087^MDC_PRESS_BLD_VEN_CENT_MEAN^MDC|1.13.
2.1|1|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE1
34535^B40_GE

OBX|10||69798^MDC_DEV_ECG_VMD^MDC|1.5.0.0|||||||X

OBX|11|NM|147842^MDC_ECG_HEART_RATE^MDC|1.5.1.1|21|26
4864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE1
34535^B40_GE

OBX|12|NM|148066^MDC_ECG_V_P_C_RATE^MDC|1.5.1.2|0|264
864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE13
4535^B40_GE

OBX|13||69902^MDC_DEV_METER_TEMP_VMD^MDC|1.26.0.0||||
|||X

OBX|14|NM|150344^MDC_TEMP^MDC|1.26.1.1|37.1|268192^MD
C_DIM_DEGC^MDC|||||R|||||||080019FFFE134535^B40_GE

Example 2
This example shows an OBR segment followed by the corresponding OBX
segments containing various periodic vital sign data collected at a user
configured time interval.

MSH|^~\&|VSP^080019FFFE0B4020^EUI-64|GE
Healthcare|||20121109160900||ORU^R01^ORU_R01|000C290B
4020|P|2.6|||NE|AL||UNICODE|||PCD_DEC_001^IHE
PCD^1.3.6.1.4.1.19376.1.6.1.1.1^ISO

PID|||999999999^^^PID^MR||^^^^^^L|||

20 2062665-001 H
Sample Messages: Transactions from the monitor HL7 interface

PV1||E|X^^B4020

OBR|1|080019FFFE0B402020121109160900^VSP^080019FFFE0B
4020^EUI-
64|080019FFFE0B402020121109160900^VSP^080019FFFE0B402
0^EUI-64|182777000^monitoring of
patient^SCT|||20121109160900

OBX|1||69965^MDC_DEV_MON_PHYSIO_MULTI_PARAM_MDS^MDC|1
.0.0.0|||||||X

OBX|2||69854^MDC_DEV_METER_PRESS_BLD_VMD^MDC|1.13.0.0
|||||||X

OBX|3||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13.1.
0|||||||X

OBX|4|NM|150033^MDC_PRESS_BLD_ART_SYS^MDC|1.13.1.1|11
2|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|5|NM|150034^MDC_PRESS_BLD_ART_DIA^MDC|1.13.1.2|76
|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B4020
^B40_GE

OBX|6|NM|150035^MDC_PRESS_BLD_ART_MEAN^MDC|1.13.1.3|9
5|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|7|NM|149522^MDC_BLD_PULS_RATE_INV^MDC|1.13.1.4|80
|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FF
FE0B4020^B40_GE

OBX|8||69855^MDC_DEV_METER_PRESS_BLD_CHAN^MDC|1.13.2.
0|||||||X

OBX|9|NM|150087^MDC_PRESS_BLD_VEN_CENT_MEAN^MDC|1.13.
2.1|9|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|10||69798^MDC_DEV_ECG_VMD^MDC|1.5.0.0|||||||X

OBX|11|NM|147842^MDC_ECG_HEART_RATE^MDC|1.5.1.1|80|26
4864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|12|NM|148066^MDC_ECG_V_P_C_RATE^MDC|1.5.1.2|0|264
864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

OBX|13|NM|131841^MDC_ECG_AMPL_ST_I^MDC|1.5.1.3|0.04|2
66419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

2062665-001 H 21
Sample Messages: Transactions from the monitor HL7 interface

OBX|14|NM|131842^MDC_ECG_AMPL_ST_II^MDC|1.5.1.4|0.04|
266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|15|NM|131901^MDC_ECG_AMPL_ST_III^MDC|1.5.1.5|0.04
|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE
0B4020^B40_GE

OBX|16|NM|131843^MDC_ECG_AMPL_ST_V1^MDC|1.5.1.6|0.04|
266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|17|NM|131844^MDC_ECG_AMPL_ST_V2^MDC|1.5.1.7|0.00|
266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|18|NM|131845^MDC_ECG_AMPL_ST_V3^MDC|1.5.1.8|0.00|
266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|19|NM|131846^MDC_ECG_AMPL_ST_V4^MDC|1.5.1.9|0.00|
266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|20|NM|131847^MDC_ECG_AMPL_ST_V5^MDC|1.5.1.10|0.00
|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE
0B4020^B40_GE

OBX|21|NM|131848^MDC_ECG_AMPL_ST_V6^MDC|1.5.1.11|0.00
|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFFE
0B4020^B40_GE

OBX|22|NM|131902^MDC_ECG_AMPL_ST_AVR^MDC|1.5.1.12|-
0.04|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019
FFFE0B4020^B40_GE

OBX|23|NM|131903^MDC_ECG_AMPL_ST_AVL^MDC|1.5.1.13|0.0
0|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFF
E0B4020^B40_GE

OBX|24|NM|131904^MDC_ECG_AMPL_ST_AVF^MDC|1.5.1.14|0.0
4|266419^MDC_DIM_MICRO_VOLT^MDC|||||R|||||||080019FFF
E0B4020^B40_GE

OBX|25||69766^MDC_DEV_GEN_CONC_AWAY_VMD^MDC|1.11.0.0|
||||||X

OBX|26|NM|151712^MDC_CONC_AWAY_CO2_EXP^MDC|1.11.1.1|3
8|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|27|NM|151716^MDC_CONC_AWAY_CO2_INSP^MDC|1.11.1.2|
8|266016^MDC_DIM_MMHG^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

22 2062665-001 H
Sample Messages: Transactions from the monitor HL7 interface

OBX|28|NM|151594^MDC_CO2_RESP_RATE^MDC|1.11.1.3|18|26
4928^MDC_DIM_RESP_PER_MIN^MDC|||||R|||||||080019FFFE0
B4020^B40_GE

OBX|29|NM|151748^MDC_AWAY_O2_EXP^MDC|1.11.1.4|16|2626
88^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B4020^B
40_GE

OBX|30|NM|152196^MDC_CONC_AWAY_O2_INSP^MDC|1.11.1.5|2
1|262688^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

OBX|31|NM|152320^MDC_AWAY_N2O_EXP^MDC|1.11.1.6|5|2626
88^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B4020^B
40_GE

OBX|32|NM|152192^MDC_CONC_AWAY_N2O_INSP^MDC|1.11.1.7|
8|262688^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

OBX|33|NM|0^MDC_CONC_MAC_SUM^MDC|1.11.1.8|0|262656^MD
C_DIM_DIMLESS^MDC|||||R|||||||080019FFFE0B4020^B40_GE

OBX|34|NM|0^MDC_CONC_MAC_SUM_AGE_CORR^MDC|1.11.1.9|0|
262656^MDC_DIM_DIMLESS^MDC|||||R|||||||080019FFFE0B40
20^B40_GE

OBX|35|NM|152312^MDC_AWAY_ISOFL_EXP^MDC|1.11.1.10|0|2
62688^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|36|NM|152184^MDC_CONC_AWAY_ISOFL_INSP^MDC|1.11.1.
11|1|262688^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFF
E0B4020^B40_GE

OBX|37||0^MDC_DEV_EEG_ENTROPY_VMD^MDC|1.8.0.0|||||||X

OBX|38|NM|155024^MDC_EEG_PAROX_CRTX_BURST_SUPPRN^MDC|
1.8.1.1|0|262688^MDC_DIM_PERCENT^MDC|||||R|||||||0800
19FFFE0B4020^B40_GE

OBX|39|NM|0^MDC_EEG_ENTROPY_RESPONSE^MDC|1.8.1.2|81|2
62656^MDC_DIM_DIMLESS^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|40|NM|0^MDC_EEG_ENTROPY_STATE^MDC|1.8.1.3|75|2626
56^MDC_DIM_DIMLESS^MDC|||||R|||||||080019FFFE0B4020^B
40_GE

OBX|41||69642^MDC_DEV_ANALY_SAT_O2_VMD^MDC|1.22.0.0||
|||||X

OBX|42|NM|149530^MDC_PULS_OXIM_PULS_RATE^MDC|1.22.1.1
|80|264864^MDC_DIM_BEAT_PER_MIN^MDC|||||R|||||||08001
9FFFE0B4020^B40_GE

2062665-001 H 23
Sample Messages: Transactions from the monitor HL7 interface

OBX|43|NM|150456^MDC_PULS_OXIM_SAT_O2^MDC|1.22.1.2|10
0|262688^MDC_DIM_PERCENT^MDC|||||R|||||||080019FFFE0B
4020^B40_GE

OBX|44||69682^MDC_DEV_ANALY_AWAY_MULTI_PARAM_VMD^MDC|
1.20.0.0|||||||X

OBX|45|NM|151562^MDC_RESP_RATE^MDC|1.20.1.1|18|264928
^MDC_DIM_RESP_PER_MIN^MDC|||||R|||||||080019FFFE0B402
0^B40_GE

OBX|46||70666^MDC_DEV_ECG_RESP_VMD^MDC|1.6.0.0|||||||
X

OBX|47|NM|151562^MDC_RESP_RATE^MDC|1.6.1.1|30|264928^
MDC_DIM_RESP_PER_MIN^MDC|||||R|||||||080019FFFE0B4020
^B40_GE

OBX|48||69902^MDC_DEV_METER_TEMP_VMD^MDC|1.26.0.0||||
|||X

OBX|49|NM|150344^MDC_TEMP^MDC|1.26.1.1|37.1|268192^MD
C_DIM_DEGC^MDC|||||R|||||||080019FFFE0B4020^B40_GE

OBX|50|NM|150344^MDC_TEMP^MDC|1.26.1.2|36.5|268192^MD
C_DIM_DEGC^MDC|||||R|||||||080019FFFE0B4020^B40_GE

Application High Level Acknowledgment Messages


Overview
The monitor Outbound HL7 interface supports application level message
acknowledgments formatted as HL7 original mode acknowledgments. This
function allows the HIS receiving application to acknowledge receipt and
successful processing.The acknowledgment message returned to the sending
application is used to determine whether to log the message to the monitor
service error system.

The HL7 acknowledgment configuration is optional in monitor’s HL7 service


menu, which will require acknowledgment message to be sent back to monitor
or not from HL7 receiver system. The default acknowledgment configuration is
Enable in monitor HL7 service menu.

NOTE: GE recommends enabling the HL7 acknowledgement option in the


monitor's service menu. Disabling this option may miss some data, if
the HL7 receiver system has the feature of sending acknowledge
message.

Acknowledgment Message Composition


Acknowledgment messages contain the following HL7 interface segments:

 MSH — Message segment header

24 2062665-001 H
Sample Messages: Transactions from the monitor HL7 interface

 MSA — Message segment acknowledgment


HL7 acknowledgment messages may contain one of statuses from the receiving
system:

 Application Accept (AA)


 Commit Accept (CA)
 Application Error (AE)
 Application Reject (AR)

If a positive accept acknowledgment (AA or CA) is returned from the HIS, it is


assumed the HIS has committed the data it received to safe storage. The
monitor HL7 application is then released from the necessity of re-sending the
message on time outs. If the acknowledgment configuration is enable, the
monitor HL7 application expects an accept acknowledgment message which
indicates successful reception and secure storage of the HL7 message data in
the HIS.

If the acknowledgment configuration is enabled, according to the HL7


specification, AE messages are those that contain an error. The outbound
interface attempts to send the ORU message again, with there being no more
than three total attempts; AR messages are also not retransmitted, the system
will disconnect the connection with the HL7 receiving system.

If the acknowledgment configuration is enabled, and no HL7 Acknowledgement


message is received after three total attempts. The outbound interface
disconnects the connection with the HL7 receiving system.

Regardless if the acknowledgement configuration is enable or disable, if monitor


receives an HL7 acknowledgement message with an Acknowledgment Code
(MSA field 1) that is not "AA" or "CA". The outbound interface creates a log entry
with at least the description from the message (MSA field 3) and error condition
(MSA field 6) if present.

Acknowledgment Message Examples


HL7 messages may be acknowledged as accepted, rejected, or returned with an
acknowledgment error. The following are examples of possible acknowledgment
messages that may be received as a result of sending messages to an HIS
server.

Acknowledgment Accept
MSH|^~\&|NUR^^|.^^|MMS

HL7|.^^|199812021001||ACK^R01|17f1be29-aa2a-11d2-
a655-00105a1e9b67|P^|2.3

MSA|AA|17f1be29-aa2a-11d2-a655-00105a1e9b67

Acknowledgment Reject
MSH|^~\&|NUR^^|.^^|MMS

HL7|.^^|199812021003||ACK^R01|17f1be29-aa2a-11d2-
a655-00105a1e9b67|P^|2.3

2062665-001 H 25
Sample Messages: Transactions from the monitor HL7 interface

MSA|AR|17f1be29-aa2a-11d2-a655-
00105a1e9b67|Unsupported message type

Acknowledgment Error
MSH|^~\&|NUR^^|.^^|MMS

HL7|.^^|199812021002||ACK^R01|17f1be29-aa2a-11d2-
a655-00105a1e9b67|P^|2.3

MSA|AE|17f1be29-aa2a-11d2-a655-00105a1e9b67|Unable to
find patient

26 2062665-001 H
HL7 Data Segment Definitions: Transactions from the monitor HL7 interface

6 HL7 Data Segment


Definitions

2062665-001 H 27
HL7 Data Segment Definitions: Introduction

Introduction
The following tables define the various data segments and are shown with the
standard HL7 message layout.

The lengths given for fields are the maximum lengths supported by the GE
system, not the HL7 definitions for field lengths. When the GE HL7 interface
support column indicates N, the data may be optimally sent in the message but
it will be ignored by the GE HL7 interface.

A data field may also be conditionally required, which is indicated with a CR


instead of an R. The Set ID field (seq. 1) in an OBR segment is an example of a
conditionally required field.

Only fields listed Y/R are available in the current HL7 output stream. Many of the
fields listed Y have no means of being entered into the monitoring devices. The Y
simply indicates that the field is supported and would not be ignored, as the
fields marked N, should it be received. However, the HL7 application is strictly
outbound at this point. The reason some fields are marked Y is that there is the
potential to add in-bound ADT capability to the HL7 application coming from an
HIS system at some point in the future. The fields could be included for outbound
data as well.

HL7 Table Abbreviations

Abbreviations Description

SEQ The sequence of the elements as they are numbered in


the segment.

LEN The length of the element.

DT The data type of the element. The data types are


described below.

TBL# Specific table reference.

RP/# Indicates if element repeats and number of times.

ITEM# HL7 unique item number for each element.

REQ/OPT Whether the field is required, optional, or conditional in


a segment.

OPT Type Description

R Required

RE Required, but may be empty.

O Optional

C Conditional

CE Conditional, but may be empty

28 2062665-001 H
HL7 Data Segment Definitions: Introduction

Abbreviations Description

X Not used with this trigger event.

Data Types Description

CE Coded element

SN Structured numeric

CK Composite ID w/check digit

ST String

CQ Composite quantity w/units

TQ Timing quantity

CX Extended composite ID w/check digit

TS Time stamp

DLN Driver's license number

TX Text data

DT Date

XAD Extended composite ID number

HD Hierarchic designator name for persons

ID Coded value

XON Extended composite name and ID

IS Sequence ID number for organizations

NM Numeric

XPN Extended person name

PT Processing type

XTN Extended telecommunications number

SI Sequence ID

* Indication that the data type for the value of an HL7


field can be of any type

2062665-001 H 29
HL7 Data Segment Definitions: Data Segments

Data Segments
MSH — Message Header Segment

SEQ LEN DT REQ/OPT TABLE# ELEMENT NAME

1 1 ST R Field Separator

2 4 ST R Encoding Characters

3 227 HD R 0361 Sending Application

4 227 HD RE 0362 Sending Facility

5 227 HD RE 0361 Receiving Application

6 227 HD RE 0362 Receiving Facility

7 26 DTM R Date/Time of Message

8 40 ST RE Security

9 15 MSG R Message Type

10 20 ST R Message Control ID

11 3 PT R Processing ID

12 60 VID R Version ID

13 15 NM RE Sequence Number

14 180 ST RE Continuation Pointer

15 2 ID R 0155 Accept Acknowledgment Type

16 2 ID R 0155 Application Acknowledgment Type

17 3 ID RE 0399 Country Code

18 16 ID RE 0211 Character Set

19 250 CE RE Principal Language of Message

20 20 ID RE 0356 Alternate Character Set Handling Scheme

21 427 EI R Message Profile Identifier

30 2062665-001 H
HL7 Data Segment Definitions: Data Segments

MSA — Message Acknowledgment

SEQ LEN DT REQ/OPT TABLE# ELEMENT NAME

1 2 ID R 0008 Acknowledgement code

2 20 ST R Message Control Id

3 80 ST X Text Message

4 1 ID X Delayed Acknowledgment Type

5 250 CWE X 0357 Error Condition

PID — Patient Identification

SEQ LEN DT REQ/OPT TBL# ITEM# ELEMENT NAME

1 4 SI R 00104 Set ID - PID

2 20 CX RE 00105 Patient ID

3 250 CX R 00106 Patient Identifier List

4 20 CX RE 00107 Alternate Patient ID - PID

5 250 XPN RE 00108 Patient Name

6 250 XPN RE 00109 Mother's Maiden Name

7 26 TS X 00110 Date/Time Birth

8 1 IS RE 0001 00111 Administrative Sex

9 250 XPN X 00112 Patient Alias

10 250 CE RE 0005 00113 Race

11 250 XAD RE 00114 Patient Address

12 4 IS RE 0289 00115 Country Code

13 250 XTN RE 00116 Phone Number - Hone

14 250 XTN X 00117 Phone Number - Business

15 250 CE RE 0296 00118 Primary Language

16 250 CE RE 0002 00119 Marital Status

17 250 CE RE 0006 00120 Religion

18 250 CX RE 00121 Patient Account Number

19 16 ST X 00122 SSN Number - Patient

20 25 DLN RE 00123 Driver's License Number - Patient

2062665-001 H 31
HL7 Data Segment Definitions: Data Segments

SEQ LEN DT REQ/OPT TBL# ITEM# ELEMENT NAME

21 250 CX RE 00124 Mother's Identifier

22 250 CE RE 0189 00125 Ethnic Group

23 250 ST RE 00126 Birth Place

24 1 ID RE 0136 00127 Multiple Birth Indicator

25 2 NM RE 00128 Birth Order

26 250 CE RE 0171 00129 Citizenship

27 250 CE RE 0172 00130 Veterans Military Status

28 250 CE RE 0212 00739 Nationality

29 26 TS RE 00740 Patient Death Data and Time

30 1 ID RE 0136 00741 Patient Death Indicator

31 1 ID RE 0136 01535 Identity Unknown Indicator

32 20 IS RE 0445 01536 Identity Reliability Code

33 26 TS RE 01537 Last Update Date/Time

34 241 HD RE 01538 Last Update Facility

35 250 CE RE 0446 01539 Species Doe

36 250 CE C 0447 01540 Breed Code

37 80 ST C 01541 Strain

38 250 CE RE 0429 01542 Production Class Code

39 250 CWE RE 0171 01840 Tribal Citizenship

32 2062665-001 H
HL7 Data Segment Definitions: Data Segments

PV1 — Patient Visit

SEQ LEN DT REQ/OPT TABLE# ELEMENT NAME

1 4 SI O Set ID - PV1

2 1 IS R 0004 Patient Class

3 80 PL RE Patient Location

4 2 IS X 0007 Admission Type

5 250 CX X Preadmit Number

6 80 PL X Prior Patient Location

7 250 XCN X 0010 Attending Doctor

8 250 XCN X 0010 Referring Doctor

9 250 XCN X 0010 Consulting Doctor

10 3 IS X 0069 Hospital Service

11 80 PL X Temporary Location

12 2 IS X 0087 Preadmit Test Indicator

13 2 IS X 0092 Re-admission Indicator

14 6 IS X 0023 Admit Source

15 2 IS X 0009 Ambulatory Status

16 2 IS X 0099 VIP Indicator

17 250 XCN X 0010 Admitting Doctor

18 2 IS X 0018 Patient Type

19 250 CX RE Visit Number

20 2 FC X 0064 Financial Class

21 2 IS X 0032 Charge Price Indicator

22 2 IS X 0045 Courtesy Code

23 2 IS X 0046 Credit Rating

24 2 IS X 0044 Contract Code

25 8 DT X Contract Effective Date

26 12 NM X Contract Amount

27 3 NM X Contract Period

28 2 IS X 0073 Interest Code

29 4 IS X 0110 Transfer to Bad Debt Code

2062665-001 H 33
HL7 Data Segment Definitions: Data Segments

SEQ LEN DT REQ/OPT TABLE# ELEMENT NAME

30 8 DT X Transfer to Bad Debt Date

31 10 IS X 0021 Bad Debt Agency Code

32 12 NM X Bad Debt Transfer Amount

33 12 NM X Bad Debt Recovery Amount

34 1 IS X 0111 Delete Account Indicator

35 8 DT X Delete Account Date

36 3 IS X 0112 Discharge Disposition

37 47 DLD X 0113 Discharged to Location

38 250 CE X 0114 Diet Type

39 2 IS X 0115 Servicing Facility

40 1 IS X 0116 Bed Status

41 2 IS X 0117 Account Status

42 80 PL X Pending Location

43 80 PL X Prior Temporary Location

44 26 TS X Admit Date/Time

45 26 TS X Discharge Date/Time

46 12 NM X Current Patient Balance

47 12 NMN X Total Charges

48 12 NM X Total Adjustments

49 12 NM X Total Payments

50 250 CX X 0203 Alternate Visit ID

51 1 IS RE 0326 Visit Indicator

34 2062665-001 H
HL7 Data Segment Definitions: Data Segments

OBR — Observation Request (To Host)

SEQ LEN DT USAGE ELEMENT NAME

1 4 SI R Set ID

2 427 EI R Placer Order Number

3 427 EI R Filler Order Number

4 250 CE R Universal Service Identifier

5 2 ID X Priority

6 26 DTM X Requested Date/Time

7 26 DTM RE Observation Date/Time

OBX — Result

SEQ LEN DT USAGE TABLE# ELEMENT NAME

1 4 SI R Set Id

2 2 ID RE 0125 Value Type

3 250 CE R Observation Identifier

4 20 ST R Observation Sub-ID

5 99999 Varies RE Observation Value

6 250 CE RE Units

7 60 ST RE Reference Range

8 5 IS RE 0078 Abnormal Flags

9 5 NM RE Probability

10 2 ID RE 0080 Nature of Abnormal Test

11 1 ID R 0085 Observation Result Status

12 26 DTM RE Effective Date of Reference Range

13 20 ST RE User Defined Access Checks

14 26 DTM R Date/Time of the Observation

15 250 CE RE Producer's ID

16 250 XCN RE Responsible Observer

17 250 CE RE Observation Method

18 22 EI RE Equipment Instance Identifier

2062665-001 H 35
HL7 Data Segment Definitions: Data Segments

SEQ LEN DT USAGE TABLE# ELEMENT NAME

19 26 DTM CE Date/Time of the Analysis

20 705 CWE RE 0163 Observation Site

36 2062665-001 H
HL7 Data Segment Definitions: Data Segments

A Supported
parameters

2062665-001 H 37
HL7 Data Segment Definitions: Supported parameters

Supported parameters
NOTE: Some parameters in this table are only available from certain versions
of the acquisition source.

NOTE: This list is subject to change without notice.

HL7 Supported Parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name

Name

REFID
Sub-

Invasive Pulmonary PA-S mm[Hg] MDC_PRESS_BLD_ART_ 150045 MDC_DIM_MMH 266016


Blood Artery PULM_SYS G
Pressure Pressure
(BP) Systolic

Pulmonary PA-D mm[Hg] MDC_PRESS_BLD_ART_ 150046 MDC_DIM_MMH 266016


Artery PULM_DIA G
Pressure
Diastolic

Pulmonary PA-M mm[Hg] MDC_PRESS_BLD_ART_ 150047 MDC_DIM_MMH 266016


Artery PULM_MEAN G
Pressure
Mean

Central CVP-M mm[Hg] MDC_PRESS_BLD_VEN_ 150087 MDC_DIM_MMH 266016


Venous CENT_MEAN G
Pressure
Mean

Intracranial ICP-M mm[Hg] MDC_PRESS_INTRA_CR 153611 MDC_DIM_MMH 266016


Pressure AN_MEAN G
Mean

Cerebral CPP mm[Hg] MDC_PRESS_CEREB_PE 153604 MDC_DIM_MMH 266016


Perfusion RF G
Pressure
Mean

Arterial ART-S mm[Hg] MDC_PRESS_BLD_ART_ 150033 MDC_DIM_MMH 266016


Pressure SYS G
Systolic

Arterial ART-D mm[Hg] MDC_PRESS_BLD_ART_ 150034 MDC_DIM_MMH 266016


Pressure DIA G
Diastolic

38 2062665-001 H
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

Arterial ART-M mm[Hg] MDC_PRESS_BLD_ART_ 150035 MDC_DIM_MMH 266016


Pressure ABP_MEAN G
Mean

Abdominal ABP-S mm[Hg] MDC_PRESS_BLD_ART_ 150037 MDC_DIM_MMH 266016


Pressure ABP_SYS G
Systolic

Abdominal ABP-D mm[Hg] MDC_PRESS_BLD_ART_ 150038 MDC_DIM_MMH 266016


Pressure ABP_DIA G
Diastolic

Abdominal ABP-M mm[Hg] MDC_PRESS_BLD_ART_ 150039 MDC_DIM_MMH 266016


Pressure ABP_MEAN G
Mean

ABP (Pulse ABP {beat}/ MDC_BLD_PULS_RATE_ 149522 MDC_DIM_BEAT 264864


Rate) (Pulse min INV _PER_MIN
Rate)

ART (Pulse ART {beat}/ MDC_BLD_PULS_RATE_ 149522 MDC_DIM_BEAT 264864


Rate) (Pulse min INV _PER_MIN
Rate)

UAC (Pulse UAC {beat}/ MDC_BLD_PULS_RATE_ 149522 MDC_DIM_BEAT 264864


Rate) (Pulse min INV _PER_MIN
Rate)

Right RVP-D mm[Hg] MDC_PRESS_BLD_VENT 150106 MDC_DIM_MMH 266016


Ventricle _RIGHT_DIA G
Pressure -
Diastolic

Right RVP-M mm[Hg] MDC_PRESS_BLD_VENT 150107 MDC_DIM_MMH 266016


Ventricle _RIGHT_MEAN G
Pressure -
Mean

Right RVP-S mm[Hg] MDC_PRESS_BLD_VENT 150105 MDC_DIM_MMH 266016


Ventricle _RIGHT_SYS G
Pressure -
Systolic

IBP1 - P1 - mm[Hg] MDC_PRESS_BLD_SYS 150017 MDC_DIM_MMH 266016


Systolic Systolic G

IBP1 - P1 - mm[Hg] MDC_PRESS_BLD_DIA 150018 MDC_DIM_MMH 266016


Diastolic Diastolic G

2062665-001 H 39
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

IBP1 - Mean P1 - mm[Hg] MDC_PRESS_BLD_MEA 150019 MDC_DIM_MMH 266016


Mean N G

IBP2 - P2 - mm[Hg] MDC_PRESS_BLD_SYS 150017 MDC_DIM_MMH 266016


Systolic Systolic G

IBP2 - P2 - mm[Hg] MDC_PRESS_BLD_DIA 150018 MDC_DIM_MMH 266016


Diastolic Diastolic G

IBP2 - Mean P2 - mm[Hg] MDC_PRESS_BLD_MEA 150019 MDC_DIM_MMH 266016


Mean N G

Right Atrial RAP-M mm[Hg] MDC_PRESS_BLD_ATR_ 150071 MDC_DIM_MMH 266016


Catheter RIGHT_MEAN G
Pressure
Mean

Left Atrial LAP-M mm[Hg] MDC_PRESS_BLD_ATR_ 150067 MDC_DIM_MMH 266016


Pressure LEFT_MEAN G
Mean

Umbilical UAC-S mm[Hg] MDC_PRESS_BLD_ART_ 150057 MDC_DIM_MMH 266016


Arterial UMB_SYS G
Catheter
Pressure
Systolic

Umbilical UAC-D mm[Hg] MDC_PRESS_BLD_ART_ 150058 MDC_DIM_MMH 266016


Arterial UMB_DIA G
Catheter
Pressure
Diastolic

Umbilical UAC-M mm[Hg] MDC_PRESS_BLD_ART_ 150059 MDC_DIM_MMH 266016


Arterial UMB_MEAN G
Catheter
Pressure
Mean

Umbilical UVC-M mm[Hg] MDC_PRESS_BLD_VEN_ 150091 MDC_DIM_MMH 266016


Venous UMB_MEAN G
Catheter
Pressure
Mean

ECG Heart Rate HR {beat}/ MDC_ECG_HEART_RATE 147842 MDC_DIM_BEAT 264864


min _PER_MIN

40 2062665-001 H
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

Premature PVC {beat}/ MDC_V_P_C_RATE 148065 MDC_DIM_BEAT 264864


Ventricular min _PER_MIN
Count

Respiration IMPR-RR {breath} MDC_RESP_RATE 151562 MDC_DIM_RESP 264928


Rate - ECG /min _PER_MIN

CO2 Expired CO2 CO2-EX mm[Hg] MDC_CONC_AWAY_CO 151712 MDC_DIM_MMH 266016


2_EXP G

Inspired CO2 CO2-IN mm[Hg] MDC_CONC_AWAY_CO 151716 MDC_DIM_MMH 266016


2_INSP G

Respiration CO2-RR {breath} MDC_CO2_RESP_RATE 151594 MDC_DIM_RESP 264928


Rate - CO2 /min _PER_MIN

Expired O2 O2-EX % MDC_AWAY_O2_EXP 151748 MDC_DIM_PERC 262688


ENT

Inspired O2 O2-IN % MDC_CONC_AWAY_O2 152196 MDC_DIM_PERC 262688


_INSP ENT

Expired N2O N2O-EX % MDC_AWAY_N2O_EXP 152320 MDC_DIM_PERC 262688


ENT

Inspired N2O N2O-IN % MDC_CONC_AWAY_N2 152192 MDC_DIM_PERC 262688


O_INSP ENT

MAC Sum MAC_SU {unitles MDC_CONC_MAC_SUM 0 MDC_DIM_DIML 262656


M s}1 ESS

MAC Sum MAC_AG {unitles MDC_CONC_MAC_SUM 0 MDC_DIM_DIML 262656


Age- E_SUM s}1 _AGE_CORR ESS
Corrected

Expired HAL-EX % MDC_AWAY_HALOTH_E 152304 MDC_DIM_PERC 262688


Halothane XP ENT

Inspired HAL-IN % MDC_CONC_AWAY_HA 152176 MDC_DIM_PERC 262688


Halothane LOTH_INSP ENT

Expired ISO-EX % MDC_AWAY_ISOFL_EXP 152312 MDC_DIM_PERC 262688


Isoflurane ENT

Inspired ISO-IN % MDC_CONC_AWAY_ISO 152184 MDC_DIM_PERC 262688


Isoflurane FL_INSP ENT

Expired ENF-EX % MDC_AWAY_ENFL_EXP 152300 MDC_DIM_PERC 262688


Enflurane ENT

2062665-001 H 41
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

Inspired ENF-IN % MDC_CONC_AWAY_EN 152172 MDC_DIM_PERC 262688


Enflurane FL_INSP ENT

Expired DES-EX % MDC_AWAY_DESFL_EX 152296 MDC_DIM_PERC 262688


Desflurane P ENT

Inspired DES-IN % MDC_CONC_AWAY_DE 152168 MDC_DIM_PERC 262688


Desflurane SFL_INSP ENT

Expired SEV-EX % MDC_AWAY_SEVOFL_E 152308 MDC_DIM_PERC 262688


Sevoflurane XP ENT

Inspired SEV-IN % MDC_CONC_AWAY_SEV 152180 MDC_DIM_PERC 262688


Sevoflurane OFL_INSP ENT

ECG/ST ST Segment I ST-I uV MDC_ECG_AMPL_ST_I 131841 MDC_DIM_MICR 266419


(ST) O_VOLT

ST Segment II ST-II uV MDC_ECG_AMPL_ST_II 131842 MDC_DIM_MICR 266419


O_VOLT

ST Segment ST-III uV MDC_ECG_AMPL_ST_III 131901 MDC_DIM_MICR 266419


III O_VOLT

ST Segment ST-V1 uV MDC_ECG_AMPL_ST_V1 131843 MDC_DIM_MICR 266419


V1 O_VOLT

ST Segment ST-V2 uV MDC_ECG_AMPL_ST_V2 131844 MDC_DIM_MICR 266419


V2 O_VOLT

ST Segment ST-V3 uV MDC_ECG_AMPL_ST_V3 131845 MDC_DIM_MICR 266419


V3 O_VOLT

ST Segment ST-V4 uV MDC_ECG_AMPL_ST_V4 131846 MDC_DIM_MICR 266419


V4 O_VOLT

ST Segment ST-V5 uV MDC_ECG_AMPL_ST_V5 131847 MDC_DIM_MICR 266419


V5 O_VOLT

ST Segment ST-V6 uV MDC_ECG_AMPL_ST_V6 131848 MDC_DIM_MICR 266419


V6 O_VOLT

ST Segment ST-AVR uV MDC_ECG_AMPL_ST_A 131902 MDC_DIM_MICR 266419


AVR VR O_VOLT

ST Segment ST-AVL uV MDC_ECG_AMPL_ST_A 131903 MDC_DIM_MICR 266419


AVL VL O_VOLT

42 2062665-001 H
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

ST Segment ST-AVF uV MDC_ECG_AMPL_ST_A 131904 MDC_DIM_MICR 266419


AVF VF O_VOLT

Non- Noninvasive NBP-S mm[Hg] MDC_PRESS_BLD_NONI 150021 MDC_DIM_MMH 266016


Invasive BP Systolic NV_SYS G
Blood
Pressure
(NIBP)

Noninvasive NBP-D mm[Hg] MDC_PRESS_BLD_NONI 150022 MDC_DIM_MMH 266016


BP Diastolic NV_DIA G

Noninvasive NBP-M mm[Hg] MDC_PRESS_BLD_NONI 150023 MDC_DIM_MMH 266016


BP Mean NV_MEAN G

Pulse Pulse SPO2-R {beat}/ MDC_PULS_OXIM_PULS 149530 MDC_DIM_BEAT 264864


Oximetry Oximetry min _RATE _PER_MIN
(SPO2) Peripheral
Heart Rate

Pulse SPO2-% % MDC_PULS_OXIM_SAT_ 150456 MDC_DIM_PERC 262688


Oximetry O2 ENT

Respirati Respiration RR {breath} MDC_RESP_RATE 151562 MDC_DIM_RESP 264928


on (RR) Rate /min _PER_MIN
Respirati
on Rate

Tempera Temperature TP-1 Cel MDC_TEMP 150344 MDC_DIM_DEGC 268192


ture (TP) 1

Temperature TP-2 Cel MDC_TEMP 150344 MDC_DIM_DEGC 268192


2

Axillary TP-Axil Cel MDC_TEMP_AXIL 0 MDC_DIM_DEGC 268192


Temperature

Esophageal TP-Eso Cel MDC_TEMP_ESO 150372 MDC_DIM_DEGC 268192


Temperature

Nasopharynx TP-Naso Cel MDC_TEMP_NASOPH 150380 MDC_DIM_DEGC 268192


Temperature

Tympanic TP- Cel MDC_TEMP_TYMP 150392 MDC_DIM_DEGC 268192


Temperature Tymp

Rectal TP-Rect Cel MDC_TEMP_RECT 188420 MDC_DIM_DEGC 268192


Temperature

Bladder TP-Blad Cel MDC_TEMP_FOLEY 150348 MDC_DIM_DEGC 268192


Temperature

2062665-001 H 43
HL7 Data Segment Definitions: Supported parameters

CF_UCODE10
Abbreviation

CF_CODE10

UOM_MDC
parameter
Parameter

UCUM
Name
Name

REFID
Sub-

Skin TP-Skin Cel MDC_TEMP_SKIN 150388 MDC_DIM_DEGC 268192


Temperature

Airway TP-AirW Cel MDC_TEMP_AWAY 150356 MDC_DIM_DEGC 268192


Temperature

Room TP- Cel MDC_TEMP_ROOM 0 MDC_DIM_DEGC 268192


Temperature Room

Myocardial TP-Myo Cel MDC_TEMP_MYO 0 MDC_DIM_DEGC 268192


Temperature

Core TP-Core Cel MDC_TEMP_CORE 150368 MDC_DIM_DEGC 268192


Temperature

Surface TP-Surf Cel MDC_TEMP_BODY 150364 MDC_DIM_DEGC 268192


Temperature

Entropy Suppression BURST % MDC_EEG_PAROX_CRT 155024 MDC_DIM_PERC 262688


Ratio SUPPRE X_BURST_SUPPRN ENT
SSION
RATIO

Response RE {unitles MDC_EEG_ENTROPY_RE 0 MDC_DIM_DIML 262656


Entropy s} 1 SPONSE ESS

State Entropy SE {unitles MDC_EEG_ENTROPY_ST 0 MDC_DIM_DIML 262656


s} 1 ATE ESS

44 2062665-001 H
HL7 Data Segment Definitions: Supported parameters

B Abbreviations

2062665-001 H 45
HL7 Data Segment Definitions: Abbreviations

Abbreviations
Abbreviations and symbols which you may encounter while reading this manual
or using the monitor HL7 application are listed below with their meanings.

Abbreviation Definition
A

ACK acknowledgment code


Addr, AD address
ADT Admit, discharge, transfer
ASCII American Standard Code for
Information Interchange
ADD Addendum
C

CCG Centricity Clinical Gateway


CE coded entry
CHAR character
Chg change
CIS Clinical Information System
CK Composite ID with check digit
CM composite
CN composite name
CQ composite quantity with units
CV cardiovascular
D

DT date
E

ECG, EKG electrocardiogram


F

FTP File Transfer Protocol


FAQs Frequently Asked Questions
H

HL7 Health Level Seven standard interface


HIS Hospital Information System
I

ID identification
IS Information Systems
ITPS Information Technologies Professional Services
K

1K 1024 bytes
L

Lic license

46 2062665-001 H
HL7 Data Segment Definitions: Abbreviations

MRG Merge Segment


MSH Message Segment Header
MSA Message Segment Acknowledgment
N

Nno
NACK negative acknowledgment code
NM numeric
Num number
O

OBR observation request


Obs observation
OBX observation result
O optional
P

PDM Patient Data Model


PN part number, person name
PID Patient Identification
PV1 Patient Visit
Q

QRD Query Definition


R

Req request
Req. Field required field
Rev revision
S

Seq sequence
ST string data
T

TCP/IP Transmission Control Protocol/Internet


Protocol
TN telephone number
TS time stamp
U

U unknown
Y

Y/O yes/optional
Y/R yes/required
Y yes

2062665-001 H 47
HL7 Data Segment Definitions: Abbreviations

48 2062665-001 H
Asian Headquarters
GE Medical Systems
GE Medical Systems GE Medical Systems
Information Technologies Asia
Information Technologies, Inc. Information Technologies GmbH
1 Huatuo Road
8200 West Tower Avenue Munzingerstrasse 5
Zhangjiang Hi-tech Park Pudong
Milwaukee, WI 53223 USA 79111 Freiburg
Shanghai, P.R. China, 201203
Tel:+ 1 414 355 5000 Germany
Tel: + 86 21 3877 7888
1 800 558 5120 (US only) Tel: + 49 761 45 43 - 0
Fax: + 86 21 3877 7451
Fax:+ 1 414 355 3790 Fax: + 49 761 45 43 - 233

GE Medical Systems Information Technologies, a General Electric Company, going to market as


GE Healthcare
www.gehealthcare.com

0459

You might also like