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

Identifiers associated with Business identifiers assigned to this Communication that are defined communication by business processes and/ the performer or used to refer to it when a direct URL reference to other systems which remain constant as the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation). updated and propagates from server to server.

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

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.

A protocol, guideline, An order, proposal or other definition that was adhered to plan fulfilled in whole or in part by this communication event. Communication.

An order, proposal or plan fulfilled in whole or in part by A larger event (e.g. Communication, Procedure) of which this Communication. particular communication is a component or step.

This must point to some sort The event the communication was part of a 'Request' resource, such - e.g. if you disclosed as CarePlan, CommunicationRequest, ReferralRequest, MedicationRequest, etc. "part" of counselling, it would be partOf that Procedure.

Part of Prior communication that this action. communication is in response to.

The status of the transmission.

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.

If true, indicates that Captures the described communication event did not actually occur. reason for the current state of the Communication.

This element is labeled as a modifier because it marks the communication generally only used for "exception" statuses such as a communication that did not occur. "not-done", "suspended" or "aborted". The more attributes are populated, the more constrained reason for performing the negated statement is. event at all is captured in reasonCode, not here.

Describes why the communication event did not occur in coded and/or textual form. The type of message conveyed such as alert, notification, reminder, instruction, etc.

There may be specified if NotDone is "true" ( expression : notDone or notDoneReason.exists().not(), xpath: f:notDone/@value=true() or not(exists(f:notDoneReason))) multiple axes of categorization and one communication may serve multiple purposes.

The type of message conveyed Characterizes how quickly the planned or in progress communication must be addressed. Includes concepts such as alert, notification, reminder, instruction, etc. stat, urgent, routine.

There may be multiple axes of categorization and one Used to prioritize workflow (such as which communication may serve multiple purposes. to read first) when the communication is planned or in progress.

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

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

The entity (e.g. person, organization, clinical information system, or device) which was the target Description of the communication. If receipts need purpose/content, similar to be tracked by individual, a separate resource instance will need to be created for each recipient.  Multiple recipient communications are intended where either a receipt(s) is not tracked (e.g. a mass mail-out) or is captured subject line in aggregate (all emails confirmed received by a particular time). an email.

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

The Other resources which were responsible for or related that pertain to producing this communication. communication and to which this communication should be associated.

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

The encounter within Encounter during which the communication this Communication was sent. created or to which the creation of this record is tightly associated.

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.

The time when this communication was sent.

The time when this communication arrived at the destination.

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

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).

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

Indicates another resource whose existence justifies this The reason or justification for the communication.

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

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

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

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.

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