I (together with some other openEHR folk) believe the emerging HL7 FHIR standard can leverage from clinical modelling using Archetypes while we (and rest of the world!) could benefit from modern and lightweight REST based exchange mechanism. Here is a post from my fellow colleague, David Day, describing nicely what FHIR is all about on his increasingly popular blog: Hay on FHIR!
In my self-appointed role as ‘FHIR evangelist’ (some would say ‘FHIR Fanatic’) at Orion Health and HL7 New Zealand I’m often asked ‘what is FHIR, and why should I care’. Rather than trying to explain each time, I’m going to write a short post here, so I can refer people to it, rather than trying to remember all the good points at the time.
So, what is FHIR?
- FHIR (Fast Health Interoperability Resources) is the latest interoperability standard from HL7, following on from Version 3. (Strictly speaking it builds on rather than replacing v3, but also pulls in ideas from other organizations such as openEHR or IHE).
- FHIR has the fundamental concept of “Resources”, where a resource is the basic unit of interoperability – the smallest ‘thing’ that makes sense to talk about – such as a Patient, a Condition (Problem) or a Practitioner
View original post 432 more words