R5-TerminologyCapabilities-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-TerminologyCapabilities-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-TerminologyCapabilities-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to TerminologyCapabilitiesversion: 4.0.1) Source Code Relationship Target Code Comment TerminologyCapabilities.meta (meta) is equivalent to TerminologyCapabilities.meta Element `TerminologyCapabilities.meta` is mapped to FHIR R4 element `TerminologyCapabilities.meta` as `Equivalent`. TerminologyCapabilities.implicitRules (implicitRules) is equivalent to TerminologyCapabilities.implicitRules Element `TerminologyCapabilities.implicitRules` is mapped to FHIR R4 element `TerminologyCapabilities.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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 to TerminologyCapabilities.language Element `TerminologyCapabilities.language` is mapped to FHIR R4 element `TerminologyCapabilities.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to th…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-TerminologyCapabilities-element-map-to-R4
  l: R5-TerminologyCapabilities-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5TerminologyCapabilitiesElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 TerminologyCapabilities to FHIR R4 TerminologyCapabilities
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:49.5648101-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 TerminologyCapabilities to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities
    l: TerminologyCapabilities
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities
    l: TerminologyCapabilities
  target version:
    v: 4.0.1
  element:
    code:
      v: TerminologyCapabilities.meta
    display:
      v: meta
    target:
      code:
        v: TerminologyCapabilities.meta
      display:
        v: TerminologyCapabilities.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.meta` is mapped to FHIR R4 element `TerminologyCapabilities.meta` as `Equivalent`.
  element:
    code:
      v: TerminologyCapabilities.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: TerminologyCapabilities.implicitRules
      display:
        v: TerminologyCapabilities.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.implicitRules` is mapped to FHIR R4 element `TerminologyCapabilities.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 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.
  element:
    code:
      v: TerminologyCapabilities.language
    display:
      v: language
    target:
      code:
        v: TerminologyCapabilities.language
      display:
        v: TerminologyCapabilities.language
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.language` is mapped to FHIR R4 element `TerminologyCapabilities.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: TerminologyCapabilities.text
    display:
      v: text
    target:
      code:
        v: TerminologyCapabilities.text
      display:
        v: TerminologyCapabilities.text
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.text` is mapped to FHIR R4 element `TerminologyCapabilities.text` as `Equivalent`. 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.
  element:
    code:
      v: TerminologyCapabilities.contained
    display:
      v: contained
    target:
      code:
        v: TerminologyCapabilities.contained
      display:
        v: TerminologyCapabilities.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.contained` is mapped to FHIR R4 element `TerminologyCapabilities.contained` as `Equivalent`. 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.
  element:
    code:
      v: TerminologyCapabilities.url
    display:
      v: url
    target:
      code:
        v: TerminologyCapabilities.url
      display:
        v: TerminologyCapabilities.url
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.url` is mapped to FHIR R4 element `TerminologyCapabilities.url` as `Equivalent`. 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.
  element:
    code:
      v: TerminologyCapabilities.version
    display:
      v: version
    target:
      code:
        v: TerminologyCapabilities.version
      display:
        v: TerminologyCapabilities.version
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.version` is mapped to FHIR R4 element `TerminologyCapabilities.version` as `Equivalent`. 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).
  element:
    code:
      v: TerminologyCapabilities.name
    display:
      v: name
    target:
      code:
        v: TerminologyCapabilities.name
      display:
        v: TerminologyCapabilities.name
      equivalence:
        v: equivalent
      comment:
        v: Element `TerminologyCapabilities.name` is mapped to FHIR R4 element `TerminologyCapabilities.name` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.title
display:
  v: title
target:
  code:
    v: TerminologyCapabilities.title
  display:
    v: TerminologyCapabilities.title
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.title` is mapped to FHIR R4 element `TerminologyCapabilities.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: TerminologyCapabilities.status
display:
  v: status
target:
  code:
    v: TerminologyCapabilities.status
  display:
    v: TerminologyCapabilities.status
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.status` is mapped to FHIR R4 element `TerminologyCapabilities.status` as `Equivalent`. 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).

code:
  v: TerminologyCapabilities.experimental
display:
  v: experimental
target:
  code:
    v: TerminologyCapabilities.experimental
  display:
    v: TerminologyCapabilities.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.experimental` is mapped to FHIR R4 element `TerminologyCapabilities.experimental` as `Equivalent`. Allows filtering of terminology capabilitiess that are appropriate for use versus not.

code:
  v: TerminologyCapabilities.date
display:
  v: date
target:
  code:
    v: TerminologyCapabilities.date
  display:
    v: TerminologyCapabilities.date
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.date` is mapped to FHIR R4 element `TerminologyCapabilities.date` as `Equivalent`. 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).

code:
  v: TerminologyCapabilities.publisher
display:
  v: publisher
target:
  code:
    v: TerminologyCapabilities.publisher
  display:
    v: TerminologyCapabilities.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.publisher` is mapped to FHIR R4 element `TerminologyCapabilities.publisher` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.contact
display:
  v: contact
target:
  code:
    v: TerminologyCapabilities.contact
  display:
    v: TerminologyCapabilities.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.contact` is mapped to FHIR R4 element `TerminologyCapabilities.contact` as `Equivalent`. 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).

code:
  v: TerminologyCapabilities.description
display:
  v: description
target:
  code:
    v: TerminologyCapabilities.description
  display:
    v: TerminologyCapabilities.description
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.description` is mapped to FHIR R4 element `TerminologyCapabilities.description` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.useContext
display:
  v: useContext
target:
  code:
    v: TerminologyCapabilities.useContext
  display:
    v: TerminologyCapabilities.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.useContext` is mapped to FHIR R4 element `TerminologyCapabilities.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: TerminologyCapabilities.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: TerminologyCapabilities.jurisdiction
  display:
    v: TerminologyCapabilities.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.jurisdiction` is mapped to FHIR R4 element `TerminologyCapabilities.jurisdiction` as `Equivalent`. 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.)

code:
  v: TerminologyCapabilities.purpose
display:
  v: purpose
target:
  code:
    v: TerminologyCapabilities.purpose
  display:
    v: TerminologyCapabilities.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.purpose` is mapped to FHIR R4 element `TerminologyCapabilities.purpose` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.copyright
display:
  v: copyright
target:
  code:
    v: TerminologyCapabilities.copyright
  display:
    v: TerminologyCapabilities.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.copyright` is mapped to FHIR R4 element `TerminologyCapabilities.copyright` as `Equivalent`.

code:
  v: TerminologyCapabilities.kind
display:
  v: kind
target:
  code:
    v: TerminologyCapabilities.kind
  display:
    v: TerminologyCapabilities.kind
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.kind` is mapped to FHIR R4 element `TerminologyCapabilities.kind` as `Equivalent`.

code:
  v: TerminologyCapabilities.software
display:
  v: software
target:
  code:
    v: TerminologyCapabilities.software
  display:
    v: TerminologyCapabilities.software
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.software` is mapped to FHIR R4 element `TerminologyCapabilities.software` as `Equivalent`.

code:
  v: TerminologyCapabilities.software.name
display:
  v: name
target:
  code:
    v: TerminologyCapabilities.software.name
  display:
    v: TerminologyCapabilities.software.name
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.software.name` is mapped to FHIR R4 element `TerminologyCapabilities.software.name` as `Equivalent`.

code:
  v: TerminologyCapabilities.software.version
display:
  v: version
target:
  code:
    v: TerminologyCapabilities.software.version
  display:
    v: TerminologyCapabilities.software.version
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.software.version` is mapped to FHIR R4 element `TerminologyCapabilities.software.version` as `Equivalent`. If possible, a version should be specified, as statements are likely to be different for different versions of software.

code:
  v: TerminologyCapabilities.implementation
display:
  v: implementation
target:
  code:
    v: TerminologyCapabilities.implementation
  display:
    v: TerminologyCapabilities.implementation
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.implementation` is mapped to FHIR R4 element `TerminologyCapabilities.implementation` as `Equivalent`.

code:
  v: TerminologyCapabilities.implementation.description
display:
  v: description
target:
  code:
    v: TerminologyCapabilities.implementation.description
  display:
    v: TerminologyCapabilities.implementation.description
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.implementation.description` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.description` as `Equivalent`.

code:
  v: TerminologyCapabilities.implementation.url
display:
  v: url
target:
  code:
    v: TerminologyCapabilities.implementation.url
  display:
    v: TerminologyCapabilities.implementation.url
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.implementation.url` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.url` as `Equivalent`.

code:
  v: TerminologyCapabilities.lockedDate
display:
  v: lockedDate
target:
  code:
    v: TerminologyCapabilities.lockedDate
  display:
    v: TerminologyCapabilities.lockedDate
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.lockedDate` is mapped to FHIR R4 element `TerminologyCapabilities.lockedDate` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem
display:
  v: codeSystem
target:
  code:
    v: TerminologyCapabilities.codeSystem
  display:
    v: TerminologyCapabilities.codeSystem
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.codeSystem` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.codeSystem.uri
display:
  v: uri
target:
  code:
    v: TerminologyCapabilities.codeSystem.uri
  display:
    v: TerminologyCapabilities.codeSystem.uri
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.uri` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.uri` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version
display:
  v: version
target:
  code:
    v: TerminologyCapabilities.codeSystem.version
  display:
    v: TerminologyCapabilities.codeSystem.version
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version` as `Equivalent`. Language translations might not be available for all codes.

code:
  v: TerminologyCapabilities.codeSystem.version.code
display:
  v: code
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.code
  display:
    v: TerminologyCapabilities.codeSystem.version.code
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.code` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.isDefault
display:
  v: isDefault
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.isDefault
  display:
    v: TerminologyCapabilities.codeSystem.version.isDefault
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.isDefault` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.isDefault` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.compositional
display:
  v: compositional
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.compositional
  display:
    v: TerminologyCapabilities.codeSystem.version.compositional
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.compositional` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.compositional` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.language
display:
  v: language
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.language
  display:
    v: TerminologyCapabilities.codeSystem.version.language
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.filter
display:
  v: filter
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.filter
  display:
    v: TerminologyCapabilities.codeSystem.version.filter
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.filter` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.filter.code
display:
  v: code
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.filter.code
  display:
    v: TerminologyCapabilities.codeSystem.version.filter.code
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.filter.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.code` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.filter.op
display:
  v: op
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.filter.op
  display:
    v: TerminologyCapabilities.codeSystem.version.filter.op
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.filter.op` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.op` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.version.property
display:
  v: property
target:
  code:
    v: TerminologyCapabilities.codeSystem.version.property
  display:
    v: TerminologyCapabilities.codeSystem.version.property
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.version.property` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.property` as `Equivalent`.

code:
  v: TerminologyCapabilities.codeSystem.subsumption
display:
  v: subsumption
target:
  code:
    v: TerminologyCapabilities.codeSystem.subsumption
  display:
    v: TerminologyCapabilities.codeSystem.subsumption
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.codeSystem.subsumption` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.subsumption` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion
display:
  v: expansion
target:
  code:
    v: TerminologyCapabilities.expansion
  display:
    v: TerminologyCapabilities.expansion
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.expansion` is mapped to FHIR R4 element `TerminologyCapabilities.expansion` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.hierarchical
display:
  v: hierarchical
target:
  code:
    v: TerminologyCapabilities.expansion.hierarchical
  display:
    v: TerminologyCapabilities.expansion.hierarchical
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.hierarchical` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.hierarchical` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.paging
display:
  v: paging
target:
  code:
    v: TerminologyCapabilities.expansion.paging
  display:
    v: TerminologyCapabilities.expansion.paging
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.paging` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.paging` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.incomplete
display:
  v: incomplete
target:
  code:
    v: TerminologyCapabilities.expansion.incomplete
  display:
    v: TerminologyCapabilities.expansion.incomplete
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.incomplete` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.incomplete` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.parameter
display:
  v: parameter
target:
  code:
    v: TerminologyCapabilities.expansion.parameter
  display:
    v: TerminologyCapabilities.expansion.parameter
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.expansion.parameter` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.parameter.name
display:
  v: name
target:
  code:
    v: TerminologyCapabilities.expansion.parameter.name
  display:
    v: TerminologyCapabilities.expansion.parameter.name
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.parameter.name` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.name` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.parameter.documentation
display:
  v: documentation
target:
  code:
    v: TerminologyCapabilities.expansion.parameter.documentation
  display:
    v: TerminologyCapabilities.expansion.parameter.documentation
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.parameter.documentation` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.documentation` as `Equivalent`.

code:
  v: TerminologyCapabilities.expansion.textFilter
display:
  v: textFilter
target:
  code:
    v: TerminologyCapabilities.expansion.textFilter
  display:
    v: TerminologyCapabilities.expansion.textFilter
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.expansion.textFilter` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.textFilter` as `Equivalent`. 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.

code:
  v: TerminologyCapabilities.codeSearch
display:
  v: codeSearch
target:
  code:
    v: TerminologyCapabilities.codeSearch
  display:
    v: TerminologyCapabilities.codeSearch
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.codeSearch` is mapped to FHIR R4 element `TerminologyCapabilities.codeSearch` as `SourceIsBroaderThanTarget`. See notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource.

code:
  v: TerminologyCapabilities.validateCode
display:
  v: validateCode
target:
  code:
    v: TerminologyCapabilities.validateCode
  display:
    v: TerminologyCapabilities.validateCode
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.validateCode` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode` as `Equivalent`.

code:
  v: TerminologyCapabilities.validateCode.translations
display:
  v: translations
target:
  code:
    v: TerminologyCapabilities.validateCode.translations
  display:
    v: TerminologyCapabilities.validateCode.translations
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.validateCode.translations` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode.translations` as `Equivalent`.

code:
  v: TerminologyCapabilities.translation
display:
  v: translation
target:
  code:
    v: TerminologyCapabilities.translation
  display:
    v: TerminologyCapabilities.translation
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.translation` is mapped to FHIR R4 element `TerminologyCapabilities.translation` as `Equivalent`.

code:
  v: TerminologyCapabilities.translation.needsMap
display:
  v: needsMap
target:
  code:
    v: TerminologyCapabilities.translation.needsMap
  display:
    v: TerminologyCapabilities.translation.needsMap
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.translation.needsMap` is mapped to FHIR R4 element `TerminologyCapabilities.translation.needsMap` as `Equivalent`.

code:
  v: TerminologyCapabilities.closure
display:
  v: closure
target:
  code:
    v: TerminologyCapabilities.closure
  display:
    v: TerminologyCapabilities.closure
  equivalence:
    v: wider
  comment:
    v: Element `TerminologyCapabilities.closure` is mapped to FHIR R4 element `TerminologyCapabilities.closure` as `Equivalent`.

code:
  v: TerminologyCapabilities.closure.translation
display:
  v: translation
target:
  code:
    v: TerminologyCapabilities.closure.translation
  display:
    v: TerminologyCapabilities.closure.translation
  equivalence:
    v: equivalent
  comment:
    v: Element `TerminologyCapabilities.closure.translation` is mapped to FHIR R4 element `TerminologyCapabilities.closure.translation` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities
  l: TerminologyCapabilities
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.codeSystem.version.language
  l: extension-TerminologyCapabilities.codeSystem.version.language
target version:
  v: 0.1.0
element:
  code:
    v: TerminologyCapabilities.codeSystem.version.language
  display:
    v: language
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities
  l: TerminologyCapabilities
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.codeSystem.content
  l: extension-TerminologyCapabilities.codeSystem.content
target version:
  v: 0.1.0
element:
  code:
    v: TerminologyCapabilities.codeSystem.content
  display:
    v: content
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `TerminologyCapabilities.codeSystem.content` has a context of TerminologyCapabilities.codeSystem based on following the parent source element upwards and mapping to `TerminologyCapabilities`. Element `TerminologyCapabilities.codeSystem.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities
  l: TerminologyCapabilities
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-TerminologyCapabilities.codeSearch
  l: extension-TerminologyCapabilities.codeSearch
target version:
  v: 0.1.0
element:
  code:
    v: TerminologyCapabilities.codeSearch
  display:
    v: codeSearch
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `TerminologyCapabilities.codeSearch` is mapped to FHIR R4 element `TerminologyCapabilities.codeSearch` as `SourceIsBroaderThanTarget`. See notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource.