Skip to main content
This quickstart walks you through one successful Patient Summary workflow on staging: upload FHIR data to CKG, authenticate, trigger summary generation for an encounter, poll job status, and retrieve the Patient Summary. Your application owns FHIR upload data orchestration, summary generation triggers, job status polling, and how retrieved summaries are presented or integrated into your product. What you will do
  1. Upload FHIR data to CKG with an SDP JWT bearer token and poll ingestion status.
  2. Authenticate to get an sdp_suki_token (and register the user if needed).
  3. Trigger summary generation for an encounter.
  4. Poll job status until complete and retrieve the full summary or pre-visit summary.
Prefer one paste-ready file? Use the Complete staging script in the preferred language below, then follow the numbered steps for the same flow with full explanations.
Using an AI coding tool?Copy the prompt below to point your agent at the Patient Summary skill and Documentation MCP. For every task skill, refer to AI coding tools.

Fetch the Patient Summary skill and connect the documentation MCP.

Open in Cursor

Access and credentials

You need partner credentials to use the Suki Patient Summary APIs. Contact our Partnership team to get your credentials. They will guide you through the Onboarding process and provide what you need to get started.

Prerequisites

To use the Suki Patient Summary APIs, you must have the following:
  • Partner credentials for Suki authentication endpoints (partner_id and partner_token).
  • Ability to generate and sign RS256 SDP JWT bearer tokens for CKG Data Ingestion endpoints.
  • FHIR R4 bundles containing patient clinical data (conditions, medications, encounters, observations).
  • A publicly accessible endpoint (or Okta authorization server) for token validation.

Environments to use for development and testing

This guide uses https://sdp.suki-stage.com for API examples (staging).
Important:
  • The production environment is https://sdp.suki.ai.
  • The staging environment is https://sdp.suki-stage.com.
  • Your partnership team will confirm which environment, base URL, and credentials apply for your integration.

Complete staging script

Replace the credential placeholders, put a FHIR R4 bundle at patient-fhir-bundle.json, then run. For detailed explanations of each step, refer to the numbered steps below.
  • Python: pip install requests then python patient_summary_staging.py.
  • TypeScript (Node): npx tsx patient_summary_staging.ts (Node 18+).

Steps

1

Upload FHIR data to CKG

Step 1:Before you can generate Patient Summaries, you must upload FHIR data to Suki’s Clinical Knowledge Graph (CKG). Call Request upload URL API with the following query parameters:
  • organization_id (required): Your organization identifier.
  • correlation_id (optional): Client-supplied identifier for tracing (max 128 characters).
Step 2:Upload your FHIR R4 bundle JSON to the upload_url using HTTP PUT with Content-Type: application/json and x-goog-content-length-range: 0,524288000.
You can upload a bundle up to 500 MB in size.
Step 3:Poll Poll ingestion status API to know the status of the ingestion job.
Your FHIR bundle must include patient, encounter, and practitioner identifiers that match what you will use when triggering summary generation in Step 3.
Code example:
2

Authenticate to Get a Suki Token

Send a POST request to the Login API endpoint with the following parameters in the request body:
  • partner_id (required): Your unique , which we provide to you securely offline.
  • partner_token (required): The user’s OAuth 2.0 ID token () from your identity provider.
  • provider_id (optional): Unique identifier for the . Required for some authentication flows only.
Handling an unregistered user:
  • If the user is not yet registered in our system, the /login request will fail.
  • In this case, you must first call the Register API endpoint to create the user, then call /login again.
  • You only need to call the register endpoint once for each new user.
  • Refer to the Register API reference for the full specification.
Code example:
Save the suki_token from the response. This token is valid for 1 hour. When it is about to expire, you can get a new one by making the same POST request to /login with a valid partner_token.
3

Trigger Patient Summary Generation for an Encounter

Send a POST request to the Trigger Patient Summary Generation for an Encounter with the following parameters in the request body:
  • fhir_encounter_id (required): The FHIR encounter identifier from your uploaded FHIR bundle.
  • fhir_practitioner_id (required): The FHIR practitioner identifier from your uploaded FHIR bundle.
Code example:
4

Poll Summary Generation Status

Poll Summary Generation Status API for an Encounter until the status field reaches a terminal state. Terminal statuses include COMPLETED, FAILED, and others documented in the API reference.
Poll at reasonable intervals (for example every 5 seconds). Summary generation typically completes within a few seconds to a few minutes depending on the amount of FHIR data.
5

Retrieve Generated Summaries

Once generation completes, retrieve the generated summaries. The Patient Summary APIs provide two retrieval endpoints.
  • Full Patient Summary: Call Retrieve Patient Summary API to get a comprehensive, structured summary containing four specific sections: About Visit, Patient Summary, Previous Visit, and Problems.
  • Pre-visit summary: Call Retrieve pre-visit summary API to get the exact pre-visit section from inside the full patient summary, which was created specifically for the user interface (UI) to display a preview to the provider.
For complete technical specifications, refer to the relevant API Reference pages.

Verify your integration

Before you design the full production workflow, confirm that your staging integration can complete this path:
  • Upload FHIR data to CKG successfully and poll until ingestion completes.
  • Authenticate successfully and use the returned sdp_suki_token in follow-up requests.
  • Trigger summary generation for an encounter with matching FHIR identifiers from your uploaded bundle.
  • Poll job status until the generation completes.
  • Retrieve the full Patient Summary or pre-visit summary with structured clinical data.
After this path works end to end on staging, continue with production rollout and error handling.

Next steps

After you complete your first Patient Summary workflow: Authentication API - Login, register, and authentication configuration. CKG Data Ingestion - Upload FHIR bundles and track ingestion status. Summary Generation API - Trigger asynchronous summary generation jobs. Patient Summaries API - Retrieve full and pre-visit Patient Summaries.
Last modified on August 7, 2026