> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Summary Jobs APIs

> Poll Patient summary generation status until jobs reach a terminal state

The Patient Summary Job Status APIs enable partners to track asynchronous Patient summary generation after a generation request is submitted. Poll job status until the summary reaches a terminal state, then retrieve the full or pre-visit summary through the Patient Summaries endpoints.

These APIs are called from your servers and authenticated with a Suki Token (`sdp_suki_token`). Critically, call a Summary Jobs endpoint only after you trigger generation through the Summary Generation APIs. Stop polling when status is `COMPLETED`, `FAILED`, or `ABORTED`.

## Available endpoints

<Columns cols={2}>
  <Card title="Generation Status Using Encounter and Practitioner IDs" href="/patient-summary-api-reference/summary-jobs/encounter-status" arrow={true} icon="code">
    Poll generation status using `fhir_encounter_id` and `fhir_practitioner_id`
  </Card>

  <Card title="Generation Status Using Patient Summary ID" href="/patient-summary-api-reference/summary-jobs/job-status" arrow={true} icon="code">
    Poll generation status using `patient_summary_id` from a generation response
  </Card>
</Columns>

## Related guides

<Columns cols={3}>
  <Card title="Generate Patient Summaries" href="/documentation/how-to/patient-summary/generate-patient-summaries" icon="book" cta="Learn more">
    Learn how generation jobs work and when to stop polling
  </Card>

  <Card title="Retrieve Patient Summaries" href="/documentation/how-to/patient-summary/retrieve-patient-summaries" icon="book" cta="Learn more">
    Learn what to retrieve after generation status is COMPLETED
  </Card>

  <Card title="Patient Summary Basic Usage" href="/documentation/how-to/patient-summary/basic-usage" icon="book" cta="Learn more">
    Learn the upload, generate, poll, and retrieve Patient Summary flow
  </Card>
</Columns>

## Common use cases

<Columns cols={2}>
  <Card title="Wait for generation before retrieving summaries">
    Poll status at reasonable intervals so your UI or backend loads summary content only after the job completes successfully.
  </Card>

  <Card title="Track bulk schedule generation per encounter">
    Check status by encounter and practitioner ID when you triggered bulk generation and need per-appointment readiness in a schedule view.
  </Card>

  <Card title="Monitor jobs when you store patient_summary_id">
    Use the ID returned from single-encounter generation to poll status without mapping back to partner encounter identifiers.
  </Card>

  <Card title="Handle failed or aborted generation jobs">
    Detect terminal failure states so your application can retry generation, surface an error to clinicians, or fall back to manual chart review.
  </Card>
</Columns>