> ## 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.

# August 2026

> August 2026 release notes for Suki APIs and SDKs

This release adds the new **Patient Summary API**, APIs that let partners push FHIR data into Suki's Clinical Knowledge Graph (CKG), generate patient summaries for encounters and scheduled appointments, poll generation jobs, and retrieve full and pre-visit Patient Summaries for clinical review and encounter preparation.

## What's new

<Update label="August 2026 - New" tag="LATEST" tags={["New Features"]}>
  ### New features

  <span id="patient-summary-api" />

  <Badge icon="code" size="sm" color="blue">Patient Summary API v1.0.0</Badge>

  **Patient Summary API**: New APIs that let partners upload FHIR data into Suki's Clinical Knowledge Graph (CKG), trigger asynchronous Patient summary generation, poll job status, and retrieve full and pre-visit summaries for encounter preparation and clinical review workflows.

  **Key endpoints**

  * <Badge color="green" size="sm">GET</Badge> [/api/v1/fhir-push/upload-url](/patient-summary-api-reference/ckg-data-ingestion/upload): Request an upload URL for a FHIR bundle.
  * <Badge color="green" size="sm">PUT</Badge> [/api/v1/fhir-push/upload](/patient-summary-api-reference/ckg-data-ingestion/fhir-data): Upload a FHIR bundle to the CKG ingestion endpoint.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/fhir-push/status/{transaction_id}](/patient-summary-api-reference/ckg-data-ingestion/ingestion-status): Check the ingestion status for a previously uploaded bundle.
  * <Badge color="green" size="sm">POST</Badge> [/api/v1/patient-summary/generate/encounter](/patient-summary-api-reference/summary-generation/encounter-summary): Enqueue Patient Summary generation for a single encounter.
  * <Badge color="green" size="sm">POST</Badge> [/api/v1/patient-summary/generate/provider-schedule](/patient-summary-api-reference/summary-generation/scheduled-appointment-summary): Enqueue summaries for a provider schedule or batch run.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/{patient_summary_id}](/patient-summary-api-reference/summaries/patient-summary): Retrieve a generated Patient Summary by ID.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/{patient_summary_id}/pre\_visit](/patient-summary-api-reference/summaries/pre-visit-summary): Retrieve a pre-visit summary used for encounter preparation.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/encounter/{fhir_encounter_id}/practitioner/{fhir_practitioner_id}](/patient-summary-api-reference/summaries/encounter-practitioner): Retrieve a practitioner-facing encounter summary filtered for a specific practitioner.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/encounter/{fhir_encounter_id}/practitioner/{fhir_practitioner_id}/pre\_visit](/patient-summary-api-reference/summaries/encounter-pre-visit): Retrieve a practitioner-facing pre-visit summary for an encounter.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/encounter/{fhir_encounter_id}/practitioner/{fhir_practitioner_id}/status](/patient-summary-api-reference/summary-jobs/encounter-status): Poll generation status for an encounter-specific Patient Summary job.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/patient-summary/{patient_summary_id}/status](/patient-summary-api-reference/summary-jobs/job-status): Poll the generation or processing status for a Patient Summary by ID.

  ## Common use cases

  * **Prepare for patient encounters**: Display pre-visit summaries so clinicians can quickly review the patient's history, active problems, medications, and recent results before the appointment.
  * **Review completed encounters**: Retrieve summaries after a visit to verify documentation, identify follow-up actions, and support billing or quality workflows.
  * **Prepare an entire schedule**: Generate pre-visit summaries for all scheduled appointments so care teams can review patients and prioritize care before the clinic day begins.

  **Why it matters**: Partners can show clinicians ready-to-use Patient summaries without building their own summarization pipeline. The asynchronous job model scales for large FHIR uploads and scheduled batch generation for clinic workflows.

  Learn more in the [Patient Summary API overview](/patient-summary-api-reference/overview).
</Update>