Generated Narrative: ConceptMap R5-ExampleScenario-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to ExampleScenarioversion: 4.0.1) Source Code Relationship Target Code Comment ExampleScenario.meta (meta) is equivalent to ExampleScenario.meta Element `ExampleScenario.meta` is mapped to FHIR R4 element `ExampleScenario.meta` as `Equivalent`. ExampleScenario.implicitRules (implicitRules) is equivalent to ExampleScenario.implicitRules Element `ExampleScenario.implicitRules` is mapped to FHIR R4 element `ExampleScenario.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. ExampleScenario.language (language) is equivalent to ExampleScenario.language Element `ExampleScenario.language` is mapped to FHIR R4 element `ExampleScenario.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). ExampleScenario.text (text) is equivalent to ExampleScenario.text Element `ExampleScenario.text` is mapped to FHIR R4 element `ExampleScenario.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. ExampleScenario.contained (contained) is equivalent to ExampleScenario.contained Element `ExampleScenario.contained` is mapped to FHIR R4 element `ExampleScenario.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. ExampleScenario.url (url) is equivalent to ExampleScenario.url Element `ExampleScenario.url` is mapped to FHIR R4 element `ExampleScenario.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found. ExampleScenario.identifier (identifier) is equivalent to ExampleScenario.identifier Element `ExampleScenario.identifier` is mapped to FHIR R4 element `ExampleScenario.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this example scenario outside of FHIR, where it is not possible to use the logical URI. ExampleScenario.version (version) is equivalent to ExampleScenario.version Element `ExampleScenario.version` is mapped to FHIR R4 element `ExampleScenario.version` as `Equivalent`. There may be different example scenario instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the example scenario with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format). ExampleScenario.name (name) is equivalent to ExampleScenario.name Element `ExampleScenario.name` is mapped to FHIR R4 element `ExampleScenario.name` as `Equivalent`. Not needed as code will never be generated from one of these ExampleScenario.status (status) is equivalent to ExampleScenario.status Element `ExampleScenario.status` is mapped to FHIR R4 element `ExampleScenario.status` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ExampleScenario.experimental (experimental) is equivalent to ExampleScenario.experimental Element `ExampleScenario.experimental` is mapped to FHIR R4 element `ExampleScenario.experimental` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. ExampleScenario.date (date) is equivalent to ExampleScenario.date Element `ExampleScenario.date` is mapped to FHIR R4 element `ExampleScenario.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the example scenario. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ExampleScenario.publisher (publisher) is equivalent to ExampleScenario.publisher Element `ExampleScenario.publisher` is mapped to FHIR R4 element `ExampleScenario.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the example scenario is the organization or individual primarily responsible for the maintenance and upkeep of the example scenario. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the example scenario. This item SHOULD be populated unless the information is available from context. ExampleScenario.contact (contact) is equivalent to ExampleScenario.contact Element `ExampleScenario.contact` is mapped to FHIR R4 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). ExampleScenario.useContext (useContext) is equivalent to ExampleScenario.useContext Element `ExampleScenario.useContext` is mapped to FHIR R4 element `ExampleScenario.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. ExampleScenario.jurisdiction (jurisdiction) is equivalent to ExampleScenario.jurisdiction Element `ExampleScenario.jurisdiction` is mapped to FHIR R4 element `ExampleScenario.jurisdiction` as `Equivalent`. Element `ExampleScenario.jurisdiction` has been flagged as deprecated. It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.) ExampleScenario.purpose (purpose) is equivalent to ExampleScenario.purpose Element `ExampleScenario.purpose` is mapped to FHIR R4 element `ExampleScenario.purpose` as `Equivalent`. This element does not describe the usage of the example scenario. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this example scenario. ExampleScenario.copyright (copyright) is equivalent to ExampleScenario.copyright Element `ExampleScenario.copyright` is mapped to FHIR R4 element `ExampleScenario.copyright` as `Equivalent`. ... ExampleScenario.actor (actor) maps to wider concept ExampleScenario.actor Element `ExampleScenario.actor` is mapped to FHIR R4 element `ExampleScenario.actor` as `Equivalent`. ExampleScenario.actor.key (key) is equivalent to ExampleScenario.actor.actorId Element `ExampleScenario.actor.key` is mapped to FHIR R4 element `ExampleScenario.actor.actorId` as `Equivalent`. ExampleScenario.actor.type (type) is equivalent to ExampleScenario.actor.type Element `ExampleScenario.actor.type` is mapped to FHIR R4 element `ExampleScenario.actor.type` as `Equivalent`. ExampleScenario.actor.title (title) is equivalent to ExampleScenario.actor.name Element `ExampleScenario.actor.title` is mapped to FHIR R4 element `ExampleScenario.actor.name` as `Equivalent`. ExampleScenario.actor.description (description) is equivalent to ExampleScenario.actor.description Element `ExampleScenario.actor.description` is mapped to FHIR R4 element `ExampleScenario.actor.description` as `Equivalent`. ExampleScenario.instance (instance) maps to wider concept ExampleScenario.instance Element `ExampleScenario.instance` is mapped to FHIR R4 element `ExampleScenario.instance` as `Equivalent`. ExampleScenario.instance.key (key) is equivalent to ExampleScenario.instance.resourceId Element `ExampleScenario.instance.key` is mapped to FHIR R4 element `ExampleScenario.instance.resourceId` as `Equivalent`. ExampleScenario.instance.structureType (structureType) is related to ExampleScenario.instance.resourceType Element `ExampleScenario.instance.structureType` is mapped to FHIR R4 element `ExampleScenario.instance.resourceType` as `RelatedTo`. The mappings for `ExampleScenario.instance.structureType` do not cover the following types: Coding. The mappings for `ExampleScenario.instance.structureType` do not cover the following types based on type expansion: userSelected. ExampleScenario.instance.title (title) is equivalent to ExampleScenario.instance.name Element `ExampleScenario.instance.title` is mapped to FHIR R4 element `ExampleScenario.instance.name` as `Equivalent`. ExampleScenario.instance.description (description) is equivalent to ExampleScenario.instance.description Element `ExampleScenario.instance.description` is mapped to FHIR R4 element `ExampleScenario.instance.description` as `Equivalent`. ExampleScenario.instance.version (version) maps to wider concept ExampleScenario.instance.version Element `ExampleScenario.instance.version` is mapped to FHIR R4 element `ExampleScenario.instance.version` as `Equivalent`. Not used if an instance doesn't change ExampleScenario.instance.version.key (key) is equivalent to ExampleScenario.instance.version.versionId Element `ExampleScenario.instance.version.key` is mapped to FHIR R4 element `ExampleScenario.instance.version.versionId` as `Equivalent`. ExampleScenario.instance.version.description (description) is equivalent to ExampleScenario.instance.version.description Element `ExampleScenario.instance.version.description` is mapped to FHIR R4 element `ExampleScenario.instance.version.description` as `Equivalent`. ExampleScenario.instance.containedInstance (containedInstance) maps to wider concept ExampleScenario.instance.containedInstance Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance` as `Equivalent`. ExampleScenario.instance.containedInstance.instanceReference (instanceReference) is equivalent to ExampleScenario.instance.containedInstance.resourceId Element `ExampleScenario.instance.containedInstance.instanceReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.resourceId` as `Equivalent`. ExampleScenario.instance.containedInstance.versionReference (versionReference) is equivalent to ExampleScenario.instance.containedInstance.versionId Element `ExampleScenario.instance.containedInstance.versionReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.versionId` as `Equivalent`. Required if the referenced instance has versions ExampleScenario.process (process) maps to wider concept ExampleScenario.process Element `ExampleScenario.process` is mapped to FHIR R4 element `ExampleScenario.process` as `Equivalent`. Some scenarios might describe only one process. ExampleScenario.process.title (title) is equivalent to ExampleScenario.process.title Element `ExampleScenario.process.title` is mapped to FHIR R4 element `ExampleScenario.process.title` as `Equivalent`. ExampleScenario.process.description (description) is equivalent to ExampleScenario.process.description Element `ExampleScenario.process.description` is mapped to FHIR R4 element `ExampleScenario.process.description` as `Equivalent`. ExampleScenario.process.preConditions (preConditions) is equivalent to ExampleScenario.process.preConditions Element `ExampleScenario.process.preConditions` is mapped to FHIR R4 element `ExampleScenario.process.preConditions` as `Equivalent`. ExampleScenario.process.postConditions (postConditions) is equivalent to ExampleScenario.process.postConditions Element `ExampleScenario.process.postConditions` is mapped to FHIR R4 element `ExampleScenario.process.postConditions` as `Equivalent`. Alternate steps might not result in all post conditions holding ExampleScenario.process.step (step) maps to wider concept ExampleScenario.process.step Element `ExampleScenario.process.step` is mapped to FHIR R4 element `ExampleScenario.process.step` as `Equivalent`. ExampleScenario.process.step.process (process) is equivalent to ExampleScenario.process.step.process Element `ExampleScenario.process.step.process` is mapped to FHIR R4 element `ExampleScenario.process.step.process` as `SourceIsNarrowerThanTarget`. ExampleScenario.process.step.operation (operation) maps to wider concept ExampleScenario.process.step.operation Element `ExampleScenario.process.step.operation` is mapped to FHIR R4 element `ExampleScenario.process.step.operation` as `Equivalent`. ExampleScenario.process.step.operation.type (type) maps to wider concept ExampleScenario.process.step.operation.type Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: Coding. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: userSelected. ExampleScenario.process.step.operation.title (title) is equivalent to ExampleScenario.process.step.operation.name Element `ExampleScenario.process.step.operation.title` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.name` as `Equivalent`. ExampleScenario.process.step.operation.initiator (initiator) is equivalent to ExampleScenario.process.step.operation.initiator Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the initiator is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.) ExampleScenario.process.step.operation.receiver (receiver) is equivalent to ExampleScenario.process.step.operation.receiver Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the receiver is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.) In some cases, receiver could be same as sender if representing a local operation ExampleScenario.process.step.operation.description (description) is equivalent to ExampleScenario.process.step.operation.description Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.description` as `Equivalent`. This should contain information not already present in the process step. It's more of a description of what the operation in general does - if not already evident from the operation.type ExampleScenario.process.step.operation.initiatorActive (initiatorActive) is equivalent to ExampleScenario.process.step.operation.initiatorActive Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation. ExampleScenario.process.step.operation.receiverActive (receiverActive) is equivalent to ExampleScenario.process.step.operation.receiverActive Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation. ExampleScenario.process.step.operation.request (request) is equivalent to ExampleScenario.process.step.operation.request Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.request` as `Equivalent`. ExampleScenario.process.step.operation.response (response) is equivalent to ExampleScenario.process.step.operation.response Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.response` as `Equivalent`. ExampleScenario.process.step.alternative (alternative) maps to wider concept ExampleScenario.process.step.alternative Element `ExampleScenario.process.step.alternative` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative` as `Equivalent`. ExampleScenario.process.step.alternative.title (title) is equivalent to ExampleScenario.process.step.alternative.title Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.title` as `Equivalent`. ExampleScenario.process.step.alternative.description (description) is equivalent to ExampleScenario.process.step.alternative.description Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.description` as `Equivalent`. ExampleScenario.process.step.alternative.step (step) is equivalent to ExampleScenario.process.step.alternative.step Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.step` as `Equivalent`. ExampleScenario.process.step.pause (pause) is equivalent to ExampleScenario.process.step.pause Element `ExampleScenario.process.step.pause` is mapped to FHIR R4 element `ExampleScenario.process.step.pause` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Data structure for example additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.structureType (structureType) maps to wider concept Extension (R5: Data structure for example additional types) Element `ExampleScenario.instance.structureType` is mapped to FHIR R4 element `ExampleScenario.instance.resourceType` as `RelatedTo`. The mappings for `ExampleScenario.instance.structureType` do not cover the following types: Coding. The mappings for `ExampleScenario.instance.structureType` do not cover the following types based on type expansion: userSelected. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: E.g. 4.0.1 (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.structureVersion (structureVersion) maps to wider concept Extension (R5: E.g. 4.0.1 (new)) Element `ExampleScenario.instance.structureVersion` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureVersion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Rules instance adheres to (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.structureProfile[x] (structureProfile[x]) maps to wider concept Extension (R5: Rules instance adheres to (new)) Element `ExampleScenario.instance.structureProfile[x]` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureProfile[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Example instance data (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.content (content) maps to wider concept Extension (R5: Example instance data (new)) Element `ExampleScenario.instance.content` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Label for instance version (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.version.title (title) maps to wider concept Extension (R5: Label for instance version (new)) Element `ExampleScenario.instance.version.title` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Example instance version data (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.version.content (content) maps to wider concept Extension (R5: Example instance version data (new)) Element `ExampleScenario.instance.version.content` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Sequential number of the step (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process.step.number (number) maps to wider concept Extension (R5: Sequential number of the step (new)) Element `ExampleScenario.process.step.number` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.number` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If step numbers are simultaneous, they will be the same. Numbers don't have to be numeric. E.g. '2c)' is a valid step number Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Step is nested workflow (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process.step.workflow (workflow) maps to wider concept Extension (R5: Step is nested workflow (new)) Element `ExampleScenario.process.step.workflow` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.workflow` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|5.0.0 to R5: Kind of action additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process.step.operation.type (type) is equivalent to Extension (R5: Kind of action additional types) Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: Coding. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: userSelected.
Cross-version mapping for FHIR R5 ExampleScenario to FHIR R4 ExampleScenario
This ConceptMap represents cross-version mappings for elements from a FHIR R5 ExampleScenario to FHIR R4.
Element `ExampleScenario.meta` is mapped to FHIR R4 element `ExampleScenario.meta` as `Equivalent`.
Element `ExampleScenario.implicitRules` is mapped to FHIR R4 element `ExampleScenario.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
Element `ExampleScenario.language` is mapped to FHIR R4 element `ExampleScenario.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `ExampleScenario.text` is mapped to FHIR R4 element `ExampleScenario.text` as `Equivalent`. Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element `ExampleScenario.contained` is mapped to FHIR R4 element `ExampleScenario.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Element `ExampleScenario.url` is mapped to FHIR R4 element `ExampleScenario.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
Element `ExampleScenario.identifier` is mapped to FHIR R4 element `ExampleScenario.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this example scenario outside of FHIR, where it is not possible to use the logical URI.
Element `ExampleScenario.version` is mapped to FHIR R4 element `ExampleScenario.version` as `Equivalent`. There may be different example scenario instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the example scenario with the format [url]|[version]. The version SHOULD NOT contain a '#' - see [Business Version](https://hl7.org/fhir/resource.h.html#bv-format).
Element `ExampleScenario.name` is mapped to FHIR R4 element `ExampleScenario.name` as `Equivalent`. Not needed as code will never be generated from one of these
Element `ExampleScenario.status` is mapped to FHIR R4 element `ExampleScenario.status` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ExampleScenario.experimental` is mapped to FHIR R4 element `ExampleScenario.experimental` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not.
Element `ExampleScenario.date` is mapped to FHIR R4 element `ExampleScenario.date` as `Equivalent`. The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the example scenario. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ExampleScenario.publisher` is mapped to FHIR R4 element `ExampleScenario.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the example scenario is the organization or individual primarily responsible for the maintenance and upkeep of the example scenario. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the example scenario. This item SHOULD be populated unless the information is available from context.
Element `ExampleScenario.contact` is mapped to FHIR R4 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `ExampleScenario.useContext` is mapped to FHIR R4 element `ExampleScenario.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `ExampleScenario.jurisdiction` is mapped to FHIR R4 element `ExampleScenario.jurisdiction` as `Equivalent`. Element `ExampleScenario.jurisdiction` has been flagged as deprecated. It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended. DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.)
Element `ExampleScenario.purpose` is mapped to FHIR R4 element `ExampleScenario.purpose` as `Equivalent`. This element does not describe the usage of the example scenario. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this example scenario.
Element `ExampleScenario.copyright` is mapped to FHIR R4 element `ExampleScenario.copyright` as `Equivalent`. ...
Element `ExampleScenario.actor` is mapped to FHIR R4 element `ExampleScenario.actor` as `Equivalent`.
Element `ExampleScenario.actor.key` is mapped to FHIR R4 element `ExampleScenario.actor.actorId` as `Equivalent`.
Element `ExampleScenario.actor.type` is mapped to FHIR R4 element `ExampleScenario.actor.type` as `Equivalent`.
Element `ExampleScenario.actor.title` is mapped to FHIR R4 element `ExampleScenario.actor.name` as `Equivalent`.
Element `ExampleScenario.actor.description` is mapped to FHIR R4 element `ExampleScenario.actor.description` as `Equivalent`.
Element `ExampleScenario.instance` is mapped to FHIR R4 element `ExampleScenario.instance` as `Equivalent`.
Element `ExampleScenario.instance.key` is mapped to FHIR R4 element `ExampleScenario.instance.resourceId` as `Equivalent`.
Element `ExampleScenario.instance.structureType` is mapped to FHIR R4 element `ExampleScenario.instance.resourceType` as `RelatedTo`. The mappings for `ExampleScenario.instance.structureType` do not cover the following types: Coding. The mappings for `ExampleScenario.instance.structureType` do not cover the following types based on type expansion: userSelected.
Element `ExampleScenario.instance.title` is mapped to FHIR R4 element `ExampleScenario.instance.name` as `Equivalent`.
Element `ExampleScenario.instance.description` is mapped to FHIR R4 element `ExampleScenario.instance.description` as `Equivalent`.
Element `ExampleScenario.instance.version` is mapped to FHIR R4 element `ExampleScenario.instance.version` as `Equivalent`. Not used if an instance doesn't change
Element `ExampleScenario.instance.version.key` is mapped to FHIR R4 element `ExampleScenario.instance.version.versionId` as `Equivalent`.
Element `ExampleScenario.instance.version.description` is mapped to FHIR R4 element `ExampleScenario.instance.version.description` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance.instanceReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.resourceId` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance.versionReference` is mapped to FHIR R4 element `ExampleScenario.instance.containedInstance.versionId` as `Equivalent`. Required if the referenced instance has versions
Element `ExampleScenario.process` is mapped to FHIR R4 element `ExampleScenario.process` as `Equivalent`. Some scenarios might describe only one process.
Element `ExampleScenario.process.title` is mapped to FHIR R4 element `ExampleScenario.process.title` as `Equivalent`.
Element `ExampleScenario.process.description` is mapped to FHIR R4 element `ExampleScenario.process.description` as `Equivalent`.
Element `ExampleScenario.process.preConditions` is mapped to FHIR R4 element `ExampleScenario.process.preConditions` as `Equivalent`.
Element `ExampleScenario.process.postConditions` is mapped to FHIR R4 element `ExampleScenario.process.postConditions` as `Equivalent`. Alternate steps might not result in all post conditions holding
Element `ExampleScenario.process.step` is mapped to FHIR R4 element `ExampleScenario.process.step` as `Equivalent`.
Element `ExampleScenario.process.step.process` is mapped to FHIR R4 element `ExampleScenario.process.step.process` as `SourceIsNarrowerThanTarget`.
Element `ExampleScenario.process.step.operation` is mapped to FHIR R4 element `ExampleScenario.process.step.operation` as `Equivalent`.
Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: Coding. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: userSelected.
Element `ExampleScenario.process.step.operation.title` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.name` as `Equivalent`.
Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the initiator is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.)
Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`. This must either be the 'key' of one of the actors defined in this scenario or the special keyword 'OTHER' if the receiver is not one of the actors defined for the scenario. (Multiple references to 'OTHER' don't necessarily indicate the same actor.) In some cases, receiver could be same as sender if representing a local operation
Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.description` as `Equivalent`. This should contain information not already present in the process step. It's more of a description of what the operation in general does - if not already evident from the operation.type
Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation.
Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`. De-activation of an actor means they have no further role until such time as they are the recipient of an operation.
Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.request` as `Equivalent`.
Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R4 element `ExampleScenario.process.step.operation.response` as `Equivalent`.
Element `ExampleScenario.process.step.alternative` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.title` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.description` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R4 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.
Element `ExampleScenario.process.step.pause` is mapped to FHIR R4 element `ExampleScenario.process.step.pause` as `Equivalent`.
Element `ExampleScenario.instance.structureVersion` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureVersion` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.instance.structureProfile[x]` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.structureProfile[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.instance.content` has a context of ExampleScenario.instance based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary.
Element `ExampleScenario.instance.version.title` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.instance.version.content` has a context of ExampleScenario.instance.version based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.instance.version.content` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If not conveying FHIR data or not using the same version of FHIR as this ExampleScenario instance, the reference must be to a Binary.
Element `ExampleScenario.process.step.number` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.number` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If step numbers are simultaneous, they will be the same. Numbers don't have to be numeric. E.g. '2c)' is a valid step number
Element `ExampleScenario.process.step.workflow` has a context of ExampleScenario.process.step based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.workflow` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).