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.
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.
If the element is present, it must have either a @value, an @id, or extensions
An absolute URI that is used to identify this plan definition when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this plan definition is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the plan definition is stored on different servers.
A formal identifier that is used to identify this plan definition when it is represented in other formats, or referenced in a specification, model, design or an instance.
The identifier that is used to identify this version of the plan definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the plan definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. 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.
A natural language name identifying the plan definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.
A short, descriptive, user-friendly title for the plan definition.
An explanatory or alternate title for the plan definition giving additional information about its content.
A high-level category for the plan definition that distinguishes the kinds of systems that would be interested in the plan definition.
The status of this plan definition. Enables tracking the life-cycle of the content.
A Boolean value to indicate that this plan definition is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
A code or group definition that describes the intended subject of the plan definition.
The date (and optionally time) when the plan definition was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the plan definition changes.
The name of the organization or individual that published the plan definition.
Contact details to assist a user in finding and communicating with the publisher.
A free text natural language description of the plan definition from a consumer's perspective.
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate plan definition instances.
A legal or geographic region in which the plan definition is intended to be used.
Explanation of why this plan definition is needed and why it has been designed as it has.
A detailed description of how the plan definition is used from a clinical perspective.
A copyright statement relating to the plan definition and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the plan definition.
The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage.
The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date.
The period during which the plan definition content was or is planned to be in active use.
Descriptive topics related to the content of the plan definition. Topics provide a high-level categorization of the definition that can be useful for filtering and searching.
An individiual or organization primarily involved in the creation and maintenance of the content.
An individual or organization primarily responsible for internal coherence of the content.
An individual or organization primarily responsible for review of some aspect of the content.
An individual or organization responsible for officially endorsing the content for use in some setting.
Related artifacts such as additional documentation, justification, or bibliographic references.
A reference to a Library resource containing any formal logic used by the plan definition.
Goals that describe what the activities within the plan are intended to achieve. For example, weight loss, restoring an activity of daily living, obtaining herd immunity via immunization, meeting a process improvement objective, etc.
An action or group of actions to be taken as part of the plan.
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.
Indicates a category the goal falls within.
Human-readable and/or coded description of a specific desired objective of care, such as "control blood pressure" or "negotiate an obstacle course" or "dance with child at wedding".
Identifies the expected level of importance associated with reaching/sustaining the defined goal.
The event after which the goal should begin being pursued.
Identifies problems, conditions, issues, or concerns the goal is intended to address.
Didactic or other informational resources associated with the goal that provide further supporting information about the goal. Information resources can include inline text commentary and links to web resources.
Indicates what should be done and within what timeframe.
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.
The parameter whose value is to be tracked, e.g. body weight, blood pressure, or hemoglobin A1c level.
The target value of the measure to be achieved to signify fulfillment of the goal, e.g. 150 pounds or 7.0%. Either the high or low or both values of the range can be specified. When a low value is missing, it indicates that the goal is achieved at any value at or below the high value. Similarly, if the high value is missing, it indicates that the goal is achieved at any value at or above the low value.
Indicates the timeframe after the start of the goal in which the goal should be met.
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.
A user-visible prefix for the action.
The title of the action displayed to a user.
A brief 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 might not be capable of interpreting it dynamically.
Indicates how quickly the action should be addressed with respect to other actions.
A code that provides meaning for the action or action group. For example, a section may have a LOINC code for the section of a documentation template.
A description of why this action is necessary or appropriate.
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.
Identifies goals that this action supports. The reference must be to a goal element defined within this plan definition.
A code or group definition that describes the intended subject of the action and its children, if any.
A description of when the action should be triggered.
An expression that describes applicability criteria or start/stop conditions for the action.
Defines input data requirements for the action.
Defines the outputs of the action, if any.
A relationship to another action such as "before" or "30-60 minutes after start of".
An optional value describing when the action should be performed.
Indicates who should participate in performing the action described.
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 required 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, or a PlanDefinition that describes a series of actions to be taken.
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.
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.
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.
The kind of condition.
An expression that returns true or false, indicating whether the condition is satisfied.
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.
The element id 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.
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.
The type of participant in the action.
The role the participant should play in performing the described action.
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.
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 specified path SHALL be a FHIRPath resolveable on the specified target type of the ActivityDefinition, and SHALL consist only of identifiers, constant indexers, and a restricted subset of functions. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements (see the [Simple FHIRPath Profile](fhirpath.html#simple) for full details).
An expression specifying the value of the customized element.
Must
Could
Must Unless Documented
Defines expectations around whether an action or action group is required.
If the element is present, it must have either a @value, an @id, or extensions
Before Start
Before
Before End
Concurrent With Start
Concurrent
Concurrent With End
After Start
After
After End
Defines the types of relationships between actions.
If the element is present, it must have either a @value, an @id, or extensions
Visual Group
Logical Group
Sentence Group
Defines organization behavior of a group.
If the element is present, it must have either a @value, an @id, or extensions
Any
All
All Or None
Exactly One
At Most One
One Or More
Defines selection behavior of a group.
If the element is present, it must have either a @value, an @id, or extensions
Single
Multiple
Defines behavior for an action or a group for how many times that item may be repeated.
If the element is present, it must have either a @value, an @id, or extensions
Yes
No
Defines selection frequency behavior for an action or group.
If the element is present, it must have either a @value, an @id, or extensions
Applicability
Start
Stop
Defines the kinds of conditions that can appear on actions.
If the element is present, it must have either a @value, an @id, or extensions