Generated Narrative: ConceptMap R4B-ExampleScenario-element-map-to-R5 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to ExampleScenarioversion: 5.0.0) Source Code Relationship Target Code Comment ExampleScenario.meta (meta) is equivalent to ExampleScenario.meta Element `ExampleScenario.meta` is mapped to FHIR R5 element `ExampleScenario.meta` as `Equivalent`. ExampleScenario.implicitRules (implicitRules) is equivalent to ExampleScenario.implicitRules Element `ExampleScenario.implicitRules` is mapped to FHIR R5 element `ExampleScenario.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. ExampleScenario.language (language) is equivalent to ExampleScenario.language Element `ExampleScenario.language` is mapped to FHIR R5 element `ExampleScenario.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (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 R5 element `ExampleScenario.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. ExampleScenario.contained (contained) is equivalent to ExampleScenario.contained Element `ExampleScenario.contained` is mapped to FHIR R5 element `ExampleScenario.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. ExampleScenario.url (url) is equivalent to ExampleScenario.url Element `ExampleScenario.url` is mapped to FHIR R5 element `ExampleScenario.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found. ExampleScenario.identifier (identifier) is equivalent to ExampleScenario.identifier Element `ExampleScenario.identifier` is mapped to FHIR R5 element `ExampleScenario.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this example scenario outside of FHIR, where it is not possible to use the logical URI. ExampleScenario.version (version) is equivalent to ExampleScenario.version Element `ExampleScenario.version` is mapped to FHIR R5 element `ExampleScenario.version` as `Equivalent`. There may be different example scenario instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the example scenario with the format [url]|[version]. ExampleScenario.name (name) is equivalent to ExampleScenario.name Element `ExampleScenario.name` is mapped to FHIR R5 element `ExampleScenario.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly. ExampleScenario.status (status) is equivalent to ExampleScenario.status Element `ExampleScenario.status` is mapped to FHIR R5 element `ExampleScenario.status` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. ExampleScenario.experimental (experimental) is equivalent to ExampleScenario.experimental Element `ExampleScenario.experimental` is mapped to FHIR R5 element `ExampleScenario.experimental` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not. ExampleScenario.date (date) is equivalent to ExampleScenario.date Element `ExampleScenario.date` is mapped to FHIR R5 element `ExampleScenario.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the example scenario. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. ExampleScenario.publisher (publisher) is equivalent to ExampleScenario.publisher Element `ExampleScenario.publisher` is mapped to FHIR R5 element `ExampleScenario.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the example scenario is the organization or individual primarily responsible for the maintenance and upkeep of the example scenario. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the example scenario. This item SHOULD be populated unless the information is available from context. ExampleScenario.contact (contact) is equivalent to ExampleScenario.contact Element `ExampleScenario.contact` is mapped to FHIR R5 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. ExampleScenario.useContext (useContext) is equivalent to ExampleScenario.useContext Element `ExampleScenario.useContext` is mapped to FHIR R5 element `ExampleScenario.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. ExampleScenario.jurisdiction (jurisdiction) is equivalent to ExampleScenario.jurisdiction Element `ExampleScenario.jurisdiction` is mapped to FHIR R5 element `ExampleScenario.jurisdiction` as `Equivalent`. It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended. ExampleScenario.copyright (copyright) is equivalent to ExampleScenario.copyright Element `ExampleScenario.copyright` is mapped to FHIR R5 element `ExampleScenario.copyright` as `Equivalent`. nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required. ExampleScenario.purpose (purpose) is equivalent to ExampleScenario.purpose Element `ExampleScenario.purpose` is mapped to FHIR R5 element `ExampleScenario.purpose` as `Equivalent`. This element does not describe the usage of the example scenario. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this example scenario. ExampleScenario.actor (actor) is broader than ExampleScenario.actor Element `ExampleScenario.actor` is mapped to FHIR R5 element `ExampleScenario.actor` as `Equivalent`. ExampleScenario.actor.actorId (actorId) is equivalent to ExampleScenario.actor.key Element `ExampleScenario.actor.actorId` is mapped to FHIR R5 element `ExampleScenario.actor.key` as `Equivalent`. should this be called ID or acronym? ExampleScenario.actor.type (type) is equivalent to ExampleScenario.actor.type Element `ExampleScenario.actor.type` is mapped to FHIR R5 element `ExampleScenario.actor.type` as `Equivalent`. ExampleScenario.actor.name (name) is equivalent to ExampleScenario.actor.title Element `ExampleScenario.actor.name` is mapped to FHIR R5 element `ExampleScenario.actor.title` as `Equivalent`. Cardinality: is name and description 1..1? ExampleScenario.actor.description (description) is equivalent to ExampleScenario.actor.description Element `ExampleScenario.actor.description` is mapped to FHIR R5 element `ExampleScenario.actor.description` as `Equivalent`. Cardinality: is name and description 1..1? ExampleScenario.instance (instance) is broader than ExampleScenario.instance Element `ExampleScenario.instance` is mapped to FHIR R5 element `ExampleScenario.instance` as `Equivalent`. ExampleScenario.instance.resourceId (resourceId) is equivalent to ExampleScenario.instance.key Element `ExampleScenario.instance.resourceId` is mapped to FHIR R5 element `ExampleScenario.instance.key` as `Equivalent`. ExampleScenario.instance.resourceType (resourceType) is related to ExampleScenario.instance.structureType Element `ExampleScenario.instance.resourceType` is mapped to FHIR R5 element `ExampleScenario.instance.structureType` as `SourceIsNarrowerThanTarget`. ExampleScenario.instance.name (name) is equivalent to ExampleScenario.instance.title Element `ExampleScenario.instance.name` is mapped to FHIR R5 element `ExampleScenario.instance.title` as `Equivalent`. ExampleScenario.instance.description (description) is equivalent to ExampleScenario.instance.description Element `ExampleScenario.instance.description` is mapped to FHIR R5 element `ExampleScenario.instance.description` as `Equivalent`. ExampleScenario.instance.version (version) is broader than ExampleScenario.instance.version Element `ExampleScenario.instance.version` is mapped to FHIR R5 element `ExampleScenario.instance.version` as `Equivalent`. ExampleScenario.instance.version.versionId (versionId) is equivalent to ExampleScenario.instance.version.key Element `ExampleScenario.instance.version.versionId` is mapped to FHIR R5 element `ExampleScenario.instance.version.key` as `Equivalent`. ExampleScenario.instance.version.description (description) is equivalent to ExampleScenario.instance.version.description Element `ExampleScenario.instance.version.description` is mapped to FHIR R5 element `ExampleScenario.instance.version.description` as `Equivalent`. ExampleScenario.instance.containedInstance (containedInstance) is broader than ExampleScenario.instance.containedInstance Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance` as `Equivalent`. ExampleScenario.instance.containedInstance.resourceId (resourceId) is equivalent to ExampleScenario.instance.containedInstance.instanceReference Element `ExampleScenario.instance.containedInstance.resourceId` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance.instanceReference` as `Equivalent`. ExampleScenario.instance.containedInstance.versionId (versionId) is equivalent to ExampleScenario.instance.containedInstance.versionReference Element `ExampleScenario.instance.containedInstance.versionId` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance.versionReference` as `Equivalent`. ExampleScenario.process (process) is broader than ExampleScenario.process Element `ExampleScenario.process` is mapped to FHIR R5 element `ExampleScenario.process` as `Equivalent`. ExampleScenario.process.title (title) is equivalent to ExampleScenario.process.title Element `ExampleScenario.process.title` is mapped to FHIR R5 element `ExampleScenario.process.title` as `Equivalent`. ExampleScenario.process.description (description) is equivalent to ExampleScenario.process.description Element `ExampleScenario.process.description` is mapped to FHIR R5 element `ExampleScenario.process.description` as `Equivalent`. ExampleScenario.process.preConditions (preConditions) is equivalent to ExampleScenario.process.preConditions Element `ExampleScenario.process.preConditions` is mapped to FHIR R5 element `ExampleScenario.process.preConditions` as `Equivalent`. ExampleScenario.process.postConditions (postConditions) is equivalent to ExampleScenario.process.postConditions Element `ExampleScenario.process.postConditions` is mapped to FHIR R5 element `ExampleScenario.process.postConditions` as `Equivalent`. ExampleScenario.process.step (step) is broader than ExampleScenario.process.step Element `ExampleScenario.process.step` is mapped to FHIR R5 element `ExampleScenario.process.step` as `Equivalent`. ExampleScenario.process.step.process (process) is broader than ExampleScenario.process.step.process Element `ExampleScenario.process.step.process` is mapped to FHIR R5 element `ExampleScenario.process.step.process` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.process` do not cover the following types: ExampleScenario.process. ExampleScenario.process.step.pause (pause) is equivalent to ExampleScenario.process.step.pause Element `ExampleScenario.process.step.pause` is mapped to FHIR R5 element `ExampleScenario.process.step.pause` as `Equivalent`. ExampleScenario.process.step.operation (operation) is broader than ExampleScenario.process.step.operation Element `ExampleScenario.process.step.operation` is mapped to FHIR R5 element `ExampleScenario.process.step.operation` as `Equivalent`. ExampleScenario.process.step.operation.type (type) is broader than ExampleScenario.process.step.operation.type Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value. ExampleScenario.process.step.operation.name (name) is equivalent to ExampleScenario.process.step.operation.title Element `ExampleScenario.process.step.operation.name` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.title` 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 R5 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`. ExampleScenario.process.step.operation.receiver (receiver) is equivalent to ExampleScenario.process.step.operation.receiver Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`. ExampleScenario.process.step.operation.description (description) is equivalent to ExampleScenario.process.step.operation.description Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.description` as `Equivalent`. ExampleScenario.process.step.operation.initiatorActive (initiatorActive) is equivalent to ExampleScenario.process.step.operation.initiatorActive Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`. ExampleScenario.process.step.operation.receiverActive (receiverActive) is equivalent to ExampleScenario.process.step.operation.receiverActive Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`. ExampleScenario.process.step.operation.request (request) is equivalent to ExampleScenario.process.step.operation.request Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 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 R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`. ExampleScenario.process.step.alternative (alternative) is broader than ExampleScenario.process.step.alternative Element `ExampleScenario.process.step.alternative` is mapped to FHIR R5 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 R5 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 R5 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 R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: The type of the resourceversion: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.instance.resourceType (resourceType) is broader than Extension (R4B: The type of the resource) Element `ExampleScenario.instance.resourceType` is mapped to FHIR R5 element `ExampleScenario.instance.structureType` as `SourceIsNarrowerThanTarget`. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: Each major process - a group of operationsversion: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process (process) is equivalent to Extension (R4B: Each major process - a group of operations) Element `ExampleScenario.process` is mapped to FHIR R5 element `ExampleScenario.process` as `Equivalent`. ExampleScenario.process.title (title) is equivalent to Extension.extension:title (R4B: The diagram title of the group of operations) Element `ExampleScenario.process.title` is mapped to FHIR R5 element `ExampleScenario.process.title` as `Equivalent`. ExampleScenario.process.description (description) is equivalent to Extension.extension:description (R4B: A longer description of the group of operations) Element `ExampleScenario.process.description` is mapped to FHIR R5 element `ExampleScenario.process.description` as `Equivalent`. ExampleScenario.process.preConditions (preConditions) is equivalent to Extension.extension:preConditions (R4B: Description of initial status before the process starts) Element `ExampleScenario.process.preConditions` is mapped to FHIR R5 element `ExampleScenario.process.preConditions` as `Equivalent`. ExampleScenario.process.postConditions (postConditions) is equivalent to Extension.extension:postConditions (R4B: Description of final status after the process ends) Element `ExampleScenario.process.postConditions` is mapped to FHIR R5 element `ExampleScenario.process.postConditions` as `Equivalent`. ExampleScenario.process.step (step) is equivalent to Extension.extension:step (R4B: Each step of the process) Element `ExampleScenario.process.step` is mapped to FHIR R5 element `ExampleScenario.process.step` as `Equivalent`. ExampleScenario.process.step.process (process) is equivalent to Extension.extension:step.extension:process (R4B: Nested process additional types) Element `ExampleScenario.process.step.process` is mapped to FHIR R5 element `ExampleScenario.process.step.process` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.process` do not cover the following types: ExampleScenario.process. ExampleScenario.process.step.pause (pause) is equivalent to Extension.extension:step.extension:pause (R4B: If there is a pause in the flow) Element `ExampleScenario.process.step.pause` is mapped to FHIR R5 element `ExampleScenario.process.step.pause` as `Equivalent`. ExampleScenario.process.step.operation (operation) is equivalent to Extension.extension:step.extension:operation (R4B: Each interaction or action) Element `ExampleScenario.process.step.operation` is mapped to FHIR R5 element `ExampleScenario.process.step.operation` as `Equivalent`. ExampleScenario.process.step.operation.number (number) is broader than Extension.extension:step.extension:operation.extension:number (R4B: The sequential number of the interaction (new)) Element `ExampleScenario.process.step.operation.number` has a context of ExampleScenario.process.step.operation based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). ExampleScenario.process.step.operation.type (type) is equivalent to Extension.extension:step.extension:operation.extension:type (R4B: The type of operation - CRUD additional types) Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value. ExampleScenario.process.step.operation.name (name) is equivalent to Extension.extension:step.extension:operation.extension:name (R4B: The human-friendly name of the interaction) Element `ExampleScenario.process.step.operation.name` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.title` as `Equivalent`. ExampleScenario.process.step.operation.initiator (initiator) is equivalent to Extension.extension:step.extension:operation.extension:initiator (R4B: Who starts the transaction) Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`. ExampleScenario.process.step.operation.receiver (receiver) is equivalent to Extension.extension:step.extension:operation.extension:receiver (R4B: Who receives the transaction) Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`. ExampleScenario.process.step.operation.description (description) is equivalent to Extension.extension:step.extension:operation.extension:description (R4B: A comment to be inserted in the diagram) Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.description` as `Equivalent`. ExampleScenario.process.step.operation.initiatorActive (initiatorActive) is equivalent to Extension.extension:step.extension:operation.extension:initiatorActive (R4B: Whether the initiator is deactivated right after the transaction) Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`. ExampleScenario.process.step.operation.receiverActive (receiverActive) is equivalent to Extension.extension:step.extension:operation.extension:receiverActive (R4B: Whether the receiver is deactivated right after the transaction) Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`. ExampleScenario.process.step.operation.request (request) is equivalent to Extension.extension:step.extension:operation.extension:request (R4B: Each resource instance used by the initiator) Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.request` as `Equivalent`. ExampleScenario.process.step.operation.response (response) is equivalent to Extension.extension:step.extension:operation.extension:response (R4B: Each resource instance used by the responder) Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`. ExampleScenario.process.step.alternative (alternative) is equivalent to Extension.extension:step.extension:alternative (R4B: alternative) Element `ExampleScenario.process.step.alternative` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative` as `Equivalent`. ExampleScenario.process.step.alternative.title (title) is equivalent to Extension.extension:step.extension:alternative.extension:title (R4B: title) Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.title` as `Equivalent`. ExampleScenario.process.step.alternative.description (description) is equivalent to Extension.extension:step.extension:alternative.extension:description (R4B: A human-readable description of each option) Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.description` as `Equivalent`. ExampleScenario.process.step.alternative.step (step) is equivalent to Extension.extension:step.extension:alternative.extension:step (R4B: What happens in each alternative option) Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: The sequential number of the interaction (new)version: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process.step.operation.number (number) is broader than Extension (R4B: The sequential number of the interaction (new)) Element `ExampleScenario.process.step.operation.number` has a context of ExampleScenario.process.step.operation based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to R4B: The type of operation - CRUD additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ExampleScenario.process.step.operation.type (type) is equivalent to Extension (R4B: The type of operation - CRUD additional types) Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.instance.containedInstance|0.1.0 Source Code Relationship Target Code Comment ExampleScenario.process.step.operation.request (request) is equivalent to Extension.extension:step.extension:operation.extension:request Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.request` as `Equivalent`. ExampleScenario.process.step.operation.response (response) is equivalent to Extension.extension:step.extension:operation.extension:response Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ExampleScenario|4.3.0 to http://hl7.org/fhir/4.3/StructureDefinition/extension-ExampleScenario.process.step|0.1.0 Source Code Relationship Target Code Comment ExampleScenario.process.step.alternative.step (step) is equivalent to Extension.extension:step.extension:alternative.extension:step Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`. Group 8 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) is broader than Extension (R4B: Another nested workflow (new)) Element `ExampleScenario.workflow` has a context of ExampleScenario based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.workflow` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Cross-version mapping for FHIR R4B ExampleScenario to FHIR R5 ExampleScenario
This ConceptMap represents cross-version mappings for elements from a FHIR R4B ExampleScenario to FHIR R5.
Element `ExampleScenario.meta` is mapped to FHIR R5 element `ExampleScenario.meta` as `Equivalent`.
Element `ExampleScenario.implicitRules` is mapped to FHIR R5 element `ExampleScenario.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
Element `ExampleScenario.language` is mapped to FHIR R5 element `ExampleScenario.language` as `Equivalent`. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element `ExampleScenario.text` is mapped to FHIR R5 element `ExampleScenario.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element `ExampleScenario.contained` is mapped to FHIR R5 element `ExampleScenario.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Element `ExampleScenario.url` is mapped to FHIR R5 element `ExampleScenario.url` as `Equivalent`. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
Element `ExampleScenario.identifier` is mapped to FHIR R5 element `ExampleScenario.identifier` as `Equivalent`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this example scenario outside of FHIR, where it is not possible to use the logical URI.
Element `ExampleScenario.version` is mapped to FHIR R5 element `ExampleScenario.version` as `Equivalent`. There may be different example scenario instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the example scenario with the format [url]|[version].
Element `ExampleScenario.name` is mapped to FHIR R5 element `ExampleScenario.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.
Element `ExampleScenario.status` is mapped to FHIR R5 element `ExampleScenario.status` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not.
Element `ExampleScenario.experimental` is mapped to FHIR R5 element `ExampleScenario.experimental` as `Equivalent`. Allows filtering of example scenarios that are appropriate for use versus not.
Element `ExampleScenario.date` is mapped to FHIR R5 element `ExampleScenario.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the example scenario. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Element `ExampleScenario.publisher` is mapped to FHIR R5 element `ExampleScenario.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the example scenario is the organization or individual primarily responsible for the maintenance and upkeep of the example scenario. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the example scenario. This item SHOULD be populated unless the information is available from context.
Element `ExampleScenario.contact` is mapped to FHIR R5 element `ExampleScenario.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
Element `ExampleScenario.useContext` is mapped to FHIR R5 element `ExampleScenario.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `ExampleScenario.jurisdiction` is mapped to FHIR R5 element `ExampleScenario.jurisdiction` as `Equivalent`. It may be possible for the example scenario to be used in jurisdictions other than those for which it was originally designed or intended.
Element `ExampleScenario.copyright` is mapped to FHIR R5 element `ExampleScenario.copyright` as `Equivalent`. nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.
Element `ExampleScenario.purpose` is mapped to FHIR R5 element `ExampleScenario.purpose` as `Equivalent`. This element does not describe the usage of the example scenario. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this example scenario.
Element `ExampleScenario.actor` is mapped to FHIR R5 element `ExampleScenario.actor` as `Equivalent`.
Element `ExampleScenario.actor.actorId` is mapped to FHIR R5 element `ExampleScenario.actor.key` as `Equivalent`. should this be called ID or acronym?
Element `ExampleScenario.actor.type` is mapped to FHIR R5 element `ExampleScenario.actor.type` as `Equivalent`.
Element `ExampleScenario.actor.name` is mapped to FHIR R5 element `ExampleScenario.actor.title` as `Equivalent`. Cardinality: is name and description 1..1?
Element `ExampleScenario.actor.description` is mapped to FHIR R5 element `ExampleScenario.actor.description` as `Equivalent`. Cardinality: is name and description 1..1?
Element `ExampleScenario.instance` is mapped to FHIR R5 element `ExampleScenario.instance` as `Equivalent`.
Element `ExampleScenario.instance.resourceId` is mapped to FHIR R5 element `ExampleScenario.instance.key` as `Equivalent`.
Element `ExampleScenario.instance.resourceType` is mapped to FHIR R5 element `ExampleScenario.instance.structureType` as `SourceIsNarrowerThanTarget`.
Element `ExampleScenario.instance.name` is mapped to FHIR R5 element `ExampleScenario.instance.title` as `Equivalent`.
Element `ExampleScenario.instance.description` is mapped to FHIR R5 element `ExampleScenario.instance.description` as `Equivalent`.
Element `ExampleScenario.instance.version` is mapped to FHIR R5 element `ExampleScenario.instance.version` as `Equivalent`.
Element `ExampleScenario.instance.version.versionId` is mapped to FHIR R5 element `ExampleScenario.instance.version.key` as `Equivalent`.
Element `ExampleScenario.instance.version.description` is mapped to FHIR R5 element `ExampleScenario.instance.version.description` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance.resourceId` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance.instanceReference` as `Equivalent`.
Element `ExampleScenario.instance.containedInstance.versionId` is mapped to FHIR R5 element `ExampleScenario.instance.containedInstance.versionReference` as `Equivalent`.
Element `ExampleScenario.process` is mapped to FHIR R5 element `ExampleScenario.process` as `Equivalent`.
Element `ExampleScenario.process.title` is mapped to FHIR R5 element `ExampleScenario.process.title` as `Equivalent`.
Element `ExampleScenario.process.description` is mapped to FHIR R5 element `ExampleScenario.process.description` as `Equivalent`.
Element `ExampleScenario.process.preConditions` is mapped to FHIR R5 element `ExampleScenario.process.preConditions` as `Equivalent`.
Element `ExampleScenario.process.postConditions` is mapped to FHIR R5 element `ExampleScenario.process.postConditions` as `Equivalent`.
Element `ExampleScenario.process.step` is mapped to FHIR R5 element `ExampleScenario.process.step` as `Equivalent`.
Element `ExampleScenario.process.step.process` is mapped to FHIR R5 element `ExampleScenario.process.step.process` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.process` do not cover the following types: ExampleScenario.process.
Element `ExampleScenario.process.step.pause` is mapped to FHIR R5 element `ExampleScenario.process.step.pause` as `Equivalent`.
Element `ExampleScenario.process.step.operation` is mapped to FHIR R5 element `ExampleScenario.process.step.operation` as `Equivalent`.
Element `ExampleScenario.process.step.operation.type` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.type` as `SourceIsBroaderThanTarget`. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types: string. The mappings for `ExampleScenario.process.step.operation.type` do not cover the following types based on type expansion: value.
Element `ExampleScenario.process.step.operation.name` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.title` as `Equivalent`.
Element `ExampleScenario.process.step.operation.initiator` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiator` as `Equivalent`.
Element `ExampleScenario.process.step.operation.receiver` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiver` as `Equivalent`.
Element `ExampleScenario.process.step.operation.description` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.description` as `Equivalent`.
Element `ExampleScenario.process.step.operation.initiatorActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.initiatorActive` as `Equivalent`.
Element `ExampleScenario.process.step.operation.receiverActive` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.receiverActive` as `Equivalent`.
Element `ExampleScenario.process.step.operation.request` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.request` as `Equivalent`.
Element `ExampleScenario.process.step.operation.response` is mapped to FHIR R5 element `ExampleScenario.process.step.operation.response` as `Equivalent`.
Element `ExampleScenario.process.step.alternative` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.title` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.title` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.description` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.description` as `Equivalent`.
Element `ExampleScenario.process.step.alternative.step` is mapped to FHIR R5 element `ExampleScenario.process.step.alternative.step` as `Equivalent`.
Element `ExampleScenario.process.step.operation.number` has a context of ExampleScenario.process.step.operation based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.process.step.operation.number` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `ExampleScenario.workflow` has a context of ExampleScenario based on following the parent source element upwards and mapping to `ExampleScenario`. Element `ExampleScenario.workflow` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).