Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R2-ValueSet-element-map-to-R4"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R2-ValueSet-element-map-to-R4</b></p><a name="R2-ValueSet-element-map-to-R4"> </a><a name="hcR2-ValueSet-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="http://hl7.org/fhir/R4/codesystem.html">CodeSystemversion: 4.0.1)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.meta</td><td>Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td>ValueSet.implicitRules (implicitRules)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.implicitRules</td><td>Element `ValueSet.implicitRules` is mapped to FHIR R4 element `CodeSystem.implicitRules` as `Equivalent`.
Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.</td></tr><tr><td>ValueSet.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.language</td><td>Element `ValueSet.language` is mapped to FHIR R4 element `CodeSystem.language` as `Equivalent`.
Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td>ValueSet.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.text</td><td>Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.</td></tr><tr><td>ValueSet.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.contained</td><td>Element `ValueSet.contained` is mapped to FHIR R4 element `CodeSystem.contained` as `SourceIsBroaderThanTarget`.
Element `ValueSet.contained` is mapped to FHIR R4 element `ValueSet.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.</td></tr><tr><td>ValueSet.url (url)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.url</td><td>Element `ValueSet.url` is mapped to FHIR R4 element `CodeSystem.url` as `Equivalent`.
Element `ValueSet.url` is mapped to FHIR R4 element `ValueSet.url` as `Equivalent`.</td></tr><tr><td>ValueSet.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.identifier</td><td>Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type.</td></tr><tr><td>ValueSet.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.version</td><td>Element `ValueSet.version` is mapped to FHIR R4 element `CodeSystem.version` as `Equivalent`.
Element `ValueSet.version` is mapped to FHIR R4 element `ValueSet.version` as `Equivalent`.
There may be multiple resource versions of the value set that have the same identifier.</td></tr><tr><td>ValueSet.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.name</td><td>Element `ValueSet.name` is mapped to FHIR R4 element `CodeSystem.name` as `Equivalent`.
Element `ValueSet.name` is mapped to FHIR R4 element `ValueSet.name` as `Equivalent`.
The name is not expected to be unique. A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.</td></tr><tr><td>ValueSet.status (status)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.status</td><td>Element `ValueSet.status` is mapped to FHIR R4 element `CodeSystem.status` as `SourceIsNarrowerThanTarget`.
Element `ValueSet.status` is mapped to FHIR R4 element `ValueSet.status` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Allows filtering of value set instances that are appropriate (or not) for use.</td></tr><tr><td>ValueSet.experimental (experimental)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.experimental</td><td>Element `ValueSet.experimental` is mapped to FHIR R4 element `CodeSystem.experimental` as `Equivalent`.
Element `ValueSet.experimental` is mapped to FHIR R4 element `ValueSet.experimental` as `Equivalent`.
Allows filtering of value sets that are appropriate for use vs. not.</td></tr><tr><td>ValueSet.publisher (publisher)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.publisher</td><td>Element `ValueSet.publisher` is mapped to FHIR R4 element `CodeSystem.publisher` as `Equivalent`.
Element `ValueSet.publisher` is mapped to FHIR R4 element `ValueSet.publisher` as `Equivalent`.
Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.</td></tr><tr><td>ValueSet.contact (contact)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.contact</td><td>Element `ValueSet.contact` is mapped to FHIR R4 element `CodeSystem.contact` as `Equivalent`.
Element `ValueSet.contact` is mapped to FHIR R4 element `ValueSet.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc.</td></tr><tr><td>ValueSet.date (date)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.date</td><td>Element `ValueSet.date` is mapped to FHIR R4 element `CodeSystem.date` as `Equivalent`.
Element `ValueSet.date` is mapped to FHIR R4 element `ValueSet.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions.</td></tr><tr><td>ValueSet.description (description)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.description</td><td>Element `ValueSet.description` is mapped to FHIR R4 element `CodeSystem.description` as `Equivalent`.
Element `ValueSet.description` is mapped to FHIR R4 element `ValueSet.description` as `Equivalent`.
The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description.</td></tr><tr><td>ValueSet.useContext (useContext)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td>CodeSystem.useContext</td><td>Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`.</td></tr><tr><td>ValueSet.copyright (copyright)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CodeSystem.copyright</td><td>Element `ValueSet.copyright` is mapped to FHIR R4 element `CodeSystem.copyright` as `Equivalent`.
Element `ValueSet.copyright` is mapped to FHIR R4 element `ValueSet.copyright` as `Equivalent`.
Frequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="http://hl7.org/fhir/R4/valueset.html">ValueSetversion: 4.0.1)</a></p><table class="grid"><tr><td colspan="2"><b>Source Concept Details</b></td><td><b>Relationship</b></td><td colspan="2"><b>Target Concept Details</b></td><td><b>Comment</b></td></tr><tr><td colspan="2"><b>Codes</b> from http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</td><td/><td colspan="2" title="http://hl7.org/fhir/StructureDefinition/ValueSet|4.0.1"><b>Codes</b> from ValueSet</td><td/></tr><tr><td style="border-right-width: 0px">ValueSet.meta</td><td style="border-left-width: 0px">meta</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.meta</td><td style="border-left-width: 0px">ValueSet.meta</td><td>Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td style="border-right-width: 0px">ValueSet.implicitRules</td><td style="border-left-width: 0px">implicitRules</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.implicitRules</td><td style="border-left-width: 0px">ValueSet.implicitRules</td><td>Element `ValueSet.implicitRules` is mapped to FHIR R4 element `CodeSystem.implicitRules` as `Equivalent`.
Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.</td></tr><tr><td style="border-right-width: 0px">ValueSet.language</td><td style="border-left-width: 0px">language</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.language</td><td style="border-left-width: 0px">ValueSet.language</td><td>Element `ValueSet.language` is mapped to FHIR R4 element `CodeSystem.language` as `Equivalent`.
Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td style="border-right-width: 0px">ValueSet.text</td><td style="border-left-width: 0px">text</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.text</td><td style="border-left-width: 0px">ValueSet.text</td><td>Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.</td></tr><tr><td style="border-right-width: 0px">ValueSet.contained</td><td style="border-left-width: 0px">contained</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.contained</td><td style="border-left-width: 0px">ValueSet.contained</td><td>Element `ValueSet.contained` is mapped to FHIR R4 element `CodeSystem.contained` as `SourceIsBroaderThanTarget`.
Element `ValueSet.contained` is mapped to FHIR R4 element `ValueSet.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.</td></tr><tr><td style="border-right-width: 0px">ValueSet.url</td><td style="border-left-width: 0px">url</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.url</td><td style="border-left-width: 0px">ValueSet.url</td><td>Element `ValueSet.url` is mapped to FHIR R4 element `CodeSystem.url` as `Equivalent`.
Element `ValueSet.url` is mapped to FHIR R4 element `ValueSet.url` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.identifier</td><td style="border-left-width: 0px">identifier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.identifier</td><td style="border-left-width: 0px">ValueSet.identifier</td><td>Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type.</td></tr><tr><td style="border-right-width: 0px">ValueSet.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.version</td><td style="border-left-width: 0px">ValueSet.version</td><td>Element `ValueSet.version` is mapped to FHIR R4 element `CodeSystem.version` as `Equivalent`.
Element `ValueSet.version` is mapped to FHIR R4 element `ValueSet.version` as `Equivalent`.
There may be multiple resource versions of the value set that have the same identifier.</td></tr><tr><td style="border-right-width: 0px">ValueSet.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.name</td><td style="border-left-width: 0px">ValueSet.name</td><td>Element `ValueSet.name` is mapped to FHIR R4 element `CodeSystem.name` as `Equivalent`.
Element `ValueSet.name` is mapped to FHIR R4 element `ValueSet.name` as `Equivalent`.
The name is not expected to be unique. A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.</td></tr><tr><td style="border-right-width: 0px">ValueSet.status</td><td style="border-left-width: 0px">status</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.status</td><td style="border-left-width: 0px">ValueSet.status</td><td>Element `ValueSet.status` is mapped to FHIR R4 element `CodeSystem.status` as `SourceIsNarrowerThanTarget`.
Element `ValueSet.status` is mapped to FHIR R4 element `ValueSet.status` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Allows filtering of value set instances that are appropriate (or not) for use.</td></tr><tr><td style="border-right-width: 0px">ValueSet.experimental</td><td style="border-left-width: 0px">experimental</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.experimental</td><td style="border-left-width: 0px">ValueSet.experimental</td><td>Element `ValueSet.experimental` is mapped to FHIR R4 element `CodeSystem.experimental` as `Equivalent`.
Element `ValueSet.experimental` is mapped to FHIR R4 element `ValueSet.experimental` as `Equivalent`.
Allows filtering of value sets that are appropriate for use vs. not.</td></tr><tr><td style="border-right-width: 0px">ValueSet.publisher</td><td style="border-left-width: 0px">publisher</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.publisher</td><td style="border-left-width: 0px">ValueSet.publisher</td><td>Element `ValueSet.publisher` is mapped to FHIR R4 element `CodeSystem.publisher` as `Equivalent`.
Element `ValueSet.publisher` is mapped to FHIR R4 element `ValueSet.publisher` as `Equivalent`.
Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.</td></tr><tr><td style="border-right-width: 0px">ValueSet.contact</td><td style="border-left-width: 0px">contact</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.contact</td><td style="border-left-width: 0px">ValueSet.contact</td><td>Element `ValueSet.contact` is mapped to FHIR R4 element `CodeSystem.contact` as `Equivalent`.
Element `ValueSet.contact` is mapped to FHIR R4 element `ValueSet.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc.</td></tr><tr><td style="border-right-width: 0px">ValueSet.date</td><td style="border-left-width: 0px">date</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.date</td><td style="border-left-width: 0px">ValueSet.date</td><td>Element `ValueSet.date` is mapped to FHIR R4 element `CodeSystem.date` as `Equivalent`.
Element `ValueSet.date` is mapped to FHIR R4 element `ValueSet.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions.</td></tr><tr><td style="border-right-width: 0px">ValueSet.lockedDate</td><td style="border-left-width: 0px">lockedDate</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.lockedDate</td><td style="border-left-width: 0px">ValueSet.compose.lockedDate</td><td>Element `ValueSet.lockedDate` is mapped to FHIR R4 element `ValueSet.compose.lockedDate` as `Equivalent`.
With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.</td></tr><tr><td style="border-right-width: 0px">ValueSet.description</td><td style="border-left-width: 0px">description</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.description</td><td style="border-left-width: 0px">ValueSet.description</td><td>Element `ValueSet.description` is mapped to FHIR R4 element `CodeSystem.description` as `Equivalent`.
Element `ValueSet.description` is mapped to FHIR R4 element `ValueSet.description` as `Equivalent`.
The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description.</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">ValueSet.useContext</td><td style="border-left-width: 0px; border-bottom-style: none">useContext</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.jurisdiction</td><td style="border-left-width: 0px">ValueSet.jurisdiction</td><td>Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.useContext</td><td style="border-left-width: 0px">ValueSet.useContext</td><td>Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.immutable</td><td style="border-left-width: 0px">immutable</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.immutable</td><td style="border-left-width: 0px">ValueSet.immutable</td><td>Element `ValueSet.immutable` is mapped to FHIR R4 element `ValueSet.immutable` as `Equivalent`.
Normally immutability is set to 'false', which is the default assumption if it is not populated. Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change. For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition.</td></tr><tr><td style="border-right-width: 0px">ValueSet.requirements</td><td style="border-left-width: 0px">requirements</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.purpose</td><td style="border-left-width: 0px">ValueSet.purpose</td><td>Element `ValueSet.requirements` is mapped to FHIR R4 element `ValueSet.purpose` as `Equivalent`.
This element does not describe the usage of the value set (that is done in comments), rather it's for traceability of ''why'' the element is either needed or ''why'' the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element.</td></tr><tr><td style="border-right-width: 0px">ValueSet.copyright</td><td style="border-left-width: 0px">copyright</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.copyright</td><td style="border-left-width: 0px">ValueSet.copyright</td><td>Element `ValueSet.copyright` is mapped to FHIR R4 element `CodeSystem.copyright` as `Equivalent`.
Element `ValueSet.copyright` is mapped to FHIR R4 element `ValueSet.copyright` as `Equivalent`.
Frequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose</td><td style="border-left-width: 0px">compose</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.compose</td><td style="border-left-width: 0px">ValueSet.compose</td><td>Element `ValueSet.compose` is mapped to FHIR R4 element `ValueSet.compose` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include</td><td style="border-left-width: 0px">include</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.compose.include</td><td style="border-left-width: 0px">ValueSet.compose.include</td><td>Element `ValueSet.compose.include` is mapped to FHIR R4 element `ValueSet.compose.include` as `Equivalent`.
If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.system</td><td style="border-left-width: 0px">system</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.system</td><td style="border-left-width: 0px">ValueSet.compose.include.system</td><td>Element `ValueSet.compose.include.system` is mapped to FHIR R4 element `ValueSet.compose.include.system` as `Equivalent`.
See ''Coding.system'' for further documentation.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.version</td><td style="border-left-width: 0px">ValueSet.compose.include.version</td><td>Element `ValueSet.compose.include.version` is mapped to FHIR R4 element `ValueSet.compose.include.version` as `Equivalent`.
This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set may not be known until a context of use binds it to a particular version.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.concept</td><td style="border-left-width: 0px">concept</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.concept</td><td style="border-left-width: 0px">ValueSet.compose.include.concept</td><td>Element `ValueSet.compose.include.concept` is mapped to FHIR R4 element `ValueSet.compose.include.concept` as `Equivalent`.
The list of concepts is considered ordered, though the order may not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.concept.code</td><td style="border-left-width: 0px">code</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.concept.code</td><td style="border-left-width: 0px">ValueSet.compose.include.concept.code</td><td>Element `ValueSet.compose.include.concept.code` is mapped to FHIR R4 element `ValueSet.compose.include.concept.code` as `Equivalent`.
Expressions are allowed if defined by the underlying code system.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.concept.display</td><td style="border-left-width: 0px">display</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.concept.display</td><td style="border-left-width: 0px">ValueSet.compose.include.concept.display</td><td>Element `ValueSet.compose.include.concept.display` is mapped to FHIR R4 element `ValueSet.compose.include.concept.display` as `Equivalent`.
The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.concept.designation</td><td style="border-left-width: 0px">designation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.concept.designation</td><td style="border-left-width: 0px">ValueSet.compose.include.concept.designation</td><td>Element `ValueSet.compose.include.concept.designation` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.filter</td><td style="border-left-width: 0px">filter</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.filter</td><td style="border-left-width: 0px">ValueSet.compose.include.filter</td><td>Element `ValueSet.compose.include.filter` is mapped to FHIR R4 element `ValueSet.compose.include.filter` as `Equivalent`.
Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.filter.property</td><td style="border-left-width: 0px">property</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.filter.property</td><td style="border-left-width: 0px">ValueSet.compose.include.filter.property</td><td>Element `ValueSet.compose.include.filter.property` is mapped to FHIR R4 element `ValueSet.compose.include.filter.property` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.filter.op</td><td style="border-left-width: 0px">op</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.filter.op</td><td style="border-left-width: 0px">ValueSet.compose.include.filter.op</td><td>Element `ValueSet.compose.include.filter.op` is mapped to FHIR R4 element `ValueSet.compose.include.filter.op` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.compose.include.filter.op` do not allow expression of the necessary codes, per the bindings on the source and target.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.include.filter.value</td><td style="border-left-width: 0px">value</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.include.filter.value</td><td style="border-left-width: 0px">ValueSet.compose.include.filter.value</td><td>Element `ValueSet.compose.include.filter.value` is mapped to FHIR R4 element `ValueSet.compose.include.filter.value` as `Equivalent`.
Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example.</td></tr><tr><td style="border-right-width: 0px">ValueSet.compose.exclude</td><td style="border-left-width: 0px">exclude</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.compose.exclude</td><td style="border-left-width: 0px">ValueSet.compose.exclude</td><td>Element `ValueSet.compose.exclude` is mapped to FHIR R4 element `ValueSet.compose.exclude` as `Equivalent`.
Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion</td><td style="border-left-width: 0px">expansion</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.expansion</td><td style="border-left-width: 0px">ValueSet.expansion</td><td>Element `ValueSet.expansion` is mapped to FHIR R4 element `ValueSet.expansion` as `Equivalent`.
Expansion is performed to produce a collection of codes that are ready to use for data entry or validation.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.identifier</td><td style="border-left-width: 0px">identifier</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.identifier</td><td style="border-left-width: 0px">ValueSet.expansion.identifier</td><td>Element `ValueSet.expansion.identifier` is mapped to FHIR R4 element `ValueSet.expansion.identifier` as `Equivalent`.
Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.timestamp</td><td style="border-left-width: 0px">timestamp</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.timestamp</td><td style="border-left-width: 0px">ValueSet.expansion.timestamp</td><td>Element `ValueSet.expansion.timestamp` is mapped to FHIR R4 element `ValueSet.expansion.timestamp` as `Equivalent`.
This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.total</td><td style="border-left-width: 0px">total</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.total</td><td style="border-left-width: 0px">ValueSet.expansion.total</td><td>Element `ValueSet.expansion.total` is mapped to FHIR R4 element `ValueSet.expansion.total` as `Equivalent`.
Paging only applies to flat expansions.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.offset</td><td style="border-left-width: 0px">offset</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.offset</td><td style="border-left-width: 0px">ValueSet.expansion.offset</td><td>Element `ValueSet.expansion.offset` is mapped to FHIR R4 element `ValueSet.expansion.offset` as `Equivalent`.
Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.parameter</td><td style="border-left-width: 0px">parameter</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.expansion.parameter</td><td style="border-left-width: 0px">ValueSet.expansion.parameter</td><td>Element `ValueSet.expansion.parameter` is mapped to FHIR R4 element `ValueSet.expansion.parameter` as `Equivalent`.
The server decides which parameters to include here, but at a minimum, the list SHOULD include the date, filter, and profile parameters passed to the $expand operation (if any).</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.parameter.name</td><td style="border-left-width: 0px">name</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.parameter.name</td><td style="border-left-width: 0px">ValueSet.expansion.parameter.name</td><td>Element `ValueSet.expansion.parameter.name` is mapped to FHIR R4 element `ValueSet.expansion.parameter.name` as `Equivalent`.
The names are assigned at the discretion of the server.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.parameter.value[x]</td><td style="border-left-width: 0px">value[x]</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.expansion.parameter.value[x]</td><td style="border-left-width: 0px">ValueSet.expansion.parameter.value[x]</td><td>Element `ValueSet.expansion.parameter.value[x]` is mapped to FHIR R4 element `ValueSet.expansion.parameter.value[x]` as `RelatedTo`.
The target context `ValueSet.expansion.parameter.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ValueSet.expansion.parameter`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains</td><td style="border-left-width: 0px">contains</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#relatedto" title="relatedto">is related to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains</td><td style="border-left-width: 0px">ValueSet.expansion.contains</td><td>Element `ValueSet.expansion.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.system</td><td style="border-left-width: 0px">system</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.system</td><td style="border-left-width: 0px">ValueSet.expansion.contains.system</td><td>Element `ValueSet.expansion.contains.system` is mapped to FHIR R4 element `ValueSet.expansion.contains.system` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.abstract</td><td style="border-left-width: 0px">abstract</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.abstract</td><td style="border-left-width: 0px">ValueSet.expansion.contains.abstract</td><td>Element `ValueSet.expansion.contains.abstract` is mapped to FHIR R4 element `ValueSet.expansion.contains.abstract` as `Equivalent`.
This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.version</td><td style="border-left-width: 0px">version</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.version</td><td style="border-left-width: 0px">ValueSet.expansion.contains.version</td><td>Element `ValueSet.expansion.contains.version` is mapped to FHIR R4 element `ValueSet.expansion.contains.version` as `Equivalent`.
The exact value of the version string is specified by the system from which the code is derived.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.code</td><td style="border-left-width: 0px">code</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.code</td><td style="border-left-width: 0px">ValueSet.expansion.contains.code</td><td>Element `ValueSet.expansion.contains.code` is mapped to FHIR R4 element `ValueSet.expansion.contains.code` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.display</td><td style="border-left-width: 0px">display</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.display</td><td style="border-left-width: 0px">ValueSet.expansion.contains.display</td><td>Element `ValueSet.expansion.contains.display` is mapped to FHIR R4 element `ValueSet.expansion.contains.display` as `Equivalent`.</td></tr><tr><td style="border-right-width: 0px">ValueSet.expansion.contains.contains</td><td style="border-left-width: 0px">contains</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td style="border-right-width: 0px">ValueSet.expansion.contains.contains</td><td style="border-left-width: 0px">ValueSet.expansion.contains.contains</td><td>Element `ValueSet.expansion.contains.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains.contains` as `Equivalent`.
If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.meta.html">DSTU2: Metadata about the resource additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Metadata about the resource additional types)</td><td>Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.text.html">DSTU2: Text summary of the resource, for human interpretation additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Text summary of the resource, for human interpretation additional types)</td><td>Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.identifier.html">DSTU2: Additional identifier for the value set (e.g. HL7 v2 / CDA) additional typesversion: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Additional identifier for the value set (e.g. HL7 v2 / CDA) additional types)</td><td>Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.con.name.html">DSTU2: Name of an individual to contact (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.contact.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Name of an individual to contact (new))</td><td>Element `ValueSet.contact.name` has a context of CodeSystem.contact based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.contact.name` has a context of ValueSet.contact based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.contact.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If there is no named individual, the telecom is for the organization as a whole.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.con.telecom.html">DSTU2: Contact details for individual or publisher (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.contact.telecom (telecom)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Contact details for individual or publisher (new))</td><td>Element `ValueSet.contact.telecom` has a context of CodeSystem.contact based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.contact.telecom` has a context of ValueSet.contact based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.contact.telecom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.extensible.html">DSTU2: Whether this is intended to be used with an extensible binding (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.extensible (extensible)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Whether this is intended to be used with an extensible binding (new))</td><td>Element `ValueSet.extensible` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.extensible` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.extensible` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.codeSystem.html">DSTU2: An inline code system, which is part of this value set (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.codeSystem (codeSystem)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: An inline code system, which is part of this value set (new))</td><td>Element `ValueSet.codeSystem` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
All code systems defined as part of a FHIR value set have an implicit valueset that includes all of the codes in the code system - the value set in which they are defined.</td></tr><tr><td>ValueSet.codeSystem.system (system)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:system (DSTU2: URI to identify the code system (e.g. in Coding.system) (new))</td><td>Element `ValueSet.codeSystem.system` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.system` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.system` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The reference is not required to point to any specific kind of definition, but the more information that can be provided, the more useful it is for implementers. Best practice is to resolve to a computable definition of the code system (either a value set, or some other format). Terminology servers MAY validate this reference (e.g. when accepting PUT/POST), and MAY make additional rules about what kind of content it refers to.</td></tr><tr><td>ValueSet.codeSystem.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version (DSTU2: Version (for use in Coding.version) (new))</td><td>Element `ValueSet.codeSystem.version` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.version` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.version` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.caseSensitive (caseSensitive)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:caseSensitive (DSTU2: If code comparison is case sensitive (new))</td><td>Element `ValueSet.codeSystem.caseSensitive` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.caseSensitive` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.caseSensitive` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.caseSensitive` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case. This element is primarily provided to support validation software.</td></tr><tr><td>ValueSet.codeSystem.concept (concept)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept (DSTU2: Concepts in the code system (new))</td><td>Element `ValueSet.codeSystem.concept` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:code (DSTU2: Code that identifies concept (new))</td><td>Element `ValueSet.codeSystem.concept.code` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.code` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.code` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.abstract (abstract)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:abstract (DSTU2: If this code is not for use as a real concept (new))</td><td>Element `ValueSet.codeSystem.concept.abstract` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.abstract` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.abstract` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.abstract` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.display (display)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:display (DSTU2: Text to display to the user (new))</td><td>Element `ValueSet.codeSystem.concept.display` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.display` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.display` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.definition (definition)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:definition (DSTU2: Formal definition (new))</td><td>Element `ValueSet.codeSystem.concept.definition` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.definition` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.definition` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.designation (designation)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:designation (DSTU2: Additional representations for the concept (new))</td><td>Element `ValueSet.codeSystem.concept.designation` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.designation.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:designation.extension:language (DSTU2: Human language of the designation (new))</td><td>Element `ValueSet.codeSystem.concept.designation.language` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.language` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.language` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
In the absence of a language, the resource language applies.</td></tr><tr><td>ValueSet.codeSystem.concept.designation.use (use)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:designation.extension:use (DSTU2: Details how this designation would be used (new))</td><td>Element `ValueSet.codeSystem.concept.designation.use` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.use` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.use` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If no use is provided, the designation can be assumed to be suitable for general display to a human user.</td></tr><tr><td>ValueSet.codeSystem.concept.designation.value (value)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:designation.extension:value (DSTU2: The text value for this designation (new))</td><td>Element `ValueSet.codeSystem.concept.designation.value` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.value` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.value` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ValueSet.codeSystem.concept.concept (concept)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:concept.extension:concept (DSTU2: Child Concepts (is-a/contains/categorizes) (new))</td><td>Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.cod.concept.html">DSTU2: Concepts in the code system (new)version: 0.1.0)</a></p><table class="grid"><tr><td colspan="2"><b>Source Concept Details</b></td><td><b>Relationship</b></td><td colspan="2"><b>Target Concept Details</b></td><td><b>Comment</b></td></tr><tr><td colspan="2"><b>Codes</b> from http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</td><td/><td colspan="2" title="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.codeSystem.concept|0.1.0"><b>Codes</b> from DSTU2: Concepts in the code system (new)</td><td/></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept</td><td style="border-left-width: 0px">concept</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.code</td><td style="border-left-width: 0px">code</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:code</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.code` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.code` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.code` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.abstract</td><td style="border-left-width: 0px">abstract</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:abstract</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.abstract` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.abstract` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.abstract` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.abstract` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.display</td><td style="border-left-width: 0px">display</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:display</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.display` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.display` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.display` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.definition</td><td style="border-left-width: 0px">definition</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:definition</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.definition` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.definition` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.definition` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.designation</td><td style="border-left-width: 0px">designation</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:designation</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.designation` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.designation.language</td><td style="border-left-width: 0px">language</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:designation.extension:language</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.designation.language` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.language` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.language` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
In the absence of a language, the resource language applies.</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.designation.use</td><td style="border-left-width: 0px">use</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:designation.extension:use</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.designation.use` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.use` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.use` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If no use is provided, the designation can be assumed to be suitable for general display to a human user.</td></tr><tr><td style="border-right-width: 0px">ValueSet.codeSystem.concept.designation.value</td><td style="border-left-width: 0px">value</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:designation.extension:value</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.designation.value` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.value` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.value` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px; border-bottom-style: none">ValueSet.codeSystem.concept.concept</td><td style="border-left-width: 0px; border-bottom-style: none">concept</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:concept.extension:concept</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td style="border-right-width: 0px; border-top-style: none"/><td style="border-top-style: none; border-left-width: 0px"/><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td style="border-right-width: 0px">Extension.extension:concept</td><td style="border-left-width: 0px"/><td>Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ValueSet|1.0.2</code> to <a href="StructureDefinition-ext-R2-ValueSet.com.import.html">DSTU2: Import the contents of another value set (new)version: 0.1.0)</a></p><table class="grid"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>ValueSet.compose.import (import)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (DSTU2: Import the contents of another value set (new))</td><td>Element `ValueSet.compose.import` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.compose.import` has a context of ValueSet.compose based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.compose.import` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The value set URI is either a logical reference to a defined value set such as a [SNOMED CT reference set]{snomedct.html#implicit}, or a direct reference to a value set definition using ValueSet.url. The reference may also not reference an actual FHIR ValueSet resource; in this case, whatever is referenced is an implicit definition of a value set that needs to be clear about how versions are resolved.</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r2.r4"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R2-ValueSet-element-map-to-R4"/>
<version value="0.1.0"/>
<name value="R2ValueSetElementMapToR4"/>
<title
value="Cross-version mapping for FHIR DSTU2 ValueSet to FHIR R4 CodeSystem"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:02.4283168-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 ValueSet to FHIR R4."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceCanonical value="http://hl7.org/fhir/1.0"/>
<targetUri value="http://hl7.org/fhir/4.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target value="http://hl7.org/fhir/StructureDefinition/CodeSystem"/>
<targetVersion value="4.0.1"/>
<element>
<code value="ValueSet.meta"/>
<display value="meta"/>
<target>
<code value="CodeSystem.meta"/>
<display value="CodeSystem.meta"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
<element>
<code value="ValueSet.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="CodeSystem.implicitRules"/>
<display value="CodeSystem.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.implicitRules` is mapped to FHIR R4 element `CodeSystem.implicitRules` as `Equivalent`.
Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible."/>
</target>
</element>
<element>
<code value="ValueSet.language"/>
<display value="language"/>
<target>
<code value="CodeSystem.language"/>
<display value="CodeSystem.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.language` is mapped to FHIR R4 element `CodeSystem.language` as `Equivalent`.
Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
</target>
</element>
<element>
<code value="ValueSet.text"/>
<display value="text"/>
<target>
<code value="CodeSystem.text"/>
<display value="CodeSystem.text"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/>
</target>
</element>
<element>
<code value="ValueSet.contained"/>
<display value="contained"/>
<target>
<code value="CodeSystem.contained"/>
<display value="CodeSystem.contained"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.contained` is mapped to FHIR R4 element `CodeSystem.contained` as `SourceIsBroaderThanTarget`.
Element `ValueSet.contained` is mapped to FHIR R4 element `ValueSet.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again."/>
</target>
</element>
<element>
<code value="ValueSet.url"/>
<display value="url"/>
<target>
<code value="CodeSystem.url"/>
<display value="CodeSystem.url"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.url` is mapped to FHIR R4 element `CodeSystem.url` as `Equivalent`.
Element `ValueSet.url` is mapped to FHIR R4 element `ValueSet.url` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.identifier"/>
<display value="identifier"/>
<target>
<code value="CodeSystem.identifier"/>
<display value="CodeSystem.identifier"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type."/>
</target>
</element>
<element>
<code value="ValueSet.version"/>
<display value="version"/>
<target>
<code value="CodeSystem.version"/>
<display value="CodeSystem.version"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.version` is mapped to FHIR R4 element `CodeSystem.version` as `Equivalent`.
Element `ValueSet.version` is mapped to FHIR R4 element `ValueSet.version` as `Equivalent`.
There may be multiple resource versions of the value set that have the same identifier."/>
</target>
</element>
<element>
<code value="ValueSet.name"/>
<display value="name"/>
<target>
<code value="CodeSystem.name"/>
<display value="CodeSystem.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.name` is mapped to FHIR R4 element `CodeSystem.name` as `Equivalent`.
Element `ValueSet.name` is mapped to FHIR R4 element `ValueSet.name` as `Equivalent`.
The name is not expected to be unique. A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name."/>
</target>
</element>
<element>
<code value="ValueSet.status"/>
<display value="status"/>
<target>
<code value="CodeSystem.status"/>
<display value="CodeSystem.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.status` is mapped to FHIR R4 element `CodeSystem.status` as `SourceIsNarrowerThanTarget`.
Element `ValueSet.status` is mapped to FHIR R4 element `ValueSet.status` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Allows filtering of value set instances that are appropriate (or not) for use."/>
</target>
</element>
<element>
<code value="ValueSet.experimental"/>
<display value="experimental"/>
<target>
<code value="CodeSystem.experimental"/>
<display value="CodeSystem.experimental"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.experimental` is mapped to FHIR R4 element `CodeSystem.experimental` as `Equivalent`.
Element `ValueSet.experimental` is mapped to FHIR R4 element `ValueSet.experimental` as `Equivalent`.
Allows filtering of value sets that are appropriate for use vs. not."/>
</target>
</element>
<element>
<code value="ValueSet.publisher"/>
<display value="publisher"/>
<target>
<code value="CodeSystem.publisher"/>
<display value="CodeSystem.publisher"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.publisher` is mapped to FHIR R4 element `CodeSystem.publisher` as `Equivalent`.
Element `ValueSet.publisher` is mapped to FHIR R4 element `ValueSet.publisher` as `Equivalent`.
Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context."/>
</target>
</element>
<element>
<code value="ValueSet.contact"/>
<display value="contact"/>
<target>
<code value="CodeSystem.contact"/>
<display value="CodeSystem.contact"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.contact` is mapped to FHIR R4 element `CodeSystem.contact` as `Equivalent`.
Element `ValueSet.contact` is mapped to FHIR R4 element `ValueSet.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc."/>
</target>
</element>
<element>
<code value="ValueSet.date"/>
<display value="date"/>
<target>
<code value="CodeSystem.date"/>
<display value="CodeSystem.date"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.date` is mapped to FHIR R4 element `CodeSystem.date` as `Equivalent`.
Element `ValueSet.date` is mapped to FHIR R4 element `ValueSet.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions."/>
</target>
</element>
<element>
<code value="ValueSet.description"/>
<display value="description"/>
<target>
<code value="CodeSystem.description"/>
<display value="CodeSystem.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.description` is mapped to FHIR R4 element `CodeSystem.description` as `Equivalent`.
Element `ValueSet.description` is mapped to FHIR R4 element `ValueSet.description` as `Equivalent`.
The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description."/>
</target>
</element>
<element>
<code value="ValueSet.useContext"/>
<display value="useContext"/>
<target>
<code value="CodeSystem.useContext"/>
<display value="CodeSystem.useContext"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.copyright"/>
<display value="copyright"/>
<target>
<code value="CodeSystem.copyright"/>
<display value="CodeSystem.copyright"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.copyright` is mapped to FHIR R4 element `CodeSystem.copyright` as `Equivalent`.
Element `ValueSet.copyright` is mapped to FHIR R4 element `ValueSet.copyright` as `Equivalent`.
Frequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<targetVersion value="4.0.1"/>
<element>
<code value="ValueSet.meta"/>
<display value="meta"/>
<target>
<code value="ValueSet.meta"/>
<display value="ValueSet.meta"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
<element>
<code value="ValueSet.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="ValueSet.implicitRules"/>
<display value="ValueSet.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.implicitRules` is mapped to FHIR R4 element `CodeSystem.implicitRules` as `Equivalent`.
Element `ValueSet.implicitRules` is mapped to FHIR R4 element `ValueSet.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible."/>
</target>
</element>
<element>
<code value="ValueSet.language"/>
<display value="language"/>
<target>
<code value="ValueSet.language"/>
<display value="ValueSet.language"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.language` is mapped to FHIR R4 element `CodeSystem.language` as `Equivalent`.
Element `ValueSet.language` is mapped to FHIR R4 element `ValueSet.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
</target>
</element>
<element>
<code value="ValueSet.text"/>
<display value="text"/>
<target>
<code value="ValueSet.text"/>
<display value="ValueSet.text"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/>
</target>
</element>
<element>
<code value="ValueSet.contained"/>
<display value="contained"/>
<target>
<code value="ValueSet.contained"/>
<display value="ValueSet.contained"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.contained` is mapped to FHIR R4 element `CodeSystem.contained` as `SourceIsBroaderThanTarget`.
Element `ValueSet.contained` is mapped to FHIR R4 element `ValueSet.contained` as `SourceIsBroaderThanTarget`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again."/>
</target>
</element>
<element>
<code value="ValueSet.url"/>
<display value="url"/>
<target>
<code value="ValueSet.url"/>
<display value="ValueSet.url"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.url` is mapped to FHIR R4 element `CodeSystem.url` as `Equivalent`.
Element `ValueSet.url` is mapped to FHIR R4 element `ValueSet.url` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.identifier"/>
<display value="identifier"/>
<target>
<code value="ValueSet.identifier"/>
<display value="ValueSet.identifier"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type."/>
</target>
</element>
<element>
<code value="ValueSet.version"/>
<display value="version"/>
<target>
<code value="ValueSet.version"/>
<display value="ValueSet.version"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.version` is mapped to FHIR R4 element `CodeSystem.version` as `Equivalent`.
Element `ValueSet.version` is mapped to FHIR R4 element `ValueSet.version` as `Equivalent`.
There may be multiple resource versions of the value set that have the same identifier."/>
</target>
</element>
<element>
<code value="ValueSet.name"/>
<display value="name"/>
<target>
<code value="ValueSet.name"/>
<display value="ValueSet.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.name` is mapped to FHIR R4 element `CodeSystem.name` as `Equivalent`.
Element `ValueSet.name` is mapped to FHIR R4 element `ValueSet.name` as `Equivalent`.
The name is not expected to be unique. A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name."/>
</target>
</element>
<element>
<code value="ValueSet.status"/>
<display value="status"/>
<target>
<code value="ValueSet.status"/>
<display value="ValueSet.status"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.status` is mapped to FHIR R4 element `CodeSystem.status` as `SourceIsNarrowerThanTarget`.
Element `ValueSet.status` is mapped to FHIR R4 element `ValueSet.status` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.status` do not allow expression of the necessary codes, per the bindings on the source and target.
Allows filtering of value set instances that are appropriate (or not) for use."/>
</target>
</element>
<element>
<code value="ValueSet.experimental"/>
<display value="experimental"/>
<target>
<code value="ValueSet.experimental"/>
<display value="ValueSet.experimental"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.experimental` is mapped to FHIR R4 element `CodeSystem.experimental` as `Equivalent`.
Element `ValueSet.experimental` is mapped to FHIR R4 element `ValueSet.experimental` as `Equivalent`.
Allows filtering of value sets that are appropriate for use vs. not."/>
</target>
</element>
<element>
<code value="ValueSet.publisher"/>
<display value="publisher"/>
<target>
<code value="ValueSet.publisher"/>
<display value="ValueSet.publisher"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.publisher` is mapped to FHIR R4 element `CodeSystem.publisher` as `Equivalent`.
Element `ValueSet.publisher` is mapped to FHIR R4 element `ValueSet.publisher` as `Equivalent`.
Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context."/>
</target>
</element>
<element>
<code value="ValueSet.contact"/>
<display value="contact"/>
<target>
<code value="ValueSet.contact"/>
<display value="ValueSet.contact"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.contact` is mapped to FHIR R4 element `CodeSystem.contact` as `Equivalent`.
Element `ValueSet.contact` is mapped to FHIR R4 element `ValueSet.contact` as `Equivalent`.
May be a web site, an email address, a telephone number, etc."/>
</target>
</element>
<element>
<code value="ValueSet.date"/>
<display value="date"/>
<target>
<code value="ValueSet.date"/>
<display value="ValueSet.date"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.date` is mapped to FHIR R4 element `CodeSystem.date` as `Equivalent`.
Element `ValueSet.date` is mapped to FHIR R4 element `ValueSet.date` as `Equivalent`.
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions."/>
</target>
</element>
<element>
<code value="ValueSet.lockedDate"/>
<display value="lockedDate"/>
<target>
<code value="ValueSet.compose.lockedDate"/>
<display value="ValueSet.compose.lockedDate"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.lockedDate` is mapped to FHIR R4 element `ValueSet.compose.lockedDate` as `Equivalent`.
With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable."/>
</target>
</element>
<element>
<code value="ValueSet.description"/>
<display value="description"/>
<target>
<code value="ValueSet.description"/>
<display value="ValueSet.description"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.description` is mapped to FHIR R4 element `CodeSystem.description` as `Equivalent`.
Element `ValueSet.description` is mapped to FHIR R4 element `ValueSet.description` as `Equivalent`.
The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description."/>
</target>
</element>
<element>
<code value="ValueSet.useContext"/>
<display value="useContext"/>
<target>
<code value="ValueSet.jurisdiction"/>
<display value="ValueSet.jurisdiction"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`."/>
</target>
<target>
<code value="ValueSet.useContext"/>
<display value="ValueSet.useContext"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.useContext` is mapped to FHIR R4 element `CodeSystem.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.useContext` as `SourceIsBroaderThanTarget`.
Element `ValueSet.useContext` is mapped to FHIR R4 element `ValueSet.jurisdiction` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.immutable"/>
<display value="immutable"/>
<target>
<code value="ValueSet.immutable"/>
<display value="ValueSet.immutable"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.immutable` is mapped to FHIR R4 element `ValueSet.immutable` as `Equivalent`.
Normally immutability is set to 'false', which is the default assumption if it is not populated. Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change. For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition."/>
</target>
</element>
<element>
<code value="ValueSet.requirements"/>
<display value="requirements"/>
<target>
<code value="ValueSet.purpose"/>
<display value="ValueSet.purpose"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.requirements` is mapped to FHIR R4 element `ValueSet.purpose` as `Equivalent`.
This element does not describe the usage of the value set (that is done in comments), rather it's for traceability of ''why'' the element is either needed or ''why'' the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this data element."/>
</target>
</element>
<element>
<code value="ValueSet.copyright"/>
<display value="copyright"/>
<target>
<code value="ValueSet.copyright"/>
<display value="ValueSet.copyright"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.copyright` is mapped to FHIR R4 element `CodeSystem.copyright` as `Equivalent`.
Element `ValueSet.copyright` is mapped to FHIR R4 element `ValueSet.copyright` as `Equivalent`.
Frequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required."/>
</target>
</element>
<element>
<code value="ValueSet.compose"/>
<display value="compose"/>
<target>
<code value="ValueSet.compose"/>
<display value="ValueSet.compose"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.compose` is mapped to FHIR R4 element `ValueSet.compose` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include"/>
<display value="include"/>
<target>
<code value="ValueSet.compose.include"/>
<display value="ValueSet.compose.include"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.compose.include` is mapped to FHIR R4 element `ValueSet.compose.include` as `Equivalent`.
If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.system"/>
<display value="system"/>
<target>
<code value="ValueSet.compose.include.system"/>
<display value="ValueSet.compose.include.system"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.system` is mapped to FHIR R4 element `ValueSet.compose.include.system` as `Equivalent`.
See ''Coding.system'' for further documentation."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.version"/>
<display value="version"/>
<target>
<code value="ValueSet.compose.include.version"/>
<display value="ValueSet.compose.include.version"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.version` is mapped to FHIR R4 element `ValueSet.compose.include.version` as `Equivalent`.
This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set may not be known until a context of use binds it to a particular version."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.concept"/>
<display value="concept"/>
<target>
<code value="ValueSet.compose.include.concept"/>
<display value="ValueSet.compose.include.concept"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.compose.include.concept` is mapped to FHIR R4 element `ValueSet.compose.include.concept` as `Equivalent`.
The list of concepts is considered ordered, though the order may not have any particular significance. Typically, the order of an expansion follows that defined in the compose element."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.concept.code"/>
<display value="code"/>
<target>
<code value="ValueSet.compose.include.concept.code"/>
<display value="ValueSet.compose.include.concept.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.concept.code` is mapped to FHIR R4 element `ValueSet.compose.include.concept.code` as `Equivalent`.
Expressions are allowed if defined by the underlying code system."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.concept.display"/>
<display value="display"/>
<target>
<code value="ValueSet.compose.include.concept.display"/>
<display value="ValueSet.compose.include.concept.display"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.concept.display` is mapped to FHIR R4 element `ValueSet.compose.include.concept.display` as `Equivalent`.
The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.concept.designation"/>
<display value="designation"/>
<target>
<code value="ValueSet.compose.include.concept.designation"/>
<display value="ValueSet.compose.include.concept.designation"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.concept.designation` is mapped to FHIR R4 element `ValueSet.compose.include.concept.designation` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.filter"/>
<display value="filter"/>
<target>
<code value="ValueSet.compose.include.filter"/>
<display value="ValueSet.compose.include.filter"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.compose.include.filter` is mapped to FHIR R4 element `ValueSet.compose.include.filter` as `Equivalent`.
Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.filter.property"/>
<display value="property"/>
<target>
<code value="ValueSet.compose.include.filter.property"/>
<display value="ValueSet.compose.include.filter.property"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.filter.property` is mapped to FHIR R4 element `ValueSet.compose.include.filter.property` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.filter.op"/>
<display value="op"/>
<target>
<code value="ValueSet.compose.include.filter.op"/>
<display value="ValueSet.compose.include.filter.op"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.filter.op` is mapped to FHIR R4 element `ValueSet.compose.include.filter.op` as `SourceIsNarrowerThanTarget`.
The mappings for `ValueSet.compose.include.filter.op` do not allow expression of the necessary codes, per the bindings on the source and target."/>
</target>
</element>
<element>
<code value="ValueSet.compose.include.filter.value"/>
<display value="value"/>
<target>
<code value="ValueSet.compose.include.filter.value"/>
<display value="ValueSet.compose.include.filter.value"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.include.filter.value` is mapped to FHIR R4 element `ValueSet.compose.include.filter.value` as `Equivalent`.
Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example."/>
</target>
</element>
<element>
<code value="ValueSet.compose.exclude"/>
<display value="exclude"/>
<target>
<code value="ValueSet.compose.exclude"/>
<display value="ValueSet.compose.exclude"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.compose.exclude` is mapped to FHIR R4 element `ValueSet.compose.exclude` as `Equivalent`.
Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored."/>
</target>
</element>
<element>
<code value="ValueSet.expansion"/>
<display value="expansion"/>
<target>
<code value="ValueSet.expansion"/>
<display value="ValueSet.expansion"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.expansion` is mapped to FHIR R4 element `ValueSet.expansion` as `Equivalent`.
Expansion is performed to produce a collection of codes that are ready to use for data entry or validation."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.identifier"/>
<display value="identifier"/>
<target>
<code value="ValueSet.expansion.identifier"/>
<display value="ValueSet.expansion.identifier"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.identifier` is mapped to FHIR R4 element `ValueSet.expansion.identifier` as `Equivalent`.
Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd)."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.timestamp"/>
<display value="timestamp"/>
<target>
<code value="ValueSet.expansion.timestamp"/>
<display value="ValueSet.expansion.timestamp"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.timestamp` is mapped to FHIR R4 element `ValueSet.expansion.timestamp` as `Equivalent`.
This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.total"/>
<display value="total"/>
<target>
<code value="ValueSet.expansion.total"/>
<display value="ValueSet.expansion.total"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.total` is mapped to FHIR R4 element `ValueSet.expansion.total` as `Equivalent`.
Paging only applies to flat expansions."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.offset"/>
<display value="offset"/>
<target>
<code value="ValueSet.expansion.offset"/>
<display value="ValueSet.expansion.offset"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.offset` is mapped to FHIR R4 element `ValueSet.expansion.offset` as `Equivalent`.
Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.parameter"/>
<display value="parameter"/>
<target>
<code value="ValueSet.expansion.parameter"/>
<display value="ValueSet.expansion.parameter"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.expansion.parameter` is mapped to FHIR R4 element `ValueSet.expansion.parameter` as `Equivalent`.
The server decides which parameters to include here, but at a minimum, the list SHOULD include the date, filter, and profile parameters passed to the $expand operation (if any)."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.parameter.name"/>
<display value="name"/>
<target>
<code value="ValueSet.expansion.parameter.name"/>
<display value="ValueSet.expansion.parameter.name"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.parameter.name` is mapped to FHIR R4 element `ValueSet.expansion.parameter.name` as `Equivalent`.
The names are assigned at the discretion of the server."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.parameter.value[x]"/>
<display value="value[x]"/>
<target>
<code value="ValueSet.expansion.parameter.value[x]"/>
<display value="ValueSet.expansion.parameter.value[x]"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.expansion.parameter.value[x]` is mapped to FHIR R4 element `ValueSet.expansion.parameter.value[x]` as `RelatedTo`.
The target context `ValueSet.expansion.parameter.value[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ValueSet.expansion.parameter`."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains"/>
<display value="contains"/>
<target>
<code value="ValueSet.expansion.contains"/>
<display value="ValueSet.expansion.contains"/>
<equivalence value="relatedto"/>
<comment
value="Element `ValueSet.expansion.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.system"/>
<display value="system"/>
<target>
<code value="ValueSet.expansion.contains.system"/>
<display value="ValueSet.expansion.contains.system"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.system` is mapped to FHIR R4 element `ValueSet.expansion.contains.system` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.abstract"/>
<display value="abstract"/>
<target>
<code value="ValueSet.expansion.contains.abstract"/>
<display value="ValueSet.expansion.contains.abstract"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.abstract` is mapped to FHIR R4 element `ValueSet.expansion.contains.abstract` as `Equivalent`.
This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.version"/>
<display value="version"/>
<target>
<code value="ValueSet.expansion.contains.version"/>
<display value="ValueSet.expansion.contains.version"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.version` is mapped to FHIR R4 element `ValueSet.expansion.contains.version` as `Equivalent`.
The exact value of the version string is specified by the system from which the code is derived."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.code"/>
<display value="code"/>
<target>
<code value="ValueSet.expansion.contains.code"/>
<display value="ValueSet.expansion.contains.code"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.code` is mapped to FHIR R4 element `ValueSet.expansion.contains.code` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.display"/>
<display value="display"/>
<target>
<code value="ValueSet.expansion.contains.display"/>
<display value="ValueSet.expansion.contains.display"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.display` is mapped to FHIR R4 element `ValueSet.expansion.contains.display` as `Equivalent`."/>
</target>
</element>
<element>
<code value="ValueSet.expansion.contains.contains"/>
<display value="contains"/>
<target>
<code value="ValueSet.expansion.contains.contains"/>
<display value="ValueSet.expansion.contains.contains"/>
<equivalence value="equivalent"/>
<comment
value="Element `ValueSet.expansion.contains.contains` is mapped to FHIR R4 element `ValueSet.expansion.contains.contains` as `Equivalent`.
If the expansion uses this element, there is no implication about the logical relationship between them, and the structure cannot be used for logical inferencing. The structure exists to provide navigational assistance for helping human users to locate codes in the expansion."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.meta"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.meta"/>
<display value="meta"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.meta` is mapped to FHIR R4 element `CodeSystem.meta` as `SourceIsBroaderThanTarget`.
Element `ValueSet.meta` is mapped to FHIR R4 element `ValueSet.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.meta` do not cover the following types: Meta.
The mappings for `ValueSet.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.text"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.text"/>
<display value="text"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.text` is mapped to FHIR R4 element `CodeSystem.text` as `SourceIsBroaderThanTarget`.
Element `ValueSet.text` is mapped to FHIR R4 element `ValueSet.text` as `SourceIsBroaderThanTarget`.
The mappings for `ValueSet.text` do not cover the following types: Narrative.
The mappings for `ValueSet.text` do not cover the following types based on type expansion: div, status.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.identifier"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.identifier"/>
<display value="identifier"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.identifier` is mapped to FHIR R4 element `CodeSystem.identifier` as `RelatedTo`.
Element `ValueSet.identifier` is mapped to FHIR R4 element `ValueSet.identifier` as `RelatedTo`.
The mappings for `ValueSet.identifier` do not cover the following types: Identifier.
The mappings for `ValueSet.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
Typically, this is used for values that can go in an HL7 v3 II data type."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.contact.name"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.contact.name"/>
<display value="name"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.contact.name` has a context of CodeSystem.contact based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.contact.name` has a context of ValueSet.contact based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.contact.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If there is no named individual, the telecom is for the organization as a whole."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.contact.telecom"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.contact.telecom"/>
<display value="telecom"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.contact.telecom` has a context of CodeSystem.contact based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.contact.telecom` has a context of ValueSet.contact based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.contact.telecom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.extensible"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.extensible"/>
<display value="extensible"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.extensible` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.extensible` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.extensible` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.codeSystem"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.codeSystem"/>
<display value="codeSystem"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
All code systems defined as part of a FHIR value set have an implicit valueset that includes all of the codes in the code system - the value set in which they are defined."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.system"/>
<display value="system"/>
<target>
<code value="Extension.extension:system"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.system` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.system` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.system` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.system` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The reference is not required to point to any specific kind of definition, but the more information that can be provided, the more useful it is for implementers. Best practice is to resolve to a computable definition of the code system (either a value set, or some other format). Terminology servers MAY validate this reference (e.g. when accepting PUT/POST), and MAY make additional rules about what kind of content it refers to."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.version"/>
<display value="version"/>
<target>
<code value="Extension.extension:version"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.version` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.version` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.version` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.caseSensitive"/>
<display value="caseSensitive"/>
<target>
<code value="Extension.extension:caseSensitive"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.caseSensitive` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.caseSensitive` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.caseSensitive` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.caseSensitive` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case. This element is primarily provided to support validation software."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept"/>
<display value="concept"/>
<target>
<code value="Extension.extension:concept"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.code"/>
<display value="code"/>
<target>
<code value="Extension.extension:concept.extension:code"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.code` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.code` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.code` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.abstract"/>
<display value="abstract"/>
<target>
<code value="Extension.extension:concept.extension:abstract"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.abstract` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.abstract` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.abstract` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.abstract` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.display"/>
<display value="display"/>
<target>
<code value="Extension.extension:concept.extension:display"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.display` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.display` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.display` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.definition"/>
<display value="definition"/>
<target>
<code value="Extension.extension:concept.extension:definition"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.definition` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.definition` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.definition` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation"/>
<display value="designation"/>
<target>
<code value="Extension.extension:concept.extension:designation"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.language"/>
<display value="language"/>
<target>
<code
value="Extension.extension:concept.extension:designation.extension:language"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.language` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.language` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.language` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
In the absence of a language, the resource language applies."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.use"/>
<display value="use"/>
<target>
<code
value="Extension.extension:concept.extension:designation.extension:use"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.use` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.use` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.use` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If no use is provided, the designation can be assumed to be suitable for general display to a human user."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.value"/>
<display value="value"/>
<target>
<code
value="Extension.extension:concept.extension:designation.extension:value"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.value` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.value` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.value` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.concept"/>
<display value="concept"/>
<target>
<code value="Extension.extension:concept.extension:concept"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.codeSystem.concept"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.codeSystem.concept"/>
<display value="concept"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept` is part of an existing definition because parent element `ValueSet.codeSystem` requires a cross-version extension.
Element `ValueSet.codeSystem.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.code"/>
<display value="code"/>
<target>
<code value="Extension.extension:code"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.code` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.code` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.code` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.abstract"/>
<display value="abstract"/>
<target>
<code value="Extension.extension:abstract"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.abstract` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.abstract` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.abstract` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.abstract` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.display"/>
<display value="display"/>
<target>
<code value="Extension.extension:display"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.display` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.display` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.display` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.definition"/>
<display value="definition"/>
<target>
<code value="Extension.extension:definition"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.definition` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.definition` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.definition` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation"/>
<display value="designation"/>
<target>
<code value="Extension.extension:designation"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.language"/>
<display value="language"/>
<target>
<code value="Extension.extension:designation.extension:language"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.language` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.language` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.language` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
In the absence of a language, the resource language applies."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.use"/>
<display value="use"/>
<target>
<code value="Extension.extension:designation.extension:use"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.use` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.use` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.use` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.use` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
If no use is provided, the designation can be assumed to be suitable for general display to a human user."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.designation.value"/>
<display value="value"/>
<target>
<code value="Extension.extension:designation.extension:value"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.designation.value` is part of an existing definition because parent element `ValueSet.codeSystem.concept.designation` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.designation.value` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.designation.value` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.designation.value` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="ValueSet.codeSystem.concept.concept"/>
<display value="concept"/>
<target>
<code value="Extension.extension:concept.extension:concept"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
<target>
<code value="Extension.extension:concept"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.codeSystem.concept.concept` is part of an existing definition because parent element `ValueSet.codeSystem.concept` requires a cross-version extension.
Element `ValueSet.codeSystem.concept.concept` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.codeSystem.concept.concept` has a context of ValueSet based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.codeSystem.concept.concept` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/ValueSet"/>
<sourceVersion value="1.0.2"/>
<target
value="http://hl7.org/fhir/1.0/StructureDefinition/extension-ValueSet.compose.import"/>
<targetVersion value="0.1.0"/>
<element>
<code value="ValueSet.compose.import"/>
<display value="import"/>
<target>
<code value="Extension"/>
<equivalence value="wider"/>
<comment
value="Element `ValueSet.compose.import` has a context of CodeSystem based on following the parent source element upwards and mapping to `CodeSystem`.
Element `ValueSet.compose.import` has a context of ValueSet.compose based on following the parent source element upwards and mapping to `ValueSet`.
Element `ValueSet.compose.import` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The value set URI is either a logical reference to a defined value set such as a [SNOMED CT reference set]{snomedct.html#implicit}, or a direct reference to a value set definition using ValueSet.url. The reference may also not reference an actual FHIR ValueSet resource; in this case, whatever is referenced is an implicit definition of a value set that needs to be clear about how versions are resolved."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r2.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change