Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R5-SubscriptionStatus-element-map-to-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R5SubscriptionStatusElementMapToR4 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R5 SubscriptionStatus to FHIR 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/SubscriptionStatus|5.0.0 to Basicversion: 4.0.1)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.meta (meta) | is equivalent to | Basic.meta | Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `SubscriptionStatus.meta` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| SubscriptionStatus.implicitRules (implicitRules) | is equivalent to | Basic.implicitRules | Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `SubscriptionStatus.implicitRules` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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. |
| SubscriptionStatus.language (language) | is equivalent to | Basic.language | Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `SubscriptionStatus.language` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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). |
| SubscriptionStatus.text (text) | is equivalent to | Basic.text | Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `SubscriptionStatus.text` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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. |
| SubscriptionStatus.contained (contained) | is equivalent to | Basic.contained | Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `SubscriptionStatus.contained` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: requested | active | error | off | entered-in-error (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.status (status) | maps to wider concept | Extension (R5: requested | active | error | off | entered-in-error (new)) | Element `SubscriptionStatus.status` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: handshake | heartbeat | event-notification | query-status | query-event (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.type (type) | maps to wider concept | Extension (R5: handshake | heartbeat | event-notification | query-status | query-event (new)) | Element `SubscriptionStatus.type` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.type` 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/SubscriptionStatus|5.0.0 to R5: Events since the Subscription was created (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.eventsSinceSubscriptionStart (eventsSinceSubscriptionStart) | maps to wider concept | Extension (R5: Events since the Subscription was created (new)) | Element `SubscriptionStatus.eventsSinceSubscriptionStart` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.eventsSinceSubscriptionStart` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: Detailed information about any events relevant to this notification (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.notificationEvent (notificationEvent) | maps to wider concept | Extension (R5: Detailed information about any events relevant to this notification (new)) | Element `SubscriptionStatus.notificationEvent` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.notificationEvent` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| SubscriptionStatus.notificationEvent.eventNumber (eventNumber) | maps to wider concept | Extension.extension:eventNumber (R5: Sequencing index of this event (new)) | Element `SubscriptionStatus.notificationEvent.eventNumber` is part of an existing definition because parent element `SubscriptionStatus.notificationEvent` requires a cross-version extension. Element `SubscriptionStatus.notificationEvent.eventNumber` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.notificationEvent.eventNumber` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). In subscriptions where delivery of notifications IS NOT guaranteed (e.g., REST-Hook), this number is a unique and monotonically-increasing event number for a subscription. In channels where delivery of notifications IS guaranteed, this number is a relative index for the events present in the notification (e.g., 1, 2, etc.). |
| SubscriptionStatus.notificationEvent.timestamp (timestamp) | maps to wider concept | Extension.extension:timestamp (R5: The instant this event occurred (new)) | Element `SubscriptionStatus.notificationEvent.timestamp` is part of an existing definition because parent element `SubscriptionStatus.notificationEvent` requires a cross-version extension. Element `SubscriptionStatus.notificationEvent.timestamp` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.notificationEvent.timestamp` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| SubscriptionStatus.notificationEvent.focus (focus) | maps to wider concept | Extension.extension:focus (R5: Reference to the primary resource or information of this event (new)) | Element `SubscriptionStatus.notificationEvent.focus` is part of an existing definition because parent element `SubscriptionStatus.notificationEvent` requires a cross-version extension. Element `SubscriptionStatus.notificationEvent.focus` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.notificationEvent.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
| SubscriptionStatus.notificationEvent.additionalContext (additionalContext) | maps to wider concept | Extension.extension:additionalContext (R5: References related to the focus resource and/or context of this event (new)) | Element `SubscriptionStatus.notificationEvent.additionalContext` is part of an existing definition because parent element `SubscriptionStatus.notificationEvent` requires a cross-version extension. Element `SubscriptionStatus.notificationEvent.additionalContext` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.notificationEvent.additionalContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: Reference to the Subscription responsible for this notification (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.subscription (subscription) | maps to wider concept | Extension (R5: Reference to the Subscription responsible for this notification (new)) | Element `SubscriptionStatus.subscription` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.subscription` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: Reference to the SubscriptionTopic this notification relates to (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.topic (topic) | maps to wider concept | Extension (R5: Reference to the SubscriptionTopic this notification relates to (new)) | Element `SubscriptionStatus.topic` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.topic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This value SHOULD NOT be present when using `empty` payloads, MAY be present when using `id-only` payloads, and SHOULD be present when using `full-resource` payloads. |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/SubscriptionStatus|5.0.0 to R5: List of errors on the subscription (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| SubscriptionStatus.error (error) | maps to wider concept | Extension (R5: List of errors on the subscription (new)) | Element `SubscriptionStatus.error` is not mapped to FHIR R4, since FHIR R5 `SubscriptionStatus` is not mapped. Element `SubscriptionStatus.error` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Recommended practice: clear errors when status is updated. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r5.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change