openEHR logo

Task Planning Visual Modelling Language (TP-VML)

Issuer: openEHR Specification Program

Release: Release-1.0.0

Status: TRIAL

Revision: [latest_issue]

Date: [latest_issue_date]

Keywords: task, planning, visual language

openEHR components
© 2017 - 2018 The openEHR Foundation

The openEHR Foundation is an independent, non-profit community organisation, facilitating the sharing of health records by consumers and clinicians via open-source, standards-based implementations.


image Creative Commons Attribution-NoDerivs 3.0 Unported.


Issues: Problem Reports

Amendment Record

Issue Details Raiser Completed

R E L E A S E     1.0.0


SPECPROC-2 Initial Writing.

T Beale

20 Oct 2017


Primary Author

  • Thomas Beale, Ars Semantica (UK); openEHR Foundation Management Board.


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


The work reported in this specification has been funded by the following organisations:

  • City of Moscow, Russia

  • DIPS, Norway

  • Marand d.o.o., Slovenia

  • Ars Semantica, UK


  • 'openEHR' is a trademark of the openEHR Foundation.

  • 'OMG' is a trademark of the Object Management Group.

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.

Prerequisite documents for reading this document include:

1.3. Status

This specification is in the TRIAL state. The development version of this document can be found at

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 technical mailing list.

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

2.1. Palette

TP VML palette
Figure 1. Plans

2.2. Tool mode

The following files can be downloaded and then imported into as libraries to provide a working palette for TP-VML diagrams.

3. Elements

3.1. Composites

3.1.1. Plans

TP VML plans
Figure 2. Plans

3.1.2. Task Groups

3.1.3. Conditional Structures

TP VML conditionals
Figure 3. Conditional structures

3.2. Primitives

3.2.1. Events

TP VML events
Figure 4. Events

3.2.2. Tasks

TP VML tasks
Figure 5. Tasks

4. Patterns