A task to be performed.

The business identifier for this task.

A name or code (or both) briefly describing what the task involves.

A description of this task.

The type of participant that can execute the task.

Use to distinguish tasks on different activity queues.

The priority of the task among other tasks of the same type.

Used to identify the service level expected while performing a task.

The current status of the task.

These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.

An explaination as to why this task failed.

The subject of the task.

Used to identify the thing to be done (not the beneficiary -- see for below).

The entity who benefits from the performance of the service specified in the task (e.g., the patient).

Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively).

A reference to a formal or informal definition of the task.

Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation) to be associated with a task, enabling automation.

The date and time this task was created.

Most often used along with lastUpdated to track duration of task to supporting monitoring and management.

This information duplicates what appear in Provenance but is often needs to be more accessible.

The date and time of last modification to this task.

Used along with history to track task activity and time in a particular task state. This enables monitoring and management.

This information duplicates what appear in Provenance but is often needs to be more accessible.

The creator of the task.

Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).

This information duplicates what appear in Provenance but is often needs to be more accessible.

The owner of this task. The participant who can execute this task.

Identifies who is expected to perform this task.

This information duplicates what appear in Provenance but is often needs to be more accessible.

Task that this particular task is part of.

Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task).

Inputs to the task.

Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.

The name of the input parameter.

Inputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the input parameter as a basic type.

Task inputs can take any form.

Outputs produced by the Task.

Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.

The name of the Output parameter.

Outputs are named to enable task automation to bind data and pass it from one task to the next.

The value of the Output parameter as a basic type.

Task outputs can take any form.