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

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

ConceptMap: R4TerminologyCapabilitiesElementMapToR4B

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4-TerminologyCapabilities-element-map-to-R4B Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R4TerminologyCapabilitiesElementMapToR4B

This ConceptMap represents cross-version mappings for elements from a FHIR R4 TerminologyCapabilities to FHIR R4B.

Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/4.3


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TerminologyCapabilities|4.0.1 to TerminologyCapabilitiesversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
TerminologyCapabilities.meta (meta)is equivalent toTerminologyCapabilities.metaElement `TerminologyCapabilities.meta` is mapped to FHIR R4B element `TerminologyCapabilities.meta` as `Equivalent`.
TerminologyCapabilities.implicitRules (implicitRules)is equivalent toTerminologyCapabilities.implicitRulesElement `TerminologyCapabilities.implicitRules` is mapped to FHIR R4B 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 it's narrative along with other profiles, value sets, etc.
TerminologyCapabilities.language (language)is equivalent toTerminologyCapabilities.languageElement `TerminologyCapabilities.language` is mapped to FHIR R4B 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 toTerminologyCapabilities.textElement `TerminologyCapabilities.text` is mapped to FHIR R4B element `TerminologyCapabilities.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
TerminologyCapabilities.contained (contained)is equivalent toTerminologyCapabilities.containedElement `TerminologyCapabilities.contained` is mapped to FHIR R4B 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 toTerminologyCapabilities.urlElement `TerminologyCapabilities.url` is mapped to FHIR R4B 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 toTerminologyCapabilities.versionElement `TerminologyCapabilities.version` is mapped to FHIR R4B 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].
TerminologyCapabilities.name (name)is equivalent toTerminologyCapabilities.nameElement `TerminologyCapabilities.name` is mapped to FHIR R4B 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 toTerminologyCapabilities.titleElement `TerminologyCapabilities.title` is mapped to FHIR R4B 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 toTerminologyCapabilities.statusElement `TerminologyCapabilities.status` is mapped to FHIR R4B 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.
TerminologyCapabilities.experimental (experimental)is equivalent toTerminologyCapabilities.experimentalElement `TerminologyCapabilities.experimental` is mapped to FHIR R4B element `TerminologyCapabilities.experimental` as `Equivalent`. Allows filtering of terminology capabilitiess that are appropriate for use versus not.
TerminologyCapabilities.date (date)is equivalent toTerminologyCapabilities.dateElement `TerminologyCapabilities.date` is mapped to FHIR R4B element `TerminologyCapabilities.date` as `Equivalent`. 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.
TerminologyCapabilities.publisher (publisher)is equivalent toTerminologyCapabilities.publisherElement `TerminologyCapabilities.publisher` is mapped to FHIR R4B 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 toTerminologyCapabilities.contactElement `TerminologyCapabilities.contact` is mapped to FHIR R4B element `TerminologyCapabilities.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
TerminologyCapabilities.description (description)is equivalent toTerminologyCapabilities.descriptionElement `TerminologyCapabilities.description` is mapped to FHIR R4B element `TerminologyCapabilities.description` as `Equivalent`. This description can be used to capture details such as why the terminology capabilities was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the terminology capabilities as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the terminology capabilities is presumed to be the predominant language in the place the terminology capabilities was created).This does not need to be populated if the description is adequately implied by the software or implementation details.
TerminologyCapabilities.useContext (useContext)is equivalent toTerminologyCapabilities.useContextElement `TerminologyCapabilities.useContext` is mapped to FHIR R4B 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 toTerminologyCapabilities.jurisdictionElement `TerminologyCapabilities.jurisdiction` is mapped to FHIR R4B element `TerminologyCapabilities.jurisdiction` as `Equivalent`. It may be possible for the terminology capabilities to be used in jurisdictions other than those for which it was originally designed or intended.
TerminologyCapabilities.purpose (purpose)is equivalent toTerminologyCapabilities.purposeElement `TerminologyCapabilities.purpose` is mapped to FHIR R4B 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 toTerminologyCapabilities.copyrightElement `TerminologyCapabilities.copyright` is mapped to FHIR R4B element `TerminologyCapabilities.copyright` as `Equivalent`.
TerminologyCapabilities.kind (kind)is equivalent toTerminologyCapabilities.kindElement `TerminologyCapabilities.kind` is mapped to FHIR R4B element `TerminologyCapabilities.kind` as `Equivalent`.
TerminologyCapabilities.software (software)maps to wider conceptTerminologyCapabilities.softwareElement `TerminologyCapabilities.software` is mapped to FHIR R4B element `TerminologyCapabilities.software` as `Equivalent`.
TerminologyCapabilities.software.name (name)is equivalent toTerminologyCapabilities.software.nameElement `TerminologyCapabilities.software.name` is mapped to FHIR R4B element `TerminologyCapabilities.software.name` as `Equivalent`.
TerminologyCapabilities.software.version (version)is equivalent toTerminologyCapabilities.software.versionElement `TerminologyCapabilities.software.version` is mapped to FHIR R4B 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 conceptTerminologyCapabilities.implementationElement `TerminologyCapabilities.implementation` is mapped to FHIR R4B element `TerminologyCapabilities.implementation` as `Equivalent`.
TerminologyCapabilities.implementation.description (description)is equivalent toTerminologyCapabilities.implementation.descriptionElement `TerminologyCapabilities.implementation.description` is mapped to FHIR R4B element `TerminologyCapabilities.implementation.description` as `Equivalent`.
TerminologyCapabilities.implementation.url (url)is equivalent toTerminologyCapabilities.implementation.urlElement `TerminologyCapabilities.implementation.url` is mapped to FHIR R4B element `TerminologyCapabilities.implementation.url` as `Equivalent`.
TerminologyCapabilities.lockedDate (lockedDate)is equivalent toTerminologyCapabilities.lockedDateElement `TerminologyCapabilities.lockedDate` is mapped to FHIR R4B element `TerminologyCapabilities.lockedDate` as `Equivalent`.
TerminologyCapabilities.codeSystem (codeSystem)maps to wider conceptTerminologyCapabilities.codeSystemElement `TerminologyCapabilities.codeSystem` is mapped to FHIR R4B 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 toTerminologyCapabilities.codeSystem.uriElement `TerminologyCapabilities.codeSystem.uri` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.uri` as `Equivalent`.
TerminologyCapabilities.codeSystem.version (version)maps to wider conceptTerminologyCapabilities.codeSystem.versionElement `TerminologyCapabilities.codeSystem.version` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version` as `Equivalent`. Language translations might not be available for all codes.
TerminologyCapabilities.codeSystem.version.code (code)is equivalent toTerminologyCapabilities.codeSystem.version.codeElement `TerminologyCapabilities.codeSystem.version.code` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.code` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.isDefault (isDefault)is equivalent toTerminologyCapabilities.codeSystem.version.isDefaultElement `TerminologyCapabilities.codeSystem.version.isDefault` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.isDefault` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.compositional (compositional)is equivalent toTerminologyCapabilities.codeSystem.version.compositionalElement `TerminologyCapabilities.codeSystem.version.compositional` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.compositional` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.language (language)is equivalent toTerminologyCapabilities.codeSystem.version.languageElement `TerminologyCapabilities.codeSystem.version.language` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.language` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.filter (filter)maps to wider conceptTerminologyCapabilities.codeSystem.version.filterElement `TerminologyCapabilities.codeSystem.version.filter` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.filter` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.filter.code (code)is equivalent toTerminologyCapabilities.codeSystem.version.filter.codeElement `TerminologyCapabilities.codeSystem.version.filter.code` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.filter.code` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.filter.op (op)is equivalent toTerminologyCapabilities.codeSystem.version.filter.opElement `TerminologyCapabilities.codeSystem.version.filter.op` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.filter.op` as `Equivalent`.
TerminologyCapabilities.codeSystem.version.property (property)is equivalent toTerminologyCapabilities.codeSystem.version.propertyElement `TerminologyCapabilities.codeSystem.version.property` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.version.property` as `Equivalent`.
TerminologyCapabilities.codeSystem.subsumption (subsumption)is equivalent toTerminologyCapabilities.codeSystem.subsumptionElement `TerminologyCapabilities.codeSystem.subsumption` is mapped to FHIR R4B element `TerminologyCapabilities.codeSystem.subsumption` as `Equivalent`.
TerminologyCapabilities.expansion (expansion)maps to wider conceptTerminologyCapabilities.expansionElement `TerminologyCapabilities.expansion` is mapped to FHIR R4B element `TerminologyCapabilities.expansion` as `Equivalent`.
TerminologyCapabilities.expansion.hierarchical (hierarchical)is equivalent toTerminologyCapabilities.expansion.hierarchicalElement `TerminologyCapabilities.expansion.hierarchical` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.hierarchical` as `Equivalent`.
TerminologyCapabilities.expansion.paging (paging)is equivalent toTerminologyCapabilities.expansion.pagingElement `TerminologyCapabilities.expansion.paging` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.paging` as `Equivalent`.
TerminologyCapabilities.expansion.incomplete (incomplete)is equivalent toTerminologyCapabilities.expansion.incompleteElement `TerminologyCapabilities.expansion.incomplete` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.incomplete` as `Equivalent`.
TerminologyCapabilities.expansion.parameter (parameter)maps to wider conceptTerminologyCapabilities.expansion.parameterElement `TerminologyCapabilities.expansion.parameter` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.parameter` as `Equivalent`.
TerminologyCapabilities.expansion.parameter.name (name)is equivalent toTerminologyCapabilities.expansion.parameter.nameElement `TerminologyCapabilities.expansion.parameter.name` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.parameter.name` as `Equivalent`.
TerminologyCapabilities.expansion.parameter.documentation (documentation)is equivalent toTerminologyCapabilities.expansion.parameter.documentationElement `TerminologyCapabilities.expansion.parameter.documentation` is mapped to FHIR R4B element `TerminologyCapabilities.expansion.parameter.documentation` as `Equivalent`.
TerminologyCapabilities.expansion.textFilter (textFilter)is equivalent toTerminologyCapabilities.expansion.textFilterElement `TerminologyCapabilities.expansion.textFilter` is mapped to FHIR R4B 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)is equivalent toTerminologyCapabilities.codeSearchElement `TerminologyCapabilities.codeSearch` is mapped to FHIR R4B element `TerminologyCapabilities.codeSearch` as `Equivalent`. See notes on the [ValueSet](https://hl7.org/fhir/v.html#) resource.
TerminologyCapabilities.validateCode (validateCode)maps to wider conceptTerminologyCapabilities.validateCodeElement `TerminologyCapabilities.validateCode` is mapped to FHIR R4B element `TerminologyCapabilities.validateCode` as `Equivalent`.
TerminologyCapabilities.validateCode.translations (translations)is equivalent toTerminologyCapabilities.validateCode.translationsElement `TerminologyCapabilities.validateCode.translations` is mapped to FHIR R4B element `TerminologyCapabilities.validateCode.translations` as `Equivalent`.
TerminologyCapabilities.translation (translation)maps to wider conceptTerminologyCapabilities.translationElement `TerminologyCapabilities.translation` is mapped to FHIR R4B element `TerminologyCapabilities.translation` as `Equivalent`.
TerminologyCapabilities.translation.needsMap (needsMap)is equivalent toTerminologyCapabilities.translation.needsMapElement `TerminologyCapabilities.translation.needsMap` is mapped to FHIR R4B element `TerminologyCapabilities.translation.needsMap` as `Equivalent`.
TerminologyCapabilities.closure (closure)maps to wider conceptTerminologyCapabilities.closureElement `TerminologyCapabilities.closure` is mapped to FHIR R4B element `TerminologyCapabilities.closure` as `Equivalent`.
TerminologyCapabilities.closure.translation (translation)is equivalent toTerminologyCapabilities.closure.translationElement `TerminologyCapabilities.closure.translation` is mapped to FHIR R4B element `TerminologyCapabilities.closure.translation` as `Equivalent`.