sdp_suki_token). Critically, summary generation reads from data previously ingested through the CKG Data Ingestion APIs. Ensure ingestion status is COMPLETED and that fhir_encounter_id and fhir_practitioner_id match the identifiers in your uploaded FHIR resources.
Available endpoints
Generate Patient Summary For Encounter
Trigger asynchronous summary generation for one encounter and practitioner
Generate Patient Summaries For Scheduled Appointments
Trigger bulk summary generation for all appointments on a provider’s schedule
Related guides
Generate Patient Summaries
Learn scheduled and single-encounter generation workflows
Integrate CKG
Complete CKG ingestion before you trigger summary generation
Patient Summary Basic Usage
Learn the upload, generate, poll, and retrieve Patient Summary flow
Common use cases
Pre-generate summaries before the clinic day starts
Call the scheduled-appointments endpoint each morning with the provider ID and date so summaries are ready when clinicians open their schedule.
Generate a summary for one upcoming visit
Trigger generation for a single encounter when a patient is added to the schedule or when fresh FHIR data arrives close to appointment time.
Kick off async jobs without blocking your UI
Start generation from your backend and return immediately while your application polls job status or loads summaries when processing completes.
Regenerate after a FHIR refresh
Re-trigger generation when you upload updated clinical data so the summary reflects the latest medications, problems, and visit history in CKG.