FHIR Bulk Data Access, often called Flat FHIR, is an HL7 standard that adds an asynchronous $export operation to FHIR for moving population-level data efficiently. Instead of paging through resources one API call at a time, a client kicks off an export at the system, group, or patient level and retrieves the result as newline-delimited JSON (NDJSON) files, authorized via SMART Backend Services. It is how analytics, quality reporting, payer exchange, and machine-learning pipelines get whole populations of data out of a FHIR server.
FHIR Bulk Data Access
FHIR Bulk Data Access — Flat FHIR — is the standard that makes FHIR usable at population scale. Reading a whole panel of patients one resource at a time is hopeless; bulk data replaces it with an asynchronous $export that hands back flat NDJSON files a data pipeline can actually consume.
- Asynchronous $export - A kick-off request returns a status endpoint; when the export is ready, the client downloads NDJSON files rather than paging live.
- Three levels - System, Group, and Patient exports cover everything from a whole tenant to a defined cohort to a single record.
- Backend-authorized - It runs on SMART Backend Services (client-credentials + signed JWT), the system-to-system half of SMART on FHIR.
In my scoring, bulk data is one of the clearest frontier signals in healthcare: it separates the API-native platforms that treat FHIR as a real data plane (1upHealth, Particle, Aidbox) from the EHRs that publish a compliance CapabilityStatement and stop. For analytics, payer-to-payer exchange, and any agent that needs to reason over a population rather than a single chart, Flat FHIR is the difference between a queryable dataset and a very slow one.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of US Healthcare APIs
Bulk / Flat FHIR $export is a real frontier resource at the API-native platforms (1upHealth, Particle, Aidbox) and largely absent elsewhere.
Governed by these regulations
A standard is the machine-readable contract; a regulation is the law that requires it. These are the regulations that mandate or drive this standard, catalogued at regulations.apievangelist.com.
CMS Interoperability & Prior Authorization Rule
Payer-to-payer and provider data exchange under CMS rules leans on bulk FHIR export.
