Opening up clinFHIR – An example generator

I’d always intended that clinFHIR would be an open source project.

It all started when we were planning the ‘Clinician Connectathons’ – now ‘Clinicians on FHIR’ a year or so back, and realized that we needed some sort of tooling to support the events – tooling that would allow a user to create resources – and view the references between those resources – in a way that made sense to a clinician rather than a techie, and didn’t require them to understand the ‘on the wire’ formats of a resource (unless they wanted to).

After a few false starts, the current version was developed that seems to meet the need of the events. In fact, there are a number of different tools under the clinFHIR umbrella:

Read more of this post

Where did that data come from?

This post grew out of a question from one of the Analysts at Orion Health. We’re in the process of embedding FHIR pretty deeply into our product stack – and part of that involves creating FHIR interfaces to our existing data repositories.

This particular repository takes data feeds from a number of sources – mostly in the form of v2 messages, but also including CCDA documents – and from them extracts clinical data of interest such as encounters, procedures, problems and so forth. Because of the varied source of the data, one of the data items in the existing output that is displayed to the user is where it come from – ie which facility and possibly which application. (As much as we’d like to get the clinician, this data is not generally available in v2 messages).

So they question they asked me was – ‘where does this stuff go in FHIR’?

Read more of this post

Access Control and FHIR

And more posts by other people (Oh, how I love avoiding work…  🙂 ).

This one by Nicola Ryzhikov discusses Access Control mechanisms in FHIR,  and prompted a follow up comment from my colleague at Orion Health – Ed Costello.

Test-Driven Development With FHIR

The following post is written by my colleague Peter Jordan – who was the HL7 New Zealand representative at the January Working Group Meeting in Orlando.

Read more of this post

FHIR Product Director

If you follow Grahames blog, then you’ll be aware that he has been appointed to the role of Product Director for FHIR (not really any other choice eh?)

Well, the web site for the role is now up – and you really should follow it.

’nuff said really.