HL7 v2.8.2 Vocabulary
0.2.0 - ci-build

HL7 v2.8.2 Vocabulary, published by HL7/FO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/hl7.v2.terminology.v282/ and changes regularly. See the Directory of published versions

## : Nature of Service/Test/Observation (2.8.2 - 1.1.0) - XML Representation

Active as of 2026-03-13

Raw xml | Download

    <CodeSystem xmlns="http://hl7.org/fhir">
      <id value="natureOfServiceTestObservation"/>
      <text>
        <status value="generated"/>
        <div xmlns="http://www.w3.org/1999/xhtml"><ul><li>Include all codes defined in <a href="CodeSystem-natureOfServiceTestObservation.html"><code>http://terminology.hl7.org/v2plusvocab/CodeSystem/natureOfServiceTestObservation</code></a></li></ul></div>
      </text>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-v2versionCreated">
        <valueString value="2.8.2"/>
      </extension>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-versionHistory">
        <valueString value="generate correct history somehow"/>
      </extension>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-tableNo">
        <valueString value="0174"/>
      </extension>
      <url
           value="http://terminology.hl7.org/v2plusvocab/CodeSystem/natureOfServiceTestObservation"/>
      <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="urn:oid:2.16.840.1.113883.18.90"/>
      </identifier>
      <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="http://terminology.hl7.org/v2plusvocab/CodeSystem/v2-0174"/>
      </identifier>
      <version value="1.1.0"/>
      <name value="NatureOfServiceTestObservation"/>
      <title value="Nature of Service/Test/Observation (2.8.2 - 1.1.0)"/>
      <status value="active"/>
      <experimental value="true"/>
      <date value="2026-03-13T11:11:43+00:00"/>
      <publisher value="HL7/FO"/>
      <contact>
        <name value="HL7/FO"/>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org"/>
        </telecom>
      </contact>
      <description
                   value="Code system of concepts specifying an identification of 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, typically used as an indicator for Master Files.  Used in HL7 Version 2.x messaging in the OM1 segment."/>
      <copyright value="HL7 Inc., 2026"/>
      <caseSensitive value="true"/>
      <compositional value="false"/>
      <content value="complete"/>
      <property>
        <code value="versionIntroduced"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced"/>
        <description value="version when was this code introduced"/>
        <type value="string"/>
      </property>
      <property>
        <code value="versionDeprecated"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated"/>
        <description value="version when was this code deprecated"/>
        <type value="string"/>
      </property>
      <property>
        <code value="status"/>
        <uri value="http://hl7.org/fhir/concept-properties#status"/>
        <description
                     value="A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired"/>
        <type value="code"/>
      </property>
      <property>
        <code value="comment"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#comment"/>
        <description
                     value="A string that provides additional detail pertinent to the use or understanding of the concept"/>
        <type value="string"/>
      </property>
      <property>
        <code value="usage"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage"/>
        <description value="usage notes for this code"/>
        <type value="string"/>
      </property>
      <property>
        <code value="modified"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified"/>
        <description value="date of last modification"/>
        <type value="dateTime"/>
      </property>
      <concept>
        <code value="A"/>
        <display value="Atomic service/test/observation"/>
        <definition
                    value="Atomic service/test/observation (test code or treatment code)"/>
        <property>
          <code value="modified"/>
          <valueDateTime value="2025-08-02"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.2"/>
        </property>
      </concept>
      <concept>
        <code value="C"/>
        <display value="Single observation, calculated"/>
        <definition
                    value="Single observation calculated via a rule or formula from other independent observations (e.g., Alveolar-arterial ratio, cardiac output)"/>
        <property>
          <code value="modified"/>
          <valueDateTime value="2025-08-02"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.2"/>
        </property>
      </concept>
      <concept>
        <code value="F"/>
        <display value="Functional procedure"/>
        <definition
                    value="Functional procedure that may consist of one or more interrelated measures (e.g., glucose tolerance test, creatinine clearance), usually done at different times and/or on different specimens"/>
        <property>
          <code value="modified"/>
          <valueDateTime value="2025-08-02"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.2"/>
        </property>
      </concept>
      <concept>
        <code value="P"/>
        <display value="Profile or battery"/>
        <definition
                    value="Profile or battery consisting of many independent atomic observations (e.g., SMA12, electrolytes), usually done at one instrument on one specimen"/>
        <designation>
          <language value="de"/>
          <value value="Batterieanordnung"/>
        </designation>
        <property>
          <code value="modified"/>
          <valueDateTime value="2025-08-02"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.2"/>
        </property>
      </concept>
      <concept>
        <code value="S"/>
        <display value="Superset-a set of batteries or procedures"/>
        <definition
                    value="Superset-a set of batteries or procedures ordered under a single code unit but processed as separate batteries (e.g., routines = CBC, UA, electrolytes)
    This set indicates that the code being described is used to order multiple service/test/observation batteries.  For example, a client who routinely orders a CBC, a differential, and a thyroxine as an outpatient profile might use a single, special code to order all three test batteries, instead of having to submit three separate order codes."/>
        <property>
          <code value="comment"/>
          <valueString
                       value="can be associated with one or more OM4 (specimen) segments
    Codes P, F, and S identify sets (batteries) and should be associated with an OM5 segment that defines the list of elements.  The definitions for the contained elements would have to be sent in other independent OMx segments, one for each contained element.  In the ASTM context, most text reports – such as discharge summaries, admission H&amp;Ps, and chest X-ray reports – are considered as sets, in which each section of the report (e.g., description, impression, and recommendation of an X-ray report) is considered a separate observation"/>
        </property>
        <property>
          <code value="modified"/>
          <valueDateTime value="2025-08-02"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.2"/>
        </property>
      </concept>
    </CodeSystem>