Clinicians on FHIR

Last week we held our first New Zealand ‘Clinicians on FHIR‘ seminar at the HINZ conference in Rotorua. This was really important for me, as it was the first ‘public outing’ of a seminar format that I’d like to see could be repeated wherever Clinicians are getting their first taste of FHIR, and showing how they can participate more fully in FHIR based Interoperability projects.

We had around 30 attendees and excellent participation – especially as the event was a combination of presentations and practical exercises. Thanks to John Fountain for presenting the clinical perspective. Talking to participants after the event was also very positive, with some good suggestions for improvement of the seminar.

Read more of this post

Using a FHIR Observation

These are some notes written by Lloyd, Grahame & Eric about using Observation in practice. I’ve copied this directly, here so I always know where to find it. You should refer to the source for the most recent version.

Read more of this post

FHIR Versions and Conformance URLs

As you probably know, there are a number of ‘conformance’ resources in FHIR that have a unique ‘canonical’ Url that identifies them globally. Other resources that need to refer to them can do so by addressing them by that URL – for example when a profile (Core or Derived) binds a coded element to a ValueSet, it does so via that URL – as does a Profile referencing an Extension Definition (both Profile and Extension Definition are StructureDefinition resources).

Looking at the definition of the Url in the spec:

For StructureDefinition:

An absolute URI that is used to identify this structure definition when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this structure definition is (or will be) published. The URL SHOULD include the major version of the structure definition.

For ValueSet

An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance. This SHALL be a URL, SHOULD be globally unique, and SHOULD be an address at which this value set is (or will be) published. The URL SHOULD include the major version of the value set.

So how do you accomplish this across different versions of FHIR?

Read more of this post

FHIR Core Extensions

A really short post to record how to download the core extensions in the spec (This came up in a FHIR Chat today). They can be found at:

This is particularly useful if you are setting up your own FHIR server and want to pre-load them with the code definitions in the spec. Just download from the link above, remove the id from the bundle, change the bundle type to ‘batch’ and POST to the root of the server.

Thanks Lloyd!

 

Creating Clinical and Analysis models

As you may know, one of the things that excites me about FHIR is the potential that it has to involve the clinician in the design of health IT systems (and I’m using ‘clinician’ in the widest sense – doctor, nurse allied health etc – anyone who delivers care to a patient).

So far a lot of my thoughts have been theory rather than practice, so it is great to try these ideas out on a real project – the reporting of Adverse Drug Reactions (ADR) by a clinician to a central service – such as a National EHR!

Read more of this post

Using the clinFHIR query tool

I’ve been in China recently (attending the CHIMA conference and presenting on FHIR in a number of events), and while there I had a bit of spare time, so decided to give the clinFHIR query tool a bit of attention (I also needed it for the workshop I gave).

The query tool has been there for quite a while, but it’s been rather basic and a bit klunky, so a facelift was overdue! Read more of this post

GraphQL

Following my post yesterday, someone who shall remain nameless (you know who you are Brian) suggested that it would also be good to be able to make GraphQL queries from clinFHIR. I know even less about GraphQL than I did about FHIRPath, but as Grahame has an implementation on his server, it was a reasonably straightforward matter to put a simple UI in so you can experiment with that against a Patient resource. (GraphQL can do a lot more than that, but this is a start).

Read more of this post