Extensions for Using Data Elements from FHIR R4B in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R4B-concept-map-equivalence-for-R5-concept-map-relationship | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 3 | Computable Name: R4BConceptMapEquivalenceForR5ConceptMapRelationship | ||
| This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/concept-map-equivalence | 4.3.0 for use in FHIR R5 that is appropriate for use but unavailable in http://hl7.org/fhir/ValueSet/concept-map-relationship|5.0.0. |
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/concept-map-equivalence|4.3.0 as defined in FHIR R4B
in FHIR R5.
The source value set is bound to the following FHIR R4B elements:
ConceptMap.group.element.target.equivalenceThe following concepts are not included in this cross-version definition because they have valid representations:
http://hl7.org/fhir/concept-map-equivalence#disjointhttp://hl7.org/fhir/concept-map-equivalence#equivalenthttp://hl7.org/fhir/concept-map-equivalence#specializeshttp://hl7.org/fhir/concept-map-equivalence#subsumesFollowing are the generation technical comments: One or more source concepts are either not mapped or broader than their targets, so the value set relationship is broadened. One or more source concepts are narrower than their targets, so the value set relationship is narrowed. The source value set has more active concepts (10) than the target (5), so the source is broader than the target.
References
http://hl7.org/fhir/concept-map-equivalence version 📍4.3.0| Code | Display | Definition |
| 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). |
| 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. |
| 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. |
| 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. |
| unmatched | Unmatched | There is no match for this concept in the target code system. |
| wider | Wider | The target mapping is wider in meaning than the source concept. |
This value set expansion contains 6 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | 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). | ||
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | 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. | ||
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | 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. | ||
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | 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. | ||
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | unmatched | Unmatched | There is no match for this concept in the target code system. | ||
http://hl7.org/fhir/concept-map-equivalence | 4.3.0 | wider | Wider | The target mapping is wider in meaning than the source 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 |