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

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

ConceptMap: R3SubscriptionElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Subscription to FHIR R4.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|3.0.2 to Subscriptionversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Subscription.meta (meta)is equivalent toSubscription.metaElement `Subscription.meta` is mapped to FHIR R4 element `Subscription.meta` as `Equivalent`.
Subscription.implicitRules (implicitRules)is equivalent toSubscription.implicitRulesElement `Subscription.implicitRules` is mapped to FHIR R4 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Subscription.language (language)is equivalent toSubscription.languageElement `Subscription.language` is mapped to FHIR R4 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 equivalent toSubscription.textElement `Subscription.text` is mapped to FHIR R4 element `Subscription.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 in formation is added later.
Subscription.contained (contained)is equivalent toSubscription.containedElement `Subscription.contained` is mapped to FHIR R4 element `Subscription.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.
Subscription.status (status)is equivalent toSubscription.statusElement `Subscription.status` is mapped to FHIR R4 element `Subscription.status` as `Equivalent`. 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. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Subscription.contact (contact)is equivalent toSubscription.contactElement `Subscription.contact` is mapped to FHIR R4 element `Subscription.contact` as `Equivalent`.
Subscription.end (end)is equivalent toSubscription.endElement `Subscription.end` is mapped to FHIR R4 element `Subscription.end` as `Equivalent`. The server is permitted to deviate from this time, but should observe it.
Subscription.reason (reason)is equivalent toSubscription.reasonElement `Subscription.reason` is mapped to FHIR R4 element `Subscription.reason` as `Equivalent`.
Subscription.criteria (criteria)is equivalent toSubscription.criteriaElement `Subscription.criteria` is mapped to FHIR R4 element `Subscription.criteria` as `Equivalent`. The rules are a search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading "/".
Subscription.error (error)is equivalent toSubscription.errorElement `Subscription.error` is mapped to FHIR R4 element `Subscription.error` as `Equivalent`.
Subscription.channel (channel)maps to wider conceptSubscription.channelElement `Subscription.channel` is mapped to FHIR R4 element `Subscription.channel` as `Equivalent`.
Subscription.channel.type (type)is equivalent toSubscription.channel.typeElement `Subscription.channel.type` is mapped to FHIR R4 element `Subscription.channel.type` as `Equivalent`.
Subscription.channel.endpoint (endpoint)is equivalent toSubscription.channel.endpointElement `Subscription.channel.endpoint` is mapped to FHIR R4 element `Subscription.channel.endpoint` as `Equivalent`. 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 toSubscription.channel.payloadElement `Subscription.channel.payload` is mapped to FHIR R4 element `Subscription.channel.payload` as `Equivalent`. Sending the payload has obvious security implications. The server is responsible for ensuring that the content is appropriately secured.
Subscription.channel.header (header)is equivalent toSubscription.channel.headerElement `Subscription.channel.header` is mapped to FHIR R4 element `Subscription.channel.header` as `Equivalent`. Exactly what these mean depend on the channel type. They can convey additional information to the recipient and/or meet security requirements; for example, support of multiple headers in the outgoing notifications for rest-hook type subscriptions.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Subscription|3.0.2 to STU3: A tag to add to matching resources (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Subscription.tag (tag)is equivalent toExtension (STU3: 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 R4. 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.