Bulk Export Status

Checks the status of a FHIR bulk data export request.

Inputs

payload.request string

The bulk export request ID or URL (required)

accessToken string

Optional: Provide your own access token. If not provided, backend token will be fetched automatically

bulkExport object

Bulk export metadata from previous nodes

Outputs

payload object

Complete status response from bulk export

payload.completed boolean

Whether the export is complete

payload.progress string

Progress indicator from the server

payload.output array

List of output files (when complete)

payload.error array

List of error files (if any)

Details

This node checks the status of a bulk export request. It can perform a single status check or poll automatically until the export completes.

The node requires an active integration context. It will automatically fetch a backend access token using the integration's credentials.

Examples

Input from Kickoff Node:

msg.payload = {
    request: "abc123-def456"  // Request ID from Kickoff node
};

Completed Export Response:

{
    "completed": true,
    "output": [
        {"type": "Patient", "url": "https://fhir.server/file1.ndjson"},
        {"type": "Encounter", "url": "https://fhir.server/file2.ndjson"}
    ],
    "error": []
}

In-Progress Response:

{
    "completed": false,
    "progress": "50%",
    "retryAfter": 120
}

Best Practices

• Enable auto-polling for exports that may take more than a few seconds
• Set appropriate maxWaitTime to prevent indefinite waiting
• Check payload.error array for partial failures
• Use a switch node to handle completed vs in-progress states
• Log export progress for debugging large exports