Terug naar index  <<  Terug naar templates

ref Template  OBX - Observation/Result

Id 2.16.840.1.113883.3.1937.777.10.13.82
ref
(van repository: ad4bbr-)
Geldigheid geldig vanaf 2013‑02‑10
Status active Actief Versielabel
Naam OBX_segment Weergavenaam OBX - Observation/Result
Classificatie HL7v2 segment level template
Open/gesloten Open (ook andere dan gedefinieerde elementen zijn toegestaan)
Gebruikt door / Gebruikt
Gebruikt door 0 transacties en 0 templates, Gebruikt 10 templates
Gebruikt als Naam Versie
2.16.840.1.113883.3.1937.777.10.15.88 Containment active SI - Sequence ID DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.83 Containment active ID - Coded value for HL7 defined tables DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.5 Containment active CE - Coded element DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.89 Containment active ST - String DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.67 Containment active varies DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.84 Containment active IS - Coded value for user-defined tables DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.86 Containment active NM - Numeric DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.64 Containment active TS - Time stamp DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.74 Containment active XCN - Extended composite ID number and name for persons DYNAMISCH
2.16.840.1.113883.3.1937.777.10.15.21 Containment active EI - Entity identifier DYNAMISCH
Item DT Card Conf Omschrijving Label
hl7v2:OBX.1
SI 0 … 1
en-US This field contains the sequence number. For compatibility with ASTM.

Bevat 2.16.840.1.113883.3.1937.777.10.15.88 SI - Sequence ID (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 569
@Type
0 … 1 F SI
@LongName
0 … 1 F Set ID - OBX
hl7v2:OBX.2
ID 0 … 1
en-US

This field contains the format of the observation value in OBX. It must be valued if OBX-11-Observ result status is not valued with an "X". If the value is CE then the result must be a coded entry. When the value type is TX or FT then the results are bulk text. The valid values for the value type of an observation are listed in HL7 Table 0125 - Value Type.

The observation value must be represented according to the format for the data type defined in Chapter 2, Section 2.9, “Data Types.” For example, a PN consists of 6 components, separated by component delimiters.

Although NM is a valid type, observations which are usually reported as numbers will sometimes have the string (ST) data type because non-numeric characters are often reported as part of the result, e.g., >300 to indicate the result was off-scale for the instrument. In the example, ">300", ">" is a symbol and the digits are considered a numeric value. However, this usage of the ST type should be discouraged since the SN (structured numeric) data type now accommodates such reporting and, in addition, permits the receiving system to interpret the magnitude.

All HL7 data types are valid, and are included in Table 0125 except CM, CQ, SI, and ID. For a CM definition to have meaning, the specifics about the CM must be included in the field definition. OBX-5-observation value is a general field definition that is influenced by the data type OBX-3, so CMs are undefined in this context. CQ is invalid because units for OBX-5-observation value are always specified explicitly in an OBX segment with OBX-6 units. SI is invalid because it only applied to HL7 message segments, and ID because it requires a constant field definition.

The RP value (reference pointer) must be used if the actual observation value is not sent in OBX but exists somewhere else. For example, if the observation consists of an image (document or medical), the image itself cannot be sent in OBX. The sending system may in that case opt to send a reference pointer. The receiving system can use this reference pointer whenever it needs access to the actual image through other interface standards, e.g., DICOM, or through appropriate data base servers.

The full definition of these data types is given in Chapter 2, Section 2.9, “Data Types.” The structured numeric (SN) data type, new to version 2.3, provides for reporting ranges (e.g., 3-5 or 10-20), titres (e.g., 1:10), and out-of-range indicators (e.g., >50) in a structured and computer interpretable way.

We allow the FT data type in the OBX segment but its use is discouraged. Formatted text usually implies a meaningful structure e.g., a list of three independent diagnoses reported on different lines. But ideally, the structure in three independent diagnostic statements would be reported as three separate OBX segments.

TX should not be used except to send large amounts of text. In the TX data type, the repeat delimiter can only be used to identify paragraph breaks. Use ST to send short, and possibly encodable, text strings.

CDA documents are to be exchanged in the OBX segment in any message that can exchange documents (such as MDM or ORU). Within the OBX segment, the MIME package is encoded as an encapsulated (ED) data type.


Bevat 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 570
@Type
0 … 1 F ID
@Table
0 … 1 F HL70125
@LongName
0 … 1 F Value Type
hl7v2:OBX.3
CE 1 … 1
en-US

This field contains a unique identifier for the observation. The format is that of the Coded Element (CE).

In most systems the identifier will point to a master observation table that will provide other attributes of the observation that may be used by the receiving system to process the observations it receives. A set of message segments for transmitting such master observation tables is described in Chapter 8. The relation of an observation ID to a master observation table is analogous to the relationship between a charge code (in a billing record) and the charge master.

When local codes are used as the first identifier in this field we strongly encourage sending a universal identifier as well to permit receivers to equivalence results from different providers of the same service (e.g., a hospital lab and commercial lab that provides serum potassium to a nursing home). LOINC® is an HL7 approved code system for the Observation identifier. It covers observations and measurements, such as laboratory tests, physical findings, radiology studies, and claims attachments and can be obtained from www.regenstrief.org/loinc/loinc.htm. One possible universal identifier is LOINC® codes for laboratory and clinical measurements (see HL7 defined Table 0396 and the HL7 www list server) and Appendix X2 of ASTM E1467 for neurophysiology tests.

For a discussion of the use of suffixes as related to narrative reports see Section 7.2.3 and Section 7.2.4.


Bevat 2.16.840.1.113883.3.1937.777.10.15.5 CE - Coded element (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 571
@Type
0 … 1 F CE
@LongName
0 … 1 F Observation Identifier
  Voorbeeld 8625-6^P-R interval^LN
hl7v2:OBX.4
ST 0 … 1 Observation Sub-ID. Dit veld wordt gebruikt om verschil te kunnen maken tussen meerdere OBX-segmenten met hetzelfde Observation ID onder dezelfde OBR.
Bevat 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 572
@Type
0 … 1 F ST
@LongName
0 … 1 F Observation Sub-ID
  Constraint
(en-NL) This field is required in two situations:
  • In a result message (ORU or OUL) when the OBR segment reports the results of a microbiology culture, then the Observation Sub-ID of each related OBX segment must be populated.
  • In an order (OML) or result (ORU, OUL) message carrying observations, if under an OBR, there is more than one observation for the same Observation Identifier (OBX-3), then these multiple observations must value OBX-4 so that each OBX segment have a unique combination of OBX-3 (Observation Identifier) and OBX-4 (Observation Sub-ID) values.
In all other situations this field is optional.
  Constraint Dit veld is verplicht in twee situaties:
  • In een resultaatbericht (ORU of OUL) waar het OBR-segment de resultaten van een microbiologiekweek rapporteert, moet de Observation Sub-ID van iedere gerelateerd OBX-segment zijn gevuld.
  • In een aanvraag (OML) of resultaat (ORU, OUL) bericht met observaties, indien er onder een OBR meer dan één observatie voor dezelfde Observation Identifier (OBX-3) bestaat, dan moeten deze observaties een waarde in OBX-4 bevatten om een unieke combinatie te vormen voor iedere OBX-segment met de waarden in OBX-3 (Observation Identifier) en OBX-4 (Observation Sub-ID).
In alle andere situaties is dit veld optioneel.
hl7v2:OBX.5
varies 0 … *
en-US Observation Value

Bevat 2.16.840.1.113883.3.1937.777.10.15.67 varies (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 573
@Type
0 … 1 F varies
@LongName
0 … 1 F Observation Value
  Constraint
en-US This field is required unless the Observation Result Status field (OBX-11) is valued either with "D", or "I" or "X". The Observation Value field shall be valued according to the definition made in Chapter 7 of HL7 2.5 version.
hl7v2:OBX.6
CE 0 … 1
en-US Units

Bevat 2.16.840.1.113883.3.1937.777.10.15.5 CE - Coded element (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 574
@Type
0 … 1 F CE
@LongName
0 … 1 F Units
  Constraint
en-US This field should be populated when there is an effective observation value (OBX-5 not empty) and when the type of this observation value is numeric (OBX-2 = "NM" or "SN"). The content of this field shall be taken from the Unified Code for Units of Measure (UCUM).
hl7v2:OBX.7
ST 0 … 1
en-US References Range

Bevat 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 575
@Type
0 … 1 F ST
@LongName
0 … 1 F References Range
hl7v2:OBX.8
IS 0 … *
en-US Abnormal Flags

Bevat 2.16.840.1.113883.3.1937.777.10.15.84 IS - Coded value for user-defined tables (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 576
@Type
0 … 1 F IS
@Table
0 … 1 F HL70078
@LongName
0 … 1 F Abnormal Flags
hl7v2:OBX.9
NM 0 … 1
en-US Probability

Bevat 2.16.840.1.113883.3.1937.777.10.15.86 NM - Numeric (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 577
@Type
0 … 1 F NM
@LongName
0 … 1 F Probability
hl7v2:OBX.10
ID 0 … *
en-US Nature of Abnormal Test

Bevat 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 578
@Type
0 … 1 F ID
@Table
0 … 1 F HL70080
@LongName
0 … 1 F Nature of Abnormal Test
hl7v2:OBX.11
ID 1 … 1
en-US Observation Result Status

Bevat 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 579
@Type
0 … 1 F ID
@Table
0 … 1 F HL70085
@LongName
0 … 1 F Observation Result Status
hl7v2:OBX.12
TS 0 … 1
en-US Effective Date of Reference Range

Bevat 2.16.840.1.113883.3.1937.777.10.15.64 TS - Time stamp (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 580
@Type
0 … 1 F TS
@LongName
0 … 1 F Effective Date of Reference Range
hl7v2:OBX.13
ST 0 … 1
en-US User Defined Access Checks

Bevat 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 581
@Type
0 … 1 F ST
@LongName
0 … 1 F User Defined Access Checks
hl7v2:OBX.14
TS 0 … 1
en-US Date/Time of the Observation

Bevat 2.16.840.1.113883.3.1937.777.10.15.64 TS - Time stamp (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 582
@Type
0 … 1 F TS
@LongName
0 … 1 F Date/Time of the Observation
hl7v2:OBX.15
CE 0 … 1
en-US Producer's ID

Bevat 2.16.840.1.113883.3.1937.777.10.15.5 CE - Coded element (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 583
@Type
0 … 1 F CE
@LongName
0 … 1 F Producer's ID
hl7v2:OBX.16
XCN 0 … *
en-US Responsible Observer

Bevat 2.16.840.1.113883.3.1937.777.10.15.74 XCN - Extended composite ID number and name for persons (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 584
@Type
0 … 1 F XCN
@LongName
0 … 1 F Responsible Observer
hl7v2:OBX.17
CE 0 … *
en-US Observation Method

Bevat 2.16.840.1.113883.3.1937.777.10.15.5 CE - Coded element (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 936
@Type
0 … 1 F CE
@LongName
0 … 1 F Observation Method
hl7v2:OBX.18
EI 0 … *
en-US Equipment Instance Identifier

Bevat 2.16.840.1.113883.3.1937.777.10.15.21 EI - Entity identifier (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 1479
@Type
0 … 1 F EI
@LongName
0 … 1 F Equipment Instance Identifier
hl7v2:OBX.19
TS 0 … 1
en-US Date/Time of the Analysis

Bevat 2.16.840.1.113883.3.1937.777.10.15.64 TS - Time stamp (DYNAMISCH)
(OBXdotsent)
@Item
0 … 1 F 1480
@Type
0 … 1 F TS
@LongName
0 … 1 F Date/Time of the Analysis