FHIR Bulk Data Proposal (aka “Flat FHIR”)


Healthcare organizations have many reasons for bulk-data export, including, populating a data warehouse for operational or clinical analytics, leveraging population health and decision support tools from external vendor, migrating from one EHR vendor to another, and submitting data to regulatory agencies like CMS. Today, bulk export is often accomplished through proprietary pipelines and every data transfer operation becomes an engineering and mapping project. This specification will sketch out a FHIR-based approach to bulk export.


The SMART on FHIR API is evolving in parallel with the FHIR ballot releases. If you spot problems, please file an issue. Or better yet, you can edit this page.