Skip to content

Bulk FHIR Coordinator

This page tracks InterSystems Bulk FHIR Coordinator as a technical capability adjacent to FHIR Server, Health Connect, and Unified Care Record.

Supported Positioning

InterSystems documentation describes Bulk FHIR Coordinator as mediating bulk data export interactions between a bulk-data client and a FHIR resource server endpoint. It can support bulk export for FHIR resource servers that do not natively support the bulk-data interaction.

Technical Shape

  • Bulk FHIR Coordinator can interact through a home page or through bulk-data REST client requests.
  • Each configuration identifies a FHIR resource server endpoint and the authorization, file location, and other parameters for bulk-data interaction.
  • The FHIR endpoint may be InterSystems IRIS for Health, InterSystems Health Connect, HealthShare Unified Care Record, or another compatible FHIR system that supports required resource-return and Patient/$everything behaviour for relevant exports.
  • Configuration evidence covers client authentication to the coordinator, coordinator authentication to the FHIR server, export storage, ndjson output, and optional direct ingestion into a target FHIR repository. FHIR security documentation also describes OAuth credentials relevant to Bulk FHIR interactions.

Evidence Status

Confidence is high for documented coordinator role, configuration concepts, and OAuth credential handling. It does not prove availability in a given licence, deployment, managed service, customer environment, or UK governance model.

The public documentation should therefore be read as a technical capability boundary: Bulk FHIR Coordinator can mediate bulk-data export interactions and credentialed cloud-FHIR requests, but public sources still do not settle customer licensing, scale limits, audit retention, operational monitoring, or NHS information-governance controls.

Remaining Follow-up Evidence

  • Licensing and product-boundary documentation for Bulk FHIR Coordinator.
  • Export-scale, audit, retention, and storage-governance documentation.
  • Customer evidence for population-health, research, migration, or EHR-to-EHR bulk export use.