Why is Patient.birthDate only a date?

Ever wondered why you need an extension to include the time of birth for a patient? Brian Postlethwaite explains why

Setting up your own FHIR server

Note that the urls in this post are a bit outdated – here is more up to date info about the HAPI CLI

I’ve been having some conversations with a group that are wanting to use clinFHIR to view profiles – and create sample resources from them – but they are using Forge to create them (good choice!) and so the question becomes about how to put them where clinFHIR can access them.

Before we get into the detail, lets take a step back and look at what we need to achieve to support clinFHIR in this way.

Read more of this post

Renaming the FHIR Conformance resource


Just a short note to let people know of a significant change that has occurred in FHIR since the Baltimore Working Group meeting in September.

Perhaps surprisingly, there’s only one actual requirement of a RESTful FHIR server – that it hosts a resource that describes what its capabilities are. It returns this resource when you call the metadata endpoint of the server like this:


Read more of this post

New FHIR Blog

Welcoming Brian to the FHIR Blog-o-sphere:


Logical models in FHIR

So one of the capabilities that has been added to FHIR reasonably recently is the capability to use the conformance infrastructure (like StructureDefinitions, ValueSets etc) to produce logical models – rather than defining resource types and such like.

The purpose of the logical model is to gather requirements from clinicians and other folk that can subsequently feed into the design process for profiles and Implementation Guides. While it’s possible to create profiles directly during this process (and one of the goals of clinFHIR is to support this) – there’s no doubting that it does require some understanding of FHIR and the structure/purpose of the existing resource types, so the Logical Model ‘bridges the gap’ by documenting the requirements in a computable fashion without placing any constraints on the model structure.

Read more of this post

Supporting SNAPP: Accessing New Zealand Medicines Terminologies With FHIR Terminology Services

A guest post from Peter Jordan – author of the Patients First Terminology server that will be available for use at SNApp, and frequent HL7 FHIR Connectathon attender…

Take it away Peter…

As those developing healthcare applications for the local market are well aware, and overseas developers preparing for the ‘SNAPP’ event at the upcoming SNOMED conference in Wellington, are becoming aware, New Zealand has its own medicines terminology. Interacting with this terminology – broadly known at the NZ Universal List of Medicines (NZULM) – is one of the many challenges facing SNAPP participants.

Read more of this post

Contained resources – MedicationStatement

Continuing our ‘mini-series’ on the SNapp event, one thing you may come across when consuming MedicationStatement resources are ‘Contained’ resources. We’ve talked about them before, but in the interest of having all the SNapp information in the same place let’s take a look at what they are.

Read more of this post

SNapp server

Just a short note to say that I’ve set up a FHIR server for the SNapp event – based on the HAPI CLI server.

The IP address of the server root is:


Read more of this post