One of the basic elements of design common to all workflow languages, including YAWL and BPMN, is the inclusion of logical expressions on decision nodes. This seems harmless, and we followed it in openEHR’s Task Planning specifications. However, it is clear that this is a basic error, and that any workflow containing such expressions is unmaintainable and semantically unreliable.
Continue reading-
Join 1,155 other subscribers
Subscribe
-
Past Posts
- Why using expressions in workflow is wrong
- 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
Categories
- Computing (43)
- Culture (3)
- decision support (3)
- FHIR (19)
- Health Informatics (92)
- openehr (66)
- Philosophy (7)
- Politics (2)
- standards (48)
- Uncategorized (2)
- workflow (1)
Recent Comments
- David Kerr on Design-by-Contract (DbC) v Test-Driven Design (TDD)
- Athanasios Anastasiou on Why using expressions in workflow is wrong
- wolandscat on Why using expressions in workflow is wrong
- Athanasios Anastasiou on Why using expressions in workflow is wrong
- wolandscat on Towards a standard analysis of computable guidelines, clinical workflow, decision support and … the curly braces problem
General ICT
Health IT
Technology