A definition of behaviors to be taken in particular circumstances, often including conditions, options and other decision points.

A unique identifier for the protocol instance.

Name of protocol.

The status of the protocol.

Allow for filtering of Protocols that are appropriate for use in production.

A code that classifies the general type of context to which these behavior definitions apply. This is used for searching, sorting and display purposes.

What does protocol deal with?

To whom does Protocol apply?

When is protocol to be used?

Who wrote protocol?

What's done as part of protocol.

Label for step.

Human description of activity.

How long does step last?

Rules prior to execution.

Human-readable description of the condition.

Defines the name/value pair that must hold for the condition to be met.

The type of observation, test or other assertion being evaluated by the condition.

Indicates what value the observation/test/assertion must have in order for the condition to be considered to be satisfied.

If the value is an interval, the condition matches if the value falls within the interval. The binding of .condition.valueCodeableConcept is unbound and is a coded value of an observation used as basis for conditional execution of one or more activities.

Lists a set of conditions that must all be met.

Lists alternative conditions, at least one of must be met.

Lists conditions of which none must be met.

Indicates the conditions that must be met for activities that are part of this time point to terminate.

If not specified, activities end based on occurrence and duration information specified in the activity. Conditions specified here may be used to allow exception handling as well as to ensure certain conditions are met while activities are proceeding.

First activity within timepoint.

Multiple activities are assumed to start in parallel.

Activities that occur within timepoint.

We send them as a collection because a single activity may be referenced multiple times; e.g. Activity C may be a follow-on activity to both A and B which happen in parallel.

What can be done instead?

Activities that are part of this activity.

Order of occurrence.

Equivalent values happen in parallel.

Component activity.

What happens next.

Multiple activities are assumed to start in parallel.

Indicates the length of time to wait between the conditions being satisfied for the activity to start and the actual start of the activity.

Information about the nature of the activity, including type, timing and other qualifiers.

High-level categorization of the type of activity.

May determine what types of extensions are permitted.

Detailed description of the type of activity; e.g. What lab test, what procedure, what kind of encounter.

Allows matching performed to planned as well as validation against protocols.

Tends to be less relevant for activities involving particular products.

The period, timing or frequency upon which the described activity is to occur.

Allows prompting for activities and detection of missed planned activities.

Identifies the facility where the activity will occur; e.g. home, hospital, specific clinic, etc.

Helps in planning of activity.

May reference a specific clinical location or may just identify a type of location.

Identifies who's expected to be involved in the activity.

Helps in planning of activity.

Identifies the food, drug or other product being consumed or supplied in the activity.

Identifies the quantity expected to be consumed at once (per dose, per meal, etc.).

This provides a textual description of constraints on the activity occurrence, including relation to other activities. It may also include objectives, pre-conditions and end-conditions. Finally, it may convey specifics about the activity such as body site, method, route, etc.

What happens next?

Description of what happens next.

Id of following step.

Condition in which next step is executed.