The Technical Steward for the OM1 segment is Orders and Observations.
The OM1 segment contains the attributes that apply to the definition of most observations. This segment also contains the field attributes that specify what additional segments might also be defined for this observation.
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
OM1
|
|||||||||
1
|
Sequence Number - Test/Observation Master File | NM | R | [1..1] | 00586 | 4 | # | ||
|
2
|
Producer's Service/Test/Observation ID | CWE | R | [1..1] | 00587 | ||||
|
3
|
Permitted Data Types | ID | O | [0..*] | 00588 | [2..3] | |||
|
4
|
Specimen Required | ID | R | [1..1] | 00589 | [1..1] | |||
|
5
|
Producer ID | CWE | R | [1..1] | 00590 | ||||
|
6
|
Observation Description | TX | O | [0..1] | 00591 | 200 | # | ||
|
7
|
Other Service/Test/Observation IDs for the Observation | CWE | O | [0..*] | 00592 | ||||
|
8
|
Other Names | ST | B | [0..*] | 00593 | 200 | # | ||
|
9
|
Preferred Report Name for the Observation | ST | O | [0..1] | 00594 | 30 | # | ||
|
10
|
Preferred Short Name or Mnemonic for the Observation | ST | O | [0..1] | 00595 | [1..8] | |||
|
11
|
Preferred Long Name for the Observation | ST | O | [0..1] | 00596 | 200 | # | ||
|
12
|
Orderability | ID | O | [0..1] | 00597 | [1..1] | |||
|
13
|
Identity of Instrument Used to Perform this Study | CWE | O | [0..*] | 00598 | ||||
|
14
|
Coded Representation of Method | CWE | O | [0..*] | 00599 | ||||
|
15
|
Portable Device Indicator | ID | O | [0..1] | 00600 | [1..1] | |||
|
16
|
Observation Producing Department/Section | CWE | B | [0..*] | 00601 | ||||
|
17
|
Telephone Number of Section | XTN | B | [0..1] | 00602 | ||||
|
18
|
Nature of Service/Test/Observation | CWE | R | [1..1] | 00603 | [1..1] | |||
|
19
|
Report Subheader | CWE | O | [0..1] | 00604 | ||||
|
20
|
Report Display Order | ST | O | [0..1] | 00605 | 20 | # | ||
|
21
|
Date/Time Stamp for Any Change in Definition for the Observation | DTM | O | [0..1] | 00606 | ||||
|
22
|
Effective Date/Time of Change | DTM | O | [0..1] | 00607 | ||||
|
23
|
Typical Turn-Around Time | NM | B | [0..1] | 00608 | ||||
|
24
|
Processing Time | NM | O | [0..1] | 00609 | ||||
|
25
|
Processing Priority | ID | O | [0..*] | 00610 | [1..1] | |||
|
26
|
Reporting Priority | ID | O | [0..1] | 00611 | [1..1] | |||
|
27
|
Outside Site(s) Where Observation May Be Performed | CWE | B | [0..*] | 00612 | ||||
|
28
|
Address of Outside Site(s) | XAD | B | [0..*] | 00613 | ||||
|
29
|
Phone Number of Outside Site | XTN | B | [0..1] | 00614 | ||||
|
30
|
Confidentiality Code | CWE | O | [0..1] | 00615 | ||||
|
31
|
Observations Required to Interpret this Observation | CWE | B | [0..*] | 00616 | ||||
|
32
|
Interpretation of Observations | TX | O | [0..1] | 00617 | ||||
|
33
|
Contraindications to Observations | CWE | O | [0..*] | 00618 | ||||
|
34
|
Reflex Tests/Observations | CWE | O | [0..*] | 00619 | ||||
|
35
|
Rules that Trigger Reflex Testing | TX | O | [0..*] | 00620 | ||||
|
36
|
Fixed Canned Message | CWE | O | [0..*] | 00621 | ||||
|
37
|
Patient Preparation | TX | O | [0..*] | 00622 | 200 | # | ||
|
38
|
Procedure Medication | CWE | O | [0..1] | 00623 | ||||
|
39
|
Factors that may Affect the Observation | TX | O | [0..1] | 00624 | 200 | # | ||
|
40
|
Service/Test/Observation Performance Schedule | ST | O | [0..*] | 00625 | 60 | # | ||
|
41
|
Description of Test Methods | TX | O | [0..1] | 00626 | ||||
|
42
|
Kind of Quantity Observed | CWE | O | [0..1] | 00937 | ||||
|
43
|
Point Versus Interval | CWE | O | [0..1] | 00938 | ||||
|
44
|
Challenge Information | TX | O | [0..1] | 00939 | 200 | # | ||
|
45
|
Relationship Modifier | CWE | O | [0..1] | 00940 | ||||
|
46
|
Target Anatomic Site Of Test | CWE | O | [0..1] | 00941 | ||||
|
47
|
Modality of Imaging Measurement | CWE | O | [0..1] | 00942 | ||||
|
48
|
Exclusive Test | ID | O | [0..1] | 03310 | [1..1] | |||
|
49
|
Diagnostic Serv Sect ID | ID | O | [0..1] | 00257 | [2..3] | |||
|
50
|
Taxonomic Classification Code | CWE | O | [0..1] | 01539 | ||||
|
51
|
Other Names | ST | O | [0..*] | 03399 | [200..*] | |||
|
52
|
Replacement Producer's Service/Test/Observation ID | CWE | O | [0..*] | 03433 | ||||
|
53
|
Prior Resuts Instructions | TX | O | [0..*] | 03434 | ||||
|
54
|
Special Instructions | TX | O | [0..1] | 03435 | ||||
|
55
|
Test Category | CWE | O | [0..*] | 03436 | ||||
|
56
|
Observation/Identifier associated with Producer’s Service/Test/Observation ID | CWE | O | [0..1] | 03437 | ||||
|
57
|
Typical Turn-Around Time | CQ | O | [0..1] | 03438 | ||||
|
58
|
Gender Restriction | CWE | O | [0..*] | 03439 | ||||
59
|
Age Restriction | NR | O | [0..*] | 03440 | ||||
Definition: This field contains the first OM1 segment in a message and is described as 1, the second as 2, and so on.
Definition: This field contains the producer's usual or preferred identification of the test or observation. Only three components should be included: <ID code>^<service text name/description>^<source list of code>. All components should be non-null. Refer to Table 0630 - Producer's Service/Test/Observation ID in Chapter 2C for valid values.
Definition: This field contains the allowed data type(s) for this observation. The codes are the same as those listed for OBX (a given observation may, under different circumstances, take on different data types). Indeed, under limited circumstances, an observation can consist of one or more fragments of different data types. When an observation may have more than one data type, e.g., coded (CWE) and numeric (NM) the allowable data types should be separated by repeat delimiters. Refer to HL7 Table 0125 – Value Type in Chapter 2C, Code Tables, for valid values.
Definition: This field contains a flag indicating whether or not at least one specimen is required for the service/test/observation. Refer to HL7 Table 0136 - Yes/no Indicator as defined in Chapter 2C, Code Tables.
Y one or more specimens are required to obtain this observation
N a specimen is not required
When a specimen is required, segment OM4 will usually be included (one per specimen is required).
Definition: This field uniquely identifies the service producing the observation described in this segment. Three components should be included: an identifying code, the name of the producer, and the identity of the coding system (e.g., 323-5678^Acme Special Lab^MC). The identity of the coding system will usually be MC (Medicare provider number or HIBCC site codes) in the United States. Each country may want to specify its preferred coding system and define a coding system ID to identify it. Refer to Table 0631 - Producer ID in Chapter 2C for valid values.
Remember that the magnitude of a treatment or the setting on a machine, such as a ventilator, can be regarded as an observation. Thus, pharmacy, respiratory care, and nursing may be producers of such observations.
Definition: This field contains a text description of this observation.
Definition: This field contains all alias codes/identifiers for this observation. If more than one alias code needs to be specified, multiple three-component, CWE-format entries (<code 1>^<name 1>^<code system 1>) may be given, separated by repeat delimiters. An observation may have as many names/codes as are applicable (e.g., ICD9, ACR-NEMA, SNOMED, and READ). We encourage the inclusion of as many different codes as may apply to assist cross-system mapping of terminology. All components of each triplet should be non-null (that is, names and coding system IDs within the CWE data type are required in addition to codes). Refer to Table 0632 - Other Service/Test/Observation IDs for the Observation in Chapter 2C for valid values.
Because the size (dose) of a treatment can also be an observation, codes that identify treatments (e.g., NDC, ICCS) may also be included in this field.
Note: In this field, the names within the CWE data type are required.
Note: This field is deprecated and retained for backward compatibility as of v 2.8. See OM1-51.
Definition: This field contains any test aliases or synonyms for the name in the context of the ordering service. These are alternative names, not associated with a particular coding system, by which the battery, test, or observation (e.g., measurement, test, diagnostic study, treatment, etc.) is known to users of the system. Multiple names in this list are separated by repeat delimiters.
Definition: This field contains the preferred name for reporting the observation or battery. The name can contain up to 30 characters (including blanks). It is the preferred name for columnar reports that require a maximum name size.
Definition: This field contains the name that can be used in space-limited reports (e.g., specimen labels) to identify the observation for the convenience of human readers. The name can contain up to eight characters.
Definition: This field contains the fully-specified name for the observation or battery. It may include the full (unabbreviated) multiple-word names and contain up to 200 characters. It should be as scientifically precise as possible.
Definition: This field indicates whether or not a service/test/observation is an orderable code. Refer to HL7 Table 0136 - Yes/no Indicator in Chapter 2C, Code Tables, for valid values.
Y the service/test/observation is an orderable code
N the service/test/observation is not orderable
For example, blood differential count is usually an orderable "test," MCV, contained within the differential count, is usually not independently orderable.
Definition: When applicable, this field identifies the instrument or device that is used to generate this observation or battery. Examples are the automated instrument in the laboratory, the imaging device and model number in radiology, and the automatic blood pressure machine on the ward. The instrument is specified as a coded entry in anticipation that these identifiers could be specified as codes. Initially, we expect that most of the information about devices will be transmitted as text in the second component of the CWE identifier. If more than one kind of instrument is used, all of them can be listed, separated by repeat delimiters. Refer to Table 0633 - Identity of Instrument Used to Perform this Study in Chapter 2C for valid values.
Definition: This field contains the method(s) used to produce the observation and should be recorded in a computer-understandable (coded) form here. This field should report the same method(s) reported in narrative in the following field. More than one method may be listed, but only if they produce results that are clinically indistinguishable. Multiple methods must be separated by repeat delimiters. Refer to Table 0635 - Coded Representation of Method in Chapter 2C for valid values.
Definition: This field indicates whether or not a portable device may be used for the service/test/observation. Refer to HL7 Table 0136 - Yes/no Indicator in Chapter 2C, Code Tables, for valid values.
Y the observation can be obtained with a portable device brought to the patient
N the patient or specimen must be transported to the device
Note: This field is deprecated and retained for backward compatibility as of v 2.8.
Definition: This field permits the sorting of observation orders and values by the providing service's department/section. It provides "source oriented" reporting when required. Free text may be used instead of these codes, but in that case, they should be recorded as the second "component" of the field to distinguish them from the standard codes. Multiple codes in this field are separated by repeat delimiters. Refer to Table 0636 - Observation Producing Department/Section in Chapter 2C for valid values.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.
Definition: This field contains the telephone number for calling responsible parties in this section to ask results or advice about the use of this test.
Definition: This field indicates whether the definition entry identifies a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations. Refer to User-defined Table 0174 - Nature of Service/Test/Observation in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains an optional string that defines the preferred header under which this observation should be listed on a standard display. For example, if the test is hemoglobin, this string might be "Complete blood count." It is represented as a coded data type so that a battery can be a header. Only the description part of the string may be included in case the subheader does not have an associated code. When a series of observations is displayed according to the sort order given below, the subheader that groups those observations is presented whenever the subheader changes. Refer to Table 0637 - Report Subheader in Chapter 2C for valid values.
Definition: This field contains an optional string that defines the sort order in which this observation is presented in a standard report or display that contains the many observations.
Definition: This field contains the date and time that the last of any field change was made and in the host's record corresponding to the OM1 segment.
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.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.2. See OM1-57.
Definition: This field contains the typical processing time for single test/observation. This field indicates the time from the delivery of a specimen or transport of a patient to a diagnostic service and the completion of the study. It includes the usual waiting time. The units are measured in minutes.
Definition: This field contains the usual length of time (in minutes) between the start of a test process and its completion.
Definition: This field contains one or more available priorities for performing the observation or test. This is the priority that can be placed in TQ1-9 - Priority. Multiple priorities may be given, separated by repeat delimiters. For example, S~A~R~P~T indicates that the test may be ordered using codes S, A, R, P, or T. Refer to HL7 Table 0168 - Processing Priority in Chapter 2C, Code Tables, for valid values.
For tests requiring a specimen, the priority for obtaining the specimen is included in OM4-13 - Specimen Priorities.
Definition: This field contains the available priorities reporting the test results when the user is asked to specify the reporting priority independent of the processing priority. Refer to HL7 Table 0169 - Reporting Priority in Chapter 2C, Code Tables, for valid values.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.
Definition: This field contains the identification(s) of the outside service(s) that produce(s) the observation. The format of this CWE field uses the producer ID (as defined in OM1-5 - Producer ID) and the name of the service separated by component delimiters. An example is ...|39221^ACME lab^MC|... If multiple services are used, they should be separated by repeat delimiter(s). Refer to Table 0638 - Outside Site(s) Where Observation May Be Performed in Chapter 2C for valid values.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.
Definition: This field contains the address of the outside services listed in OM1-28 - Address of Outside Site(s) where observation may be performed. If multiple services are recorded in that field, their addresses should be separated by repeat delimiters, and the addresses should appear in the same order in which the services appear in the preceding field.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.
Definition: This field contains the telephone number of the outside site.
Definition: This field contains the degree to which special confidentiality protection should be applied to the observation. For example, a tighter control may be applied to an HIV test than to a CBC. Refer to User-defined Table 0177 - Confidentiality Code in Chapter 2C, Code Tables, for suggested values.
Note: This field is deprecated and retained for backward compatibility as of v 2.8.2. See OMC Segment.
Definition: This field contains the list of variables that the diagnostic service needs to interpret the results of an ordered study. The observations specified here should be sent to the diagnostic service as OBX segments along with the order (OBR) segment. Separate multiple items by repeat delimiters. Refer to Table 0639 - Observations Required to Interpret this Observation in Chapter 2C for valid values.
Definition: This field contains the clinical information about interpreting test results. Examples are the conditions (drugs) that may cause false abnormals, and the information about the sensitivity and specificity of the test for diagnoses.
Definition: This field contains the diagnosis or problem for which the test is a contraindication or of possible danger (e.g., pacemaker, pregnancy, diabetes). For example, if the test identified in OM1 was an intravenous pyelogram, this field would include warnings about the use of contrast media in diabetes. The contraindication diagnoses should be separated by repeat delimiters. Refer to Table 0640 - Contraindications to Observations in Chapter 2C for valid values.
Most contraindication rules will be transmitted as free text. In such cases, the contents serve only as information for human reading. However, an alternative for machine readable contraindication rules also exists. The rule may be defined formally in the Arden Syntax (ASTM 1460-1992) which has syntax for defining algebraic and transcendental equations, as well as temporal and logical selection criteria based on patient information stored in the computer record. Reflex rules that are written in Arden Syntax should begin and end with a double semi-colon (;;), the Arden slot delimiter.
Definition: This field contains the test names as type CWE (i.e., <code>^<text name>^<coding system>) that may be ordered automatically by the diagnostic service, depending on the results obtained from the ordered battery. A screening CBC might trigger a reticulocyte count if the Hgb is less than 12. Multiple reflex tests are separated by repeat delimiters. Refer to Table 0641 - Reflex Tests/Observations in Chapter 2C for valid values.
Definition: This field contains the rules that trigger the reflex tests listed above. If multiple reflex tests are listed in OM1-34 - Reflex Text/Observations separated by repeat delimiters, a set of corresponding rules will be included in this section. The first rule will apply to the first test, the second to the second test, and so on.
Most reflex rules will usually be transmitted as free text. In such cases, the contents serve only as information for human reading. However, an alternative for machine readable rules also exists. The rule may be defined formally in the Arden Syntax (ASTM 1460-1992) which has syntax for defining algebraic and transcendental equations, as well as temporal and logical selection criteria based on patient information stored in the computer record. Reflex rules that are written in Arden Syntax should begin and end with a double semi-colon (;;), the Arden slot delimiter.
Definition: This field contains the codes and a fixed text message that is always associated with an abbreviation. The field may include multiple messages separated by repeat delimiters. Refer to Table 0643 - Fixed Canned Message in Chapter 2C for valid values.
Most rules about patient testing will be transmitted as free text. In such cases, the contents serve only as information for human reading. However, an alternative for machine readable rules also exists. The rule may be defined formally in the Arden Syntax (ASTM 1460-1992) which has syntax for defining algebraic and transcendental equations, as well as temporal and logical selection criteria based on patient information stored in the computer record. Rules about patient preparation are written in Arden Syntax should begin and end with a double semi-colon (;;), the Arden slot delimiter.
Definition: This field contains the tests or observations that require special patient preparation, diet, or medications. For GI contrast studies, this field would contain the pretest diet, e.g., low residue for two days, NPO before study, and the preferred purgatives. Each separate med, diet, or preparation should be delimited by a repeat delimiter. Separate each requirement by a repeat delimiter. Example for a sigmoidectomy:
...|clear liquid diet full day before procedure~take 8 oz mag citrate 6pm day before procedure~take 2 ducat tabs (5m) at 4pm day before procedure~NPO past midnight.|...
Definition: This field contains the treatments that may be needed as part of the procedure. Examples are radioactive iodine for a thyroid screen, and methacholine for a methacholine spirometry challenge. This field should be identified as a CWE data type. Refer to Table 0644 - Procedure Medication in Chapter 2C for valid values.
Definition: This field contains the text description of the foods, diagnoses, drugs, or other conditions that may influence the interpretation of the observation. Information about the direction of the effect, and any recommendation about altering the diet, conditions, or drug before initiating the test observation.
Most rules about factors that effect the test interpretation will be transmitted as free text. In such cases, the contents serve only as information for human reading. However, an alternative for machine readable rules also exists. The rule may be defined formally in the Arden Syntax (ASTM 1460-1992) which has syntax for defining algebraic and transcendental equations, as well as temporal and logical selection criteria based on patient information stored in the computer record. Rules about patient preparation are written in Arden Syntax and should begin and end with a double semi-colon (;;), the Arden slot delimiter.
Definition: This field contains the diagnostic studies/tests that are performed only at certain times during the course of a work day or work week. This field indicates the maximum interval between successive test performances (the test may actually be performed more frequently). The format given in Chapter 4, Section 4.3.2.1, "Repeat Pattern," should be used. If necessary, multiple codes may be given, separated by repeat delimiters. The use of multiple codes indicates that the test is performed at multiple concurrent intervals. For example, Q6H indicates that the test is performed at least once every 6 hours around the clock. QJ1 indicates that the test is performed at least every week on Mondays. QAM~QPM indicates that the test is performed at least once every morning and every evening. QJ1~QJ3~QJ5 indicates that the test is performed at least every week on Mondays, Wednesdays, and Fridays. C indicates that the test is performed continuously, 7 days per week.
Definition: This field contains the text description of the methods used to perform the text and generate the observations. Bibliographic citations may be included.
Definitions: This optional attribute describes the underlying kind of property represented by this observation. This attribute distinguishes concentrations from total amounts, molar concentrations from mass concentrations, partial pressures from colors, and so forth. These are discussed more fully in the LOINC Users' Manual.1 They are derived from the approach described in 1995 edition of the IUPAC Silver Book.2 These distinctions are used in IUPAC and LOINC standard codes. Defined categories are listed in HL7 Table 0254 - Kind of Quantity in Chapter 2C, Code Tables.
The distinctions of true quantities in this table are based primarily on dimensional analyses. The table contains a number of "families," those related to simple counts (number, number concentration, etc.), to mass (mass, mass concentration, etc.), to enzyme activity (catalytic content, catalytic concentration, etc.), and molar or equivalents (substance content, substance concentration).
By this classification, a glucose (in the US) would be classed as a mass concentration. A sodium would be classed as a substance concentration. Within the family, a total amount should be described as the unadorned variant; e.g., the property of measure for a patient's weight would be mass, not mass content. Most chemical measures produce concentrations, as exemplified by sodium and glucose. However, a 24-hour urine protein is not a mass concentration, but a mass rate (mass per unit time). The content variants (e.g., mass content, substance content) are used to reflect an amount per mass (usually) of tissue.
This attribute would be valued in a master file only if the service sending the master file classified observations by their principle of measurement.
Definition: This optional attribute allows master files to classify observations as measuring the patient's state at a point in time (e.g., spot urines, random urines, serum potassium), or averaged over an interval of time (e.g., concentration, total amount, or clearance over a 24-hour collection). Interval measures most often apply to urine and stool specimens (e.g., 24-hour urines, 3-day stool fats). They also apply to clinical measurements such as urine outputs, which are reported as shift totals and 24-hour totals, and event counts on physiologic monitors such as the number of PVCs on a 24-hour Holter monitor.
This field would only be valued in a transaction if the service sending this master file message classified its observation by point versus time interval. This field is not used to record the time collection interval for a particular sample. It is used to specify a characteristic of an observation which has a defined normal range and to distinguish observations of the same kind but observed over varying periods of time. A spot urine sodium would have PT stored in this field. A 24-hour urine sodium and a 24-hour Holter monitor would have 24H stored here. This attribute would only be valued if the filling service classified its observations by timing. Refer to User-defined Table 0255 - Duration Categories in Chapter 2C, Code Tables, for suggested values.
Definition: This optional attribute provides information for classifying observations by the challenge component of the test, if a challenge does speciate the observation. For example, distinguishing tests that have a challenge component in database. There co-ascribes the physiologic or drug challenge that is intrinsic to the measurement. To identify, for example, tests that include a glucose challenge.
To construct this text string, use the following template. (Note: This field is not constructed of formally defined components; it is a free text field. Component delimiters are not used and it is not necessary to supply placeholders if some "components" are not used.)
The time delay follows the syntax: n<S|M|H|D|W> where n is a number (possibly a decimal); S denotes seconds; M denotes minutes; H denotes hours; D denotes days; and W denotes weeks. The time delay can be preceded by a 'greater than' (>) sign, e.g. >4H.
HL7 Table 0256 - Time Delay Post Challenge in Chapter 2C, Code Tables, lists possible values for time delay.
Examples:
PRE 100 GM GLUCOSE PO
PRE 100 GM GLUCOSE PO
30M POST 100 GM GLUCOSE PO
2H POST 100 GM GLUCOSE PO
TROUGH
For drug peak and trough measures the nature of the substance challenged is the same as the analyte name, and need not be included.
We denote the route of the challenge via abbreviations for medication routes (see Chapter 4A, section 4A.4.2.1, "Route," which references HL7 Table 0162 - Route of Administration in Chapter 2C, Code Tables). An oral route of administration would be denoted by "PO," an intravenous route by "IV."
Details of the drug dose, time the dose was given, route of administration, etc., would be noted in separate OBX, and would have corresponding master observation definitions stored in the observation master file map to different records stored in the master file segments contained in the drug level message.
The nature of a physiologic (non-drug) challenge may also be specified, using the terms in HL7 Table 0257 - Nature of challenge in Chapter 2C, Code Tables.
Definition: This optional attribute provides a mechanism for classifying observations according to the subject, in relation to the patient whose results might be stored with as "patient" data. It is standard practice, for example, to report values for controls, donors, and blood product units as well as the patient's own values, and store them in the patient's record. (This may not be the best way to model such information, but it is the way it is usually reported.) This should be valued when two values (e.g., one for patient and one for a blood product unit) could otherwise be confused.
The default value is "Patient," and if not specified, this value is assumed. The persons sub-component can refer to HL7 Table 0258 - Relationship Modifier in Chapter 2C, Code Tables, for valid values.
Definition: This optional attribute formally indicates the site of the observation (to make it easy for a system to find all tests related to one anatomic site). It can be used to classify the observation by target site of the examination. For example, "heart" might be recorded as the target of the electrocardiogram, cardiac echo, and thallium exercise test. This attribute would be applicable to most imaging and electro-physiologic examinations. The SNOMED topology axis is an example of a coding system for anatomic sites. User-defined tables may also apply here. Refer to Table 0645 - Target Anatomic Site Of Test in Chapter 2C for valid values.
Definition: This optional attribute describes the modality used to acquire the observation data, e.g., radiograph, ultrasound, CT scan, MR, etc. This attribute is especially important for imaging studies. Refer to External Table 0910 – Acquisition Modality in Chapter 2C, Code Tables, for the defined value set, which may be repalce or extended with local codes. If the DICOM codes are used, the coding system ID is DCM.
Note: The use of User-defined Table 0259 - Modality for this field is deprecated and retained for backward compatibility as of v 2.7.
Definition: This field defines if this test should be a specific event with no other tests to be performed with this test. Refer to HL7 Table 0919 – Exclusive Test in Chapter 2C, Code Tables, for valid values.
If not populated, the default value of "N" is assumed and that this test can be included with any number of other tests.
When D is specified for this field, using field OM1-49 determines how tests must be grouped together. Tests within the same Diagnostic Service Sector may be on the same requisition, and therefore in the same message.
Definition: This field is the section of the diagnostic service where the observation was performed. If the study was performed by an outside service, the identification of that service should be recorded here. Refer to HL7 Table 0074 – Diagnostic Service Section ID in Chapter 2C, Code Tables, for valid entries. Same as OBR-24.
Definition: The species of living organism. This may include the common or scientific name, based on the coding system(s) used. SNOMED is the recommended coding system. If this field is not valued, a human is assumed. Refer to User-defined Table 0446 - Species Code in Chapter 2C, Code Tables, for suggested values.
For example:
...|L-80700^Canine, NOS^SNM3|...
...|L-80100^Bovine^SNM3|...
...|L-80A00^Feline^SNM3|....
This field is a list of species or other taxonomic classification(s) to which the indicated specimen type may appropriately be applied for the indicated observation or test. If this field is omitted the default meaning is that the test or observation is applicable to humans. In a veterinary context if the test is applicable to any species, an appropriate code such as "Kingdom Animalia (organism)" should be used to avoid confusion with the meaning of human only.
Definition: This field contains any test aliases or synonyms for the name in the context of the ordering service. These are alternative names, not associated with a particular coding system, by which the battery, test, or observation (e.g., measurement, test, diagnostic study, treatment, etc.) is known to users of the system. Multiple names in this list are separated by repeat delimiters.
Definition: This field is used in conjunction with a MFE-1 Record-Level Event Code 'MDC' defined as: "Deactivate: discontinue using record in master file, but do not delete from database", in conjunction with an OM1 segment providing detail for the deactivate code. When the OM1-2 Producer's Service/Test/Observation ID is being deactivated, use OM1-52 to indicate the producer's replacement test or observation code(s), as it was defined in the OM1-2 Producer's Service/Test/Observation ID when the new/replacement code was added. Refer to Table 0646 - Replacement Producer's Service/Test/Observation ID in Chapter 2C for valid values.
Note: Replacement codes referenced by OM1-52 must be added to the receiver's system before sending a deactivate record for the code being obsoleted. The Sequence is illustrated below:
Sequence 1 – Activate new code
OM1-2 Adding a new code X; Example: X^New Code X^L
OM1-52 Empty
Sequence 2 – Deactive obsolete code and indicate it's new replacement code
OM1-2 obsolete code: Examle: Y^Deactivated code^L
OM1-52 X^New Code X^L
Table below for information in change request proposal process and not intended for inclusion in the base standard:
File-Level Event MFI-3 | Record-Level Event MFE-1 | Comment |
REP | MAD – Add record to master file | Note: If the MFI-3 - File-Level Event Code is "REP" (replace file), then each MFE segment must have an MFE-1 - Record-Level Event Code of "MAD" (add record to master file). |
UPD | MAD – Add record to master file | (MFI-3) UPD means that the events are defined according to the record-level event code contained in each MFE segment in that message. |
UPD | MDC – Deactivate: discontinue using record in master file, but do not delete from database | (MFI-3) UPD means that the events are defined according to the record-level event code contained in each MFE segment in that message. |
UPD | MAC – Reactivate deactivated record | (MFI-3) UPD means that the events are defined according to the record-level event code contained in each MFE segment in that message. |
Definition: This field is used to indicate when the test in OM1-2 Producer's Service/Test/Observation ID is ordered, prior results should accompany the order (OML^O21^OML_O21: Laboratory Order Message). For example, when ordering a Thyroid FNA (Fine Needle Aspiration) Evaluation, send the prior results of Ultrasound Findings. The instructions may also indicate a timeframe; for example, send the prior results of CBC in past 60 days.
Definition: This field is used to convey special instructions for the test, for example: "Chain-of-custody documentation is required for samples submitted for pre-employment, random employee testing, and forensic purposes. For other applications, use the standard request form." (Note: this is for toxicology testing); "If reflex test is performed, additional charges/CPT code(s) may apply."; "Please direct any questions regarding this test to Oncology Customer Service"; "Please include tentative diagnosis/treatment on the request form. This is necessary for proper culturing and result interpretation." (Note: this is for chromosome analysis.)
Definition: This field may be used to organize tests for display or other user defined purpose. For example, tests might be categorized by disease state, such as molecular tests for solid tumors; example categories are: breast, colorectal, lung, and melanoma.
Definition: This field contains the code for resulted tests, which are associated with the Producer’s Service/Test/Observation ID code in OM1-2 and will appear in OBX-3 Observation Identifier in a result message. Refer to Table 0647 - Observation/Identifier associated with Producer’s Service/Test/Observation ID in Chapter 2C for valid values.
Definition: This field contains the typical processing time for single test/observation. This field indicates the time from delivery of a specimen or transport of a patient to a diagnostic service and the completion of the study. It includes the usual waiting time.
Definition: This field is used to convey gender restrictions for ordering the test specified in OM1-2 Producer's Service/Test/Observation ID. If there are no restrictions the field is left empty. If the test is restricted to order for certain gender(s), the restricted genders are listed. For example, a Prostate Specific AG (PSA) test is typically ordered only for male patients, thus for PSA the field would be valued 'M' for Male. Refer to User-defined Table 0001 – Administrative Sex in Chapter 2C, Code Tables, for suggested values.
Definition: This field is used to convey age restrictions for ordering the test specified in OM1-2 Producer's Service/Test/Observation ID. If there are no restrictions the field is left empty. If the test is restricted to order for certain age(s), the age range restriction(s) are listed in years. For example, newborn tests are typically restricted to age 1 year or below, thus for newborn tests the field would be valued 0^1.
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
