Implementation Overview in FHIR

Paradigms In order to make FHIR interoperable, it was based on 4 paradigms: RESTful API Documents Messages Services This is what's called an exchange framework. REST FHIR was primary designed to be used with Restful services which handle all requests. Restful service implies that we have a choice between using JSON or XML and it...

Understanding Interoperability in FHIR

What is this interoperability all about? Well, the time when the records are held in one place is quickly becoming the past. HL7 and other standards mostly addressed the issue of turning paper health records into digital. This requirement is still present, but nowadays there is a growing need to share those resources with other...

What is FHIR?

FHIR (pronounced 'fire') builds on the HL7 v.3. It's been introduced at the end of 2011 and has been implemented to improve interoperability (exchange of data) between health units. The need to exchange healthcare information electronically has been around for over decades - HL7 v. 2 is 25 years old! Currently FHIR is only a...

Adding Controllers to Spark

Recently, I've been working with Furore Spark. In order to enable /fihr endpoint they had to modify the route settings.

Clearly, {controller} is not used. So in order to add new we pages I would have to add another route setting: