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
Generation Status Using Encounter and Practitioner IDs
Poll generation status using
fhir_encounter_id and fhir_practitioner_idGeneration Status Using Patient Summary ID
Poll generation status using
patient_summary_id from a generation responseRelated guides
Generate Patient Summaries
Learn how generation jobs work and when to stop polling
Retrieve Patient Summaries
Learn what to retrieve after generation status is COMPLETED
Patient Summary Basic Usage
Learn the upload, generate, poll, and retrieve Patient Summary flow
Common use cases
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.
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.
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.
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.