Chief Technology Officer at Corepoint Health, member of the HL7 Board of Directors, and co-chair of the HL7 FHIR Governance Committee

Dave Shaver

In a July, 2017 webinar titled, The Future of Interoperability: APIs + Traditional Interfaces, Corepoint Health CTO Dave Shaver discussed how future integration API touch-points will allow a more open ecosystem of applications, and support patient demands for access to their health data while empowering providers though data exchange. Below are a few questions and answers from that webinar.

What if my current integration engine doesn’t support FHIR?

With a variety of methods to add FHIR support, this video explores the different solutions. From adding a new platform to waiting for official support, Dave discusses when each approach would make sense. If the decision is made to change engine vendors, participation in the FHIR standard should be noted, along with the ability to build interfaces faster with less code.

Which vendors are accepting FHIR requests?

Since development first began on FHIR, vendors have played a crucial role in shaping the new standard. Vendor collaboration through Project Argonaut has allowed for an accelerated implementation process with the potential to greatly expand database access. In the video below, Dave outlines the current use of FHIR and how vendors plan to support the standard.

When will EHRs have FHIR APIs available?

While many EHR vendors claim to currently support FHIR, most organizations face significant hurdles before machine-room use becomes a reality. In this video, Dave shares the role modules will play in FHIR adoption and reveals how APIs will change workflows. For the FHIR timeline, Meaningful Use Stage 3 also plays a critical role in API development.

Tags: , ,
 Print Friendly