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.

A unique ID of this request for reference purposes. It must be provided if user wants it returned as part of any output, otherwise it will be autogenerated, if needed, by CDS system. Does not need to be the actual ID of the source system.

The type of message to be sent such as alert, notification, reminder, instruction, etc. A plan or proposal that is fulfilled in whole or in part by this request.

Allows tracing of authorization for the request and tracking whether proposals/recommendations were acted upon.

The entity (e.g. person, organization, clinical information system, Completed or device) which terminated request(s) whose function is to be the source of the communication. taken by this new request.

Allows tracing the continuation of a therapy or administrative process instantiated through multiple requests.

The replacement could be because the initial request was immediately rejected (due to an issue) or because the previous request was completed, but the need for the action described by the request remains ongoing.

The entity (e.g. person, organization, clinical information system, A shared identifier common to all requests that were authorized more or device) which is less simultaneously by a single author, representing the intended target identifier of the communication. requisition, prescription or similar form.

Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.

Text, attachment(s), or resource(s) to be communicated to The status of the recipient. proposal or order.

This element is labeled as a modifier because the status contains the codes cancelled and entered-in-error that mark the request as not currently valid.

The communicated content (or for multi-part communications, one portion type of the communication). message to be sent such as alert, notification, reminder, instruction, etc.

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

Characterizes how quickly the proposed act must be initiated. Includes concepts such as stat, urgent, routine.

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

The patient or group that is the focus of this communication request.

The responsible person who authorizes this order, e.g. physician. This may be different than entity (e.g. person, organization, clinical information system, device, group, or care team) which is the author intended target of the order statement, e.g. clerk, who may have entered the statement into the order entry application. communication.

The resources which were related to producing this communication request.

The status encounter or episode of care within which the proposal or order. communication request was created.

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

The encounter within which communicated content (or for multi-part communications, one portion of the communication request was created. communication).

The time when this communication is to occur.

The reason or justification for For draft requests, indicates the communication request. date of initial creation. For requests with other statuses, indicates the date of activation.

The entity (e.g. person, organization, clinical information system, or device) which is to be the occurrence source of a the communication.

The individual who initiated the request and has responsibility for its activation.

The time when device, practitioner, etc. who initiated the request was made. request.

The patient who is organization the focus of this communication request. device or practitioner was acting on behalf of.

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request.

Characterizes how quickly Describes why the proposed act must be initiated. Includes concepts such as stat, urgent, routine. request is being made in coded or textual form.

Textual reasons can be caprued using reasonCode.text.

Indicates another resource whose existence justifies this request.

Comments made about the request by the requester, sender, recipient, subject or other participants.