Download:
pdf |
pdfOMB NO. 0920-0004
Abbreviation
Segment
Definition
• Three-character code for the segment and the abstract syntax (e.g., the
square and curly braces). Note that for segment groups there is no segment
code present, but the square and curly braces will still be present.
• [ XXX ]
Optional
• { XXX }
Repeating
• XXX
Required
• [{ XXX }]
Optional and Repeating
Name
Name of the segment or segment group element.
Usage
Use of the segment for PHLIP. Indicates if the segment is required, optional, or
conditional in a message. Legal values are:
• R – Required. Must always be populated.
• O – Optional.
• C – Conditional. Must be populated based on computable Conditionality
Statement.
• X – Not used.
Cardinality
Minimum and maximum number of times the segment may appear.
• [0..0] Segment never present.
• [0..1] Segment may be omitted and can have, at most, one occurrence.
• [1..1] Segment must have exactly one occurrence.
• [0..n] Segment may be omitted or may repeat up to n times.
• [1..n] Segment must appear at least once, and may repeat up to n times.
• [0..*] Segment may be omitted or repeat an unlimited number of times.
• [1..*] Segment must appear at least once, and may repeat unlimited number
of times.
• [m..n] Segment must appear at least m and at most n times.
Description
Explanation of the use of the segment.
1.1 HL7 V2.3.1 MESSAGE ORU^R01 SYNTAX
The 2.3.1 version ORU^R01 abstract message has been constrained
for PHLIP Influenza Test Result Reporting as follows:
TABLE 5-2. HL7 V2.3.1 MESSAGE ORU^R01 SYNTAX
Segmen
Seg
men
tt
Name
HEADER Begin
Usage Cardinality
R
Description
[1..1]
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
MSH
Message Header
R
[1..1]
The Message Header (MSH) Segment
contains information explaining how to
parse and process the message. This
includes identification of message
delimiters, sender, receiver, message
type, timestamp, etc.
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
OMB NO. 0920-0004
TABLE 5-2. HL7 V 2.3.1 MESSAGE ORU^R01 SYNTAX
Segmen t
Name
Usage Cardinality
Description
HEADER End
PATIENT GROUP Begin R
[1..1]
The Patient Group is required for
PHLIP. This is a deviation from the
HL7 Version 2.3.1 standard.
PID
Patient Identification
R
[1..1]
The Patient Identification (PID)
segment contains patient identifying
and demographic information. The PID
is required for PHLIP.
[NK1]
Next-of-Kin/
Associated Parties
O
[0..1]
The Next-of-Kin/Associated Parties
(NK1) segment contains the
relationship information of patient and
others. If the subject of the testing is
something other than a person, the
NK1 will document the person or
organization responsible for, or owning,
the subject. For patients who are
persons, the NK1 documents the next
of kin of the patient.
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the NK1 Segment can be
used to carry any associated party’s
related comments.
R
[1..*]
The Order_ObservationOrder
Observation group is required and
may repeat. This means that multiple
test results may be reported on a
single specimen.
The Common Order (ORC) segment
identifies basic information about the
order for testing of the specimen. This
segment includes identifiers for the
order, who placed the order,
whenorder when it was placed, etc.
[NTE]
PATIENT GROUP End
ORDER_OBSERVATIO
N
Begin
[ORC]
Common Order
O
[0..1]
OBR
Observation Request
R
[1..1]
The Observation Request (OBR)
segment is used to capture information
about a single test being performed on
the specimen, or to report information
about patient and specimen.
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the OBR Segment can be
used to carry any order-related
comments.
[NTE]
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted Table
OMB NO. 0920-0004
TABLE 5-2. HL7 V2.3.1 MESSAGE ORU^R01 SYNTAX
SegmenS
egme
nt t
{
Name
Usage Cardinality
OBSERVATION Begin R
Description
[1..*]
For PHLIP, the Observation group is
required in the ORU^R01 message.
This is a deviation from the HL7
Version 2.3.1 standard.
OBX
Observation/Result
R
[1..1]
The Observation/Result (OBX)
segment following the OBR is used for
observations regarding the test
ordered. For instance, this may be
used to capture test results, the
specimen identifying information, and
epidemiologically important information
regarding the case diagnosis, such as
patient vaccination history, travel
history, treatment history, etc. For
PHLIP, the OBX is required in the
ORU^R01 message. This is a
deviation from the HL7 Version 2.3.1
standard.
[NTE]
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the OBX segment can be
used to carry any observation-related
comments.
}
OBSERVATION End
ORDER_OBSERVATIO
N
End
}
1.2 SEGMENT PROFILE ATTRIBUTES
Fields or components that are NOT documented in this guide are
considered NOT SUPPORTED. Inclusion of any field or component
that is not supported will result in the creation of an error message.
The abbreviated terms and their definitions used in the ORU^R01
segment profile are detailed in the following table.
TABLE 5-3. SEGMENT PROFILE ATTRIBUTES
Abbreviation
Seq
Definition
Sequence of the elements as they are numbered in the HL7 segment.
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted Table
OMB NO. 0920-0004
TABLE 5-3. SEGMENT PROFILE ATTRIBUTES
Abbreviation
Definition
Len
PHIN maximum length of the element. Length of an element is calculated using the
following rules:
Field length = (Sum of all supported component lengths) + (component number of
the last supported component) – 1.
Component length = (Sum of all supported sub-component lengths) + (subcomponent number of the last supported component) – 1.
Lengths should be considered recommendations, not absolutes. The receiver can
truncate fields, components and sub-components that are longer than the
recommended length. The receiver should continue to process a message even
when a field, component, or sub-component length exceeds the maximum
recommended length identified in this specification.
DT
Data type used by PHIN for HL7 element.
Indicator whether a data element is required, optional, or conditional in a message.
Legal values are:
•
R
Required. Must always be populated. May use “” (two sets
of quote marks) for a null value if no specific value is delineated in the
Description column of the table.
•
RE1
Required, but may be empty (no values, no quotes)
•
O
Optional.
•
C
Conditional, must be populated, when condition is met, must be
empty if condition is not met.
•
CE
Conditional, must be populated, but may be empty when
condition is met, must be empty if condition is not met,
•
X Not used.
Usage
Note: A required field in an optional segment does not mean the segment must be
present in the message. It means that if the segment is present, the required
fields within that segment must be populated. The same applies to required
components of optional fields. If the field is being populated, then the required
components must be populated. The same applies to required sub-components
of optional components. If a component is being populated, then the required
sub-components of that component must be populated.
1
The element may be missing from the message, but must be sent by sending application if
there is relevant data. A conforming sending application must be capable of providing all ‘RE’
elements. If conforming sending application knows required values for the element, it must
send that element. If conforming sending application does not know the required values, then
that element will be omitted.
Receiving applications will be expected to process (save/print/archive, etc.) or ignore data
contained in the element, but must be able to successfully process the message if the element
is omitted (no error message should be generated because the element is missing).
Health Level Seven, Version 2.5, July 2003, Section 2.12.6.2
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
OMB NO. 0920-0004
TABLE 5-3. SEGMENT PROFILE ATTRIBUTES
Abbreviation
Definition
Cardinality
Minimum and maximum number of times the segment may appear.
• [0..0] Segment never present.
• [0..1] Segment may be omitted and can have, at most, one occurrence.
• [1..1] Segment must have exactly one occurrence.
• [0..n] Segment may be omitted or may repeat up to n times.
• [1..n] Segment must appear at least once, and may repeat up to n times.
• [0..*] Segment may be omitted or repeat an unlimited number of times.
• [1..*] Segment must appear at least once, and may repeat unlimited number
of times.
•
[m..n] Segment must appear at least m and at most n times.
Value Set Name
Pre-coordinated tables used in public health messages, accessible via the Public
Health Information Network Vocabulary Access and Distribution Services at
http://www.cdc.gov/PhinVSBrowser/StrutsController.do.
HL7 Tbl
The HL7 table number as defined in the HL7 V2.3.1 (1999) standard.
Element Name
Descriptive name of the data element.
Description
Explanation of the use of the field/component/sub-component.
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
OMB NO. 0920-0004
1.3 MESSAGE HEADER (MSH) SEGMENT LEVEL PROFILE
The MSH Segment is used to define the intent, source, destination, and some specifics of the syntax of the message.
This segment includes identification of message delimiters, sender, receiver, message type, timestamp, etc. The
message header is required for the test result message.
TABLE 5-4. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
1
1
ST
R
[1..1]
Field Separator
Character to be used as the field separator for the rest
of the message. The supported value is |, ASCII (124).
2
4
ST
R
[1..1]
Encoding Characters
Literal value: ‘ ^~\&’.
3
224
HD
O
[0..1]
Sending Application
Field that may be used to uniquely identify the sending
application for messaging purposes. If populated, it will
contain an OID that represents the sending application
instance. For this version of PHLIP, the sending
application will be the name and OID from the state
that is sending the message.
3.1
20
IS
RE
[0..1]
Namespace ID
Laboratory information system name.
3.2
199
ST
R
[1..1]
Universal ID
OID.
3.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’.
4
224
HD
R
[1..1]
Sending Facility
Unique identifier of the facility that sends the message.
The sending facility must be part of the PHIN OID
registry. For this version of PHLIP, the sending facility
will be the name and OID from the state that is sending
the message.
4.1
20
IS
RE
[0..1]
Namespace ID
Laboratory name.
4.2
199
ST
R
[1..1]
Universal ID
OID.
OMB NO. 0920-0004
TABLE 5-4. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
4.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’
5
224
HD
O
[0..1]
Receiving Application
Unique identifier of the receiving application for
messaging purposes. If populated, it will contain an
OID that represents the receiving application instance.
For this version of PHLIP, the receiving application will
always be the CDC application, as denoted in MSH-5.1
and MSH-5.2.
5.1
20
IS
RE
[0..1]
Namespace ID
Laboratory information system name.
Literal value: ‘US WHO Collab LabSys’
5.2
199
ST
R
[1..1]
Universal ID
Literal value: ‘2.16.840.1.114222.4.3.3.7’
5.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’.
6
224
HD
R
[1..1]
Receiving Facility
Unique identifier of the facility that is to receive the
message. This unique identifier must be part of the
PHIN OID registry. For this version of PHLIP, the
receiving facility will always be the CDC facility, as
denoted in MSH-6.1 & MSH-6.2.
6.1
20
IS
RE
[0..1]
Namespace ID
Laboratory name.
Literal value: ‘CDC–EPI Surv Branch’
6.2
199
ST
R
[1..1]
Universal ID
Literal value: ‘2.16.840.1.114222.4.1.10416’
6.3
3
ID
R
[1..1]
Universal ID Type
`Literal value: ‘ISO’
7
26
TS
R
[1..1]
Date/Time of Message Date and time the message was created by the
sending system. The user inputs values for the field
only as far as needed. When a system has only a
partial date/time, e.g., month, day, and year, but not
hour and minute, the missing values may be
interpreted as zeros.
OMB NO. 0920-0004
TABLE 5-4. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
7.1
24
DTM R
[1..1]
Time
YYYY[MMDD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ],
where at least the first fourteen are used to specify to a
precision of "second.”
The time zone (+/-ZZZZ) is represented as +/-HHMM
offset from Coordinated Universal Time (UTC)
(formerly Greenwich Mean Time [GMT]), where +0000
or -0000 both represent UTC (without offset).
It is strongly recommended that the time zone be used
in PHIN messaging.
9
7
CM
R
[1..1]
Message Type
Literal value: ‘ORU^R01’.
9.1
3
ID
R
[1..1]
Message Code
Literal value: ‘ORU’. Null flavors are not allowed.
9.2
3
ID
R
[1..1]
Trigger Event
Literal value: ‘R01’. Null flavors are not allowed.
9.3
3
ID
?
?
Message Structure
Literal value: ‘ORU_R01’. Null flavors are not allowed.
10
30
ST
R
[1..1]
Message Control ID
String that uniquely identifies the message instance
from the sending application. Recommended to use a
counter.
11
3
PT
R
[1..1]
12
60
VID
R
[1..1]
Version ID
Literal value: "2.3.1."
21
424
EI
R
[1..1]
Message Profile
Identifier
Field used to reference or assert adherence to a
message profile.
Message profiles contain detailed explanations of
grammar, syntax, and usage for a particular message
or set of messages.
Processing ID
Processing ID
(HL7)table# HL70103
Indicator of the intent for processing the message,
such as "T" - training, "D" - de-bugging, or "P" production. For PHLIP, this field will always contain
"P."
OMB NO. 0920-0004
TABLE 5-4. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
21.1
199
ST
R
[1..1]
Entity Identifier
Literal value: ‘PHLIP_ORU_v1.0.2’
21.2
20
IS
RE
[1..1]
Namespace ID
Recommended value: ‘PHIN_Profile_ID’.
21.3
199
ST
R
[1..1]
Universal ID
First instance literal value: ‘2.16.840.1.114222.4.10.3’.
21.4
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’
Constrained HL7
table #301
1.4 PATIENT IDENTIFICATION (PID) SEGMENT LEVEL PROFILE
The PID Segment is used as the primary means of communicating patient identification information. This segment
contains pertinent patient identifying and demographic information. The PID Segment is required in the patient group.
For PHLIP, the patient group is required. If the message sender has detailed patient information, and that information
is needed/required by the message receiver, this patient group will be used. For the PHLIP influenza test result
message, only one PID Segment is expected per message. If the message sender does not have sufficient
information to construct a legal PID Segment, such as a patient name and patient ID, the message sender should
send the default data as noted in the Description column, below.
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
1
4
SI
R
3
564
CX
R
Cardinality
[1..1]
[1..*]
Value Set
Name
Element Name
Description
Set ID - PID
Literal value: "1."
Patient Identifier List
This field contains the list of identifiers (one or more)
used by the facility to uniquely identify a
patient (e.g., medical record number, billing number,
birth registry, national unique individual identifier,
etc.)
OMB NO. 0920-0004
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
3.1
Len
30
Dt
ST
Usage
R
Cardinality
Value Set
Name
[1..1]
Element Name
Patient ID
Description
. The assigning authority is required for PHLIP.
Do NOT send social security numbers at all!
Note: If no Patient ID is available, the Specimen ID
should be defaulted into this field. For PHLIP, the
Specimen ID will be an observation sent in OBX-5
(Observation Value) with a data type of "CX." In
the case where the Specimen ID is used in place
of the Patient ID, it should also be a separate
OBX.
3.4
252
HD
R
[1..1]
Assigning Authority
3.4.1
48
IS
O
[0..1]
Namespace ID
3.4.2
199
ST
R
[1..1]
Universal ID
OID.
3.4.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’.
3.5
25
IS
R
[1..1]
3.6
252
HD
O
[0..1]
Assigning Facility
3.6.1
48
IS
R
[1..1]
Namespace
3.6.2
199
ST
R
[1..1]
Universal ID
OID.
3.6.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’.
Identifier Type
Composite value set:
values from HL7
table# 203 or
PHVS_IdentifierType
_CDC
Entity that assigned the Identifier.
Identifier Type Code
Facility that assigned the Identifier.
OMB NO. 0920-0004
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
5
236
XPN R
[0..*]
Patient Name
Do not send patient name - the default value for this field
SHALL be:
The 1st repeat of PID-5 empty. The 2nd repeat shall
contain an “S” (code for pseudonym) in the Name Type
Code component (~^^^^^^S)
7
26
TS
RE
[0..1]
Date/Time of Birth
Patient's date and time of birth.
8
1
IS
RE
[0..1]
Administrative Sex
(HL7) table# 1
Sex
Patient's sex.
10
703
CE
RE
Race
Patient's race(s).
10.1
50
ST
C
[0..1]
Race Category
( PHVS_Race_CDC)
Identifier
Standardized code.
Rule of conditionality: The standard code component is
mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
10.2
100
ST
O
[0..1]
Text
Standardized description.
10.3
199
ID
C
[0..1]
10.4
50
ST
C
[0..1]
[0..*]
Coding System (HL7) Name of Coding
table# 396
System
Alternate Identifier
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system identifier
is always required if there is a value in component 1.
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
OMB NO. 0920-0004
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
10.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
10.6
199
ID
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
11
608
XAD RE
[0..*]
Patient Address
Residence address of the patient.
If multiple patient addresses are sent, the 1st repeat
should contain the patient’s primary address.
Note: If the state is not sent in the message, the
receiver should default the sending system’s state
in PID-11.4.
11.1
100
ST
RE
[0..1]
Street Address
11.2
100
ST
RE
[0..1]
Other Designation
11.3
100
ST
RE
[0..1]
11.4
20
ST
RE
[0..1]
11.5
10
ST
RE
[0..1]
11.6
100
ID
RE
[0..1]
City
State (FIPS_5-2)
State or Province
Zip or Postal Code
Country
Country
(PH_Country_ISO_31
66-1)
Reference the FIPS 5-2 alpha codes here, though this
is not a coded field, so no coding system will be
identified.
US Zip Codes, Zip+4 and Canadian Postal Codes will
be supported.
OMB NO. 0920-0004
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
11.7
20
ID
RE
[0..1]
11.8
50
ST
RE
[0..1]
11.9
100
IS
RE
[0..1]
22
703
CE
RE
[0..1]
22.1
50
ST
C
[0..1]
22.2
100
ST
O
[0..1]
22.3
199
ID
C
[0..1]
22.4
50
ST
C
[0..1]
Value Set
Name
Address Type (HL7)
table# 190
Element Name
Description
Address Type
Other Geographic
Designation
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bulletins
/fy2007/b07-01.pdf
County
County/Parish
(PH_County_FIPS_64)
Ethnic Group
Ethnicity Group
Identifier
(PHVS_Ethnicity_CD
C) including Unknown
(subset of
PH_NullFlavor_HL7_
V3)
Coding system (HL7)
table 0396
Field that defines the patient as Hispanic, Non-Hispanic
or Unknown.
Standardized code.
Rule of conditionality: The standard code component is
mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
Text
Standardized description.
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system identifier
is always required if there is a value in component 1.
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
OMB NO. 0920-0004
TABLE 5-5. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
22.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is Coded.
Rule of conditionality: Required if no standardized
code or local code value passed.
22.6
199
ID
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
29
26
TS
RE
[0..1]
Patient Death Date
and Time
Date and time of patient’s death, if the patient is known
to be deceased at the time of the message.
30
1
ID
RE
[0..1]
Yes No Indicator
(HL7)table# 136
Patient Death Indicator Indicator (Y) of patient’s death, ifdeath if the patient is
known to be deceased at the time of the message. If
unknown, this field should be empty (no value, no
quotes).
1.5 NEXT OF KIN/ASSOCIATED PARTIES (NK1) SEGMENT LEVEL PROFILE
The NK1 Segment contains information regarding the patient's other related parties.
TABLE 5-6. NEXT OF KIN/ASSOCIATED PARTIES (NK1) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
1
4
SI
2
236
XPN RE
R
Cardinality
Value Set
Name
Element Name
Description
[1..1]
Set ID - NK1
Literal Value: "1."
[0..1]
Name
Name of the next of kin or associated party.
OMB NO. 0920-0004
TABLE 5-6. NEXT OF KIN/ASSOCIATED PARTIES (NK1) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
2.1
50
ST
R
[1..1]
Last Name
2.2
50
ST
R
[1..1]
First Name
2.3
50
ST
RE
[0..1]
Middle Initial/Middle
Name
2.4
20
ST
RE
[0..1]
Suffix
2.5
20
ST
RE
[0..1]
2.6
20
IS
RE
[0..1]
Degree License
Certification (HL7)
table# 360
Degree
2.7
20
ID
RE
[0..1]
Name Type (HL7)
table# 200
Name Type Code
3
703
CE
RE
[0..1]
3.1
50
ST
C
[0..1]
3.2
100
ST
O
[0..1]
3.3
199
ID
C
[0..1]
Description
Prefix
Relationship (HL7)
table# 63
Relationship
Description of the relationship between the next of
kin/related party and the patient.
Identifier
Standardized code.
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
Text
Standardized description.
Coding system (HL7) Name of Coding
table# 0396
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
OMB NO. 0920-0004
TABLE 5-6. NEXT OF KIN/ASSOCIATED PARTIES (NK1) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
3.4
50
ST
C
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
3.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is Coded.
Rule of conditionality: Required if no standardized
code or local code value passed.
3.6
199
ID
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
4
608
XAD O
[0..*]
Address
The address of the next of kin/associated party.
If multiple addresses are sent, the 1st repeat should
contain the next of kin’s primary address.
Note: If the state is not sent in the message, the
receiver should default the sending system’s
state in NK1-4.4
4.1
100
ST
O
[0..1]
Street Address
4.2
100
ST
O
[0..1]
Other Designation
4.3
100
ST
O
[0..1]
4.4
20
ST
RE
[0..1]
City
State (FIPS_5-2)
State or Province
Reference the FIPS 5-2 alpha codes here, though this
is not a coded field, so no coding system will be
identified.
OMB NO. 0920-0004
TABLE 5-6. NEXT OF KIN/ASSOCIATED PARTIES (NK1) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
4.5
10
ST
O
[0..1]
4.6
100
ID
O
[0..1]
Country
Country
(PH_Country_ISO_31
66-1)
4.7
20
ID
RE
[0..1]
Address Type (HL7)
table# 190
4.8
50
ST
O
[0..1]
4.9
100
IS
O
[0..1]
Zip or Postal Code
Description
US Zip Codes, Zip+4 and Canadian Postal Codes will
be supported.
Address Type
Other Geographic
Designation
County
County/Parish
(PH_County_FIPS_64)
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bulletin
s/fy2007/b07-01.pdf
http://www.census.gov/geo/www/fips/
fips.html
1.6 COMMON ORDER (ORC) SEGMENT LEVEL PROFILE
The ORC Segment is used to transmit test order information. This segment includes identifiers for the order, who
placed the order, whenorder when it was placed, etc. The ORC Segment is optional in the Test Result (ORU)
message. Any information that could be included in either the ORC or the OBR must be included in the OBR on
reporting.
TABLE 5-7. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Seq
1
Len
2
Dt
ID
Usa ge Cardi
nality
R
[1..1]
Value Set
Name
Order Control
Code (HL7)
table# 119
Element Name
Order Control
Description
Order action to be performed with this specific
order message. For the PHLIP result message,
"RE" (observations to follow) is used.
Formatted Table
OMB NO. 0920-0004
TABLE 5-7. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
2
255
EI
RE
[0..1]
Placer Order
Number
2.1
30
ST
R
[1..1]
Entity Identifier
2.2
20
IS
RE
[0..1]
Namespace ID
Assigning authority.
2.3
199
ST
R
[1..1]
Universal ID
Field required to contain an assigning authority
OID for the application/ organization responsible
for creating the placer order number. The placer
order number is expected to be unique within this
assigning authority.
2.4
3
ID
RE
[0..1]
Universal ID type
Literal value: ‘ISO’.
3
255
EI
R
[1..1]
Filler Order Number
Order number associated with the filling
application.
Note: The same value is populated in ORC.3 and
OBR.3.
3.1
30
ST
R
[1..1]
Entity Identifier
3.2
20
IS
RE
[0..1]
Namespace ID
3.3
199
ST
RE
[0..1]
Universal ID
Field required to contain an assigning authority
OID for the application/organization responsible
for creating the filler order number. The filler
order number is expected to be unique within this
assigning authority.
3.4
3
ID
RE
[0..1]
Universal ID Type
Literal value: ‘ISO’.
5
2
ID
RE
[0..1]
Order Status
Status of an order.
Order Status (HL7) table# 38
Unique identifying number assigned to the test
request or order by the system that initiated the
request for performance of the test.
Note: The same value is populated in ORC.2 and
OBR.2.
OMB NO. 0920-0004
TABLE 5-7. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
21
50
XON RE
[0..1]
Ordering Facility
Name
21.1
50
ST
R
[1..1]
Organization Name
22
608
XAD
RE
[0..*]
Ordering Facility
Address
22.1
100
ST
O
[0..1]
Street Address
22.2
100
ST
O
[0..1]
Other Designation
22.3
100
ST
O
[0..1]
22.4
20
ST
R
[1..1]
22.5
10
ST
O
[0..1]
22.6
100
ID
O
[0..1]
Country
(PH_Country_ISO_3166-1)
Country
22.7
20
ID
RE
[0..1]
Address Type (HL7) table#
190
Address Type
22.8
50
ST
O
[0..1]
Description
Name of the facility that placed the order.
Address of the facility that placed the order.
If multiple addresses are sent, the 1st repeat
should contain the ordering facility’s primary
address.
Note: If the state is not sent in the message, the
receiver should default the sending
system’s state in ORC-22.4.
City
State (FIPS_5-2)
State or Province
Reference the FIPS 5-2 alpha codes here
Zip/Postal Code
US Zip Codes, Zip+4 and Canadian Postal Codes
will be supported.
Other Geographic
Designation
May be used for MSAs (Metropolitan and
Micropolitan Statistical Areas). Source:
http://www.whitehouse.gov/omb/bull
etins/fy2007/b07-01.pdf
OMB NO. 0920-0004
TABLE 5-7. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
County (PH_County_FIPS_64)
Element Name
22.9
100
IS
RE
[0..1]
23
211
XTN
RE
[0..*]
23.2
20
ID
RE
[0..1]
Telecommunication Use Code
(HL7) table# 201
23.3
100
ST
RE
[0..1]
Telecommunication Equipment Telecom Equipment
Type (HL7) table# 202
Type
23.4
20
ST
RE
[0..1]
Email Address
23.5
3
NM
RE
[0..1]
Country Code
23.6
3
NM
RE
[0..1]
Area Code
Description
County/Parish
Ordering Facility
Phone Number
Telephone number of the facility placing the
order. The receiver must minimally support the
1st repeat when populating this field.
Email address, if sent, is a separate "repeat" with
appropriate Telecommunication Use Code and
Telecommunication Equipment Type.
Telecom use code
Example of email address format: [email protected]
Look-up service for area codes:
http://www.nanpa.com/nas/public/np
a_query_step1.do?
method=resetNpaReportModel
23.7
17
NM
RE
[0..1]
Phone Number
23.8
20
NM
RE
[0..1]
Extension
23.9
20
ST
RE
[0..1]
Any Text
OMB NO. 0920-0004
1.7 OBSERVATION REQUEST (OBR) SEGMENT LEVEL PROFILE
The OBR Segment in the Test Result Message (ORU) is used to capture information about one test being performed
on the specimen or report information about patient and specimen.
Note: For PHLIP, only one specimen is allowed per ORU^R01 message.
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
1
4
SI
R
[1..1]
Set ID - OBR
Sequence number of the OBR in relation to the Result
message to which it refers. The sequence number
should start at 1 and be incremented by 1 for each
OBR in the result message.
2
255
EI
RE
[0..1]
Placer Order Number
Unique identifying number assigned to the test request
or order by the system that initiated the request for
performance of the test.
Note: The same value is populated in ORC.2 and
OBR.2.
2.1
30
ST
R
[1..1]
Entity Identifier
2.2
20
IS
RE
[0..1]
Namespace ID
Assigning authority.
2.3
199
ST
R
[1..1]
Universal ID
Field required to contain an assigning authority OID for
the application/ organization responsible for creating
the placer order number. The placer order number is
expected to be unique within this assigning authority.
2.4
3
ID
RE
[0..1]
Universal ID Type
Literal value: ‘ISO’.
3
255
EI
R
[1..1]
Filler Order Number
Order number associated with the filling application.
Note: The same value is populated in ORC.3 and
OBR.3.
3.1
30
ST
R
[1..1]
Entity Identifier
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
3.2
20
IS
RE
[0..1]
Namespace ID
3.3
199
ST
RE
[0..1]
Universal ID
Field required to contain an assigning authority OID for
the application/organization responsible for creating the
filler order number. The filler order number is expected
to be unique within this assigning authority.
3.4
3
ID
RE
[0..1]
Universal ID Type
Literal value: ‘ISO’.
4
643
CE
R
[1..1]
Universal Service ID
Identifier code for the test. This will be used to pass
PHLIP orderable test codes.
4.1
20
ST
C
[0..1]
Lab Test Order
Identifier
(PHLIP Flu)
(Composite value set:
values from LOINC
and PLT)
4.2
100
ST
O
[0..1]
4.3
199
ID
C
[0..1]
4.4
20
ST
C
[0..1]
Text
Coding system (HL7) Name of Coding
table# 0396
System
Alternate Identifier
Standardized code.
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
Standardized description.
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
4.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
4.6
199
ID
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
7
26
TS
R
[1..1]
Observation Date/Time The date and time the specimen was collected.
A minimum of year, month and day must be provided
when the actual date/time is known. For unknown
collection date/time use "0000".
10
337
XCN O
[0..1]
Collector Identifier
10.1
100
ST
O
[0..1]
ID Number
10.2
50
ST
O
[0..1]
Family Name
10.3
50
ST
O
[0..1]
Given Name
10.4
50
ST
O
[0..1]
Middle Name/Initial
10.5
20
ST
O
[0..1]
Suffix
10.6
20
ST
O
[0..1]
Prefix
10.7
20
IS
O
[0..1]
Degree
10.10
20
IS
O
[0..1]
Name Type Code
This field will identify the person, department or facility
that collected the specimen.
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
14
26
TS
RE
[0..1]
Specimen Received
Date/Time
Date and time specimen is received at the submitter.
15
1060
CM
R
[1..1]
Specimen Source
Identifier of the type and/or source of specimen on
which a test is performed.
15.1
703
CE
R
[1..1]
Specimen Source
Name or Code
Identifier of the type and/or source of specimen on
which a test is performed. The SNOMED CT specimen
concepts will not be used to encode this component in
PHLIP. For this version of PHLIP, the HL7 table 0070
will be used as the reference table for OBR 15.1.
If specimen source is not known, enter the HL7 table
0070 item: "USUB” and "Unknown substance" in the
sub-components OBR-15.1.1 & 15.1.2, respectively.
15.1.1
50
ST
R
[1..1]
Identifier
Standardized code.
The standard code sub-component is mandatory
unless there is no standard to match the local value
passed by the application. An attempt will be made by
the sender to map the local value to the standard. If
the specimen source is not listed in table 0070, enter
"ORH" and "Other" in sub-components 15.1.1 & 15.1.2,
with the description of the specimen source in subcomponent 15.1.5 (Alternate Text).
15.1.2
100
ST
O
[0..1]
Text
Standardized description.
Specimen Source
(HL7) table#70
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Coding system (HL7) Name of Coding
table# 0396
System
Description
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
15.1.3
199
ID
R
[1..1]
15.1.4
50
ST
C
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code sub-component
is mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in sub-component 5.
15.1.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if standard code
(15.1.1) is “ORH” .
15.1.6
199
ID
C
[0..1]
15.4
354
CE
O
[0..1]
Coding system (HL7) Name of Alternate
table# 0396
Coding System
Body Site
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
For PHLIP, the 1st 3 sub-components of 15.4 are not
supported. The local information will be entered in the
Alternate Text sub-component OBR-15.4.5
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
15.4.4
50
ST
C
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code sub-component
is mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in sub-component 5.
15.4.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
15.4.6
199
ID
C
[0..1]
Coding system (HL7) Name of Alternate
table# 0396
Coding System
16
591
XCN RE
[0..1]
Ordering Provider
16.1
100
ST
RE
[0..1]
Ordering Provider ID
16.2
50
ST
RE
[0..1]
Last Name
16.3
16.4
50
50
ST
ST
RE
RE
[0..1]
[0..1]
First Name
Middle Initial/Middle
Name
16.5
20
ST
RE
[0..1]
Suffix
16.6
20
ST
RE
[0..1]
Prefix
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
Identifier of the provider who ordered the testing being
performed.
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Degree License
Certification (HL7)
table# 360
Element Name
Description
16.7
20
IS
RE
[0..1]
16.9
252
HD
O
[0..1]
Assigning Authority
16.9.1
48
IS
R
[1..1]
Namespace ID
16.9.2
199
ST
R
[1..1]
Universal ID
OID.
16.9.3
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’
16.10
20
ID
RE
[0..1]
17
211
XTN RE
[0..*]
17.2
20
ID
RE
[0..1]
Telecommunication
Use Code (HL7)
table# 201
Telecom Use Code
17.3
100
ST
RE
[0..1]
Telecommunication
Equipment Type
(HL7) table# 202
Telecom Equipment
Type
17.4
20
ST
RE
[0..1]
Email Address
17.5
3
NM
RE
[0..1]
Country Code
Name Type (HL7)
table# 200
Degree
Entity that assigned the ID.
Name Type Code
Order Callback Phone
Number
Phone number that can be called to obtain additional
clarification regarding the order.
Note: The receiver must minimally support the 1st
repeat when populating this field.
Email address, if sent, is a separate "Repeat" with
appropriate Telecommunication Use Code and
Telecommunication Equipment Type.
Example of email address format: [email protected]
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
17.6
Len
3
Dt
NM
Usage
RE
Cardinality
Value Set
Name
[0..1]
Element Name
Area Code
Description
Look-up service for area codes:
http://www.nanpa.com/nas/public/npa_qu
ery_step1.do?
method=resetNpaReportModel
17.7
17
NM
RE
[0..1]
Phone Number
17.8
20
NM
RE
[0..1]
Extension
17.9
20
ST
RE
[0..1]
Any Text
22
26
TS
RE
[0..1]
Results Rpt/Status
Change - Date/Time
Date/time the results were reportedreported, or status
changed.
25
1
ID
R
[1..1]
Result Status
Status of results for this order.
Corrected Results: A corrected result occurs when a
previously final result report (i.e., an OBR and
associated OBXs where OBR-25 was Final and all
OBX-11s were Final) is being resent with a change to a
value in one or more OBXs.
OBR-25 (Result Status): The status of the entire report
is marked as "C-Corrected" in OBR-25.
OBX-11 (Observation Result Status): The status of
each OBX is marked as either "Final" or "Corrected."
Those OBX values being corrected should have an
OBX-11 status of "C-Corrected." Those OBX values
that remain unchanged should have an OBX-11 status
of "F-Final." A minimum of one OBX must be marked
as corrected.
26
745
CM
RE
[0..1]
Parent Result
Field defined to make it available for linkages between
the parent result and its children result. This important
information, together with the information in OBR.29
Parent, uniquely identifies the OBX Segment of the
Result Status (HL7)
table# 123
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
parent result related to this order.
26.1
623
CE
RE
[0..1]
OBX-3 (Observation
Identifier) of Parent
Result
26.1.1
50
ST
C
[0..1]
Identifier
Standardized code.
Rule of conditionality: The standard code subcomponent is mandatory unless there is no standard to
match the local value passed by the application. An
attempt will be made by the sender to map the local
value to the standard. In the case that no standard
code was found, this field may be blank.
26.1.2
100
ST
O
[0..1]
Text
Standardized description.
26.1.3
199
ID
C
[0..1]
26.1.4
50
ST
C
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code sub-component
is mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in sub-component 5.
26.1.5
199
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
Coding system (HL7) Name of Coding
table# 0396
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
26.1.6
20
ID
C
[0..1]
Coding system (HL7) Name of Alternate
table# 0396
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate identifier
is present.
26.2
20
ST
O
[0..1]
OBX-4 (Sub-ID) of
Parent Result
26.3
100
TX
RE
[0..1]
Part of OBX-5
(Observation Result)
from Parent Result
The description of the organism from OBX-5, which will
have a data type of "ST" or "TX."
29
511
CM
RE
[0..1]
Parent
Parent ID number.
Field that relates a child to its parent when a parentchild relationship exists.
29.1
255
EI
RE
[0..1]
Placer Order Number
of Parent Result
From ORC-2 (Placer Order Number) or OBR-2 (Placer
Order Number) of parent.
29.1.1
30
ST
R
[1..1]
Entity Identifier
29.1.2
20
IS
RE
[0..1]
Namespace ID
29.1.3
199
ST
RE
[0..1]
Universal ID
Field required to contain an assigning authority OID for
the application/organization responsible for creating the
placer order number. The placer order number is
expected to be unique within this assigning authority.
29.1.4
3
ID
RE
[0..1]
Universal ID Type
Literal value: ‘ISO’.
29.2
255
EI
R
[1..1]
Filler Order Number of
Parent Result
From ORC-3 (Filler Order Number) or OBR-3 (Filler
Order Number) of parent.
29.2.1
30
ST
R
[1..1]
Entity Identifier
OMB NO. 0920-0004
TABLE 5-8. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinality
Value Set
Name
Element Name
Description
29.2.2
20
IS
RE
[0..1]
Namespace ID
29.2.3
199
ST
RE
[0..1]
Universal ID
Field required to contain an assigning authority OID for
the application/organization responsible for creating the
filler order number. The filler order number is expected
to be unique within this assigning authority.
29.2.4
3
ID
RE
[0..1]
Universal ID Type
Literal value: ‘ISO’.
1.8 OBSERVATION/RESULT (OBX) SEGMENT LEVEL PROFILE
The OBX Segment in the Test Result (ORU) Message is used to transmit observations related to the test result and
other information about patient and specimen, including test result, specimen-related information (such as specimen
IDs from both the test order and the test filler), additional information passed by the test order, etc.
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
1
4
SI
R
[1..1]
2
3
ID
R
[1..1]
Value Set Name
Value Type (HL7) table# 125
Element Name
Description
Set ID - OBX
Sequence number of the OBX in relation to the
OBR Segment to which it refers. The sequence
number should start at 1 and increment by 1 for
each OBX in the Order_Observation group.
Value Type
Field in which allowed values are "CE," "CX,"
"NM," "SN," "ST," "TS" and "TX." The CE data
type is used primarily to convey epidemiologically
important information and coded lab results like
organism name. The CX data type is used
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
primarily to convey additional specimen identifiers
in OBXs. The NM data type is used to report a
numeric value. The SN data type is used to
report a numeric clinical value with qualifications.
The ST data type is used to report a short string
of text. The TS data type is used to convey the
date/time of illness onset. The TX data type is
used to carry a large text observation.
3
703
CE
R
[1..1]
3.1
50
ST
C
3.2
100
ST
O
Resulted Lab Test Name
(PHLIP Flu) (Composite value
set: values from LOINC and
PLT)
or
PHLIP Questions (Flu)
(Composite value set: values
from LOINC and
PHINQUESTIONS)
Observation
Identifier
Unique identifier for the observation. This field
will be populated by either a resulted test
identifier or an identifier for an observation related
to patient or specimen information (EPI question).
[0..1]
Identifier
Standardized code.
Rule of conditionality: The standard code
component is mandatory unless there is no
standard to match the local value passed by the
application. An attempt will be made by the
sender to map the local value to the standard.
[0..1]
Text
Standardized description.
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” =
LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component
is mandatory if there is no standard to match the
local value passed by the application AND there
is no text present in component 5.
C
[0..1]
Alternate Text
Local description. Note that if the field is
collected as text in the application, this may be
the only field populated if the data type is
"Coded."
Rule of conditionality: Required if no
standardized code or local code value passed.
Not required but recommended to always send
local codes.
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
3.3
199
ID
C
[0..1]
3.4
50
ST
C
3.5
100
ST
3.6
199
ID
Coding system (HL7) table#
0396
Coding system (HL7) table#
0396
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
4
20
ST
CE
5
65536
Varie
Varie
s ssee
belob
elow
w
Varie [0..*]
Varie
ss
by
data
type
5
703
CE
C
Value Set Name
[0..1]
[0..1]
Lab Test Result (PHLIP Flu)
Composite value set: values
from SNOMED CT and PLR)
or
Patient Location Status at
Specimen Collection
(Composite value set:HL7
table# 4 and
PH_HealthcareProviderTaxon
omy_HIPAA)
or
Yes No Unknown (YNU)
Composite value set: values
from Hl7 table#136 and
NullFlavor_HL7_V3
or
Country (ISO_3166-1)
Element Name
Description
Observation Sub-ID
Conditionality Rule: Field required if there is
more than one OBX with the same OBX.3
(Observation Identifier) associated with the same
OBR. Normally, this field is populated with a
number, but text values may also be used.
Observation Value
Actual observation associated with the test order.
The data type in OBX.2 Value Type indicates the
format of the observation.
Observation Value
Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’.
This data type transmits a code and the text
associated with the code.
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
5.1
50
ST
C
[0..1]
5.2
100
ST
O
[0..1]
5.3
199
ID
C
[0..1]
5.4
50
ST
C
5.5
100
ST
C
Value Set Name
Element Name
Description
Identifier
Standardized code.
Rule of conditionality: The standard code
component is mandatory unless there is no
standard to match the local value passed by the
application. An attempt will be made by the
sender to map the local value to the standard. In
the case that no standard code was found, this
field may be blank.
Text
Standardized Description
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” =
LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component
is mandatory if there is no standard to match the
local value passed by the application AND there
is no text present in component 5.
[0..1]
Alternate Text
Local description. Note that if the field is
collected as text in the application, this may be
the only field populated if the value type is
"Coded."
Rule of conditionality: Required if no
standardized code or local code value passed.
Coding system (HL7) table#
0396
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
5.6
199
ID
C
[0..1]
5
285
CX
R
5.1
30
ST
5.4
252
5.4.1
48
5.4.2
5.4.3
5
Value Set Name
Coding system (HL7) table#
0396
Element Name
Description
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
[1..1]
Observation Value
The CX data type is used to carry the specimen
ID from the filler.
R
[1..1]
Specimen ID
The laboratory-generated (local) number that
identifies the specimen related to the test.
Note: PHLIP only supports 1 specimen per
message.
HD
R
[1..1]
Assigning Authority
Entity that assigned the ID.
IS
O
[0..1]
Namespace ID
199
ST
R
[1..1]
Universal ID
OID.
3
ID
R
[1..1]
Universal ID Type
Literal value: ‘ISO’.
65536
TX
C
[0..1]
Observation Value
Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’.
Field using the TX data type to carry a text result
value. Numeric results and numeric results with
units of measure should not be reported as text.
These should be reported as "NM" or "SN" with
the units of measure in OBX-6. The TX data type
is intended for strings longer than 200 characters.
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
5.1
65536
TX
R
[1..1]
Text Data
Text observation in the result message.
5
36
SN
C
[0..1]
Observation Value
Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’.
Test result in structured numeric format (i.e., an
unambiguous expression of numeric clinical
results along with qualifications). Structured
numeric include intervals (^0^-^1), ratios (^1^/^2
or ^1^:^2), inequalities (<^10), or categorical
results (2^+). The units for the structured
numeric value should be reported in OBX-6.
5.1
2
ST
RE
[0..1]
Comparator
5.2
15
NM
R
[1..1]
Num1
5.3
1
ST
RE
[0..1]
Separator/Suffix
5.4
15
NM
RE
[0..1]
Num2
5
16
NM
C
[0..1]
Observation Value
5.1
16
NM
R
[1..1]
Numeric Data
Component that must be one of ‘>‘ or ‘<’ or ‘>=’’
or ‘<=’ or ‘=’ or ‘<>’. If this component is not
valued, it defaults to equal (‘=’).
Component that must be one of ‘-‘ or ‘+’ or ‘/’’ or
‘.’ or ‘:’.
Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’.
Test result in numeric format.
Number consisting of an optional leading sign (+
or -), the digits, and an optional decimal point. In
the absence of a sign, the number is assumed to
be positive. If there is no decimal point, the
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
number is assumed to be an integer.
5
26
TS
R
[1..1]
Observation Value
Contains the test result as a time stamp. The
date portion of the time stamp follows the rules of
a date field (DT), and the time portion follows the
rules of a time field (TM).
5.1
26
TS
R
[1..1]
Date and Time
Field uses the following format:
YYYY[MM[DD[HHMM]]]
Example: 200707060000 for July 6, 2007, 12:00
a.m.
ST
C
[0..*]
Observation Value
Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’.
5
199
Field using the ST data type to carry a short text
result value. Numeric results and numeric results
with units of measure should not be reported as
text. These should be reported as NM or SN,
with the units of measure in OBX-6.
5.1
199
ST
R
[1..1]
String Data
The ST data type is intended for short strings
(e.g., less than 200 characters).
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
6
Len
703
Dt
CE
Usa Cardi
ge nality
C or
CE?
[0..1]
Value Set Name
PH_UnitsOfMeasure_UCUM
(subset of UCUM)
Element Name
Description
Units
Field populated with units of measure if the data
type identified in OBX.2 (and carried in OBX.5) is
""SN." If we use C, then need to explain to use
“1” for any unitless value in OBX.5, for example a
titer.
Identifier
Standardized code.
Rule of conditionality: The standard code
component is mandatory unless there is no
standard to match the local value passed by the
application. An attempt will be made by the
sender to map the local value to the standard. In
the case that no standard code was found, this
field may be blank.
Text
Standardized description.
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” =
LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
Alternate Identifier
Local code.
Rule of conditionality: The local code component
is mandatory if there is no standard to match the
local value passed by the application AND there
is no text present in component 5.
or
Age Unit Composite value set:
values from UCUM
NullFlavor_HL7_V3)
6.1
50
ST
C
[0..1]
6.2
100
ST
O
[0..1]
6.3
199
ID
C
[0..1]
6.4
50
ST
C
[0..1]
Coding system (HL7) table#
0396
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
6.5
100
ST
C
[0..1]
6.6
199
ID
C
[0..1]
7
60
ST
RE
[0..1]
8
5
ID
RE
[0..1]
Value Set Name
Coding system (HL7) table#
0396
Element Name
Description
Alternate Text
Local description. Note that if the field is
collected as text in the application, this may be
the only field populated if the data type is
"Coded."
Rule of conditionality: Required if no
standardized code or local code value passed.
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
References Range
Interpretation range that applies to the value
reported in OBX-5. It should provide enough
information to understand the abnormal flags
reported in OBX.8.
Abnormal Flag (HL7) table# 78 Abnormal Flags
Indicator of the normalcy of the result found in
OBX.5.
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
11
Len
1
Dt
ID
Usa Cardi
ge nality
R
[1..1]
Value Set Name
Observation Result Status
(HL7) table# 85
Element Name
Observation Result
Status
Description
Status of the observation result.
Corrected Results: A corrected result occurs
when a previously final result report (i.e., an OBR
and associated OBXs where OBR-25 was "Final"
and all OBX-11s were Final) is being resent with
a change to a value in one or more OBXs.
OBR-25 (Result Status): The status of the entire
report is marked as "C-Corrected" in OBR-25.
OBX-11 (Observation Result Status): The status
of each OBX is marked as either "Final" or
"Corrected." Those OBX values being corrected
should have an OBX-11 status of "C-Corrected."
Those OBX values that remain unchanged
should have an OBX-11 status of "F-Final." A
minimum of one OBX must be marked as
corrected.
OBX-11 = “N” - Not asked; used to affirmatively
document that the observation identified in the
OBX was not sought when the universal service
ID in OBR-4 implies that it would be sought.
OBX-11 = ‘X” - Results cannot be obtained for
this observation
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
14
26
TS
RE
[0..1]
Date/Time of the
Observation
17
354
CE
RE
[0..1]
Observation Method Identifier of the method used to find the result.
Note: For PHLIP, the 1st 3 components are not
supported. The local information will be entered
in the Alternate Text component OBX-17.5.
17.1
50
ST
C
[0..1]
Identifier
Standardized code.
Rule of conditionality: The standard code
component is mandatory unless there is no
standard to match the local value passed by the
application. An attempt will be made by the
sender to map the local value to the standard. In
the case that no standard code was found, this
field may be blank.
17.2
100
ST
O
[0..1]
Text
Standardized description.
17.3
199
ID
C
[0..1]
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” =
LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
Coding system (HL7) table#
0396
For PHLIP, this field will be used to record the
observation time.
Note: This is a deviation from the HL7 Version
2.3.1 standard, which is the Specimen
Collection Date/Time. In HL7 Version 2.5,
the specimen information has been
expanded. OBX-14 is Specimen Collection
Date/Time; OBX-19 is Date/Time of the
Analysis.
OMB NO. 0920-0004
TABLE 5-9. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Seq
Len
Dt
Usa Cardi
ge nality
Value Set Name
Element Name
Description
17.4
50
ST
C
[0..1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component
is mandatory if there is no standard to match the
local value passed by the application AND there
is no text present in component 5.
17.5
100
ST
C
[0..1]
Alternate Text
Local description. Note that if the field is
collected as text in the application, this may be
the only field populated if the data type is
"Coded."
Rule of conditionality: Required if no
standardized code or local code value passed.
17.6
199
ID
C
[0..1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
Coding system (HL7) table#
0396
OMB NO. 0920-0004
1.9 NOTES AND COMMENTS (NTE) SEGMENT LEVEL PROFILE
The NTE Segment in the test result message can be used to carry comments for the NK1, OBR, and OBX segments.
The NTE segment applies to the entity that immediately precedes it (e.g., order-related comments if it follows the
OBR segment, observation-related comments if it follows the OBX segment).
TABLE 5-10. NOTES AND COMMENTS SEGMENT (NTE) PROFILE – ORU^R01 USAGE
Seq
Len
Dt
Usage
Cardinalit
Cardi
nality
y
1
4
SI
O
[0..1]
2
8
ID
O
[0..1]
3
65536
FT
R
[1..*]
Value Set Name
Element Name
Description
Set ID - NTE
Source of Comment
(HL7) table# 105
Source of Comment
HL7 defined values from Table 0105 of the standard ("L" =
Filler, "P" = Placer, "O" = Other)
Comment
This field uses an FT rather than a TX data type. Since
there is no difference between an FT data type without any
embedded formatting commands, and a TX data type, this
change is compatible with previous versions.
2
HL7 V2.5.1 MESSAGE ORU^R01 SYNTAX
Abbreviation
Segment
Definition
• Three-character code for the segment and the abstract syntax (e.g., the
square and curly braces). Note that for segment groups there is no segment
code present, but the square and curly braces will still be present.
• [ XXX ]
Optional
• { XXX }
Repeating
• XXX
Required
• [{ XXX }]
Optional and Repeating
Name
Name of the segment or segment group element.
Usage
Use of the segment for PHLIP. Indicates if the segment is required, optional, or
conditional in a message. Legal values are:
• R – Required. Must always be populated.
• O – Optional.
• C – Conditional. Must be populated based on computable Conditionality
Statement.
• X – Not used.
Cardinality
Minimum and maximum number of times the segment may appear.
• [0..0] Segment never present.
• [0..1] Segment may be omitted and can have, at most, one occurrence.
• [1..1] Segment must have exactly one occurrence.
• [0..n] Segment may be omitted or may repeat up to n times.
• [1..n] Segment must appear at least once, and may repeat up to n times.
• [0..*] Segment may be omitted or repeat an unlimited number of times.
• [1..*] Segment must appear at least once, and may repeat unlimited number
of times.
• [m..n] Segment must appear at least m and at most n times.
Description
Explanation of the use of the segment.
2.1 HL7 V2.5.1 MESSAGE ORU^R01 SYNTAX
The 2.5.1 version ORU^R01 abstract message has been constrained
for PHLIP Influenza Test Result Reporting as follows:
Segment
TABLE 5-12. HL7 V2.5.1 MESSAGE ORU^R01
SYNTAX
Name
Usage Cardinality
Description
HEADER Begin
MSH
Message Header
R
[1..1]
R
[1..1]
The Message Header (MSH) Segment
contains information explaining how to
parse and process the message. This
includes identification of message
delimiters, sender, receiver, message
type, timestamp, etc.
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
Formatted Table
OMB NO. 0920-0004
TABLE 5-12. HL7 2.5.1 MESSAGE ORU^R01 SYNTAX
Segment
SFT
Name
Software
Usage Cardinality
O
[1..1]
Description
The Software segment provides
additional information about the software
product(s) used as a sending application.
HEADER End
SPECIMEN GROUP
Begin
R
The Patient Group is required for
PHLIP. This is a deviation from the
HL7 Version 2.5.1 standard.
SPM
Specimen Identification
R
[1..1]
The Specimen (SPM) segment describes
the characteristics of a specimen
collected for use in a laboratory test.
NTE
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the SPM Segment can be
used to carry any specimen related
comments.
PATIENT GROUP Begin R
[1..1]
The Patient Group is required for
PHLIP. This is a deviation from the
HL7 Version 2.5.1 standard.
SPECIMEN GROUP End
PID
Patient Identification
R
[1..1]
The Patient Identification (PID)
segment contains patient identifying
and demographic information. The PID
is required for PHLIP.
PV1
Patient Visit
O
[0..1]
The Patient Visit Segment (PV1)
segment is to communicate information
on an account or visit-specific basis.
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the PV1 Segment can be
used to carry any patient visit related
comments.
R
[1..*]
The Order_Observation group is
required and may repeat. This means
that multiple test results may be
reported on a single specimen.
NTE
PATIENT GROUP End
{
ORDER_OBSERVATIO
N
Begin
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted Table
OMB NO. 0920-0004
TABLE 5-12. HL7 2.5.1 MESSAGE ORU^R01 SYNTAX
Segment
Name
Usage Cardinality
Description
[ORC]
Common Order
O
[0..1]
The Common Order (ORC) segment
identifies basic information about the
order for testing of the specimen. This
segment includes identifiers for the
order, who placed the order when it
was placed, etc.
OBR
Observation Request
R
[1..1]
The Observation Request (OBR)
segment is used to capture information
about a single test being performed on
the specimen, or to report information
about patient and specimen.
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the OBR Segment can be
used to carry any order-related
comments.
R
[1..*]
For PHLIP, the Observation group is
required in the ORU^R01 message.
This is a deviation from the HL7
Version 2.5.1 standard.
NTE
{
}
}
OBSERVATION Begin
OBX
Observation/Result
R
[1..1]
The Observation/Result (OBX)
segment following the OBR is used for
observations regarding the test
ordered. For instance, this may be
used to capture test results, the
specimen identifying information, and
epidemiologically important information
regarding the case diagnosis, such as
patient vaccination history, travel
history, treatment history, etc. For
PHLIP, the OBX is required in the
ORU^R01 message. This is a
deviation from the HL7 Version 2.5.1
standard.
[NTE]
Notes and Comments
O
[0..*]
The Notes and Comments (NTE)
segment for the OBX segment can be
used to carry any observation-related
comments.
Formatted Table
OBSERVATION End
ORDER_OBSERVATION
End
2.2 SEGMENT PROFILE ATTRIBUTES
Fields or components that are NOT documented in this guide are
considered NOT SUPPORTED. Inclusion of any field or component
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
that is not supported will result in the creation of an error message.
The abbreviated terms and their definitions used in the ORU^R01
segment profile are detailed in the following table.
TABLE 5-13. SEGMENT PROFILE ATTRIBUTES
Abbreviation
Definition
Seq
Sequence of the elements as they are numbered in the HL7 segment.
Len
PHIN maximum length of the element. Length of an element is calculated using the
following rules:
Field length = (Sum of all supported component lengths) + (component number of
the last supported component) – 1.
Component length = (Sum of all supported sub-component lengths) + (subcomponent number of the last supported component) – 1.
Lengths should be considered recommendations, not absolutes. The receiver can
truncate fields, components and sub-components that are longer than the
recommended length. The receiver should continue to process a message even
when a field, component, or sub-component length exceeds the maximum
recommended length identified in this specification.
DT
Data type used by PHIN for HL7 element.
Indicator whether a data element is required, optional, or conditional in a message.
Legal values are:
•
R
Required. Must always be populated. May use “” (two sets of
quote marks) for a null value if no specific value is delineated in the
Description column of the table.
•
RE1
Required, but may be empty (no values, no quotes)
•
O
Optional.
•
C
Conditional, must be populated, when condition is met, must be
empty if condition is not met.
•
CE
Conditional, must be populated, but may be empty when
condition is met, must be empty if condition is not met,
•
X Not used.
Usage
Note: A required field in an optional segment does not mean the segment must be
present in the message. It means that if the segment is present, the required
fields within that segment must be populated. The same applies to required
components of optional fields. If the field is being populated, then the required
components must be populated. The same applies to required sub-components
of optional components. If a component is being populated, then the required
sub-components of that component must be populated.
1
The element may be missing from the message, but must be sent by sending application if there is
relevant data. A conforming sending application must be capable of providing all ‘RE’ elements. If
conforming sending application knows required values for the element, it must send that element. If
conforming sending application does not know the required values, then that element will be omitted.
Receiving applications will be expected to process (save/print/archive, etc.) or ignore data
contained in the element, but must be able to successfully process the message if the element
is omitted (no error message should be generated because the element is missing).
Health Level Seven, Version 2.5, July 2003, Section 2.12.6.2
Public reporting burden of this collection of information is estimated to average 5 minutes per
response. An agency may not conduct or sponsor, and a person is not required to respond to a
collection of information unless it displays a currently valid OMB control number. Send comments
regarding this burden estimate or any other aspect of this collection of information, including
suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE,
MS D-24, Atlanta, Georgia 30333; ATTN: PRA (0920-0004).
Formatted: Right: 0", Space Before: 0.4 pt
OMB NO. 0920-0004
TABLE 5-13. SEGMENT PROFILE ATTRIBUTES
Abbreviation
Definition
Cardinality
Minimum and maximum number of times the segment may appear.
• [0..0] Segment never present.
• [0..1] Segment may be omitted and can have, at most, one occurrence.
• [1..1] Segment must have exactly one occurrence.
• [0..n] Segment may be omitted or may repeat up to n times.
• [1..n] Segment must appear at least once, and may repeat up to n times.
• [0..*] Segment may be omitted or repeat an unlimited number of times.
• [1..*] Segment must appear at least once, and may repeat unlimited number
of times.
•
[m..n] Segment must appear at least m and at most n times.
Value Set Name
Pre-coordinated tables used in public health messages, accessible via the Public
Health Information Network Vocabulary Access and Distribution Services at
http://www.cdc.gov/PhinVSBrowser/StrutsController.do.
HL7 Tbl
The HL7 table number as defined in the HL7 V2.5.1 standard.
Element Name
Descriptive name of the data element.
Description
Explanation of the use of the field/component/sub-component.
OMB NO. 0920-0004
2.3 MESSAGE HEADER (MSH) SEGMENT LEVEL PROFILE
The MSH Segment is used to define the intent, source, destination, and some specifics of the syntax of the message.
This segment includes identification of message delimiters, sender, receiver, message type, timestamp, etc. The
message header is required for the test result message.
Seq
Len
TABLE 5-14. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name Description
Name
1
1
ST
R
[1,1]
Field Separator
The HL7 field separator, shall contain the constant
value '|', ASCII (124).
2
5
ST
R
[1,1]
Encoding Characters
The HL7 encoding characters, shall contain the
constant value '^~\&#'
3
227
HD
R
[1,1]
Sending Application
Field that may be used to uniquely identify the sending
application for messaging purposes. If populated, it will
contain an OID that represents the sending application
instance. For this version of PHLIP, the sending
application will be the PHIN namespace ID and OID of
your LIMS
3.1
20
IS
RE
[1,1]
Namespace ID
Namespace ID of LIMS
3.2
199
ST
R
Universal ID
OID of LIMS
3.3
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
4
227
HD
R
[1,1]
Sending Facility
Unique identifier of the facility that sends the message.
The sending facility must be part of the PHIN OID
registry. For this version of PHLIP, the sending facility
will be the PHIN namespace ID and OID of your Lab
4.1
20
IS
RE
[1,1]
Namespace ID
The PHIN namespace ID of Lab
4.2
199
ST
R
Universal ID
OID of Lab
4.3
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
5
227
HD
R
[1,1]
Receiving Application
Unique identifier of the receiving application for
messaging purposes. If populated, it will contain an
OID that represents the receiving application instance.
For this version of PHLIP, the receiving application will
always be the CDC application, as denoted in MSH-5.1
and MSH-5.2.
5.1
20
IS
RE
[1,1]
Namespace ID
Laboratory name.
Literal value: "US WHO Collab LabSys"
5.2
199
ST
R
[1,1]
Universal ID
US WHO Collab LabSys OID
Literal value: "2.16.840.1.114222.4.3.3.7’"
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-14. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
5.3
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
6
227
HD
R
[1,1]
Receiving Facility
Unique identifier of the facility that is to receive the
message. This unique identifier must be part of the
PHIN OID registry. For this version of PHLIP, the
receiving facility will always be the CDC facility, as
denoted in MSH-6.1 & MSH-6.2.
6.1
20
IS
RE
[1,1]
Namespace ID
Laboratory name.
Literal value: ‘CDC–EPI Surv Branch’
6.2
199
ST
R
[1,1]
Universal ID
CDC–EPI Surv Branch OID
Literal value: ‘2.16.840.1.114222.4.1.10416’
6.3
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
7
26
TS
R
[1,1]
Date/Time Of Message Date and time the message was created by the
sending system
7.1
24
DTM R
[1,1]
Time
8
40
ST
O
[0,1]
Security
9
15
MSG R
[1,1]
Message Type
The type of HL7 message you are sending
9.1
3
ID
R
[1,1]
Message Code
Literal value: ‘ORU’. Null flavors are not allowed.
9.2
3
ID
R
[1,1]
Trigger Event
Literal value: ‘R01’. Null flavors are not allowed.
9.3
7
ID
R
[1,1]
Message Structure
Literal value: ‘ORU_R01’. Null flavors are not allowed.
10
199
ST
R
[1,1]
Message Control ID
String that uniquely identifies the message instance
from the sending application. Recommended to use a
counter.
11
3
PT
R
[1,1]
Processing ID
Indicator of the intent for processing the message, such
as "T" - training/test, "D" - de-bugging, or "P" production. For PHLIP, this field will always contain "P."
11.1
1
ID
R
[1,1]
Processing ID
11.2
1
ID
O
[1,1]
Processing Mode
YYYY[MMDD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ],
where at least the first fourteen are used to specify to a
precision of "second.”
The time zone (+/-ZZZZ) is represented as +/-HHMM
offset from Coordinated Universal Time (UTC)
(formerly Greenwich Mean Time [GMT]), where +0000
or -0000 both represent UTC (without offset).
It is strongly recommended that the time zone be used
in PHIN messaging.
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-14. MESSAGE HEADER (MSH) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
12
973
VID
R
[1,1]
Version ID
The version of HL7 that this PHLIP message spec is
based upon
12.1
5
ID
R
[1,1]
Version ID
Literal value: '2.5.1'
12.2
705
CE
O
[1,1]
Internationalization
Code
12.3
705
CE
O
[1,1]
International Version
ID
13
15
NM
O
[0,1]
Sequence Number
14
180
ST
O
[0,1]
Continuation Pointer
15
2
ID
C(R/RE)
[0,1]
Accept
The PHLIP program does not send system level
Acknowledgment Type acknowledgements (ACKs) therefore the literal value of
"NE" should always be used
16
2
ID
C(R/RE)
[0,1]
Application
The PHLIP program does not send application level
Acknowledgment Type acknowledgements (ACKs) therefore the literal value of
"NE" should always be used
17
3
ID
O
[0,1]
Country Code
18
15
ID
O
[0,*]
Character Set
19
483
CWE O
[0,1]
Principal Language Of
Message
20
13
ID
O
[0,1]
Alternate Character Set
Handling Scheme
21[1]
427
EI
R
[1,*]
Message Profile
Identifier
Information about the ELR message profile
21.1[1] 199
ST
R
[1,1]
Entity Identifier
Literal: 'PHLabReport-NoAck'
21.2[1] 20
IS
RE
[1,1]
Namespace ID
21.3[1] 199
ST
R
[1,1]
Universal ID
Literal: '2.16.840.1.113883.9.11'
21.4[1] 6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
21[2]
EI
R
[1,*]
Message Profile
Identifier
Information about the PHLIP message profile
21.1[2] 199
ST
R
[1,1]
Entity Identifier
Literal: 'PHLIP_ELSM_251'
21.2[2] 20
IS
RE
[1,1]
Namespace ID
21.3[2] 199
ST
R
[1,1]
Universal ID
Literal: '2.16.840.1.113883.9.179'
21.4[2] 6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
427
OMB NO. 0920-0004
2.4 SOFTWARE (SFT) SEGMENT LEVEL PROFILE
The SFT segment is used primarily for diagnostic purposes. The SFT segment is not required in the header group.
Seq
Len
TABLE 5-15. SOFTWARE (SFT) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name Description
Name
1
567
XON R
[1,1]
Software Vendor
Organization
Name of LIMS or Interface Engine Vendor
1.1
50
ST
C(R/RE)
[1,1]
1.2
20
IS
RE
[1,1]
1.4
4
NM
O
[1,1]
1.5
3
ID
O
[1,1]
1.6
227
HD
C(R/X)
[1,1]
Assigning Authority
Note: Not needed for PHLIP
1.6.1
20
IS
RE
[1,1]
Namespace ID
Note: Not needed for PHLIP
1.6.2
199
ST
R
Universal ID
Note: Not needed for PHLIP
1.6.3
6
ID
R
[1,1]
HL70301
Universal ID Type
Note: Not needed for PHLIP
1.7
5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
Note: Not needed for PHLIP
1.8
227
HD
O
[1,1]
1.9
1
ID
O
[1,1]
1.9.1
20
IS
RE
[1,1]
1.9.2
199
ST
R
Organization Name
HL70204
Organization Name
Type Code
Note: Not needed for PHLIP
Check Digit
HL7061
Check Digit Scheme
Assigning Facility
HL70465
Name Representation
Code
Namespace ID
Universal ID
ELR-063:IF HD.3(Universal ID type) value is "ISO",
SHALL be a valid ISO OID format.
ELR-062:IF HD.3(Universal ID type) value is "CLIA",
SHALL be a valid CLIA identifier format
1.9.3
6
ID
R
[1,1]
1.10
20
ST
RE
2
15
ST
R
3
20
ST
R
HL70301
Universal ID Type
ELR-007:IF element is MSH-4.3 (Universal ID type) ,
then HD.3 (Universal ID type) SHALL contain the value
"ISO" OR "CLIA", ELSE HD.3 (Universal ID type)
SHALL contain the value "ISO"
[1,1]
Organization Identifier
Note: Not needed for PHLIP
[1,1]
Software Certified
Version or Release
Number
Latest software version of LIMS or Interface Engine.
[1,1]
Software Product
Name
Name of the LIMS or Interface Engine that submitted
the HL7 message
Formatted: Outline numbered + Level: 2 + Numbering
Style: 1, 2, 3, … + Start at: 1 + Alignment: Left + Aligned
at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
Seq
Len
TABLE 5-15. SOFTWARE (SFT) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Name
Description
4
20
ST
R
[1,1]
Software Binary ID
Binary ID is 20 digit code supplied by vendor for each
release of software.
If unknown, use any text string "binary ID unknown" or
"version"
5
1024
TX
O
[0,1]
Software Product
Information
Software identification information supplied by vendor
with transaction.
6
26
TS
RE
[0,1]
Software Install Date
Software Install Date following the format
YYYY[MM[DD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ]
Note: Not needed for PHLIP
6.1
24
DTM R
[1,1]
Time
2.5 SPECIMEN (SPM) SEGMENT LEVEL PROFILE
The SPM segment is used to describe the characteristics of a specimen collected for use in a laboratory test. It contains information on the type of
specimen and information around the collection of the specimen.
Seq Len
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
5
1024
TX
O
[0,1]
Software Product
Information
Software identification information supplied by vendor
with transaction.
1
4
SI
R
[1,1]
Set ID - SPM
SHALL contain the constant value '1' since there is
only one specimen per message
2
855
EIP
R
[1,1]
Specimen ID
Placer and Filler Specimen ID
2.1
427
EI
O
[1,1]
Placer Assigned
Identifier
This is an optional data element.
Note: Submitter is the same as placer. Placer is the
ordering facility/provider
2.1.1
199
ST
R
[1,1]
Entity Identifier
2.1.2
20
IS
RE
[1,1]
Namespace ID
2.1.3
199
ST
R
[1,1]
2.1.4
6
ID
R
[1,1]
2.2
427
EI
R
[1,1]
Universal ID
HL70301
Universal ID Type
Filler Assigned
Identifier
Literal value: ‘ISO’
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
Formatted Table
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
2.2.1
199
ST
R
[1,1]
Entity Identifier
The unique Specimen number
2.2.2
20
IS
RE
[1,1]
Namespace ID
Namespace ID of LIMS
2.2.3
199
ST
R
[1,1]
Universal ID
OID of LIMS
2.2.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
3
855
EIP
O
[0,*]
4
705
CWE R
[1,1]
4.1
20
ST
RE
4.2
199
ST
4.3
12
4.4
4.5
HL70301
Specimen Parent IDs
Specimen Type Value
Set
Specimen Type
Specimen type
Recommend send both the Standard (SNOMED) and
local code.
[1,1]
Identifier
Code for Specimen Type.
Use SNOMED code or local code
C(RE/X)
[1,1]
Text
Specimen Type Concept Name
If using SNOMED code use fully specified concept
name
ID
C(R/X)
[1,1]
Name of Coding
System
Code System for Specimen Type
If SNOMED use 'SCT'. If local use 'L' or '99zzz' (where
ZZ is any alphanumeric character - not constrained to
3).
20
ST
RE
[1,1]
Alternate Identifier
Code for Specimen Type
199
ST
C(RE/X)
[1,1]
Alternate Text
Specimen Type Concept Name
If using SNOMED code use fully specified concept
name
4.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Code System for Specimen Type
If SNOMED use 'SCT'. If local use 'L' or '99zzz' (where
zzz is any alphanumeric character - not constrained to
3).
4.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
4.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
4.9
199
ST
C(R/X)
[1,1]
Original Text
Original text for Specimen type
5
705
CWE RE
[0,*]
Specimen Type
Modifier
Modifier term for Specimen type
5.1
20
ST
RE
[1,1]
Identifier
SNOMED Code for qualifier
5.2
199
ST
C(RE/X)
[1,1]
Text
SNOMED Concept Name
HL70396
HL70396
PHVS Modifier Or
Qualifier CDC
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-6. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
5.3
12
ID
C(R/X)
[1,1]
HL70396
Name of Coding
System
Literal: 'SCT'
This will be SCT (for SNOMED) - can be hardcoded if
always populate first triplet with SNOMED codes.
If you put a SNOMED specimen code in SPM4.1, you
must put SCT in SPM4.3. If you leave SPM4.1 empty,
you should also leave SPM4.3 empty
5.4
20
ST
RE
[1,1]
5.5
199
ST
C(RE/X)
[1,1]
5.6
12
ID
C(R/X)
[1,1]
5.7
10
ST
RE
[1,1]
Coding System Version SNOMED Version ID
ID
5.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
5.9
199
ST
C(R/X)
[1,1]
6
705
CWE RE
[0,*]
6.1
20
ST
RE
[1,1]
6.2
199
ST
C(RE/X)
[1,1]
6.3
12
ID
C(R/X)
[1,1]
6.4
20
ST
RE
[1,1]
6.5
199
ST
C(RE/X)
[1,1]
6.6
12
ID
C(R/X)
[1,1]
6.7
10
ST
RE
[1,1]
Coding System Version Note: Recommended if a coding system is identified in
ID
component 3
6.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
6.9
199
ST
C(R/X)
[1,1]
7
705
CWE RE
[0,1]
7.1
20
ST
RE
[1,1]
7.2
199
ST
C(RE/X)
[1,1]
7.3
12
ID
C(R/X)
[1,1]
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Original Text
HL70371
Specimen Additives
Uses HL7 table 371 for additives
Identifier
Text
HL70396
Name of Coding
System
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Original Text
Specimen Collection
Method Value Set
Specimen Collection
Method
Identifier
Text
HL70396
Name of Coding
System
Uses HL7 table 488 or SNOMED CT from procedure
hierarchy under specimen collection
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
7.4
20
ST
RE
[1,1]
Alternate Identifier
7.5
199
ST
C(RE/X)
[1,1]
Alternate Text
7.6
12
ID
C(R/X)
[1,1]
7.7
10
ST
RE
[1,1]
Coding System Version
ID
7.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
7.9
199
ST
C(R/X)
[1,1]
8
705
CWE RE
[0,1]
8.1
20
ST
RE
[1,1]
Identifier
Code for Specimen Type.
Use SNOMED code or local code
8.2
199
ST
C(RE/X)
[1,1]
Text
Specimen Type Concept Name
If using SNOMED code use fully specified concept
name
8.3
12
ID
C(R/X)
[1,1]
Name of Coding
System
Code System for Specimen Type
If SNOMED use 'SCT'. If local use 'L' or '99zzz' (where
zzz is any alphanumeric character - not constrained to
3).
8.4
20
ST
RE
[1,1]
Alternate Identifier
Code for Specimen Type.
Use SNOMED code or local code
8.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Specimen Type Concept Name
If using SNOMED code use fully specified concept
name
8.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Code System for Specimen Type
If SNOMED use 'SCT'. If local use 'L' or '99zzz' (where
zzz is any alphanumeric character - not constrained to
3).
8.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
8.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
8.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
9
705
CWE RE
[0,*]
9.1
20
ST
[1,1]
RE
HL70396
Formatted Table
Name of Alternate
Coding System
Original Text
Body Site Value Set
HL70396
HL70396
PHVS Modifier or
Qualifier CDC
Specimen Source Site Specimen Source (body)Site
Specimen Source Site
Modifier
Identifier
SNOMED Code for qualifier
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
9.2
199
ST
C(RE/X)
[1,1]
9.3
12
ID
C(R/X)
[1,1]
9.4
20
ST
RE
[1,1]
9.5
199
ST
C(RE/X)
[1,1]
9.6
12
ID
C(R/X)
[1,1]
9.7
10
ST
RE
[1,1]
Coding System Version SNOMED Version ID
ID
9.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
9.9
199
ST
C(R/X)
[1,1]
10
705
CWE O
[0,1]
HL70543
Specimen Collection
Site
11
705
CWE RE
[0,*]
HL70369
Specimen Role
11.1
20
ST
RE
[1,1]
11.2
199
ST
C(RE/X)
[1,1]
11.3
12
ID
C(R/X)
[1,1]
11.4
20
ST
RE
[1,1]
11.5
199
ST
C(RE/X)
[1,1]
11.6
12
ID
C(R/X)
[1,1]
11.7
10
ST
RE
[1,1]
Coding System Version
ID
11.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
11.9
199
ST
C(R/X)
[1,1]
12
500
CQ
RE
[0,1]
12.1
16
NM
R
[1,1]
HL70396
Text
SNOMED Concept Name
Name of Coding
System
Literal: 'SCT'
This will be SCT (for SNOMED) - can be hardcoded if
always populate first triplet with SNOMED codes.
If you put a SNOMED specimen code in SPM4.1, you
must put SCT in SPM4.3. If you leave SPM4.1 empty,
you should also leave SPM4.3 empty
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Original Text
For PHLIP, this element can be empty
Identifier
Text
HL70396
Name of Coding
System
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Original Text
UCUM
Specimen Collection
Amount
Quantity
For PLHIP, this element can be empty
Formatted Table
OMB NO. 0920-0004
Seq
Len
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Name
12.2
483
CE
RE
[1,1]
Units
12.1
20
ST
RE
[1,1]
Identifier
12.2
199
ST
C(RE/X)
[1,1]
12.3
12
ID
C(R/X)
[1,1]
12.4
20
ST
RE
[1,1]
12.5
199
ST
C(RE/X)
[1,1]
12.6
12
ID
C(R/X)
[1,1]
12.7
10
ST
RE
[1,1]
Coding System Version
ID
12.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
12.9
199
ST
C(R/X)
[1,1]
Original Text
13
6
NM
O
[0,1]
Grouped Specimen
Count
14
250
ST
O
[0,*]
15
705
CWE O
[0,*]
HL70376
Specimen Handling
Code
16
705
CWE O
[0,*]
HL70489
Specimen Risk Code
17
53
DR
R
[1,1]
Specimen Collection
Date/Time
17.1
26
TS
RE
Description
Text
HL70396
Name of Coding
System
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Specimen Description
Specimen Collection Date/Time Range
[1,1]
Range Start Date/Time Specimen Collection Date/Time
17.1.1 24
DTM R
[1,1]
Time
17.2
TS
[1,1]
Range End Date/Time
26
RE
Specimen Collection Date/Time
17.2.1 24
DTM R
[1,1]
Time
18
26
TS
R
[1,1]
Specimen Received
Date/Time
Specimen Received Date/Time
18.1
24
DTM R
[1,1]
Time
Specimen Received Date/Time
Format: YYYYMMDD[HH[MM[SS[.S[S[S[S]]]]]]][+/ZZZZ]
19
26
TS
O
[0,1]
Specimen Expiration
Date/Time
20
1
ID
O
[0,1]
HL70136
Specimen Availability
OMB NO. 0920-0004
Seq
Len
Dt
TABLE 5-16. SPECIMEN (SPM) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Usage
Cardinality
Element Name
Description
Name
21
705
CWE RE
[0,*]
HL70490
Specimen Reject
Reason
21.1
20
ST
RE
[1,1]
21.2
199
ST
C(RE/X)
[1,1]
21.3
12
ID
C(R/X)
[1,1]
21.4
20
ST
RE
[1,1]
21.5
199
ST
C(RE/X)
[1,1]
21.6
12
ID
C(R/X)
[1,1]
21.7
10
ST
RE
[1,1]
Coding System Version
ID
21.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
21.9
199
ST
C(R/X)
[1,1]
22
705
CWE O
[0,1]
HL70491
Specimen Quality
23
705
CWE O
[0,1]
HL70492
Specimen
Appropriateness
24
705
CWE O
[0,*]
HL70493
Specimen Condition
25
500
CQ
O
[0,1]
UCUM
Specimen Current
Quantity
26
4
NM
O
[0,1]
27
705
CWE O
[0,1]
28
705
CWE O
[0,1]
HL70544
Container Condition
29
705
CWE O
[0,1]
HL70494
Specimen Child Role
Identifier
Text
HL70396
Name of Coding
System
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Original Text
Number of Specimen
Containers
Container Type
Note: Not Needed for PHLIP
OMB NO. 0920-0004
2.6 NOTES AND COMMENTS (NTE) SEGMENT LEVEL PROFILE
The NTE Segment in the test result message can be used to carry comments for the SPM, PV1, OBR, and OBX
segments. The NTE segment applies to the entity that immediately precedes it (e.g., order-related comments if it
follows the OBR segment, observation-related comments if it follows the OBX segment).
Seq
Len
TABLE 5-17. NOTES AND COMMENTS (NTE) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
1
4
SI
R
[1,1]
2
1
ID
RE
[0,1]
Set ID - NTE
3
65536
FT
R
[1,*]
4
483
CWE RE
[0,1]
4.1
20
ST
RE
[1,1]
Identifier
Code for Source of Comment
4.2
199
ST
C(RE/X)
[1,1]
Text
Source of Comment Concept Name
4.3
12
ID
C(R/X)
[1,1]
Name of Coding
System
Code System for Source of Comment
4.4
20
ST
RE
[1,1]
Alternate Identifier
Code for Source of Comment
4.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Source of Comment Concept Name
4.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Code System for Source of Comment
4.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
4.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
4.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
HL70105
HL70364
HL70396
HL70396
Source of Comment
HL7 defined values from Table 0105 of where the
comment originated ("L" = Filler, "P" = Placer, "O" =
Other)
Comment
The comment
Note: This field uses an FT rather than a TX data type.
Since there is no difference between an FT data type
without any embedded formatting commands, and a TX
data type, this change is compatible with previous
versions.
Comment Type
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
2.7 PATIENT IDENTIFICATION (PID) SEGMENT LEVEL PROFILE
The PID Segment is used as the primary means of communicating patient identification information. This segment
contains pertinent patient identifying and demographic information. The PID Segment is required in the patient group.
For PHLIP, the patient group is required. If the message sender has detailed patient information, and that information
is needed/required by the message receiver, this patient group will be used. For the PHLIP influenza test result
message, only one PID Segment is expected per message. If the message sender does not have sufficient
information to construct a legal PID Segment, such as a patient name and patient ID, the message sender should
send the default data as noted in the Description column, below.
Seq
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
1
4
SI
R
[1,1]
Set ID - PID
Literal value: "1"
3
1913
CX
R
[1,*]
Patient Identifier List
This field contains the list of identifiers (one or more)
used to uniquely identify a
patient (e.g., medical record number, billing number,
birth registry, national unique individual identifier, etc.)
3.1
15
ST
R
[1,1]
ID Number
The unique Patient ID number.
Do NOT send social security numbers at all.
Note: If no Patient ID is available, the Specimen ID
should be defaulted into this field. For PHLIP, the
Specimen ID will be an observation sent in OBX-5
(Observation Value) with a data type of "CX." In the
case where the Specimen ID is used in place of the
Patient ID, it should also be a separate OBX.
3.2
4
ST
O
[1,1]
3.3
3
ID
O
[1,1]
Check Digit
3.4
227
HD
R
[1,1]
Assigning Authority
Entity that assigned the patient identifier.
3.4.1
20
IS
RE
[1,1]
Namespace ID
Namespace ID of LIMS
3.4.2
199
ST
R
Universal ID
OID of your LIMS( assuming LIMS assigned the ID
above)
3.4.3
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’.
3.5
5
ID
R
[1,1]
Identifier Type Code
Patient Identifier type
3.6
227
HD
RE
[1,1]
Assigning Facility
Facility that assigned the patient identifier.
3.6.1
20
IS
RE
[1,1]
Namespace ID
3.6.2
199
ST
R
HL7061
HL70301
HL70203
Check Digit Scheme
Universal ID
OID of your LIMS( assuming LIMS assigned the ID
above)
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
Seq
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
3.6.3
6
ID
R
[1,1]
3.7
8
DT
O
[1,1]
Effective Date
3.8
8
DT
O
[1,1]
Expiration Date
3.9
705
CWE O
[1,1]
Assigning Jurisdiction
3.10
705
CWE O
[1,1]
Assigning Agency or
Department
5
1044
XPN R
[1,*]
Patient Name
6
1044
XPN RE
[0,1]
Mother's Maiden Name DO NOT send any patient name information.
7
26
TS
[0,1]
Date/Time of Birth
7.1
24
DTM R
[1,1]
Time
8
20
IS
RE
[0,1]
HL70001
Administrative Sex
Patient's sex
10
483
CWE RE
[0,*]
HL70005
Race
Patient's race(s)
10.1
20
ST
RE
[1,1]
Identifier
Standardized code.
Rule of conditionality: The standard code component is
mandatory unless there is no standard to match the
local value passed by the application. An attempt will be
made by the sender to map the local value to the
standard. In the case that no standard code was found,
this field may be blank.
10.2
199
ST
C(RE/X)
[1,1]
Text
Standardized description
10.3
12
ID
C(R/X)
[1,1]
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system identifier
is always required if there is a value in component 1.
10.4
20
ST
RE
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
10.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized code
or local code value passed.
RE
HL70301
HL70396
Universal ID Type
Literal value: 'ISO'
DO NOT send any patient name information. The
default value for this field SHALL be: "~^^^^^^U",
"^^^^^^U", or "~^^^^^^S"
Patient's date and time of birth
OMB NO. 0920-0004
Seq
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
10.6
12
ID
C(R/X)
[1,1]
10.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
10.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
10.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
11
578
XAD RE
[0,*]
Patient Address
Residence address of the patient.
If multiple patient addresses are sent, the 1st repeat
should contain the patient’s primary address.
Note: If the state is not sent in the message, the
receiver should default the sending system’s state in
PID-11.4.
11.1
184
HL70396
Name of Alternate
Coding System
SAD RE
[1,1]
Street Address
11.1.1 120
ST
R
[1,1]
Street or Mailing
Address
11.1.2 50
ST
O
[0,1]
Street Name
11.1.3 12
ST
O
[0,1]
Dwelling Number
11.2
120
ST
RE
[1,1]
Other Designation
11.3
50
ST
RE
[1,1]
11.4
50
ST
RE
[1,1]
State Value Set
11.5
12
ST
RE
[1,1]
Postal Code Value Set Zip or Postal Code
11.6
3
ID
RE
[1,1]
11.7
3
ID
RE
[1,1]
HL70399
HL70190
11.8
50
ST
O
[1,1]
Locally defined codes for purpose of sender or receiver.
Local codes can be identified by "L" (for backward
compatibility) or "99zzz" (where z is an alphanumeric
character).
Rule of conditionality: Required if an alternate identifier
is present.
City
State or Province
Reference the FIPS 5-2 alpha codes here, though this
is not a coded field, so no coding system will be
identified.
US Zip Codes, Zip+4 and Canadian Postal Codes will
be supported.
Country
Address Type
Other Geographic
Designation
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bulletins/fy2007/b0701.pdf
OMB NO. 0920-0004
Seq
11.9
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
20
IS
RE
[1,1]
PHVS_County_FIPS_6 County/Parish Code
-4
Census Tract
Address
Representation Code
Effective Date
11.10 20
IS
O
[1,1]
11.11 1
ID
O
[1,1]
11.13 24
TS
O
[1,1]
11.14 24
TS
O
[1,1]
Expiration Date
13
651
XTN RE
[0,*]
Phone Number - Home DO NOT send patient telephone information
14
651
XTN RE
[0,*]
Phone Number Business
15
483
CWE O
[0,*]
16
483
CWE O
[0,1]
17
483
CWE O
[0,1]
18
1913
CX
O
[0,1]
21
1913
CX
O
[0,*]
PHVS_Language_ISO Primary Language
_639-2_Alpha3
Marital Status
HL702
Religion
HL706
Patient Account
Number
Mother's Identifier
22
483
CWE RE
[0,*]
HL70189
22.1
20
ST
RE
[1,1]
22.2
199
ST
C(RE/X)
[1,1]
22.3
12
ID
C(R/X)
[1,1]
22.4
20
ST
RE
[1,1]
HL70396
Map to FIPS 6-4 code
DO NOT send patient telephone information
Ethnic Group
Patient's ethnicity defined as Hispanic, Non-Hispanic, or
Unknown
Identifier
Standardized code.
Rule of conditionality: The standard code component is
mandatory unless there is no standard to match the
local value passed by the application. An attempt will be
made by the sender to map the local value to the
standard. In the case that no standard code was found,
this field may be blank.
Text
Standardized description.
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system identifier
is always required if there is a value in component 1.
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
OMB NO. 0920-0004
Seq
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
22.5
199
ST
C(RE/X)
[1,1]
22.6
12
ID
C(R/X)
[1,1]
22.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
22.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
22.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
23
250
ST
O
[0,1]
Birth Place
24
1
ID
O
[0,1]
25
2
NM
O
[0,1]
26
483
CWE O
[0,*]
HL70171
Citizenship
27
483
CWE O
[0,1]
HL70172
Veterans Military
Status
29
26
TS
[0,1]
29.1
24
DTM R
[1,1]
30
1
ID
RE
[0,1]
HL70136
Patient Death Indicator Indicator (Y) of patient’s death, if the patient is known to
be deceased at the time of the message. If unknown,
this field should be empty (no value, no quotes).
31
1
ID
O
[0,1]
HL70136
Identity Unknown
Indicator
32
20
IS
O
[0,*]
HL70445
Identity Reliability Code
33
26
TS
RE
[0,1]
Last Update Date/Time When updating demographic information update this
field to flag receiver of new information.
33.1
24
DTM R
[1,1]
Time
34
241
HD
[0,1]
Last Update Facility
RE
C(R/X)
HL70396
HL70136
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is Coded.
Rule of conditionality: Required if no standardized code
or local code value passed.
Name of Alternate
Coding System
Locally defined codes for purpose of sender or receiver.
Local codes can be identified by "L" (for backward
compatibility) or "99zzz" (where z is an alphanumeric
character).
Rule of conditionality: Required if an alternate identifier
is present.
Multiple Birth Indicator
Birth Order
Patient Death Date and Date and time of patient’s death, if the patient is known
Time
to be deceased at the time of the message.
Time
The PHIN namespace ID and OID of your Lab
OMB NO. 0920-0004
Seq
Len
TABLE 5-18. PATIENT IDENTIFICATION (PID) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
34.1
20
IS
RE
34.2
199
ST
R
[1,1]
Namespace ID
34.3
6
ID
R
35
483
CWE RE
[0,1]
35.1
20
ST
RE
[1,1]
35.2
199
ST
C(RE/X)
[1,1]
35.3
12
ID
C(R/X)
[1,1]
35.4
20
ST
RE
[1,1]
35.5
199
ST
C(RE/X)
[1,1]
35.6
12
ID
C(R/X)
[1,1]
35.7
10
ST
RE
[1,1]
Coding System Version
ID
35.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
35.9
199
ST
C(R/X)
[1,1]
Original Text
36
483
CWE O
[0,1]
Breed Code
37
80
ST
O
[0,1]
38
483
CWE O
[0,2]
HL70429
Production Class Code
39
705
CWE O
[0,*]
Tribal Citizenship
Value Set
Tribal Citizenship
Universal ID
[1,1]
HL70301
PHVS_Animal_CDC
Universal ID Type
Species Code
Note: For PHLIP, this element can be empty
Identifier
Text
HL70396
Name of Coding
System
Alternate Identifier
Alternate Text
HL70396
Name of Alternate
Coding System
Strain
2.8 PATIENT VISIT (PV1) SEGMENT LEVEL PROFILE
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
The PV1 Segment contains information on patient visits at the visit- or account-level.
TABLE 5-19. PATIENT VISIT (PV1) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
1
4
SI
R
[1,1]
Set ID - PV1
SHALL contain the constant value '1'.
1
4
SI
R
[1,1]
Set ID - PV1
SHALL contain the constant value '1'.
OMB NO. 0920-0004
TABLE 5-19. PATIENT VISIT (PV1) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
2
20
IS
R
[1,1]
HL70004
3
1230
PL
O
[0,1]
4
20
IS
RE
[0,1]
5
1913
CX
O
[0,1]
Preadmit Number
6
1230
PL
O
[0,1]
Prior Patient Location
7
2945
XCN O
[0,*]
Attending Doctor
8
2945
XCN O
[0,*]
Referring Doctor
9
2945
XCN O
[0,*]
Consulting Doctor
10
20
IS
O
[0,1]
Hospital Service
11
1230
PL
O
[0,1]
12
20
IS
O
[0,1]
HL7087
Preadmit Test Indicator
14
20
IS
O
[0,1]
HL7023
Admit Source
17
2945
XCN O
[0,*]
18
20
IS
O
[0,1]
19
1913
CX
O
[0,1]
Visit Number
20
50
FC
O
[0,*]
Financial Class
30
8
DT
O
[0,1]
Transfer to Bad Debt
Date
31
20
IS
O
[0,1]
32
12
NM
O
[0,1]
Bad Debt Transfer
Amount
33
12
NM
O
[0,1]
Bad Debt Recovery
Amount
34
20
IS
O
[0,1]
35
8
DT
O
[0,1]
36
20
IS
O
[0,1]
37
47
DLD O
[0,1]
38
483
CWE O
[0,1]
HL70114
Diet Type
39
20
IS
O
[0,1]
HL70115
Servicing Facility
41
20
IS
O
[0,1]
HL70117
Account Status
HL70007
Patient Class
Kind of patient, should be indicated in EPI question
LAB330 instead of in PV1 segment
Assigned Patient
Location
The patients initial assigned location or location where
the patient is being moved at point of care
Admission Type
Temporary Location
Admitting Doctor
HL7018
HL7021
HL70111
Patient Type
Bad Debt Agency Code
Delete Account
Indicator
Delete Account Date
HL70112
Description
Discharge Disposition
Discharged to Location
OMB NO. 0920-0004
TABLE 5-19. PATIENT VISIT (PV1) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
42
1230
PL
O
[0,1]
Pending Location
43
1230
PL
O
[0,1]
Prior Temporary
Location
44
26
TS
RE
[0,1]
Admit Date/Time
44.1
24
DTM R
[1,1]
Time
45
26
TS
[1,1]
Discharge Date/Time
45.1
24
DTM R
[1,1]
Time
46
12
NM
O
[0,1]
Current Patient
Balance
47
12
NM
O
[0,1]
Total Charges
48
12
NM
O
[0,1]
Total Adjustments
49
12
NM
O
[0,1]
Total Payments
50
1913
CX
O
[0,1]
51
20
IS
O
[0,1]
52
2945
XCN O
[0,*]
RE
Description
Admit Date/Time SHALL follow the format
YYYY[MM[DD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ]
Discharge Date/Time SHALL follow the format
YYYY[MM[DD[HH[MM[SS[.S[S[S[S]]]]]]]]][+/-ZZZZ]
Alternate Visit ID
HL70326
Visit Indicator
Other Healthcare
Provider
2.9 COMMON ORDER (ORC) SEGMENT LEVEL PROFILE
The ORC Segment is used to transmit test order information. This segment includes identifiers for the order, who
placed the order, when it was placed, etc. The ORC Segment is optional in the Test Result (ORU) message. Any
information that could be included in either the ORC or the OBR must be included in the OBR on reporting.
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
1
2
ID
R
[1,1]
HL70119
Order Control
Description
HL7 Order Control Codes indicate the order action to
be performed, i.e., the circumstances of the order that
is contained in this message. For PHLIP messages the
Order Control Code is RE (Observations/Performed
Service to follow).
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
2
427
EI
C(R/X)
[0,1]
Placer Order Number
2.1
199
ST
R
[1,1]
Entity Identifier
2.2
20
IS
RE
[1,1]
Namespace ID
Assigning authority
2.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID for
the application/ organization responsible for creating
the placer order number. The placer order number is
expected to be unique within this assigning authority.
2.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
3
427
EI
R
[1,1]
Filler Order Number
Order number associated with the filling application.
Note: The same value is populated in ORC.3 and
OBR.3.
3.1
199
ST
R
[1,1]
Entity Identifier
3.2
20
IS
RE
[1,1]
Namespace ID
Namespace ID of the application/organization
responsible for creating the filler order number
3.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID for
the application/organization responsible for creating the
filler order number. The filler order number is expected
to be unique within this assigning authority.
3.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
4
427
EI
RE
[0,1]
Placer Group Number
Note: Not needed for PLHIP
5
2
ID
O
[0,1]
HL7038
Order Status
Status of an order
6
1
ID
O
[0,1]
HL70121
Response Flag
8
855
EIP
O
[0,1]
Parent
9
26
TS
O
[0,1]
Date/Time of
Transaction
10
2945
XCN O
[0,*]
Entered By
11
2945
XCN O
[0,*]
Verified By
12
2945
XCN C(R/X)
[0,*]
Ordering Provider
Physician or other provider who ordered the test
12.1
15
ST
RE
[1,1]
ID Number
Provider ID
12.2
194
FN
RE
[1,1]
Family Name
Ordering provider's last name
ST
R
[1,1]
Surname
12.2.1 50
HL70301
HL70301
Unique identifying number assigned to the test request
or order by the system that initiated the request for
performance of the test.
Note: The same value is populated in ORC.2 and
OBR.2.
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
12.2.2 20
ST
O
[1,1]
Own Surname Prefix
12.2.3 50
ST
O
[1,1]
Own Surname
12.2.4 20
ST
O
[1,1]
Surname Prefix From
Partner/Spouse
12.2.5 50
ST
O
[1,1]
Surname From
Partner/Spouse
12.3
30
ST
RE
[1,1]
Given Name
12.4
30
ST
RE
[1,1]
Second and Further
Ordering provider's middle Initial or middle name
Given Names or Initials
Thereof
12.5
20
ST
RE
[1,1]
Suffix (e.g., JR or III)
Ordering provider's name suffix
12.6
20
ST
RE
[1,1]
Prefix (e.g., DR)
Ordering provider's name prefix
12.7
20
IS
O
[1,1]
HL70360
Degree (e.g., MD)
12.8
20
IS
O
[1,1]
HL70297
Source Table
12.9
227
HD
C(R/X)
[1,1]
Assigning Authority
The assigning authority for the ordering provider's ID
12.9.1 20
IS
RE
[1,1]
Namespace ID
Namespace ID of entity (e.g. NPI, your LIMS, etc) that
assigned the identifier above
12.9.2 199
ST
R
Universal ID
OID of entity (e.g. NPI, your LIMS, etc) that assignee
the identifier above
12.9.3 6
ID
R
[1,1]
HL70301
Universal ID Type
Literal value: ‘ISO’
12.10 5
ID
RE
[1,1]
HL70200
Name Type Code
12.11 4
ST
O
[1,1]
12.12 3
ID
O
[1,1]
HL7061
Check Digit Scheme
12.13 5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
12.14 227
HD
RE
[1,1]
Assigning Facility
12.14. 20
1
IS
RE
[1,1]
Namespace ID
12.14. 199
2
ST
R
12.14. 6
3
ID
R
Identifier Check Digit
Universal ID
[1,1]
Ordering provider's last name
HL70301
Universal ID Type
The Assigning Facility identifies the place or location
that the ID Number was assigned for use. (Not needed
in most states)
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
12.15 1
ID
O
[1,1]
HL70465
Name Representation
Code
12.16 483
CE
O
[1,1]
HL70448
Name Context
12.18 1
ID
O
[1,1]
HL70444
Name Assembly Order
12.19 8
TS
O
[1,1]
12.20 8
TS
O
[1,1]
12.21 199
ST
RE
[1,1]
12.22 705
CWE O
[1,1]
Assigning Jurisdiction
12.23 705
CWE O
[1,1]
Assigning Agency or
Department
13
1230
PL
O
[0,1]
Enterer's Location
14
651
XTN C(R/X)
[0,2]
Call Back Phone
Number
15
26
TS
O
[0,1]
Order Effective
Date/Time
16
483
CWE O
[0,1]
Order Control Code
Reason
17
483
CWE O
[0,1]
Entering Organization
18
483
CWE O
[0,1]
Entering Device
19
2945
XCN O
[0,*]
Action By
21
563
XON R
[1,1]
Ordering Facility Name Name and ID of the facility that placed the order
21.1
50
ST
C(R/RE)
[1,1]
21.2
20
IS
RE
[1,1]
21.4
4
NM
O
[1,1]
21.5
3
ID
O
[1,1]
21.6
227
HD
C(R/X)
[1,1]
Assigning Authority
The Assigning Authority component is used to identify
the system, application, organization, etc. that assigned
the ID in component 10.
21.6.1 20
IS
RE
[1,1]
Namespace ID
Namespace ID of entity (e.g. NPI, submitting public
health lab LIMS, etc) that assigned the facility identified
below
21.6.2 199
ST
R
Universal ID
OID of entity (e.g. NPI, submitting public health lab
LIMS, etc) that assigned the identifier below
Effective Date
Expiration Date
HL70360
HL70204
Professional Suffix
Ordering provider's name suffix
Submitter's contact info
Notes: Not needed for PHLIP
Organization Name
Name of the organization
Organization Name
Type Code
Name type code of the organization
Check Digit
HL7061
Check Digit Scheme
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
Literal value: ‘ISO’
21.6.3 6
ID
R
[1,1]
HL70301
Universal ID Type
21.7
5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
21.8
227
HD
O
[1,1]
21.9
1
ID
O
[1,1]
21.10 20
ST
RE
[1,1]
Organization Identifier
Ordering facility ID
22
578
XAD R
[1,1]
Ordering Facility
Address
Address of the facility that placed the order. If multiple
addresses are sent, the 1st repeat should contain the
ordering facility’s primary address.
Note: If the state is not sent in the message, the
receiver should default the sending system’s state in
ORC-22.4.
22.1
184
Street Address
Assigning Facility
HL70465
Name Representation
Code
SAD RE
[1,1]
Street Address
22.1.1 120
ST
R
[1,1]
Street or Mailing
Address
22.1.2 50
ST
O
[0,1]
Street Name
22.1.3 12
ST
O
[0,1]
Dwelling Number
22.2
120
ST
RE
[1,1]
Other Designation
Other Designation
Note: This isn't needed for most addresses. It could be
a district name, building name, floor number, etc
22.3
50
ST
RE
[1,1]
City
City
22.4
50
ST
RE
[1,1]
State Value Set
State or Province
State or Province
Note: FIPS 5-2 alpha codes are supported
22.5
12
ST
RE
[1,1]
Postal Code Value
Set
Zip or Postal Code
Zip or Postal Code
Note: US Zip Codes, Zip+4 and Canadian Postal Codes
are supported.
22.6
3
ID
RE
[1,1]
Country Value Set
Country
Country
22.7
3
ID
RE
[1,1]
HL70190
Address Type
Address Type code from HL7 Table 190
22.8
50
ST
O
[1,1]
Other Geographic
Designation
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bull etins/fy2007/b0701.pdf
22.9
20
IS
RE
[1,1]
22.10 20
IS
O
[1,1]
PHVS_County_FIPS_ County/Parish Code
6-4
Census Tract
County code from FIPS6_4
Note: This element can be empty in PHLIP
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
22.11 1
ID
O
[1,1]
Address
Representation Code
22.13 24
TS
O
[1,1]
Effective Date
22.14 24
TS
O
[1,1]
Expiration Date
23
651
XTN R
[1,*]
Ordering Facility Phone Telephone number of the facility placing the order. The
Number
receiver must minimally support the 1st repeat when
populating this field.
Email address, if sent, is a separate "repeat" with
appropriate Telecommunication Use Code and
Telecommunication Equipment Type.
23.2
3
ID
RE
[1,1]
HL70201
Telecommunication
Use Code
Ordering facility telecom use code from HL7 table 0201
23.3
8
ID
RE
[1,1]
HL70202
Telecommunication
Equipment Type
Ordering facility telecom equipment type from HL7 table
0202
23.4
199
ST
C(R/X)
[1,1]
Email Address
Ordering facility email address
Example of email address format: [email protected]
23.5
3
NM
C(RE/X)
[1,1]
Country Code
Ordering facility international dialing code
23.6
3
NM
C(RE/X)
[1,1]
Area/City Code
Ordering facility area code
23.7
9
NM
C(R/X)
[1,1]
Local Number
Ordering facility phone number
23.8
5
NM
C(RE/X)
[1,1]
Extension
Extension for phone number
23.9
199
ST
RE
[1,1]
Any Text
Any text
24
578
XAD RE
[0,*]
Ordering Provider
Address
The address of the ordering provider.
24.1
184
Street Address
SAD RE
[1,1]
Street Address
24.1.1 120
ST
R
[1,1]
Street or Mailing
Address
24.1.2 50
ST
O
[0,1]
Street Name
24.1.3 12
ST
O
[0,1]
Dwelling Number
24.2
120
ST
RE
[1,1]
Other Designation
Other Designation
Note: This isn't needed for most addresses. It could be
a district name, building name, floor number, etc
24.3
50
ST
RE
[1,1]
City
City
24.4
50
ST
RE
[1,1]
State or Province
State or Province
Note: FIPS 5-2 alpha codes are supported
State Value Set
OMB NO. 0920-0004
TABLE 5-20. COMMON ORDER (ORC) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Len
Dt Usage
Cardinality
Element Name
Name
Seq
Description
24.5
12
ST
RE
[1,1]
Postal Code Value
Set
Zip or Postal Code
Zip or Postal Code
Note: US Zip Codes, Zip+4 and Canadian Postal Codes
are supported.
24.6
3
ID
RE
[1,1]
Country Value Set
Country
Country
24.7
3
ID
RE
[1,1]
HL70190
Address Type
Address Type code from HL7 Table 190
24.8
50
ST
O
[1,1]
Other Geographic
Designation
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bull etins/fy2007/b0701.pdf
24.9
20
IS
RE
[1,1]
24.10 20
IS
O
[1,1]
Census Tract
24.11 1
ID
O
[1,1]
Address
Representation Code
24.13 24
TS
O
[1,1]
Effective Date
24.14 24
TS
O
[1,1]
Expiration Date
25
705
CWE O
[0,1]
Order Status Modifier
27
26
TS
O
[0,1]
Filler's Expected
Availability Date/Time
28
705
CWE O
[0,1]
HL70177
Confidentiality Code
29
705
CWE O
[0,1]
HL70482
Order Type
30
705
CNE O
[0,1]
HL70483
Enterer Authorization
Mode
31
705
CWE O
[0,1]
Laboratory Order
Value Set
Parent Universal
Service Identifier
PHVS_County_FIPS_ County/Parish Code
6-4
County code from FIPS6_4
Note: This element can be empty of PHLIP
OMB NO. 0920-0004
2.10
OBSERVATION REQUEST (OBR) SEGMENT LEVEL PROFILE
The OBR Segment in the Test Result Message (ORU) is used to capture information about one test being performed
on the specimen or report information about patient and specimen.
Note: For PHLIP, only one specimen is allowed per ORU^R01 message.
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
1
4
SI
R
[1,1]
Set ID - OBR
Sequence number of the OBR in relation to the Result
message to which it refers. The sequence number
should start at 1 and be incremented by 1 for each
OBR in the result message.
2
427
EI
RE
[1,1]
Placer Order Number
Unique identifying number assigned to the test
request or order by the system that initiated the
request for performance of the test.
Note: The same value is populated in ORC.2 and
OBR.2.
2.1
199
ST
R
[1,1]
Entity Identifier
Placer order number
2.2
20
IS
RE
[1,1]
Namespace ID
Namespace ID of placer (e .g. EHRS)
2.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID
for the application/ organization responsible for
creating the placer order number. The placer order
number is expected to be unique within this assigning
authority.
2.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
3
427
EI
R
[1,1]
Filler Order Number
Order number associated with the filling application.
Note: The same value is populated in ORC.3 and
OBR.3.
3.1
199
ST
R
[1,1]
Entity Identifier
Lab order number
Note: This filler number should be a systemgenerated number from the LIMS.
3.2
20
IS
RE
[1,1]
Namespace ID
Namespace ID of your LIMS
3.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID
for the application/organization responsible for
creating the filler order number. The filler order
number is expected to be unique within this assigning
authority.
3.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’
HL70301
HL70301
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
4
483
CWE R
[1,1]
Universal Service
Identifier
Identifier code for the test. This will be used to pass
PHLIP orderable test codes.
4.1
20
ST
RE
[1,1]
Identifier
Standardized Ordered test code.
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
4.2
199
ST
C(RE/X)
[1,1]
4.3
12
ID
C(R/X)
[1,1]
Text
Standardized Ordered test name
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
4.4
20
ST
RE
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
4.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Local ordered test name. Note that if the field is
collected as text in the application, this may be the
only field populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
4.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Locally defined ordered test code system for purpose
of sender or receiver. Local codes can be identified by
"L" (for backward compatibility) or "99zzz" (where z is
an alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
4.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
4.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
4.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
Laboratory Order Value
Set
HL70396
HL70396
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
7
26
TS
R
[1,1]
Observation Date/Time The date and time the specimen was collected.
A minimum of year, month and day must be provided
when the actual date/time is known. For unknown
collection date/time use "0000".
7.1
24
DTM R
[1,1]
Time
Date and time the specimen was collected
Note: This field must contain the same value as the
first component of SPM-17 and OBX.14
If you know the date and time, you must include at
least the year, month and day.
Format use:
YYYYMMDD[HH[MM[SS[.S[S[S[S]]]]]]][+/-ZZZZ]
Example: 20091124. If collection date and time is
unknown use "0000".
8
26
TS
[0,1]
Observation End
Date/Time
If specimen was collected over a period of time,
include observation end date/time
8.1
24
DTM R
[1,1]
Time
End point Date and time the specimen was collected
10
2945
XCN O
[0,*]
Collector Identifier
This field will identify the person, department or facility
that collected the specimen.
11
1
ID
O
[0,1]
12
483
CWE O
[0,1]
Danger Code
13
300
ST
RE
[0,1]
Relevant Clinical
Information
16
2945
XCN RE
[0,*]
Ordering Provider
Identifier of the provider who ordered the testing being
performed.
Note: Either this element is required or ORC.21 and
ORC.22
This is the same as ORC.12
If all you have is a single field text name then populate
OBR 16.2.1 with this value
This element may repeat
16.1
15
ST
RE
[1,1]
ID Number
Provider ID
16.2
194
FN
RE
[1,1]
Family Name
Ordering provider's last name
16.2.1
50
ST
R
[1,1]
Surname
16.2.2
20
ST
O
[1,1]
Own Surname Prefix
16.2.3
50
ST
O
[1,1]
Own Surname
16.2.4
20
ST
O
[1,1]
Surname Prefix From
Partner/Spouse
C(R/X)
HL7065
Specimen Action Code Specimen action code for identifying
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
16.2.5
50
ST
O
[1,1]
Surname From
Partner/Spouse
16.3
30
ST
RE
[1,1]
Given Name
16.4
30
ST
RE
[1,1]
Second and Further
Ordering provider's middle Initial or middle name
Given Names or Initials
Thereof
16.5
20
ST
RE
[1,1]
Suffix (e.g., JR or III)
Ordering provider's name suffix
16.6
20
ST
RE
[1,1]
Prefix (e.g., DR)
Ordering provider's name prefix
16.7
20
IS
O
[1,1]
HL70360
Degree (e.g., MD)
16.8
20
IS
O
[1,1]
HL70297
Source Table
16.9
227
HD
C(R/X)
[1,1]
Assigning Authority
The assigning authority for the ordering provider's ID
16.9.1
20
IS
RE
[1,1]
Namespace ID
Namespace ID of entity (e.g. NPI, your LIMS, etc)
that assigned the identifier above
16.9.2
199
ST
R
Universal ID
OID of entity (e.g. NPI, your LIMS, etc) that assigned
the identifier above
16.9.3
6
ID
R
[1,1]
HL70301
Universal ID Type
Literal value: ‘ISO’
16.10
5
ID
RE
[1,1]
HL70200
Name Type Code
16.11
4
ST
O
[1,1]
16.12
3
ID
O
[1,1]
HL7061
Check Digit Scheme
16.13
5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
16.14
227
HD
RE
[1,1]
Assigning Facility
16.14.1 20
IS
RE
[1,1]
Namespace ID
16.14.2 199
ST
R
16.14.3 6
ID
R
[1,1]
HL70301
Universal ID Type
16.15
1
ID
O
[1,1]
HL70465
Name Representation
Code
16.16
483
CE
O
[1,1]
HL70448
Name Context
16.18
1
ID
O
[1,1]
HL70444
Name Assembly Order
16.19
8
TS
O
[1,1]
Effective Date
16.20
8
TS
O
[1,1]
Expiration Date
16.21
199
ST
RE
[1,1]
Professional Suffix
16.22
705
CWE O
[1,1]
Assigning Jurisdiction
Ordering provider's first name
Identifier Check Digit
The facility that assigned the patient identifier. (Not
needed in most states)
Universal ID
Ordering provider's name suffix
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
16.23
705
CWE O
[1,1]
Assigning Agency or
Department
17
651
XTN RE
[0,2]
Order Callback Phone
Number
18
199
ST
O
[0,1]
Placer Field 1
19
199
ST
O
[0,1]
Placer Field 2
20
199
ST
O
[0,1]
Filler Field 1
21
199
ST
O
[0,1]
Filler Field 2
22
26
TS
R
[1,1]
Results Rpt/Status
Chng - Date/Time
22.1
24
DTM R
[1,1]
Time
23
504
MOC O
[0,1]
24
3
ID
O
[0,1]
HL7074
Diagnostic Serv Sect
ID
25
1
ID
R
[1,1]
HL70123
Result Status
Status of results for this order.
Corrected Results: A corrected result occurs when a
previously final result report (i.e., an OBR and
associated OBXs where OBR-25 was Final and all
OBX-11s were Final) is being resent with a change to
a value in one or more OBXs.
OBR-25 (Result Status): The status of the entire
report is marked as "C-Corrected" in OBR-25.
OBX-11 (Observation Result Status): The status of
each OBX is marked as either "Final" or "Corrected."
Those OBX values being corrected should have an
OBX-11 status of "C-Corrected." Those OBX values
that remain unchanged should have an OBX-11
status of "F-Final." A minimum of one OBX must be
marked as corrected.
26
755
PRL CE
[0,1]
Parent Result
The parent result
Field defined to make it available for linkages between
the parent result and its children result. This important
information, together with the information in OBR.29
Parent, uniquely identifies the OBX Segment of the
parent result related to this order.
26.1
483
CWE R
[1,1]
Parent Observation
Identifier
The OBX3 of the parent result
Submitter's contact info
Note: Not needed for PHLIP
Date/time the results were reported.
Note: MUST always generate a new time each time a
report is sent ( e.g prelim, final, corrected, resend)
Charge to Practice
Laboratory Observation
Identifier Value Set
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
26.1.1
20
ST
RE
[1,1]
Identifier
Standardized code.
Rule of conditionality: The standard code subcomponent is mandatory unless there is no standard
to match the local value passed by the application. An
attempt will be made by the sender to map the local
value to the standard. In the case that no standard
code was found, this field may be blank.
26.1.2
199
ST
C(RE/X)
[1,1]
26.1.3
12
ID
C(R/X)
[1,1]
Text
Standardized description.
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
26.1.4
20
ST
RE
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code sub-component
is mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in sub-component 5.
26.1.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
26.1.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
26.1.7
10
ST
RE
[1,1]
Coding System Version
ID
26.1.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
26.1.9
199
HL70396
HL70396
ST
C(R/X)
[1,1]
Original Text
26.1.10 20
ST
O
[1,1]
Second Alternate
Identifier
26.1.11 199
ST
O
[1,1]
26.1.12 12
ID
O
[1,1]
Second Alternate Text
HL70396
Second Name of
Alternate Coding
System
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
26.1.13 10
ST
O
[1,1]
Second Alternate
Coding System Version
ID
26.1.14 199
ST
O
[1,1]
Coding System OID
26.2
20
ST
RE
[1,1]
Parent Observation
Sub-identifier
OBX4 (Sub-ID) of the Parent Result
26.3
250
TX
RE
[1,1]
Parent Observation
Value Descriptor
The description of the organism from OBX-5, which
will have a data type of "ST" or "TX."
28
2945
XCN O
[0,*]
Result Copies To
29
855
EIP
CE
[0,1]
Parent
Parent ID number.
Field that relates a child to its parent when a parentchild relationship exists.
Note: OBR-29 is a complex field that contains both
the Placer order number (OBR-2) and the Filler order
number (OBR-3). OBR-29 is only needed if you need
to reference a parent result.
29.1
427
EI
O
[1,1]
Placer Assigned
Identifier
From ORC-2 (Placer Order Number) or OBR-2
(Placer Order Number) of parent.
29.1.1
199
ST
R
[1,1]
Entity Identifier
29.1.2
20
IS
RE
[1,1]
Namespace ID
29.1.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID
for the application/organization responsible for
creating the placer order number. The placer order
number is expected to be unique within this assigning
authority.
29.1.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’.
29.2
427
EI
R
[1,1]
Filler Assigned
Identifier
From ORC-3 (Filler Order Number) or OBR-3 (Filler
Order Number) of parent.
29.2.1
199
ST
R
[1,1]
Entity Identifier
29.2.2
20
IS
RE
[1,1]
Namespace ID
29.2.3
199
ST
R
[1,1]
Universal ID
Field required to contain an assigning authority OID
for the application/organization responsible for
creating the filler order number. The filler order
number is expected to be unique within this assigning
authority.
29.2.4
6
ID
R
[1,1]
Universal ID Type
Literal value: ‘ISO’.
HL70301
HL70301
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
31
483
CWE RE
[0,*]
31.1
20
ST
RE
[1,1]
Identifier
Code for Reason for Study
Note: Use Standard code ( ICD-9, ICD-10, SNOMED,
PHLIP ) or local code here.
31.2
199
ST
C(RE/X)
[1,1]
Text
Reason for Study Concept Name
Note: If SNOMED code, Use either SNOMED fully
specified concept name or SNOMED Preferred
concept name
31.3
12
ID
C(R/X)
[1,1]
Name of Coding
System
Code System for Reason for Study
Note: This will be SCT (for SNOMED), I9CD ( ICD9),
or ""L ""or ""99zzz"" (where zzz is any alphanumeric
character - not constrained to 3) for local coding
system.
31.4
20
ST
RE
[1,1]
Alternate Identifier
Code for Reason for Study
Note: Use Standard code ( ICD-9, ICD-10, SNOMED,
PHLIP ) or local code here.
31.5
199
ST
C(RE/X)
[1,1]
Alternate Text
Reason for Study Concept Name
Note: If SNOMED code, Use either SNOMED fully
specified concept name or SNOMED Preferred
concept name
31.6
12
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Code System for Reason for Study
Note: This will be SCT (for SNOMED), I9CD ( ICD9),
or ""L ""or ""99zzz"" (where zzz is any alphanumeric
character - not constrained to 3) for local coding
system.
31.7
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
31.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
31.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
32
838
NDL RE
[0,1]
Principal Result
Interpreter
32.1
409
CNN R
[1,1]
Name
32.1.1
15
ST
RE
[1,1]
ID Number
32.1.2
50
ST
RE
[1,1]
Family Name
32.1.3
30
ST
RE
[1,1]
Given Name
Reason For Study Value
Set
HL70396
HL70396
Reason for Study
OMB NO. 0920-0004
Seq
Len
TABLE 5-21. OBSERVATION REQUEST (OBR) SEGMENT PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
32.1.4
30
ST
RE
[1,1]
Second and Further
Given Names or Initials
Thereof
32.1.5
20
ST
RE
[1,1]
Suffix (e.g., JR or III)
32.1.6
20
ST
RE
[1,1]
32.1.7
5
IS
RE
[1,1]
32.1.9
20
IS
RE
[1,1]
Assigning Authority Namespace ID
32.1.10 199
ST
C(R/X)
[1,1]
Assigning Authority Universal ID
32.1.11 6
ID
C(R/X)
[1,1]
33
838
NDL O
[0,*]
Assistant Result
Interpreter
34
838
NDL O
[0,*]
Technician
35
838
NDL O
[0,*]
Transcriptionist
36
26
TS
O
[0,1]
Scheduled Date/Time
39
483
CWE O
[0,*]
44
483
CWE O
[0,1]
HL7088
Procedure Code
45
483
CWE O
[0,*]
HL70340
Procedure Code
Modifier
46
483
CWE O
[0,*]
HL70411
Placer Supplemental
Service Information
47
483
CWE O
[0,*]
HL70411
Filler Supplemental
Service Information
48
705
CWE O
[0,*]
HL70476
Medically Necessary
Duplicate Procedure
Reason.
49
2
IS
O
[0,1]
HL70507
Result Handling
50
705
CWE O
[0,1]
Laboratory Order Value
Set
Parent Universal
Service Identifier
Prefix (e.g., DR)
HL70360
HL70301
Degree (e.g., MD
Assigning Authority Universal ID Type
Collector's Comment
OMB NO. 0920-0004
2.11
OBSERVATION/RESULT (OBX) SEGMENT LEVEL PROFILE
The OBX Segment in the Test Result (ORU) Message is used to transmit observations related to the test result and
other information about patient and specimen, including test result, specimen-related information (such as specimen
IDs from both the test order and the test filler), additional information passed by the test order, etc.
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
1
4
SI
R
[1,1]
Set ID - OBX
Sequence number of the OBX in relation to the OBR
Segment to which it refers. The sequence number
should start at 1 and increment by 1 for each OBX in
the Order_Observation group.
2
3
ID
C(R/X)
[0,1]
HL70125
Value Type
The HL7 data type of the result in OBX-5.Field in
which allowed values are "CE," "CX," "NM," "SN,"
"ST," "TS" and "TX." The CE data type is used
primarily to convey epidemiologically important
information and coded lab results like organism name.
The CX data type is used primarily to convey
additional specimen identifiers in OBXs. The NM data
type is used to report a numeric value. The SN data
type is used to report a numeric clinical value with
qualifications. The ST data type is used to report a
short string of text. The TS data type is used to
convey the date/time of illness onset. The TX data
type is used to carry a large text observation.
3
483
CWE R
[1,1]
Laboratory Observation
Identifier Value Set
Observation Identifier
Unique identifier for the observation. This field will be
populated by either a resulted test identifier (i.e.
LOINC or PLT) or an identifier for an observation
related to patient or specimen information (EPI
question).
3.1
20
ST
RE
[1,1]
Identifier
Standardized code (LOINC or PLR)
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard.
3.2
199
ST
C(RE/X)
[1,1]
Text
Standardized description.
Note: If LOINC, use LOINC Short Name or LOINC
Long Common Name
Formatted: Left, Outline numbered + Level: 2 +
Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment:
Left + Aligned at: 0.1" + Indent at: 0.5"
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
C(RE/X)
[1,1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed. Not required but
recommended to always send
local codes.
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
3.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
3.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
4
20
ST
C(R/X)
[0,1]
Observation Sub-ID
Conditionality Rule: Field required if there is more
than one OBX with the same OBX.3 (Observation
Identifier) associated with the same OBR. Normally,
this field is populated with a number, but text values
may also be used.
5
99999
VARI C(RE/X)
ES
[0,1]
Observation Value
Actual observation associated with the test order. The
data type in OBX.2 Value Type indicates the format of
the observation.
Note: Rule of conditionality: This data element is
required unless OBX.11 = ‘X’ or ‘N’. This data type
transmits a code and the text associated with the
code.
3.3
12
ID
C(R/X)
[1,1]
3.4
20
ST
RE
3.5
199
ST
3.6
12
3.7
HL70396
HL70396
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
Begin OBX-5 Data Types
CWE
coded results
5.1
20
ST
R
Identifier
coded result
5.2
199
ST
RE
Text
coded result text
5.3
12
ID
R
Name of Coding
System
code system for coded result in component 1
5.4
20
ST
RE
Alternate Identifier
coded result
5.5
199
ST
RE
Alternate Text
coded result text
5.6
12
ID
C(R/X)
Name of Alternate
Coding System
code system for coded result in component 1
5.7
10
ST
RE
Coding System Version Version of code system identified in component 3
ID
5.8
10
ST
RE
Alternate Coding
System Version ID
Version of code system identified in component 6
5.9
199
ST
RE
Original Text
original text of result
5.1
2
ST
RE
[1,1]
Comparator
5.2
65536
NM
RE
[1,1]
Num1
5.3
1
ST
RE
[1,1]
Separator/Suffix
5.4
65536
NM
RE
[1,1]
Num2
99999
ST
C(RE/X)
[0,1]
Observation Value
99999
ST,
TX,
or
FT
C(RE/X)
[0,1]
Observation Value
24
DTM C(RE/X)
[0,1]
Date/Time
99999
NM
C(RE/X)
[0,1]
Observation Value
1913
CX
R
[1,*]
Identifier
HL70396
HL70396
SN
ST
5
TX
5
TX
5.1
NM
5
CX
5
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
5.1
15
ST
R
[1,1]
5.2
4
ST
O
[1,1]
ID Number
5.3
3
ID
O
[1,1]
5.4
227
HD
R
[1,1]
Assigning Authority
5.4.1
20
IS
RE
[1,1]
Namespace ID
5.4.2
199
ST
R
5.4.3
6
ID
R
[1,1]
HL70301
Universal ID Type
5.5
5
ID
R
[1,1]
HL70203
Identifier Type Code
5.6
227
HD
RE
[1,1]
Assigning Facility
5.6.1
20
IS
RE
[1,1]
Universal ID
5.6.2
199
ST
R
5.6.3
6
ID
R
[1,1]
5.7
8
DT
O
[1,1]
Effective Date
5.8
8
DT
O
[1,1]
Expiration Date
5.9
705
CWE O
[1,1]
Assigning Jurisdiction
5.10
70
CWE O
[1,1]
Assigning Agency or
Department
Check Digit
HL7061
Check Digit Scheme
Universal ID
Universal ID Type
HL70301
Identifier Type Code
End OBX-5 Data Types
6
483
CWE C(R/X)
[0,1]
Units
Field populated with units of measure if the data type
identified in OBX.2 (and carried in OBX.5) is ""SN." If
we use C, then need to explain to use “1” for any
unitless value in OBX.5, for example a titer.
Note: If the data type in OBX 2 is "NM" or "SN" and
the OBX-11 observation result status is not ‘X’ then
this field is Required.
6.1
20
ST
RE
[1,1]
Identifier
Standardized code.
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
6.2
199
ST
C(RE/X)
[1,1]
Text
Standardized description.
UCUM
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
C(RE/X)
[1,1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
10
ST
RE
[1,1]
Coding System Version Version of code system identified in component 3
ID
6.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Version of code system identified in component 6
6.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
7
60
ST
RE
[0,1]
References Range
Interpretation range that applies to the value reported
in OBX-5. It should provide enough information to
understand the abnormal flags reported in OBX.8.
8
20
CWE C(RE/X)
[0,*]
Abnormal Flags
Indicator of the normalcy of the result found in OBX.5.
8.1
20
ST
RE
[1,1]
Identifier
Interpretation code from HL7 table 0078
8.2
199
ST
C(RE/X)
[1,1]
Text
Interpretation code text from HL7 table 0078
8.3
12
ID
C(R/X)
[1,1]
Name of Coding
System
Literal: 'HL70078'
8.4
20
ST
RE
[1,1]
Alternate Identifier
Note: Can be empty in PHLIP
8.5
199
ST
C(RE/X)
[1,1]
Alternate Text
8.6
12
ID
C(R/X)
[1,1]
6.3
12
ID
C(R/X)
[1,1]
6.4
20
ST
RE
6.5
199
ST
6.6
12
6.7
HL70396
HL70396
HL7078
HL70396
HL70396
Name of Alternate
Coding System
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
8.7
10
ST
RE
[1,1]
Coding System Version Version of HL7 table 0078
ID
8.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Recommended if a coding system is identified in
component 6.
8.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
9
5
NM
O
[0,1]
Probability
10
2
ID
O
[0,1]
HL7080
Nature of Abnormal
Test
11
1
ID
R
[1,1]
HL7085
Observation Result
Status
12
26
TS
O
[0,1]
Effective Date of
Reference Range
Values
13
20
ST
O
[0,1]
User Defined Access
Checks
14
26
TS
CE
[0,1]
Date/Time of the
Observation
14.1
24
DTM R
[1,1]
Time
15
483
CWE O
[0,1]
Producer's ID
Status of the observation result.
Corrected Results: A corrected result occurs when a
previously final result report (i.e., an OBR and
associated OBXs where OBR-25 was "Final" and all
OBX-11s were Final) is being resent with a change to
a value in one or more OBXs.
OBR-25 (Result Status): The status of the entire
report is marked as "C-Corrected" in OBR-25.
OBX-11 (Observation Result Status): The status of
each OBX is marked as either "Final" or "Corrected."
Those OBX values being corrected should have an
OBX-11 status of "C-Corrected." Those OBX values
that remain unchanged should have an OBX-11
status of "F-Final." A minimum of one OBX must be
marked as corrected.
OBX-11 = “N” - Not asked; used to affirmatively
document that the observation identified in the OBX
was not sought when the universal service ID in OBR4 implies that it would be sought.
OBX-11 = ‘X” - Results cannot be obtained for this
observation
Specimen collection date and time. This is the same
as OBR.7 and SPM.17
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
16
2945
XCN O
[0,*]
17
483
CWE RE
[0,*]
17.1
20
ST
RE
[1,1]
17.2
199
ST
C(RE/X)
[1,1]
17.3
12
ID
C(R/X)
[1,1]
17.4
20
ST
RE
17.5
199
ST
17.6
12
17.7
Responsible Observer
Observation Method
Additional details about the test method
Identifier
Standardized code.
Rule of conditionality: The standard code component
is mandatory unless there is no standard to match the
local value passed by the application. An attempt will
be made by the sender to map the local value to the
standard. In the case that no standard code was
found, this field may be blank.
Text
Standardized description.
Name of Coding
System
HL7 identifier for Coding System (e.g. “LN” = LOINC).
Rule of conditionality: The HL7 coding system
identifier is always required if there is a value in
component 1.
[1,1]
Alternate Identifier
Local code.
Rule of conditionality: The local code component is
mandatory if there is no standard to match the local
value passed by the application AND there is no text
present in component 5.
C(RE/X)
[1,1]
Alternate Text
Local description. Note that if the field is collected as
text in the application, this may be the only field
populated if the data type is "Coded."
Rule of conditionality: Required if no standardized
code or local code value passed.
ID
C(R/X)
[1,1]
Name of Alternate
Coding System
Locally defined codes for purpose of sender or
receiver. Local codes can be identified by "L" (for
backward compatibility) or "99zzz" (where z is an
alphanumeric character).
Rule of conditionality: Required if an alternate
identifier is present.
10
ST
RE
[1,1]
Coding System Version Recommended if a coding system is identified in
ID
component 3.
17.8
10
ST
RE
[1,1]
Alternate Coding
System Version ID
Recommended if a coding system is identified in
component 6.
17.9
199
ST
C(R/X)
[1,1]
Original Text
Original text
18
427
EI
O
[0,*]
Equipment Instance
Identifier
HL7 V3 Observation
Method
HL70396
HL70396
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
19
26
TS
19.1
24
23
567
23.1
23.2
RE
[0,1]
Date/Time of the
Analysis
DTM R
[1,1]
Time
XON R
[1,1]
Performing
Organization Name
Name and ID of the performing lab
Note: For producing laboratories that are CLIAcertified, the CLIA identifier should be used for the
organization identifier (component 10).
50
ST
C(R/RE)
[1,1]
Organization Name
Name of the performing lab
20
IS
RE
[1,1]
Organization Name
Type Code
Name type code of the performing Lab
23.4
4
NM
O
[1,1]
23.5
3
ID
O
[1,1]
23.6
227
HD
C(R/X)
[1,1]
Assigning Authority
Organization that assigned LAB ID
Note: The assigning authority is CLIA for CLIA
certified labs
23.6.1
20
IS
RE
[1,1]
Namespace ID
Namespace ID of entity (e.g. CLIA) that assigned the
facility identified below
23.6.2
199
ST
R
Universal ID
OID of entity (e.g. CLIA) that assigned the identifier
Note: If the ID is an NPI use: 2.16.840.1.113883.4.6.
If it's a CLIA number use: 2.16.840.1.113883.4.7
23.6.3
6
ID
R
[1,1]
HL70301
Universal ID Type
Literal value: ‘ISO’
23.7
5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
23.8
227
HD
O
[1,1]
23.9
1
ID
O
[1,1]
23.10
20
ST
RE
[1,1]
Organization Identifier
Public Health Lab CLIA ID
24
631
XAD R
[1,1]
Performing
Organization Address
The Address of the laboratory that actually performed
the test - whether or not is used as a reference
laboratory.
24.1
184
SAD RE
[1,1]
Street Address
24.1.1
120
ST
R
[1,1]
Street or Mailing
Address
24.1.2
50
ST
O
[0,1]
Street Name
24.1.3
12
ST
O
[0,1]
Dwelling Number
HL70204
Time at which the testing was performed
Note: Use this field instead of OBX.14 for date and
time of testing. (CLIA requirement)
Check Digit
HL7061
Check Digit Scheme
Assigning Facility
HL70465
Name Representation
Code
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
24.2
120
ST
RE
[1,1]
Other Designation
Other Designation
Note: This isn't needed for most addresses. It could
be a district name, building name, floor number, etc
24.3
50
ST
RE
[1,1]
24.4
50
ST
RE
[1,1]
State Value Set
City
City
State or Province
State or Province
Note: FIPS 5-2 alpha codes are supported
24.5
12
ST
RE
[1,1]
Postal Code Value Set
Zip or Postal Code
Zip or Postal Code
Note: US Zip Codes, Zip+4 and Canadian Postal
Codes are supported.
24.6
3
ID
RE
24.7
3
ID
RE
[1,1]
Country Value Set
Country
Country
[1,1]
HL70190
Address Type
24.8
50
ST
O
[1,1]
Address Type code from HL7 Table 190
Other Geographic
Designation
May be used for MSAs (Metropolitan and Micropolitan
Statistical Areas). Source:
http://www.whitehouse.gov/omb/bull etins/fy2007/b0701.pdf
24.9
20
IS
RE
[1,1]
24.10
20
IS
O
[1,1]
Census Tract
24.11
1
ID
O
[1,1]
Address
Representation Code
24.13
24
TS
O
[1,1]
Effective Date
24.14
24
TS
O
[1,1]
Expiration Date
25
3002
XCN RE
[0,1]
Performing
Organization Medical
Director
25.1
15
ST
RE
[1,1]
ID Number
25.2
194
FN
RE
[1,1]
Family Name
25.2.1
50
ST
R
[1,1]
Surname
25.2.2
20
ST
O
[1,1]
Own Surname Prefix
25.2.3
50
ST
O
[1,1]
Own Surname
25.2.4
20
ST
O
[1,1]
Surname Prefix From
Partner/Spouse
25.2.5
50
ST
O
[1,1]
Surname From
Partner/Spouse
25.3
30
ST
RE
[1,1]
Given Name
PHVS_County_FIPS_6-4 County/Parish Code
County code from FIPS6_4
Note: This element can be empty of PHLIP
Public Health Lab Director
OMB NO. 0920-0004
Seq
Len
TABLE 5-22. OBSERVATION/RESULT SEGMENT (OBX) PROFILE - ORU^R01 USAGE
Value Set
Dt Usage
Cardinality
Element Name
Description
Name
25.4
30
ST
RE
[1,1]
Second and Further
Given Names or Initials
Thereof
25.5
20
ST
RE
[1,1]
Suffix (e.g., JR or III)
25.6
20
ST
RE
[1,1]
25.7
20
IS
O
[1,1]
HL70360
Degree (e.g., MD)
25.8
20
IS
O
[1,1]
HL70297
Source Table
25.9
227
HD
C(R/X)
[1,1]
Assigning Authority
25.6.1
20
IS
RE
[1,1]
Namespace ID
25.6.2
199
ST
R
25.6.3
6
ID
R
[1,1]
HL70301
Universal ID Type
25.10
5
ID
RE
[1,1]
HL70200
Name Type Code
25.11
4
ST
O
[1,1]
25.12
3
ID
O
[1,1]
HL7061
Check Digit Scheme
25.13
5
ID
C(R/X)
[1,1]
HL70203
Identifier Type Code
25.14
227
HD
RE
[1,1]
Assigning Facility
25.14.1 20
IS
RE
[1,1]
Namespace ID
25.14.2 199
ST
R
25.14.3 6
ID
R
[1,1]
HL70301
Universal ID Type
25.15
1
ID
O
[1,1]
HL70465
Name Representation
Code
25.16
483
CE
O
[1,1]
HL70448
Name Context
25.18
1
ID
O
[1,1]
HL70444
Name Assembly Order
25.19
8
TS
O
[1,1]
Effective Date
25.20
8
TS
O
[1,1]
Expiration Date
25.21
199
ST
RE
[1,1]
Professional Suffix
25.22
705
CWE O
[1,1]
Assigning Jurisdiction
25.23
705
CWE O
[1,1]
Assigning Agency or
Department
Prefix (e.g., DR)
Universal ID
Identifier Check Digit
Universal ID
2.1
Formatted: Right, Indent: Left: 0.5", No bullets or
numbering
OMB NO. 0920-0004
3
PHLIP DATA ELEMENTS OF INTEREST
3.1 COLUMN DEFINITIONS FOR ELEMENTS OF INTEREST TABLE
Column
Description
Program Variables Section
PHIN Variable ID
PHIN element UID drawn from the coding system PH_PHINQuestions_CDC
Label
Short name for the data element, which is passed in the message.
Description
Description of the data element.
Data Type
Data type for the variable response expected by the program area
Prog. Req/Opt
Indicator whether the program specifies the field as:
R - Required - mandatory for sending the message
RE – Required, but may be empty – sender must be able to process (collect/store, display/print etc) this data element and needs
to send data, if information is available, but need not make up “null” values, if information is not available
O - Optional - if the data is available it should be passed
May Rpt
Indicator whether the response to the data element may repeat. “Yes” in the field indicates that it may; otherwise, the field is not
populated. Repeats require special processing.
Value Set Name
Name of the pre-coordinated value set from which the response is drawn. The value sets and
coding systems are accessible via the Public Health Information Network Vocabulary Access
and Distribution Services at http://phinvads.cdc.gov/vads/SearchVocab.action
Message Mapping Methodology Section
Message Context
Specific HL7 segment and field mapping for the element.
OMB NO. 0920-0004
HL7 Data Type
HL7 data type used by PHIN to express the variable.
HL7 Usage
Use of the field for PHIN. Indicates if the field is required, optional, or conditional in a segment. The only values that appear in the
Message Mapping are:
• R – Required. Must always be populated
• O – Optional. May optionally be populated.
HL7 Rpt
Indicator whether the response to the data element may repeat. “Yes” in the field indicates that it may; otherwise, the field is not
populated. Repeats require special processing.
3.2 DATA ELEMENTS OF INTEREST FOR UNSOLICITED RESULTS
The CDC Influenza Epidemiologists have defined the elements listed in the following table as Data Elements of
Interest.
The PHLIP Data Elements of Interest are cross-referenced below to the HL7 context in which the element would be
expressed in the unsolicited result message. Please note that all of the Data Elements of Interest for the unsolicited
result are included, although each site may opt not to send a particular data element that is not a required data
element.
OMB NO. 0920-0004
Variable ID
DEM197
Program Specific Data Elements for Unsolicited Results
Label
Description
Value Set Name
Data Prog.
May
Type
Req/
Rpt
Opt
Local
The local ID of
Text
R
patient ID
the
patient/entity.
DEM115
Birth Date
Reported date
of birth of
patient.
Date
RE
DEM113
Patient’s
sex
Patient’s current
sex.
Code
O
Administrative Sex
DEM162
Patient
Address
State
Patient’s
address state.
Code
RE
State
DEM163
Patient
Address Zip
Code
Patient’s
address zip
code.
Text
RE
DEM165
Patient
Address
County
County of
residence of the
subject.
Code
RE
County
Mapping Methodology
Message Context
HL7
HL7
Usage
Data
Type
PID-3 Patient Identifier List
CX
R
(Note that the variable ID and
label do not appear in the
message.)
PID-7 Date/Time of Birth
TS
O
(Note that the variable ID and
label do not appear in the
message.)
PID-8 Administrative Sex
IS
O
(Note that the variable ID and
label do not appear in the
message.)
PID-11.4 Patient Address ST
O
State (Note that the variable
ID and label do not appear in
the message.)
PID-11.5 Patient Address ST
O
Postal Code (Note that the
variable ID and label do not
appear in the message.)
PID-11.9 Patient Address –
IS
O
County or
OBX.5 Observation Value
Formatted Table
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
Message Context
HL7
Data
Type
HL7
Usage
LAB505
Submitting
Laboratory
Name
Name of
organization
collecting
specimen
Text
O
OBR-10 Collector Identifier
(Note that the variable ID and
label do not appear in the
message.)
XCN
O
LAB128
Submitting
Physician
Name
Ordering
Provider
Text
O
OBR-16 Ordering Provider
(Note that the variable ID and
label do not appear in the
message.)
XCN
O
LAB143
Laboratory
ID
Laboratory ID of
the public health
lab sending the
result
OID
R
MSH-4.2 Sending FacilityUniversal ID component
(Note that the variable ID and
label do not appear in the
message.)
HD
R
TS
R
May
Rpt
Value Set Name
Mapping Methodology
MSH-4.3 Universal ID Type.
Literal value: ‘ISO’
LAB163
Collection
Date
Date clinical
specimen was
collected
Date
C
OBR-7 Observation
Date/Time (Note that the
variable ID and label do not
appear in the message.)
Conditionality Rule: If
Receive Date is not
populated, Collection Date
must be present.
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
LAB334
Receive
Date
Date specimen
was received at
public health
laboratory
Date
C
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
OBR-14 Specimen Received
Date/Time (Note that the
variable ID and label do not
appear in the message.)
TS
O
Conditionality Rule: If
Collection Date is not
populated, Receive Date
must be present
LAB165
Specimen
Source
Source of
Specimen
Code
R
Specimen Source
(PHLIP)
OBR-15 Specimen Source
(Note that the variable ID and
label do not appear in the
message.)
CM
O
LAB101
Test
PerformedCode
Test code as
known by the
laboratory
Code
R
Resulted Lab Test
Name (PHLIP Flu)
or
PHLIP Questions
(Flu)
OBX-3 Observation Identifier
(Note that the variable ID and
label do not appear in the
message.)
2.3.1:
CE
R
OBX-5 Observation Value
SN
O
OBX-5 Observation Value
2.3.1:
CE
O
LAB114
Numeric
Result
Value
Test result in
numeric format
Numeric
C
LAB192
Coded
Result
Value
Test result as
coded value
Code
C
Lab Test Result
(PHLIP Flu)
2.5.1:
CWE
2.5.1:
CWE
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
LAB108
Test Date
Date specimen/
isolate was
tested
Date
O
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
OBX-14 Date/Time of
Observation (Note that the
variable ID and label do not
appear in the message.)
TS
O
CX
O
Note: This is a deviation
from HL7 2.3.1 where
this field is the
Collection Date/Time.
LAB202
Specimen
ID
Unique
specimen/
accession/
aliquot ID
assigned by
laboratory-
Code
R
Observation/OBX Segment
with this variable ID and
label.
OBX-2 = CX
OBX-3 = LAB202^Unique
Specimen
ID^PHINQUESTION
OBX-5 = Specimen
ID^^^Assigning Authority
Name&Assigning Authority
ID&Assigning Authority ID
Type
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
21612-7
Reported
Patient Age
Patient’s age as
reported in an
application at
the source
Numeric
with
Units
RE
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
Observation/OBX Segment
with this variable ID and
label.
SN
O
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-2 = SN
OBX-3 = 21612-7^ Age
Patient Qn Reported^LN
OBX-5 = Age number
OBX-6 = Age units
FLU002
Vaccinated
Was the patient
vaccinated for
Influenza?
Code
O
Yes No Unknown
(YNU)
OBX-3 = FLU002^ Was the
patient vaccinated for
influenza?^ PHINQUESTION
OBX-5 = Y/N
Identifier^Text^HL70136
Or UNK^unknown^ NULLFL
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
FLU001
Antiviral
Medication
Was the patient
receiving
influenza
antiviral
medication?
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
HL7
Usage
Yes No Unknown
(YNU)
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = FLU001^Was the
patient receiving influenza
antiviral medication?
^PHINQUESTION
LAB514
Outbreak
Related
Was the
specimen
outbreak
related?
Code
O
Yes No Unknown
(YNU)
OBX-5 =
Y/N^Identifier^Text^HL70136
Or UNK^unknown^ NULLFL
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = LAB514^ Was this
specimen related to an
outbreak?^PHINQUESTION
OBX-5 =
Y/N^Identifier^Text^HL70136
Or UNK^unknown^ NULLFL
O
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
LAB330
Type of
Facility
Did the
specimen come
from an
outpatient,
inpatient or
long-term care
facility?
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
HL7
Usage
Patient Location
Status at
Specimen
Collection
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = LAB330^ Patient
location status at specimen
collection (e.g., outpatient,
inpatient, long-term
care).^PHINQUESTION
OBX-5 = I/O/
Identifier^Text^HL70004
Or 282E00000X^Long Term
Care Hospital^ HCPT
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
PHLIP01
Travel
Outside the
US
Did the patient
travel outside
the U.S. within
10 days of
illness onset?
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
HL7
Usage
Yes No Unknown
(YNU)
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = PHLIP01^Did the
patient travel outside the
U.S. within 10 days of illness
onset?^PHINQUESTION
OBX-5 =
Y/N^Identifier^Text^HL70136
Or UNK^unknown^ NULLFL
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
TRAVEL05
Destination
(s) Traveled
To
International
destination(s)
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
HL7
Usage
Country
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = TRAVEL05^
International destination(s)
^PHINQUESTION
OBX-5 = Country
Identifier^Text^ISO31661^Local Identifier^Local
Text^Name of Coding
System
Business Rule: Only
applicable if PHLIP01 was
“Yes”.
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
LAB515
Isolate Sent
to CDC
Is Isolate being
sent to CDC?
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
HL7
Usage
Yes No Unknown
(YNU)
Observation/OBX Segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = LAB515^Was
isolate sent to CDC?
^PHINQUESTION
11368-8
Illness
Onset Date
Date and time of
illness onset
Date
O
OBX-5 =
Y/N^Identifier^Text^HL70136
Or UNK^unknown^ NULLFL
Observation/OBX Segment
with this variable ID and label
OBX-2 = TS
OBX-3 =
11368-8^ILLNESS/INJURY
ONSET DATE/TIME^LN
OBX-5 = Date/time of illness
onset = TS
TS
O
HL7
Rpt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
LAB517
Isolate ID
Sent to
CDC
Laboratory ID
assigned to the
isolate sent to
the CDC
Code
O
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
Observation/OBX Segment
with this variable ID and label
CX
O
TX
O
HL7
Rpt
OBX-2 = CX
OBX-3 = LAB517^Identifier
assigned by laboratory to the
isolate sent to
CDC^PHINQUESTION
OBX-5 = Isolate
ID^^^Assigning Authority
Name&Assigning Authority
ID&Assigning Authority ID
Type
PHLIP02
Passage
History
History of
Culture Medium
Text
O
Observation/OBX segment
with this variable ID and label
OBX-2 = TX
OBX-3 = PHLIP02^History of
culture medium
^PHINQUESTION
OBX-5 = Passage History
Text Description
Formatted Table
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
95417-2
First
Test
Is the patient's
first test for the
condition of
interest
Code
O
May
Rpt
Value Set Name
Yes No Unknown
(YNU)
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
Observation/OBX segment
with this variable ID and label
2.3.1:
CE
O
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
HL7
Rpt
OBX-3 = 95417-2^First test
for condition of interest^LN
95418-0
Employe
d in
Healthca
re
Is the patient
employed in a
healthcare
setting
Code
O
Yes No Unknown
(YNU)
OBX-5 OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
Observation/OBX segment
with this variable ID and label
2.3.1:
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
2.5.1:
CWE
OBX-3 = 95418-0^Employed
in a healthcare setting^LN
OBX-5 OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
O
Formatted Table
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
95419-8
Sympto
matic
Did the patient
have symptoms
related to
condition of
interest
Code
O
May
Rpt
Value Set Name
Yes No Unknown
(YNU)
Mapping Methodology
Message Context
HL7
Data
Type
Observation/OBX segment
with this variable ID and label
2.3.1: O
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
HL7
Usage
HL7
Rpt
2.5.1:
CWE
OBX-3 = 95419-8^Has
symptoms related to
condition of interest^LN
65222-2
Date of
Sympto
m Onset
Date and time
of symptom
onset
Date
O
mm/dd/yy
OBX-5 OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
Observation/OBX segment
with this variable ID and label
OBX-2 = DT
OBX-3 = UPDATED LOINC
65222-2^Date and time of
symptom onset^LN
OBX-5 = formatted as
YYYYMMDD
DT or
TS
O
Formatted Table
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
75325-1
Sympto
ms
Symptoms the
patient
experienced
Code
O
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
HL7
Usage
Observation/OBX segment with
this variable ID and label
2.3.1: O
CE
HL7
Rpt
Formatted Table
Formatted: Font: 8.5 pt
OBX-2 = CWE
OBX-3 =75325-1^Symptom^LN
2.5.1:
CWE
OBX-4 = if needed for more than
one symptom (suggest to
number sequentially starting with
"1" for each occurrence)
OBX-5 can be one of:
49727002^Cough^SCT
426000000^Fever over 100.4
Fahrenheit^SCT
267036007^Shortness of
Breath^SCT
84229001^Fatigue^SCT
25064002^Headache^SCT
62315008^Diarrhea^SCT
103001002^Feeling
feverish^SCT
43724002^Chills^SCT
230145002^Difficulty
breathing^SCT
68962001^Muscle pain^SCT
36955009^Loss of sense of
taste^SCT
44169009^Loss of sense of
smell^SCT
162397003^Sore throat^SCT
68235000^Nasal
congestion^SCT
64531003^Nasal
Discharge^SCT
422587007^Nausea^SCT
422400008^Vomiting^SCT
Formatted: Font: 8 pt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
77974-4
Hospitali
zation
Patient
hospitalization
status due to
condition
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
Yes No Unknown
(YNU)
Observation/OBX segment
with this variable ID and label
2.3.1: O
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
HL7
Usage
HL7
Rpt
2.5.1:
CWE
OBX-3 = 77974-4^Patient
was hospitalized because of
this condition^LN
95420-6
ICU
Patient was
admitted to
intensive care
unit for
condition of
interest
Code
O
Yes No Unknown
(YNU)
OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
Observation/OBX segment
with this variable ID and label
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
OBX-3 = 95420-6^Admitted
to intensive care unit for
condition of interest^LN
OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
2.3.1: O
CE
2.5.1:
CWE
Formatted Table
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
95421-4
Congreg
ate Care
Did the patient
reside in a
congregate
care setting
Code
O
May
Rpt
Mapping Methodology
Value Set Name
Message Context
HL7
Data
Type
Yes No Unknown
(YNU)
Observation/OBX segment
with this variable ID and label
2.3.1: O
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
OBX-3 = 95421-4^Resides
in a congregate care
setting^LN
OBX-5 can be one of:
Y^Yes^HL70136
N^No^HL70136
UNK^Unknown^NULLFL
2.5.1:
CWE
HL7
Usage
HL7
Rpt
Formatted Table
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
75617-1
Residen
ce Type
The type of
residence of
the congregate
care setting
Code
O
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
Observation/OBX segment with
this variable ID and label
2.3.1: O
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
OBX-3 = 75617-1^Residence
type^LN
OBX-5 can be one of:
22232009^Hospital^SCT
2081004^Hospital ship^SCT
32074000^Long term care
hospital^SCT
224929004^Secure
hospital^SCT
42665001^Nursing home^SCT
30629002^Retirement
home^SCT
74056004^Orphanage^SCT
722173008^Prison-based care
site^SCT
20078004^Substance abuse
treatment center^SCT
257573002^Boarding
house^SCT
224683003^Military
accommodation^SCT
284546000^Hospice^SCT
257628001^Hostel^SCT
310207003^Sheltered
housing^SCT
257656006^Penal
institution^SCT
285113009^Religious
institutional residence^SCT
2.5.1:
CWE
HL7
Usage
HL7
Rpt
Formatted Table
Formatted: Font: 8.5 pt
OMB NO. 0920-0004
Program Specific Data Elements for Unsolicited Results
Variable ID
Label
Description
Data
Type
Prog.
Req/
Opt
82810-3
Pregnan
t
Pregnancy
status of patient
Code
O
May
Rpt
Value Set Name
Mapping Methodology
Message Context
HL7
Data
Type
Observation/OBX segment
with this variable ID and label
2.3.1: O
CE
2.3.1 OBX-2 = CE
2.5.1 OBX-2 = CWE
HL7
Usage
HL7
Rpt
2.5.1:
CWE
OBX-3 = 828103^Pregnancy status^LN
30525-0
Age
Patient Age
Numeric
with
Units
O
OBX-5 can be one of:
77386006^Patient currently
pregnant^SCT
102874004^Possible
pregnancy^SCT
60001007^Not
pregnant^SCT
UNK^Unknown^NULLFL
Observation/OBX segment
with this variable ID and label
OBX-2 = NM (can be SN)
OBX-3 = 305250^Age^LN^^^^2.68
OBX-5 = numeric value
OBX-6 = age units in UCUM
as applicable - expected as
years => a^year^UCUM
other options:
months =>
mo^month^UCUM
days => d^day^UCUM
hours => h^hour^UCUM
NM or O
SN
Formatted Table
OMB NO. 0920-0004
4
SAMPLE HL7 MESSAGE
4.1 STORYBOARD
Dr. Marcus Welby, Jr., sees Jared Doe, Jr., a 30-year-old male, during an office visit. Jared Doe
presents symptoms of fever, cough, sore throat and muscle aches, all consistent with a diagnosis of
influenza or SARS-CoV-2. While examining the patient, Dr. Welby discovers that Mr. Doe has been
traveling outside of the United States recently, specifically Italy, West Africa, and Bangkok. Dr.
Welby decides to order an Influenza and SARS-CoV-2 Identification Test from his local public health
department to determine the type of virus the patient has acquired.
A sputum sample is taken from the patient, and an electronic order for the testing is placed through
Dr. Welby's EHR application, a Northeast Medical Center ordering application. The Northeast
Medical Center ordering application transmits the order to the Virginia State STARLIMS application
for processing. Dr. Welby sends the patient home, prescribing bed rest, plenty of fluids and an antiinflammatory, such as ibuprofen or aspirin.
The Virginia State Public Health Laboratory tests the specimen collected from Mr. Doe and finds it
to be positive for influenza A and negative for SARS-CoV-2. The laboratory tests the specimen
further to determine the subtype of the influenza virus and finds the specimen is not positive for
normally circulating influenza viruses. They further test the virus for influenza A/H5 and A/H7 based
on Mr. Doe’s travel history.
4.1.1 Sample HL7 V2.3.1
MSH|^~\&|VA STARLIMS Stage^2.16.840.1.114222.4.3.3.2.2.1^ISO|VA PHL
Richmond^2.16.840.1.114222.4.1.9977^ISO|US WHO Collab LabSys^2.16.840.1.114222.4.3.3.7^ISO|CDC EPI Surv
Branch^2.16.840.1.114222.4.1.10416^ISO|200707071830||ORU^R01|200707070897|P|2.3.1 |||||||||
PHLIP_ORU_v1.0.2^PHIN_Profile_ID^2.16.840.1.114222.4.10.3^ISO
PID|1||105431122VA^^^VA STARLIMS_Stage&2.16.840.1.114222.4.3.3.2.2.1&ISO^MR^VA PHL
Richmond&2.16.840.1.114222.4.1.9977&ISO||Doe^Jared^Q^Jr^^BBA^L||19760909|M||2106-3^White^CDCREC~20289^Asian^CDCREC|2166 Wells Dr^AptB^Richmond^51^23235^US^H|||||||||||2186-5^Not Hispanic or
Latino^CDCREC^N^Not Hispanic^L||||||||N
ORC|RE|NE5400123^NE Med System^2.16.840.1.114222.75.9.1.2.1^ISO|F67993405^VA STARLIMS
Stage^2.16.840.1.114222.4.3.3.2.2.1^ISO||CM||||||||||||||||Northeast Medical Center|1600 Hospital
Drive^Ste 350^Richmond^51^23235^US^M|^WPN^PH^^^804^6486154^320~^NET^X.400^[email protected]
OBR|1|NE5400123^NE Med System^2.16.840.1.114222.75.9.1.2.1^ISO|F67993405^VA STARLIMS
Stage^2.16.840.1.114222.4.3.3.2.2.1^ISO|PLT40^Epidemiologically Important Information Influenza^PLT|||200706270930|||||||200706271530|SPT&Sputum& HL70070&SPU&Sputum&L|
^Welby^Marcus^J^Jr^Dr^MD|||||||||F
OBX|1|SN|21612-7^Age Patient Qn Reported^LN||^30|a^year^UCUM|||||F
OBX|2|CE|FLU002^Was the patient vaccinated for Influenza?^PHINQUESTION||Y^Yes^HL70136||||||F
OMB NO. 0920-0004
OBX|3|CE|FLU001^Was the patient receiving influenza antiviral medication?^PHINQUESTION||
N^No^HL70136||||||F
OBX|4|CE|LAB514^Was this specimen related to an outbreak?^PHINQUESTION||Y^Yes^ HL70136||||||F
OBX|5|CE|LAB330^Patient location status at specimen collection (e.g., outpatient, inpatient, long-term
care)^PHINQUESTION||O^Outpatient^HL70489||||||F
OBX|6|CE|PHLIP01^Did the patient travel outside the U.S. within 10 days of illness onset?
^PHINQUESTION||Y^Yes^HL70136||||||F
OBX|7|CE|TRAVEL05^International destination(s)^PHINQUESTION||IT^Italy^ISO3166-1~^^^WTAF^West
Africa^L~^^^BANT^Bangkok^L||||||F
OBX|8|CE|LAB515^Is Isolate being sent to CDC?^PHINQUESTION||Y^Yes^ HL70136||||||F
OBX|9|TS|11368-8^ILLNESS/INJURY ONSET DATE/TIME^LN||20070622||||||F
OBX|10|CX|LAB517^Identifier assigned by laboratory to the isolate sent to CDC^PHINQUESTION||A16170^^^VA
STARLIMS_Stage&2.16.840.1.114222.4.3.3.2.2.1&ISO||||||F
OBX|11|TX|PHLIP02^History of culture medium^PHINQUESTION||E1 One Time in Egg||||||F
OBX|12|IS|DEM165^Patient Address County^PHINQUESTION||Prince William||||||F
OBR|2|NE5400123^NE Med System^2.16.840.1.114222.75.9.1.2.1^ISO|F67993405^VA STARLIMS
Stage^2.16.840.1.114222.4.3.3.2.2.1^ISO|PLT77^Influenza Virus Detection and Identification^PLT|||
200706270930|||||||200706271530|SPT&Sputum&HL70070&CSW&Cheek Swab&L|^Welby^Marcus^J^Jr^Dr^MD|||||||||
F
OBX|1|CX|LAB202^Unique Specimen ID^PHINQUESTION||VA12345^^^VA STARLIMS
Stage&2.16.840.1.114222.4.3.3.2.2.1&ISO||||||F
OBX|2|CE|22827-0^FluAV subtype XXX PCR^LN||PLR67^Influenza A H5 asian lineage detected^PLR|||A|||F|||
200707011422| File Type | application/pdf |
| File Title | Att AA_ Influenza Virus Electronic year round PHLIP_HL7 Messaging Data Elements |
| Author | APHL-CDC Messaging Specifications Team |
| File Modified | 2022-11-18 |
| File Created | 2022-11-18 |