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

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

: R3ExpansionProfileElementMapToR4B - XML Representation

Page standards status: Trial-use Maturity Level: 0

Raw xml | Download


<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="R3-ExpansionProfile-element-map-to-R4B"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R3-ExpansionProfile-element-map-to-R4B</b></p><a name="R3-ExpansionProfile-element-map-to-R4B"> </a><a name="hcR3-ExpansionProfile-element-map-to-R4B"> </a><p>Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="http://hl7.org/fhir/R4B/parameters.html">Parametersversion: 4.3.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>ExpansionProfile.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>Parameters.meta</td><td>Element `ExpansionProfile.meta` is mapped to FHIR R4B element `Parameters.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ExpansionProfile.meta` do not cover the following types: Meta.
The mappings for `ExpansionProfile.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr><tr><td>ExpansionProfile.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>Parameters.implicitRules</td><td>Element `ExpansionProfile.implicitRules` is mapped to FHIR R4B element `Parameters.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. 

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.</td></tr><tr><td>ExpansionProfile.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>Parameters.language</td><td>Element `ExpansionProfile.language` is mapped to FHIR R4B element `Parameters.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></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.meta.html">STU3: meta 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>ExpansionProfile.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 (STU3: meta additional types)</td><td>Element `ExpansionProfile.meta` is mapped to FHIR R4B element `Parameters.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ExpansionProfile.meta` do not cover the following types: Meta.
The mappings for `ExpansionProfile.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.text.html">STU3: Text summary of the resource, for human interpretation (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>ExpansionProfile.text (text)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Text summary of the resource, for human interpretation (new))</td><td>Element `ExpansionProfile.text` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.text` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.contained.html">STU3: Contained, inline Resources (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>ExpansionProfile.contained (contained)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Contained, inline Resources (new))</td><td>Element `ExpansionProfile.contained` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.contained` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.url.html">STU3: Logical URI to reference this expansion profile (globally unique) (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>ExpansionProfile.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>Extension (STU3: Logical URI to reference this expansion profile (globally unique) (new))</td><td>Element `ExpansionProfile.url` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.url` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred.  Multiple instances may share the same url if they have a distinct version.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.identifier.html">STU3: Additional identifier for the expansion profile (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>ExpansionProfile.identifier (identifier)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Additional identifier for the expansion profile (new))</td><td>Element `ExpansionProfile.identifier` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.identifier` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this expansion profile outside of FHIR, where it is not possible to use the logical URI.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.version.html">STU3: Business version of the expansion profile (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>ExpansionProfile.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>Extension (STU3: Business version of the expansion profile (new))</td><td>Element `ExpansionProfile.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
There may be different expansion profile instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a refrence to a particular business version of the expansion profile with the format [url]|[version].</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.name.html">STU3: Name for this expansion profile (computer friendly) (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>ExpansionProfile.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>Extension (STU3: Name for this expansion profile (computer friendly) (new))</td><td>Element `ExpansionProfile.name` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.name` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.</td></tr></table><hr/><p><b>Group 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.status.html">STU3: draft | active | retired | unknown (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>ExpansionProfile.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>Extension (STU3: draft | active | retired | unknown (new))</td><td>Element `ExpansionProfile.status` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.status` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Allows filtering of expansion profiles that are appropriate for use vs. not.  
This is labeled as &quot;Is Modifier&quot; because applications should not use a retired expansion profile without due consideration.</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.experimental.html">STU3: For testing purposes, not real usage (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>ExpansionProfile.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>Extension (STU3: For testing purposes, not real usage (new))</td><td>Element `ExpansionProfile.experimental` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.experimental` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Allows filtering of expansion profile that are appropriate for use vs. not. This is labeled as &quot;Is Modifier&quot; because applications should not use an experimental expansion profile in production.</td></tr></table><hr/><p><b>Group 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.date.html">STU3: Date this was last changed (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>ExpansionProfile.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>Extension (STU3: Date this was last changed (new))</td><td>Element `ExpansionProfile.date` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.date` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the expansion profile. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.publisher.html">STU3: Name of the publisher (organization or individual) (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>ExpansionProfile.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>Extension (STU3: Name of the publisher (organization or individual) (new))</td><td>Element `ExpansionProfile.publisher` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.publisher` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Usually an organization, but may be an individual. The publisher (or steward) of the expansion profile is the organization or individual primarily responsible for the maintenance and upkeep of the expansion profile. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the expansion profile. This item SHOULD be populated unless the information is available from context.</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.contact.html">STU3: Contact details for the 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>ExpansionProfile.contact (contact)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Contact details for the publisher (new))</td><td>Element `ExpansionProfile.contact` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.contact` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
May be a web site, an email address, a telephone number, etc.</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.description.html">STU3: Natural language description of the expansion profile (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>ExpansionProfile.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>Extension (STU3: Natural language description of the expansion profile (new))</td><td>Element `ExpansionProfile.description` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.description` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This description can be used to capture details such as why the expansion profile was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the expansion profile as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created).</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.useContext.html">STU3: Context the content is intended to support (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>ExpansionProfile.useContext (useContext)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Context the content is intended to support (new))</td><td>Element `ExpansionProfile.useContext` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.useContext` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.</td></tr></table><hr/><p><b>Group 16 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.jurisdiction.html">STU3: Intended jurisdiction for expansion profile (if applicable) (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>ExpansionProfile.jurisdiction (jurisdiction)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Intended jurisdiction for expansion profile (if applicable) (new))</td><td>Element `ExpansionProfile.jurisdiction` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.jurisdiction` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
It may be possible for the expansion profile to be used in jurisdictions other than those for which it was originally designed or intended.</td></tr></table><hr/><p><b>Group 17 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.fixedVersion.html">STU3: Fix use of a code system to a particular version (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>ExpansionProfile.fixedVersion (fixedVersion)</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 (STU3: Fix use of a code system to a particular version (new))</td><td>Element `ExpansionProfile.fixedVersion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ExpansionProfile.fixedVersion.system (system)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:system (STU3: System to have its version fixed (new))</td><td>Element `ExpansionProfile.fixedVersion.system` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.system` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
See ''Coding.system'' for further documentation.</td></tr><tr><td>ExpansionProfile.fixedVersion.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>Extension.extension:version (STU3: Specific version of the code system referred to (new))</td><td>Element `ExpansionProfile.fixedVersion.version` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ExpansionProfile.fixedVersion.mode (mode)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:mode (STU3: default | check | override (new))</td><td>Element `ExpansionProfile.fixedVersion.mode` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.mode` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.mode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 18 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.excludedSystem.html">STU3: Systems/Versions to be exclude (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>ExpansionProfile.excludedSystem (excludedSystem)</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 (STU3: Systems/Versions to be exclude (new))</td><td>Element `ExpansionProfile.excludedSystem` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
When a system is excluded, and this makes a material difference to the expansion, the exclusion SHALL  be noted in the expansion parameters using a parameter 'excluded'.</td></tr><tr><td>ExpansionProfile.excludedSystem.system (system)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:system (STU3: The specific code system to be excluded (new))</td><td>Element `ExpansionProfile.excludedSystem.system` is part of an existing definition because parent element `ExpansionProfile.excludedSystem` requires a cross-version extension.
Element `ExpansionProfile.excludedSystem.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem.system` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
See ''Coding.system'' for further documentation.</td></tr><tr><td>ExpansionProfile.excludedSystem.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>Extension.extension:version (STU3: Specific version of the code system referred to (new))</td><td>Element `ExpansionProfile.excludedSystem.version` is part of an existing definition because parent element `ExpansionProfile.excludedSystem` requires a cross-version extension.
Element `ExpansionProfile.excludedSystem.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This is used to apply version specifc exclusion contraints. If no version is specified, then all codes from the code system present in the expansion (prior to application of the expansion profile) will be excluded.</td></tr></table><hr/><p><b>Group 19 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.includeDesignations.html">STU3: Whether the expansion should include concept designations (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>ExpansionProfile.includeDesignations (includeDesignations)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Whether the expansion should include concept designations (new))</td><td>Element `ExpansionProfile.includeDesignations` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.includeDesignations` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are only evaluated if includeDesignations is present and set to &quot;true&quot;. If includeDesignations is present with a value of &quot;true&quot; and both ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are absent, then all designations are returned in the expansion.</td></tr></table><hr/><p><b>Group 20 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.designation.html">STU3: When the expansion profile imposes designation contraints (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>ExpansionProfile.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 (STU3: When the expansion profile imposes designation contraints (new))</td><td>Element `ExpansionProfile.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ExpansionProfile.designation.include (include)</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:include (STU3: Designations to be included (new))</td><td>Element `ExpansionProfile.designation.include` is part of an existing definition because parent element `ExpansionProfile.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ExpansionProfile.designation.include.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:include.extension:designation (STU3: The designation to be included (new))</td><td>Element `ExpansionProfile.designation.include.designation` is part of an existing definition because parent element `ExpansionProfile.designation.include` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
At least one of designation.language or designation.use must be provided for each include.designation element.</td></tr><tr><td>ExpansionProfile.designation.include.designation.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>Extension.extension:include.extension:designation.extension:language (STU3: Human language of the designation to be included (new))</td><td>Element `ExpansionProfile.designation.include.designation.language` is part of an existing definition because parent element `ExpansionProfile.designation.include.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation.language` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a language, all designations are retained which match the designation.use parameter for this include.designation.</td></tr><tr><td>ExpansionProfile.designation.include.designation.use (use)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:include.extension:designation.extension:use (STU3: What kind of Designation to include (new))</td><td>Element `ExpansionProfile.designation.include.designation.use` is part of an existing definition because parent element `ExpansionProfile.designation.include.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation.use` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation.use` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a use, all designations are retained which match the designation.language parameter for this include.designation element.</td></tr><tr><td>ExpansionProfile.designation.exclude (exclude)</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:exclude (STU3: Designations to be excluded (new))</td><td>Element `ExpansionProfile.designation.exclude` is part of an existing definition because parent element `ExpansionProfile.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>ExpansionProfile.designation.exclude.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:exclude.extension:designation (STU3: The designation to be excluded (new))</td><td>Element `ExpansionProfile.designation.exclude.designation` is part of an existing definition because parent element `ExpansionProfile.designation.exclude` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
At least one of designation.language or designation.use must be provided for each exclude.designation element.</td></tr><tr><td>ExpansionProfile.designation.exclude.designation.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>Extension.extension:exclude.extension:designation.extension:language (STU3: Human language of the designation to be excluded (new))</td><td>Element `ExpansionProfile.designation.exclude.designation.language` is part of an existing definition because parent element `ExpansionProfile.designation.exclude.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation.language` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a language, all designations are excluded which match the designation.use parameter for this exclude.designation element.</td></tr><tr><td>ExpansionProfile.designation.exclude.designation.use (use)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension.extension:exclude.extension:designation.extension:use (STU3: What kind of Designation to exclude (new))</td><td>Element `ExpansionProfile.designation.exclude.designation.use` is part of an existing definition because parent element `ExpansionProfile.designation.exclude.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation.use` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation.use` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a use, all designations are retained which match the designation.language parameter for this exclude.designation element.</td></tr></table><hr/><p><b>Group 21 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.includeDefinition.html">STU3: Include or exclude the value set definition in the expansion (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>ExpansionProfile.includeDefinition (includeDefinition)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Include or exclude the value set definition in the expansion (new))</td><td>Element `ExpansionProfile.includeDefinition` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.includeDefinition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The ValueSet defintion refers to all fields in the ValueSet definition apart from  ValueSet.contains. The definition is only included if includeDefinition is present and has a value of &quot;true&quot;.</td></tr></table><hr/><p><b>Group 22 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.activeOnly.html">STU3: Include or exclude inactive concepts in the expansion (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>ExpansionProfile.activeOnly (activeOnly)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Include or exclude inactive concepts in the expansion (new))</td><td>Element `ExpansionProfile.activeOnly` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.activeOnly` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Inactive codes are included if activeOnly is present and has a value of &quot;true&quot;. Note that if the value set explicitly specifies that inactive codes are included, this property can still remove them from a specific expansion, but this parameter cannot include them if the value set excludes them.</td></tr></table><hr/><p><b>Group 23 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.excludeNested.html">STU3: Nested codes in the expansion or not (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>ExpansionProfile.excludeNested (excludeNested)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Nested codes in the expansion or not (new))</td><td>Element `ExpansionProfile.excludeNested` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludeNested` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Nesting of codes is excluded if excludeNested is present and has a value of &quot;true&quot;.</td></tr></table><hr/><p><b>Group 24 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.excludeNotForUI.html">STU3: Include or exclude codes which cannot be rendered in user interfaces in the value set expansion (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>ExpansionProfile.excludeNotForUI (excludeNotForUI)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Include or exclude codes which cannot be rendered in user interfaces in the value set expansion (new))</td><td>Element `ExpansionProfile.excludeNotForUI` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludeNotForUI` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Codes which cannot be used in user interfaces will be excluded if excludeNotForUI is present and has a value of &quot;true&quot;.</td></tr></table><hr/><p><b>Group 25 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.excludePostCoordinated.html">STU3: Include or exclude codes which are post coordinated expressions in the value set expansion (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>ExpansionProfile.excludePostCoordinated (excludePostCoordinated)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Include or exclude codes which are post coordinated expressions in the value set expansion (new))</td><td>Element `ExpansionProfile.excludePostCoordinated` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludePostCoordinated` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Post coordinated codes are excluded if excludePostCoordinated is present and has a value of &quot;true&quot;.</td></tr></table><hr/><p><b>Group 26 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.displayLanguage.html">STU3: Specify the language for the display element of codes in the value set expansion (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>ExpansionProfile.displayLanguage (displayLanguage)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Specify the language for the display element of codes in the value set expansion (new))</td><td>Element `ExpansionProfile.displayLanguage` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.displayLanguage` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 27 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/ExpansionProfile|3.0.2</code> to <a href="StructureDefinition-ext-R3-ExpansionProfile.limitedExpansion.html">STU3: Controls behaviour of the value set expand operation when value sets are too large to be completely expanded (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>ExpansionProfile.limitedExpansion (limitedExpansion)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (STU3: Controls behaviour of the value set expand operation when value sets are too large to be completely expanded (new))</td><td>Element `ExpansionProfile.limitedExpansion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.limitedExpansion` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This field overides the default behaviour (which is to return an error). This does not apply to expansions which are unbounded. Clients SHALL process the extension [http://hl7.org/fhir/StructureDefinition/valueset-toocostly](https://hl7.org/fhir/extension-valueset-toocostly.html) correctly if limitedExpansion = true.</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-r3.r4b"/>
      </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-r3.r4b"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ConceptMap/R3-ExpansionProfile-element-map-to-R4B"/>
  <version value="0.1.0"/>
  <name value="R3ExpansionProfileElementMapToR4B"/>
  <title
         value="Cross-version mapping for FHIR STU3 ExpansionProfile to FHIR R4B Parameters"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T16:04:10.8008056-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 STU3 ExpansionProfile to FHIR R4B."/>
  <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/3.0"/>
  <targetUri value="http://hl7.org/fhir/4.3"/>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target value="http://hl7.org/fhir/StructureDefinition/Parameters"/>
    <targetVersion value="4.3.0"/>
    <element>
      <code value="ExpansionProfile.meta"/>
      <display value="meta"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Parameters.meta"/>
        <display value="Parameters.meta"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.meta` is mapped to FHIR R4B element `Parameters.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ExpansionProfile.meta` do not cover the following types: Meta.
The mappings for `ExpansionProfile.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.implicitRules"/>
      <display value="implicitRules"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Parameters.implicitRules"/>
        <display value="Parameters.implicitRules"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.implicitRules` is mapped to FHIR R4B element `Parameters.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. 

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.language"/>
      <display value="language"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Parameters.language"/>
        <display value="Parameters.language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.language` is mapped to FHIR R4B element `Parameters.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>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.meta"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.meta"/>
      <display value="meta"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.meta` is mapped to FHIR R4B element `Parameters.meta` as `SourceIsBroaderThanTarget`.
The mappings for `ExpansionProfile.meta` do not cover the following types: Meta.
The mappings for `ExpansionProfile.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/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.text"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.text"/>
      <display value="text"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.text` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.text` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded in formation is added later."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.contained"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.contained"/>
      <display value="contained"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.contained` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.contained` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
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>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.url"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.url"/>
      <display value="url"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.url` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.url` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred.  Multiple instances may share the same url if they have a distinct version."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.identifier"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.identifier"/>
      <display value="identifier"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.identifier` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.identifier` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this expansion profile outside of FHIR, where it is not possible to use the logical URI."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.version"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.version"/>
      <display value="version"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
There may be different expansion profile instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a refrence to a particular business version of the expansion profile with the format [url]|[version]."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.name"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.name"/>
      <display value="name"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.name` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.name` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.status"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.status"/>
      <display value="status"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.status` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.status` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Allows filtering of expansion profiles that are appropriate for use vs. not.  
This is labeled as &quot;Is Modifier&quot; because applications should not use a retired expansion profile without due consideration."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.experimental"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.experimental"/>
      <display value="experimental"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.experimental` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.experimental` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Allows filtering of expansion profile that are appropriate for use vs. not. This is labeled as &quot;Is Modifier&quot; because applications should not use an experimental expansion profile in production."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.date"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.date"/>
      <display value="date"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.date` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.date` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the expansion profile. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.publisher"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.publisher"/>
      <display value="publisher"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.publisher` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.publisher` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Usually an organization, but may be an individual. The publisher (or steward) of the expansion profile is the organization or individual primarily responsible for the maintenance and upkeep of the expansion profile. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the expansion profile. This item SHOULD be populated unless the information is available from context."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.contact"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.contact"/>
      <display value="contact"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.contact` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.contact` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
May be a web site, an email address, a telephone number, etc."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.description"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.description"/>
      <display value="description"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.description` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.description` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This description can be used to capture details such as why the expansion profile was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the expansion profile as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.useContext"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.useContext"/>
      <display value="useContext"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.useContext` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.useContext` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.jurisdiction"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.jurisdiction"/>
      <display value="jurisdiction"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.jurisdiction` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.jurisdiction` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
It may be possible for the expansion profile to be used in jurisdictions other than those for which it was originally designed or intended."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.fixedVersion"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.fixedVersion"/>
      <display value="fixedVersion"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.fixedVersion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.fixedVersion.system"/>
      <display value="system"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:system"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.fixedVersion.system` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.system` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
See ''Coding.system'' for further documentation."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.fixedVersion.version"/>
      <display value="version"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:version"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.fixedVersion.version` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.fixedVersion.mode"/>
      <display value="mode"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:mode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.fixedVersion.mode` is part of an existing definition because parent element `ExpansionProfile.fixedVersion` requires a cross-version extension.
Element `ExpansionProfile.fixedVersion.mode` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.fixedVersion.mode` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.excludedSystem"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.excludedSystem"/>
      <display value="excludedSystem"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.excludedSystem` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
When a system is excluded, and this makes a material difference to the expansion, the exclusion SHALL  be noted in the expansion parameters using a parameter 'excluded'."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.excludedSystem.system"/>
      <display value="system"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:system"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.excludedSystem.system` is part of an existing definition because parent element `ExpansionProfile.excludedSystem` requires a cross-version extension.
Element `ExpansionProfile.excludedSystem.system` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem.system` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
See ''Coding.system'' for further documentation."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.excludedSystem.version"/>
      <display value="version"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension.extension:version"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.excludedSystem.version` is part of an existing definition because parent element `ExpansionProfile.excludedSystem` requires a cross-version extension.
Element `ExpansionProfile.excludedSystem.version` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludedSystem.version` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This is used to apply version specifc exclusion contraints. If no version is specified, then all codes from the code system present in the expansion (prior to application of the expansion profile) will be excluded."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.includeDesignations"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.includeDesignations"/>
      <display value="includeDesignations"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.includeDesignations` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.includeDesignations` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are only evaluated if includeDesignations is present and set to &quot;true&quot;. If includeDesignations is present with a value of &quot;true&quot; and both ExpansionProfile.designation.include and ExpansionProfile.designation.exclude are absent, then all designations are returned in the expansion."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.designation"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.designation"/>
      <display value="designation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.include"/>
      <display value="include"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:include"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.designation.include` is part of an existing definition because parent element `ExpansionProfile.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.include.designation"/>
      <display value="designation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:include.extension:designation"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.designation.include.designation` is part of an existing definition because parent element `ExpansionProfile.designation.include` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
At least one of designation.language or designation.use must be provided for each include.designation element."/>
      </target>
    </element>
    <element>
      <code
            value="ExpansionProfile.designation.include.designation.language"/>
      <display value="language"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="Extension.extension:include.extension:designation.extension:language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.designation.include.designation.language` is part of an existing definition because parent element `ExpansionProfile.designation.include.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation.language` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a language, all designations are retained which match the designation.use parameter for this include.designation."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.include.designation.use"/>
      <display value="use"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="Extension.extension:include.extension:designation.extension:use"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.designation.include.designation.use` is part of an existing definition because parent element `ExpansionProfile.designation.include.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.include.designation.use` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.include.designation.use` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a use, all designations are retained which match the designation.language parameter for this include.designation element."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.exclude"/>
      <display value="exclude"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:exclude"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.designation.exclude` is part of an existing definition because parent element `ExpansionProfile.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.exclude.designation"/>
      <display value="designation"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="wider"/>
        </modifierExtension>
        <code value="Extension.extension:exclude.extension:designation"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `ExpansionProfile.designation.exclude.designation` is part of an existing definition because parent element `ExpansionProfile.designation.exclude` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
At least one of designation.language or designation.use must be provided for each exclude.designation element."/>
      </target>
    </element>
    <element>
      <code
            value="ExpansionProfile.designation.exclude.designation.language"/>
      <display value="language"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="Extension.extension:exclude.extension:designation.extension:language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.designation.exclude.designation.language` is part of an existing definition because parent element `ExpansionProfile.designation.exclude.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation.language` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation.language` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a language, all designations are excluded which match the designation.use parameter for this exclude.designation element."/>
      </target>
    </element>
    <element>
      <code value="ExpansionProfile.designation.exclude.designation.use"/>
      <display value="use"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code
              value="Extension.extension:exclude.extension:designation.extension:use"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.designation.exclude.designation.use` is part of an existing definition because parent element `ExpansionProfile.designation.exclude.designation` requires a cross-version extension.
Element `ExpansionProfile.designation.exclude.designation.use` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.designation.exclude.designation.use` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
In the absence of a use, all designations are retained which match the designation.language parameter for this exclude.designation element."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.includeDefinition"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.includeDefinition"/>
      <display value="includeDefinition"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.includeDefinition` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.includeDefinition` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
The ValueSet defintion refers to all fields in the ValueSet definition apart from  ValueSet.contains. The definition is only included if includeDefinition is present and has a value of &quot;true&quot;."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.activeOnly"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.activeOnly"/>
      <display value="activeOnly"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.activeOnly` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.activeOnly` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Inactive codes are included if activeOnly is present and has a value of &quot;true&quot;. Note that if the value set explicitly specifies that inactive codes are included, this property can still remove them from a specific expansion, but this parameter cannot include them if the value set excludes them."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.excludeNested"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.excludeNested"/>
      <display value="excludeNested"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.excludeNested` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludeNested` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Nesting of codes is excluded if excludeNested is present and has a value of &quot;true&quot;."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.excludeNotForUI"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.excludeNotForUI"/>
      <display value="excludeNotForUI"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.excludeNotForUI` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludeNotForUI` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Codes which cannot be used in user interfaces will be excluded if excludeNotForUI is present and has a value of &quot;true&quot;."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.excludePostCoordinated"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.excludePostCoordinated"/>
      <display value="excludePostCoordinated"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.excludePostCoordinated` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.excludePostCoordinated` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
Post coordinated codes are excluded if excludePostCoordinated is present and has a value of &quot;true&quot;."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.displayLanguage"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.displayLanguage"/>
      <display value="displayLanguage"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.displayLanguage` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.displayLanguage` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/ExpansionProfile"/>
    <sourceVersion value="3.0.2"/>
    <target
            value="http://hl7.org/fhir/3.0/StructureDefinition/extension-ExpansionProfile.limitedExpansion"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="ExpansionProfile.limitedExpansion"/>
      <display value="limitedExpansion"/>
      <target>
        <modifierExtension
                           url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
          <valueCode value="equivalent"/>
        </modifierExtension>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `ExpansionProfile.limitedExpansion` has a context of Parameters based on following the parent source element upwards and mapping to `Parameters`.
Element `ExpansionProfile.limitedExpansion` has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
This field overides the default behaviour (which is to return an error). This does not apply to expansions which are unbounded. Clients SHALL process the extension [http://hl7.org/fhir/StructureDefinition/valueset-toocostly](https://hl7.org/fhir/extension-valueset-toocostly.html) correctly if limitedExpansion = true."/>
      </target>
    </element>
  </group>
</ConceptMap>