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 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 to TerminologyCapabilities.text 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. TerminologyCapabilities.contained (contained) is equivalent to TerminologyCapabilities.contained 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. TerminologyCapabilities.url (url) is equivalent to TerminologyCapabilities.url 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. TerminologyCapabilities.version (version) is equivalent to TerminologyCapabilities.version 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). TerminologyCapabilities.name (name) is equivalent to TerminologyCapabilities.name 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. TerminologyCapabilities.title (title) is equivalent to TerminologyCapabilities.title 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. TerminologyCapabilities.status (status) is equivalent to TerminologyCapabilities.status 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). TerminologyCapabilities.experimental (experimental) is equivalent to TerminologyCapabilities.experimental 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. TerminologyCapabilities.date (date) is equivalent to TerminologyCapabilities.date 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). TerminologyCapabilities.publisher (publisher) is equivalent to TerminologyCapabilities.publisher 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. TerminologyCapabilities.contact (contact) is equivalent to TerminologyCapabilities.contact 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). TerminologyCapabilities.description (description) is equivalent to TerminologyCapabilities.description 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. TerminologyCapabilities.useContext (useContext) is equivalent to TerminologyCapabilities.useContext 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. TerminologyCapabilities.jurisdiction (jurisdiction) is equivalent to TerminologyCapabilities.jurisdiction 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.) TerminologyCapabilities.purpose (purpose) is equivalent to TerminologyCapabilities.purpose 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. TerminologyCapabilities.copyright (copyright) is equivalent to TerminologyCapabilities.copyright Element `TerminologyCapabilities.copyright` is mapped to FHIR R4 element `TerminologyCapabilities.copyright` as `Equivalent`. TerminologyCapabilities.kind (kind) is equivalent to TerminologyCapabilities.kind Element `TerminologyCapabilities.kind` is mapped to FHIR R4 element `TerminologyCapabilities.kind` as `Equivalent`. TerminologyCapabilities.software (software) maps to wider concept TerminologyCapabilities.software Element `TerminologyCapabilities.software` is mapped to FHIR R4 element `TerminologyCapabilities.software` as `Equivalent`. TerminologyCapabilities.software.name (name) is equivalent to TerminologyCapabilities.software.name Element `TerminologyCapabilities.software.name` is mapped to FHIR R4 element `TerminologyCapabilities.software.name` as `Equivalent`. TerminologyCapabilities.software.version (version) is equivalent to TerminologyCapabilities.software.version 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. TerminologyCapabilities.implementation (implementation) maps to wider concept TerminologyCapabilities.implementation Element `TerminologyCapabilities.implementation` is mapped to FHIR R4 element `TerminologyCapabilities.implementation` as `Equivalent`. TerminologyCapabilities.implementation.description (description) is equivalent to TerminologyCapabilities.implementation.description Element `TerminologyCapabilities.implementation.description` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.description` as `Equivalent`. TerminologyCapabilities.implementation.url (url) is equivalent to TerminologyCapabilities.implementation.url Element `TerminologyCapabilities.implementation.url` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.url` as `Equivalent`. TerminologyCapabilities.lockedDate (lockedDate) is equivalent to TerminologyCapabilities.lockedDate Element `TerminologyCapabilities.lockedDate` is mapped to FHIR R4 element `TerminologyCapabilities.lockedDate` as `Equivalent`. TerminologyCapabilities.codeSystem (codeSystem) maps to wider concept TerminologyCapabilities.codeSystem 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. TerminologyCapabilities.codeSystem.uri (uri) is equivalent to TerminologyCapabilities.codeSystem.uri Element `TerminologyCapabilities.codeSystem.uri` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.uri` as `Equivalent`. TerminologyCapabilities.codeSystem.version (version) maps to wider concept TerminologyCapabilities.codeSystem.version Element `TerminologyCapabilities.codeSystem.version` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version` as `Equivalent`. Language translations might not be available for all codes. TerminologyCapabilities.codeSystem.version.code (code) is equivalent to TerminologyCapabilities.codeSystem.version.code Element `TerminologyCapabilities.codeSystem.version.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.code` as `Equivalent`. TerminologyCapabilities.codeSystem.version.isDefault (isDefault) is equivalent to TerminologyCapabilities.codeSystem.version.isDefault Element `TerminologyCapabilities.codeSystem.version.isDefault` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.isDefault` as `Equivalent`. TerminologyCapabilities.codeSystem.version.compositional (compositional) is equivalent to TerminologyCapabilities.codeSystem.version.compositional Element `TerminologyCapabilities.codeSystem.version.compositional` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.compositional` as `Equivalent`. TerminologyCapabilities.codeSystem.version.language (language) maps to wider concept TerminologyCapabilities.codeSystem.version.language Element `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`. TerminologyCapabilities.codeSystem.version.filter (filter) maps to wider concept TerminologyCapabilities.codeSystem.version.filter Element `TerminologyCapabilities.codeSystem.version.filter` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter` as `Equivalent`. TerminologyCapabilities.codeSystem.version.filter.code (code) is equivalent to TerminologyCapabilities.codeSystem.version.filter.code Element `TerminologyCapabilities.codeSystem.version.filter.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.code` as `Equivalent`. TerminologyCapabilities.codeSystem.version.filter.op (op) is equivalent to TerminologyCapabilities.codeSystem.version.filter.op Element `TerminologyCapabilities.codeSystem.version.filter.op` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.op` as `Equivalent`. TerminologyCapabilities.codeSystem.version.property (property) is equivalent to TerminologyCapabilities.codeSystem.version.property Element `TerminologyCapabilities.codeSystem.version.property` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.property` as `Equivalent`. TerminologyCapabilities.codeSystem.subsumption (subsumption) is equivalent to TerminologyCapabilities.codeSystem.subsumption Element `TerminologyCapabilities.codeSystem.subsumption` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.subsumption` as `Equivalent`. TerminologyCapabilities.expansion (expansion) maps to wider concept TerminologyCapabilities.expansion Element `TerminologyCapabilities.expansion` is mapped to FHIR R4 element `TerminologyCapabilities.expansion` as `Equivalent`. TerminologyCapabilities.expansion.hierarchical (hierarchical) is equivalent to TerminologyCapabilities.expansion.hierarchical Element `TerminologyCapabilities.expansion.hierarchical` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.hierarchical` as `Equivalent`. TerminologyCapabilities.expansion.paging (paging) is equivalent to TerminologyCapabilities.expansion.paging Element `TerminologyCapabilities.expansion.paging` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.paging` as `Equivalent`. TerminologyCapabilities.expansion.incomplete (incomplete) is equivalent to TerminologyCapabilities.expansion.incomplete Element `TerminologyCapabilities.expansion.incomplete` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.incomplete` as `Equivalent`. TerminologyCapabilities.expansion.parameter (parameter) maps to wider concept TerminologyCapabilities.expansion.parameter Element `TerminologyCapabilities.expansion.parameter` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter` as `Equivalent`. TerminologyCapabilities.expansion.parameter.name (name) is equivalent to TerminologyCapabilities.expansion.parameter.name Element `TerminologyCapabilities.expansion.parameter.name` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.name` as `Equivalent`. TerminologyCapabilities.expansion.parameter.documentation (documentation) is equivalent to TerminologyCapabilities.expansion.parameter.documentation Element `TerminologyCapabilities.expansion.parameter.documentation` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.documentation` as `Equivalent`. TerminologyCapabilities.expansion.textFilter (textFilter) is equivalent to TerminologyCapabilities.expansion.textFilter 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. TerminologyCapabilities.codeSearch (codeSearch) maps to wider concept TerminologyCapabilities.codeSearch 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. TerminologyCapabilities.validateCode (validateCode) maps to wider concept TerminologyCapabilities.validateCode Element `TerminologyCapabilities.validateCode` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode` as `Equivalent`. TerminologyCapabilities.validateCode.translations (translations) is equivalent to TerminologyCapabilities.validateCode.translations Element `TerminologyCapabilities.validateCode.translations` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode.translations` as `Equivalent`. TerminologyCapabilities.translation (translation) maps to wider concept TerminologyCapabilities.translation Element `TerminologyCapabilities.translation` is mapped to FHIR R4 element `TerminologyCapabilities.translation` as `Equivalent`. TerminologyCapabilities.translation.needsMap (needsMap) is equivalent to TerminologyCapabilities.translation.needsMap Element `TerminologyCapabilities.translation.needsMap` is mapped to FHIR R4 element `TerminologyCapabilities.translation.needsMap` as `Equivalent`. TerminologyCapabilities.closure (closure) maps to wider concept TerminologyCapabilities.closure Element `TerminologyCapabilities.closure` is mapped to FHIR R4 element `TerminologyCapabilities.closure` as `Equivalent`. TerminologyCapabilities.closure.translation (translation) is equivalent to TerminologyCapabilities.closure.translation Element `TerminologyCapabilities.closure.translation` is mapped to FHIR R4 element `TerminologyCapabilities.closure.translation` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: languageversion: 0.1.0) Source Code Relationship Target Code Comment TerminologyCapabilities.codeSystem.version.language (language) is equivalent to Extension (R5: language) Element `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: not-present | example | fragment | complete | supplement (new)version: 0.1.0) Source Code Relationship Target Code Comment TerminologyCapabilities.codeSystem.content (content) maps to wider concept Extension (R5: not-present | example | fragment | complete | supplement (new)) 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). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|5.0.0 to R5: in-compose | in-expansion | in-compose-or-expansionversion: 0.1.0) Source Code Relationship Target Code Comment TerminologyCapabilities.codeSearch (codeSearch) is equivalent to Extension (R5: in-compose | in-expansion | in-compose-or-expansion) 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.
Cross-version mapping for FHIR R5 TerminologyCapabilities to FHIR R4 TerminologyCapabilities
This ConceptMap represents cross-version mappings for elements from a FHIR R5 TerminologyCapabilities to FHIR R4.
Element `TerminologyCapabilities.meta` is mapped to FHIR R4 element `TerminologyCapabilities.meta` as `Equivalent`.
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 `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 `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 `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 `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 `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 `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.
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.
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).
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.
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).
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.
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).
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.
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.
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.)
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.
Element `TerminologyCapabilities.copyright` is mapped to FHIR R4 element `TerminologyCapabilities.copyright` as `Equivalent`.
Element `TerminologyCapabilities.kind` is mapped to FHIR R4 element `TerminologyCapabilities.kind` as `Equivalent`.
Element `TerminologyCapabilities.software` is mapped to FHIR R4 element `TerminologyCapabilities.software` as `Equivalent`.
Element `TerminologyCapabilities.software.name` is mapped to FHIR R4 element `TerminologyCapabilities.software.name` as `Equivalent`.
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.
Element `TerminologyCapabilities.implementation` is mapped to FHIR R4 element `TerminologyCapabilities.implementation` as `Equivalent`.
Element `TerminologyCapabilities.implementation.description` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.description` as `Equivalent`.
Element `TerminologyCapabilities.implementation.url` is mapped to FHIR R4 element `TerminologyCapabilities.implementation.url` as `Equivalent`.
Element `TerminologyCapabilities.lockedDate` is mapped to FHIR R4 element `TerminologyCapabilities.lockedDate` as `Equivalent`.
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.
Element `TerminologyCapabilities.codeSystem.uri` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.uri` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version` as `Equivalent`. Language translations might not be available for all codes.
Element `TerminologyCapabilities.codeSystem.version.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.code` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.isDefault` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.isDefault` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.compositional` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.compositional` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.filter` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.filter.code` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.code` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.filter.op` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.filter.op` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.version.property` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.version.property` as `Equivalent`.
Element `TerminologyCapabilities.codeSystem.subsumption` is mapped to FHIR R4 element `TerminologyCapabilities.codeSystem.subsumption` as `Equivalent`.
Element `TerminologyCapabilities.expansion` is mapped to FHIR R4 element `TerminologyCapabilities.expansion` as `Equivalent`.
Element `TerminologyCapabilities.expansion.hierarchical` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.hierarchical` as `Equivalent`.
Element `TerminologyCapabilities.expansion.paging` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.paging` as `Equivalent`.
Element `TerminologyCapabilities.expansion.incomplete` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.incomplete` as `Equivalent`.
Element `TerminologyCapabilities.expansion.parameter` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter` as `Equivalent`.
Element `TerminologyCapabilities.expansion.parameter.name` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.name` as `Equivalent`.
Element `TerminologyCapabilities.expansion.parameter.documentation` is mapped to FHIR R4 element `TerminologyCapabilities.expansion.parameter.documentation` as `Equivalent`.
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.
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.
Element `TerminologyCapabilities.validateCode` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode` as `Equivalent`.
Element `TerminologyCapabilities.validateCode.translations` is mapped to FHIR R4 element `TerminologyCapabilities.validateCode.translations` as `Equivalent`.
Element `TerminologyCapabilities.translation` is mapped to FHIR R4 element `TerminologyCapabilities.translation` as `Equivalent`.
Element `TerminologyCapabilities.translation.needsMap` is mapped to FHIR R4 element `TerminologyCapabilities.translation.needsMap` as `Equivalent`.
Element `TerminologyCapabilities.closure` is mapped to FHIR R4 element `TerminologyCapabilities.closure` as `Equivalent`.
Element `TerminologyCapabilities.closure.translation` is mapped to FHIR R4 element `TerminologyCapabilities.closure.translation` as `Equivalent`.
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).