This resource allows for the definition of some activity to be performed, independent of a particular patient, practitioner, or other performance context.

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. Note that at least one identifier is required for non-experimental active assets.

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 assets.

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 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 knowledge 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 knowledge 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 module is the organization or individual primarily responsible for the maintenance and upkeep of the module. 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 module.

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 asset.

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.

The type of participant in the action.

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.).

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.

Dynamic values that will be evaluated to produce values for elements of the resulting resource. For example, if the dosage of a medication must be computed based on the patient's weight, a dynamic value would be used to specify an expression that calculated the weight, and the path on the intent 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.