Skip to main content

FHIR export & bulk data

What it does​

Interop surfaces let authorized staff export a patient's FHIR record from the patient dashboard and run Bulk Data population exports for downstream analytics or exchange. Exports carry a mandatory purpose of use for audit; output is downloaded to the browser and is not cached by the UI.

Where to find it​

  • Bulk Data export console — /admin/interop/bulk-export (requires fhir.bulk-export.read).
  • Patient record export — Export FHIR record button on the patient dashboard (requires fhir.export.read).

Common tasks​

Export one patient's record​

  1. Open a patient in Demographics.
  2. Choose Export FHIR record and select a purpose of use.
  3. Confirm; the browser saves a FHIR JSON bundle. If you lack permission the action is unavailable (the server answers not-found by design).

Run a bulk export​

  1. Open Admin → Interop → Bulk export.
  2. Select a purpose of use and the resource types to include.
  3. Start the job; the screen polls progress until a manifest appears.
  4. Download each NDJSON file from the manifest. Review any error file listed — it names patients who could not be included.
  5. Cancel or delete the job when finished; output expires after the backend retention window.

Tips & limitations​

  • Bulk export is async: you poll status until files are ready — there is no instant download.
  • Manifest links require your session token; use the in-app download buttons, not copied URLs.
  • Exported bundles and NDJSON files are PHI; handle them per local policy.