- Upload FHIR data to CKG with an SDP JWT bearer token and poll ingestion status.
- Authenticate to get an
sdp_suki_token(and register the user if needed). - Trigger summary generation for an encounter.
- Poll job status until complete and retrieve the full summary or pre-visit summary.
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_idandpartner_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 useshttps://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 atpatient-fhir-bundle.json, then run. For detailed explanations of each step, refer to the numbered steps below.
- Python:
pip install requeststhenpython 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:Step 3:Poll Poll ingestion status API to know the status of the ingestion job.Code example:
- organization_id (required): Your organization identifier.
- correlation_id (optional): Client-supplied identifier for tracing (max 128 characters).
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.
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.
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.
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.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_tokenin 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.