Grahame Grieve
Podcast

Grahame Grieve - the future of healthcare interoperability (part 1)

April 15, 2016   FHIR HL7 integration Interoperability

The Healthcare Innovators Podcast is proud to connect you with Grahame Grieve, Product Director of FHIR for HL7. Grahame hails from Melbourne, Australia and has come to be industry known as the “Father of FHIR.” Before creating the Fast Healthcare Interoperability Resources, he spent years working with the HL7 standards that assist in transferring clinical and administrative data between software applications. Today, we’ll learn a bit more about the background of FHIR and why healthcare subdomains are attracted to the FHIR standard. This is first in a three-part interview series around the FHIR standard and one that will leave you laughing as Grieve shares his favorite answer to what FHIR stands for.

On which subdomain is expressing the most Interest: “The one that is getting the most focus and attraction right now is EHRs. We have projects in multiple countries, particularly in the USA, to provide open EHR access to data. That’s primarily the highest profile work that we have going, but everybody’s working relatively hard.”

On the origin of naming FHIR: “I’m very happy to say it wasn’t my idea. Once it became clear that we had a working standard, I just called resources for help because I’m a boring kind of techie geek. I just called it what it was. Then the marketing committee at HL7 looked at it and said, ‘if you want this to be a big deal, you’ve got to give it a funny name, so people can play with the name.’ They banged it around and came up with the FHIR name.”

On a favorite FHIR acronym twist: “I’ve heard them all, but there are always new ones, as well as puns on the FHIR as part of the name. There’s also a whole series of jokes around what the latest F-H-I-R actually stands for. My personal favorite is: ‘Fixing HL7’s International Reputation’.”

**On FHIR current pilots: ** “At the moment, we have prototypes and pilot projects in many countries in the world, in many domains. Some are high profile projects; some are under the radar projects. My focus is now on scaling up the community, because that’s where our focus needs to be, because we are getting more and more implementations. In the next five years, FHIR will transition from being the next greatest thing to what everybody does, and becoming boring, in fact.”

On the advantage of FHIR: “One of the architectural advantages of FHIR versus other healthcare data exchange processes is that we leverage the Web.”

**On high-profile hacks: ** “Given the number of high profile identity hacks we’ve had this year, and those are only the reported ones, I think that we should stop assuming that there is any security around people’s fundamental identification and the same should apply to their health. Instead of regarding that as necessary to secure, I think society will be forced to move to a world where everybody’s information is open, and the social consequences aren’t there.”

On open-sourcing FHIR:

  • “Health information should be free — free to move.” “ …giving your information away increases its value.”
  • “If you hold onto it and try to extract money out of its use, you’re actually decreasing the value.”
  • “I’ve become a strident believer in the value of open source for at least the area that we work in. There are a few other specifications providers who are moving away from any form of openness, getting more and more restrictive, insisting that we must pay them or they’ll aggressively prosecute. I look at that and say, “I don’t know why you would spend so much time decreasing your value.”

On how much interoperability you need: “I have a formula: How much interoperability do you need? The answer is n times two, where ‘n’ is the amount you have.”


After the interview, read more about the FHIR standard here, and don’t miss parts two and three of our interview series with Grahame.


Previous: Dr. Sanjeev Arora — Improving rural access to care: the role technology plays and the value of telehealth

Next: Grahame Grieve - the future of healthcare interoperability (part 2)