This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols.

An absolute URL that is used to identify this asset when it is referenced. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this asset is (or will be) published.

Allows the asset to be referenced by a single globally unique identifier.

A logical identifier for the asset such as the CMS or NQF identifiers for a measure artifact. Note that at least one identifier is required for non-experimental active artifacts.

Allows external business identifiers to be easily associated with the asset.

The version of the asset, if any. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts.

Allows for versioning of the content of the asset.

A machine-friendly name for the asset. This name should be usable as an identifier for the asset by machine processing applications such as code generation.

Simplifies machine-processing tasks related to the asset such as code-generation or logging.

This identifier for the asset should be unique within the intended scope of use, and should conform to the traditional syntactic definition of an identifier within most programming languages. regex: ([A-Za-z][A-Za-z0-9]*).

A short, descriptive, user-friendly title for the asset.

The type of asset the plan definition represents, e.g. an order set, protocol, or event-condition-action rule.

The status of the asset.

Enables tracking the life-cycle of the content of the asset.

Determines whether the asset was developed for testing purposes (or education/evaluation/marketing), and is not intended to be used in production environments.

Enables experimental content to be developed following the same life-cycle as a production-level asset would.

A free text natural language description of the asset from the consumer's perspective.

This description can be used to capture details such as why the asset was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the asset as conveyed in the text field of the resource itself. This item SHOULD be populated unless the information is available from context.

A brief description of the purpose of the asset.

This description should address the question of why this asset was built, though not necessarily in as much detail as the justification, rationale, or clinical recommendation statement of a measure would. That information would typically be provided in the related resource element.

A detailed description of how the asset is used from a clinical perspective.

The date on which the asset was published.

The date on which the asset content was last reviewed.

The period during which the asset content is effective.

The effective period for an asset determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 would be published in 2015.

Specifies various attributes of the patient population for whom and/or environment of care in which, the asset is applicable.

Consumers of the asset must be able to determine the intended applicability for the asset. Ideally, this information would be used programmatically to determine when and how it should be incorporated or exposed.

Clinical topics related to the content of the asset.

Repositories must be able to determine how to categorize the asset so that it can be found by topical searches.

A contributor to the content of the asset, including authors, editors, reviewers, and endorsers.

Consumers of the content must be able to quickly determine who contributed to the content of the asset.

The name of the individual or organization that published the asset (also known as the steward for the asset). This information is required for non-experimental active artifacts.

Consumers of the asset must be able to determine where to obtain support in the use of this asset, as well as where to direct questions and concerns about the content.

The publisher (or steward) of the asset is the organization or individual primarily responsible for the maintenance and upkeep of the asset. This is not necessarily the same organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the asset.

Contact details to assist a user in finding and communicating with the publisher.

A copyright statement relating to the asset and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the asset.

Consumers of the asset must be able to determine any legal restrictions on the use of the asset and/or its content.

Related resources such as additional documentation, justification, or bibliographic references.

Assets must be able to provide enough information for consumers of the content (and/or interventions or results produced by the content) to be able to determine and understand the justification for and evidence in support of the content.

Each related resource is either an attachment, or a reference to another resource, but not both.

A reference to a Library resource containing any formal logic used by the plan definition.

An action to be taken as part of the plan.

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.

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 description of when the action should be triggered.

An expression specifying whether or not the action is applicable in a given context.

A brief, natural language description of the condition that effectively communicates the intended semantics.

The media type of the language for the expression.

An expression that returns true or false, indicating whether or not the condition is satisfied.

The expression may be inlined, or may be a reference to a named expression within a logic library referenced by the library element.

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

When an action depends on multiple actions, the meaning is that all actions are dependencies, rather than that any of the actions are a dependency.

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.

An optional value describing when the action should be performed.

The type of participant in the action.

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

Defines the grouping behavior for the action and its children.

Defines the selection behavior for the action and its children.

Defines the requiredness behavior for the action.

Defines whether the action should usually be preselected.

Defines whether the action can be selected multiple times.

A reference to an ActivityDefinition that describes the action to be taken in detail.

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

A reference to a StructureMap resource that defines a transform that can be executed to produce the intent resource using the ActivityDefinition instance as the input.

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.

A brief, natural language description of the intended semantics of the dynamic value.

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.

The media type of the language for the expression.

An expression specifying the value of the customized element.

The expression may be inlined, or may be a reference to a named expression within a logic library referenced by the library 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.