CommunicationRequest

A request to convey information; e.g. the CDS system proposes that an alert be sent to a responsible provider, the CDS system proposes that the public health agency be notified about a reportable condition.

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

Field	Card.	Type	Description
orderedBy	0..1	Extension	Agent that ordered the communication.
authorizedBy	0..1	Extension	The practitioner who authorized the communication request, usually the same as the orderer when the orderer is a practitioner.
reasonRejected	0..1	Extension	The reason associated with the rejection of this communication request by the receiver. Applicable only if the status is rejected. Binding: Reason communication request was not performed (example)
status	1..1	String	The status of the proposal or order. Binding: Codes identifying the stage lifecycle stage of a request (required)
category	0..*	List<Concept>	The type of message to be sent 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 encounter or episode of care within which the communication request was created.
recipient	0..*	List<Device | Organization | Patient | Practitioner | RelatedPerson | Group | CareTeam>	The entity (e.g. person, organization, clinical information system, device, group, or care team) which is the intended target of the communication.
context	0..1	Encounter | EpisodeOfCare	The encounter or episode of care within which the communication request was created.
occurrence[x]	0..1	DateTime | Interval<DateTime>	The time when this communication is to occur.
sender	0..1	Device | Organization | Patient | Practitioner | RelatedPerson	The entity (e.g. person, organization, clinical information system, or device) which is to be the source of the communication.
requester	0..1	requester	The individual who initiated the request and has responsibility for its activation.
reasonCode	0..*	List<Concept>	Describes why the request is being made in coded or textual form. Binding: A set of codes specifying the motivation, cause, or rationale of an Act, when such rationale is not reasonably represented as an ActRelationship of type "has reason" linking to another Act. Examples: Example reasons that might qualify for being coded in this field might be: "routine requirement", "infectious disease reporting requirement", "on patient request", "required by law". (example)