FHIR Extensions Pack
5.2.0-ballot - 5.2.0 Ballot - September 2024) International flag

FHIR Extensions Pack, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 5.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-extensions/ and changes regularly. See the Directory of published versions

: Concept Map Equivalence Code System - XML Representation

Page standards status: Trial-use Maturity Level: 3

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="concept-map-equivalence"/>
  <meta>
    <lastUpdated value="2023-01-31T07:07:38.434+11:00"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem concept-map-equivalence</b></p><a name="concept-map-equivalence"> </a><a name="hcconcept-map-equivalence"> </a><a name="concept-map-equivalence-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Last updated: 2023-01-31 07:07:38+1100</p></div><p>This case-sensitive code system <code>http://hl7.org/fhir/concept-map-equivalence</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td>1</td><td style="white-space:nowrap">relatedto<a name="concept-map-equivalence-relatedto"> </a></td><td>Related To</td><td>The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known.</td></tr><tr><td>2</td><td style="white-space:nowrap">  equivalent<a name="concept-map-equivalence-equivalent"> </a></td><td>Equivalent</td><td>The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical).</td></tr><tr><td>3</td><td style="white-space:nowrap">    equal<a name="concept-map-equivalence-equal"> </a></td><td>Equal</td><td>The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical).</td></tr><tr><td>2</td><td style="white-space:nowrap">  wider<a name="concept-map-equivalence-wider"> </a></td><td>Wider</td><td>The target mapping is wider in meaning than the source concept.</td></tr><tr><td>2</td><td style="white-space:nowrap">  subsumes<a name="concept-map-equivalence-subsumes"> </a></td><td>Subsumes</td><td>The target mapping subsumes the meaning of the source concept (e.g. the source is-a target).</td></tr><tr><td>2</td><td style="white-space:nowrap">  narrower<a name="concept-map-equivalence-narrower"> </a></td><td>Narrower</td><td>The target mapping is narrower in meaning than the source concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally.</td></tr><tr><td>2</td><td style="white-space:nowrap">  specializes<a name="concept-map-equivalence-specializes"> </a></td><td>Specializes</td><td>The target mapping specializes the meaning of the source concept (e.g. the target is-a source).</td></tr><tr><td>2</td><td style="white-space:nowrap">  inexact<a name="concept-map-equivalence-inexact"> </a></td><td>Inexact</td><td>The target mapping overlaps with the source concept, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is inexact SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally.</td></tr><tr><td>1</td><td style="white-space:nowrap">unmatched<a name="concept-map-equivalence-unmatched"> </a></td><td>Unmatched</td><td>There is no match for this concept in the target code system.</td></tr><tr><td>2</td><td style="white-space:nowrap">  disjoint<a name="concept-map-equivalence-disjoint"> </a></td><td>Disjoint</td><td>This is an explicit assertion that there is no mapping between the source and target concept.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="3"/>
  </extension>
  <url value="http://hl7.org/fhir/concept-map-equivalence"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.1.18"/>
  </identifier>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.4.18"/>
  </identifier>
  <version value="5.2.0-ballot"/>
  <name value="ConceptMapEquivalence"/>
  <title value="Concept Map Equivalence Code System"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2023-01-31T07:07:38+11:00"/>
  <publisher value="HL7 International / FHIR Infrastructure"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description value="The degree of equivalence between concepts."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/concept-map-equivalence"/>
  <hierarchyMeaning value="is-a"/>
  <content value="complete"/>
  <concept>
    <code value="relatedto"/>
    <display value="Related To"/>
    <definition
                value="The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known."/>
    <concept>
      <code value="equivalent"/>
      <display value="Equivalent"/>
      <definition
                  value="The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical)."/>
      <concept>
        <code value="equal"/>
        <display value="Equal"/>
        <definition
                    value="The definitions of the concepts are exactly the same (i.e. only grammatical differences) and structural implications of meaning are identical or irrelevant (i.e. intentionally identical)."/>
      </concept>
    </concept>
    <concept>
      <code value="wider"/>
      <display value="Wider"/>
      <definition
                  value="The target mapping is wider in meaning than the source concept."/>
    </concept>
    <concept>
      <code value="subsumes"/>
      <display value="Subsumes"/>
      <definition
                  value="The target mapping subsumes the meaning of the source concept (e.g. the source is-a target)."/>
    </concept>
    <concept>
      <code value="narrower"/>
      <display value="Narrower"/>
      <definition
                  value="The target mapping is narrower in meaning than the source concept. The sense in which the mapping is narrower SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally."/>
    </concept>
    <concept>
      <code value="specializes"/>
      <display value="Specializes"/>
      <definition
                  value="The target mapping specializes the meaning of the source concept (e.g. the target is-a source)."/>
    </concept>
    <concept>
      <code value="inexact"/>
      <display value="Inexact"/>
      <definition
                  value="The target mapping overlaps with the source concept, but both source and target cover additional meaning, or the definitions are imprecise and it is uncertain whether they have the same boundaries to their meaning. The sense in which the mapping is inexact SHALL be described in the comments in this case, and applications should be careful when attempting to use these mappings operationally."/>
    </concept>
  </concept>
  <concept>
    <code value="unmatched"/>
    <display value="Unmatched"/>
    <definition
                value="There is no match for this concept in the target code system."/>
    <concept>
      <code value="disjoint"/>
      <display value="Disjoint"/>
      <definition
                  value="This is an explicit assertion that there is no mapping between the source and target concept."/>
    </concept>
  </concept>
</CodeSystem>