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

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

ConceptMap: R4CompartmentDefinitionElementMapToR5

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4 CompartmentDefinition to FHIR R5.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CompartmentDefinition|4.0.1 to CompartmentDefinitionversion: 5.0.0)

Source CodeRelationshipTarget CodeComment
CompartmentDefinition.meta (meta)is equivalent toCompartmentDefinition.metaElement `CompartmentDefinition.meta` is mapped to FHIR R5 element `CompartmentDefinition.meta` as `Equivalent`.
CompartmentDefinition.implicitRules (implicitRules)is equivalent toCompartmentDefinition.implicitRulesElement `CompartmentDefinition.implicitRules` is mapped to FHIR R5 element `CompartmentDefinition.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.
CompartmentDefinition.language (language)is equivalent toCompartmentDefinition.languageElement `CompartmentDefinition.language` is mapped to FHIR R5 element `CompartmentDefinition.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).
CompartmentDefinition.text (text)is equivalent toCompartmentDefinition.textElement `CompartmentDefinition.text` is mapped to FHIR R5 element `CompartmentDefinition.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.
CompartmentDefinition.contained (contained)is equivalent toCompartmentDefinition.containedElement `CompartmentDefinition.contained` is mapped to FHIR R5 element `CompartmentDefinition.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.
CompartmentDefinition.url (url)is equivalent toCompartmentDefinition.urlElement `CompartmentDefinition.url` is mapped to FHIR R5 element `CompartmentDefinition.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.
CompartmentDefinition.version (version)is equivalent toCompartmentDefinition.versionElement `CompartmentDefinition.version` is mapped to FHIR R5 element `CompartmentDefinition.version` as `Equivalent`. There may be different compartment definition 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 compartment definition with the format [url]|[version].
CompartmentDefinition.name (name)is equivalent toCompartmentDefinition.nameElement `CompartmentDefinition.name` is mapped to FHIR R5 element `CompartmentDefinition.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.This is often the same as the code for the parameter, but does not need to be.
CompartmentDefinition.status (status)is equivalent toCompartmentDefinition.statusElement `CompartmentDefinition.status` is mapped to FHIR R5 element `CompartmentDefinition.status` as `Equivalent`. Allows filtering of compartment definitions that are appropriate for use versus not.
CompartmentDefinition.experimental (experimental)is equivalent toCompartmentDefinition.experimentalElement `CompartmentDefinition.experimental` is mapped to FHIR R5 element `CompartmentDefinition.experimental` as `Equivalent`. Allows filtering of compartment definitions that are appropriate for use versus not.
CompartmentDefinition.date (date)is equivalent toCompartmentDefinition.dateElement `CompartmentDefinition.date` is mapped to FHIR R5 element `CompartmentDefinition.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 compartment definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
CompartmentDefinition.publisher (publisher)is equivalent toCompartmentDefinition.publisherElement `CompartmentDefinition.publisher` is mapped to FHIR R5 element `CompartmentDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the compartment definition is the organization or individual primarily responsible for the maintenance and upkeep of the compartment definition. 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 compartment definition. This item SHOULD be populated unless the information is available from context.
CompartmentDefinition.contact (contact)is equivalent toCompartmentDefinition.contactElement `CompartmentDefinition.contact` is mapped to FHIR R5 element `CompartmentDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
CompartmentDefinition.description (description)is equivalent toCompartmentDefinition.descriptionElement `CompartmentDefinition.description` is mapped to FHIR R5 element `CompartmentDefinition.description` as `Equivalent`. This description can be used to capture details such as why the compartment definition 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 compartment definition 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 compartment definition is presumed to be the predominant language in the place the compartment definition was created).
CompartmentDefinition.useContext (useContext)is equivalent toCompartmentDefinition.useContextElement `CompartmentDefinition.useContext` is mapped to FHIR R5 element `CompartmentDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
CompartmentDefinition.purpose (purpose)is equivalent toCompartmentDefinition.purposeElement `CompartmentDefinition.purpose` is mapped to FHIR R5 element `CompartmentDefinition.purpose` as `Equivalent`. This element does not describe the usage of the compartment definition. 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 compartment definition.
CompartmentDefinition.code (code)is equivalent toCompartmentDefinition.codeElement `CompartmentDefinition.code` is mapped to FHIR R5 element `CompartmentDefinition.code` as `SourceIsNarrowerThanTarget`. The mappings for `CompartmentDefinition.code` do not allow expression of the necessary codes, per the bindings on the source and target. Only the specification can define the compartments that can exist. Servers can choose to support them.
CompartmentDefinition.search (search)is equivalent toCompartmentDefinition.searchElement `CompartmentDefinition.search` is mapped to FHIR R5 element `CompartmentDefinition.search` as `Equivalent`. Servers may define and use compartments to manage logical access without implementing the compartment related syntax.
CompartmentDefinition.resource (resource)is broader thanCompartmentDefinition.resourceElement `CompartmentDefinition.resource` is mapped to FHIR R5 element `CompartmentDefinition.resource` as `Equivalent`.
CompartmentDefinition.resource.code (code)is broader thanCompartmentDefinition.resource.codeElement `CompartmentDefinition.resource.code` is mapped to FHIR R5 element `CompartmentDefinition.resource.code` as `RelatedTo`. The mappings for `CompartmentDefinition.resource.code` do not allow expression of the necessary codes, per the bindings on the source and target.
CompartmentDefinition.resource.param (param)is equivalent toCompartmentDefinition.resource.paramElement `CompartmentDefinition.resource.param` is mapped to FHIR R5 element `CompartmentDefinition.resource.param` as `Equivalent`. If no search parameters are listed, then the resource is not linked to the compartment.
CompartmentDefinition.resource.documentation (documentation)is equivalent toCompartmentDefinition.resource.documentationElement `CompartmentDefinition.resource.documentation` is mapped to FHIR R5 element `CompartmentDefinition.resource.documentation` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CompartmentDefinition|4.0.1 to R4: code additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
CompartmentDefinition.resource.code (code)is equivalent toExtension (R4: code additional codes)Element `CompartmentDefinition.resource.code` is mapped to FHIR R5 element `CompartmentDefinition.resource.code` as `RelatedTo`. The mappings for `CompartmentDefinition.resource.code` do not allow expression of the necessary codes, per the bindings on the source and target.