And how can FHIR APIs help?

Interoperability – or rather a lack of interoperability – remains a dilemma for many healthcare organisations. This can be an issue as their mission is to enable quality patient care, by providing clinicians with timely access to data which helps to improve the decision-making process and empower fully-informed actions. 

But what is Interoperability?

 think there are (at least) 2 aspects to interoperability – the technical and the social.

  1. Technical interoperability, which has been described by HIMSS as the ability of different IT systems and software applications to communicate, exchange data, and use the information that has been exchanged.
  2. Social interoperability, which refers to the willingness of participants to share data they have collected – and to the formation of a cross sector community to facilitate that.

Technical interoperability should actually be quite straightforward to solve. While many of the legacy applications within healthcare organisations have their own unique way of representing information, emerging standards like FHIR and the use of terminology standards like SNOMED CT offer a way forward for data sharing that many vendors and organisations have enthusiastically taken up.

By making high quality coded data available through secure, real-time APIs as well as by documents and messaging paradigms, we are able to share information in a way that the recipient can understand what we are saying – so-called Semantic Interoperability. And we can protect access to those APIs using an API manager to ensure that only those who have a right to access the data can do so.

FHIR and associated standards can help to establish a digital health ecosystem of medical information – enabling patient data to be made available when and where it is needed.

Social interoperability is harder. A great deal of how we organise healthcare is predicated on the ‘ownership’ of information, and controlling it’s distribution. Changing this model has very wide impacts on the ‘business’ of healthcare, and this sort of change is never simple.

Encouragingly, in the past few years we’ve seen a global community of users from all parts of the healthcare sector coming together to help improve interoperability for healthcare organisations, great examples are the FHIR chat or FHIR Connectathons.

The Wild Health Summit next week in Melbourne will discuss the Holy Grail of healthcare interoperability – one patient, one virtual record; primary to tertiary interoperability and how healthcare organisations can drive their journey to achieve this. If you would like to hear more about interoperability, please come along to the event on Tuesday where I am on a panel for the agenda session – Bridging Interoperability Gaps – What’s next? The panel will be discussing what true, seamless interoperability: what does success look like?  

Wild Health Summit

Tuesday, 17 April 2018

Collins Square Events Centre, Melbourne, Australia

Or, if you would like to read my white paper, where we will take a closer look at how FHIR APIs and several derived standards could underpin a digital health ecosystem that could improve interoperability for healthcare organisations.