Lyniate Team

FHIR, IHE Profiles and Open EHR

August 30, 2017

Video Thumbnail
Access our latest FHIR Resources.

In a July, 2017 webinar titled The Future of Interoperability: APIs + Traditional Interfaces Corepoint Founder 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.

How will FHIR ensure better consistency?

When it comes to consistency, the lack of a central standard can have a negative effect on interoperability. While proprietary APIs exhibit some of these downfalls, the also offer some positives, such as enabling users to interact with data in the original form. In the video below, Dave speaks to previous standards and what they can teach us about FHIR development.

Video Thumbnail

Will FHIR supplement or supplant IHE Profiles?

With the new FHIR standard, many tasks will become easier to complete. In this video, Dave discusses how FHIR will operate alongside some of today’s existing standards, while replacing other integration methods. The real-time aspects of FHIR will allow for optimized workflows in more complex cases which are not easily solvable today.

Video Thumbnail

Related Blogs

InteropNOW Podcast Michelle Blackmer Q&A

Michelle Blackmer

Q&A: Data interoperability and the future of health IT

Read more

Stephan Rubin

Do doctors really care about interoperability? … and other insights from Day 2 of ViVE2022

A session from ViVE Day 2, The Complicated Convergence of Clinical and Claims Data, evolved into a conversation about how challenges in interoperability are secondary to challenges in care delivery,

Read more
Lyniate_Rapid_illustration_api_gateway_manager (1)

Lyniate Team

Lyniate introduces Rapid, a healthcare API gateway

Rapid is a healthcare API gateway and manager designed to help health teams create and safeguard APIs, including Fast Healthcare Interoperability Resources (FHIR)-based APIs like those required by the CMS Interoperability and Patient Access Rule.

Read more