v2+ Vocabulary
0.3.0 - Working Draft to present the concept ideas (FO)

v2+ Vocabulary - Local Development build (v0.3.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

: Exclusive Test (2.9 - 1.0.1) - XML Representation

Active as of 2025-08-05

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="exclusiveTestV101"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><ul><li>Include all codes defined in <a href="CodeSystem-exclusiveTestV101.html"><code>http://terminology.hl7.org/v2plusvocab/CodeSystem/exclusiveTestV101</code></a></li></ul></div>
  </text>
  <extension
             url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-v2versionCreated">
    <valueString value="2.9"/>
  </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="0919"/>
  </extension>
  <url
       value="http://terminology.hl7.org/v2plusvocab/CodeSystem/exclusiveTestV101"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.18.425"/>
  </identifier>
  <version value="1.0.1"/>
  <name value="ExclusiveTestV101"/>
  <title value="Exclusive Test (2.9 - 1.0.1)"/>
  <status value="active"/>
  <experimental value="true"/>
  <date value="2025-08-05T15:14:51+02:00"/>
  <description
               value="HL7-defined code system of concepts that define if a test should be a specific event with no other tests to be performed with this test, or not, or other special circumstances.  Used in HL7 Version 2.x messaging in Master Files (OM1 segment) to characterize observations in a master of such orderables."/>
  <copyright value="HL7 Inc., 2024"/>
  <caseSensitive value="true"/>
  <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="D"/>
    <display
             value="In some cases, this test should be only exclusively with like tests (examples are cyto or pathology)"/>
    <definition
                value="In some cases, this test should be only exclusively with like tests (examples are cyto or pathology)"/>
    <property>
      <code value="comment"/>
      <valueString
                   value="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"/>
    </property>
    <property>
      <code value="modified"/>
      <valueDateTime value="2015-07-13"/>
    </property>
    <property>
      <code value="versionIntroduced"/>
      <valueString value="2.8"/>
    </property>
  </concept>
  <concept>
    <code value="N"/>
    <display
             value="This test can be included with any number of other tests"/>
    <definition
                value="This test can be included with any number of other tests"/>
    <property>
      <code value="comment"/>
      <valueString
                   value="Default -.will be assumed when this field is empty"/>
    </property>
    <property>
      <code value="modified"/>
      <valueDateTime value="2015-07-13"/>
    </property>
    <property>
      <code value="versionIntroduced"/>
      <valueString value="2.8"/>
    </property>
  </concept>
  <concept>
    <code value="Y"/>
    <display value="This test should be exclusive"/>
    <definition value="This test should be exclusive"/>
    <property>
      <code value="modified"/>
      <valueDateTime value="2015-07-13"/>
    </property>
    <property>
      <code value="versionIntroduced"/>
      <valueString value="2.8"/>
    </property>
  </concept>
</CodeSystem>