The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

OMC - Supporting Clinical Information Segment

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

HL7 Attribute Table - OMC - Supporting Clinical Information Segment
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
OMC
1 00586 Sequence Number - Test/Observation Master File = [0..1] 4 NM
2

00763 Segment Action Code MAY
True:
False:
C(R/X)
[1..1]
[0..1]
[1..1] ID
3

00764 Segment Unique Key MAY
True:
False:
C(R/X)
[1..1]
[0..1]
EI
4 03444 Clinical Information Request SHALL [1..1] CWE
5 03445 Collection Event/Process Step SHALL [1..*] CWE
6 03446 Communication Location SHALL [1..1] CWE
7 03447 Answer Required [0..1] ID
8 03448 Hint/Help Text [0..1] ST
9 03449 Type of Answer [0..1] ID
10 03450 Multiple Answers Allowed [0..1] ID
11 03451 Answer Choices [0..*] CWE
12 03452 Character Limit [0..1] NM
13 03453 Number of Decimals [0..1] NM

OMC-1: Sequence Number - Test/Observation Master File (NM) 00586

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

OMC-2: Segment Action Code (ID) 00763

(Definition from OMC.2 in Ch. 8)

Definition:  This field indicates whether this repetition of the segment is being added, changed or deleted.  When using dynamic update mode (See Chapter 2, Section 2.23.4.2, "Action code/unique identifier mode update definition.")  OMC-2 and OMC-3 Segment Unique Key are used to establish the "unique key" and to determine the data subject to the action. Refer to HL7 Table 0206 – Segment action code for valid values.

If the transaction uses dynamic/action code messaging, the field must be valued. 

Condition Predicate: Required if OMC-3 is valued.

(Definition from LCH.2 in Ch. 8)

Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. The action code adds a validation check to indicate, from the point of view of the sending system, whether this repetition of a segment is being added, changed or deleted. This and the following field are used to implement the "unique key" mode of updating repeating segments. (See Chapter 2, section 2.10.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from LRL.2 in Ch. 8)

Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. The action code adds a validation check to indicate, from the point of view of the sending system, whether this repetition of a segment is being added, changed or deleted. This and the following field are used to implement the "unique key" mode of updating repeating segments. (See Chapter 2, section 2.10.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

(Definition from RGS.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIS.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIG.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIL.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values

This field is conditionally required. It is required for all updating or modifying trigger events.

(Definition from AIP.2 in Ch. 10)

Definition: This field contains the action to be taken when updating or modifying information in this segment from previously sent interface transactions. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

This field is conditionally required. It is required for all updating or modifying trigger events.

OMC-3: Segment Unique Key (EI) 00764

(Definition from OMC.3 in Ch. 8)

Definition: This field contains a unique identifier for one of the multiple repetitions of this segment, to be used in conjunction with the preceding field. Each of the repetitions of the segment will be uniquely identified by this unique key field for the purposes of updates.

Condition Predicate: Required if OMC-2 is valued.

(Definition from LCH.3 in Ch. 8)

Definition: This field contains a unique identifier for one of the multiple repetitions of this segment, to be used in conjunction with the preceding field. Each of the repetitions of the segment will be uniquely identified by this unique key field for the purposes of updates.

(Definition from LRL.3 in Ch. 8)

Definition: This field contains a unique identifier for one of the multiple repetitions of this segment, to be used in conjunction with the preceding field. Each of the repetitions of the segment will be uniquely identified by this unique key field for the purposes of updates.

OMC-4: Clinical Information Request (CWE) 03444

Definition: This field contains a variable that the diagnostic service needs to interpret the results of an ordered study. Where the observations specified here should be sent is specified in the OMC-6 (Communication Location). Refer to Table 0664 - Clinical Information Request in Chapter 2C for valid values.

OMC-5: Collection Event/Process Step (CWE) 03445

Definition: This field indicates by when in the ordering process or workflow this information must be collected. Limit indicates must be done by X point in the workflow. Refer to HL7 Table 0938 – Collection Even/Process Step Limit for valid values.

OMC-6: Communication Location (CWE) 03446

Definition: This field indicates where in the message this information is expected to be communicated, e.g. PID, OBR, and SPM). Refer to HL7 Table 0939 – Communication Loction for valid values.

OMC-7: Answer Required (ID) 03447

Definition: Must the question be answered, or just displayed and can be blank. Refer to HL7 Table 0136 – Yes/no Indicator for valid values.

Y    Answer must be provided

N    Answer not required

OMC-8: Hint/Help Text (ST) 03448

Definition: This field gives guidance to the provider on how to answer the question.

OMC-9: Type of Answer (ID) 03449

Definition: This field contains the allowed datatype for answers, and is drawn from HL7 Table 0125 – Value Type for valid values. Type of answers include: numeric, date, coded, text, etc.

OMC-10: Multiple Answers Allowed (ID) 03450

Definition: This field indicates if multiple answers are allowed, which may impact EHR system display and selection functionality. Refer to HL7 Table 0136 – Yes/no Indicator for valid values.

Y    Multiple Answers Allowed

N    Single Answer only Allowed

OMC-11: Answer Choices (CWE) 03451

Definition: Allowed coded answers to be sent in HL7 file (CWE.1) and/or display Text for Ordering system to present to provider (CWE.2). Refer to Table 0665 - Answer Choices in Chapter 2C for valid values.

The condition is valued only if OMC-9 is valued 'CWE' or 'CNE'.

OMC-12: Character Limit (NM) 03452

Definition: Total number of characters allowed. Required for numeric and (long) text answers.

The field is valued only if OMC-9 is valued 'NM', 'SN', 'ST", 'TX', or 'FT'.

OMC-13: Number of Decimals (NM) 03453

Definition: For numeric answers the number of digits after the decimal.

The field is valued only if OMC-9 is valued 'NM' or 'SN'.