What problem does it solve? Exporting large volumes of FHIR resources from the Helios FHIR Server requires an asynchronous workflow with job state tracking, output storage, and conformance to the FHIR Bulk Data Access specification, which is complex to configure and operate correctly. ## Core Features & Use Cases - Asynchronous Export Lifecycle: Kick off system, patient, or group exports with Prefer: respond-async, poll job status, retrieve manifests, download NDJSON output, and cancel jobs. - Flexible Output Storage: Write export files to local filesystem or S3-compatible storage such as MinIO, with pre-signed download URLs and configurable retention TTLs. - Parameter Handling: Supports _typeFilter, _elements with SUBSETTED tagging, and group export _since behavior, while rejecting unsupported parameters per the Prefer: handling header. - Use Case: Run the Inferno bulk data conformance workflow against a multi-instance deployment using PostgreSQL for job state and MinIO for export output. ## Quick Start Start the HFS server and kick off a patient export by sending a GET request to /Patient/$export with the Prefer: respond-async header, then poll the returned status URL for the manifest.
