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

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

ConceptMap: R2BundleElementMapToR4B

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

This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 Bundle to FHIR R4B.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Bundle|1.0.2 to Bundleversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
Bundle.meta (meta)maps to wider conceptBundle.metaElement `Bundle.meta` is mapped to FHIR R4B element `Bundle.meta` as `SourceIsBroaderThanTarget`. The mappings for `Bundle.meta` do not cover the following types: Meta. The mappings for `Bundle.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Bundle.implicitRules (implicitRules)is equivalent toBundle.implicitRulesElement `Bundle.implicitRules` is mapped to FHIR R4B element `Bundle.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 as much as possible.
Bundle.language (language)is equivalent toBundle.languageElement `Bundle.language` is mapped to FHIR R4B element `Bundle.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).
Bundle.type (type)is equivalent toBundle.typeElement `Bundle.type` is mapped to FHIR R4B element `Bundle.type` as `Equivalent`. It's possible to use a bundle for other purposes (e.g. a document can be accepted as a transaction). This is primarily defined so that there can be specific rules for some of the bundle types.
Bundle.total (total)is equivalent toBundle.totalElement `Bundle.total` is mapped to FHIR R4B element `Bundle.total` as `Equivalent`. Only used if the bundle is a search result set.
Bundle.link (link)maps to wider conceptBundle.linkElement `Bundle.link` is mapped to FHIR R4B element `Bundle.link` as `Equivalent`.
Bundle.link.relation (relation)is equivalent toBundle.link.relationElement `Bundle.link.relation` is mapped to FHIR R4B element `Bundle.link.relation` as `Equivalent`.
Bundle.link.url (url)is equivalent toBundle.link.urlElement `Bundle.link.url` is mapped to FHIR R4B element `Bundle.link.url` as `Equivalent`.
Bundle.entry (entry)maps to wider conceptBundle.entryElement `Bundle.entry` is mapped to FHIR R4B element `Bundle.entry` as `Equivalent`.
Bundle.entry.link (link)is equivalent toBundle.entry.linkElement `Bundle.entry.link` is mapped to FHIR R4B element `Bundle.entry.link` as `Equivalent`.
Bundle.entry.fullUrl (fullUrl)is equivalent toBundle.entry.fullUrlElement `Bundle.entry.fullUrl` is mapped to FHIR R4B element `Bundle.entry.fullUrl` as `Equivalent`. fullUrl may not be [unique in the context of a resource](https://hl7.org/fhir/bundle.html#bu.html#bundle-unique). Note that since [FHIR resources do not need to be served through the FHIR API](https://hl7.org/fhir/references.html), the absolute URL may not end with the logical id of the resource (Resource.id), but if the fullUrl does look like a RESTful server URL (e.g. meets the [regex](https://hl7.org/fhir/refere.html#regex), then it SHALL end with the Resource.id.
Bundle.entry.resource (resource)is equivalent toBundle.entry.resourceElement `Bundle.entry.resource` is mapped to FHIR R4B element `Bundle.entry.resource` as `SourceIsBroaderThanTarget`.
Bundle.entry.search (search)maps to wider conceptBundle.entry.searchElement `Bundle.entry.search` is mapped to FHIR R4B element `Bundle.entry.search` as `Equivalent`.
Bundle.entry.search.mode (mode)is equivalent toBundle.entry.search.modeElement `Bundle.entry.search.mode` is mapped to FHIR R4B element `Bundle.entry.search.mode` as `Equivalent`. There is only one mode. In some corner cases, a resource may be included because it is both a match and an include. In these circumstances, 'match' takes precedence.
Bundle.entry.search.score (score)is equivalent toBundle.entry.search.scoreElement `Bundle.entry.search.score` is mapped to FHIR R4B element `Bundle.entry.search.score` as `Equivalent`. Servers are not required to return a ranking score. 1 is most relevant, and 0 is least relevant. Often, search results are sorted by score, but the client may specify a different sort order.
Bundle.entry.request (request)maps to wider conceptBundle.entry.requestElement `Bundle.entry.request` is mapped to FHIR R4B element `Bundle.entry.request` as `Equivalent`.
Bundle.entry.request.method (method)is equivalent toBundle.entry.request.methodElement `Bundle.entry.request.method` is mapped to FHIR R4B element `Bundle.entry.request.method` as `SourceIsNarrowerThanTarget`. The mappings for `Bundle.entry.request.method` do not allow expression of the necessary codes, per the bindings on the source and target.
Bundle.entry.request.url (url)is equivalent toBundle.entry.request.urlElement `Bundle.entry.request.url` is mapped to FHIR R4B element `Bundle.entry.request.url` as `Equivalent`. E.g. for a Patient Create, the method would be "POST" and the URL would be "Patient". For a Patient Update, the method would be PUT, and the URL would be "Patient/[id]".
Bundle.entry.request.ifNoneMatch (ifNoneMatch)is equivalent toBundle.entry.request.ifNoneMatchElement `Bundle.entry.request.ifNoneMatch` is mapped to FHIR R4B element `Bundle.entry.request.ifNoneMatch` as `Equivalent`.
Bundle.entry.request.ifModifiedSince (ifModifiedSince)is equivalent toBundle.entry.request.ifModifiedSinceElement `Bundle.entry.request.ifModifiedSince` is mapped to FHIR R4B element `Bundle.entry.request.ifModifiedSince` as `Equivalent`.
Bundle.entry.request.ifMatch (ifMatch)is equivalent toBundle.entry.request.ifMatchElement `Bundle.entry.request.ifMatch` is mapped to FHIR R4B element `Bundle.entry.request.ifMatch` as `Equivalent`.
Bundle.entry.request.ifNoneExist (ifNoneExist)is equivalent toBundle.entry.request.ifNoneExistElement `Bundle.entry.request.ifNoneExist` is mapped to FHIR R4B element `Bundle.entry.request.ifNoneExist` as `Equivalent`.
Bundle.entry.response (response)maps to wider conceptBundle.entry.responseElement `Bundle.entry.response` is mapped to FHIR R4B element `Bundle.entry.response` as `Equivalent`.
Bundle.entry.response.status (status)is equivalent toBundle.entry.response.statusElement `Bundle.entry.response.status` is mapped to FHIR R4B element `Bundle.entry.response.status` as `Equivalent`.
Bundle.entry.response.location (location)is equivalent toBundle.entry.response.locationElement `Bundle.entry.response.location` is mapped to FHIR R4B element `Bundle.entry.response.location` as `Equivalent`.
Bundle.entry.response.etag (etag)is equivalent toBundle.entry.response.etagElement `Bundle.entry.response.etag` is mapped to FHIR R4B element `Bundle.entry.response.etag` as `Equivalent`. This has to match the version id in the header if a resource is included.
Bundle.entry.response.lastModified (lastModified)is equivalent toBundle.entry.response.lastModifiedElement `Bundle.entry.response.lastModified` is mapped to FHIR R4B element `Bundle.entry.response.lastModified` as `Equivalent`. This has to match the same time in the meta header if a resource is included.
Bundle.signature (signature)maps to wider conceptBundle.signatureElement `Bundle.signature` is mapped to FHIR R4B element `Bundle.signature` as `SourceIsBroaderThanTarget`. The mappings for `Bundle.signature` do not cover the following types: Signature. The mappings for `Bundle.signature` do not cover the following types based on type expansion: blob, contentType, type, when, who[x]. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Bundle|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Bundle.meta (meta)is equivalent toExtension (DSTU2: meta additional types)Element `Bundle.meta` is mapped to FHIR R4B element `Bundle.meta` as `SourceIsBroaderThanTarget`. The mappings for `Bundle.meta` do not cover the following types: Meta. The mappings for `Bundle.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Bundle|1.0.2 to DSTU2: signature additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Bundle.signature (signature)is equivalent toExtension (DSTU2: signature additional types)Element `Bundle.signature` is mapped to FHIR R4B element `Bundle.signature` as `SourceIsBroaderThanTarget`. The mappings for `Bundle.signature` do not cover the following types: Signature. The mappings for `Bundle.signature` do not cover the following types based on type expansion: blob, contentType, type, when, who[x]. The signature could be created by the "author" of the bundle or by the originating device. Requirements around inclusion of a signature, verification of signatures and treatment of signed/non-signed bundles is implementation-environment specific.