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, 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). ExampleScenario.text (text) is equivalent to Basic.text 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. ExampleScenario.contained (contained) is equivalent to Basic.contained 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. ExampleScenario.identifier (identifier) is equivalent to Basic.identifier 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 2 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Canonical identifier for this example scenario, represented as a URI (globally unique) (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.url (url) maps to wider concept Extension (R4B: Canonical identifier for this example scenario, represented as a URI (globally unique) (new)) 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. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Business version of the example scenario (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.version (version) maps to wider concept Extension (R4B: Business version of the example scenario (new)) 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]. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Name for this example scenario (computer friendly) (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.name (name) maps to wider concept Extension (R4B: Name for this example scenario (computer friendly) (new)) 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. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: draft | active | retired | unknown (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.status (status) maps to wider concept Extension (R4B: draft | active | retired | unknown (new)) 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. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: For testing purposes, not real usage (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.experimental (experimental) maps to wider concept Extension (R4B: For testing purposes, not real usage (new)) 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. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Date last changed (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.date (date) maps to wider concept Extension (R4B: Date last changed (new)) 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. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Name of the publisher (organization or individual) (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.publisher (publisher) maps to wider concept Extension (R4B: Name of the publisher (organization or individual) (new)) 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. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Contact details for the publisher (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.contact (contact) maps to wider concept Extension (R4B: Contact details for the publisher (new)) 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. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: The context that the content is intended to support (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.useContext (useContext) maps to wider concept Extension (R4B: The context that the content is intended to support (new)) 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Intended jurisdiction for example scenario (if applicable) (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.jurisdiction (jurisdiction) maps to wider concept Extension (R4B: Intended jurisdiction for example scenario (if applicable) (new)) 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. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Use and/or publishing restrictions (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.copyright (copyright) maps to wider concept Extension (R4B: Use and/or publishing restrictions (new)) 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. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: The purpose of the example, e.g. to illustrate a scenario (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.purpose (purpose) maps to wider concept Extension (R4B: The purpose of the example, e.g. to illustrate a scenario (new)) 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. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Actor participating in the resource (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.actor (actor) maps to wider concept Extension (R4B: Actor participating in the resource (new)) 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). ExampleScenario.actor.actorId (actorId) maps to wider concept Extension.extension:actorId (R4B: ID or acronym of the actor (new)) 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? ExampleScenario.actor.type (type) maps to wider concept Extension.extension:type (R4B: person | entity (new)) 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). ExampleScenario.actor.name (name) maps to wider concept Extension.extension:name (R4B: The name of the actor as shown in the page (new)) 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? ExampleScenario.actor.description (description) maps to wider concept Extension.extension:description (R4B: The description of the actor (new)) 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? Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Each resource and each version that is present in the workflow (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance (instance) maps to wider concept Extension (R4B: Each resource and each version that is present in the workflow (new)) 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). ExampleScenario.instance.resourceId (resourceId) maps to wider concept Extension.extension:resourceId (R4B: The id of the resource for referencing (new)) 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). ExampleScenario.instance.resourceType (resourceType) maps to wider concept Extension.extension:resourceType (R4B: The type of the resource (new)) 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). ExampleScenario.instance.name (name) maps to wider concept Extension.extension:name (R4B: A short name for the resource instance (new)) 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). ExampleScenario.instance.description (description) maps to wider concept Extension.extension:description (R4B: Human-friendly description of the resource instance (new)) 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). ExampleScenario.instance.version (version) maps to wider concept Extension.extension:version (R4B: A specific version of the resource (new)) 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). ExampleScenario.instance.version.versionId (versionId) maps to wider concept Extension.extension:version.extension:versionId (R4B: The identifier of a specific version of a resource (new)) 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). ExampleScenario.instance.version.description (description) maps to wider concept Extension.extension:version.extension:description (R4B: The description of the resource version (new)) 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). ExampleScenario.instance.containedInstance (containedInstance) maps to wider concept Extension.extension:containedInstance (R4B: Resources contained in the instance (new)) 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). ExampleScenario.instance.containedInstance.resourceId (resourceId) maps to wider concept Extension.extension:containedInstance.extension:resourceId (R4B: Each resource contained in the instance (new)) 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). ExampleScenario.instance.containedInstance.versionId (versionId) maps to wider concept Extension.extension:containedInstance.extension:versionId (R4B: A specific version of a resource contained in the instance (new)) 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). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Resources contained in the instance (new)version: 0.1.0) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 Codes from R4B: Resources contained in the instance (new) ExampleScenario.instance.containedInstance containedInstance maps to wider concept Extension 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). ExampleScenario.instance.containedInstance.resourceId resourceId maps to wider concept Extension.extension:resourceId 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). ExampleScenario.instance.containedInstance.versionId versionId maps to wider concept Extension.extension:versionId 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). ExampleScenario.process.step.operation.request request maps to wider concept Extension.extension:step.extension:operation.extension:request 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). maps to wider concept Extension.extension:operation.extension:request 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). ExampleScenario.process.step.operation.response response maps to wider concept Extension.extension:step.extension:operation.extension:response 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). maps to wider concept Extension.extension:operation.extension:response 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). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Each major process - a group of operations (new)version: 0.1.0) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 Codes from R4B: Each major process - a group of operations (new) ExampleScenario.process process maps to wider concept Extension 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). ExampleScenario.process.title title maps to wider concept Extension.extension:title 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). ExampleScenario.process.description description maps to wider concept Extension.extension:description 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). ExampleScenario.process.preConditions preConditions maps to wider concept Extension.extension:preConditions 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). ExampleScenario.process.postConditions postConditions maps to wider concept Extension.extension:postConditions 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). ExampleScenario.process.step step maps to wider concept Extension.extension:step 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). ExampleScenario.process.step.process process maps to wider concept Extension.extension:step.extension:process 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). maps to wider concept Extension.extension:process 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). ExampleScenario.process.step.pause pause maps to wider concept Extension.extension:step.extension:pause 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). ExampleScenario.process.step.operation operation maps to wider concept Extension.extension:step.extension:operation 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). ExampleScenario.process.step.operation.number number maps to wider concept Extension.extension:step.extension:operation.extension:number 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). ExampleScenario.process.step.operation.type type maps to wider concept Extension.extension:step.extension:operation.extension:type 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). ExampleScenario.process.step.operation.name name maps to wider concept Extension.extension:step.extension:operation.extension:name 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). ExampleScenario.process.step.operation.initiator initiator maps to wider concept Extension.extension:step.extension:operation.extension:initiator 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). ExampleScenario.process.step.operation.receiver receiver maps to wider concept Extension.extension:step.extension:operation.extension:receiver 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). ExampleScenario.process.step.operation.description description maps to wider concept Extension.extension:step.extension:operation.extension:description 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). ExampleScenario.process.step.operation.initiatorActive initiatorActive maps to wider concept Extension.extension:step.extension:operation.extension:initiatorActive 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). ExampleScenario.process.step.operation.receiverActive receiverActive maps to wider concept Extension.extension:step.extension:operation.extension:receiverActive 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). ExampleScenario.process.step.operation.request request maps to wider concept Extension.extension:step.extension:operation.extension:request 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). ExampleScenario.process.step.operation.response response maps to wider concept Extension.extension:step.extension:operation.extension:response 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). ExampleScenario.process.step.alternative alternative maps to wider concept Extension.extension:step.extension:alternative 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). ExampleScenario.process.step.alternative.title title maps to wider concept Extension.extension:step.extension:alternative.extension:title 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). ExampleScenario.process.step.alternative.description description maps to wider concept Extension.extension:step.extension:alternative.extension:description 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). ExampleScenario.process.step.alternative.step step maps to wider concept Extension.extension:step.extension:alternative.extension:step 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). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Each step of the process (new)version: 0.1.0) Source Concept Details Relationship Target Concept Details Comment Codes from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 Codes from R4B: Each step of the process (new) ExampleScenario.process.step step maps to wider concept Extension 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). ExampleScenario.process.step.process process maps to wider concept Extension.extension:process 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). ExampleScenario.process.step.pause pause maps to wider concept Extension.extension:pause 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). ExampleScenario.process.step.operation operation maps to wider concept Extension.extension:operation 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). ExampleScenario.process.step.operation.number number maps to wider concept Extension.extension:operation.extension:number 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). ExampleScenario.process.step.operation.type type maps to wider concept Extension.extension:operation.extension:type 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). ExampleScenario.process.step.operation.name name maps to wider concept Extension.extension:operation.extension:name 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). ExampleScenario.process.step.operation.initiator initiator maps to wider concept Extension.extension:operation.extension:initiator 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). ExampleScenario.process.step.operation.receiver receiver maps to wider concept Extension.extension:operation.extension:receiver 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). ExampleScenario.process.step.operation.description description maps to wider concept Extension.extension:operation.extension:description 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). ExampleScenario.process.step.operation.initiatorActive initiatorActive maps to wider concept Extension.extension:operation.extension:initiatorActive 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). ExampleScenario.process.step.operation.receiverActive receiverActive maps to wider concept Extension.extension:operation.extension:receiverActive 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). ExampleScenario.process.step.operation.request request maps to wider concept Extension.extension:operation.extension:request 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). ExampleScenario.process.step.operation.response response maps to wider concept Extension.extension:operation.extension:response 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). ExampleScenario.process.step.alternative alternative maps to wider concept Extension.extension:alternative 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). ExampleScenario.process.step.alternative.title title maps to wider concept Extension.extension:alternative.extension:title 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). ExampleScenario.process.step.alternative.description description maps to wider concept Extension.extension:alternative.extension:description 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). ExampleScenario.process.step.alternative.step step maps to wider concept Extension.extension:step.extension:alternative.extension:step 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). maps to wider concept Extension.extension:alternative.extension:step 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). Group 19 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Another nested workflow (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.workflow (workflow) maps to wider concept Extension (R4B: Another nested workflow (new)) 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).
Cross-version mapping for FHIR R4B ExampleScenario to FHIR STU3 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR R4B ExampleScenario to FHIR STU3.
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 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 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 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 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 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.
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.
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].
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 `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 `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 `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 `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?
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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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).
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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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 `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).
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).
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).
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).
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).
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).
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).