Category Archives: standards

Why using expressions in workflow is wrong

Posted on 07/11/2022 by wolandscat

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 … Continue reading →

Posted in openehr, standards, workflow | Tagged , , , , , | 3 Comments

A Lingua Franca for e-health takes shape with GraphiteHealth

Posted on 15/05/2022 by wolandscat

Colleagues in e-health often say to me: why don’t you make openEHR easier to map to <insert popular interop standard> (used to be HL7v3, then HL7 CDA, now, HL7 FHIR… DSTU2/3/4/5?). To which I usually reply: if you are implying … Continue reading →

Posted in FHIR, Health Informatics, openehr, standards | Tagged , , , | 4 Comments

The Health IT Platform – a definition

Posted on 14/05/2021 by wolandscat

Following on from various posts in the past, including my 2014 post What is an open platform?, I thought it might be time to post a succinct (as possible) definition of the platform idea, for e-health. As stated in that … Continue reading →

Posted in Health Informatics, standards | Tagged , , | 1 Comment

What is interoperability?

Posted on 17/04/2021 by wolandscat

There are some rather obscure definitions of health IT’s favourite term interoperability floating around, for example:

Posted in Computing, Health Informatics, openehr, standards | Tagged | 6 Comments

Directions in clinical guideline programming – CHA2DS2-VASc

Posted on 29/03/2021 by wolandscat

The above shows a typical web form calculator for the CHA2DS2-VASc score, used for estimating the risk of stroke in patients with non-rheumatic atrial fibrillation (AF), primarily for the purpose of deciding the use of anti-coagulant therapy [Wikipedia]. How would such … Continue reading →

Posted in Computing, decision support, Health Informatics, openehr, standards | Tagged , , , | 2 Comments

Clinical Decision Logic Fun

Posted on 22/10/2020 by wolandscat

How close can we get to making a clinical decision logic language look like the published guidelines which it is used to encode? Below is an openEHR Decision Logic Module (DLM) example, in the current form of the openEHR Decision … Continue reading →

Posted in Computing, decision support, Health Informatics, openehr, standards | Tagged , , , | Leave a comment

Towards a standard analysis of computable guidelines, clinical workflow, decision support and … the curly braces problem

Posted on 24/06/2020 by wolandscat

Why don’t we have widespread clinical decision support (CDS), computable guidelines, clinical workflow (plans), and why don’t the pieces we do have talk to the health record? The first time I heard such challenges framed was around 2000, and even … Continue reading →

Posted in decision support, Health Informatics, openehr, standards | Tagged , , , , , , | 10 Comments

FHIR fixes: why a type hierarchy would help

Posted on 14/11/2019 by wolandscat

One of the principal reasons for why I and others are proposing (some) type hierarchy in the FHIR Admin resources is as follows (my earlier post on this). Working Groups (i.e. committees) building Resources are currently in the situation of … Continue reading →

Posted in FHIR, Health Informatics, standards | Tagged , , | 1 Comment

FHIR Fixes – the Observation.value problem

Posted on 12/09/2019 by wolandscat

As described in some detail in this earlier post on the FHIR formalism, a number of FHIR Resources contain ‘choice’ attributes of the form attribute[x], such as the one shown above in Observation. These are mapped in the FHIR UML … Continue reading →

Posted in FHIR, Health Informatics, openehr, standards | Tagged , | Leave a comment

Fixes for FHIR – the Admin Resources

Posted on 11/09/2019 by wolandscat

In this post I revisit the issues with the FHIR Resources described in the earlier post – A FHIR experience: models or just definitions? To summarise: FHIR has no semantic inheritance, only a generic structural inheritance of Resources from abstract … Continue reading →

Posted in FHIR, Health Informatics, standards | 5 Comments