®

FHIR® (Fast Healthcare Interoperability Resources) Specification is a standard for exchanging healthcare information electronically.

FHIR aims to simplify the sharing of health information without sacrificing information integrity. It leverages existing logical and theoretical models to provide a consistent, easy to implement, and rigorous mechanism for exchanging data between healthcare applications. FHIR has built-in mechanisms for traceability to the HL7 RIM and other important content models. 

The Argonaut Project is an implementation community that includes leading technology vendors and provider organizations.  Their goal is to accelerate the use of FHIR and OAuth in health care information exchange.

SMART: Tech Stack for Health Apps

SMART on FHIR is a set of open specifications to integrate apps with Electronic Health Records, portals, Health Information Exchanges, and other Health IT systems. You get…

Clean, structured data: FHIR

Easy-to-use, resource-oriented REST API for structured clinical data.

Scopes and permissions: OAuth2

When an EHR user launches your app, you get a “launch request” notification.

Simple sign-in: OpenID Connect

If your app needs to authenticate the EHR end-user, OpenID Connect is there to help.

Lightweight UI integration: HTML5

SMART on FHIR allows web apps to run inside browser widgets or inline frames, so users can interact without leaving the EHR environment.

HL7 FHIR for Executives - an overview
(Rene Spronk)

Data interoperability in the healthcare sector remains a challenge - there are a lot of interoperability standards in this area, yet the goal of seamless systems integration remains elusive. Healthcare is fractal in nature, and the economics tend to favor a silo-ed approach. At the same time, technology does change healthcare: the patient is put in ever more control, Open APIs are in increasing demand, and the use of AI is a necessity going forward. The HL7 FHIR standard is tool which was specifically created to deal with these changes.

Rene Spronk, Trainer, and involved with the FHIR standard since its inception, provides a "TED-like" summary overview of the HL7 FHIR standard from a strategic perspective. He will cover the origins of FHIR, its core components, as well as its benefits and challenges.

 

Recorded on March 25, 2019, during an HL7 Norway event at eHelse Direktoratet in Oslo.

HL7 FHIR for Executives.png

Our Commitment to FHIR

We chose FHIR because it combines the domain-specific features developed over many years through the HL7 standards organization with leading-edge enterprise and security authorization protocols used by industry leaders like Google, Facebook and Amazon. We are committed to developing a range of applications and services that combine the FHIR standard with an accessible end-user experience in order to help achieve long-promised goals in interoperability and patient engagement.

The developers and stakeholders behind the standard have been widening its reach to a variety of use cases in a collaborative process that includes periodic Connectathons, Development Days and other meetups. A sampling of recent events is found below.

FHIR Connectathon 4
FHIR and CCDA Implementation-a-thon 4: Care Plans, Root IDs and much more
Last month, Dynamic Health IT was in attendance for another meeting of minds hosted by HL7 International down in San Antonio, TX. While these events around CCDA and FHIR have become a regular part of our travel schedule, there's nothing routine about taking a deep dive into healthcare standards. Each trip provides an opportunity to combine ground-level development with high-level policy-making, up to and including interactions with HL7 and ONC policy-makers.
For more information on HL7 FHIR®, click here.

FHIR® is the registered trademark of Health Level Seven International and is used with the permission of HL7. The use of these trademarks do not constitute a product endorsement by HL7.    

Dynamic Health IT, Inc . © 2019

FHIR® is the registered trademark of Health Level Seven International and is used with the permission of HL7. The use of these trademarks do not constitute a product endorsement by HL7.