article thumbnail

Finding the future of interoperability with Redox: Part 2 – HL7 v2 to FHIR (and back again)

Redox

In the first post, I covered how Redox is overcoming current limitations with bulk FHIR. This time, I’ll be discussing our capabilities to translate between HL7 ® v2 and HL7 ® FHIR ® —a reoccurring challenge for many of our customers. However, modern technology shops want everything in FHIR. Let’s dive in. What does HL7 v2 do?

FHIR 59
article thumbnail

Hard #FHIR Safety Problem: Synchronization

Health Intersections

It’s a common thing for implementers to want to do with FHIR: connect to a FHIR server, and make a local copy of the information provided by the server, and then check back occasionally with the server for updates – that is, new resources, or changes to existing resources. (In “I never took X”).

FHIR 92
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

#FHIR and the Gartner Hype Cycle

Health Intersections

On a forum for FHIR Foundation members, I raised the subject of where FHIR is on the Gartner Hype Cycle (see Gartner write up , or Wikipedia ). FHIR Foundation member Wes Rishel ( @wrishel ), who’s a FHIR user, and also was a Gartner Analyst before he retired, graciously made this contribution that I could post here.

FHIR 69
article thumbnail

The Tension in TEFCA

Healthcare IT Today

The Sequoia Project, a spinoff of a prior EHR network, was chosen as the governing body for TEFCA. Today TEFCA only supports document exchange and frankly largely within legacy EHR vendors who have familiarity with the IHE protocols. Of course, the big question is, what is the public benefit?

FHIR 93
article thumbnail

Trans Tasman Connectathon

HAY on FHIR

The track itself defines a number of actors: The creator of an IPS document – for example an EHR (Electronic Health Record). This could be another EHR, or a mobile application. I’m going to be doing a number of things over the course of the event (a couple of days) – and the days leading up to it.

FHIR 58
article thumbnail

#FHIR and Cancer Patient Empowerment – Mike’s story

Health Intersections

I’m very honoured to make a guest today from Mike Morris, who I met at the HL7 FHIR Applications Round Table in Washington DC a couple of weeks ago. Mike is a cancer patient who is using FHIR improve his own treatment. APIs were not an important feature in terms of creating interoperability across siloed EHRs.

FHIR 54
article thumbnail

OntarioMD is Making Interoperability a Priority for Ontario

Healthcare IT Today

Of course that finish line has moved substantially forward. The adoption of FHIR-based standards in Ontario is a notable development. We have achieved all of our wildest dreams from 15 to 20 years ago when we first set down the path of interoperability. We have a long way to go.”