Extensions for Using Data Elements from FHIR STU3 in FHIR R5
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions

ValueSet: R3ConceptMapEquivalenceForR5ConceptMapRelationship

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-concept-map-equivalence-for-R5-concept-map-relationship Version: 0.1.0
Standards status: Trial-use Maturity Level: 3 Responsible: HL7 International / Terminology Infrastructure Computable Name: R3ConceptMapEquivalenceForR5ConceptMapRelationship

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/concept-map-equivalence 3.0.2 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|3.0.2 as defined in FHIR STU3 in FHIR R5.

The source value set is bound to the following FHIR STU3 elements:

  • ConceptMap.group.element.target.equivalence as Required

Across FHIR versions, the value set has been mapped as:

  • http://hl7.org/fhir/ValueSet/concept-map-equivalence|3.0.2
  • http://hl7.org/fhir/ValueSet/concept-map-equivalence|4.0.1
  • http://hl7.org/fhir/ValueSet/concept-map-equivalence|4.3.0
  • http://hl7.org/fhir/ValueSet/concept-map-relationship|5.0.0

The following concepts are not included in this cross-version definition because they have valid representations:

  • http://hl7.org/fhir/concept-map-equivalence#disjoint
  • http://hl7.org/fhir/concept-map-equivalence#equivalent
  • http://hl7.org/fhir/concept-map-equivalence#specializes
  • http://hl7.org/fhir/concept-map-equivalence#subsumes
  • http://hl7.org/fhir/concept-map-equivalence#unmatched

Following are the generation technical comments: All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (10). All concepts in the comparison are listed as identical. The source and target value sets have the same number of active concepts (10). 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

Logical Definition (CLD)

  • Include these codes as defined in http://hl7.org/fhir/concept-map-equivalence version 📍3.0.2
    CodeDisplayDefinition
    equalEqualThe 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).
    inexactInexactThe 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 attempting to use these mappings operationally.
    narrowerNarrowerThe 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.
    relatedtoRelated ToThe concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known
    widerWiderThe target mapping is wider in meaning than the source concept.

 

Expansion

This value set expansion contains 5 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/concept-map-equivalence3.0.2  equalEqualThe 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-equivalence3.0.2  inexactInexactThe 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 attempting to use these mappings operationally.
http://hl7.org/fhir/concept-map-equivalence3.0.2  narrowerNarrowerThe 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-equivalence3.0.2  relatedtoRelated ToThe 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-equivalence3.0.2  widerWiderThe 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