28 2062665-001 G
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
To Next Page
Loading...
Need help?
General