R4B-ExampleScenario-element-map-to-R3
type: ConceptMap
node role: treeRoot
id:
  v: R4B-ExampleScenario-element-map-to-R3
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4B-ExampleScenario-element-map-to-R3 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2 Source Code Relationship Target Code Comment ExampleScenario.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ExampleScenario.meta` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). ExampleScenario.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ExampleScenario.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. ExampleScenario.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ExampleScenario.language` is not mapped to FHIR STU3, sin…
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: Uri
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3
        l: hl7.fhir.uv.xver-r4b.r3
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: Uri
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4b.r3
        l: hl7.fhir.uv.xver-r4b.r3
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-ExampleScenario-element-map-to-R3
  l: R4B-ExampleScenario-element-map-to-R3
version:
  v: 0.1.0
name:
  v: R4BExampleScenarioElementMapToR3
title:
  v: Cross-version mapping for FHIR R4B ExampleScenario to FHIR STU3 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:04:31.7864903-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 STU3.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Uri
  v: http://hl7.org/fhir/4.3
  l: http://hl7.org/fhir/4.3
target: Uri
  v: http://hl7.org/fhir/3.0
  l: http://hl7.org/fhir/3.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
    l: ExampleScenario
  source version:
    v: 4.3.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 3.0.2
  element:
    code:
      v: ExampleScenario.meta
    display:
      v: meta
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ExampleScenario.meta` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: ExampleScenario.implicitRules
    display:
      v: implicitRules
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ExampleScenario.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.implicitRules` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
  element:
    code:
      v: ExampleScenario.language
    display:
      v: language
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ExampleScenario.language` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.language` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
  element:
    code:
      v: ExampleScenario.text
    display:
      v: text
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ExampleScenario.text` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Contained resources do not have 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:
      modifier extension:
        value: Code
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ExampleScenario.contained` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.contained` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
  element:
    code:
      v: ExampleScenario.identifier
    display:
      v: identifier
    target:
      modifier extension:
        value: Code
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ExampleScenario.identifier` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.identifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
    l: ExampleScenario
  source version:
    v: 4.3.0
  target:
    v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.url
    l: extension-ExampleScenario.url
  target version:
    v: 0.1.0
  element:
    code:
      v: ExampleScenario.url

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

Code
v: equivalent

v: url

modifier extension:
  url:
    v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
    l: extension-ConceptMap.element.target.equivalence
  value: Code
    v: wider
code:
  v: Extension
equivalence:
  v: wider
comment:
  v: Element `ExampleScenario.url` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.url` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.version
  l: extension-ExampleScenario.version
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.version
  display:
    v: version
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.version` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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].

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.name
  l: extension-ExampleScenario.name
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.name
  display:
    v: name
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.status
  l: extension-ExampleScenario.status
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.status
  display:
    v: status
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.status` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of example scenarios that are appropriate for use versus not.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.experimental
  l: extension-ExampleScenario.experimental
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.experimental
  display:
    v: experimental
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.experimental` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.experimental` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of example scenarios that are appropriate for use versus not.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.date
  l: extension-ExampleScenario.date
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.date
  display:
    v: date
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.date` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.date` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.publisher
  l: extension-ExampleScenario.publisher
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.publisher
  display:
    v: publisher
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.publisher` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.publisher` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.contact
  l: extension-ExampleScenario.contact
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.contact
  display:
    v: contact
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.contact` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.contact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.useContext
  l: extension-ExampleScenario.useContext
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.useContext
  display:
    v: useContext
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.useContext` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.useContext` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.jurisdiction
  l: extension-ExampleScenario.jurisdiction
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.jurisdiction
  display:
    v: jurisdiction
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.jurisdiction` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.jurisdiction` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.copyright
  l: extension-ExampleScenario.copyright
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.copyright
  display:
    v: copyright
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.copyright` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.copyright` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.purpose
  l: extension-ExampleScenario.purpose
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.purpose
  display:
    v: purpose
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.purpose` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.purpose` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.actor
  l: extension-ExampleScenario.actor
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.actor
  display:
    v: actor
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.actor` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.actor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.actor.actorId
  display:
    v: actorId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:actorId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.actor.actorId` is part of an existing definition because parent element `ExampleScenario.actor` requires a cross-version extension. Element `ExampleScenario.actor.actorId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.actor.actorId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). should this be called ID or acronym?
element:
  code:
    v: ExampleScenario.actor.type
  display:
    v: type
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.actor.type` is part of an existing definition because parent element `ExampleScenario.actor` requires a cross-version extension. Element `ExampleScenario.actor.type` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.actor.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.actor.name
  display:
    v: name
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:name
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.actor.name` is part of an existing definition because parent element `ExampleScenario.actor` requires a cross-version extension. Element `ExampleScenario.actor.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.actor.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Cardinality: is name and description 1..1?
element:
  code:
    v: ExampleScenario.actor.description
  display:
    v: description
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.actor.description` is part of an existing definition because parent element `ExampleScenario.actor` requires a cross-version extension. Element `ExampleScenario.actor.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.actor.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Cardinality: is name and description 1..1?

source:
  v: http://hl7.org/fhir/StructureDefinition/ExampleScenario
  l: ExampleScenario
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance
  l: extension-ExampleScenario.instance
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance
  display:
    v: instance
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.resourceId
  display:
    v: resourceId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:resourceId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.resourceId` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.resourceId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.resourceId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.resourceType
  display:
    v: resourceType
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:resourceType
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.resourceType` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.resourceType` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.resourceType` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.name
  display:
    v: name
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:name
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.name` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.description
  display:
    v: description
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.description` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.version
  display:
    v: version
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:version
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.version` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.version` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.version` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.version.versionId
  display:
    v: versionId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:version.extension:versionId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.version.versionId` is part of an existing definition because parent element `ExampleScenario.instance.version` requires a cross-version extension. Element `ExampleScenario.instance.version.versionId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.version.versionId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.version.description
  display:
    v: description
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:version.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.version.description` is part of an existing definition because parent element `ExampleScenario.instance.version` requires a cross-version extension. Element `ExampleScenario.instance.version.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.version.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.containedInstance
  display:
    v: containedInstance
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:containedInstance
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.containedInstance` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.containedInstance.resourceId
  display:
    v: resourceId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:containedInstance.extension:resourceId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.containedInstance.resourceId` is part of an existing definition because parent element `ExampleScenario.instance.containedInstance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance.resourceId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance.resourceId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.containedInstance.versionId
  display:
    v: versionId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider

v: Extension.extension:containedInstance.extension:versionId

v: wider

v: Element `ExampleScenario.instance.containedInstance.versionId` is part of an existing definition because parent element `ExampleScenario.instance.containedInstance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance.versionId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance.versionId` has no mapping targets in FHIR STU3. 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: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance
  l: extension-ExampleScenario.instance.containedInstance
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.instance.containedInstance
  display:
    v: containedInstance
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.containedInstance` is part of an existing definition because parent element `ExampleScenario.instance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.containedInstance.resourceId
  display:
    v: resourceId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:resourceId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.containedInstance.resourceId` is part of an existing definition because parent element `ExampleScenario.instance.containedInstance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance.resourceId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance.resourceId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.instance.containedInstance.versionId
  display:
    v: versionId
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:versionId
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.instance.containedInstance.versionId` is part of an existing definition because parent element `ExampleScenario.instance.containedInstance` requires a cross-version extension. Element `ExampleScenario.instance.containedInstance.versionId` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.instance.containedInstance.versionId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.request
  display:
    v: request
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:operation.extension:request
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.request` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.request` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.request` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:request
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.request` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.request` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.request` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.response
  display:
    v: response
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:operation.extension:response
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.response` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.response` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.response` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:response
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.response` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.response` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.response` has no mapping targets in FHIR STU3. 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: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process
  l: extension-ExampleScenario.process
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.process
  display:
    v: process
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.title
  display:
    v: title
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:title
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.title` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.title` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.description
  display:
    v: description
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.description` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.preConditions
  display:
    v: preConditions
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:preConditions
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.preConditions` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.preConditions` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.preConditions` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.postConditions
  display:
    v: postConditions
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:postConditions
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.postConditions` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.postConditions` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.postConditions` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step
  display:
    v: step
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.process
  display:
    v: process
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:process
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.process` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:process
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.process` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.pause
  display:
    v: pause
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:pause
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.pause` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.pause` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.pause` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation
  display:
    v: operation
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:operation
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.operation` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.number
  display:
    v: number
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:step.extension:operation.extension:number
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.number` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.number` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.type
display:
  v: type
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:type
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.type` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.type` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.name
display:
  v: name
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:name
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.name` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.initiator
display:
  v: initiator
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:initiator
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.initiator` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiator` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.receiver
display:
  v: receiver
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:receiver
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.receiver` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiver` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.description
display:
  v: description
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:description
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.description` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.initiatorActive
display:
  v: initiatorActive
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:initiatorActive
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.initiatorActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiatorActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiatorActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.receiverActive
display:
  v: receiverActive
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:receiverActive
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.receiverActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiverActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiverActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.request
display:
  v: request
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:request
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.request` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.request` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.request` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.response
display:
  v: response
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:operation.extension:response
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.response` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.response` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.response` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative
display:
  v: alternative
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:alternative
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.alternative` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.title
display:
  v: title
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:alternative.extension:title
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.title` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.title` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.description
display:
  v: description
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:alternative.extension:description
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.description` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.step
display:
  v: step
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:alternative.extension:step
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.step` has no mapping targets in FHIR STU3. 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: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step
  l: extension-ExampleScenario.process.step
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.process.step
  display:
    v: step
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step` is part of an existing definition because parent element `ExampleScenario.process` requires a cross-version extension. Element `ExampleScenario.process.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.process
  display:
    v: process
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:process
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.process` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.process` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.process` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.pause
  display:
    v: pause
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:pause
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.pause` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.pause` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.pause` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation
  display:
    v: operation
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.operation` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.number
  display:
    v: number
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:number
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.number` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.number` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR STU3. 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:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:type
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.type` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.type` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.name
  display:
    v: name
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:name
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.name` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.name` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.name` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.initiator
  display:
    v: initiator
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:initiator
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.initiator` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiator` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiator` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.receiver
  display:
    v: receiver
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:receiver
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.receiver` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiver` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiver` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.description
  display:
    v: description
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension.extension:operation.extension:description
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.process.step.operation.description` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
element:
  code:
    v: ExampleScenario.process.step.operation.initiatorActive
  display:
    v: initiatorActive
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider

v: Extension.extension:operation.extension:initiatorActive

v: wider

v: Element `ExampleScenario.process.step.operation.initiatorActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.initiatorActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.initiatorActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.receiverActive
display:
  v: receiverActive
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:operation.extension:receiverActive
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.receiverActive` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.receiverActive` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.receiverActive` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.request
display:
  v: request
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:operation.extension:request
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.request` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.request` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.request` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.operation.response
display:
  v: response
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:operation.extension:response
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.operation.response` is part of an existing definition because parent element `ExampleScenario.process.step.operation` requires a cross-version extension. Element `ExampleScenario.process.step.operation.response` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.operation.response` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative
display:
  v: alternative
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:alternative
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative` is part of an existing definition because parent element `ExampleScenario.process.step` requires a cross-version extension. Element `ExampleScenario.process.step.alternative` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.title
display:
  v: title
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:alternative.extension:title
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.title` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.title` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.description
display:
  v: description
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:alternative.extension:description
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.description` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.description` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.description` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

code:
  v: ExampleScenario.process.step.alternative.step
display:
  v: step
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:step.extension:alternative.extension:step
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.step` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
target:
  modifier extension:
    url:
      v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
      l: extension-ConceptMap.element.target.equivalence
    value: Code
      v: wider
  code:
    v: Extension.extension:alternative.extension:step
  equivalence:
    v: wider
  comment:
    v: Element `ExampleScenario.process.step.alternative.step` is part of an existing definition because parent element `ExampleScenario.process.step.alternative` requires a cross-version extension. Element `ExampleScenario.process.step.alternative.step` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.process.step.alternative.step` has no mapping targets in FHIR STU3. 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: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.workflow
  l: extension-ExampleScenario.workflow
target version:
  v: 0.1.0
element:
  code:
    v: ExampleScenario.workflow
  display:
    v: workflow
  target:
    modifier extension:
      url:
        v: http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence
        l: extension-ConceptMap.element.target.equivalence
      value: Code
        v: wider
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ExampleScenario.workflow` is not mapped to FHIR STU3, since FHIR R4B `ExampleScenario` is not mapped. Element `ExampleScenario.workflow` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).