clinFHIR and the CodeSystem resource (STU-3)

As you’ll probably be aware, a lot of my focus in recent months has been in updating clinFHIR to help non-technical folk like clinicians understand what FHIR is, and how they can get involved in FHIR related projects. Here’s a White Paper I did for Orion Health on the subject…

There are a couple of core components that have been developed to assist this.

Read more of this post

New UI for clinFHIR

If you’ve used clinFHIR in the last 24 hours then you’ll have noticed a new User Interface. This is a recognition that clinFHIR is now really a number of ‘co-operating’ modules rather than a single application, so the previous UI wasn’t really the best any more.

In this post I’ll describe the UI (Actually I call it a ‘Launcher’ as it’s really a start point for the various modules).

Read more of this post

FHIR QA

We’re looking for volunteers to help out with QA (Quality Assurance) for the STU3 FHIR specification.

Read more of this post

Move to New Zealand!

If you’re thinking of moving to New Zealand (and, of course, everyone wants to), then have I got a deal for you!

https://www.bayleys.co.nz/Listing/Auckland/Auckland/Mt-Eden/1630149

(Sorry, blatant misuse of a FHIR blog!)

 

Videos on clinFHIR Scenario Builder and Logical Modelers

So in a fit of enthusiasm I offered to do a short demo of clinFHIR at the CATonFHIR event in the UK in a couple of days. As it turns out, the reality of the timing is that this would be at 2am my time (New Zealand). Of course I’d be happy to do this to support FHIR (and have done it before), but when the organizer Philip Scott suggested I record a video that they could show instead of a live performance I jumped at the chance!

And having done one, a second wasn’t that hard…

Read more of this post

Extending a required ValueSet Binding

One of the issues we come across quite a lot at Orion Health is where we are creating a read FHIR interface to an existing data service with elements in the FHIR resource that are coded and have a ‘required’ binding to a ValueSet (which means that you must only use one of the values in the ValueSet) – and the data we are mapping from has a different value. AllergyIntolerance is a particular culprit in this regard as it has a number of required bindings, but it has come up most recently in MedicationStatement.status where we have values that are different to the ones in STU2 – the FHIR version we are using.

Read more of this post

Scenario Builder: Library and Documents

In the last post we talked about the new builder component that was developed to help people (especially clinicians) develop sets of resources to represent clinical scenarios. There are a couple of features we didn’t have time to discuss then – the Library and Documents – so let’s talk about them now.

Read more of this post