Draft Website - For Review Purposes Only

The Technical Steward for the OM5 segment is Orders and Observations.

This segment contains the information about batteries and supersets (a nature code of F, P or S, as described in OM1-18 - Nature of Service/Test/Observation).

HL7 Attribute Table - OM5 - Observation Batteries (Sets) Segment

Seq#	DataElement	Description	Must Implement	Flags	Cardinality	Length	C.LEN	Vocabulary	DataType
OM5
1	00586	Sequence Number - Test/Observation Master File		=	[0..1]		4		NM
2	00655	Test/Observations Included Within an Ordered Test Battery			[0..*]			0662	CWE
3	00656	Observation ID Suffixes			[0..1]				ST

(Definition from OM1.1 in Ch. 8)

Definition: This field contains the first OM1 segment in a message and is described as 1, the second as 2, and so on.

(Definition from OM2.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment. Refer to Table 0648 - Units of Measure in Chapter 2C for valid values.

(Definition from OM3.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment.

(Definition from OM4.1 in Ch. 8)

Definition: The OM4-1 contains a numeric value that indicates a unique set of OM1, OM2, OM3, and OM4 components; each OMn-1 in a set will have the same value as illustrated in the example below. Because the OM4 segment can repeat, but needs to have a unique number for use with OM4-17, the sequence number must be appended with a sequence number as shown in the second example below.

OM4-1 Sequence Number – Test/Observation Master File Example:

MSH|...<cr>

// start MFE Test Begin group

MFE|A|...<cr>

OM1|1|...<cr>

OM2|1|...<cr>

OM3|1|...<cr>

OM4|1|...<cr>

// end MFE Test Begin group

// start MFE_Test_Begin group

MFE|A|...<cr>

OM1|2|...<cr>

OM2|2|...<cr>

OM3|2|...<cr>

OM4|2.1|...<cr>

OM4|2.2|...<cr>

//end MFE_Test_Begin group

(Definition from OM5.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment.

(Definition from OM6.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment.

(Definition from OM7.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment.

(Definition from OMC.1 in Ch. 8)

Definition: This field contains the same value as the sequence number of the associated OM1 segment.

Definition: This field contains the codes and names of all tests/observations included within a single battery (nature code P, as described in OM1-18 - Nature of Service/Test/Observation), a single functional procedure (nature code F), or a given superset (nature code S). When a segment includes a list of component elements, the sending system should be sure that the segments defining all of the components are sent before the segment that references them. An entry in this list can itself be a battery. Refer to Table 0662 - Test/Observations Included Within an Ordered Test Battery in Chapter 2C for valid values.

The individual service/test/observation code should be recorded as type CWE, i.e., in the standard format for coded observation identifiers. Multiple observations should be separated by repeat delimiters. In the US, it is recommended that, within a single occurrence of OM5-2 Tests/Observations included within an Orders Test Battery, these child observations be identified with LOINC codes as well as by the producer’s local identifier. Examples of code systems used may be LOINC (emerging as the global standard for observation identifiers), JLAC10, or SNOMED CT.

If the definition segment defined serum electrolytes, this field might look like the following:

2951-2^SODIUM^LN~

2823-3^POTASSIUM^LN~

2075-0^CHLORIDE^LN~

2028-9^CARBON DIOXIDE^LN

For S (superset) parameters, this field contains the batteries that are included within the "super" battery. For example, ROUTINES might be defined as:

402^Electrolytes~352^Urinalysis~432^CBC~520^SMA12

Definition: This field contains the tests or procedures that produce a type which uses observation ID suffixes following the service/test/observation ID code. This field lists the possible options. For example, a chest X-ray may use the suffixes IMP, REC, DEV, or others. Each of the expected suffixes should be listed here.