A FHIR learning application for non-technical folk

One of the things that is happening to FHIR is that as it grows in maturity, it is starting to attract more Clinicians and Business Analysts who are less interested in the technology, and more interested in how it can be used to represent the clinical information they want to share – both inside and between organizations.

Indeed, the chair of HL7 – Stan Huff – referred to this explicitly at the last Working Group Meeting when he referred to the importance of the clinical community getting together to develop the profiles of use that take the core FHIR specification, and make it work for the clinical community. There is a very real risk of developing multiple different profiles that actually mean the same thing and thus harming interoperability. FHIR offers mechanisms to avoid this, but it does mean that people – especially clinical and analysts –need to have a good idea of how FHIR in general – and these mechanisms in particular – work.

Read more of this post

FHIR Messages

Rene Spronk recorded this video on the v2/FHIR messaging at the recent FHIR connectathon.


Creating simple FHIR clients

From our colleagues at Furore – even Managers can create FHIR clients!

Responsibilities of a FHIR client

As we start to do more ‘real’ work implementing FHIR here at Orion Health, we wind up making a number of implementation decisions about the interfaces we develop, and these – of course – influence how clients will use the services we create. Naturally, we will use the Conformance resource to document these, but it got me thinking about the overall responsibilities of a FHIR client. Read more of this post