Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions

ConceptMap: R3CommunicationElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-Communication-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3CommunicationElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 Communication to FHIR R4.

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to Communicationversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
Communication.meta (meta)is equivalent toCommunication.metaElement `Communication.meta` is mapped to FHIR R4 element `Communication.meta` as `Equivalent`.
Communication.implicitRules (implicitRules)is equivalent toCommunication.implicitRulesElement `Communication.implicitRules` is mapped to FHIR R4 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. 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.
Communication.language (language)is equivalent toCommunication.languageElement `Communication.language` is mapped to FHIR R4 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 toCommunication.textElement `Communication.text` is mapped to FHIR R4 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 in formation is added later.
Communication.contained (contained)is equivalent toCommunication.containedElement `Communication.contained` is mapped to FHIR R4 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.
Communication.identifier (identifier)is equivalent toCommunication.identifierElement `Communication.identifier` is mapped to FHIR R4 element `Communication.identifier` as `Equivalent`.
Communication.basedOn (basedOn)is equivalent toCommunication.basedOnElement `Communication.basedOn` is mapped to FHIR R4 element `Communication.basedOn` as `Equivalent`. This must point to some sort of a 'Request' resource, such as CarePlan, CommunicationRequest, ReferralRequest, MedicationRequest, etc.
Communication.partOf (partOf)is equivalent toCommunication.partOfElement `Communication.partOf` is mapped to FHIR R4 element `Communication.partOf` as `Equivalent`.
Communication.status (status)maps to wider conceptCommunication.statusElement `Communication.status` is mapped to FHIR R4 element `Communication.status` as `RelatedTo`. The mappings for `Communication.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `Communication.status` is a modifier element, so this extension does not need to be defined as a modifier. 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.category (category)is equivalent toCommunication.categoryElement `Communication.category` is mapped to FHIR R4 element `Communication.category` as `Equivalent`. There may be multiple axes of categorization and one communication may serve multiple purposes.
Communication.medium (medium)is equivalent toCommunication.mediumElement `Communication.medium` is mapped to FHIR R4 element `Communication.medium` as `Equivalent`.
Communication.subject (subject)is equivalent toCommunication.subjectElement `Communication.subject` is mapped to FHIR R4 element `Communication.subject` as `Equivalent`.
Communication.recipient (recipient)is equivalent toCommunication.recipientElement `Communication.recipient` is mapped to FHIR R4 element `Communication.recipient` as `Equivalent`.
Communication.context (context)maps to wider conceptCommunication.encounterElement `Communication.context` is mapped to FHIR R4 element `Communication.encounter` as `SourceIsBroaderThanTarget`. The mappings for `Communication.context` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `Communication.context` with unmapped reference targets: EpisodeOfCare.
Communication.sent (sent)is equivalent toCommunication.sentElement `Communication.sent` is mapped to FHIR R4 element `Communication.sent` as `Equivalent`.
Communication.received (received)is equivalent toCommunication.receivedElement `Communication.received` is mapped to FHIR R4 element `Communication.received` as `Equivalent`.
Communication.sender (sender)is equivalent toCommunication.senderElement `Communication.sender` is mapped to FHIR R4 element `Communication.sender` as `Equivalent`.
Communication.reasonCode (reasonCode)is equivalent toCommunication.reasonCodeElement `Communication.reasonCode` is mapped to FHIR R4 element `Communication.reasonCode` as `Equivalent`. Textual reasons can be caprued using reasonCode.text.
Communication.reasonReference (reasonReference)is equivalent toCommunication.reasonReferenceElement `Communication.reasonReference` is mapped to FHIR R4 element `Communication.reasonReference` as `Equivalent`.
Communication.payload (payload)maps to wider conceptCommunication.payloadElement `Communication.payload` is mapped to FHIR R4 element `Communication.payload` as `Equivalent`.
Communication.payload.content[x] (content[x])is equivalent toCommunication.payload.content[x]Element `Communication.payload.content[x]` is mapped to FHIR R4 element `Communication.payload.content[x]` as `Equivalent`. 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 toCommunication.noteElement `Communication.note` is mapped to FHIR R4 element `Communication.note` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to STU3: Instantiates protocol or definition (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Communication.definition (definition)is equivalent toExtension (STU3: Instantiates protocol or definition (new))Element `Communication.definition` has a context of Communication based on following the parent source element upwards and mapping to `Communication`. Element `Communication.definition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to STU3: preparation | in-progress | suspended | aborted | completed | entered-in-error additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
Communication.status (status)is equivalent toExtension (STU3: preparation | in-progress | suspended | aborted | completed | entered-in-error additional codes)Element `Communication.status` is mapped to FHIR R4 element `Communication.status` as `RelatedTo`. The mappings for `Communication.status` do not allow expression of the necessary codes, per the bindings on the source and target. The target context `Communication.status` is a modifier element, so this extension does not need to be defined as a modifier. 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to STU3: Communication did not occur (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Communication.notDone (notDone)is equivalent toExtension (STU3: Communication did not occur (new))Element `Communication.notDone` has a context of Communication based on following the parent source element upwards and mapping to `Communication`. Element `Communication.notDone` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is labeled as a modifier because it marks the communication as a communication that did not occur. The more attributes are populated, the more constrained the negated statement is.

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to STU3: Why communication did not occur (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Communication.notDoneReason (notDoneReason)is equivalent toExtension (STU3: Why communication did not occur (new))Element `Communication.notDoneReason` has a context of Communication based on following the parent source element upwards and mapping to `Communication`. Element `Communication.notDoneReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/Communication|3.0.2 to STU3: Focal resources (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
Communication.topic (topic)is equivalent toExtension (STU3: Focal resources (new))Element `Communication.topic` has a context of Communication based on following the parent source element upwards and mapping to `Communication`. Element `Communication.topic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).