Communication

An occurrence of information being transmitted; e.g. an alert that was sent to a responsible provider, a public health agency was notified about a reportable condition.

= Must Support, = Is Modifier, = QiCore defined extension

Field	Card.	Type	Description
basedOn	0..*	List<Resource>	An order, proposal or plan fulfilled in whole or in part by this Communication.
status	1..1	String	The status of the transmission. Binding: Codes identifying the stage lifecycle stage of a event (required)
notDoneReason	0..1	Concept	Describes why the communication event did not occur in coded and/or textual form. Binding: Codes for the reason why a communication was not done. (example)
category	0..*	List<Concept>	The type of message conveyed such as alert, notification, reminder, instruction, etc. Binding: Codes for general categories of communications such as alerts, instruction, etc. (example)
medium	0..*	List<Concept>	A channel that was used for this communication (e.g. email, fax). Binding: A set of codes specifying the modality by which the Entity playing the Role is participating in the Act. Examples: Physically present, over the telephone, written communication. Rationale: Particularly for author (originator) participants this is used to specify whether the information represented by the act was initially provided verbally, (hand-)written, or electronically. Open Issue: There needs to be a reexamination of the hierarchies as there seems to be some muddling between ELECTRONIC and other concepts that involve electronic communication that are in other hierarchies. (example)
subject	0..1	Patient | Group	The patient or group that was the focus of this communication.
recipient	0..*	List<Device | Organization | Patient | Practitioner | RelatedPerson | Group>	The entity (e.g. person, organization, clinical information system, or device) which was the target of the communication. If receipts need 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 in aggregate (all emails confirmed received by a particular time).
context	0..1	Encounter | EpisodeOfCare	The encounter within which the communication was sent.
sent	0..1	DateTime	The time when this communication was sent.
received	0..1	DateTime	The time when this communication arrived at the destination.
sender	0..1	Device | Organization | Patient | Practitioner | RelatedPerson	The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
reasonCode	0..*	List<Concept>	The reason or justification for the communication. Binding: This value set includes all the "Clinical finding" SNOMED CT codes - concepts where concept is-a 404684003 (Clinical finding (finding)). (example)