FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r3
Resource TypeConceptMap
IdConceptMap-R5-TerminologyCapabilities-element-map-to-R3.json
FHIR VersionR3
Sourcehttp://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-TerminologyCapabilities-element-map-to-R3.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-TerminologyCapabilities-element-map-to-R3
Version0.1.0
Statusactive
Date2026-03-17T16:05:22.4283638-05:00
NameR5TerminologyCapabilitiesElementMapToR3
TitleCross-version mapping for FHIR R5 TerminologyCapabilities to FHIR STU3 Basic
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 TerminologyCapabilities to FHIR STU3.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.closureR5: Information about the [ConceptMap/$closure](https://hl7.org/fhir/conceptmap-operation-closure.html) operation (new)
hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2extension-TerminologyCapabilities.codeSearchCross-version Extension for R5.TerminologyCapabilities.codeSearch for use in FHIR R4
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.codeSystemR5: A code system supported by the server (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.contactR5: Contact details for the publisher (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.copyrightR5: Use and/or publishing restrictions (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.dateR5: Date last changed (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.descriptionR5: Natural language description of the terminology capabilities (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.expansionR5: Information about the [ValueSet/$expand](https://hl7.org/fhir/valueset-operation-expand.html) operation (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.experimentalR5: For testing purposes, not real usage (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.implementationR5: If this describes a specific instance (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.jurisdictionR5: Intended jurisdiction for terminology capabilities (if applicable) (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.kindR5: instance | capability | requirements (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.lockedDateR5: Whether lockedDate is supported (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.nameR5: Name for this terminology capabilities (computer friendly) (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.publisherR5: Name of the publisher/steward (organization or individual) (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.purposeR5: Why this terminology capabilities is defined (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.softwareR5: Software that is covered by this terminology capability statement (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.statusR5: draft | active | retired | unknown (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.titleR5: Name for this terminology capabilities (human friendly) (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.translationR5: Information about the [ConceptMap/$translate](https://hl7.org/fhir/conceptmap-operation-translate.html) operation (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.urlR5: Canonical identifier for this terminology capabilities, represented as a URI (globally unique) (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.useContextR5: The context that the content is intended to support (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.validateCodeR5: Information about the [ValueSet/$validate-code](https://hl7.org/fhir/valueset-operation-validate-code.html) operation (new)
hl7.fhir.uv.xver-r5.r3#0.1.0extension-TerminologyCapabilities.versionR5: Business version of the terminology capabilities (new)

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R5-TerminologyCapabilities-element-map-to-R3

Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.meta (meta)is equivalent toBasic.metaElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `TerminologyCapabilities.meta` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.implicitRules (implicitRules)is equivalent toBasic.implicitRulesElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `TerminologyCapabilities.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `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 its narrative along with other profiles, value sets, etc.
TerminologyCapabilities.language (language)is equivalent toBasic.languageElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `TerminologyCapabilities.language` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.text (text)is equivalent toBasic.textElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `TerminologyCapabilities.text` is not mapped to FHIR STU3, since FHIR R5 `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 a 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.
TerminologyCapabilities.contained (contained)is equivalent toBasic.containedElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `TerminologyCapabilities.contained` is not mapped to FHIR STU3, since FHIR R5 `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.
TerminologyCapabilities.identifier (identifier)is equivalent toBasic.identifierElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `TerminologyCapabilities.identifier` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped. Element `TerminologyCapabilities.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element `TerminologyCapabilities.identifier`: `http://hl7.org/fhir/StructureDefinition/artifact-identifier`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this terminology capabilities outside of FHIR, where it is not possible to use the logical URI.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Canonical identifier for this terminology capabilities, represented as a URI (globally unique) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.url (url)maps to wider conceptExtension (R5: Canonical identifier for this terminology capabilities, represented as a URI (globally unique) (new))Element `TerminologyCapabilities.url` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Business version of the terminology capabilities (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.version (version)maps to wider conceptExtension (R5: Business version of the terminology capabilities (new))Element `TerminologyCapabilities.version` is not mapped to FHIR STU3, since FHIR R5 `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]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Name for this terminology capabilities (computer friendly) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.name (name)maps to wider conceptExtension (R5: Name for this terminology capabilities (computer friendly) (new))Element `TerminologyCapabilities.name` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Name for this terminology capabilities (human friendly) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.title (title)maps to wider conceptExtension (R5: Name for this terminology capabilities (human friendly) (new))Element `TerminologyCapabilities.title` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: draft | active | retired | unknown (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.status (status)maps to wider conceptExtension (R5: draft | active | retired | unknown (new))Element `TerminologyCapabilities.status` is not mapped to FHIR STU3, since FHIR R5 `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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: For testing purposes, not real usage (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.experimental (experimental)maps to wider conceptExtension (R5: For testing purposes, not real usage (new))Element `TerminologyCapabilities.experimental` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Date last changed (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.date (date)maps to wider conceptExtension (R5: Date last changed (new))Element `TerminologyCapabilities.date` is not mapped to FHIR STU3, since FHIR R5 `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). The date is often not tracked until the resource is published, but may be present on draft content. 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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Name of the publisher/steward (organization or individual) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.publisher (publisher)maps to wider conceptExtension (R5: Name of the publisher/steward (organization or individual) (new))Element `TerminologyCapabilities.publisher` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Contact details for the publisher (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.contact (contact)maps to wider conceptExtension (R5: Contact details for the publisher (new))Element `TerminologyCapabilities.contact` is not mapped to FHIR STU3, since FHIR R5 `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. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Natural language description of the terminology capabilities (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.description (description)maps to wider conceptExtension (R5: Natural language description of the terminology capabilities (new))Element `TerminologyCapabilities.description` is not mapped to FHIR STU3, since FHIR R5 `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 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.

Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: The context that the content is intended to support (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.useContext (useContext)maps to wider conceptExtension (R5: The context that the content is intended to support (new))Element `TerminologyCapabilities.useContext` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Intended jurisdiction for terminology capabilities (if applicable) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.jurisdiction (jurisdiction)maps to wider conceptExtension (R5: Intended jurisdiction for terminology capabilities (if applicable) (new))Element `TerminologyCapabilities.jurisdiction` is not mapped to FHIR STU3, since FHIR R5 `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). Element `TerminologyCapabilities.jurisdiction` has been flagged as deprecated. It may be possible for the terminology capabilities to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Why this terminology capabilities is defined (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.purpose (purpose)maps to wider conceptExtension (R5: Why this terminology capabilities is defined (new))Element `TerminologyCapabilities.purpose` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Use and/or publishing restrictions (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.copyright (copyright)maps to wider conceptExtension (R5: Use and/or publishing restrictions (new))Element `TerminologyCapabilities.copyright` is not mapped to FHIR STU3, since FHIR R5 `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).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: instance | capability | requirements (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.kind (kind)maps to wider conceptExtension (R5: instance | capability | requirements (new))Element `TerminologyCapabilities.kind` is not mapped to FHIR STU3, since FHIR R5 `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).

Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Software that is covered by this terminology capability statement (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.software (software)maps to wider conceptExtension (R5: Software that is covered by this terminology capability statement (new))Element `TerminologyCapabilities.software` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.software.name (name)maps to wider conceptExtension.extension:name (R5: A name the software is known by (new))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 R5 `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).
TerminologyCapabilities.software.version (version)maps to wider conceptExtension.extension:version (R5: Version covered by this statement (new))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 R5 `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.

Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: If this describes a specific instance (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.implementation (implementation)maps to wider conceptExtension (R5: If this describes a specific instance (new))Element `TerminologyCapabilities.implementation` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.implementation.description (description)maps to wider conceptExtension.extension:description (R5: Describes this specific instance (new))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 R5 `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).
TerminologyCapabilities.implementation.url (url)maps to wider conceptExtension.extension:url (R5: Base URL for the implementation (new))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 R5 `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).

Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Whether lockedDate is supported (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.lockedDate (lockedDate)maps to wider conceptExtension (R5: Whether lockedDate is supported (new))Element `TerminologyCapabilities.lockedDate` is not mapped to FHIR STU3, since FHIR R5 `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).

Group 20 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: A code system supported by the server (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.codeSystem (codeSystem)maps to wider conceptExtension (R5: A code system supported by the server (new))Element `TerminologyCapabilities.codeSystem` is not mapped to FHIR STU3, since FHIR R5 `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.
TerminologyCapabilities.codeSystem.uri (uri)maps to wider conceptExtension.extension:uri (R5: Canonical identifier for the code system, represented as a URI (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version (version)maps to wider conceptExtension.extension:version (R5: Version of Code System supported (new))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 R5 `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.
TerminologyCapabilities.codeSystem.version.code (code)maps to wider conceptExtension.extension:version.extension:code (R5: Version identifier for this version (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.isDefault (isDefault)maps to wider conceptExtension.extension:version.extension:isDefault (R5: If this is the default version for this code system (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.compositional (compositional)maps to wider conceptExtension.extension:version.extension:compositional (R5: If compositional grammar is supported (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.language (language)maps to wider conceptExtension.extension:version.extension:language (R5: Language Displays supported (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.filter (filter)maps to wider conceptExtension.extension:version.extension:filter (R5: Filter Properties supported (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.filter.code (code)maps to wider conceptExtension.extension:version.extension:filter.extension:code (R5: Code of the property supported (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.filter.op (op)maps to wider conceptExtension.extension:version.extension:filter.extension:op (R5: Operations supported for the property (new))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 R5 `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).
TerminologyCapabilities.codeSystem.version.property (property)maps to wider conceptExtension.extension:version.extension:property (R5: Properties supported for $lookup (new))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 R5 `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).
TerminologyCapabilities.codeSystem.content (content)maps to wider conceptExtension.extension:content (R5: not-present | example | fragment | complete | supplement (new))Element `TerminologyCapabilities.codeSystem.content` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension. Element `TerminologyCapabilities.codeSystem.content` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped. Element `TerminologyCapabilities.codeSystem.content` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
TerminologyCapabilities.codeSystem.subsumption (subsumption)maps to wider conceptExtension.extension:subsumption (R5: Whether subsumption is supported (new))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 R5 `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).

Group 21 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Information about the [ValueSet/$expand](https://hl7.org/fhir/valueset-operation-expand.html) operation (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.expansion (expansion)maps to wider conceptExtension (R5: Information about the [ValueSet/$expand](https://hl7.org/fhir/valueset-operation-expand.html) operation (new))Element `TerminologyCapabilities.expansion` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.expansion.hierarchical (hierarchical)maps to wider conceptExtension.extension:hierarchical (R5: Whether the server can return nested value sets (new))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 R5 `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).
TerminologyCapabilities.expansion.paging (paging)maps to wider conceptExtension.extension:paging (R5: Whether the server supports paging on expansion (new))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 R5 `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).
TerminologyCapabilities.expansion.incomplete (incomplete)maps to wider conceptExtension.extension:incomplete (R5: Allow request for incomplete expansions? (new))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 R5 `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).
TerminologyCapabilities.expansion.parameter (parameter)maps to wider conceptExtension.extension:parameter (R5: Supported expansion parameter (new))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 R5 `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).
TerminologyCapabilities.expansion.parameter.name (name)maps to wider conceptExtension.extension:parameter.extension:name (R5: Name of the supported expansion parameter (new))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 R5 `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).
TerminologyCapabilities.expansion.parameter.documentation (documentation)maps to wider conceptExtension.extension:parameter.extension:documentation (R5: Description of support for parameter (new))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 R5 `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).
TerminologyCapabilities.expansion.textFilter (textFilter)maps to wider conceptExtension.extension:textFilter (R5: Documentation about text searching works (new))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 R5 `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.

Group 22 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: in-compose | in-expansion | in-compose-or-expansion (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.codeSearch (codeSearch)maps to wider conceptExtension (R5: in-compose | in-expansion | in-compose-or-expansion (new))Element `TerminologyCapabilities.codeSearch` is not mapped to FHIR STU3, since FHIR R5 `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.

Group 23 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Information about the [ValueSet/$validate-code](https://hl7.org/fhir/valueset-operation-validate-code.html) operation (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.validateCode (validateCode)maps to wider conceptExtension (R5: Information about the [ValueSet/$validate-code](https://hl7.org/fhir/valueset-operation-validate-code.html) operation (new))Element `TerminologyCapabilities.validateCode` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.validateCode.translations (translations)maps to wider conceptExtension.extension:translations (R5: Whether translations are validated (new))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 R5 `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).

Group 24 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Information about the [ConceptMap/$translate](https://hl7.org/fhir/conceptmap-operation-translate.html) operation (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.translation (translation)maps to wider conceptExtension (R5: Information about the [ConceptMap/$translate](https://hl7.org/fhir/conceptmap-operation-translate.html) operation (new))Element `TerminologyCapabilities.translation` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.translation.needsMap (needsMap)maps to wider conceptExtension.extension:needsMap (R5: Whether the client must identify the map (new))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 R5 `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).

Group 25 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: Information about the [ConceptMap/$closure](https://hl7.org/fhir/conceptmap-operation-closure.html) operation (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.closure (closure)maps to wider conceptExtension (R5: Information about the [ConceptMap/$closure](https://hl7.org/fhir/conceptmap-operation-closure.html) operation (new))Element `TerminologyCapabilities.closure` is not mapped to FHIR STU3, since FHIR R5 `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).
TerminologyCapabilities.closure.translation (translation)maps to wider conceptExtension.extension:translation (R5: If cross-system closure is supported (new))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 R5 `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).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-TerminologyCapabilities-element-map-to-R3",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-TerminologyCapabilities-element-map-to-R3",
  "version": "0.1.0",
  "name": "R5TerminologyCapabilitiesElementMapToR3",
  "title": "Cross-version mapping for FHIR R5 TerminologyCapabilities to FHIR STU3 Basic",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:05:22.4283638-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 TerminologyCapabilities to FHIR STU3.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceUri": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/3.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Basic",
      "targetVersion": "3.0.2",
      "element": [
        {
          "code": "TerminologyCapabilities.meta",
          "display": "meta",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.meta",
              "display": "Basic.meta",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `TerminologyCapabilities.meta` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.implicitRules",
              "display": "Basic.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `TerminologyCapabilities.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAsserting 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 its narrative along with other profiles, value sets, etc."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.language",
          "display": "language",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.language",
              "display": "Basic.language",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `TerminologyCapabilities.language` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nLanguage 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)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.text",
          "display": "text",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.text",
              "display": "Basic.text",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `TerminologyCapabilities.text` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nContained resources do not have a 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."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.contained",
          "display": "contained",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.contained",
              "display": "Basic.contained",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `TerminologyCapabilities.contained` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.identifier",
          "display": "identifier",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "equivalent"
                }
              ],
              "code": "Basic.identifier",
              "display": "Basic.identifier",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `TerminologyCapabilities.identifier` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAn externally-defined extension that has been mapped as the representation of FHIR R5 element `TerminologyCapabilities.identifier`: `http://hl7.org/fhir/StructureDefinition/artifact-identifier`.\nTypically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this terminology capabilities outside of FHIR, where it is not possible to use the logical URI."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.url",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.url",
          "display": "url",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.url` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nCan 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.\n\nThe 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). \n\nIn 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.version",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.version",
          "display": "version",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.version` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThere 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]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.name",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.name",
          "display": "name",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.name` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.title",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.title",
          "display": "title",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.title` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.status",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.status",
          "display": "status",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.status` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAllows 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.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.experimental",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.experimental",
          "display": "experimental",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.experimental` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nAllows filtering of terminology capabilitiess that are appropriate for use versus not."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.date",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.date",
          "display": "date",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.date` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe date is often not tracked until the resource is published, but may be present on draft content. 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.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.publisher",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.publisher",
          "display": "publisher",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.publisher` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.publisher` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nUsually 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.contact",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.contact",
          "display": "contact",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.contact` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.contact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nMay be a web site, an email address, a telephone number, etc.\n\nSee guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.description",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.description",
          "display": "description",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.description` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis description can be used to capture details such as 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.useContext",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.useContext",
          "display": "useContext",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.useContext` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nWhen multiple useContexts are specified, there is no expectation that all or any of the contexts apply."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.jurisdiction",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.jurisdiction` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nElement `TerminologyCapabilities.jurisdiction` has been flagged as deprecated.\nIt may be possible for the terminology capabilities to be used in jurisdictions other than those for which it was originally designed or intended.\n\nDEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element.  (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)"
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.purpose",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.purpose",
          "display": "purpose",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.purpose` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.copyright",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.copyright",
          "display": "copyright",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.copyright` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.kind",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.kind",
          "display": "kind",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.kind` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.kind` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.software",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.software",
          "display": "software",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.software` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.software` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.software.name",
          "display": "name",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:name",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.software.name` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.\nElement `TerminologyCapabilities.software.name` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.software.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.software.version",
          "display": "version",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.software.version` is part of an existing definition because parent element `TerminologyCapabilities.software` requires a cross-version extension.\nElement `TerminologyCapabilities.software.version` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.software.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nIf possible, a version should be specified, as statements are likely to be different for different versions of software."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.implementation",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.implementation",
          "display": "implementation",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.implementation` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.implementation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.implementation.description",
          "display": "description",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:description",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.implementation.description` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.\nElement `TerminologyCapabilities.implementation.description` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.implementation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.implementation.url",
          "display": "url",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:url",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.implementation.url` is part of an existing definition because parent element `TerminologyCapabilities.implementation` requires a cross-version extension.\nElement `TerminologyCapabilities.implementation.url` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.implementation.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.lockedDate",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.lockedDate",
          "display": "lockedDate",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.lockedDate` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.lockedDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.codeSystem",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.codeSystem",
          "display": "codeSystem",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe code system - identified by its system URL - may also be declared explicitly as a Code System Resource at /CodeSystem, but it might not be."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.uri",
          "display": "uri",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:uri",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.uri` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.uri` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.uri` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version",
          "display": "version",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nLanguage translations might not be available for all codes."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.code",
          "display": "code",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:code",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.code` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.isDefault",
          "display": "isDefault",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:isDefault",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.isDefault` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.isDefault` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.isDefault` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.compositional",
          "display": "compositional",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:compositional",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.compositional` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.compositional` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.compositional` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.language",
          "display": "language",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:language",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.language` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.language` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.filter",
          "display": "filter",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:filter",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.filter` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.filter` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.filter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.filter.code",
          "display": "code",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:filter.extension:code",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.filter.code` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.filter.code` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `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)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.filter.op",
          "display": "op",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:filter.extension:op",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.filter.op` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version.filter` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.filter.op` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `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)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.version.property",
          "display": "property",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:version.extension:property",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.version.property` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem.version` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.version.property` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.version.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.content",
          "display": "content",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:content",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.content` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.content` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.content` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.codeSystem.subsumption",
          "display": "subsumption",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:subsumption",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSystem.subsumption` is part of an existing definition because parent element `TerminologyCapabilities.codeSystem` requires a cross-version extension.\nElement `TerminologyCapabilities.codeSystem.subsumption` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSystem.subsumption` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.expansion",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.expansion",
          "display": "expansion",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.hierarchical",
          "display": "hierarchical",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:hierarchical",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.hierarchical` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.hierarchical` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.hierarchical` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.paging",
          "display": "paging",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:paging",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.paging` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.paging` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.paging` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.incomplete",
          "display": "incomplete",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:incomplete",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.incomplete` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.incomplete` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.incomplete` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.parameter",
          "display": "parameter",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:parameter",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.parameter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.parameter` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.parameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.parameter.name",
          "display": "name",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:parameter.extension:name",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.parameter.name` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.parameter.name` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.parameter.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.parameter.documentation",
          "display": "documentation",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:parameter.extension:documentation",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.parameter.documentation` is part of an existing definition because parent element `TerminologyCapabilities.expansion.parameter` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.parameter.documentation` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.parameter.documentation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.expansion.textFilter",
          "display": "textFilter",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:textFilter",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.expansion.textFilter` is part of an existing definition because parent element `TerminologyCapabilities.expansion` requires a cross-version extension.\nElement `TerminologyCapabilities.expansion.textFilter` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.expansion.textFilter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThis 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.codeSearch",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.codeSearch",
          "display": "codeSearch",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.codeSearch` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.codeSearch` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nSee notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.validateCode",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.validateCode",
          "display": "validateCode",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.validateCode` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.validateCode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.validateCode.translations",
          "display": "translations",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:translations",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.validateCode.translations` is part of an existing definition because parent element `TerminologyCapabilities.validateCode` requires a cross-version extension.\nElement `TerminologyCapabilities.validateCode.translations` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.validateCode.translations` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.translation",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.translation",
          "display": "translation",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.translation` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.translation.needsMap",
          "display": "needsMap",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:needsMap",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.translation.needsMap` is part of an existing definition because parent element `TerminologyCapabilities.translation` requires a cross-version extension.\nElement `TerminologyCapabilities.translation.needsMap` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.translation.needsMap` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.closure",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "TerminologyCapabilities.closure",
          "display": "closure",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.closure` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.closure` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "TerminologyCapabilities.closure.translation",
          "display": "translation",
          "target": [
            {
              "modifierExtension": [
                {
                  "url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
                  "valueCode": "wider"
                }
              ],
              "code": "Extension.extension:translation",
              "equivalence": "wider",
              "comment": "Element `TerminologyCapabilities.closure.translation` is part of an existing definition because parent element `TerminologyCapabilities.closure` requires a cross-version extension.\nElement `TerminologyCapabilities.closure.translation` is not mapped to FHIR STU3, since FHIR R5 `TerminologyCapabilities` is not mapped.\nElement `TerminologyCapabilities.closure.translation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}