Overview
Server-to-server FHIR, bulk import, and HL7v2-over-HTTP that run unattended.
Backend integrations are for data movement that should run without a patient or clinician sitting in the browser. A provider organization authorizes server-to-server access, and Medblocks uses that relationship to pull, sync, and export records in the background.
Use this when your product needs organization-scoped data for cohorts, operations, analytics, registries, or downstream systems that stay current over time.
What backend access is for
Backend access fits workflows such as:
- Nightly or scheduled sync for a patient panel.
- Population-level export into your warehouse or FHIR server.
- Operational dashboards that should update without a user launching an app.
- Bulk retrieval from an organization that has approved your integration.
The important difference from patient access is who grants the relationship. Patient access starts with a patient approving your app. Backend access starts with an organization authorizing your server.
How Medblocks fits
Medblocks handles the connection setup, credential storage, source-specific authentication, and operational monitoring around the pull. Once records land, you can export them, listen to events, or inspect status through the API.
For Epic, backend setup centers on SMART Backend Services, organization selection, and FHIR Group IDs.
Configure the connection
Start with Configure Backend. That guide shows where to add backend credentials, organizations, and Group IDs for Epic.
Not sure if this fits you?
Tell us what you're building and we'll show you exactly what you can integrate.