The Technical Steward for the OMC segment is Orders and Observations.
Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
---|---|---|---|---|---|---|---|---|---|
OMC | |||||||||
1 | Sequence Number - Test/Observation Master File | NM | O | [0..1] | 00586 | 4 | # | ||
2 | Segment Action Code | ID | C | 00763 | [1..1] | ||||
3 | Segment Unique Key | EI | C | 00764 | |||||
4 | Clinical Information Request | CWE | R | [1..1] | 03444 | ||||
5 | Collection Event/Process Step | CWE | R | [1..*] | 03445 | ||||
6 | Communication Location | CWE | R | [1..1] | 03446 | ||||
7 | Answer Required | ID | O | [0..1] | 03447 | ||||
8 | Hint/Help Text | ST | O | [0..1] | 03448 | ||||
9 | Type of Answer | ID | O | [0..1] | 03449 | ||||
10 | Multiple Answers Allowed | ID | O | [0..1] | 03450 | ||||
11 | Answer Choices | CWE | O | [0..*] | 03451 | ||||
12 | Character Limit | NM | O | [0..1] | 03452 | ||||
13 | Number of Decimals | NM | O | [0..1] | 03453 |
Definition: This field contains the same value as the sequence number of the associated OM1 segment.
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: 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: 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.
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.
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.
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
Definition: This field gives guidance to the provider on how to answer the question.
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.
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
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'.
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'.
Definition: For numeric answers the number of digits after the decimal.
The field is valued only if OMC-9 is valued 'NM' or 'SN'.