FHIR 4.0.1 © HL7.org  |  FHIRsmith 0.9.6  |  Server Home  |  TX Home  |  Capability Statement  |  Terminology Capabilities  |  Operations  |  Problems  |   

TX: CodeSystem concept-map-equivalence

Properties

Last updated: January 30, 2023 at 08:07:38 PM UTC
Defining URL http://hl7.org/fhir/concept-map-equivalence
Version 5.1.0
Name ConceptMapEquivalence
Title Concept Map Equivalence Code System
Status active
Definition

The degree of equivalence between concepts.
Publisher HL7 International / FHIR Infrastructure
Committee fhir
EXT_FMM_LEVEL 3
Source hl7.fhir.uv.extensions.r4#5.1.0
Value Set ConceptMapEquivalence

This case-sensitive code system http://hl7.org/fhir/concept-map-equivalence defines the following codes in a is-a hierarchy:

Level Code Display Definition
1 relatedto 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 Equivalent The definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical).
3     equal 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 Wider The target mapping is wider in meaning than the source concept.
2   subsumes Subsumes The target mapping subsumes the meaning of the source concept (e.g. the source is-a target).
2   narrower 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 Specializes The target mapping specializes the meaning of the source concept (e.g. the target is-a source).
2   inexact 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 Unmatched There is no match for this concept in the target code system.
2   disjoint Disjoint This is an explicit assertion that there is no mapping between the source and target concept.