R5-ExampleScenario-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R5-ExampleScenario-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R5-ExampleScenario-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to ExampleScenarioversion: 4.0.1) Source Code Relationship Target Code Comment ExampleScenario.meta (meta) is equivalent to ExampleScenario.meta Element `ExampleScenario.meta` is mapped to FHIR R4 element `ExampleScenario.meta` as `Equivalent`. ExampleScenario.implicitRules (implicitRules) is equivalent to ExampleScenario.implicitRules Element `ExampleScenario.implicitRules` is mapped to FHIR R4 element `ExampleScenario.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. 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. ExampleScenario.language (language) is equivalent to ExampleScenario.language Element `ExampleScenario.language` is mapped to FHIR R4 element `ExampleScenario.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 (se…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4
        l: hl7.fhir.uv.xver-r5.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R5-ExampleScenario-element-map-to-R4
  l: R5-ExampleScenario-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R5ExampleScenarioElementMapToR4
title:
  v: Cross-version mapping for FHIR R5 ExampleScenario to FHIR R4 ExampleScenario
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:45.4207812-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR R5 ExampleScenario to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
    l: ExampleScenario
  source version:
    v: 5.0.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
    l: ExampleScenario
  target version:
    v: 4.0.1
  element:
    code:
      v: ExampleScenario.meta
    display:
      v: meta
    target:
      code:
        v: ExampleScenario.meta
      display:
        v: ExampleScenario.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.meta` is mapped to FHIR R4 element `ExampleScenario.meta` as `Equivalent`.
  element:
    code:
      v: ExampleScenario.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: ExampleScenario.implicitRules
      display:
        v: ExampleScenario.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.implicitRules` is mapped to FHIR R4 element `ExampleScenario.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. 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.
  element:
    code:
      v: ExampleScenario.language
    display:
      v: language
    target:
      code:
        v: ExampleScenario.language
      display:
        v: ExampleScenario.language
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.language` is mapped to FHIR R4 element `ExampleScenario.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).
  element:
    code:
      v: ExampleScenario.text
    display:
      v: text
    target:
      code:
        v: ExampleScenario.text
      display:
        v: ExampleScenario.text
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.text` is mapped to FHIR R4 element `ExampleScenario.text` as `Equivalent`. 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.
  element:
    code:
      v: ExampleScenario.contained
    display:
      v: contained
    target:
      code:
        v: ExampleScenario.contained
      display:
        v: ExampleScenario.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.contained` is mapped to FHIR R4 element `ExampleScenario.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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: ExampleScenario.url
    display:
      v: url
    target:
      code:
        v: ExampleScenario.url
      display:
        v: ExampleScenario.url
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.url` is mapped to FHIR R4 element `ExampleScenario.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
  element:
    code:
      v: ExampleScenario.identifier
    display:
      v: identifier
    target:
      code:
        v: ExampleScenario.identifier
      display:
        v: ExampleScenario.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.identifier` is mapped to FHIR R4 element `ExampleScenario.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this example scenario outside of FHIR, where it is not possible to use the logical URI.
  element:
    code:
      v: ExampleScenario.version
    display:
      v: version
    target:
      code:
        v: ExampleScenario.version
      display:
        v: ExampleScenario.version
      equivalence:
        v: equivalent
      comment:
        v: Element `ExampleScenario.version` is mapped to FHIR R4 element `ExampleScenario.version` as `Equivalent`. There may be different example scenario instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the example scenario with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).

code:
  v: ExampleScenario.name
display:
  v: name
target:
  code:
    v: ExampleScenario.name
  display:
    v: ExampleScenario.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.name` is mapped to FHIR R4 element `ExampleScenario.name` as `Equivalent`. Not needed as code will never be generated from one of these

code:
  v: ExampleScenario.status
display:
  v: status
target:
  code:
    v: ExampleScenario.status
  display:
    v: ExampleScenario.status
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.status` is mapped to FHIR R4 element `ExampleScenario.status` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: ExampleScenario.experimental
display:
  v: experimental
target:
  code:
    v: ExampleScenario.experimental
  display:
    v: ExampleScenario.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.experimental` is mapped to FHIR R4 element `ExampleScenario.experimental` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not.

code:
  v: ExampleScenario.date
display:
  v: date
target:
  code:
    v: ExampleScenario.date
  display:
    v: ExampleScenario.date
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.date` is mapped to FHIR R4 element `ExampleScenario.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the example scenario. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: ExampleScenario.publisher
display:
  v: publisher
target:
  code:
    v: ExampleScenario.publisher
  display:
    v: ExampleScenario.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.publisher` is mapped to FHIR R4 element `ExampleScenario.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the example scenario is the organization or individual primarily responsible for the maintenance and upkeep of the example scenario. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the example scenario. This item SHOULD be populated unless the information is available from context.

code:
  v: ExampleScenario.contact
display:
  v: contact
target:
  code:
    v: ExampleScenario.contact
  display:
    v: ExampleScenario.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.contact` is mapped to FHIR R4 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).

code:
  v: ExampleScenario.useContext
display:
  v: useContext
target:
  code:
    v: ExampleScenario.useContext
  display:
    v: ExampleScenario.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.useContext` is mapped to FHIR R4 element `ExampleScenario.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: ExampleScenario.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: ExampleScenario.jurisdiction
  display:
    v: ExampleScenario.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.jurisdiction` is mapped to FHIR R4 element `ExampleScenario.jurisdiction` as `Equivalent`. Element `ExampleScenario.jurisdiction` has been flagged as deprecated. It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended. 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.)

code:
  v: ExampleScenario.purpose
display:
  v: purpose
target:
  code:
    v: ExampleScenario.purpose
  display:
    v: ExampleScenario.purpose
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.purpose` is mapped to FHIR R4 element `ExampleScenario.purpose` as `Equivalent`. This element does not describe the usage of the example scenario. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this example scenario.

code:
  v: ExampleScenario.copyright
display:
  v: copyright
target:
  code:
    v: ExampleScenario.copyright
  display:
    v: ExampleScenario.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.copyright` is mapped to FHIR R4 element `ExampleScenario.copyright` as `Equivalent`. ...

code:
  v: ExampleScenario.actor
display:
  v: actor
target:
  code:
    v: ExampleScenario.actor
  display:
    v: ExampleScenario.actor
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.actor` is mapped to FHIR R4 element `ExampleScenario.actor` as `Equivalent`.

code:
  v: ExampleScenario.actor.key
display:
  v: key
target:
  code:
    v: ExampleScenario.actor.actorId
  display:
    v: ExampleScenario.actor.actorId
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.key` is mapped to FHIR R4 element `ExampleScenario.actor.actorId` as `Equivalent`.

code:
  v: ExampleScenario.actor.type
display:
  v: type
target:
  code:
    v: ExampleScenario.actor.type
  display:
    v: ExampleScenario.actor.type
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.type` is mapped to FHIR R4 element `ExampleScenario.actor.type` as `Equivalent`.

code:
  v: ExampleScenario.actor.title
display:
  v: title
target:
  code:
    v: ExampleScenario.actor.name
  display:
    v: ExampleScenario.actor.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.title` is mapped to FHIR R4 element `ExampleScenario.actor.name` as `Equivalent`.

code:
  v: ExampleScenario.actor.description
display:
  v: description
target:
  code:
    v: ExampleScenario.actor.description
  display:
    v: ExampleScenario.actor.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.description` is mapped to FHIR R4 element `ExampleScenario.actor.description` as `Equivalent`.

code:
  v: ExampleScenario.instance
display:
  v: instance
target:
  code:
    v: ExampleScenario.instance
  display:
    v: ExampleScenario.instance
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.instance` is mapped to FHIR R4 element `ExampleScenario.instance` as `Equivalent`.

code:
  v: ExampleScenario.instance.key
display:
  v: key
target:
  code:
    v: ExampleScenario.instance.resourceId
  display:
    v: ExampleScenario.instance.resourceId
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.key` is mapped to FHIR R4 element `ExampleScenario.instance.resourceId` as `Equivalent`.

code:
  v: ExampleScenario.instance.structureType
display:
  v: structureType
target:
  code:
    v: ExampleScenario.instance.resourceType
  display:
    v: ExampleScenario.instance.resourceType
  equivalence:
    v: relatedto
  comment:
    v: Element `ExampleScenario.instance.structureType` is mapped to FHIR R4 element `ExampleScenario.instance.resourceType` as `RelatedTo`. The mappings for `ExampleScenario.instance.structureType` do not cover the following types: Coding. The mappings for `ExampleScenario.instance.structureType` do not cover the following types based on type expansion: userSelected.

code:
  v: ExampleScenario.instance.title
display:
  v: title
target:
  code:
    v: ExampleScenario.instance.name
  display:
    v: ExampleScenario.instance.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.title` is mapped to FHIR R4 element `ExampleScenario.instance.name` as `Equivalent`.

code:
  v: ExampleScenario.instance.description
display:
  v: description
target:
  code:
    v: ExampleScenario.instance.description
  display:
    v: ExampleScenario.instance.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.description` is mapped to FHIR R4 element `ExampleScenario.instance.description` as `Equivalent`.

code:
  v: ExampleScenario.instance.version
display:
  v: version
target:
  code:
    v: ExampleScenario.instance.version
  display:
    v: ExampleScenario.instance.version
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.instance.version` is mapped to FHIR R4 element `ExampleScenario.instance.version` as `Equivalent`. Not used if an instance doesn't change

code:
  v: ExampleScenario.instance.version.key
display:
  v: key
target:
  code:
    v: ExampleScenario.instance.version.versionId
  display:
    v: ExampleScenario.instance.version.versionId
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.version.key` is mapped to FHIR R4 element `ExampleScenario.instance.version.versionId` as `Equivalent`.

code:
  v: ExampleScenario.instance.version.description
display:
  v: description
target:
  code:
    v: ExampleScenario.instance.version.description
  display:
    v: ExampleScenario.instance.version.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.version.description` is mapped to FHIR R4 element `ExampleScenario.instance.version.description` as `Equivalent`.

code:
  v: ExampleScenario.instance.containedInstance
display:
  v: containedInstance
target:
  code:
    v: ExampleScenario.instance.containedInstance
  display:
    v: ExampleScenario.instance.containedInstance
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance` as `Equivalent`.

code:
  v: ExampleScenario.instance.containedInstance.instanceReference
display:
  v: instanceReference
target:
  code:
    v: ExampleScenario.instance.containedInstance.resourceId
  display:
    v: ExampleScenario.instance.containedInstance.resourceId
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.containedInstance.instanceReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.resourceId` as `Equivalent`.

code:
  v: ExampleScenario.instance.containedInstance.versionReference
display:
  v: versionReference
target:
  code:
    v: ExampleScenario.instance.containedInstance.versionId
  display:
    v: ExampleScenario.instance.containedInstance.versionId
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.containedInstance.versionReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.versionId` as `Equivalent`. Required if the referenced instance has versions

code:
  v: ExampleScenario.process
display:
  v: process
target:
  code:
    v: ExampleScenario.process
  display:
    v: ExampleScenario.process
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process` is mapped to FHIR R4 element `ExampleScenario.process` as `Equivalent`. Some scenarios might describe only one process.

code:
  v: ExampleScenario.process.title
display:
  v: title
target:
  code:
    v: ExampleScenario.process.title
  display:
    v: ExampleScenario.process.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.title` is mapped to FHIR R4 element `ExampleScenario.process.title` as `Equivalent`.

code:
  v: ExampleScenario.process.description
display:
  v: description
target:
  code:
    v: ExampleScenario.process.description
  display:
    v: ExampleScenario.process.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.description` is mapped to FHIR R4 element `ExampleScenario.process.description` as `Equivalent`.

code:
  v: ExampleScenario.process.preConditions
display:
  v: preConditions
target:
  code:
    v: ExampleScenario.process.preConditions
  display:
    v: ExampleScenario.process.preConditions
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.preConditions` is mapped to FHIR R4 element `ExampleScenario.process.preConditions` as `Equivalent`.

code:
  v: ExampleScenario.process.postConditions
display:
  v: postConditions
target:
  code:
    v: ExampleScenario.process.postConditions
  display:
    v: ExampleScenario.process.postConditions
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.postConditions` is mapped to FHIR R4 element `ExampleScenario.process.postConditions` as `Equivalent`. Alternate steps might not result in all post conditions holding

code:
  v: ExampleScenario.process.step
display:
  v: step
target:
  code:
    v: ExampleScenario.process.step
  display:
    v: ExampleScenario.process.step
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step` is mapped to FHIR R4 element `ExampleScenario.process.step` as `Equivalent`.

code:
  v: ExampleScenario.process.step.process
display:
  v: process
target:
  code:
    v: ExampleScenario.process.step.process
  display:
    v: ExampleScenario.process.step.process
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.process` is mapped to FHIR R4 element `ExampleScenario.process.step.process` as `SourceIsNarrowerThanTarget`.

code:
  v: ExampleScenario.process.step.operation
display:
  v: operation
target:
  code:
    v: ExampleScenario.process.step.operation
  display:
    v: ExampleScenario.process.step.operation
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation` is mapped to FHIR R4 element `ExampleScenario.process.step.operation` as `Equivalent`.

code:
  v: ExampleScenario.process.step.operation.type
display:
  v: type
target:
  code:
    v: ExampleScenario.process.step.operation.type
  display:
    v: ExampleScenario.process.step.operation.type
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: Coding. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: userSelected.

code:
  v: ExampleScenario.process.step.operation.title
display:
  v: title
target:
  code:
    v: ExampleScenario.process.step.operation.name
  display:
    v: ExampleScenario.process.step.operation.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.title` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.name` as `Equivalent`.

code:
  v: ExampleScenario.process.step.operation.initiator
display:
  v: initiator
target:
  code:
    v: ExampleScenario.process.step.operation.initiator
  display:
    v: ExampleScenario.process.step.operation.initiator
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the initiator is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.)

code:
  v: ExampleScenario.process.step.operation.receiver
display:
  v: receiver
target:
  code:
    v: ExampleScenario.process.step.operation.receiver
  display:
    v: ExampleScenario.process.step.operation.receiver
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the receiver is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.) In some cases, receiver could be same as sender if representing a local operation

code:
  v: ExampleScenario.process.step.operation.description
display:
  v: description
target:
  code:
    v: ExampleScenario.process.step.operation.description
  display:
    v: ExampleScenario.process.step.operation.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.description` as `Equivalent`. This should contain information not already present in the process step. It's more of a description of what the operation in general does - if not already evident from the operation.type

code:
  v: ExampleScenario.process.step.operation.initiatorActive
display:
  v: initiatorActive
target:
  code:
    v: ExampleScenario.process.step.operation.initiatorActive
  display:
    v: ExampleScenario.process.step.operation.initiatorActive
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation.

code:
  v: ExampleScenario.process.step.operation.receiverActive
display:
  v: receiverActive
target:
  code:
    v: ExampleScenario.process.step.operation.receiverActive
  display:
    v: ExampleScenario.process.step.operation.receiverActive
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation.

code:
  v: ExampleScenario.process.step.operation.request
display:
  v: request
target:
  code:
    v: ExampleScenario.process.step.operation.request
  display:
    v: ExampleScenario.process.step.operation.request
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.request` as `Equivalent`.

code:
  v: ExampleScenario.process.step.operation.response
display:
  v: response
target:
  code:
    v: ExampleScenario.process.step.operation.response
  display:
    v: ExampleScenario.process.step.operation.response
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.response` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative
display:
  v: alternative
target:
  code:
    v: ExampleScenario.process.step.alternative
  display:
    v: ExampleScenario.process.step.alternative
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.title
display:
  v: title
target:
  code:
    v: ExampleScenario.process.step.alternative.title
  display:
    v: ExampleScenario.process.step.alternative.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.title` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.description
display:
  v: description
target:
  code:
    v: ExampleScenario.process.step.alternative.description
  display:
    v: ExampleScenario.process.step.alternative.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.description` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.step
display:
  v: step
target:
  code:
    v: ExampleScenario.process.step.alternative.step
  display:
    v: ExampleScenario.process.step.alternative.step
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.

code:
  v: ExampleScenario.process.step.pause
display:
  v: pause
target:
  code:
    v: ExampleScenario.process.step.pause
  display:
    v: ExampleScenario.process.step.pause
  equivalence:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.pause` is mapped to FHIR R4 element `ExampleScenario.process.step.pause` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.structureType
  l: extension-ExampleScenario.instance.structureType
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.structureType
  display:
    v: structureType
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.structureType` is mapped to FHIR R4 element `ExampleScenario.instance.resourceType` as `RelatedTo`. The mappings for `ExampleScenario.instance.structureType` do not cover the following types: Coding. The mappings for `ExampleScenario.instance.structureType` do not cover the following types based on type expansion: userSelected.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.structureVersion
  l: extension-ExampleScenario.instance.structureVersion
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.structureVersion
  display:
    v: structureVersion
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.structureVersion` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureVersion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.structureProfile
  l: extension-ExampleScenario.instance.structureProfile
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.structureProfile[x]
  display:
    v: structureProfile[x]
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.structureProfile[x]` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureProfile[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.content
  l: extension-ExampleScenario.instance.content
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.content
  display:
    v: content
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.content` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.version.title
  l: extension-ExampleScenario.instance.version.title
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.version.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.version.title` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.instance.version.content
  l: extension-ExampleScenario.instance.version.content
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.version.content
  display:
    v: content
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.version.content` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.process.step.number
  l: extension-ExampleScenario.process.step.number
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.process.step.number
  display:
    v: number
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.number` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.number` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If step numbers are simultaneous, they will be the same. Numbers don't have to be numeric. E.g. '2c)' is a valid step number

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.process.step.workflow
  l: extension-ExampleScenario.process.step.workflow
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.process.step.workflow
  display:
    v: workflow
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.workflow` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.workflow` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 5.0.0
target:
  v: http://hl7.org/fhir/5.0/StructureDefinition/extension-ExampleScenario.process.step.operation.type
  l: extension-ExampleScenario.process.step.operation.type
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.process.step.operation.type
  display:
    v: type
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: Coding. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: userSelected.