August 2026

August 2026 release notes for Suki APIs and SDKs

This release introduces the Patient Summary API so you can ingest FHIR into Suki’s Clinical Knowledge Graph (CKG), generate summaries for encounters and scheduled appointments, poll generation jobs, and retrieve full and pre-visit Patient Summaries for clinical review and encounter preparation. For the Web SDK, we’ve shipped Patient Summary in v3.3.0: the patient profile UI shows a pre-visit snippet and full summary so clinicians can prepare for the visit when your organization is enabled and matching FHIR data is in CKG.

What’s new

​

August 2026 - New

New Features

New features

Patient Summary API v1.0.0

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

• GET /api/v1/fhir-push/upload-url: Request an upload URL for a FHIR bundle.
• PUT /api/v1/fhir-push/upload: Upload a FHIR bundle to the CKG ingestion endpoint.
• GET /api/v1/fhir-push/status/: Check the ingestion status for a previously uploaded bundle.
• POST /api/v1/patient-summary/generate/encounter: Enqueue Patient Summary generation for a single encounter.
• POST /api/v1/patient-summary/generate/provider-schedule: Enqueue summaries for a provider schedule or batch run.
• GET /api/v1/patient-summary/: Retrieve a generated Patient Summary by ID.
• GET /api/v1/patient-summary//pre_visit: Retrieve a pre-visit summary used for encounter preparation.
• GET /api/v1/patient-summary/encounter//practitioner/: Retrieve a practitioner-facing encounter summary filtered for a specific practitioner.
• GET /api/v1/patient-summary/encounter//practitioner//pre_visit: Retrieve a practitioner-facing pre-visit summary for an encounter.
• GET /api/v1/patient-summary/encounter//practitioner//status: Poll generation status for an encounter-specific Patient Summary job.
• GET /api/v1/patient-summary//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: Clinicians can review ready-to-use Patient Summaries before and after visits without partners 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.

What’s enhanced

​

August 2026 - Enhanced

Enhancements

Enhancements

Web SDK v3.3.0

Patient Summary in the Web SDK: From Web SDK v3.3.0, the Headed Web SDK can show a pre-visit Patient Summary on the patient profile. Clinicians see a short snippet, then expand it for the full summary.

To enable this feature in the headed Web SDK:

• Upgrade @suki-sdk/js or @suki-sdk/react to v3.3.0 or later.
• Ask Suki Technical Support to enable Patient Summary for your organization.
• Keep ingesting FHIR into CKG with the Patient Summary CKG Data Ingestion APIs.
• Pass the FHIR encounter id as encounter.identifier and the FHIR practitioner id as encounter.practitionerFhirId when you initialize, and pass the same encounter again when you mount.

You can embed this experience without building the summary screens or calling generate, status, or retrieve APIs yourself. The SDK triggers generation at login from the initialize options. Mounting or calling setEncounter loads the summary. It does not generate again. To generate Patient Summary for a different practitioner, initialize the SDK again with the new practitioner id.

Why it matters: Clinicians get pre-visit context on the patient profile before the appointment, without leaving the headed Web SDK. If you already embed the Web SDK, you can ship that experience without building the summary screens or wiring generate and retrieve calls yourself.

Learn more in the Patient Summary in Web SDK guide, the Encounter type, and the Web SDK changelog.