Supporting the SNOMED SNAPP hackathon

So there’s a ‘hackathon’ (I actually don’t like that word) associated with the SNOMED conference in Auckland next month. They’re calling it a ‘SNAPP’ event (SNOMED App) – which is much nicer!

As part of supporting this event, HL7 New Zealand is going to stand up a server that can be used for the ‘My List of Medicines’ challenge. (The other challenge – Machine Mapping – is a bit esoteric for me).

So there are a couple of things we need to do.

  • Stand up a FHIR server for participants to use that can respond to appropriate requests (we’ll talk about what they will be in the next post).
  • Populate that server with the sample data given on the web site

Read more of this post

Baltimore Working Group Meeting

Well, the Baltimore Working Group Meeting is finished – and what a time it was!

For me the WGM was all about Connectathons – one way or another.

Read more of this post

FHIR and Version 2: the Location

So last week  Simone Heckman  (CTO of Gefyra GmbH) wrote a piece in the FHIR chat in response to a query about mapping data from an HL7 v2 message into FHIR – specifically about representing the location of a patient as shown in the PV1 segment of the message into FHIR resources. It was a great response so I asked her if I could repeat it here and she was kind enough to not only say yes, but also beef it up a bit!

Over to you Simone…

Read more of this post

Terminology services

Just a short post to call peoples attention to terminology services in FHIR. Rob Hausam (who co-ordinates the Terminology track at the connectathon) made the excellent comment in the Zulip chat that terminology is a ‘cross-cutting’ concern that can be integrated into many different applications – and tracks at connectathon.

Read more of this post

Projects in clinFHIR

One of the things that the Resource Builder in clinFHIR does is to allow you to use different servers for the various ‘roles‘ that are needed. These include:

  • The Conformance server – holds resources like StructureDefinition and NamingSystem
  • The Terminology server – ValueSets and the Terminology operations required by the different applications within clinFHIR
  • The Data server – where patient (and other) data is kept.

This isn’t an official part of the spec, but is a useful way to think about the main ‘components’ of a FHIR solution.


While flexible, this can make it somewhat more complicated to use, as you need to select the right combination of servers to suit a particular need.

Read more of this post

What is SMART and why should you care.

This was actually a summary of SMART that was intended to wrap up a series I wrote a few months back, but I forgot to post it! So, better late than never…

Read more of this post

Dev days in November

In the past I’ve talked about the FHIR Developer days hosted by our friends Furore in November in Amsterdam – generally with a slightly envious tone. This year – thanks to my employer Orion Health – I’m able to attend! (I’m going to get into the group picture at last :) )

Since I’m going to be there and I have a clinical background, the Furore folk suggested that I might want to lead a track specifically for Clinicians and Business Analysts who want to learn more about FHIR – so this post is all about putting some ideas out to get feedback.

Read more of this post