Task Planning Visual Modelling Language (TP-VML)
| Issuer: openEHR Specification Program | |
|---|---|
Release: PROC latest |
Status: TRIAL |
Revision: [latest_issue] |
Date: [latest_issue_date] |
Keywords: task planning, visual language, workflow, care pathway, guideline, order set |
|
| © 2017 - 2022 The openEHR Foundation | |
|---|---|
The openEHR Foundation is an independent, non-profit foundation, facilitating the sharing of health records by consumers and clinicians via open specifications, clinical models and open platform implementations. |
|
Licence |
|
Support |
Issues: Problem Reports |
Amendment Record
| Issue | Details | Raiser | Completed |
|---|---|---|---|
PROC Release 1.6.0 |
|||
Add Task Repeat. |
T Beale |
||
0.6.2 |
Add parallel synchronisation example. |
N Iglesias, |
30 Oct 2020 |
0.6.1 |
Add concurrent end blocks and T/F Gates. |
T Beale |
03 Jun 2020 |
PROC Release 1.0.0 |
|||
0.6.0 |
Update to modelling shapes used in main specification. |
T Beale |
07 Mar 2019 |
0.5.0 |
SPECPROC-2 Initial Writing. |
T Beale |
20 Oct 2017 |
Acknowledgements
Contributors
This specification benefited from formal and informal input from the openEHR and wider health informatics community. The openEHR Foundation would like to recognise the following people for their contributions.
-
Borut Fabjan, Program Manager, Marand, Slovenia
-
Matija Kejžar, Marand, Slovenia
-
Eugeny Leonov, Solit Clouds, Moscow, Russia
-
Bjørn Næss, DIPS, Norway
1. Preface
1.1. Purpose
This document describes a visual modelling language for the openEHR Task Planning Model, known as TP-VML. This is designed to enable visually efficient visual representations of Task Plans to be authored with appropriately configured tools.
The intended audience includes:
-
Task Plan and workflow authors;
-
Tool vendors.
1.3. Status
This specification is in the TRIAL state. The development version of this document can be found at https://specifications.openehr.org/releases/PROC/latest/tp_vml.html.
Known omissions or questions are indicated in the text with a 'to be determined' paragraph, as follows:
TBD: (example To Be Determined paragraph)
1.4. Feedback
Feedback may be provided on the process specifications forum.
Issues may be raised on the specifications Problem Report tracker.
To see changes made due to previously reported issues, see the PROC component Change Request tracker.
1.5. Conformance
Conformance of a data or software artifact to an openEHR Reference Model specification is determined by a formal test of that artifact against the relevant openEHR Implementation Technology Specification(s) (ITSs), such as an IDL interface or an XML-schema. Since ITSs are formal, automated derivations from the Reference Model, ITS conformance indicates RM conformance.
2. Overview
3. Elements
The elements of TP-VML are based directly on the openEHR Task Planning formal specification, and can be used to construct exectuable Plans.
3.1. Composites
The TP-VML elements in this section are composite structures that contain primitive elements.
3.1.1. Plans
TP-VML icons for WORK_PLAN and TASK_PLAN are used (TP plan structure), enabling some of the relevant meta-data to be visualised.
3.1.2. Task Groups
Task Group icons and their conditional structure derivatives use two visual elements to indicate the extent of the (container structure) they represent from the TP model.
Since Tasks and other Task Groups within any Task Group are included by ordered containment (i.e. 'list' semantics) rather than chaining, contained items are shown connected with dashed arrows, indicating the implied ordered.
3.1.3. Conditional Structures
TP conditional structures follow the same structural logic as Task Groups, with the addition of various specific meta-data as per the specificaion.
3.2. Primitives
The TP-VML elements in this section are atomic primitives that are used within various levels of containment structure, including Task Groups, the various kinds of conditional structure, Task Plans and Work Plans.
3.2.1. Tasks
TP-VML Tasks correspond to formal types of the form TASK<T> (TP main model; TP Task Action types), whose concrete forms are: PERFORMABLE_TASK<DEFINED_ACTION>, PERFORMABLE_TASK<SUB_PLAN>, DISPATCHABLE_TASK<HAND_OFF>, DISPATCHABLE_TASK<SYSTEM_REQUEST>, DISPATCHABLE_TASK<EXTERNAL_REQUEST>.
Performable Tasks may have one or more associated capture_datasets. Dispatchable Tasks may have an associated callback wait state (CALLBACK_WAIT).
3.2.2. Task Repeats
A Task, or more usually a Task Group may have a repeat specification (TASK_REPEAT) associted with it (TP Repetitions). Various forms are possible. This is diagrammed as follows.
3.2.3. Events
TP-VML Events are defined in the Events section in the TP specification and can be visually represented in three forms:
-
full form: with icon and named attributes from the TP model;
-
short form: with icon and implicit attributes from the TP model;
-
informal: via an icon, with no further specification of details.
Events are specified as triggers for the wait states TASK_WAIT, TIMER_WAIT and CALLBACK_WAIT.
