Logical Containment Structures
Work Plan
The top-level formal concept defined is the Work Plan, which
- consists of one or more Task Plans;
- is a definition of work to be performed by one or more workers in order to achieve a defined goal with respect to a subject of care.
- is assumed to be executable within a single computational context (e.g. a 'Task Planning engine'), in which methods of notification and worker communication are available, enabling the state of progress of the work defined in the Plan to be fully represented.
Task Plan
Within a Work Plan, each included Task Plan is:
- a definition of work to be performed in a single work context, by a 'principal performer' and possibly other participants.
Task Group
The principal type of container of Nodes in a Task Plan.
Nodes
Decision Nodes
Technically, these are currently special kinds of Task Group, but we will probably change that in v2. The general concept is a decision group consists of a root node followed by 2 or more branches. Each branch does work like a Task Group in that it contains elements.
...
This is a wait state, each branch is like a when/then rule. When one of the conditions becomes True, that branch is followed. The 'when' part is expressed as a 'Task Wait' entity (see below).
Task
A Task is a 'doing' object, i.e. represents an item of work. The
Kinds of Task
xxx
xxx
Task Wait
Object representing a point in time in terms of one or more events. The start_window is used to add an 'acceptable delay' time within which the Task should be start with respect to the intended start time. The timeout attribute can be used for non-deterministic Events.
clock time: event =
TIMELINE_MOMENT,CALENDAR_EVENT;notification-based: event =
CALLBACK_NOTIFICATIONorMANUAL_EVENT,NOTIFICATIONSYSTEM_NOTIFICATION;task-linked: event =
TASK_TRANSITION, e.g. 1hr after previous Task done;state-linked: event =
STATE_TRIGGER, e.g. 'when systolic BP > 165';any event with added delay:
DELAY_EVENT.
Events
The various kinds of Event in a Task Wait object can be specified in the following ways:
CALENDAR_EVENT: use a date or date/time, e.g. '2018-04-22', possibly with a calendar symbolTIMELINE_MOMENT: is an offset from the time origin of the Task Plan e.g +2d; this can be converted to calendar time once the plan has started, but probably should be displayed in both forms, e.g. '2018-04-22 (+2d)'TASK_TRANSITION: occurs when a Task has undergone a lifecycle state transition, e.g. 'Task 54 {Done, Cancelled}'STATE_TRIGGER: event representing an expression referring to one or more tracked variables, reaching a value or passing a threshold value (here 'state' refers to something in the outside world, usually a patient variable like BP, platelets etc).MANUAL_EVENT: Event type representing the manual notification of a real-world event to the system, such as arrival of a test result, manually taken vital sign value over a threshold etc;SYSTEM_NOTIFICATION: Event type representing a notification from a system of some event, represented by notification type and reference identifier.DELAY_EVENT: any other kind of event, with an added delay;CALLBACK_NOTIFICATION: a callback from elsewhere in the plan has occurred.