Generated Narrative: ConceptMap R4-MessageDefinition-element-map-to-R3 Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/3.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 Source Code Relationship Target Code Comment MessageDefinition.meta (meta) is equivalent to MessageDefinition.meta Element `MessageDefinition.meta` is mapped to FHIR STU3 element `MessageDefinition.meta` as `Equivalent`. MessageDefinition.implicitRules (implicitRules) is equivalent to MessageDefinition.implicitRules Element `MessageDefinition.implicitRules` is mapped to FHIR STU3 element `MessageDefinition.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. MessageDefinition.language (language) is equivalent to MessageDefinition.language Element `MessageDefinition.language` is mapped to FHIR STU3 element `MessageDefinition.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). MessageDefinition.text (text) is equivalent to MessageDefinition.text Element `MessageDefinition.text` is mapped to FHIR STU3 element `MessageDefinition.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. MessageDefinition.contained (contained) is equivalent to MessageDefinition.contained Element `MessageDefinition.contained` is mapped to FHIR STU3 element `MessageDefinition.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. MessageDefinition.url (url) is equivalent to MessageDefinition.url Element `MessageDefinition.url` is mapped to FHIR STU3 element `MessageDefinition.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. MessageDefinition.identifier (identifier) is equivalent to MessageDefinition.identifier Element `MessageDefinition.identifier` is mapped to FHIR STU3 element `MessageDefinition.identifier` as `SourceIsBroaderThanTarget`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this message definition outside of FHIR, where it is not possible to use the logical URI. MessageDefinition.version (version) is equivalent to MessageDefinition.version Element `MessageDefinition.version` is mapped to FHIR STU3 element `MessageDefinition.version` as `Equivalent`. There may be different message definition 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 message definition with the format [url]|[version]. MessageDefinition.name (name) is equivalent to MessageDefinition.name Element `MessageDefinition.name` is mapped to FHIR STU3 element `MessageDefinition.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. MessageDefinition.title (title) is equivalent to MessageDefinition.title Element `MessageDefinition.title` is mapped to FHIR STU3 element `MessageDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. MessageDefinition.replaces (replaces) maps to wider concept MessageDefinition.replaces Element `MessageDefinition.replaces` is mapped to FHIR STU3 element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: canonical. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: value. MessageDefinition.status (status) is equivalent to MessageDefinition.status Element `MessageDefinition.status` is mapped to FHIR STU3 element `MessageDefinition.status` as `Equivalent`. Allows filtering of message definitions that are appropriate for use versus not. MessageDefinition.experimental (experimental) is equivalent to MessageDefinition.experimental Element `MessageDefinition.experimental` is mapped to FHIR STU3 element `MessageDefinition.experimental` as `Equivalent`. Allows filtering of message definitions that are appropriate for use versus not. MessageDefinition.date (date) is equivalent to MessageDefinition.date Element `MessageDefinition.date` is mapped to FHIR STU3 element `MessageDefinition.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 message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource. MessageDefinition.publisher (publisher) is equivalent to MessageDefinition.publisher Element `MessageDefinition.publisher` is mapped to FHIR STU3 element `MessageDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the message definition is the organization or individual primarily responsible for the maintenance and upkeep of the message definition. 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 message definition. This item SHOULD be populated unless the information is available from context. MessageDefinition.contact (contact) is equivalent to MessageDefinition.contact Element `MessageDefinition.contact` is mapped to FHIR STU3 element `MessageDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc. MessageDefinition.description (description) is equivalent to MessageDefinition.description Element `MessageDefinition.description` is mapped to FHIR STU3 element `MessageDefinition.description` as `Equivalent`. This description can be used to capture details such as why the message definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created). MessageDefinition.useContext (useContext) is equivalent to MessageDefinition.useContext Element `MessageDefinition.useContext` is mapped to FHIR STU3 element `MessageDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. MessageDefinition.jurisdiction (jurisdiction) is equivalent to MessageDefinition.jurisdiction Element `MessageDefinition.jurisdiction` is mapped to FHIR STU3 element `MessageDefinition.jurisdiction` as `Equivalent`. It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended. MessageDefinition.purpose (purpose) is equivalent to MessageDefinition.purpose Element `MessageDefinition.purpose` is mapped to FHIR STU3 element `MessageDefinition.purpose` as `Equivalent`. This element does not describe the usage of the message definition. 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 message definition. MessageDefinition.copyright (copyright) is equivalent to MessageDefinition.copyright Element `MessageDefinition.copyright` is mapped to FHIR STU3 element `MessageDefinition.copyright` as `Equivalent`. MessageDefinition.base (base) maps to wider concept MessageDefinition.base Element `MessageDefinition.base` is mapped to FHIR STU3 element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: canonical. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: value. MessageDefinition.parent (parent) maps to wider concept MessageDefinition.parent Element `MessageDefinition.parent` is mapped to FHIR STU3 element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: canonical. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: value. It should be possible to use MessageDefinition to describe a message to be used by certain steps in a particular protocol as part of a PlanDefinition or ActivityDefinition. MessageDefinition.event[x] (event[x]) maps to wider concept MessageDefinition.event Element `MessageDefinition.event[x]` is mapped to FHIR STU3 element `MessageDefinition.event` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.event[x]` do not cover the following types: uri. The mappings for `MessageDefinition.event[x]` do not cover the following types based on type expansion: value. MessageDefinition.category (category) is equivalent to MessageDefinition.category Element `MessageDefinition.category` is mapped to FHIR STU3 element `MessageDefinition.category` as `Equivalent`. MessageDefinition.focus (focus) maps to wider concept MessageDefinition.focus Element `MessageDefinition.focus` is mapped to FHIR STU3 element `MessageDefinition.focus` as `Equivalent`. MessageDefinition.focus.code (code) maps to wider concept MessageDefinition.focus.code Element `MessageDefinition.focus.code` is mapped to FHIR STU3 element `MessageDefinition.focus.code` as `SourceIsBroaderThanTarget`. Multiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc. MessageDefinition.focus.profile (profile) maps to wider concept MessageDefinition.focus.profile Element `MessageDefinition.focus.profile` is mapped to FHIR STU3 element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: canonical. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: value. This should be present for most message definitions. However, if the message focus is only a single resource and there is no need to include referenced resources or otherwise enforce the presence of particular elements, it can be omitted. MessageDefinition.focus.min (min) is equivalent to MessageDefinition.focus.min Element `MessageDefinition.focus.min` is mapped to FHIR STU3 element `MessageDefinition.focus.min` as `Equivalent`. MessageDefinition.focus.max (max) is equivalent to MessageDefinition.focus.max Element `MessageDefinition.focus.max` is mapped to FHIR STU3 element `MessageDefinition.focus.max` as `Equivalent`. MessageDefinition.responseRequired (responseRequired) maps to wider concept MessageDefinition.responseRequired Element `MessageDefinition.responseRequired` is mapped to FHIR STU3 element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: code. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value. This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message instance level whether a response is required or only upon error or success, or never. MessageDefinition.allowedResponse (allowedResponse) maps to wider concept MessageDefinition.allowedResponse Element `MessageDefinition.allowedResponse` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse` as `Equivalent`. This indicates an application level response to "close" a transaction implicit in a particular request message. To define a complete workflow scenario, look to the PlanDefinition resource which allows the definition of complex orchestrations, conditionality, etc. MessageDefinition.allowedResponse.message (message) maps to wider concept MessageDefinition.allowedResponse.message Element `MessageDefinition.allowedResponse.message` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: canonical. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: value. MessageDefinition.allowedResponse.situation (situation) is equivalent to MessageDefinition.allowedResponse.situation Element `MessageDefinition.allowedResponse.situation` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse.situation` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: replaces additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.replaces (replaces) is equivalent to Extension (R4: replaces additional types) Element `MessageDefinition.replaces` is mapped to FHIR STU3 element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: canonical. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: value. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: base additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.base (base) is equivalent to Extension (R4: base additional types) Element `MessageDefinition.base` is mapped to FHIR STU3 element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: canonical. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: value. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: parent additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.parent (parent) is equivalent to Extension (R4: parent additional types) Element `MessageDefinition.parent` is mapped to FHIR STU3 element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: canonical. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: value. It should be possible to use MessageDefinition to describe a message to be used by certain steps in a particular protocol as part of a PlanDefinition or ActivityDefinition. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: Event code or link to the EventDefinition additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.event[x] (event[x]) maps to wider concept Extension (R4: Event code or link to the EventDefinition additional types) Element `MessageDefinition.event[x]` is mapped to FHIR STU3 element `MessageDefinition.event` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.event[x]` do not cover the following types: uri. The mappings for `MessageDefinition.event[x]` do not cover the following types based on type expansion: value. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: codeversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.focus.code (code) is equivalent to Extension (R4: code) Element `MessageDefinition.focus.code` is mapped to FHIR STU3 element `MessageDefinition.focus.code` as `SourceIsBroaderThanTarget`. Multiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: profile additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.focus.profile (profile) is equivalent to Extension (R4: profile additional types) Element `MessageDefinition.focus.profile` is mapped to FHIR STU3 element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: canonical. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: value. This should be present for most message definitions. However, if the message focus is only a single resource and there is no need to include referenced resources or otherwise enforce the presence of particular elements, it can be omitted. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: always | on-error | never | on-success additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.responseRequired (responseRequired) is equivalent to Extension (R4: always | on-error | never | on-success additional types) Element `MessageDefinition.responseRequired` is mapped to FHIR STU3 element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: code. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value. This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message instance level whether a response is required or only upon error or success, or never. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: message additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.allowedResponse.message (message) is equivalent to Extension (R4: message additional types) Element `MessageDefinition.allowedResponse.message` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: canonical. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: value. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|4.0.1 to R4: Canonical reference to a GraphDefinition (new)version: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.graph (graph) maps to wider concept Extension (R4: Canonical reference to a GraphDefinition (new)) Element `MessageDefinition.graph` has a context of MessageDefinition based on following the parent source element upwards and mapping to `MessageDefinition`. Element `MessageDefinition.graph` 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 R4 MessageDefinition to FHIR STU3 MessageDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR R4 MessageDefinition to FHIR STU3.
Element `MessageDefinition.meta` is mapped to FHIR STU3 element `MessageDefinition.meta` as `Equivalent`.
Element `MessageDefinition.implicitRules` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.language` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.text` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.contained` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.url` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.identifier` is mapped to FHIR STU3 element `MessageDefinition.identifier` as `SourceIsBroaderThanTarget`. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this message definition outside of FHIR, where it is not possible to use the logical URI.
Element `MessageDefinition.version` is mapped to FHIR STU3 element `MessageDefinition.version` as `Equivalent`. There may be different message definition 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 message definition with the format [url]|[version].
Element `MessageDefinition.name` is mapped to FHIR STU3 element `MessageDefinition.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 `MessageDefinition.title` is mapped to FHIR STU3 element `MessageDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Element `MessageDefinition.replaces` is mapped to FHIR STU3 element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: canonical. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: value.
Element `MessageDefinition.status` is mapped to FHIR STU3 element `MessageDefinition.status` as `Equivalent`. Allows filtering of message definitions that are appropriate for use versus not.
Element `MessageDefinition.experimental` is mapped to FHIR STU3 element `MessageDefinition.experimental` as `Equivalent`. Allows filtering of message definitions that are appropriate for use versus not.
Element `MessageDefinition.date` is mapped to FHIR STU3 element `MessageDefinition.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 message definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.
Element `MessageDefinition.publisher` is mapped to FHIR STU3 element `MessageDefinition.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the message definition is the organization or individual primarily responsible for the maintenance and upkeep of the message definition. 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 message definition. This item SHOULD be populated unless the information is available from context.
Element `MessageDefinition.contact` is mapped to FHIR STU3 element `MessageDefinition.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
Element `MessageDefinition.description` is mapped to FHIR STU3 element `MessageDefinition.description` as `Equivalent`. This description can be used to capture details such as why the message definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the message definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the message definition is presumed to be the predominant language in the place the message definition was created).
Element `MessageDefinition.useContext` is mapped to FHIR STU3 element `MessageDefinition.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `MessageDefinition.jurisdiction` is mapped to FHIR STU3 element `MessageDefinition.jurisdiction` as `Equivalent`. It may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended.
Element `MessageDefinition.purpose` is mapped to FHIR STU3 element `MessageDefinition.purpose` as `Equivalent`. This element does not describe the usage of the message definition. 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 message definition.
Element `MessageDefinition.copyright` is mapped to FHIR STU3 element `MessageDefinition.copyright` as `Equivalent`.
Element `MessageDefinition.base` is mapped to FHIR STU3 element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: canonical. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: value.
Element `MessageDefinition.parent` is mapped to FHIR STU3 element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: canonical. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: value. It should be possible to use MessageDefinition to describe a message to be used by certain steps in a particular protocol as part of a PlanDefinition or ActivityDefinition.
Element `MessageDefinition.event[x]` is mapped to FHIR STU3 element `MessageDefinition.event` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.event[x]` do not cover the following types: uri. The mappings for `MessageDefinition.event[x]` do not cover the following types based on type expansion: value.
Element `MessageDefinition.category` is mapped to FHIR STU3 element `MessageDefinition.category` as `Equivalent`.
Element `MessageDefinition.focus` is mapped to FHIR STU3 element `MessageDefinition.focus` as `Equivalent`.
Element `MessageDefinition.focus.code` is mapped to FHIR STU3 element `MessageDefinition.focus.code` as `SourceIsBroaderThanTarget`. Multiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc.
Element `MessageDefinition.focus.profile` is mapped to FHIR STU3 element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: canonical. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: value. This should be present for most message definitions. However, if the message focus is only a single resource and there is no need to include referenced resources or otherwise enforce the presence of particular elements, it can be omitted.
Element `MessageDefinition.focus.min` is mapped to FHIR STU3 element `MessageDefinition.focus.min` as `Equivalent`.
Element `MessageDefinition.focus.max` is mapped to FHIR STU3 element `MessageDefinition.focus.max` as `Equivalent`.
Element `MessageDefinition.responseRequired` is mapped to FHIR STU3 element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: code. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value. This enables the capability currently available through MSH-16 (Application Level acknowledgement) in HL7 Version 2 to declare at a message instance level whether a response is required or only upon error or success, or never.
Element `MessageDefinition.allowedResponse` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse` as `Equivalent`. This indicates an application level response to "close" a transaction implicit in a particular request message. To define a complete workflow scenario, look to the PlanDefinition resource which allows the definition of complex orchestrations, conditionality, etc.
Element `MessageDefinition.allowedResponse.message` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: canonical. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: value.
Element `MessageDefinition.allowedResponse.situation` is mapped to FHIR STU3 element `MessageDefinition.allowedResponse.situation` as `Equivalent`.
Element `MessageDefinition.graph` has a context of MessageDefinition based on following the parent source element upwards and mapping to `MessageDefinition`. Element `MessageDefinition.graph` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).