FHIR IG analytics| Package | hl7.fhir.uv.xver-r4.r5 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R4-Communication-element-map-to-R5.json |
| FHIR Version | R5 |
| Source | http://hl7.org/fhir/uv/xver-r4.r5/0.1.0/ConceptMap-R4-Communication-element-map-to-R5.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R4-Communication-element-map-to-R5 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:04:34.7393185-05:00 |
| Name | R4CommunicationElementMapToR5 |
| Title | Cross-version mapping for FHIR R4 Communication to FHIR R5 Communication |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R4 Communication to FHIR R5. |
No resources found
| StructureDefinition | ||
| hl7.fhir.uv.xver-r4.r5#0.1.0 | extension-Communication.payload.content | R4: content additional types |
| hl7.fhir.uv.xver-r4.r5#0.1.0 | extension-Communication.reasonReference | R4: Why was communication done? additional types |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R4-Communication-element-map-to-R5
Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|4.0.1 to Communicationversion: 5.0.0)
| Source Code | Relationship | Target Code | Comment |
| Communication.meta (meta) | is equivalent to | Communication.meta | Element `Communication.meta` is mapped to FHIR R5 element `Communication.meta` as `Equivalent`. |
| Communication.implicitRules (implicitRules) | is equivalent to | Communication.implicitRules | Element `Communication.implicitRules` is mapped to FHIR R5 element `Communication.implicitRules` as `Equivalent`. Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. |
| Communication.language (language) | is equivalent to | Communication.language | Element `Communication.language` is mapped to FHIR R5 element `Communication.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). |
| Communication.text (text) | is equivalent to | Communication.text | Element `Communication.text` is mapped to FHIR R5 element `Communication.text` as `Equivalent`. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
| Communication.contained (contained) | is equivalent to | Communication.contained | Element `Communication.contained` is mapped to FHIR R5 element `Communication.contained` as `Equivalent`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
| Communication.identifier (identifier) | is equivalent to | Communication.identifier | Element `Communication.identifier` is mapped to FHIR R5 element `Communication.identifier` as `Equivalent`. This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number. |
| Communication.instantiatesCanonical (instantiatesCanonical) | is equivalent to | Communication.instantiatesCanonical | Element `Communication.instantiatesCanonical` is mapped to FHIR R5 element `Communication.instantiatesCanonical` as `Equivalent`. |
| Communication.instantiatesUri (instantiatesUri) | is equivalent to | Communication.instantiatesUri | Element `Communication.instantiatesUri` is mapped to FHIR R5 element `Communication.instantiatesUri` as `Equivalent`. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier. |
| Communication.basedOn (basedOn) | is equivalent to | Communication.basedOn | Element `Communication.basedOn` is mapped to FHIR R5 element `Communication.basedOn` as `Equivalent`. This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc. |
| Communication.partOf (partOf) | is equivalent to | Communication.partOf | Element `Communication.partOf` is mapped to FHIR R5 element `Communication.partOf` as `Equivalent`. |
| Communication.inResponseTo (inResponseTo) | is equivalent to | Communication.inResponseTo | Element `Communication.inResponseTo` is mapped to FHIR R5 element `Communication.inResponseTo` as `Equivalent`. |
| Communication.status (status) | is equivalent to | Communication.status | Element `Communication.status` is mapped to FHIR R5 element `Communication.status` as `Equivalent`. This element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid. |
| Communication.statusReason (statusReason) | is equivalent to | Communication.statusReason | Element `Communication.statusReason` is mapped to FHIR R5 element `Communication.statusReason` as `Equivalent`. This is generally only used for "exception" statuses such as "not-done", "suspended" or "aborted". The reason for performing the event at all is captured in reasonCode, not here. |
| Communication.category (category) | is equivalent to | Communication.category | Element `Communication.category` is mapped to FHIR R5 element `Communication.category` as `Equivalent`. There may be multiple axes of categorization and one communication may serve multiple purposes. |
| Communication.priority (priority) | is equivalent to | Communication.priority | Element `Communication.priority` is mapped to FHIR R5 element `Communication.priority` as `Equivalent`. Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress. |
| Communication.medium (medium) | is equivalent to | Communication.medium | Element `Communication.medium` is mapped to FHIR R5 element `Communication.medium` as `Equivalent`. |
| Communication.subject (subject) | is equivalent to | Communication.subject | Element `Communication.subject` is mapped to FHIR R5 element `Communication.subject` as `Equivalent`. |
| Communication.topic (topic) | is equivalent to | Communication.topic | Element `Communication.topic` is mapped to FHIR R5 element `Communication.topic` as `Equivalent`. Communication.topic.text can be used without any codings. |
| Communication.about (about) | is equivalent to | Communication.about | Element `Communication.about` is mapped to FHIR R5 element `Communication.about` as `Equivalent`. Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference. |
| Communication.encounter (encounter) | is equivalent to | Communication.encounter | Element `Communication.encounter` is mapped to FHIR R5 element `Communication.encounter` as `Equivalent`. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. |
| Communication.sent (sent) | is equivalent to | Communication.sent | Element `Communication.sent` is mapped to FHIR R5 element `Communication.sent` as `Equivalent`. |
| Communication.received (received) | is equivalent to | Communication.received | Element `Communication.received` is mapped to FHIR R5 element `Communication.received` as `Equivalent`. |
| Communication.recipient (recipient) | is equivalent to | Communication.recipient | Element `Communication.recipient` is mapped to FHIR R5 element `Communication.recipient` as `Equivalent`. |
| Communication.sender (sender) | is equivalent to | Communication.sender | Element `Communication.sender` is mapped to FHIR R5 element `Communication.sender` as `Equivalent`. |
| Communication.reasonCode (reasonCode) | is narrower than | Communication.reason | Element `Communication.reasonCode` is mapped to FHIR R5 element `Communication.reason` as `SourceIsNarrowerThanTarget`. Textual reasons can be captured using reasonCode.text. |
| Communication.reasonReference (reasonReference) | is broader than | Communication.reason | Element `Communication.reasonReference` is mapped to FHIR R5 element `Communication.reason` as `SourceIsBroaderThanTarget`. The mappings for `Communication.reasonReference` do not cover the following types: Reference. |
| Communication.payload (payload) | is broader than | Communication.payload | Element `Communication.payload` is mapped to FHIR R5 element `Communication.payload` as `Equivalent`. |
| Communication.payload.content[x] (content[x]) | is broader than | Communication.payload.content[x] | Element `Communication.payload.content[x]` is mapped to FHIR R5 element `Communication.payload.content[x]` as `SourceIsBroaderThanTarget`. The mappings for `Communication.payload.content[x]` do not cover the following types: string. The target context `Communication.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Communication.payload`. |
| Communication.note (note) | is equivalent to | Communication.note | Element `Communication.note` is mapped to FHIR R5 element `Communication.note` as `Equivalent`. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|4.0.1 to R4: Why was communication done? additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Communication.reasonReference (reasonReference) | is broader than | Extension (R4: Why was communication done? additional types) | Element `Communication.reasonReference` is mapped to FHIR R5 element `Communication.reason` as `SourceIsBroaderThanTarget`. The mappings for `Communication.reasonReference` do not cover the following types: Reference. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|4.0.1 to R4: content additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| Communication.payload.content[x] (content[x]) | is equivalent to | Extension (R4: content additional types) | Element `Communication.payload.content[x]` is mapped to FHIR R5 element `Communication.payload.content[x]` as `SourceIsBroaderThanTarget`. The mappings for `Communication.payload.content[x]` do not cover the following types: string. The target context `Communication.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Communication.payload`. |
{
"resourceType": "ConceptMap",
"id": "R4-Communication-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-r4.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-r4.r5"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R4-Communication-element-map-to-R5",
"version": "0.1.0",
"name": "R4CommunicationElementMapToR5",
"title": "Cross-version mapping for FHIR R4 Communication to FHIR R5 Communication",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:04:34.7393185-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 R4 Communication to FHIR R5.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceScopeCanonical": "http://hl7.org/fhir/4.0",
"targetScopeUri": "http://hl7.org/fhir/5.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/Communication|4.0.1",
"target": "http://hl7.org/fhir/StructureDefinition/Communication|5.0.0",
"element": [
{
"code": "Communication.meta",
"display": "meta",
"target": [
{
"code": "Communication.meta",
"display": "Communication.meta",
"relationship": "equivalent",
"comment": "Element `Communication.meta` is mapped to FHIR R5 element `Communication.meta` as `Equivalent`."
}
]
},
{
"code": "Communication.implicitRules",
"display": "implicitRules",
"target": [
{
"code": "Communication.implicitRules",
"display": "Communication.implicitRules",
"relationship": "equivalent",
"comment": "Element `Communication.implicitRules` is mapped to FHIR R5 element `Communication.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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc."
}
]
},
{
"code": "Communication.language",
"display": "language",
"target": [
{
"code": "Communication.language",
"display": "Communication.language",
"relationship": "equivalent",
"comment": "Element `Communication.language` is mapped to FHIR R5 element `Communication.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": "Communication.text",
"display": "text",
"target": [
{
"code": "Communication.text",
"display": "Communication.text",
"relationship": "equivalent",
"comment": "Element `Communication.text` is mapped to FHIR R5 element `Communication.text` as `Equivalent`.\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 information is added later."
}
]
},
{
"code": "Communication.contained",
"display": "contained",
"target": [
{
"code": "Communication.contained",
"display": "Communication.contained",
"relationship": "equivalent",
"comment": "Element `Communication.contained` is mapped to FHIR R5 element `Communication.contained` as `Equivalent`.\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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "Communication.identifier",
"display": "identifier",
"target": [
{
"code": "Communication.identifier",
"display": "Communication.identifier",
"relationship": "equivalent",
"comment": "Element `Communication.identifier` is mapped to FHIR R5 element `Communication.identifier` as `Equivalent`.\nThis is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number."
}
]
},
{
"code": "Communication.instantiatesCanonical",
"display": "instantiatesCanonical",
"target": [
{
"code": "Communication.instantiatesCanonical",
"display": "Communication.instantiatesCanonical",
"relationship": "equivalent",
"comment": "Element `Communication.instantiatesCanonical` is mapped to FHIR R5 element `Communication.instantiatesCanonical` as `Equivalent`."
}
]
},
{
"code": "Communication.instantiatesUri",
"display": "instantiatesUri",
"target": [
{
"code": "Communication.instantiatesUri",
"display": "Communication.instantiatesUri",
"relationship": "equivalent",
"comment": "Element `Communication.instantiatesUri` is mapped to FHIR R5 element `Communication.instantiatesUri` as `Equivalent`.\nThis might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier."
}
]
},
{
"code": "Communication.basedOn",
"display": "basedOn",
"target": [
{
"code": "Communication.basedOn",
"display": "Communication.basedOn",
"relationship": "equivalent",
"comment": "Element `Communication.basedOn` is mapped to FHIR R5 element `Communication.basedOn` as `Equivalent`.\nThis must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ServiceRequest, MedicationRequest, etc."
}
]
},
{
"code": "Communication.partOf",
"display": "partOf",
"target": [
{
"code": "Communication.partOf",
"display": "Communication.partOf",
"relationship": "equivalent",
"comment": "Element `Communication.partOf` is mapped to FHIR R5 element `Communication.partOf` as `Equivalent`."
}
]
},
{
"code": "Communication.inResponseTo",
"display": "inResponseTo",
"target": [
{
"code": "Communication.inResponseTo",
"display": "Communication.inResponseTo",
"relationship": "equivalent",
"comment": "Element `Communication.inResponseTo` is mapped to FHIR R5 element `Communication.inResponseTo` as `Equivalent`."
}
]
},
{
"code": "Communication.status",
"display": "status",
"target": [
{
"code": "Communication.status",
"display": "Communication.status",
"relationship": "equivalent",
"comment": "Element `Communication.status` is mapped to FHIR R5 element `Communication.status` as `Equivalent`.\nThis element is labeled as a modifier because the status contains the codes aborted and entered-in-error that mark the communication as not currently valid."
}
]
},
{
"code": "Communication.statusReason",
"display": "statusReason",
"target": [
{
"code": "Communication.statusReason",
"display": "Communication.statusReason",
"relationship": "equivalent",
"comment": "Element `Communication.statusReason` is mapped to FHIR R5 element `Communication.statusReason` as `Equivalent`.\nThis is generally only used for \"exception\" statuses such as \"not-done\", \"suspended\" or \"aborted\". The reason for performing the event at all is captured in reasonCode, not here."
}
]
},
{
"code": "Communication.category",
"display": "category",
"target": [
{
"code": "Communication.category",
"display": "Communication.category",
"relationship": "equivalent",
"comment": "Element `Communication.category` is mapped to FHIR R5 element `Communication.category` as `Equivalent`.\nThere may be multiple axes of categorization and one communication may serve multiple purposes."
}
]
},
{
"code": "Communication.priority",
"display": "priority",
"target": [
{
"code": "Communication.priority",
"display": "Communication.priority",
"relationship": "equivalent",
"comment": "Element `Communication.priority` is mapped to FHIR R5 element `Communication.priority` as `Equivalent`.\nUsed to prioritize workflow (such as which communication to read first) when the communication is planned or in progress."
}
]
},
{
"code": "Communication.medium",
"display": "medium",
"target": [
{
"code": "Communication.medium",
"display": "Communication.medium",
"relationship": "equivalent",
"comment": "Element `Communication.medium` is mapped to FHIR R5 element `Communication.medium` as `Equivalent`."
}
]
},
{
"code": "Communication.subject",
"display": "subject",
"target": [
{
"code": "Communication.subject",
"display": "Communication.subject",
"relationship": "equivalent",
"comment": "Element `Communication.subject` is mapped to FHIR R5 element `Communication.subject` as `Equivalent`."
}
]
},
{
"code": "Communication.topic",
"display": "topic",
"target": [
{
"code": "Communication.topic",
"display": "Communication.topic",
"relationship": "equivalent",
"comment": "Element `Communication.topic` is mapped to FHIR R5 element `Communication.topic` as `Equivalent`.\nCommunication.topic.text can be used without any codings."
}
]
},
{
"code": "Communication.about",
"display": "about",
"target": [
{
"code": "Communication.about",
"display": "Communication.about",
"relationship": "equivalent",
"comment": "Element `Communication.about` is mapped to FHIR R5 element `Communication.about` as `Equivalent`.\nDon't use Communication.about element when a more specific element exists, such as basedOn or reasonReference."
}
]
},
{
"code": "Communication.encounter",
"display": "encounter",
"target": [
{
"code": "Communication.encounter",
"display": "Communication.encounter",
"relationship": "equivalent",
"comment": "Element `Communication.encounter` is mapped to FHIR R5 element `Communication.encounter` as `Equivalent`.\nThis will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter."
}
]
},
{
"code": "Communication.sent",
"display": "sent",
"target": [
{
"code": "Communication.sent",
"display": "Communication.sent",
"relationship": "equivalent",
"comment": "Element `Communication.sent` is mapped to FHIR R5 element `Communication.sent` as `Equivalent`."
}
]
},
{
"code": "Communication.received",
"display": "received",
"target": [
{
"code": "Communication.received",
"display": "Communication.received",
"relationship": "equivalent",
"comment": "Element `Communication.received` is mapped to FHIR R5 element `Communication.received` as `Equivalent`."
}
]
},
{
"code": "Communication.recipient",
"display": "recipient",
"target": [
{
"code": "Communication.recipient",
"display": "Communication.recipient",
"relationship": "equivalent",
"comment": "Element `Communication.recipient` is mapped to FHIR R5 element `Communication.recipient` as `Equivalent`."
}
]
},
{
"code": "Communication.sender",
"display": "sender",
"target": [
{
"code": "Communication.sender",
"display": "Communication.sender",
"relationship": "equivalent",
"comment": "Element `Communication.sender` is mapped to FHIR R5 element `Communication.sender` as `Equivalent`."
}
]
},
{
"code": "Communication.reasonCode",
"display": "reasonCode",
"target": [
{
"code": "Communication.reason",
"display": "Communication.reason",
"relationship": "source-is-narrower-than-target",
"comment": "Element `Communication.reasonCode` is mapped to FHIR R5 element `Communication.reason` as `SourceIsNarrowerThanTarget`.\nTextual reasons can be captured using reasonCode.text."
}
]
},
{
"code": "Communication.reasonReference",
"display": "reasonReference",
"target": [
{
"code": "Communication.reason",
"display": "Communication.reason",
"relationship": "source-is-broader-than-target",
"comment": "Element `Communication.reasonReference` is mapped to FHIR R5 element `Communication.reason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Communication.reasonReference` do not cover the following types: Reference."
}
]
},
{
"code": "Communication.payload",
"display": "payload",
"target": [
{
"code": "Communication.payload",
"display": "Communication.payload",
"relationship": "source-is-broader-than-target",
"comment": "Element `Communication.payload` is mapped to FHIR R5 element `Communication.payload` as `Equivalent`."
}
]
},
{
"code": "Communication.payload.content[x]",
"display": "content[x]",
"target": [
{
"code": "Communication.payload.content[x]",
"display": "Communication.payload.content[x]",
"relationship": "source-is-broader-than-target",
"comment": "Element `Communication.payload.content[x]` is mapped to FHIR R5 element `Communication.payload.content[x]` as `SourceIsBroaderThanTarget`.\nThe mappings for `Communication.payload.content[x]` do not cover the following types: string.\nThe target context `Communication.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Communication.payload`."
}
]
},
{
"code": "Communication.note",
"display": "note",
"target": [
{
"code": "Communication.note",
"display": "Communication.note",
"relationship": "equivalent",
"comment": "Element `Communication.note` is mapped to FHIR R5 element `Communication.note` as `Equivalent`."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Communication|4.0.1",
"target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Communication.reasonReference|0.1.0",
"element": [
{
"code": "Communication.reasonReference",
"display": "reasonReference",
"target": [
{
"code": "Extension",
"relationship": "source-is-broader-than-target",
"comment": "Element `Communication.reasonReference` is mapped to FHIR R5 element `Communication.reason` as `SourceIsBroaderThanTarget`.\nThe mappings for `Communication.reasonReference` do not cover the following types: Reference."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/Communication|4.0.1",
"target": "http://hl7.org/fhir/4.0/StructureDefinition/extension-Communication.payload.content|0.1.0",
"element": [
{
"code": "Communication.payload.content[x]",
"display": "content[x]",
"target": [
{
"code": "Extension",
"relationship": "equivalent",
"comment": "Element `Communication.payload.content[x]` is mapped to FHIR R5 element `Communication.payload.content[x]` as `SourceIsBroaderThanTarget`.\nThe mappings for `Communication.payload.content[x]` do not cover the following types: string.\nThe target context `Communication.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `Communication.payload`."
}
]
}
]
}
]
}