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

Draft Website - For Review Purposes Only

OM7 - Additional Basic Attributes Segment (Fields That Apply To Most Observations/Services)

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

The OM7 segment contains additional basic attributes that apply to the definition of most observations/services.

HL7 Attribute Table - OM7 - Additional Basic Attributes Segment (Fields That Apply to Most Observations/Services)
Seq# DataElement Description Must Implement Flags Cardinality Length C.LEN Vocabulary DataType
OM7
1 00586 Sequence Number - Test/Observation Master File SHALL = [1..1] 4 NM
2 00238 Universal Service Identifier SHALL [1..1] CWE
3 01481 Category Identifier [0..*] CWE
4 01482 Category Description = [0..1] 200 TX
5 01483 Category Synonym # [0..*] 200 ST
6 01484 Effective Test/Service Start Date/Time [0..1] DTM
7 01485 Effective Test/Service End Date/Time [0..1] DTM
8 01486 Test/Service Default Duration Quantity # [0..1] 5 NM
9 01487 Test/Service Default Duration Units [0..1] CWE
10 01488 Test/Service Default Frequency = [0..1] 60 CWE
11 01489 Consent Indicator [0..1] [1..1] ID
12 01490 Consent Identifier [0..1] CWE
13 01491 Consent Effective Start Date/Time [0..1] DTM
14 01492 Consent Effective End Date/Time [0..1] DTM
15 01493 Consent Interval Quantity # [0..1] 5 NM
16

01494 Consent Interval Units MAY
True:
False:
C
[1..1]
[0..1]
CWE
17 01495 Consent Waiting Period Quantity # [0..1] 5 NM
18

01496 Consent Waiting Period Units MAY
True:
False:
C
[1..1]
[0..1]
CWE
19 00607 Effective Date/Time of Change [0..1] DTM
20 00224 Entered By B [0..1] XCN
21 01497 Orderable-at Location B [0..*] PL
22 01498 Formulary Status = [0..1] 1 CWE
23 01499 Special Order Indicator [0..1] [1..1] ID
24 01306 Primary Key Value - CDM [0..*] CWE

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

OM7-2: Universal Service Identifier (CWE) 00238

(Definition from OBR.4 in Ch. 4)

Definition: This field contains the identifier code for the requested observation/test/battery. The identifier can come from either a local coding system or industry standards. Examples may be LOINC (emerging as the global standard for observation identifiers), JLAC10, or SNOMED CT. Refer to Table 0612 - Universal Service Identifier in Chapter 2C for valid values.

(Definition from OBR.4 in Ch. 7)

Definition: This field contains the identifier code for the requested observation/test/battery. The identifier can come from either a local coding system or industry standards. Examples may be LOINC (emerging as the global standard for observation identifiers), JLAC10, or SNOMED CT. Refer to Table 0612 - Universal Service Identifier in Chapter 2C for valid values.

(Definition from OM7.2 in Ch. 8)

Definition: This field contains the producer's usual or preferred identification of the test or service.

(Definition from AIS.3 in Ch. 10)

Definition: This field contains an identifier code for a service to be scheduled. This field may contain a universal service identifier describing the observation/test/battery/procedure or other activity that is to be performed during the requested appointment, similar to the universal service identifier defined for the OBR segment in the Order Entry chapter (Chapter 4). This code can be based on local and/or universal codes. The use of universal codes is recommended.

(Definition from TCC.1 in Ch. 13)

Definition: This field identifies the test code that information is being transmitted about. The alternate elements represent the test code identifier that has been assigned by the manufacturer to this particular test code. Refer to Table 0787 - Universal Service Identifier in Chapter 2C for valid values.

(Definition from TCD.1 in Ch. 13)

Definition: This field identifies the test code that information is being transmitted about. Refer to Table 0789 - Universal Service Identifier in Chapter 2C for valid values.

OM7-3: Category Identifier (CWE) 01481

Definition: This field contains the category name (term given to a group of service items for the purpose of classification). Examples: Laboratory, Pharmacy, Diagnostic Imaging, etc. Refer to User-defined Table 0412 - Category Identifier in Chapter 2C, Code Tables, for suggested values.

OM7-4: Category Description (TX) 01482

Definition: This field contains a text description for the category of the test/service item.

Example: The category "Pathology" may be described as a specialty practice concerned with all aspects of disease, with special reference to the essential natural cause and development of abnormal conditions, as well as the structural and functional changes that result from the disease process.

OM7-5: Category Synonym (ST) 01483

Definition: This field contains an alternate name(s) for the category of the test/service. Example: The category "Radiology" is a synonym name for the category "Diagnostic Imaging".

OM7-6: Effective Test/Service Start Date/Time (DTM) 01484

Definition: This field contains the date and time that the service item is available to be ordered, performed, etc.

OM7-7: Effective Test/Service End Date/Time (DTM) 01485

Definition: This field contains the date and time that the service item is no longer authorized to be ordered, performed, etc.

OM7-8: Test/Service Default Duration Quantity (NM) 01486

Definition: This field indicates the default duration quantity for the service.

OM7-9: Test/Service Default Duration Units (CWE) 01487

Definition: This field indicates the default duration units for the service. Refer to Table 0663 - Test/Service Default Duration Units in Chapter 2C for valid values.

OM7-10: Test/Service Default Frequency (CWE) 01488

Definition: This field indicates the default frequency (how often) the service would be ordered for or performed on.

OM7-11: Consent Indicator (ID) 01489

Definition: This field indicates if a consent is needed for the service item. Refer to HL7 Table 0136 - Yes/no Indicator in Chapter 2C, Code Tables.

OM7-12: Consent Identifier (CWE) 01490

Definition: This field contains the identifier for the consent specified for the service item. Refer to User-defined Table 0413 - Consent Identifier in Chapter 2C, Code Tables, for suggested values.

OM7-13: Consent Effective Start Date/Time (DTM) 01491

Definition: This field contains the date and time the consent is valid for the service item.

OM7-14: Consent Effective End Date/Time (DTM) 01492

Definition: This field contains the date and time the consent is no longer valid for the test/service.

OM7-15: Consent Interval Quantity (NM) 01493

Definition: This field specifies the period of time for which a consent is valid for a specific service item.

OM7-16: Consent Interval Units (CWE) 01494

Definition: This field specifies the unit of time for OM7-15 - Consent Interval Quantity. Refer to User-defined Table 0414 - Units of Time in Chapter 2C, Code Tables, for suggested values.

Note: If Consent Interval Quantity is specified, then Consent Interval Unit is required.


OM7-17: Consent Waiting Period Quantity (NM) 01495

Definition: This field contains the time period between the time the consent is signed and the procedure can be performed.

OM7-18: Consent Waiting Period Units (CWE) 01496

Definition: This field specifies the unit of time for OM7-17 - Consent Waiting Period Quantity. Refer to User-defined Table 0414 - Units of time in Chapter 2C, Code Tables, for suggested values.

Note: If Consent Waiting Period Quantity is specified, then Consent Waiting Period Unit is required.


OM7-19: Effective Date/Time of Change (DTM) 00607

(Definition from OM1.22 in Ch. 8)

Definition: This field contains the date and time of the last change in the test procedure that would make previous results incompatible with new results, e.g., the last time that normal reference range or units changed for a numeric test/observation.

We strongly suggest that observation producers never use the same observation ID when the measurement procedures change in such a way that results produced under the new procedure are clinically different from those produced with the old procedure. Rather, the producer should try to adjust the new procedure so that its values are clinically indistinguishable from the old. Failing that, one should create a new observation ID for the observation produced under the new procedure.

In the rare circumstances when a procedure change occurs and neither of the above two options is viable, this field shall be used to transmit the effective date/time of the new procedure. The receiving system shall assume that any values that come across under this observation ID are under the new procedure after this date and take appropriate steps to distinguish the old from the new observations.

This number is included to provide a means of communicating with the observation producing service when they have questions about particular observations or results.

(Definition from OM7.19 in Ch. 8)

Definition: This field contains the date and time of the last change in the test procedure that would make previous results incompatible with new results.

OM7-20: Entered By (XCN) 00224

(Definition from NTE.5 in Ch. 2)

Definition: This field contains the identity of the person who actually keyed the comment into the application. It provides an audit trail in case the comment is entered incorrectly and the ancillary department needs to clarify the comment. By local agreement, either the ID number or name component MAY be omitted.

(Definition from ORC.10 in Ch. 4)

Definition: This field was retained for backward compatibility only as of v 2.7 and the detail was withdrawn and removed from the standard as of v 2.9. The reader is referred to the PRT segment described in Chapter 7.

(Definition from ACC.7 in Ch. 6)

Definition: This field identifies the person entering the accident information.

(Definition from MFE.7 in Ch. 8)

Definition: This field contains the identity of the person who actually keyed the master file entry into the application. It provides an audit trail in case the request is entered incorrectly and the ancillary department needs to clarify the request.

(Definition from OM7.20 in Ch. 8)

Note: This field is deprecated and retained for backward compatibility as of v 2.8.

Definition: This field contains the identity of the person who actually keyed the service item into the application. It provides an audit trail in case the request is entered incorrectly and the ancillary department needs to clarify the request.

OM7-21: Orderable-at Location (PL) 01497

Note: This field is deprecated and retained for backward compatibility as of v 2.8.

Definition: This field contains the location(s) where the test/service can be ordered.

OM7-22: Formulary Status (CWE) 01498

Definition: This field indicates whether or not the service (pharmaceutical) is in the formulary. Refer to User-defined Table 0473 - Formulary Status in Chapter 2C, Code Tables, for valid values.

OM7-23: Special Order Indicator (ID) 01499

Definition: This field indicates whether or not the service (pharmaceutical) is a special order. Refer to HL7 Table 0136 - Yes/no Indicator in Chapter 2C, Code Tables, for valid values.

Y    This is a special order.

N    This is not a special order

OM7-24: Primary Key Value - CDM (CWE) 01306

(Definition from OM7.24 in Ch. 8)

Definition: Allows the ability to associate a Service/Test/Observation item with a CIM (charge item master). This field contains the corresponding value of CDM-1 for the CIM being linked to. It is possible to allow multiple charge items to a single Service/Test/Observation item.

(Definition from CDM.1 in Ch. 8)

Definition: The key field of the entry. Must match MFE-4 - Primary Key Value - MFE. This field contains the code assigned by the institution for the purpose of uniquely identifying the thing that can be charged. For example, this field would be used to uniquely identify a procedure, item, or test for charging purposes. Probably the same set of values as used in FT1-7- Transaction Code in financial messages (refer to User-defined Table 0132 - Transaction Code in Chapter 2C, Code Tables, for suggested values). See Chapter 7 for discussion of the universal service ID.