FHIR IG analytics| Package | hl7.fhir.uv.xver-r3.r5 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R3-MessageDefinition-element-map-to-R5.json |
| FHIR Version | R5 |
| Source | http://hl7.org/fhir/uv/xver-r3.r5/0.1.0/ConceptMap-R3-MessageDefinition-element-map-to-R5.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R3-MessageDefinition-element-map-to-R5 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:05:00.2973356-05:00 |
| Name | R3MessageDefinitionElementMapToR5 |
| Title | Cross-version mapping for FHIR STU3 MessageDefinition to FHIR R5 MessageDefinition |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR STU3 MessageDefinition to FHIR R5. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.allowedResponse.message | Cross-version Extension for R3.MessageDefinition.allowedResponse.message for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.base | Cross-version Extension for R3.MessageDefinition.base for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.contact | STU3: contact additional types |
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.focus.code | Cross-version Extension for R3.MessageDefinition.focus.code for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.focus.profile | Cross-version Extension for R3.MessageDefinition.focus.profile for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.identifier | STU3: Additional identifier for the message definition additional types |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.meta | STU3: meta additional types |
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.parent | Cross-version Extension for R3.MessageDefinition.parent for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b.r4#0.0.1-snapshot-2 | extension-MessageDefinition.replaces | Cross-version Extension for R3.MessageDefinition.replaces for use in FHIR R4B |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.responseRequired | STU3: Is a response required? additional types |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.text | STU3: text additional types |
| hl7.fhir.uv.xver-r3.r4b#0.1.0 | extension-MessageDefinition.useContext | STU3: Context the content is intended to support additional types |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R3-MessageDefinition-element-map-to-R5
Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2 to MessageDefinitionversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| MessageDefinition.meta (meta) | is broader than | MessageDefinition.meta | Element `MessageDefinition.meta` is mapped to FHIR R5 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 R5 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 R5 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 broader than | MessageDefinition.text | Element `MessageDefinition.text` is mapped to FHIR R5 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 R5 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 R5 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) | is broader than | MessageDefinition.identifier | Element `MessageDefinition.identifier` is mapped to FHIR R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 broader than | MessageDefinition.contact | Element `MessageDefinition.contact` is mapped to FHIR R5 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 R5 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) | is broader than | MessageDefinition.useContext | Element `MessageDefinition.useContext` is mapped to FHIR R5 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 R5 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 R5 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 R5 element `MessageDefinition.copyright` as `Equivalent`. |
| MessageDefinition.base (base) | is broader than | MessageDefinition.base | Element `MessageDefinition.base` is mapped to FHIR R5 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) | is broader than | MessageDefinition.parent | Element `MessageDefinition.parent` is mapped to FHIR R5 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) | is broader than | MessageDefinition.replaces | Element `MessageDefinition.replaces` is mapped to FHIR R5 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 R5 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 R5 element `MessageDefinition.category` as `Equivalent`. |
| MessageDefinition.focus (focus) | is broader than | MessageDefinition.focus | Element `MessageDefinition.focus` is mapped to FHIR R5 element `MessageDefinition.focus` as `Equivalent`. |
| MessageDefinition.focus.code (code) | is broader than | MessageDefinition.focus.code | Element `MessageDefinition.focus.code` is mapped to FHIR R5 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) | is broader than | MessageDefinition.focus.profile | Element `MessageDefinition.focus.profile` is mapped to FHIR R5 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 R5 element `MessageDefinition.focus.min` as `Equivalent`. |
| MessageDefinition.focus.max (max) | is equivalent to | MessageDefinition.focus.max | Element `MessageDefinition.focus.max` is mapped to FHIR R5 element `MessageDefinition.focus.max` as `Equivalent`. |
| MessageDefinition.responseRequired (responseRequired) | is broader than | MessageDefinition.responseRequired | Element `MessageDefinition.responseRequired` is mapped to FHIR R5 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) | is broader than | MessageDefinition.allowedResponse | Element `MessageDefinition.allowedResponse` is mapped to FHIR R5 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) | is broader than | MessageDefinition.allowedResponse.message | Element `MessageDefinition.allowedResponse.message` is mapped to FHIR R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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 R5 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. |
{
"resourceType": "ConceptMap",
"id": "R3-MessageDefinition-element-map-to-R5",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode": "fhir"
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger": 0,
"_valueInteger": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r5"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r5"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R3-MessageDefinition-element-map-to-R5",
"version": "0.1.0",
"name": "R3MessageDefinitionElementMapToR5",
"title": "Cross-version mapping for FHIR STU3 MessageDefinition to FHIR R5 MessageDefinition",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:05:00.2973356-05:00",
"contact": [
{
"name": "FHIR Infrastructure",
"telecom": [
{
"system": "url",
"value": "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description": "This ConceptMap represents cross-version mappings for elements from a FHIR STU3 MessageDefinition to FHIR R5.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceScopeCanonical": "http://hl7.org/fhir/3.0",
"targetScopeUri": "http://hl7.org/fhir/5.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|5.0.0",
"element": [
{
"code": "MessageDefinition.meta",
"display": "meta",
"target": [
{
"code": "MessageDefinition.meta",
"display": "MessageDefinition.meta",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.meta` is mapped to FHIR R5 element `MessageDefinition.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.meta` do not cover the following types: Meta.\nThe mappings for `MessageDefinition.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
}
]
},
{
"code": "MessageDefinition.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "MessageDefinition.implicitRules",
"display": "MessageDefinition.implicitRules",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.implicitRules` is mapped to FHIR R5 element `MessageDefinition.implicitRules` as `Equivalent`.\nAsserting 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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
}
]
},
{
"code": "MessageDefinition.language",
"display": "language",
"target": [
{
"code": "MessageDefinition.language",
"display": "MessageDefinition.language",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.language` is mapped to FHIR R5 element `MessageDefinition.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code": "MessageDefinition.text",
"display": "text",
"target": [
{
"code": "MessageDefinition.text",
"display": "MessageDefinition.text",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.text` is mapped to FHIR R5 element `MessageDefinition.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.text` do not cover the following types: Narrative.\nThe mappings for `MessageDefinition.text` do not cover the following types based on type expansion: div, status.\nContained 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."
}
]
},
{
"code": "MessageDefinition.contained",
"display": "contained",
"target": [
{
"code": "MessageDefinition.contained",
"display": "MessageDefinition.contained",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.contained` is mapped to FHIR R5 element `MessageDefinition.contained` as `SourceIsBroaderThanTarget`.\nThis 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."
}
]
},
{
"code": "MessageDefinition.url",
"display": "url",
"target": [
{
"code": "MessageDefinition.url",
"display": "MessageDefinition.url",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.url` is mapped to FHIR R5 element `MessageDefinition.url` as `Equivalent`.\nCan 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."
}
]
},
{
"code": "MessageDefinition.identifier",
"display": "identifier",
"target": [
{
"code": "MessageDefinition.identifier",
"display": "MessageDefinition.identifier",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.identifier` is mapped to FHIR R5 element `MessageDefinition.identifier` as `RelatedTo`.\nThe mappings for `MessageDefinition.identifier` do not cover the following types: Identifier.\nThe mappings for `MessageDefinition.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nTypically, 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."
}
]
},
{
"code": "MessageDefinition.version",
"display": "version",
"target": [
{
"code": "MessageDefinition.version",
"display": "MessageDefinition.version",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.version` is mapped to FHIR R5 element `MessageDefinition.version` as `Equivalent`.\nThere 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]."
}
]
},
{
"code": "MessageDefinition.name",
"display": "name",
"target": [
{
"code": "MessageDefinition.name",
"display": "MessageDefinition.name",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.name` is mapped to FHIR R5 element `MessageDefinition.name` as `Equivalent`.\nThe 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."
}
]
},
{
"code": "MessageDefinition.title",
"display": "title",
"target": [
{
"code": "MessageDefinition.title",
"display": "MessageDefinition.title",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.title` is mapped to FHIR R5 element `MessageDefinition.title` as `Equivalent`.\nThis name does not need to be machine-processing friendly and may contain punctuation, white-space, etc."
}
]
},
{
"code": "MessageDefinition.status",
"display": "status",
"target": [
{
"code": "MessageDefinition.status",
"display": "MessageDefinition.status",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.status` is mapped to FHIR R5 element `MessageDefinition.status` as `Equivalent`.\nAllows filtering of message definitions that are appropriate for use vs. not. \nThis is labeled as \"Is Modifier\" because applications should not use a retired message definition without due consideration."
}
]
},
{
"code": "MessageDefinition.experimental",
"display": "experimental",
"target": [
{
"code": "MessageDefinition.experimental",
"display": "MessageDefinition.experimental",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.experimental` is mapped to FHIR R5 element `MessageDefinition.experimental` as `Equivalent`.\nAllows 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."
}
]
},
{
"code": "MessageDefinition.date",
"display": "date",
"target": [
{
"code": "MessageDefinition.date",
"display": "MessageDefinition.date",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.date` is mapped to FHIR R5 element `MessageDefinition.date` as `Equivalent`.\nNote 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."
}
]
},
{
"code": "MessageDefinition.publisher",
"display": "publisher",
"target": [
{
"code": "MessageDefinition.publisher",
"display": "MessageDefinition.publisher",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.publisher` is mapped to FHIR R5 element `MessageDefinition.publisher` as `Equivalent`.\nUsually 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."
}
]
},
{
"code": "MessageDefinition.contact",
"display": "contact",
"target": [
{
"code": "MessageDefinition.contact",
"display": "MessageDefinition.contact",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.contact` is mapped to FHIR R5 element `MessageDefinition.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.contact` do not cover the following types: ContactDetail.\nThe mappings for `MessageDefinition.contact` do not cover the following types based on type expansion: name, telecom.\nMay be a web site, an email address, a telephone number, etc."
}
]
},
{
"code": "MessageDefinition.description",
"display": "description",
"target": [
{
"code": "MessageDefinition.description",
"display": "MessageDefinition.description",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.description` is mapped to FHIR R5 element `MessageDefinition.description` as `Equivalent`.\nThis 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)."
}
]
},
{
"code": "MessageDefinition.useContext",
"display": "useContext",
"target": [
{
"code": "MessageDefinition.useContext",
"display": "MessageDefinition.useContext",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.useContext` is mapped to FHIR R5 element `MessageDefinition.useContext` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.useContext` do not cover the following types: UsageContext.\nThe mappings for `MessageDefinition.useContext` do not cover the following types based on type expansion: code, value[x].\nWhen multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."
}
]
},
{
"code": "MessageDefinition.jurisdiction",
"display": "jurisdiction",
"target": [
{
"code": "MessageDefinition.jurisdiction",
"display": "MessageDefinition.jurisdiction",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.jurisdiction` is mapped to FHIR R5 element `MessageDefinition.jurisdiction` as `Equivalent`.\nIt may be possible for the message definition to be used in jurisdictions other than those for which it was originally designed or intended."
}
]
},
{
"code": "MessageDefinition.purpose",
"display": "purpose",
"target": [
{
"code": "MessageDefinition.purpose",
"display": "MessageDefinition.purpose",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.purpose` is mapped to FHIR R5 element `MessageDefinition.purpose` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "MessageDefinition.copyright",
"display": "copyright",
"target": [
{
"code": "MessageDefinition.copyright",
"display": "MessageDefinition.copyright",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.copyright` is mapped to FHIR R5 element `MessageDefinition.copyright` as `Equivalent`."
}
]
},
{
"code": "MessageDefinition.base",
"display": "base",
"target": [
{
"code": "MessageDefinition.base",
"display": "MessageDefinition.base",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.base` is mapped to FHIR R5 element `MessageDefinition.base` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.base` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.base` do not cover the following types based on type expansion: display, identifier, reference."
}
]
},
{
"code": "MessageDefinition.parent",
"display": "parent",
"target": [
{
"code": "MessageDefinition.parent",
"display": "MessageDefinition.parent",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.parent` is mapped to FHIR R5 element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.parent` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: display, identifier, reference."
}
]
},
{
"code": "MessageDefinition.replaces",
"display": "replaces",
"target": [
{
"code": "MessageDefinition.replaces",
"display": "MessageDefinition.replaces",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.replaces` is mapped to FHIR R5 element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.replaces` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: display, identifier, reference."
}
]
},
{
"code": "MessageDefinition.event",
"display": "event",
"target": [
{
"code": "MessageDefinition.event[x]",
"display": "MessageDefinition.event[x]",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.event` is mapped to FHIR R5 element `MessageDefinition.event[x]` as `Equivalent`.\nThe target context `MessageDefinition.event[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `MessageDefinition`."
}
]
},
{
"code": "MessageDefinition.category",
"display": "category",
"target": [
{
"code": "MessageDefinition.category",
"display": "MessageDefinition.category",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.category` is mapped to FHIR R5 element `MessageDefinition.category` as `Equivalent`."
}
]
},
{
"code": "MessageDefinition.focus",
"display": "focus",
"target": [
{
"code": "MessageDefinition.focus",
"display": "MessageDefinition.focus",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.focus` is mapped to FHIR R5 element `MessageDefinition.focus` as `Equivalent`."
}
]
},
{
"code": "MessageDefinition.focus.code",
"display": "code",
"target": [
{
"code": "MessageDefinition.focus.code",
"display": "MessageDefinition.focus.code",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.focus.code` is mapped to FHIR R5 element `MessageDefinition.focus.code` as `RelatedTo`.\nThe mappings for `MessageDefinition.focus.code` do not allow expression of the necessary codes, per the bindings on the source and target.\nMultiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc."
}
]
},
{
"code": "MessageDefinition.focus.profile",
"display": "profile",
"target": [
{
"code": "MessageDefinition.focus.profile",
"display": "MessageDefinition.focus.profile",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.focus.profile` is mapped to FHIR R5 element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.focus.profile` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: display, identifier, reference.\nThis 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."
}
]
},
{
"code": "MessageDefinition.focus.min",
"display": "min",
"target": [
{
"code": "MessageDefinition.focus.min",
"display": "MessageDefinition.focus.min",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.focus.min` is mapped to FHIR R5 element `MessageDefinition.focus.min` as `Equivalent`."
}
]
},
{
"code": "MessageDefinition.focus.max",
"display": "max",
"target": [
{
"code": "MessageDefinition.focus.max",
"display": "MessageDefinition.focus.max",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.focus.max` is mapped to FHIR R5 element `MessageDefinition.focus.max` as `Equivalent`."
}
]
},
{
"code": "MessageDefinition.responseRequired",
"display": "responseRequired",
"target": [
{
"code": "MessageDefinition.responseRequired",
"display": "MessageDefinition.responseRequired",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.responseRequired` is mapped to FHIR R5 element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.responseRequired` do not cover the following types: boolean.\nThe mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value."
}
]
},
{
"code": "MessageDefinition.allowedResponse",
"display": "allowedResponse",
"target": [
{
"code": "MessageDefinition.allowedResponse",
"display": "MessageDefinition.allowedResponse",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.allowedResponse` is mapped to FHIR R5 element `MessageDefinition.allowedResponse` as `Equivalent`.\nThis 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."
}
]
},
{
"code": "MessageDefinition.allowedResponse.message",
"display": "message",
"target": [
{
"code": "MessageDefinition.allowedResponse.message",
"display": "MessageDefinition.allowedResponse.message",
"relationship": "source-is-broader-than-target",
"comment": "Element `MessageDefinition.allowedResponse.message` is mapped to FHIR R5 element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: display, identifier, reference."
}
]
},
{
"code": "MessageDefinition.allowedResponse.situation",
"display": "situation",
"target": [
{
"code": "MessageDefinition.allowedResponse.situation",
"display": "MessageDefinition.allowedResponse.situation",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.allowedResponse.situation` is mapped to FHIR R5 element `MessageDefinition.allowedResponse.situation` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.meta|0.1.0",
"element": [
{
"code": "MessageDefinition.meta",
"display": "meta",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.meta` is mapped to FHIR R5 element `MessageDefinition.meta` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.meta` do not cover the following types: Meta.\nThe mappings for `MessageDefinition.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.text|0.1.0",
"element": [
{
"code": "MessageDefinition.text",
"display": "text",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.text` is mapped to FHIR R5 element `MessageDefinition.text` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.text` do not cover the following types: Narrative.\nThe mappings for `MessageDefinition.text` do not cover the following types based on type expansion: div, status.\nContained 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.identifier|0.1.0",
"element": [
{
"code": "MessageDefinition.identifier",
"display": "identifier",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.identifier` is mapped to FHIR R5 element `MessageDefinition.identifier` as `RelatedTo`.\nThe mappings for `MessageDefinition.identifier` do not cover the following types: Identifier.\nThe mappings for `MessageDefinition.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.\nTypically, 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.contact|0.1.0",
"element": [
{
"code": "MessageDefinition.contact",
"display": "contact",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.contact` is mapped to FHIR R5 element `MessageDefinition.contact` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.contact` do not cover the following types: ContactDetail.\nThe mappings for `MessageDefinition.contact` do not cover the following types based on type expansion: name, telecom.\nMay be a web site, an email address, a telephone number, etc."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.useContext|0.1.0",
"element": [
{
"code": "MessageDefinition.useContext",
"display": "useContext",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.useContext` is mapped to FHIR R5 element `MessageDefinition.useContext` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.useContext` do not cover the following types: UsageContext.\nThe mappings for `MessageDefinition.useContext` do not cover the following types based on type expansion: code, value[x].\nWhen multiple useContexts are specified, there is no expectation whether all or any of the contexts apply."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.base|0.1.0",
"element": [
{
"code": "MessageDefinition.base",
"display": "base",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.base` is mapped to FHIR R5 element `MessageDefinition.base` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.base` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.base` do not cover the following types based on type expansion: display, identifier, reference."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.parent|0.1.0",
"element": [
{
"code": "MessageDefinition.parent",
"display": "parent",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.parent` is mapped to FHIR R5 element `MessageDefinition.parent` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.parent` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.parent` do not cover the following types based on type expansion: display, identifier, reference."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.replaces|0.1.0",
"element": [
{
"code": "MessageDefinition.replaces",
"display": "replaces",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.replaces` is mapped to FHIR R5 element `MessageDefinition.replaces` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.replaces` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.replaces` do not cover the following types based on type expansion: display, identifier, reference."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.focus.code|0.1.0",
"element": [
{
"code": "MessageDefinition.focus.code",
"display": "code",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.focus.code` is mapped to FHIR R5 element `MessageDefinition.focus.code` as `RelatedTo`.\nThe mappings for `MessageDefinition.focus.code` do not allow expression of the necessary codes, per the bindings on the source and target.\nMultiple focuses addressing different resources may occasionally occur. E.g. to link or unlink a resource from a particular account or encounter, etc."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.focus.profile|0.1.0",
"element": [
{
"code": "MessageDefinition.focus.profile",
"display": "profile",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.focus.profile` is mapped to FHIR R5 element `MessageDefinition.focus.profile` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.focus.profile` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.focus.profile` do not cover the following types based on type expansion: display, identifier, reference.\nThis 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.responseRequired|0.1.0",
"element": [
{
"code": "MessageDefinition.responseRequired",
"display": "responseRequired",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.responseRequired` is mapped to FHIR R5 element `MessageDefinition.responseRequired` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.responseRequired` do not cover the following types: boolean.\nThe mappings for `MessageDefinition.responseRequired` do not cover the following types based on type expansion: value."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/MessageDefinition|3.0.2",
"target": "http://hl7.org/fhir/3.0/StructureDefinition/extension-MessageDefinition.allowedResponse.message|0.1.0",
"element": [
{
"code": "MessageDefinition.allowedResponse.message",
"display": "message",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `MessageDefinition.allowedResponse.message` is mapped to FHIR R5 element `MessageDefinition.allowedResponse.message` as `SourceIsBroaderThanTarget`.\nThe mappings for `MessageDefinition.allowedResponse.message` do not cover the following types: Reference.\nThe mappings for `MessageDefinition.allowedResponse.message` do not cover the following types based on type expansion: display, identifier, reference."
}
]
}
]
}
]
}