-
Join 1,197 other subscribers
Subscribe
-
Past Posts
- openEHR turns 20 today
- 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)
Categories
- Computing (44)
- Culture (3)
- decision support (3)
- FHIR (19)
- Health Informatics (93)
- openehr (67)
- Philosophy (7)
- Politics (2)
- standards (49)
- Uncategorized (2)
- workflow (1)
Recent Comments
- MD on A Lingua Franca for e-health takes shape with GraphiteHealth
- Oliver Ford on Why NPfIT failed
- Pablo Pazos on openEHR turns 20 today
- Natalia Iglesias on openEHR turns 20 today
- dr. William Goossen on openEHR turns 20 today
General ICT
Health IT
Technology
Author Archives: wolandscat
openEHR turns 20 today
openEHR was officially created on 13 March 2003, 20 years ago today. Prof David Ingram thought of the name, and he and a small band of optimists – Dr Sam Heard, Dr Dipak Kalra, David Lloyd and myself – launched … Continue reading
Posted in Computing, Health Informatics, openehr, standards
Tagged archetype, e-health, Health Informatics, openEHR, standards
3 Comments
Why using expressions in workflow is wrong
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 BPMN, DMN, Health Informatics, openEHR, standards, workflow
3 Comments
A Lingua Franca for e-health takes shape with GraphiteHealth
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 archetype, CEM, graphite, openEHR
5 Comments
The Health IT Platform – a definition
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
What is interoperability?
There are some rather obscure definitions of health IT’s favourite term interoperability floating around, for example:
Directions in clinical guideline programming – CHA2DS2-VASc
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 cds, CIGs, CPGs, guidelines
2 Comments
Design-by-Contract (DbC) v Test-Driven Design (TDD)
Another bit of software engineering knowledge from my archive relates to two well-known formal quality methods used in software development. This is from a presentation made at ETH Zurich in 2010.
Posted in Computing
8 Comments
Software – from Development to Use and Ownership
Here’s an infographic (alright, it’s just a diagram) I created over a decade ago, randomly extracted from the archives. I think it’s almost self-explanatory. Here’s a few more slides using this. I wouldn’t adjust too much today, but note that … Continue reading
Nominalism versus Ontology
Most nominalist arguments are straightforwardly wrong, but not for the usual reasons that universals and/or abstracta are said by realists to exist, but for the opposite reason: types and abstracta are ‘just there’, even if they don’t ‘exist’, in the sense of being spatio-temporally concretised. The real problem is that we misuse the word ‘exists’ at least half the time in philosophy. Continue reading
Aide Memoire for Computable Domain Models
Sometimes a graphic is worth more than words. This is an attempt to capture all the salient features of multi-level modelling, the openEHR way. See the openEHR primer for the story. Although this is ‘our way’ of doing it, I … Continue reading