2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Concept-equivalence.xml

Raw XML (canonical form)

Definition for Value SetConceptMapEquivalence

Raw XML

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="concept-equivalence"/>
  <meta>
    <lastUpdated value="2015-02-23T09:07:27.665+11:00"/>
    <profile value="http://hl7.org/fhir/Profile/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div>
  </text>
  <extension url="http://hl7.org/fhir/ExtensionDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.306"/>
  </extension>
  <url value="http://hl7.org/fhir/vs/concept-equivalence"/>
  <version value="0.4.0"/>
  <name value="ConceptMapEquivalence"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  <description value="The degree of equivalence between concepts"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2015-02-23T09:07:27+11:00"/>
  <define>
    <extension url="http://hl7.org/fhir/ExtensionDefinition/valueset-oid">
      <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.306"/>
    </extension>
    <system value="http://hl7.org/fhir/concept-equivalence"/>
    <caseSensitive value="true"/>
    <concept>
      <code 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"/>
        <definition value="The definitions of the concepts are exactly the same (i.e. only grammatical differences)
         and structural implications of meaning are identifical or irrelevant (i.e. intensionally
         identical)."/>
      </concept>
    </concept>
    <concept>
      <code value="wider"/>
      <definition value="The target mapping is wider in meaning than the source concept."/>
      <concept>
        <code value="subsumes"/>
        <definition value="The target mapping subsumes the meaning of the source concept (e.g. the source is-a target)."/>
      </concept>
    </concept>
    <concept>
      <code value="narrower"/>
      <definition value="The target mapping is narrower in meaning that 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 atempting to use these mappings operationally."/>
      <concept>
        <code value="specialises"/>
        <definition value="The target mapping specialises the meaning of the source concept (e.g. the target is-a
         source)."/>
      </concept>
    </concept>
    <concept>
      <code 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 narrower
       SHALL be described in the comments in this case, and applications should be careful when
       atempting to use these mappings operationally."/>
    </concept>
    <concept>
      <code value="unmatched"/>
      <definition value="There is no match for this concept in the destination concept system."/>
      <concept>
        <code value="disjoint"/>
        <definition value="This is an explicit assertion that there is no mapping between the source and target concept."/>
      </concept>
    </concept>
  </define>
</ValueSet>

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.