Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR DSTU2 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R2-Subscription-element-map-to-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R2SubscriptionElementMapToR5 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR DSTU2 Subscription to FHIR R5.
Mapping from http://hl7.org/fhir/1.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to Subscriptionversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.meta (meta) | is broader than | Subscription.meta | Element `Subscription.meta` is mapped to FHIR R5 element `Subscription.meta` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.meta` do not cover the following types: Meta. The mappings for `Subscription.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. |
| Subscription.implicitRules (implicitRules) | is equivalent to | Subscription.implicitRules | Element `Subscription.implicitRules` is mapped to FHIR R5 element `Subscription.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. |
| Subscription.language (language) | is equivalent to | Subscription.language | Element `Subscription.language` is mapped to FHIR R5 element `Subscription.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). |
| Subscription.text (text) | is broader than | Subscription.text | Element `Subscription.text` is mapped to FHIR R5 element `Subscription.text` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.text` do not cover the following types: Narrative. The mappings for `Subscription.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
| Subscription.contained (contained) | is equivalent to | Subscription.contained | Element `Subscription.contained` is mapped to FHIR R5 element `Subscription.contained` as `SourceIsBroaderThanTarget`. 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. |
| Subscription.contact (contact) | is broader than | Subscription.contact | Element `Subscription.contact` is mapped to FHIR R5 element `Subscription.contact` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.contact` do not cover the following types: ContactPoint. The mappings for `Subscription.contact` do not cover the following types based on type expansion: period, rank, system, use, value. |
| Subscription.reason (reason) | is equivalent to | Subscription.reason | Element `Subscription.reason` is mapped to FHIR R5 element `Subscription.reason` as `Equivalent`. |
| Subscription.status (status) | is equivalent to | Subscription.status | Element `Subscription.status` is mapped to FHIR R5 element `Subscription.status` as `SourceIsNarrowerThanTarget`. The mappings for `Subscription.status` do not allow expression of the necessary codes, per the bindings on the source and target. A client can only submit subscription resources in the requested or off state. Only the server can move a subscription from requested to active, and then to error. Either the server or the client can turn a subscription off. |
| Subscription.end (end) | is equivalent to | Subscription.end | Element `Subscription.end` is mapped to FHIR R5 element `Subscription.end` as `Equivalent`. The server is permitted to deviate from this time, but should observe it. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.meta (meta) | is equivalent to | Extension (DSTU2: meta additional types) | Element `Subscription.meta` is mapped to FHIR R5 element `Subscription.meta` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.meta` do not cover the following types: Meta. The mappings for `Subscription.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/Subscription|1.0.2 to DSTU2: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.text (text) | is equivalent to | Extension (DSTU2: text additional types) | Element `Subscription.text` is mapped to FHIR R5 element `Subscription.text` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.text` do not cover the following types: Narrative. The mappings for `Subscription.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: Rule for server push criteria (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.criteria (criteria) | is equivalent to | Extension (DSTU2: Rule for server push criteria (new)) | Element `Subscription.criteria` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.criteria` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The rules are a search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/". |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: contact additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.contact (contact) | is equivalent to | Extension (DSTU2: contact additional types) | Element `Subscription.contact` is mapped to FHIR R5 element `Subscription.contact` as `SourceIsBroaderThanTarget`. The mappings for `Subscription.contact` do not cover the following types: ContactPoint. The mappings for `Subscription.contact` do not cover the following types based on type expansion: period, rank, system, use, value. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: Latest error note (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.error (error) | is equivalent to | Extension (DSTU2: Latest error note (new)) | Element `Subscription.error` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.error` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: The channel on which to report matches to the criteria (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.channel (channel) | is equivalent to | Extension (DSTU2: The channel on which to report matches to the criteria (new)) | Element `Subscription.channel` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.channel` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| Subscription.channel.type (type) | is equivalent to | Extension.extension:type (DSTU2: rest-hook | websocket | email | sms | message (new)) | Element `Subscription.channel.type` is part of an existing definition because parent element `Subscription.channel` requires a cross-version extension. Element `Subscription.channel.type` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.channel.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). |
| Subscription.channel.endpoint (endpoint) | is equivalent to | Extension.extension:endpoint (DSTU2: Where the channel points to (new)) | Element `Subscription.channel.endpoint` is part of an existing definition because parent element `Subscription.channel` requires a cross-version extension. Element `Subscription.channel.endpoint` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.channel.endpoint` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). For rest-hook, and websocket, the end-point must be an http: or https: URL; for email, a mailto: url, for sms, a tel: url, and for message the endpoint can be in any form of url the server understands (usually, http: or mllp:). The URI is allowed to be relative; in which case, it is relative to the server end-point (since their may be more than one, clients should avoid using relative URIs). |
| Subscription.channel.payload (payload) | is equivalent to | Extension.extension:payload (DSTU2: Mimetype to send, or blank for no payload (new)) | Element `Subscription.channel.payload` is part of an existing definition because parent element `Subscription.channel` requires a cross-version extension. Element `Subscription.channel.payload` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.channel.payload` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Sending the payload has obvious security consequences. The server is responsible for ensuring that the content is appropriately secured. |
| Subscription.channel.header (header) | is broader than | Extension.extension:header (DSTU2: Usage depends on the channel type (new)) | Element `Subscription.channel.header` is part of an existing definition because parent element `Subscription.channel` requires a cross-version extension. Element `Subscription.channel.header` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.channel.header` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Exactly what these mean depend on the channel type. The can convey additional information to the recipient and/or meet security requirements. |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|1.0.2 to DSTU2: A tag to add to matching resources (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Subscription.tag (tag) | is equivalent to | Extension (DSTU2: A tag to add to matching resources (new)) | Element `Subscription.tag` has a context of Subscription based on following the parent source element upwards and mapping to `Subscription`. Element `Subscription.tag` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). So that other systems can tell which resources have been the subject of a notification. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r2.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change