type: resource-definitionsresource: Communication

Communication Definitions

Communication

A clinical or business level record of information being transmitted or shared

Definition: A clinical or business level record of information being transmitted or shared; e.g. an alert that was sent to a responsible provider, a public health agency communication to a provider/reporter in response to a case report for a reportable condition.

Cardinality: 0..*

Mappings: workflow=Event; w5=workflow.encounter

Communication.identifier

Unique identifier

Definition: Business identifiers assigned to this communication by the performer or other systems which remain constant as the resource is updated and propagates from server to server.

Comments: This is a business identifier, not a resource identifier (see discussion). 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.

Requirements: Allows identification of the communication as it is known by various participating systems and in a way that remains consistent across servers.

Cardinality: 0..*

Type: Identifier

Summary: true

Mappings: workflow=Event.identifier; w5=FiveWs.identifier

Communication.basedOn

Request fulfilled by this communication

Definition: An order, proposal or plan fulfilled in whole or in part by this Communication.

Aliases: fulfills

Cardinality: 0..*

Type: Reference(CarePlan, CommunicationRequest, DeviceRequest, MedicationRequest, NutritionOrder, ServiceRequest, Task, VisionPrescription)

Summary: true

Mappings: workflow=Event.basedOn

Communication.partOf

Part of referenced event (e.g. Communication, Procedure)

Definition: A larger event (e.g. Communication, Procedure) of which this particular communication is a component or step.

Comments: The event the communication was part of - e.g. if you disclosed as "part" of counselling, it would be partOf that Procedure.

Aliases: container

Cardinality: 0..*

Type: Reference(Resource)

Summary: true

Mappings: workflow=Event.partOf

Communication.inResponseTo

Reply to

Definition: Prior communication that this communication is in response to.

Cardinality: 0..*

Type: Reference(Communication)

Communication.status

Definition: The status of the transmission.

Comments: 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.

Cardinality: 1..1

Type: code

Binding: required:event-status

Summary: true

Is Modifier: true (Reason: This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid)

Mappings: workflow=Event.status; w5=FiveWs.status

Communication.statusReason

Reason for current status

Definition: Captures the reason for the current state of the Communication.

Comments: 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.

Aliases: Suspended Reason, Cancelled Reason

Cardinality: 0..1

Type: CodeableConcept

Binding: example:communication-not-done-reason

Summary: true

Mappings: workflow=Event.statusReason

Communication.category

Message category

Definition: The type of message conveyed such as alert, notification, reminder, instruction, etc.

Comments: There may be multiple axes of categorization and one communication may serve multiple purposes.

Cardinality: 0..*

Type: CodeableConcept

Binding: example:communication-category

Mappings: w5=FiveWs.class

Communication.priority

routine | urgent | asap | stat

Definition: Characterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as stat, urgent, routine.

Comments: Used to prioritize workflow (such as which communication to read first) when the communication is planned or in progress.

Meaning if Missing: If missing, this communication should be treated with normal priority

Cardinality: 0..1

Type: code

Binding: required:request-priority

Summary: true

Mappings: w5=FiveWs.grade

Communication.medium

A channel of communication

Definition: A channel that was used for this communication (e.g. email, fax, SMS).

Cardinality: 0..*

Type: CodeableConcept

Binding: example:v3-ParticipationMode

Communication.subject

Focus of message

Definition: The patient or group that was the focus of this communication.

Aliases: patient

Cardinality: 0..1

Type: Reference(Patient, Group)

Summary: true

Mappings: workflow=Event.subject; w5=FiveWs.subject

Communication.topic

Description of the purpose/content

Definition: Description of the purpose/content, similar to a subject line in an email.

Comments: Communication.topic.text can be used without any codings.

Cardinality: 0..1

Type: CodeableConcept

Binding: example:communication-topic

Mappings: w5=FiveWs.context

Communication.about

Resources that pertain to this communication

Definition: Other resources that pertain to this communication and to which this communication should be associated.

Comments: Don't use Communication.about element when a more specific element exists, such as basedOn or reasonReference.

Cardinality: 0..*

Type: Reference(Resource)

Mappings: w5=FiveWs.context

Communication.encounter

The Encounter during which this Communication was created

Definition: The Encounter during which this Communication was created or to which the creation of this record is tightly associated.

Comments: 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.

Cardinality: 0..1

Type: Reference(Encounter)

Summary: true

Mappings: workflow=Event.encounter; w5=FiveWs.context

Communication.sent

When sent

Definition: The time when this communication was sent.

Cardinality: 0..1

Type: dateTime

Mappings: workflow=Event.occurrence[x] {Invariant: maps to period.start}; w5=FiveWs.done[x]

Communication.received

When received

Definition: The time when this communication arrived at the destination.

Cardinality: 0..1

Type: dateTime

Mappings: workflow=Event.occurrence[x] {Invariant: maps to period.end}; w5=FiveWs.done[x]

Communication.recipient

Who the information is shared with

Definition: The entity (e.g. person, organization, clinical information system, care team or device) which is the target of the communication.

Comments: If receipts need to be tracked by an individual, a separate resource instance will need to be created for each recipient. Multiple recipient communications are intended where either receipts are not tracked (e.g. a mass mail-out) or a receipt is captured in aggregate (all emails confirmed received by a particular time).

Cardinality: 0..*

Type: Reference(CareTeam, Device, Group, HealthcareService, Location, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson, Endpoint)

Mappings: workflow=Event.performer.actor; w5=FiveWs.actor

Communication.sender

Who shares the information

Definition: The entity (e.g. person, organization, clinical information system, or device) which is the source of the communication.

Cardinality: 0..1

Type: Reference(Device, Organization, Patient, Practitioner, PractitionerRole, RelatedPerson, HealthcareService, Endpoint, CareTeam)

Mappings: workflow=Event.performer.actor; w5=FiveWs.actor

Communication.reason

Indication for message

Definition: The reason or justification for the communication.

Comments: Textual reasons can be captured using reason.concept.text.

Cardinality: 0..*

Type: CodeableReference

Binding: example:clinical-findings

Summary: true

Mappings: workflow=Event.reason; w5=FiveWs.why[x]; rim=.reasonCode

Communication.payload

Message payload

Definition: Text, attachment(s), or resource(s) that was communicated to the recipient.

Cardinality: 0..*

Type: BackboneElement

Communication.payload.content[x]

Message part content

Definition: A communicated content (or for multi-part communications, one portion of the communication).

Comments: The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

If the content isn't codified, contentCodeableConcept.text can be used.

When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

Cardinality: 1..1

Type: Attachment, Reference(Resource), CodeableConcept

Communication.note

Comments made about the communication

Definition: Additional notes or commentary about the communication by the sender, receiver or other interested parties.

Cardinality: 0..*

Type: Annotation

Mappings: workflow=Event.note