Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4B in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-CommunicationRequest-element-map-to-R3 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R4BCommunicationRequestElementMapToR3 | ||
This ConceptMap represents cross-version mappings for elements from a FHIR R4B CommunicationRequest to FHIR STU3.
Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to http://hl7.org/fhir/StructureDefinition/CommunicationRequest|3.0.2
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.meta (meta) | maps to wider concept | CommunicationRequest.meta | Element `CommunicationRequest.meta` is mapped to FHIR STU3 element `CommunicationRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.meta` do not cover the following types: Meta. The mappings for `CommunicationRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId. |
| CommunicationRequest.implicitRules (implicitRules) | is equivalent to | CommunicationRequest.implicitRules | Element `CommunicationRequest.implicitRules` is mapped to FHIR STU3 element `CommunicationRequest.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. |
| CommunicationRequest.language (language) | is equivalent to | CommunicationRequest.language | Element `CommunicationRequest.language` is mapped to FHIR STU3 element `CommunicationRequest.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). |
| CommunicationRequest.text (text) | maps to wider concept | CommunicationRequest.text | Element `CommunicationRequest.text` is mapped to FHIR STU3 element `CommunicationRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.text` do not cover the following types: Narrative. The mappings for `CommunicationRequest.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 information is added later. |
| CommunicationRequest.contained (contained) | is equivalent to | CommunicationRequest.contained | Element `CommunicationRequest.contained` is mapped to FHIR STU3 element `CommunicationRequest.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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. |
| CommunicationRequest.identifier (identifier) | maps to wider concept | CommunicationRequest.identifier | Element `CommunicationRequest.identifier` is mapped to FHIR STU3 element `CommunicationRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.identifier` do not cover the following types: Identifier. The mappings for `CommunicationRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. 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. |
| CommunicationRequest.basedOn (basedOn) | maps to wider concept | CommunicationRequest.basedOn | Element `CommunicationRequest.basedOn` is mapped to FHIR STU3 element `CommunicationRequest.basedOn` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.basedOn` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.basedOn` with unmapped reference targets: Resource. |
| CommunicationRequest.replaces (replaces) | maps to wider concept | CommunicationRequest.replaces | Element `CommunicationRequest.replaces` is mapped to FHIR STU3 element `CommunicationRequest.replaces` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.replaces` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.replaces` with unmapped reference targets: CommunicationRequest. The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing. |
| CommunicationRequest.groupIdentifier (groupIdentifier) | maps to wider concept | CommunicationRequest.groupIdentifier | Element `CommunicationRequest.groupIdentifier` is mapped to FHIR STU3 element `CommunicationRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.groupIdentifier` do not cover the following types: Identifier. The mappings for `CommunicationRequest.groupIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation. |
| CommunicationRequest.status (status) | is equivalent to | CommunicationRequest.status | Element `CommunicationRequest.status` is mapped to FHIR STU3 element `CommunicationRequest.status` as `Equivalent`. |
| CommunicationRequest.category (category) | is equivalent to | CommunicationRequest.category | Element `CommunicationRequest.category` is mapped to FHIR STU3 element `CommunicationRequest.category` as `Equivalent`. There may be multiple axes of categorization and one communication request may serve multiple purposes. |
| CommunicationRequest.priority (priority) | is equivalent to | CommunicationRequest.priority | Element `CommunicationRequest.priority` is mapped to FHIR STU3 element `CommunicationRequest.priority` as `Equivalent`. |
| CommunicationRequest.medium (medium) | is equivalent to | CommunicationRequest.medium | Element `CommunicationRequest.medium` is mapped to FHIR STU3 element `CommunicationRequest.medium` as `Equivalent`. |
| CommunicationRequest.subject (subject) | maps to wider concept | CommunicationRequest.subject | Element `CommunicationRequest.subject` is mapped to FHIR STU3 element `CommunicationRequest.subject` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.subject` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.subject` with unmapped reference targets: Group, Patient. |
| CommunicationRequest.about (about) | maps to wider concept | CommunicationRequest.topic | Element `CommunicationRequest.about` is mapped to FHIR STU3 element `CommunicationRequest.topic` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.about` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.about` with unmapped reference targets: Resource. Don't use CommunicationRequest.about element when a more specific element exists, such as basedOn, reasonReference, or replaces. |
| CommunicationRequest.encounter (encounter) | maps to wider concept | CommunicationRequest.context | Element `CommunicationRequest.encounter` is mapped to FHIR STU3 element `CommunicationRequest.context` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.encounter` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.encounter` with unmapped reference targets: Encounter. 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. |
| CommunicationRequest.payload (payload) | maps to wider concept | CommunicationRequest.payload | Element `CommunicationRequest.payload` is mapped to FHIR STU3 element `CommunicationRequest.payload` as `Equivalent`. |
| CommunicationRequest.payload.content[x] (content[x]) | maps to wider concept | CommunicationRequest.payload.content[x] | Element `CommunicationRequest.payload.content[x]` is mapped to FHIR STU3 element `CommunicationRequest.payload.content[x]` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.payload.content[x]` do not cover the following types: Attachment. The target context `CommunicationRequest.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `CommunicationRequest.payload`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R4B element `CommunicationRequest.payload.content[x]` with unmapped reference targets: Resource. Source element `CommunicationRequest.payload.content[x]` has unmapped reference types. While the target element `CommunicationRequest.payload.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. |
| CommunicationRequest.occurrence[x] (occurrence[x]) | is equivalent to | CommunicationRequest.occurrence[x] | Element `CommunicationRequest.occurrence[x]` is mapped to FHIR STU3 element `CommunicationRequest.occurrence[x]` as `SourceIsBroaderThanTarget`. The target context `CommunicationRequest.occurrence[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `CommunicationRequest`. |
| CommunicationRequest.authoredOn (authoredOn) | is equivalent to | CommunicationRequest.authoredOn | Element `CommunicationRequest.authoredOn` is mapped to FHIR STU3 element `CommunicationRequest.authoredOn` as `Equivalent`. |
| CommunicationRequest.requester (requester) | maps to wider concept | CommunicationRequest.requester.agent | Element `CommunicationRequest.requester` is mapped to FHIR STU3 element `CommunicationRequest.requester.agent` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.requester` with unmapped reference targets: Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. |
| CommunicationRequest.recipient (recipient) | maps to wider concept | CommunicationRequest.recipient | Element `CommunicationRequest.recipient` is mapped to FHIR STU3 element `CommunicationRequest.recipient` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.recipient` with unmapped reference targets: CareTeam, Device, Group, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. |
| CommunicationRequest.sender (sender) | maps to wider concept | CommunicationRequest.sender | Element `CommunicationRequest.sender` is mapped to FHIR STU3 element `CommunicationRequest.sender` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.sender` with unmapped reference targets: Device, HealthcareService, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson. |
| CommunicationRequest.reasonCode (reasonCode) | is equivalent to | CommunicationRequest.reasonCode | Element `CommunicationRequest.reasonCode` is mapped to FHIR STU3 element `CommunicationRequest.reasonCode` as `Equivalent`. Textual reasons can be captured using reasonCode.text. |
| CommunicationRequest.reasonReference (reasonReference) | maps to wider concept | CommunicationRequest.reasonReference | Element `CommunicationRequest.reasonReference` is mapped to FHIR STU3 element `CommunicationRequest.reasonReference` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R4B element `CommunicationRequest.reasonReference` with unmapped reference targets: Condition, DiagnosticReport, DocumentReference, Observation. |
| CommunicationRequest.note (note) | maps to wider concept | CommunicationRequest.note | Element `CommunicationRequest.note` is mapped to FHIR STU3 element `CommunicationRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.note` do not cover the following types: Annotation. The mappings for `CommunicationRequest.note` do not cover the following types based on type expansion: author[x], text, time. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: meta additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.meta (meta) | is equivalent to | Extension (R4B: meta additional types) | Element `CommunicationRequest.meta` is mapped to FHIR STU3 element `CommunicationRequest.meta` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.meta` do not cover the following types: Meta. The mappings for `CommunicationRequest.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, source, tag, versionId. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: text additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.text (text) | is equivalent to | Extension (R4B: text additional types) | Element `CommunicationRequest.text` is mapped to FHIR STU3 element `CommunicationRequest.text` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.text` do not cover the following types: Narrative. The mappings for `CommunicationRequest.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 information is added later. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: identifier additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.identifier (identifier) | is equivalent to | Extension (R4B: identifier additional types) | Element `CommunicationRequest.identifier` is mapped to FHIR STU3 element `CommunicationRequest.identifier` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.identifier` do not cover the following types: Identifier. The mappings for `CommunicationRequest.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. 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. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: groupIdentifier additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.groupIdentifier (groupIdentifier) | is equivalent to | Extension (R4B: groupIdentifier additional types) | Element `CommunicationRequest.groupIdentifier` is mapped to FHIR STU3 element `CommunicationRequest.groupIdentifier` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.groupIdentifier` do not cover the following types: Identifier. The mappings for `CommunicationRequest.groupIdentifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: Reason for current status (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.statusReason (statusReason) | is equivalent to | Extension (R4B: Reason for current status (new)) | Element `CommunicationRequest.statusReason` has a context of CommunicationRequest based on following the parent source element upwards and mapping to `CommunicationRequest`. Element `CommunicationRequest.statusReason` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This is generally only used for "exception" statuses such as "suspended" or "cancelled". The reason why the CommunicationRequest was created at all is captured in reasonCode, not here. [distinct reason codes for different statuses can be enforced using invariants if they are universal bindings]. |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: True if request is prohibiting action (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.doNotPerform (doNotPerform) | is equivalent to | Extension (R4B: True if request is prohibiting action (new)) | Element `CommunicationRequest.doNotPerform` has a context of CommunicationRequest based on following the parent source element upwards and mapping to `CommunicationRequest`. Element `CommunicationRequest.doNotPerform` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The attributes provided with the request qualify what is not to be done. |
Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: content additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.payload.content[x] (content[x]) | is equivalent to | Extension (R4B: content additional types) | Element `CommunicationRequest.payload.content[x]` is mapped to FHIR STU3 element `CommunicationRequest.payload.content[x]` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.payload.content[x]` do not cover the following types: Attachment. The target context `CommunicationRequest.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `CommunicationRequest.payload`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R4B element `CommunicationRequest.payload.content[x]` with unmapped reference targets: Resource. Source element `CommunicationRequest.payload.content[x]` has unmapped reference types. While the target element `CommunicationRequest.payload.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. |
Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to http://hl7.org/fhir/StructureDefinition/alternate-reference
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.payload.content[x] (content[x]) | is equivalent to | Extension | Element `CommunicationRequest.payload.content[x]` is mapped to FHIR STU3 element `CommunicationRequest.payload.content[x]` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.payload.content[x]` do not cover the following types: Attachment. The target context `CommunicationRequest.payload.content[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `CommunicationRequest.payload`. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR R4B element `CommunicationRequest.payload.content[x]` with unmapped reference targets: Resource. Source element `CommunicationRequest.payload.content[x]` has unmapped reference types. While the target element `CommunicationRequest.payload.content[x]` is a choice type and does not allow extensions, the `alternate-reference` extension can be applied to Reference values within it. |
Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/CommunicationRequest|4.3.0 to R4B: note additional typesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| CommunicationRequest.note (note) | is equivalent to | Extension (R4B: note additional types) | Element `CommunicationRequest.note` is mapped to FHIR STU3 element `CommunicationRequest.note` as `SourceIsBroaderThanTarget`. The mappings for `CommunicationRequest.note` do not cover the following types: Annotation. The mappings for `CommunicationRequest.note` do not cover the following types based on type expansion: author[x], text, time. |
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4b.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change