FHIR © HL7.org  |  FHIRsmith 4.0.1  |  Server Home  |  XIG Home  |  XIG Stats  | 

FHIR IG analytics

Packagehl7.fhir.uv.xver-r5.r4
Resource TypeConceptMap
IdConceptMap-R5-SubscriptionTopic-element-map-to-R4.json
FHIR VersionR4
Sourcehttp://hl7.org/fhir/uv/xver-r5.r4/0.1.0/ConceptMap-R5-SubscriptionTopic-element-map-to-R4.html
URLhttp://hl7.org/fhir/uv/xver/ConceptMap/R5-SubscriptionTopic-element-map-to-R4
Version0.1.0
Statusactive
Date2026-03-17T16:04:48.3322176-05:00
NameR5SubscriptionTopicElementMapToR4
TitleCross-version mapping for FHIR R5 SubscriptionTopic to FHIR R4 Basic
Realmuv
Authorityhl7
DescriptionThis ConceptMap represents cross-version mappings for elements from a FHIR R5 SubscriptionTopic to FHIR R4.

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.canFilterByR5: Properties by which a Subscription can filter notifications from the SubscriptionTopic (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.derivedFromR5: Based on FHIR protocol or definition (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.eventTriggerR5: Event definitions the SubscriptionTopic (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.jurisdictionR5: Intended jurisdiction of the SubscriptionTopic (if applicable) (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.notificationShapeR5: Properties for describing the shape of notifications generated by this topic (new)
hl7.fhir.uv.xver-r5.r4#0.1.0extension-SubscriptionTopic.resourceTriggerR5: Definition of a resource-based trigger for the subscription topic (new)

Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ConceptMap R5-SubscriptionTopic-element-map-to-R4

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


Group 1 Mapping from SubscriptionTopic to Basic

Source CodeCard.TypeRelationshipTarget CodeCard.TypeComment
SubscriptionTopic.meta0..1todois equivalent toBasic.meta0..1todoElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `SubscriptionTopic.meta` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.implicitRules0..1todois equivalent toBasic.implicitRules0..1todoElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `SubscriptionTopic.implicitRules` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.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.
SubscriptionTopic.language0..1todois equivalent toBasic.language0..1todoElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `SubscriptionTopic.language` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.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).
SubscriptionTopic.text0..1todois equivalent toBasic.text0..1todoElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `SubscriptionTopic.text` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.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.
SubscriptionTopic.contained0..*todois equivalent toBasic.contained0..*todoElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `SubscriptionTopic.contained` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.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.
SubscriptionTopic.identifier0..*todois equivalent toBasic.identifier0..*todoElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `SubscriptionTopic.identifier` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.identifier` has no mapping targets in FHIR R4. 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.derivedFrom0..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.derivedFrom` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.jurisdiction` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.jurisdiction` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.resourceTrigger` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.description0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.description` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.supportedInteraction0..*todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.supportedInteraction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.previous0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.previous` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.current0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.current` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.resourceTrigger.fhirPathCriteria` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.eventTrigger` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.eventTrigger.description0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.description` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.eventTrigger.resource1..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.eventTrigger.resource` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.canFilterBy` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.canFilterBy.description0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.canFilterBy.resource0..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.resource` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.filterParameter` has no mapping targets in FHIR R4. 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..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.filterDefinition` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.comparator` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.canFilterBy.modifier` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension0..*todoElement `SubscriptionTopic.notificationShape` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.notificationShape.resource1..1todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.resource` has no mapping targets in FHIR R4. 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..*todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.include` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
SubscriptionTopic.notificationShape.revInclude0..*todomaps to wider conceptExtension.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 R4, since FHIR R5 `SubscriptionTopic` is not mapped. Element `SubscriptionTopic.notificationShape.revInclude` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Source1

{
  "resourceType": "ConceptMap",
  "id": "R5-SubscriptionTopic-element-map-to-R4",
  "text": {
    "status": "generated",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "fhir"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 0,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-SubscriptionTopic-element-map-to-R4",
  "version": "0.1.0",
  "name": "R5SubscriptionTopicElementMapToR4",
  "title": "Cross-version mapping for FHIR R5 SubscriptionTopic to FHIR R4 Basic",
  "status": "active",
  "experimental": false,
  "date": "2026-03-17T16:04:48.3322176-05:00",
  "contact": [
    {
      "name": "FHIR Infrastructure",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/fiwg"
        }
      ]
    }
  ],
  "description": "This ConceptMap represents cross-version mappings for elements from a FHIR R5 SubscriptionTopic to FHIR R4.",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "sourceCanonical": "http://hl7.org/fhir/5.0",
  "targetUri": "http://hl7.org/fhir/4.0",
  "group": [
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/StructureDefinition/Basic",
      "targetVersion": "4.0.1",
      "element": [
        {
          "code": "SubscriptionTopic.meta",
          "display": "meta",
          "target": [
            {
              "code": "Basic.meta",
              "display": "Basic.meta",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead.\nElement `SubscriptionTopic.meta` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.implicitRules",
          "display": "implicitRules",
          "target": [
            {
              "code": "Basic.implicitRules",
              "display": "Basic.implicitRules",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead.\nElement `SubscriptionTopic.implicitRules` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAsserting 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."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.language",
          "display": "language",
          "target": [
            {
              "code": "Basic.language",
              "display": "Basic.language",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead.\nElement `SubscriptionTopic.language` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nLanguage 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)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.text",
          "display": "text",
          "target": [
            {
              "code": "Basic.text",
              "display": "Basic.text",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead.\nElement `SubscriptionTopic.text` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nContained 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."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.contained",
          "display": "contained",
          "target": [
            {
              "code": "Basic.contained",
              "display": "Basic.contained",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead.\nElement `SubscriptionTopic.contained` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThis 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."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.identifier",
          "display": "identifier",
          "target": [
            {
              "code": "Basic.identifier",
              "display": "Basic.identifier",
              "equivalence": "equivalent",
              "comment": "Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead.\nElement `SubscriptionTopic.identifier` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nAn externally-defined extension that has been mapped as the representation of FHIR R5 element `SubscriptionTopic.identifier`: `http://hl7.org/fhir/StructureDefinition/artifact-identifier`.\nNote: 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."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.derivedFrom",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.derivedFrom",
          "display": "derivedFrom",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.derivedFrom` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.derivedFrom` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.jurisdiction",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.jurisdiction",
          "display": "jurisdiction",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.jurisdiction` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nElement `SubscriptionTopic.jurisdiction` has been flagged as deprecated.\nDEPRECATION 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.)"
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.resourceTrigger",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.resourceTrigger",
          "display": "resourceTrigger",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.description",
          "display": "description",
          "target": [
            {
              "code": "Extension.extension:description",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.description` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.description` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nImplementation of particular subscription topics might not use a computable definition and instead base their design on the definition."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.resource",
          "display": "resource",
          "target": [
            {
              "code": "Extension.extension:resource",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.resource` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.resource` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.supportedInteraction",
          "display": "supportedInteraction",
          "target": [
            {
              "code": "Extension.extension:supportedInteraction",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.supportedInteraction` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.supportedInteraction` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.supportedInteraction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria",
          "display": "queryCriteria",
          "target": [
            {
              "code": "Extension.extension:queryCriteria",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria.previous",
          "display": "previous",
          "target": [
            {
              "code": "Extension.extension:queryCriteria.extension:previous",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria.previous` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.previous` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.previous` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (`/`)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate",
          "display": "resultForCreate",
          "target": [
            {
              "code": "Extension.extension:queryCriteria.extension:resultForCreate",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForCreate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria.current",
          "display": "current",
          "target": [
            {
              "code": "Extension.extension:queryCriteria.extension:current",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria.current` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.current` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.current` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nThe rules are search criteria (without the [base] part). Like Bundle.entry.request.url, it has no leading slash character (`/`)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete",
          "display": "resultForDelete",
          "target": [
            {
              "code": "Extension.extension:queryCriteria.extension:resultForDelete",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.resultForDelete` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth",
          "display": "requireBoth",
          "target": [
            {
              "code": "Extension.extension:queryCriteria.extension:requireBoth",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger.queryCriteria` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.queryCriteria.requireBoth` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nPlease 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."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.resourceTrigger.fhirPathCriteria",
          "display": "fhirPathCriteria",
          "target": [
            {
              "code": "Extension.extension:fhirPathCriteria",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.resourceTrigger.fhirPathCriteria` is part of an existing definition because parent element `SubscriptionTopic.resourceTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.resourceTrigger.fhirPathCriteria` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.resourceTrigger.fhirPathCriteria` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nFHIRPath expression with %previous and %current vars."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.eventTrigger",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.eventTrigger",
          "display": "eventTrigger",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.eventTrigger` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.eventTrigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.eventTrigger.description",
          "display": "description",
          "target": [
            {
              "code": "Extension.extension:description",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.eventTrigger.description` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.eventTrigger.description` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.eventTrigger.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nImplementation of particular subscription topics might not use a computable definition and instead base their design on the definition."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.eventTrigger.event",
          "display": "event",
          "target": [
            {
              "code": "Extension.extension:event",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.eventTrigger.event` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.eventTrigger.event` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.eventTrigger.event` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.eventTrigger.resource",
          "display": "resource",
          "target": [
            {
              "code": "Extension.extension:resource",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.eventTrigger.resource` is part of an existing definition because parent element `SubscriptionTopic.eventTrigger` requires a cross-version extension.\nElement `SubscriptionTopic.eventTrigger.resource` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.eventTrigger.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.canFilterBy",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.canFilterBy",
          "display": "canFilterBy",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.description",
          "display": "description",
          "target": [
            {
              "code": "Extension.extension:description",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.description` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.description` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.resource",
          "display": "resource",
          "target": [
            {
              "code": "Extension.extension:resource",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.resource` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.resource` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nURL 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)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.filterParameter",
          "display": "filterParameter",
          "target": [
            {
              "code": "Extension.extension:filterParameter",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.filterParameter` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.filterParameter` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.filterParameter` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nChained parameters are allowed (like \"patient.gender\") - but can not use colons or modifiers."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.filterDefinition",
          "display": "filterDefinition",
          "target": [
            {
              "code": "Extension.extension:filterDefinition",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.filterDefinition` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.filterDefinition` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.filterDefinition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nChained parameters are allowed (like \"patient.gender\") - but can not use colons or modifiers."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.comparator",
          "display": "comparator",
          "target": [
            {
              "code": "Extension.extension:comparator",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.comparator` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.comparator` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.comparator` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nIf no comparators are listed, clients should not expect servers to support any comparators."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.canFilterBy.modifier",
          "display": "modifier",
          "target": [
            {
              "code": "Extension.extension:modifier",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.canFilterBy.modifier` is part of an existing definition because parent element `SubscriptionTopic.canFilterBy` requires a cross-version extension.\nElement `SubscriptionTopic.canFilterBy.modifier` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.canFilterBy.modifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nIf no modifiers are listed, clients should not expect servers to support any modifiers."
            }
          ]
        }
      ]
    },
    {
      "source": "http://hl7.org/fhir/StructureDefinition/SubscriptionTopic",
      "sourceVersion": "5.0.0",
      "target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-SubscriptionTopic.notificationShape",
      "targetVersion": "0.1.0",
      "element": [
        {
          "code": "SubscriptionTopic.notificationShape",
          "display": "notificationShape",
          "target": [
            {
              "code": "Extension",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.notificationShape` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.notificationShape` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.notificationShape.resource",
          "display": "resource",
          "target": [
            {
              "code": "Extension.extension:resource",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.notificationShape.resource` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension.\nElement `SubscriptionTopic.notificationShape.resource` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.notificationShape.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).\nURL 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)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.notificationShape.include",
          "display": "include",
          "target": [
            {
              "code": "Extension.extension:include",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.notificationShape.include` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension.\nElement `SubscriptionTopic.notificationShape.include` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.notificationShape.include` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        },
        {
          "code": "SubscriptionTopic.notificationShape.revInclude",
          "display": "revInclude",
          "target": [
            {
              "code": "Extension.extension:revInclude",
              "equivalence": "wider",
              "comment": "Element `SubscriptionTopic.notificationShape.revInclude` is part of an existing definition because parent element `SubscriptionTopic.notificationShape` requires a cross-version extension.\nElement `SubscriptionTopic.notificationShape.revInclude` is not mapped to FHIR R4, since FHIR R5 `SubscriptionTopic` is not mapped.\nElement `SubscriptionTopic.notificationShape.revInclude` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
            }
          ]
        }
      ]
    }
  ]
}