Lyniate Team

The Interoperability Paradigms of HL7 FHIR

January 31, 2016

Originally posted in Health Standards, by our Sr. Product Manager Rob Brull.

Grieve discussed four interoperability paradigms as they relate to FHIR.  The interoperability paradigms are:

Graphic courtesy of Grahame Grieve.

  1. REST
  2. Documents
  3. Messages
  4. Services

FHIR is meant to be flexible to use and easy to implement. FHIR does not care about the architectural design of the systems. It works equally well for light (mobile) clients and heavy (infrastructure) clients. It can be used for push-based requirements or query-based requirements.

FHIR is promising in many different ways and it will be interesting to watch as it develops and more folks voice their praises and concerns.

Rob has written extensively on FHIR and RESTful web services over the past 3 or so years. To learn more about how FHIR will be used in health data exchange in the coming years, visit our FHIR resources page where we have published a wealth of information, from a basic primer to a full 30-minute webinar presentation on the topic from our CTO Dave Shaver. 

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