Dynamic FHIR API, FHIR, API, HL7, standards, interoperability

®

Interested in pulling data into your APP from Dynamic FHIR API?

The Dynamic FHIR® API provides leading-edge interoperability functionality while meeting ONC 2015 EHR certification requirements 170.315(g)(7-9).
 
It can be implemented as a stand-alone product or as part of the DHIT suite of applications.

Dynamic FHIR API & Patient Portal are modules within the Certified ConnectEHR Enterprise Solution

2015 Edition Cures Edition Logo.png
EHR Vendors

For 2015 Edition certification, the “Base EHR” criteria are the minimum building blocks.  During 2020 and beyond, your customers will need software that is 2015 Edition Certified for:

 

  • 170.315(g)(7) : Application access - patient selection

  • 170.315(g)(8) : Application access - data category request

  • 170.315(g)(9) : Application access - all data request

 

This is a requirement for Improving Interoperability or for maximizing their score under the MIPS/Quality Payment Program.

 

Our API can be easily configured to work with your EHR because it can acquire data from a CCDA,  flat file, or your database via a SQL stored procedure.

Hospitals

Hospitals attesting to Promoting Interoperability in 2020 will need software that is 2015 Edition Certified for:

 

  • 170.315(g)(7) : Application access - patient selection

  • 170.315(g)(8) : Application access - data category request

  • 170.315(g)(9) : Application access - all data request

 

This certification is required for the "Provide Patient Access" measure of the "Patient Electronic Access to Health Information" objective.

 

Our API can be easily configured to work with any 2014 Edition or 2015 Edition certified EHR because it can acquire data from a CCDA and any certified EHR is required to have a native capability to produce CCDAs.

Ambulatory

The Promoting Interoperability portion of MIPS has a required category called "Provide Patients Electronic Access to Their Health Information". One of the two components of Provide Patient Access states:

 

The MIPS eligible clinician ensures the patient's health information is available for the patient (or patient-authorized representative) to access using any application of their choice that is configured to meet the technical specifications of the Application Programming Interface (API) in the MIPS eligible clinician's certified EHR technology.

EHR to Smartphone.png
Multi-Tenant 

Allows a Hospital System to have one Dynamic FHIR server

cloud with flame.png
Hosted Solution

Our hosted Dynamic FHIR solution meets ONC Certification requirements

SMART.png
SMART On FHIR

Create apps that seamlessly and securely run across the healthcare system

hands-shaking.png
Demographics on FHIR

Dynamic FHIR API is connected to third-party applications such as Kno2

ArgonautProject_logo.png
Argonaut Project

Dynamic FHIR API is Argonaut FHIR DSTU 2 enabled

cert.png
FHIR-Enable Your CCDs

Converts each section of a 2.1 or prior CCDA to a FHIR Resource

Please see our Dynamic FHIR API R4 documentation here for full details. Dynamic FHIR API STU3 documentation here.

 

The API makes health information broadly available using FHIR®, a set of clinical interoperability resources under the umbrella of the HL7 standards organization. FHIR is based on common web standards, including XML and JSON, and can be reached through a RESTful protocol in which each FHIR resource has a known URL. The standard continues to grow and become more widely used for patient data.

 

We chose FHIR because it combines the domain-specific features developed over many years through the HL7 standards organization with leading-edge e-commerce and security authorization protocols used by industry leaders like Google, Facebook, and Amazon.

 

The Dynamic FHIR API jumpstarts your interoperability and patient engagement efforts while meeting ONC 2015 Cures Act EHR API certification requirements 170.315(g)(7), (g)(8), and (g)(9).

 

The Dynamic FHIR API makes EHR patient data readily available:

 

  • Uniquely identifies patients by Token

 

  • Enables retrieval of patient data using this token

 

  • Retrieve a specific class of patient data (e.g. problems or medications) or filter by date range

 

  • Retrieve all data available under the Common Clinical Dataset and US Core Data for Interoperability (USCDI) specifications

 

  • Secures the data using the HIPAA-compliant OAuth standard for user authorization

 

  • CCDA to FHIR: data can populated into the DHIT FHIR server via receipt of a version 2.1 CCDA.

To learn more about FHIR®, click here
DHIT Team at Connectathon
DHIT Team at Connectathon

HL7 Connectathon

DHIT Team Nailed it
DHIT Team Nailed it

At HL7 Connectathon (Atlanta)

DHIT Team at Connectathon
DHIT Team at Connectathon

HL7 Connectathon

1/2

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.