Task orientated Services in FHIR

Last year New Zealand published a number of documents that were distilled from the Interoperability Reference Architecture we published the previous year. One of them was about the utility services that we envisaged would be needed to support the National strategy around health information interoperability, and the following diagram was included to show how we described a service based layer (we called it an HIE – which has a different meaning in the US) providing access to regional data repositories for shareable clinical data.

HIE

I’ve always believed that FHIR was an excellent candidate for this layer – and so I was especially pleased to see this  post from Keith Boone describing how FHIR could support Task orientated services as well as Entity services – just as we had envisaged (though I’d have different examples for the entity services these days)!

It will be interesting to see if the FHIR core team look at standardizing the common interfaces (like the admission services that Keith mentioned), or whether that will be left to individual implementers…

About David Hay
I'm an independent contractor working with organizations like Rhapsody, Corepoint, CSIRO in Australia and the New Zealand Ministry Of Health. I'm an HL7 Fellow, Chair Emeritus of HL7 New Zealand and a co-chair of the FHIR Management Group. I have a keen interest in health IT, especially health interoperability with HL7 and the new FHIR standard.

2 Responses to Task orientated Services in FHIR

  1. Pingback: Getting more that one type of Resource back in a #FHIR query | Hay on FHIR

  2. Pingback: Using the mailbox endpoint for Immunization Decision Support | Hay on FHIR

Leave a Reply

%d bloggers like this: