Skip to main content
Patient Summary generation is async. Empty or incomplete summaries usually mean you retrieved too early, CKG ingestion never reached COMPLETED, or generation ended in FAILED or ABORTED. You need a Suki Token (sdp_suki_token) for upload, generate, status, and retrieve. A Partner Token alone is not enough.

โ€‹
Common causes

  • Retrieving the summary before generation status is COMPLETED.
  • Triggering generation before CKG ingestion status is COMPLETED.
  • Keeping the poll loop running after FAILED or ABORTED.
  • Treating a 403 permission_denied as empty content.

โ€‹
Fix

1

Finish CKG Ingestion First

Upload FHIR data, then poll ingestion status until COMPLETED. Stop on FAILED or ARCHIVED.
2

Generate, Then Poll Job Status

Call generate, then poll encounter or job status until COMPLETED. Status values include READY, RUNNING, COMPLETED, FAILED, and ABORTED. Stop on FAILED or ABORTED.
3

Retrieve Only After COMPLETED

Call full or pre-visit summary endpoints only when generation status is COMPLETED. Use patient_summary_id from generation, or the fhir_encounter_id and fhir_practitioner_id pair you used.
4

If You Get 403

Fix organization access. See 403 permission_denied, insufficient_scope, or sbac_denied.
Order from the Patient Summary quickstart: upload and poll ingestion, Login when needed, generate, poll generation status, then retrieve.

โ€‹
Next steps

Patient Summary quickstart - Upload, generate, poll, and retrieve Summary jobs - When to stop polling Patient Summary error messages - Authorization and request error ids 403 permission_denied, insufficient_scope, or sbac_denied - Organization and scope failures Suki Token expired during a long session - Refresh the 1 hour Suki Token during long poll loops
Last modified on September 29, 2026