This page is part of the FHIR Core Extensions Registry (v0.1.0: Releases Draft) based on FHIR v5.0.0. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/ValueSet/concept-map-equivalence | Version: 0.1.0 | |||
Draft as of 2023-01-31 | Computable Name: ConceptMapEquivalence | |||
Other Identifiers: id: urn:oid:2.16.840.1.113883.4.642.3.17 |
The degree of equivalence between concepts.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/concept-map-equivalence
This value set contains 10 concepts
Expansion based on ConceptMapEquivalence v5.0.0-draft-final (CodeSystem)
Level | Code | System | Display | Definition |
1 | relatedto | http://hl7.org/fhir/concept-map-equivalence | Related To | The concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known. |
2 | equivalent | http://hl7.org/fhir/concept-map-equivalence | Equivalent | The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical). |
3 | equal | http://hl7.org/fhir/concept-map-equivalence | Equal | 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). |
2 | wider | http://hl7.org/fhir/concept-map-equivalence | Wider | The target mapping is wider in meaning than the source concept. |
2 | subsumes | http://hl7.org/fhir/concept-map-equivalence | Subsumes | The target mapping subsumes the meaning of the source concept (e.g. the source is-a target). |
2 | narrower | http://hl7.org/fhir/concept-map-equivalence | Narrower | 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. |
2 | specializes | http://hl7.org/fhir/concept-map-equivalence | Specializes | The target mapping specializes the meaning of the source concept (e.g. the target is-a source). |
2 | inexact | http://hl7.org/fhir/concept-map-equivalence | Inexact | 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. |
1 | unmatched | http://hl7.org/fhir/concept-map-equivalence | Unmatched | There is no match for this concept in the target code system. |
2 | disjoint | http://hl7.org/fhir/concept-map-equivalence | Disjoint | This is an explicit assertion that there is no mapping between the source and target concept. |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |