Recent discussions on the FHIR chat forum with various HL7 people around the topic of how openEHR and other architectural frameworks (e.g. VA FHIM, CDISC) could work with FHIR led to a realisation that some people in HL7 at least don’t understand some of the technical basics of openEHR. This might simply because they have not been involved enough to learn them, but now that we appear to be in the era of FHIR, in which no e-health solution can be without FHIR (according to the now pervasive FHIR hype), I would argue that HL7 now needs to understand some of the basics of the other major architectural frameworks and model-based platforms in e-health – all of which precede FHIR.
-
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