R4B-ExampleScenario-element-map-to-R5
type: ConceptMap
node role: treeRoot
id:
  v: R4B-ExampleScenario-element-map-to-R5
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4B-ExampleScenario-element-map-to-R5 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to ExampleScenarioversion: 5.0.0) Source Code Relationship Target Code Comment ExampleScenario.meta (meta) is equivalent to ExampleScenario.meta Element `ExampleScenario.meta` is mapped to FHIR R5 element `ExampleScenario.meta` as `Equivalent`. ExampleScenario.implicitRules (implicitRules) is equivalent to ExampleScenario.implicitRules Element `ExampleScenario.implicitRules` is mapped to FHIR R5 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 it's narrative along with other profiles, value sets, etc. ExampleScenario.language (language) is equivalent to ExampleScenario.language Element `ExampleScenario.language` is mapped to FHIR R5 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 (…
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-r4b.r5
        l: hl7.fhir.uv.xver-r4b.r5
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-r4b.r5
        l: hl7.fhir.uv.xver-r4b.r5
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-ExampleScenario-element-map-to-R5
  l: R4B-ExampleScenario-element-map-to-R5
version:
  v: 0.1.0
name:
  v: R4BExampleScenarioElementMapToR5
title:
  v: Cross-version mapping for FHIR R4B ExampleScenario to FHIR R5 ExampleScenario
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:03:51.603194-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 R4B ExampleScenario to FHIR R5.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source scope: Canonical
  v: http://hl7.org/fhir/4.3
  l: http://hl7.org/fhir/4.3
target scope: Uri
  v: http://hl7.org/fhir/5.0
  l: http://hl7.org/fhir/5.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
    l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  target:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0
    l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  element:
    code:
      v: ExampleScenario.meta
    display:
      v: meta
    target:
      code:
        v: ExampleScenario.meta
      display:
        v: ExampleScenario.meta
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.meta` is mapped to FHIR R5 element `ExampleScenario.meta` as `Equivalent`.
  element:
    code:
      v: ExampleScenario.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: ExampleScenario.implicitRules
      display:
        v: ExampleScenario.implicitRules
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.implicitRules` is mapped to FHIR R5 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 it's 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
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.language` is mapped to FHIR R5 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
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.text` is mapped to FHIR R5 element `ExampleScenario.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
  element:
    code:
      v: ExampleScenario.contained
    display:
      v: contained
    target:
      code:
        v: ExampleScenario.contained
      display:
        v: ExampleScenario.contained
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.contained` is mapped to FHIR R5 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
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.url` is mapped to FHIR R5 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
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.identifier` is mapped to FHIR R5 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
      relationship:
        v: equivalent
      comment:
        v: Element `ExampleScenario.version` is mapped to FHIR R5 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].
  element:
    code:
      v: ExampleScenario.name

v: name

code:
  v: ExampleScenario.name
display:
  v: ExampleScenario.name
relationship:
  v: equivalent
comment:
  v: Element `ExampleScenario.name` is mapped to FHIR R5 element `ExampleScenario.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

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

code:
  v: ExampleScenario.experimental
display:
  v: experimental
target:
  code:
    v: ExampleScenario.experimental
  display:
    v: ExampleScenario.experimental
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.experimental` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.date` is mapped to FHIR R5 element `ExampleScenario.date` as `Equivalent`. 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.

code:
  v: ExampleScenario.publisher
display:
  v: publisher
target:
  code:
    v: ExampleScenario.publisher
  display:
    v: ExampleScenario.publisher
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.publisher` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.contact` is mapped to FHIR R5 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.

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

code:
  v: ExampleScenario.copyright
display:
  v: copyright
target:
  code:
    v: ExampleScenario.copyright
  display:
    v: ExampleScenario.copyright
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.copyright` is mapped to FHIR R5 element `ExampleScenario.copyright` as `Equivalent`. nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.

code:
  v: ExampleScenario.purpose
display:
  v: purpose
target:
  code:
    v: ExampleScenario.purpose
  display:
    v: ExampleScenario.purpose
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.purpose` is mapped to FHIR R5 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.actor
display:
  v: actor
target:
  code:
    v: ExampleScenario.actor
  display:
    v: ExampleScenario.actor
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.actor` is mapped to FHIR R5 element `ExampleScenario.actor` as `Equivalent`.

code:
  v: ExampleScenario.actor.actorId
display:
  v: actorId
target:
  code:
    v: ExampleScenario.actor.key
  display:
    v: ExampleScenario.actor.key
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.actorId` is mapped to FHIR R5 element `ExampleScenario.actor.key` as `Equivalent`. should this be called ID or acronym?

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

code:
  v: ExampleScenario.actor.name
display:
  v: name
target:
  code:
    v: ExampleScenario.actor.title
  display:
    v: ExampleScenario.actor.title
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.name` is mapped to FHIR R5 element `ExampleScenario.actor.title` as `Equivalent`. Cardinality: is name and description 1..1?

code:
  v: ExampleScenario.actor.description
display:
  v: description
target:
  code:
    v: ExampleScenario.actor.description
  display:
    v: ExampleScenario.actor.description
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.actor.description` is mapped to FHIR R5 element `ExampleScenario.actor.description` as `Equivalent`. Cardinality: is name and description 1..1?

code:
  v: ExampleScenario.instance
display:
  v: instance
target:
  code:
    v: ExampleScenario.instance
  display:
    v: ExampleScenario.instance
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.instance` is mapped to FHIR R5 element `ExampleScenario.instance` as `Equivalent`.

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

code:
  v: ExampleScenario.instance.resourceType
display:
  v: resourceType
target:
  code:
    v: ExampleScenario.instance.structureType
  display:
    v: ExampleScenario.instance.structureType
  relationship:
    v: related-to
  comment:
    v: Element `ExampleScenario.instance.resourceType` is mapped to FHIR R5 element `ExampleScenario.instance.structureType` as `SourceIsNarrowerThanTarget`.

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

code:
  v: ExampleScenario.instance.description
display:
  v: description
target:
  code:
    v: ExampleScenario.instance.description
  display:
    v: ExampleScenario.instance.description
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.description` is mapped to FHIR R5 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
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.instance.version` is mapped to FHIR R5 element `ExampleScenario.instance.version` as `Equivalent`.

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

code:
  v: ExampleScenario.instance.version.description
display:
  v: description
target:
  code:
    v: ExampleScenario.instance.version.description
  display:
    v: ExampleScenario.instance.version.description
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.version.description` is mapped to FHIR R5 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
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance` as `Equivalent`.

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

code:
  v: ExampleScenario.instance.containedInstance.versionId
display:
  v: versionId
target:
  code:
    v: ExampleScenario.instance.containedInstance.versionReference
  display:
    v: ExampleScenario.instance.containedInstance.versionReference
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.instance.containedInstance.versionId` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance.versionReference` as `Equivalent`.

code:
  v: ExampleScenario.process
display:
  v: process
target:
  code:
    v: ExampleScenario.process
  display:
    v: ExampleScenario.process
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process` is mapped to FHIR R5 element `ExampleScenario.process` as `Equivalent`.

code:
  v: ExampleScenario.process.title
display:
  v: title
target:
  code:
    v: ExampleScenario.process.title
  display:
    v: ExampleScenario.process.title
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.title` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.description` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.preConditions` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.postConditions` is mapped to FHIR R5 element `ExampleScenario.process.postConditions` as `Equivalent`.

code:
  v: ExampleScenario.process.step
display:
  v: step
target:
  code:
    v: ExampleScenario.process.step
  display:
    v: ExampleScenario.process.step
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process.step` is mapped to FHIR R5 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
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process.step.process` is mapped to FHIR R5 element `ExampleScenario.process.step.process` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.process` do not cover the following types: ExampleScenario.process.

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

code:
  v: ExampleScenario.process.step.operation
display:
  v: operation
target:
  code:
    v: ExampleScenario.process.step.operation
  display:
    v: ExampleScenario.process.step.operation
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process.step.operation` is mapped to FHIR R5 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
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value.

code:
  v: ExampleScenario.process.step.operation.name
display:
  v: name
target:
  code:
    v: ExampleScenario.process.step.operation.title
  display:
    v: ExampleScenario.process.step.operation.title
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.name` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.title` 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`.

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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`.

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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.description` as `Equivalent`.

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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`.

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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`.

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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 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
  relationship:
    v: source-is-broader-than-target
  comment:
    v: Element `ExampleScenario.process.step.alternative` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R5 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
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.resourceType|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.resourceType
element:
  code:
    v: ExampleScenario.instance.resourceType
  display:
    v: resourceType
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: Element `ExampleScenario.instance.resourceType` is mapped to FHIR R5 element `ExampleScenario.instance.structureType` as `SourceIsNarrowerThanTarget`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process
element:
  code:
    v: ExampleScenario.process
  display:
    v: process
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process` is mapped to FHIR R5 element `ExampleScenario.process` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.title
  display:
    v: title
  target:
    code:
      v: Extension.extension:title
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.title` is mapped to FHIR R5 element `ExampleScenario.process.title` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:description
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.description` is mapped to FHIR R5 element `ExampleScenario.process.description` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.preConditions
  display:
    v: preConditions
  target:
    code:
      v: Extension.extension:preConditions
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.preConditions` is mapped to FHIR R5 element `ExampleScenario.process.preConditions` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.postConditions
  display:
    v: postConditions
  target:
    code:
      v: Extension.extension:postConditions
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.postConditions` is mapped to FHIR R5 element `ExampleScenario.process.postConditions` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step
  display:
    v: step
  target:
    code:
      v: Extension.extension:step
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step` is mapped to FHIR R5 element `ExampleScenario.process.step` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.process
  display:
    v: process
  target:
    code:
      v: Extension.extension:step.extension:process
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.process` is mapped to FHIR R5 element `ExampleScenario.process.step.process` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.process` do not cover the following types: ExampleScenario.process.
element:
  code:
    v: ExampleScenario.process.step.pause
  display:
    v: pause
  target:
    code:
      v: Extension.extension:step.extension:pause
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.pause` is mapped to FHIR R5 element `ExampleScenario.process.step.pause` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation
  display:
    v: operation
  target:
    code:
      v: Extension.extension:step.extension:operation
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation` is mapped to FHIR R5 element `ExampleScenario.process.step.operation` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.number
  display:
    v: number
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:number
    relationship:
      v: source-is-broader-than-target
    comment:
      v: Element `ExampleScenario.process.step.operation.number` has a context of ExampleScenario.process.step.operation based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.type
  display:
    v: type
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:type
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value.
element:
  code:
    v: ExampleScenario.process.step.operation.name
  display:
    v: name
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:name
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.name` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.title` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.initiator
  display:
    v: initiator
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:initiator
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.receiver
  display:
    v: receiver
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:receiver
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.description
  display:
    v: description
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:description
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.description` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.initiatorActive
  display:
    v: initiatorActive
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:initiatorActive
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.receiverActive

v: receiverActive

code:
  v: Extension.extension:step.extension:operation.extension:receiverActive
relationship:
  v: equivalent
comment:
  v: Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`.

code:
  v: ExampleScenario.process.step.operation.request
display:
  v: request
target:
  code:
    v: Extension.extension:step.extension:operation.extension:request
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.request` as `Equivalent`.

code:
  v: ExampleScenario.process.step.operation.response
display:
  v: response
target:
  code:
    v: Extension.extension:step.extension:operation.extension:response
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative
display:
  v: alternative
target:
  code:
    v: Extension.extension:step.extension:alternative
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.title
display:
  v: title
target:
  code:
    v: Extension.extension:step.extension:alternative.extension:title
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.title` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.description
display:
  v: description
target:
  code:
    v: Extension.extension:step.extension:alternative.extension:description
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.description` as `Equivalent`.

code:
  v: ExampleScenario.process.step.alternative.step
display:
  v: step
target:
  code:
    v: Extension.extension:step.extension:alternative.extension:step
  relationship:
    v: equivalent
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step.operation.number|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step.operation.number
element:
  code:
    v: ExampleScenario.process.step.operation.number
  display:
    v: number
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: Element `ExampleScenario.process.step.operation.number` has a context of ExampleScenario.process.step.operation based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step.operation.type|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step.operation.type
element:
  code:
    v: ExampleScenario.process.step.operation.type
  display:
    v: type
  target:
    code:
      v: Extension
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance
element:
  code:
    v: ExampleScenario.process.step.operation.request
  display:
    v: request
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:request
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.request` as `Equivalent`.
element:
  code:
    v: ExampleScenario.process.step.operation.response
  display:
    v: response
  target:
    code:
      v: Extension.extension:step.extension:operation.extension:response
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step
element:
  code:
    v: ExampleScenario.process.step.alternative.step
  display:
    v: step
  target:
    code:
      v: Extension.extension:step.extension:alternative.extension:step
    relationship:
      v: equivalent
    comment:
      v: Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0
  l: http://hl7.org/fhir/StructureDefinition/ExampleScenario
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.workflow|0.1.0
  l: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.workflow
element:
  code:
    v: ExampleScenario.workflow
  display:
    v: workflow
  target:
    code:
      v: Extension
    relationship:
      v: source-is-broader-than-target
    comment:
      v: Element `ExampleScenario.workflow` has a context of ExampleScenario based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.workflow` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).