R4 Draft for Comment

This page is part of the FHIR Specification (v3.2.0: R4 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3 R2

4.3.1.17 Value Set http://hl7.org/fhir/ValueSet/concept-map-equivalence

FHIR Infrastructure Work Group Maturity Level: 3Normative Use Context: Any

Normative Candidate Note: This page is candidate normative content for R4 in the Conformance Package. Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/concept-map-equivalence
Name:ConceptMapEquivalence
Definition:

The degree of equivalence between concepts.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.17 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.3.1.17.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.3.1.17.2 Expansion

This expansion generated 20 Dec 2017

This value set contains 10 concepts

Expansion based on http://hl7.org/fhir/concept-map-equivalence version 3.2.0

All codes from system http://hl7.org/fhir/concept-map-equivalence

LvlCodeDisplayDefinition
0relatedtoRelated ToThe concepts are related to each other, and have at least some overlap in meaning, but the exact relationship is not known
1  equivalentEquivalentThe definitions of the concepts mean the same thing (including when structural implications of meaning are considered) (i.e. extensionally identical).
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).
1  widerWiderThe target mapping is wider in meaning than the source concept.
1  subsumesSubsumesThe target mapping subsumes the meaning of the source concept (e.g. the source is-a target).
1  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.
1  specializesSpecializesThe target mapping specializes the meaning of the source concept (e.g. the target is-a source).
1  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.
0unmatchedUnmatchedThere is no match for this concept in the destination concept system.
1  disjointDisjointThis is an explicit assertion that there is no mapping between the source and target concept.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organise codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code