Pronounced as ‘Fire’ (hopefully bringing clarity to the pun in the title), it was initially developed by Graham Grieve, who insisted upon FHIR being open sourced.
In our Introduction to FHIR Academy article, Datica Co-founder Mohan Balachandran, guides us through why FHIR was necessary due to the current state of healthcare integration and interoperability and why FHIR brings a better, more modern approach with concepts such as Restful APIs and accompanying documentation to integration systems. In this introduction, you will learn what makes FHIR the superior in flexibility, the advantages FHIR has over the existing HL7 standards, and where FHIR is headed from here.
In the second entry to our FHIR series, The FHIR Resource Object: The Core Building Block, Mohan guides us through an understanding of the Resource object outlining its origins and intent, but also providing resources to further expand our HL7 comprehension. By listing various resource categories and their structures, including clinical, administrative, and infrastructure, Mohan is able to show how these models allow for the creation of nearly any clinical condition.
Still want to know more about FHIR? We sure hope so as Mohan’s third entry, Recommended FHIR API Implementation shows the general design principles that we have followed at Datica and what the key underlying principles are when building RESTful APIs.
As always, Datica is here to be your trusted resource and partner in all aspects of HL7. Stay tuned for more Academy entries as we stay up to date on the latest in digital health.