Generated Narrative: ConceptMap R3-MessageDefinition-element-map-to-R4B Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.3 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to MessageDefinitionversion: 4.3.0) Source Code Relationship Target Code Comment MessageDefinition.meta (meta) maps to wider concept MessageDefinition.meta Element `MessageDefinition.meta` is mapped to FHIR R4B element `MessageDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.meta` do not cover the following types: Meta. The mappings for `MessageDefinition.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. MessageDefinition.implicitRules (implicitRules) is equivalent to MessageDefinition.implicitRules Element `MessageDefinition.implicitRules` is mapped to FHIR R4B 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. MessageDefinition.language (language) is equivalent to MessageDefinition.language Element `MessageDefinition.language` is mapped to FHIR R4B 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) maps to wider concept MessageDefinition.text Element `MessageDefinition.text` is mapped to FHIR R4B element `MessageDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.text` do not cover the following types: Narrative. The mappings for `MessageDefinition.text` do not cover the following types based on type expansion: div, status. 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 in formation is added later. MessageDefinition.contained (contained) is equivalent to MessageDefinition.contained Element `MessageDefinition.contained` is mapped to FHIR R4B element `MessageDefinition.contained` as `SourceIsBroaderThanTarget`. 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. MessageDefinition.url (url) is equivalent to MessageDefinition.url Element `MessageDefinition.url` is mapped to FHIR R4B 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. MessageDefinition.identifier (identifier) maps to wider concept MessageDefinition.identifier Element `MessageDefinition.identifier` is mapped to FHIR R4B element `MessageDefinition.identifier` as `RelatedTo`. The mappings for `MessageDefinition.identifier` do not cover the following types: Identifier. The mappings for `MessageDefinition.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to 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 R4B 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 refrence 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 R4B element `MessageDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly. MessageDefinition.title (title) is equivalent to MessageDefinition.title Element `MessageDefinition.title` is mapped to FHIR R4B element `MessageDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc. MessageDefinition.status (status) is equivalent to MessageDefinition.status Element `MessageDefinition.status` is mapped to FHIR R4B element `MessageDefinition.status` as `Equivalent`. Allows filtering of message definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired message definition without due consideration. MessageDefinition.experimental (experimental) is equivalent to MessageDefinition.experimental Element `MessageDefinition.experimental` is mapped to FHIR R4B element `MessageDefinition.experimental` as `Equivalent`. Allows filtering of message definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental message definition in production. MessageDefinition.date (date) is equivalent to MessageDefinition.date Element `MessageDefinition.date` is mapped to FHIR R4B 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 R4B 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) maps to wider concept MessageDefinition.contact Element `MessageDefinition.contact` is mapped to FHIR R4B element `MessageDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.contact` do not cover the following types: ContactDetail. The mappings for `MessageDefinition.contact` do not cover the following types based on type expansion: name, telecom. 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 R4B 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 profile is presumed to be the predominant language in the place the profile was created). MessageDefinition.useContext (useContext) maps to wider concept MessageDefinition.useContext Element `MessageDefinition.useContext` is mapped to FHIR R4B element `MessageDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.useContext` do not cover the following types: UsageContext. The mappings for `MessageDefinition.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. MessageDefinition.jurisdiction (jurisdiction) is equivalent to MessageDefinition.jurisdiction Element `MessageDefinition.jurisdiction` is mapped to FHIR R4B 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 R4B 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 R4B element `MessageDefinition.copyright` as `Equivalent`. MessageDefinition.base (base) maps to wider concept MessageDefinition.base Element `MessageDefinition.base` is mapped to FHIR R4B element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: Reference. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: display, identifier, reference. MessageDefinition.parent (parent) maps to wider concept MessageDefinition.parent Element `MessageDefinition.parent` is mapped to FHIR R4B element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: Reference. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: display, identifier, reference. MessageDefinition.replaces (replaces) maps to wider concept MessageDefinition.replaces Element `MessageDefinition.replaces` is mapped to FHIR R4B element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: Reference. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: display, identifier, reference. MessageDefinition.event (event) is equivalent to MessageDefinition.event[x] Element `MessageDefinition.event` is mapped to FHIR R4B element `MessageDefinition.event[x]` as `Equivalent`. The target context `MessageDefinition.event[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MessageDefinition`. MessageDefinition.category (category) is equivalent to MessageDefinition.category Element `MessageDefinition.category` is mapped to FHIR R4B element `MessageDefinition.category` as `Equivalent`. MessageDefinition.focus (focus) maps to wider concept MessageDefinition.focus Element `MessageDefinition.focus` is mapped to FHIR R4B element `MessageDefinition.focus` as `Equivalent`. MessageDefinition.focus.code (code) maps to wider concept MessageDefinition.focus.code Element `MessageDefinition.focus.code` is mapped to FHIR R4B element `MessageDefinition.focus.code` as `RelatedTo`. The mappings for `MessageDefinition.focus.code` do not allow expression of the necessary codes, per the bindings on the source and target. 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 R4B element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: Reference. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: display, identifier, reference. 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 R4B element `MessageDefinition.focus.min` as `Equivalent`. MessageDefinition.focus.max (max) is equivalent to MessageDefinition.focus.max Element `MessageDefinition.focus.max` is mapped to FHIR R4B element `MessageDefinition.focus.max` as `Equivalent`. MessageDefinition.responseRequired (responseRequired) maps to wider concept MessageDefinition.responseRequired Element `MessageDefinition.responseRequired` is mapped to FHIR R4B element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: boolean. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value. MessageDefinition.allowedResponse (allowedResponse) maps to wider concept MessageDefinition.allowedResponse Element `MessageDefinition.allowedResponse` is mapped to FHIR R4B 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 R4B element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: Reference. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: display, identifier, reference. MessageDefinition.allowedResponse.situation (situation) is equivalent to MessageDefinition.allowedResponse.situation Element `MessageDefinition.allowedResponse.situation` is mapped to FHIR R4B element `MessageDefinition.allowedResponse.situation` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.meta (meta) is equivalent to Extension (STU3: meta additional types) Element `MessageDefinition.meta` is mapped to FHIR R4B element `MessageDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.meta` do not cover the following types: Meta. The mappings for `MessageDefinition.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.text (text) is equivalent to Extension (STU3: text additional types) Element `MessageDefinition.text` is mapped to FHIR R4B element `MessageDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.text` do not cover the following types: Narrative. The mappings for `MessageDefinition.text` do not cover the following types based on type expansion: div, status. 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 in formation is added later. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: Additional identifier for the message definition additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.identifier (identifier) is equivalent to Extension (STU3: Additional identifier for the message definition additional types) Element `MessageDefinition.identifier` is mapped to FHIR R4B element `MessageDefinition.identifier` as `RelatedTo`. The mappings for `MessageDefinition.identifier` do not cover the following types: Identifier. The mappings for `MessageDefinition.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this message definition outside of FHIR, where it is not possible to use the logical URI. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: contact additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.contact (contact) is equivalent to Extension (STU3: contact additional types) Element `MessageDefinition.contact` is mapped to FHIR R4B element `MessageDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.contact` do not cover the following types: ContactDetail. The mappings for `MessageDefinition.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: Context the content is intended to support additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.useContext (useContext) is equivalent to Extension (STU3: Context the content is intended to support additional types) Element `MessageDefinition.useContext` is mapped to FHIR R4B element `MessageDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.useContext` do not cover the following types: UsageContext. The mappings for `MessageDefinition.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: base additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.base (base) is equivalent to Extension (STU3: base additional types) Element `MessageDefinition.base` is mapped to FHIR R4B element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: Reference. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: display, identifier, reference. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: parent additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.parent (parent) is equivalent to Extension (STU3: parent additional types) Element `MessageDefinition.parent` is mapped to FHIR R4B element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: Reference. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: display, identifier, reference. Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: replaces additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.replaces (replaces) is equivalent to Extension (STU3: replaces additional types) Element `MessageDefinition.replaces` is mapped to FHIR R4B element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: Reference. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: display, identifier, reference. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: code additional codesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.focus.code (code) is equivalent to Extension (STU3: code additional codes) Element `MessageDefinition.focus.code` is mapped to FHIR R4B element `MessageDefinition.focus.code` as `RelatedTo`. The mappings for `MessageDefinition.focus.code` do not allow expression of the necessary codes, per the bindings on the source and target. Multiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: profile additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.focus.profile (profile) is equivalent to Extension (STU3: profile additional types) Element `MessageDefinition.focus.profile` is mapped to FHIR R4B element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: Reference. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: display, identifier, reference. 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 12 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: Is a response required? additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.responseRequired (responseRequired) is equivalent to Extension (STU3: Is a response required? additional types) Element `MessageDefinition.responseRequired` is mapped to FHIR R4B element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: boolean. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value. Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to STU3: message additional typesversion: 0.1.0) Source Code Relationship Target Code Comment MessageDefinition.allowedResponse.message (message) is equivalent to Extension (STU3: message additional types) Element `MessageDefinition.allowedResponse.message` is mapped to FHIR R4B element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: Reference. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: display, identifier, reference.
Cross-version mapping for FHIR STU3 MessageDefinition to FHIR R4B MessageDefinition
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 MessageDefinition to FHIR R4B.
Element `MessageDefinition.meta` is mapped to FHIR R4B element `MessageDefinition.meta` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.meta` do not cover the following types: Meta. The mappings for `MessageDefinition.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `MessageDefinition.implicitRules` is mapped to FHIR R4B 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element `MessageDefinition.language` is mapped to FHIR R4B 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 R4B element `MessageDefinition.text` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.text` do not cover the following types: Narrative. The mappings for `MessageDefinition.text` do not cover the following types based on type expansion: div, status. 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 in formation is added later.
Element `MessageDefinition.contained` is mapped to FHIR R4B element `MessageDefinition.contained` as `SourceIsBroaderThanTarget`. 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.
Element `MessageDefinition.url` is mapped to FHIR R4B 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.
Element `MessageDefinition.identifier` is mapped to FHIR R4B element `MessageDefinition.identifier` as `RelatedTo`. The mappings for `MessageDefinition.identifier` do not cover the following types: Identifier. The mappings for `MessageDefinition.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this message definition outside of FHIR, where it is not possible to use the logical URI.
Element `MessageDefinition.version` is mapped to FHIR R4B 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 refrence to a particular business version of the message definition with the format [url]|[version].
Element `MessageDefinition.name` is mapped to FHIR R4B element `MessageDefinition.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.
Element `MessageDefinition.title` is mapped to FHIR R4B element `MessageDefinition.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
Element `MessageDefinition.status` is mapped to FHIR R4B element `MessageDefinition.status` as `Equivalent`. Allows filtering of message definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired message definition without due consideration.
Element `MessageDefinition.experimental` is mapped to FHIR R4B element `MessageDefinition.experimental` as `Equivalent`. Allows filtering of message definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental message definition in production.
Element `MessageDefinition.date` is mapped to FHIR R4B 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 R4B 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 R4B element `MessageDefinition.contact` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.contact` do not cover the following types: ContactDetail. The mappings for `MessageDefinition.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.
Element `MessageDefinition.description` is mapped to FHIR R4B 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 profile is presumed to be the predominant language in the place the profile was created).
Element `MessageDefinition.useContext` is mapped to FHIR R4B element `MessageDefinition.useContext` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.useContext` do not cover the following types: UsageContext. The mappings for `MessageDefinition.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Element `MessageDefinition.jurisdiction` is mapped to FHIR R4B 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 R4B 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 R4B element `MessageDefinition.copyright` as `Equivalent`.
Element `MessageDefinition.base` is mapped to FHIR R4B element `MessageDefinition.base` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.base` do not cover the following types: Reference. The mappings for `MessageDefinition.base` do not cover the following types based on type expansion: display, identifier, reference.
Element `MessageDefinition.parent` is mapped to FHIR R4B element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.parent` do not cover the following types: Reference. The mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: display, identifier, reference.
Element `MessageDefinition.replaces` is mapped to FHIR R4B element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.replaces` do not cover the following types: Reference. The mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: display, identifier, reference.
Element `MessageDefinition.event` is mapped to FHIR R4B element `MessageDefinition.event[x]` as `Equivalent`. The target context `MessageDefinition.event[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MessageDefinition`.
Element `MessageDefinition.category` is mapped to FHIR R4B element `MessageDefinition.category` as `Equivalent`.
Element `MessageDefinition.focus` is mapped to FHIR R4B element `MessageDefinition.focus` as `Equivalent`.
Element `MessageDefinition.focus.code` is mapped to FHIR R4B element `MessageDefinition.focus.code` as `RelatedTo`. The mappings for `MessageDefinition.focus.code` do not allow expression of the necessary codes, per the bindings on the source and target. 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 R4B element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.focus.profile` do not cover the following types: Reference. The mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: display, identifier, reference. 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 R4B element `MessageDefinition.focus.min` as `Equivalent`.
Element `MessageDefinition.focus.max` is mapped to FHIR R4B element `MessageDefinition.focus.max` as `Equivalent`.
Element `MessageDefinition.responseRequired` is mapped to FHIR R4B element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.responseRequired` do not cover the following types: boolean. The mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value.
Element `MessageDefinition.allowedResponse` is mapped to FHIR R4B 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 R4B element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: Reference. The mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: display, identifier, reference.
Element `MessageDefinition.allowedResponse.situation` is mapped to FHIR R4B element `MessageDefinition.allowedResponse.situation` as `Equivalent`.