Bulk FHIR
Flat FHIR / FHIR Bulk Data
Bulk FHIR is the FHIR Bulk Data ("$export") specification for efficiently moving large populations of FHIR resources as NDJSON, used for analytics and payer-to-payer exchange.
Bulk FHIR — also called Flat FHIR or FHIR Bulk Data — is the specification for exporting large volumes of FHIR resources at once, rather than one patient at a time. It uses an asynchronous $export operation that produces newline-delimited JSON (NDJSON) files for whole populations.
Bulk FHIR (Flat FHIR STU 1) is part of the CMS-0057-F mandated stack and is essential for use cases that operate on many patients: population health analytics, quality measurement, and the Payer-to-Payer and Provider Access bulk data flows the rule contemplates.
The tradeoff versus transactional FHIR is throughput over immediacy: Bulk FHIR is built to move millions of resources efficiently, which introduces its own mapping, validation, and delivery challenges at scale.
How this relates to Health1st
Health1st's Transformation Agent executes bulk FHIR $export as NDJSON and validates the exported resources against US Core, so large payer-to-payer and analytics data movements come out conformant, not just complete.
Related terms
FHIR is HL7's modern, web-native standard for exchanging healthcare data as modular JSON/XML resources over RESTful APIs.
CMS-0057-F requires impacted US payers to stand up four FHIR APIs — Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization (PARDD) — with API compliance generally due January 1, 2027.
US Core is the HL7 implementation guide that constrains FHIR resources into the specific profiles US regulation requires, binding them to USCDI data elements.
Ready to turn months of interface work into days?
See a live HL7 v2 ↔ FHIR translation on your own message types. No obligation.