Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R4B-TerminologyCapabilities-element-map-to-R3"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4B-TerminologyCapabilities-element-map-to-R3</b></p><a name="R4B-TerminologyCapabilities-element-map-to-R3"> </a><a name="hcR4B-TerminologyCapabilities-element-map-to-R3"> </a><p>Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <code>http://hl7.org/fhir/StructureDefinition/Basic|3.0.2</code></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>TerminologyCapabilities.meta (meta)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Basic.meta</td><td>Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.
Element `TerminologyCapabilities.meta` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.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>Basic.implicitRules</td><td>Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.
Element `TerminologyCapabilities.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.</td></tr><tr><td>TerminologyCapabilities.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>Basic.language</td><td>Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.
Element `TerminologyCapabilities.language` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td>TerminologyCapabilities.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>Basic.text</td><td>Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.
Element `TerminologyCapabilities.text` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.text` has no mapping targets in FHIR STU3. 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 "text blob" or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>TerminologyCapabilities.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>Basic.contained</td><td>Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.
Element `TerminologyCapabilities.contained` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.contained` has no mapping targets in FHIR STU3. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.url.html">R4B: Canonical identifier for this terminology capabilities, represented as a URI (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>TerminologyCapabilities.url (url)</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 (R4B: Canonical identifier for this terminology capabilities, represented as a URI (globally unique) (new))</td><td>Element `TerminologyCapabilities.url` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.url` has no mapping targets in FHIR STU3. 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.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.version.html">R4B: Business version of the terminology capabilities (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>TerminologyCapabilities.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Business version of the terminology capabilities (new))</td><td>Element `TerminologyCapabilities.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
There may be different terminology capabilities instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the terminology capabilities with the format [url]|[version].</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.name.html">R4B: Name for this terminology capabilities (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>TerminologyCapabilities.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: Name for this terminology capabilities (computer friendly) (new))</td><td>Element `TerminologyCapabilities.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.name` has no mapping targets in FHIR STU3. 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 alphanumeric type name to ensure that it is machine-processing friendly.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.title.html">R4B: Name for this terminology capabilities (human 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>TerminologyCapabilities.title (title)</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 (R4B: Name for this terminology capabilities (human friendly) (new))</td><td>Element `TerminologyCapabilities.title` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.status.html">R4B: 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>TerminologyCapabilities.status (status)</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 (R4B: draft | active | retired | unknown (new))</td><td>Element `TerminologyCapabilities.status` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Allows filtering of terminology capabilitiess that are appropriate for use versus not.This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems.</td></tr></table><hr/><p><b>Group 7 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.experimental.html">R4B: 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>TerminologyCapabilities.experimental (experimental)</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 (R4B: For testing purposes, not real usage (new))</td><td>Element `TerminologyCapabilities.experimental` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Allows filtering of terminology capabilitiess that are appropriate for use versus not.</td></tr></table><hr/><p><b>Group 8 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.date.html">R4B: Date 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>TerminologyCapabilities.date (date)</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 (R4B: Date last changed (new))</td><td>Element `TerminologyCapabilities.date` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.date` has no mapping targets in FHIR STU3. 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 terminology capabilities. 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 9 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.publisher.html">R4B: 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>TerminologyCapabilities.publisher (publisher)</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 (R4B: Name of the publisher (organization or individual) (new))</td><td>Element `TerminologyCapabilities.publisher` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.publisher` has no mapping targets in FHIR STU3. 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 terminology capabilities is the organization or individual primarily responsible for the maintenance and upkeep of the terminology capabilities. 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 terminology capabilities. This item SHOULD be populated unless the information is available from context.</td></tr></table><hr/><p><b>Group 10 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.contact.html">R4B: 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>TerminologyCapabilities.contact (contact)</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 (R4B: Contact details for the publisher (new))</td><td>Element `TerminologyCapabilities.contact` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.contact` has no mapping targets in FHIR STU3. 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 11 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.description.html">R4B: Natural language description of the terminology capabilities (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>TerminologyCapabilities.description (description)</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 (R4B: Natural language description of the terminology capabilities (new))</td><td>Element `TerminologyCapabilities.description` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.description` has no mapping targets in FHIR STU3. 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 terminology capabilities 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 terminology capabilities 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 terminology capabilities is presumed to be the predominant language in the place the terminology capabilities was created).This does not need to be populated if the description is adequately implied by the software or implementation details.</td></tr></table><hr/><p><b>Group 12 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.useContext.html">R4B: The context that 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>TerminologyCapabilities.useContext (useContext)</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 (R4B: The context that the content is intended to support (new))</td><td>Element `TerminologyCapabilities.useContext` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.</td></tr></table><hr/><p><b>Group 13 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.jurisdiction.html">R4B: Intended jurisdiction for terminology capabilities (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>TerminologyCapabilities.jurisdiction (jurisdiction)</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 (R4B: Intended jurisdiction for terminology capabilities (if applicable) (new))</td><td>Element `TerminologyCapabilities.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
It may be possible for the terminology capabilities to be used in jurisdictions other than those for which it was originally designed or intended.</td></tr></table><hr/><p><b>Group 14 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.purpose.html">R4B: Why this terminology capabilities is defined (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>TerminologyCapabilities.purpose (purpose)</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 (R4B: Why this terminology capabilities is defined (new))</td><td>Element `TerminologyCapabilities.purpose` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This element does not describe the usage of the terminology capabilities. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this terminology capabilities.</td></tr></table><hr/><p><b>Group 15 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.copyright.html">R4B: Use and/or publishing restrictions (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>TerminologyCapabilities.copyright (copyright)</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 (R4B: Use and/or publishing restrictions (new))</td><td>Element `TerminologyCapabilities.copyright` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 16 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.kind.html">R4B: instance | capability | requirements (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>TerminologyCapabilities.kind (kind)</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 (R4B: instance | capability | requirements (new))</td><td>Element `TerminologyCapabilities.kind` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.kind` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 17 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.software.html">R4B: Software that is covered by this terminology capability statement (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>TerminologyCapabilities.software (software)</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 (R4B: Software that is covered by this terminology capability statement (new))</td><td>Element `TerminologyCapabilities.software` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.software.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:name (R4B: A name the software is known by (new))</td><td>Element `TerminologyCapabilities.software.name` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.
Element `TerminologyCapabilities.software.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.software.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version (R4B: Version covered by this statement (new))</td><td>Element `TerminologyCapabilities.software.version` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.
Element `TerminologyCapabilities.software.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
If possible, a version should be specified, as statements are likely to be different for different versions of software.</td></tr></table><hr/><p><b>Group 18 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.implementation.html">R4B: If this describes a specific instance (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>TerminologyCapabilities.implementation (implementation)</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 (R4B: If this describes a specific instance (new))</td><td>Element `TerminologyCapabilities.implementation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.implementation.description (description)</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:description (R4B: Describes this specific instance (new))</td><td>Element `TerminologyCapabilities.implementation.description` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.
Element `TerminologyCapabilities.implementation.description` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.implementation.url (url)</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:url (R4B: Base URL for the implementation (new))</td><td>Element `TerminologyCapabilities.implementation.url` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.
Element `TerminologyCapabilities.implementation.url` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 19 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.lockedDate.html">R4B: Whether lockedDate is supported (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>TerminologyCapabilities.lockedDate (lockedDate)</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 (R4B: Whether lockedDate is supported (new))</td><td>Element `TerminologyCapabilities.lockedDate` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.lockedDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 20 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.codeSystem.html">R4B: A code system supported by the server (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>TerminologyCapabilities.codeSystem (codeSystem)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R4B: A code system supported by the server (new))</td><td>Element `TerminologyCapabilities.codeSystem` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The code system - identified by its system URL - may also be declared explicitly as a Code System Resource at /CodeSystem, but it might not be.</td></tr><tr><td>TerminologyCapabilities.codeSystem.uri (uri)</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:uri (R4B: URI for the Code System (new))</td><td>Element `TerminologyCapabilities.codeSystem.uri` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.uri` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.uri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version (version)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version (R4B: Version of Code System supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.version` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Language translations might not be available for all codes.</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:code (R4B: Version identifier for this version (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.code` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.isDefault (isDefault)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:isDefault (R4B: If this is the default version for this code system (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.isDefault` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.isDefault` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.isDefault` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.compositional (compositional)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:compositional (R4B: If compositional grammar is supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.compositional` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.compositional` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.compositional` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.language (language)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:language (R4B: Language Displays supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.language` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.language` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.filter (filter)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:filter (R4B: Filter Properties supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.filter` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.filter.code (code)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:filter.extension:code (R4B: Code of the property supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.filter.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter.code` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.filter.op (op)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:filter.extension:op (R4B: Operations supported for the property (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.filter.op` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter.op` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter.op` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.version.property (property)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:version.extension:property (R4B: Properties supported for $lookup (new))</td><td>Element `TerminologyCapabilities.codeSystem.version.property` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.property` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.codeSystem.subsumption (subsumption)</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:subsumption (R4B: Whether subsumption is supported (new))</td><td>Element `TerminologyCapabilities.codeSystem.subsumption` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.subsumption` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.subsumption` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 21 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.expansion.html">R4B: Information about the [ValueSet/$expand](https://hl7.org/fhir/valueset-operation-expand.html) operation (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>TerminologyCapabilities.expansion (expansion)</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 (R4B: Information about the [ValueSet/$expand](https://hl7.org/fhir/valueset-operation-expand.html) operation (new))</td><td>Element `TerminologyCapabilities.expansion` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.hierarchical (hierarchical)</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:hierarchical (R4B: Whether the server can return nested value sets (new))</td><td>Element `TerminologyCapabilities.expansion.hierarchical` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.hierarchical` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.hierarchical` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.paging (paging)</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:paging (R4B: Whether the server supports paging on expansion (new))</td><td>Element `TerminologyCapabilities.expansion.paging` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.paging` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.paging` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.incomplete (incomplete)</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:incomplete (R4B: Allow request for incomplete expansions? (new))</td><td>Element `TerminologyCapabilities.expansion.incomplete` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.incomplete` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.incomplete` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.parameter (parameter)</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:parameter (R4B: Supported expansion parameter (new))</td><td>Element `TerminologyCapabilities.expansion.parameter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.parameter.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:parameter.extension:name (R4B: Expansion Parameter name (new))</td><td>Element `TerminologyCapabilities.expansion.parameter.name` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.parameter.documentation (documentation)</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:parameter.extension:documentation (R4B: Description of support for parameter (new))</td><td>Element `TerminologyCapabilities.expansion.parameter.documentation` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter.documentation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter.documentation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.expansion.textFilter (textFilter)</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:textFilter (R4B: Documentation about text searching works (new))</td><td>Element `TerminologyCapabilities.expansion.textFilter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.textFilter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.textFilter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This documentation should cover things like case sensitivity, use of punctuation if not ignored, what wild cards are supported (if any), whether text is starts with or contains, and whether word order matters.</td></tr></table><hr/><p><b>Group 22 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.codeSearch.html">R4B: explicit | all (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>TerminologyCapabilities.codeSearch (codeSearch)</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 (R4B: explicit | all (new))</td><td>Element `TerminologyCapabilities.codeSearch` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSearch` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
See notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource.</td></tr></table><hr/><p><b>Group 23 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.validateCode.html">R4B: Information about the [ValueSet/$validate-code](https://hl7.org/fhir/valueset-operation-validate-code.html) operation (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>TerminologyCapabilities.validateCode (validateCode)</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 (R4B: Information about the [ValueSet/$validate-code](https://hl7.org/fhir/valueset-operation-validate-code.html) operation (new))</td><td>Element `TerminologyCapabilities.validateCode` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.validateCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.validateCode.translations (translations)</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:translations (R4B: Whether translations are validated (new))</td><td>Element `TerminologyCapabilities.validateCode.translations` is part of an existing definition because parent element `TerminologyCapabilities.validateCode` requires a cross-version extension.
Element `TerminologyCapabilities.validateCode.translations` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.validateCode.translations` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 24 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.translation.html">R4B: Information about the [ConceptMap/$translate](https://hl7.org/fhir/conceptmap-operation-translate.html) operation (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>TerminologyCapabilities.translation (translation)</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 (R4B: Information about the [ConceptMap/$translate](https://hl7.org/fhir/conceptmap-operation-translate.html) operation (new))</td><td>Element `TerminologyCapabilities.translation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.translation.needsMap (needsMap)</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:needsMap (R4B: Whether the client must identify the map (new))</td><td>Element `TerminologyCapabilities.translation.needsMap` is part of an existing definition because parent element `TerminologyCapabilities.translation` requires a cross-version extension.
Element `TerminologyCapabilities.translation.needsMap` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.translation.needsMap` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 25 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.3.0</code> to <a href="StructureDefinition-ext-R4B-TerminologyCapabilities.closure.html">R4B: Information about the [ConceptMap/$closure](https://hl7.org/fhir/conceptmap-operation-closure.html) operation (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>TerminologyCapabilities.closure (closure)</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 (R4B: Information about the [ConceptMap/$closure](https://hl7.org/fhir/conceptmap-operation-closure.html) operation (new))</td><td>Element `TerminologyCapabilities.closure` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.closure` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>TerminologyCapabilities.closure.translation (translation)</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:translation (R4B: If cross-system closure is supported (new))</td><td>Element `TerminologyCapabilities.closure.translation` is part of an existing definition because parent element `TerminologyCapabilities.closure` requires a cross-version extension.
Element `TerminologyCapabilities.closure.translation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.closure.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3"/>
</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">
<valueUri
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R4B-TerminologyCapabilities-element-map-to-R3"/>
<version value="0.1.0"/>
<name value="R4BTerminologyCapabilitiesElementMapToR3"/>
<title
value="Cross-version mapping for FHIR R4B TerminologyCapabilities to FHIR STU3 Basic"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:25.9472802-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 R4B TerminologyCapabilities to FHIR STU3."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceUri value="http://hl7.org/fhir/4.3"/>
<targetUri value="http://hl7.org/fhir/3.0"/>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target value="http://hl7.org/fhir/StructureDefinition/Basic"/>
<targetVersion value="3.0.2"/>
<element>
<code value="TerminologyCapabilities.meta"/>
<display value="meta"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="equivalent"/>
</modifierExtension>
<code value="Basic.meta"/>
<display value="Basic.meta"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.
Element `TerminologyCapabilities.meta` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.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="Basic.implicitRules"/>
<display value="Basic.implicitRules"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.
Element `TerminologyCapabilities.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.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="Basic.language"/>
<display value="Basic.language"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.
Element `TerminologyCapabilities.language` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.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="Basic.text"/>
<display value="Basic.text"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.
Element `TerminologyCapabilities.text` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.text` has no mapping targets in FHIR STU3. 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 "text blob" or where text is additionally entered raw or narrated and encoded information is added later."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.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="Basic.contained"/>
<display value="Basic.contained"/>
<equivalence value="equivalent"/>
<comment
value="Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.
Element `TerminologyCapabilities.contained` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.contained` has no mapping targets in FHIR STU3. 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.url"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.url"/>
<display value="url"/>
<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 `TerminologyCapabilities.url` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.url` has no mapping targets in FHIR STU3. 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.
The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions).
In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.version"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.version"/>
<display value="version"/>
<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 `TerminologyCapabilities.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
There may be different terminology capabilities instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the terminology capabilities with the format [url]|[version]."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.name"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.name"/>
<display value="name"/>
<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 `TerminologyCapabilities.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.name` has no mapping targets in FHIR STU3. 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 alphanumeric type name to ensure that it is machine-processing friendly."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.title"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.title"/>
<display value="title"/>
<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 `TerminologyCapabilities.title` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.status"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.status"/>
<display value="status"/>
<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 `TerminologyCapabilities.status` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Allows filtering of terminology capabilitiess that are appropriate for use versus not.This is not intended for use with actual capability statements, but where capability statements are used to describe possible or desired systems."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.experimental"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.experimental"/>
<display value="experimental"/>
<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 `TerminologyCapabilities.experimental` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Allows filtering of terminology capabilitiess that are appropriate for use versus not."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.date"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.date"/>
<display value="date"/>
<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 `TerminologyCapabilities.date` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.date` has no mapping targets in FHIR STU3. 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 terminology capabilities. 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/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.publisher"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.publisher"/>
<display value="publisher"/>
<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 `TerminologyCapabilities.publisher` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.publisher` has no mapping targets in FHIR STU3. 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 terminology capabilities is the organization or individual primarily responsible for the maintenance and upkeep of the terminology capabilities. 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 terminology capabilities. This item SHOULD be populated unless the information is available from context."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.contact"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.contact"/>
<display value="contact"/>
<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 `TerminologyCapabilities.contact` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.contact` has no mapping targets in FHIR STU3. 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/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.description"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.description"/>
<display value="description"/>
<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 `TerminologyCapabilities.description` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.description` has no mapping targets in FHIR STU3. 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 terminology capabilities 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 terminology capabilities 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 terminology capabilities is presumed to be the predominant language in the place the terminology capabilities was created).This does not need to be populated if the description is adequately implied by the software or implementation details."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.useContext"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.useContext"/>
<display value="useContext"/>
<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 `TerminologyCapabilities.useContext` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
When multiple useContexts are specified, there is no expectation that all or any of the contexts apply."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.jurisdiction"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.jurisdiction"/>
<display value="jurisdiction"/>
<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 `TerminologyCapabilities.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
It may be possible for the terminology capabilities 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/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.purpose"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.purpose"/>
<display value="purpose"/>
<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 `TerminologyCapabilities.purpose` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This element does not describe the usage of the terminology capabilities. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this terminology capabilities."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.copyright"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.copyright"/>
<display value="copyright"/>
<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 `TerminologyCapabilities.copyright` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.kind"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.kind"/>
<display value="kind"/>
<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 `TerminologyCapabilities.kind` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.kind` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.software"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.software"/>
<display value="software"/>
<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 `TerminologyCapabilities.software` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.software.name"/>
<display value="name"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:name"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.software.name` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.
Element `TerminologyCapabilities.software.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.software.version"/>
<display value="version"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.software.version` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.
Element `TerminologyCapabilities.software.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.software.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
If possible, a version should be specified, as statements are likely to be different for different versions of software."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.implementation"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.implementation"/>
<display value="implementation"/>
<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 `TerminologyCapabilities.implementation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.implementation.description"/>
<display value="description"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:description"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.implementation.description` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.
Element `TerminologyCapabilities.implementation.description` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.implementation.url"/>
<display value="url"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:url"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.implementation.url` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.
Element `TerminologyCapabilities.implementation.url` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.implementation.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.lockedDate"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.lockedDate"/>
<display value="lockedDate"/>
<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 `TerminologyCapabilities.lockedDate` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.lockedDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.codeSystem"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.codeSystem"/>
<display value="codeSystem"/>
<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 `TerminologyCapabilities.codeSystem` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
The code system - identified by its system URL - may also be declared explicitly as a Code System Resource at /CodeSystem, but it might not be."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.uri"/>
<display value="uri"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:uri"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.uri` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.uri` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.uri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version"/>
<display value="version"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Language translations might not be available for all codes."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:code"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.code` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.isDefault"/>
<display value="isDefault"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:isDefault"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.isDefault` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.isDefault` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.isDefault` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.compositional"/>
<display value="compositional"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:compositional"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.compositional` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.compositional` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.compositional` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.language"/>
<display value="language"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:language"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.language` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.language` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.filter"/>
<display value="filter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:filter"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.filter` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.filter.code"/>
<display value="code"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code
value="Extension.extension:version.extension:filter.extension:code"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.filter.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter.code` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.filter.op"/>
<display value="op"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code
value="Extension.extension:version.extension:filter.extension:op"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.filter.op` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.filter.op` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.filter.op` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.version.property"/>
<display value="property"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:version.extension:property"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.version.property` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.version.property` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.version.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.codeSystem.subsumption"/>
<display value="subsumption"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:subsumption"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.codeSystem.subsumption` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.
Element `TerminologyCapabilities.codeSystem.subsumption` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSystem.subsumption` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.expansion"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.expansion"/>
<display value="expansion"/>
<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 `TerminologyCapabilities.expansion` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.hierarchical"/>
<display value="hierarchical"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:hierarchical"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.hierarchical` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.hierarchical` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.hierarchical` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.paging"/>
<display value="paging"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:paging"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.paging` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.paging` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.paging` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.incomplete"/>
<display value="incomplete"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:incomplete"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.incomplete` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.incomplete` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.incomplete` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.parameter"/>
<display value="parameter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:parameter"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.parameter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.parameter.name"/>
<display value="name"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:parameter.extension:name"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.parameter.name` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter.name` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code
value="TerminologyCapabilities.expansion.parameter.documentation"/>
<display value="documentation"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:parameter.extension:documentation"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.parameter.documentation` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.parameter.documentation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.parameter.documentation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.expansion.textFilter"/>
<display value="textFilter"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:textFilter"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.expansion.textFilter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.
Element `TerminologyCapabilities.expansion.textFilter` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.expansion.textFilter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
This documentation should cover things like case sensitivity, use of punctuation if not ignored, what wild cards are supported (if any), whether text is starts with or contains, and whether word order matters."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.codeSearch"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.codeSearch"/>
<display value="codeSearch"/>
<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 `TerminologyCapabilities.codeSearch` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.codeSearch` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
See notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.validateCode"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.validateCode"/>
<display value="validateCode"/>
<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 `TerminologyCapabilities.validateCode` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.validateCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.validateCode.translations"/>
<display value="translations"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:translations"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.validateCode.translations` is part of an existing definition because parent element `TerminologyCapabilities.validateCode` requires a cross-version extension.
Element `TerminologyCapabilities.validateCode.translations` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.validateCode.translations` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.translation"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.translation"/>
<display value="translation"/>
<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 `TerminologyCapabilities.translation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.translation.needsMap"/>
<display value="needsMap"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:needsMap"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.translation.needsMap` is part of an existing definition because parent element `TerminologyCapabilities.translation` requires a cross-version extension.
Element `TerminologyCapabilities.translation.needsMap` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.translation.needsMap` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source
value="http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities"/>
<sourceVersion value="4.3.0"/>
<target
value="http://hl7.org/fhir/4.3/StructureDefinition/extension-TerminologyCapabilities.closure"/>
<targetVersion value="0.1.0"/>
<element>
<code value="TerminologyCapabilities.closure"/>
<display value="closure"/>
<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 `TerminologyCapabilities.closure` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.closure` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
<element>
<code value="TerminologyCapabilities.closure.translation"/>
<display value="translation"/>
<target>
<modifierExtension
url="http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence">
<valueCode value="wider"/>
</modifierExtension>
<code value="Extension.extension:translation"/>
<equivalence value="wider"/>
<comment
value="Element `TerminologyCapabilities.closure.translation` is part of an existing definition because parent element `TerminologyCapabilities.closure` requires a cross-version extension.
Element `TerminologyCapabilities.closure.translation` is not mapped to FHIR STU3, since FHIR R4B `TerminologyCapabilities` is not mapped.
Element `TerminologyCapabilities.closure.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change