Export to FHIR server
Push records from Medblocks to a destination FHIR R4 server.
FHIR server export pushes records from Medblocks to a destination FHIR R4 server. Use it when another system should receive FHIR resources directly instead of reading files from object storage.
This is a dashboard-managed export. Create it once for the workspace, then Medblocks runs a first backfill and later delta exports when new pulls finish.
Add a FHIR server destination
Click Add FHIR Server, then choose an internal test server or a custom FHIR server.
Enter destination settings
The destination needs these fields.
| Field | Purpose |
|---|---|
| Name | Label shown in the dashboard. |
| FHIR base URL | Destination R4 server base URL. |
| Auth type | No auth, bearer token, or OAuth 2.0 client credentials. |
| Bearer token | Token used when auth type is bearer token. |
| Token endpoint | OAuth 2.0 token URL when client credentials are used. |
| Client ID and secret | OAuth 2.0 client credentials. |
| Scope | Optional OAuth 2.0 scope if your server requires one. |
Medblocks validates connectivity before saving. If the test fails, fix the URL, credentials, or network allowlist before creating the destination.
Save and backfill
Saving starts an initial export that backfills existing data. After that, new patient data triggers delta exports automatically based on the destination watermark.
Monitor runs
Open the destination detail page for run history, progress, completion times, resource counts, and errors.
Delivery notes
- Exports run per destination.
- One destination failing does not affect others.
- Disabled destinations are skipped.
- Reactivating a destination resumes from its last saved position.
- Rotate credentials in the dashboard before revoking the old credential on the destination server.