The definition of an action to be performed. Some aspects of the definition are specified statically, and some aspects can be specified dynamically by referencing logic defined in a library.

A unique identifier for the action. The identifier SHALL be unique within the container in which it appears, and MAY be universally unique.

A user-visible label for the action.

The title of the action displayed to a user.

A short description of the action used to provide a summary to display to the user.

A text equivalent of the action to be performed. This provides a human-interpretable description of the action when the definition is consumed by a system that may not be capable of interpreting it dynamically.

The concept represented by this action or its sub-actions.

The evidence grade and the sources of evidence for this action.

Didactic or other informational resources associated with the action that can be provided to the CDS recipient. Information resources can include inline text commentary and links to web resources.

A relationship to another action such as "before" or "30-60 minutes after start of".

The unique identifier of the related action.

The relationship of this action to the related action.

A duration or range of durations to apply to the relationship. For example, 30-60 minutes before.

An optional indicator for how the relationship is anchored to the related action. For example "before the start" or "before the end" of the related action.

The type of participant in the action.

The type of action to perform (create, update, remove).

A behavior associated with the action. Behaviors define how the action is to be presented and/or executed within the receiving environment.

The type of the behavior to be described, such as grouping, visual, or selection behaviors.

The specific behavior. The code used here is determined by the type of behavior being described. For example, the grouping behavior uses the grouping-behavior-type valueset.

The resource that is the target of the action (e.g. CommunicationRequest). The resource described here defines any aspects of the action that can be specified statically (i.e. are known at the time of definition).

Note that the resource is optional, and if no resource is specified, a customization with a root (/) path can be used to define the entire resource dynamically.

Customizations that should be applied to the statically defined resource. For example, if the dosage of a medication must be computed based on the patient's weight, a customization would be used to specify an expression that calculated the weight, and the path on the resource that would contain the result.

The path to the element to be customized. This is the path on the resource that will hold the result of the calculation defined by the expression.

An expression specifying the value of the customized element.

Sub actions that are contained within the action. The behavior of this action determines the functionality of the sub-actions. For example, a selection behavior of at-most-one indicates that of the sub-actions, at most one may be chosen as part of realizing the action definition.