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

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

ConceptMap: R5SubscriptionTopicElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 SubscriptionTopic to FHIR STU3.

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


Group 1 Mapping from SubscriptionTopicversion: 5.0.0) to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2

Source CodeRelationshipTarget CodeComment
SubscriptionTopic.meta (meta)​is equivalent toBasic.metaElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `SubscriptionTopic.meta` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.implicitRules (implicitRules)​is equivalent toBasic.implicitRulesElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `SubscriptionTopic.implicitRules` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.implicitRules` has no mapping targets in FHIR STU3. 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.
SubscriptionTopic.language (language)​is equivalent toBasic.languageElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `SubscriptionTopic.language` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.language` has no mapping targets in FHIR STU3. 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).
SubscriptionTopic.text (text)​is equivalent toBasic.textElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `SubscriptionTopic.text` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.text` has no mapping targets in FHIR STU3. 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.
SubscriptionTopic.contained (contained)​is equivalent toBasic.containedElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `SubscriptionTopic.contained` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.contained` has no mapping targets in FHIR STU3. 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.
SubscriptionTopic.identifier (identifier)​is equivalent toBasic.identifierElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `SubscriptionTopic.identifier` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element `SubscriptionTopic.identifier`: `http://hl7.org/fhir/StructureDefinition/artifact-identifier`. Note: This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

Group 2 Mapping from SubscriptionTopic to R5: Based on FHIR protocol or definition (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.derivedFrom​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.derivedFrom` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.derivedFrom` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from SubscriptionTopic to R5: Intended jurisdiction of the SubscriptionTopic (if applicable) (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.jurisdiction0..*todo​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.jurisdiction` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Element `SubscriptionTopic.jurisdiction` has been flagged as deprecated. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)

Group 4 Mapping from SubscriptionTopic to R5: Definition of a resource-based trigger for the subscription topic (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.resourceTrigger0..*todo​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.resourceTrigger` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.description0..1todo​maps to wider concept​Extension.extension:description0..1todoElement `SubscriptionTopic.resourceTrigger.description` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.description` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Implementation of particular subscription topics might not use a computable definition and instead base their design on the definition.
SubscriptionTopic.resourceTrigger.resource1..1todo​maps to wider concept​Extension.extension:resource1..1todoElement `SubscriptionTopic.resourceTrigger.resource` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.resource` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.supportedInteraction0..*todo​maps to wider concept​Extension.extension:supportedInteraction0..*todoElement `SubscriptionTopic.resourceTrigger.supportedInteraction` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.supportedInteraction` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.supportedInteraction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria0..1todo​maps to wider concept​Extension.extension:queryCriteria0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.previous0..1todo​maps to wider concept​Extension.extension:queryCriteria.extension:previous0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria.previous` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria.previous` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.previous` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (`/`).
SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate0..1todo​maps to wider concept​Extension.extension:queryCriteria.extension:resultForCreate0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.current0..1todo​maps to wider concept​Extension.extension:queryCriteria.extension:current0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria.current` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria.current` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.current` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (`/`).
SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete0..1todo​maps to wider concept​Extension.extension:queryCriteria.extension:resultForDelete0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth0..1todo​maps to wider concept​Extension.extension:queryCriteria.extension:requireBoth0..1todoElement `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Please note the interaction between this element and the `resultForCreate`/`resultForDelete` elements during `create` and `delete` interactions. For example, if `resultForCreate` is set to `test-passes`, setting `requireBoth` to `false` means that every `create` will trigger a notification while setting `requireBoth` to `true` will result in notifications if the `current` test passes. Similarly, if `resultForCreate` is set to `test-fails`, setting `requireBoth` to `true` means that no `create` will be able to generate a notification while setting `requireBoth` to `false` will result in notifications if the `current` test passes.
SubscriptionTopic.resourceTrigger.fhirPathCriteria0..1todo​maps to wider concept​Extension.extension:fhirPathCriteria0..1todoElement `SubscriptionTopic.resourceTrigger.fhirPathCriteria` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension. Element `SubscriptionTopic.resourceTrigger.fhirPathCriteria` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.fhirPathCriteria` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). FHIRPath expression with %previous and %current vars.

Group 5 Mapping from SubscriptionTopic to R5: Event definitions the SubscriptionTopic (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.eventTrigger0..*todo​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.eventTrigger` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.eventTrigger.description0..1todo​maps to wider concept​Extension.extension:description0..1todoElement `SubscriptionTopic.eventTrigger.description` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension. Element `SubscriptionTopic.eventTrigger.description` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Implementation of particular subscription topics might not use a computable definition and instead base their design on the definition.
SubscriptionTopic.eventTrigger.event1..1todo​maps to wider concept​Extension.extension:event1..1todoElement `SubscriptionTopic.eventTrigger.event` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension. Element `SubscriptionTopic.eventTrigger.event` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.event` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.eventTrigger.resource1..1todo​maps to wider concept​Extension.extension:resource1..1todoElement `SubscriptionTopic.eventTrigger.resource` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension. Element `SubscriptionTopic.eventTrigger.resource` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 6 Mapping from SubscriptionTopic to R5: Properties by which a Subscription can filter notifications from the SubscriptionTopic (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.canFilterBy0..*todo​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.canFilterBy` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.canFilterBy.description0..1todo​maps to wider concept​Extension.extension:description0..1todoElement `SubscriptionTopic.canFilterBy.description` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.description` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.canFilterBy.resource0..1todo​maps to wider concept​Extension.extension:resource0..1todoElement `SubscriptionTopic.canFilterBy.resource` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.resource` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). URL of the Resource that is the type used in this filter. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, "Patient" maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see [ElementDefinition.type.code](https://hl7.org/fhir/elementdefinition-definition.html#ElementDefinition.type.code).
SubscriptionTopic.canFilterBy.filterParameter1..1todo​maps to wider concept​Extension.extension:filterParameter1..1todoElement `SubscriptionTopic.canFilterBy.filterParameter` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.filterParameter` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.filterParameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Chained parameters are allowed (like "patient.gender") - but can not use colons or modifiers.
SubscriptionTopic.canFilterBy.filterDefinition0..1todo​maps to wider concept​Extension.extension:filterDefinition0..1todoElement `SubscriptionTopic.canFilterBy.filterDefinition` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.filterDefinition` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.filterDefinition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Chained parameters are allowed (like "patient.gender") - but can not use colons or modifiers.
SubscriptionTopic.canFilterBy.comparator0..*todo​maps to wider concept​Extension.extension:comparator0..*todoElement `SubscriptionTopic.canFilterBy.comparator` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.comparator` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.comparator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If no comparators are listed, clients should not expect servers to support any comparators.
SubscriptionTopic.canFilterBy.modifier0..*todo​maps to wider concept​Extension.extension:modifier0..*todoElement `SubscriptionTopic.canFilterBy.modifier` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension. Element `SubscriptionTopic.canFilterBy.modifier` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.modifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). If no modifiers are listed, clients should not expect servers to support any modifiers.

Group 7 Mapping from SubscriptionTopic to R5: Properties for describing the shape of notifications generated by this topic (new)

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.notificationShape0..*todo​maps to wider conceptExtension0..*todoElement `SubscriptionTopic.notificationShape` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.notificationShape.resource1..1todo​maps to wider concept​Extension.extension:resource1..1todoElement `SubscriptionTopic.notificationShape.resource` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.resource` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). URL of the Resource that is the type used in this shape. Relative URLs are relative to the StructureDefinition root of the implemented FHIR version (e.g., http://hl7.org/fhir/StructureDefinition). For example, 'Patient' maps to http://hl7.org/fhir/StructureDefinition/Patient. For more information, see [ElementDefinition.type.code](https://hl7.org/fhir/elementdefinition-definition.html#ElementDefinition.type.code).
SubscriptionTopic.notificationShape.include0..*todo​maps to wider concept​Extension.extension:include0..*todoElement `SubscriptionTopic.notificationShape.include` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.include` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.include` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.notificationShape.revInclude0..*todo​maps to wider concept​Extension.extension:revInclude0..*todoElement `SubscriptionTopic.notificationShape.revInclude` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension. Element `SubscriptionTopic.notificationShape.revInclude` is not mapped to FHIR STU3, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.revInclude` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).