Lyniate Team

FHIR and the Future of Integration Engines

August 16, 2017

Video Thumbnail
Integration engines allow healthcare organizations to take control of their data and make it interoperable between databases and applications – along with many additional features and functions that make building, monitoring, and managing high quality interfaces easier. Although manual code is sometimes required when building interfaces in Corepoint Integration Engine, the automation and building processes allow for a dramatically improved process that promotes consistency, which benefits other members of the interface team. The FHIR standard aims to further simplify interfacing by using modern RESTful-based web services.

Access our latest FHIR Resources.

With Corepoint, the main goal is allowing interface developers to focus on workflow improvements and clinical data instead of spending time on the technical parts of interface construction. FHIR takes the next logical step and further simplifies the technical components, giving Corepoint users a faster and more streamlined experience.

Watch Corepoint Health CTO Dave Shaver explain FHIR interfacing in more detail:


Video Thumbnail
3:56

Related Blogs

Lyniate Team

FHIR vs. HL7: We explain the key differences

This article offers a deep dive into the differences between HL7 and FHIR to help industry insiders and newcomers understand how healthcare standards have evolved over time and what’s on the horizon.

Read more
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