By EHR

Bulk FHIR support by EHR through one certified API.

Clinical Extract works with Epic, Oracle Health, eClinicalWorks, athenahealth, MEDITECH, NextGen and Veradigm. Each is certified to ONC §170.315(g)(10) and exports a Group of patients through the same HL7 Bulk Data API. Clinical Extract connects to every one as a read-only backend app running in your environment.

Request a demo The bulk export guide

1 The seven

Pick your EHR.

Each page confirms support and shows the registration steps in that vendor's terms, export time, a dated fact table, sample requests and files, and common questions.

  • Epic

    A Backend Systems app on Epic on FHIR, the study Group by its FHIR ID, Community Connect affiliates through the host organization.

  • Oracle Health

    A System application in code Console on your tenant; the Cerner bulk export under Oracle Health’s name.

  • eClinicalWorks

    A backend app your practice enables; the cohort you build or the roster you match, exported read-only.

  • athenahealth

    A backend app with private_key_jwt on the athenaOne FHIR R4 API, your practice by its practice ID.

  • MEDITECH

    A backend app registered through Greenfield on Expanse; the token endpoint read from the service base.

  • NextGen

    An application entry in the API Developer Portal; access granted in the API Client Portal.

  • Veradigm EHR

    A System app with a JWKS URL; the study Group built from a Reporting module segment.

2 One API

Your EHR already has a certified bulk-export API.

The certification criterion ONC §170.315(g)(10) requires certified EHR technology to export data for a group of patients through HL7 FHIR Bulk Data Access, authorized with SMART Backend Services. Under 45 CFR 170.404(b)(3), developers had to make it available to their customers by December 31, 2022. Clinical Extract uses that API on all seven.

One certified API, seven EHRsSeven EHRs stacked on the left edge of a dashed boundary labelled your environment: Epic and Community Connect, Oracle Health (formerly Cerner), eClinicalWorks, athenahealth (athenaOne), MEDITECH (Expanse), NextGen (NextGen Enterprise) and Veradigm (formerly Allscripts). An arrow from each EHR joins one vertical line, the certified API every one of them serves: ONC §170.315(g)(10), HL7 FHIR Bulk Data Access and SMART Backend Services, with a signed JWT (RS384) and system/<Resource>.read scopes, one per resource type. A single highlighted arrow, labelled NDJSON, from GET Group/{id}/$export, carries the export from that line into Clinical Extract, read-only, inside your environment. Under the arrow, the exchange: Prefer: respond-async, 202 Accepted with Content-Location, 200 OK with the JSON manifest, then the NDJSON files. Under Clinical Extract, the resources it reads and their code systems: Condition (ICD-10-CM, SNOMED CT), Observation (LOINC), MedicationRequest (RxNorm) and Procedure (CPT, SNOMED CT). Clinical Extract writes study.csv and data-dictionary.json.YOUR ENVIRONMENTEpicand Community ConnectOracle Healthformerly CernereClinicalWorksathenahealthathenaOneMEDITECHExpanseNextGenNextGen EnterpriseVeradigmformerly AllscriptsCERTIFIED APIONC §170.315(g)(10)HL7 FHIR Bulk Data AccessSMART Backend ServicesNDJSON, from GET Group/{id}/$exportPrefer: respond-async202 Accepted, Content-Location200 OK, the JSON manifestNDJSON files, one resource per linesigned JWT (RS384), client_credentialssystem/<Resource>.read scopes,one per resource typeClinical Extractread-onlyRESOURCECODE SYSTEMConditionICD-10-CM, SNOMED CTObservationLOINCMedicationRequestRxNormProcedureCPT, SNOMED CTstudy.csvdata-dictionary.json
One certified API, seven EHRsSeven EHRs stacked on the left edge of a dashed boundary labelled your environment: Epic and Community Connect, Oracle Health (formerly Cerner), eClinicalWorks, athenahealth (athenaOne), MEDITECH (Expanse), NextGen (NextGen Enterprise) and Veradigm (formerly Allscripts). An arrow from each EHR joins one vertical line, the certified API every one of them serves: ONC §170.315(g)(10), HL7 FHIR Bulk Data Access and SMART Backend Services, with a signed JWT (RS384) and system/<Resource>.read scopes, one per resource type. A single highlighted arrow, labelled NDJSON, from GET Group/{id}/$export, carries the export from that line into Clinical Extract, read-only, inside your environment. Under the arrow, the exchange: Prefer: respond-async, 202 Accepted with Content-Location, 200 OK with the JSON manifest, then the NDJSON files. Under Clinical Extract, the resources it reads and their code systems: Condition (ICD-10-CM, SNOMED CT), Observation (LOINC), MedicationRequest (RxNorm) and Procedure (CPT, SNOMED CT). Clinical Extract writes study.csv and data-dictionary.json.YOUR ENVIRONMENTEpicand Community ConnectOracle Healthformerly CernereClinicalWorksathenahealthathenaOneMEDITECHExpanseNextGenNextGen EnterpriseVeradigmformerly AllscriptsONC§170.315(g)(10)HL7 FHIRBulk Data AccessSMART BackendServicessigned JWT, RS384one system/<Resource>.readper resource typeNDJSON, fromGET Group/{id}/$exportClinical Extractread-onlyRESOURCE, CODE SYSTEMConditionICD-10-CM, SNOMED CTObservationLOINCMedicationRequestRxNormProcedureCPT, SNOMED CTstudy.csvdata-dictionary.json
Figure 1. One certified API, seven EHRs. Every EHR on this list is certified to ONC §170.315(g)(10), which requires the HL7 Bulk Data Group export behind SMART Backend Services. Clinical Extract uses that one API and connects to each EHR the same way, read-only, in your environment.

How the connection works

3 Questions

Questions about EHR support

Which EHRs support bulk FHIR export?

Every EHR certified to ONC §170.315(g)(10): the criterion requires bulk export for a group of patients through HL7 FHIR Bulk Data Access, authorized with SMART Backend Services, and under 45 CFR 170.404(b)(3) developers had to make it available to their customers by December 31, 2022. Works with Epic, Oracle Health, eClinicalWorks, athenahealth, MEDITECH, NextGen and Veradigm.

Does Clinical Extract connect to each EHR the same way?

On every one it is a read-only backend app: a signed JWT for a token with read scopes, one Group export for the study cohort, the status poll, the NDJSON downloads, then study.csv and its data dictionary. Each page above shows the steps in that vendor’s own terms.

Our EHR is not one of the seven. Does it work?

A certified EHR exposes the same API, so the connection is the same. Tell us which one you run when you request a demo and we walk through its registration with you.

Next

See Clinical Extract run on one of your studies.

Tell us which EHR you run and what the study or registry needs. We reply within one business day to set a meeting time.

Request a demo