The Dynamic FHIR® API provides leading edge interoperability and meets ONC 2015 Cures Update EHR certification requirements 170.315(g)(7, 9) and now (g)(10) Bulk FHIR (Flat FHIR).
Dynamic FHIR API leverages FHIR R4 and SMART on FHIR Core Capabilities:
Launch Standalone Patient (g)(7, 9) & (g)(10)
LaunchEHR Practitioner (g)(10)
Bulk FHIR with Backend Service Authorization (g)(10)
It can be implemented as a stand-alone product or as part of the DHIT suite of applications.
Interested in pulling data into your APP from Dynamic FHIR API?
Dynamic FHIR API & Patient Portal are modules within the Certified ConnectEHR Enterprise Solution
Allows a health system or EHR vendor to share a Dynamic FHIR server
Our hosted Dynamic FHIR solution meets ONC Certification requirements
SMART On FHIR
Create apps that run seamlessly and securely across the healthcare system
Demographics on FHIR
Dynamic FHIR API is connected to third-party applications such as, Kno2
Dynamic FHIR API is Argonaut FHIR DSTU 2 enabled
Bulk FHIR Data Store
Populated from CCDs. Development underway for additional data sources.
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 jump-starts your interoperability and patient engagement efforts while meeting ONC 2015 EHR API certification requirements 170.315(g)(7), (g)(9), and (g)(10).
The Dynamic FHIR API makes EHR patient data readily available:
The data is populated into the DHIT FHIR server via receipt of a version 2.1 CCDA.
It includes an optional FHIR Datastore and FHIR server. The FHIR Datastore can optionally be populated from various sources such as HL7v2 messages, in addition to C-CDAs.
Delivers XML or JSON to API client of your choice.
Retrieves all USCDIv1 data or a class of data (e.g. clinical notes, problems, labs, or medications)
Implemented as a stand-alone product or part of the DHIT suite.
Secures the data using the HIPAA-compliant OATH standard for user authorization
The Dynamic FHIR API supports the following access/launch types:
Patient Access from an End-User Device: Standalone Launch provides patients access to USCDIv1 data in XML or JSON format via FHIR R4 DocumentReference Resource from any compatible app using Authorization Code Flow.
Patient Portal API Access: Patient Launch of an App from within a Patient Portal user session using the EHR Launch Flow.
Practitioner Portal API Access: Practitioner Launch of an App from within their EHR session. The EHR Launch Flow can be either a Single-patient app that runs in the context of a patient record or a User-level app (Ex. Appointment manager).
Backend Service Access for Bulk Data (Flat FHIR): Provides access to Clients autonomously or semi-autonomously that need to access to resources from FHIR servers that have pre-authorized defined scopes of access.