We have been making steady progress on the openEHR Task Planning specification and visual modelling language (TP-VML) for clinical workflow. One of the differentiators of Task Planning, is that, like YAWL, it is designed as a formalism for developing fully executable process plans. This means that all the semantics of a TP Plan are formally defined and executable in a TP engine. It also means that the accompanying visual language, TP-VML, consists of visual elements formally related to the TP model. This is in contrast with BPMN, which is defined as a diagramming language with some formal elements mixed in, and other formal requirements expressed separately in the specification. Nonetheless, we are carefully studying the semantics of OMG’s BPMN2 / CMMN / DMN specifications to make sure we cover the necessary requirements, and use the same conceptual terminology as far as possible.
Continue readingSubscribe
-
Past Posts
- A Lingua Franca for e-health takes shape with GraphiteHealth
- The Health IT Platform – a definition
- What is interoperability?
- Directions in clinical guideline programming – CHA2DS2-VASc
- Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Software – from Development to Use and Ownership
- Nominalism versus Ontology
Categories
- Computing (43)
- Culture (3)
- decision support (3)
- FHIR (19)
- Health Informatics (92)
- openehr (65)
- Philosophy (7)
- Politics (2)
- standards (47)
- Uncategorized (2)
Recent Comments
- wolandscat on A Lingua Franca for e-health takes shape with GraphiteHealth
- Santosh Shevade (@santoshshevade) on A Lingua Franca for e-health takes shape with GraphiteHealth
- wolandscat on A Lingua Franca for e-health takes shape with GraphiteHealth
- Mark Kramer on A Lingua Franca for e-health takes shape with GraphiteHealth
- Aurimas on Design-by-Contract (DbC) v Test-Driven Design (TDD)
General ICT
Health IT
Technology