Welcome to Suki Developer Documentation

Explore the docs to understand how to use Suki APIs and SDKs to embed Ambient Clinical Intelligence into healthcare applications. Integrate in days, not months

Suki for Partners provides production-ready APIs and SDKs to embed Ambient Clinical Intelligence (ACI) directly into healthcare applications without building speech, language, and model infrastructure yourself.

Build modular, interoperable clinical AI workflows with Suki for Partners:

• Ambient documentation: Record the visit conversation and generate a structured clinical note for review.
• Form filling: Fill medical form fields from what was said during the visit.
• Dictation: Turn speech into text as the clinician speaks, so they can edit in the chart or capture notes in a scratchpad.
• Patient summaries: Create a short pre-visit briefing from the patient’s existing health records (FHIR).
• Modular integration: Combine hosted UI, headless React hooks, or REST APIs in the same product.
• Clinical intelligence: Use ICD10 and HCC coding, LOINC note sections, Problem-Based Charting, and support for 80+ languages.

You keep your UI, branding, and workflows. Suki handles all clinical AI infrastructure and services behind your product.

Get started

Recommended path for new developers: Follow these steps to go from zero to a working Suki integration.

1. Build with AI Tools

   Build with AI tools like Claude, Gemini, or GPT. Use the Suki Documentation MCP, Skills and Plugins to get started.

   AI Coding Tools

   Connect skills, the Documentation MCP, custom plugins, page AI tools, and product prompts to your coding agent.

   Documentation MCP

   Give your editor live search and page read access to published Suki docs.

   Install Skills

   Load custom skills based on which workflow you are integrating to build your product.

2. Get Access and Make Your First Call

   Get partner credentials, then run one product quickstart until a single end-to-end flow works on staging. Skip webhooks and extra options until that succeeds.
3. Secure Your Credentials

   Keep Partner Tokens and Suki Tokens on your backend. Configure partner authentication before you move past staging experiments.

4. Understand Core Workflows

   Learn what each workflow does, and how partner apps combine them to build their product.

5. Choose an SDK or API

   Decide how much UI Suki should own (headed, headless, or API-first). Most partner products use SDKs and APIs together to reach their desired user experience.

6. Explore Features and Guides

   After one path works, add context, webhooks, interoperability, and deeper product guides.

Popular workflows

With Suki, you can build different workflows and features into your application. Choose the workflows that match your use case, then use the relevant SDKs, APIs, or a combination of both to build your integration. Start by reading the workflow guides to understand how each workflow works then follow the quickstart to build your first working integration.

Ambient Documentation (Interoperable)

Capture patient-provider conversations and draft structured clinical notes.

npx skills add https://developer.suki.ai --skill suki-ambient

Form Filling

Turn visit conversation into structured medical form fields.

npx skills add https://developer.suki.ai --skill suki-form-filling

Dictation

Stream speech-to-text for inline editing and scratchpad entry.

npx skills add https://developer.suki.ai --skill suki-dictation

Patient Summary

Generate encounter and pre-visit summaries from FHIR data.

npx skills add https://developer.suki.ai --skill suki-patient-summary

Why Suki

Suki is a purpose-built clinical AI platform, not a general-purpose speech or LLM API adapted for healthcare. Suki for Partners provides production-ready APIs and SDKs that let you embed AI-powered clinical workflows into your application without building speech recognition, clinical language understanding, note generation, or the supporting infrastructure yourself.

You keep full control of your application’s UI, workflows, and branding, while Suki provides the clinical intelligence, AI models, security, compliance, and platform services behind those experiences.

Whether you are building an EHR, telehealth platform, care management system, hardware solution, or revenue cycle application, Suki gives you the building blocks to add clinical AI capabilities to your product. You can choose the workflows and capabilities that fit your use case, then integrate them into your existing application with Suki APIs and SDKs.

A few things that distinguish Suki:

• Clinical depth across 100+ specialties. Note content reflects real clinical context for cardiology, behavioral health, and other specialties rather than generic templates.
• 80+ language support. Patients can speak in their preferred language while clinicians receive formatted English documentation automatically, with no manual translation step.
• Multiple integration modalities. Choose a pre-built headed UI, headless React hooks, native iOS, or REST APIs, and combine them in the same workflow. Most platforms offer one or two paths; Suki supports all of them from a single platform.
• You own the UX and branding. Customize the Web SDK to match your design system, own every screen with the Headless Web SDK, or go fully API-driven. You control how much Suki branding appears.
• Enterprise healthcare compliance. HIPAA compliance, SOC 2 Type II certification, and end-to-end encryption are built in, so you inherit an established security posture rather than building it yourself.
• Production-ready in weeks, not months. Partner teams typically integrate in 2 to 4 weeks instead of spending 6 to 12 months building AI infrastructure, clinical workflows, and compliance programs in house.

For a full business and technical evaluation, see the Suki for Partners Executive Summary.

Platform architecture

Your app connects to Suki through client SDKs or backend REST APIs. Suki processes clinical audio with Ambient AI services, while your application integrates with FHIR / EHR systems downstream.

Typical developer workflow

Most Ambient, Form filling, and Dictation integrations follow the same session lifecycle:

Recommended integrations

Choose the SDK, API, or a combination of both that best fits your application and integration requirements.

Requirement	Recommended integration	UI	Availability
Embed Suki’s Ambient UI in your web app	Web SDK	Pre-built	GA
Build Ambient in React with your own UI	Headless Web SDK	Custom	Beta
Add Ambient to a native iOS app	Mobile SDK	Custom	GA
Add real-time dictation to your web app	Dictation SDK	Pre-built	Beta
Fill medical forms by voice in your web app	Form filling SDK	Pre-built	Beta
Add Form filling to a native iOS app	Mobile SDK Form filling	Custom	GA
Call Ambient APIs from your backend	Ambient REST APIs	Custom	GA
Generate a pre-visit summary from FHIR data	Patient Summary API	Custom	Beta
Build Form filling with your own UI	Form filling APIs	Custom	GA
Continue the same ambient note across Web SDK, Mobile SDK, and APIs	Web SDK, Mobile SDK, and Ambient REST APIs	Custom + Pre-built	GA

What can you build

Build Ambient Clinical Intelligence workflows across Ambient documentation, structured forms, real-time dictation, clinical context, and more:

Ambient Documentation

Capture patient-provider conversations and generate structured clinical notes for clinician review before EHR handoff.

Form Filling

Convert visit conversation into structured medical form fields using Suki templates, then review and save those values.

Dictation

Convert clinician speech into medical text in real time when your product needs transcription, not a full ambient note.

Patient Summaries

Generate concise patient summaries from FHIR data, poll job status, and retrieve full or pre-visit encounter summaries.

Interoperable Note Workflow

Start an ambient encounter on mobile, continue on web, and retrieve one shared note. Pass `emr_encounter_id` across SDKs and APIs.

Assisted Revenue Cycle

Retrieve ICD-10 and HCC diagnosis codes from ambient structured data for coding and risk-adjustment workflows.

Problem-Based Charting

Organize clinical notes by patient problems and active diagnoses instead of traditional SOAP sections.

Multilingual Support

Support 80+ languages during capture while generating standardized English clinical notes automatically.

LOINC Note Sections

Configure custom clinical note sections and templates using standardized LOINC codes and specialty preferences.

---

Explore All Use Cases

Explore all use cases and how to build them with Suki.

Explore All Features

Explore all features and how to build them with Suki.

Explore New Features

Stay updated as we continuously release features to improve the platform offerings.

Integrate with available SDKs & APIs

Choose the SDK, API, or a combination of both to start integrating with Suki.

Ambient Workflows

Choose the SDK or API that matches your UI strategy and technical approach:

Ambient REST APIs

Call Suki directly from your backend when you need a custom UI, selective feature wiring, or full control of the user experience.

Use REST for session management and content retrieval, the Partner WebSocket for audio streaming, and webhooks for asynchronous completion.

Feature availability depends on your partner configuration. To confirm access, contact our Partnership team.

Web SDK

The Suki Web SDK ships hosted UI components for web healthcare apps. Add ambient note workflows without designing the full clinical UI yourself.

Headless Web SDK

Beta

For React 18+ apps that need full control over layout and branding. Use hooks and core APIs for authentication, ambient sessions, and streaming while you build every screen to match your design system.

The Headless Web SDK is currently in Beta.

Mobile SDK

The Suki Mobile SDK is a headless SDK for native mobile apps. Design your own UI while using SDK functions for note generation and session control.

The Mobile SDK currently supports iOS.

Form Filling Workflows

Choose the integration method that fits your UI strategy and technical approach:

Form Filling REST APIs

Use Form filling APIs when you need a custom UI, existing-system integration, or full control over capture, session lifecycle, and how structured output is saved.

Create sessions, seed context, stream audio over the shared Partner ambient WebSocket, retrieve structured form data, and submit feedback using REST endpoints.

For streaming audio and shared WebSocket behavior, see Audio streaming.

Form Filling SDK

Beta

Embed Form filling in web applications with a hosted iframe or React components when you want voice-driven medical forms without building the full Form filling API workflow yourself.

Sign in with partner credentials, call start() with your form template IDs, and receive structured JSON through SDK callbacks and your partner webhook.

The Form filling SDK is currently in Beta.

Web SDK

Use Web SDK Form filling when you already use @suki-sdk/js or @suki-sdk/react at v3.2.0 or later. Import Form filling from the Web SDK package. You do not need a standalone Form filling SDK install.

Start Form filling with your form template IDs and receive structured JSON through callbacks and your partner webhook.

Mobile SDK

Use Mobile SDK Form filling on iOS when you already use SukiAmbientCore and want a headless Form filling session.

You own the recorder and form review UI. Requires Mobile SDK v2.9.0 or later. Ambient note sessions remain a separate workflow on the same stack.

The Mobile SDK currently supports iOS for Form filling.

Dictation Workflows

Choose the integration method that fits your UI strategy and technical approach:

Dictation REST APIs

Use Dictation APIs when you need a custom UI, existing-system integration, or full control over capture, session lifecycle, and how transcript text is returned.

Create transcription sessions, stream audio over a WebSocket, receive live transcripts, and end sessions when capture is finished.

For streaming audio and WebSocket behavior, see Dictation streaming. For reshaping selected text after Dictation, see Content rewrite.

Dictation SDK

Beta

Embed clinical Dictation in web applications with a hosted iframe. Use in-field mode on a specific text control or scratchpad mode for a floating Dictation UI. Integrate with JavaScript or React; you design entry points and receive transcript text through callbacks.

The Dictation SDK is currently in Beta.

Web SDK

Use Web SDK Dictation when you already use @suki-sdk/js or @suki-sdk/react. Import Dictation from the Web SDK package. You do not need a standalone Dictation SDK install.

Use in-field mode on a specific text control or scratchpad mode for a floating Dictation UI. You design entry points and receive transcript text through callbacks.

Patient Summary Workflows

Choose the integration method that fits your UI strategy and technical approach:

Patient Summary REST APIs

Beta

Use Patient Summary APIs when you need a custom UI or full control over FHIR ingestion, summary generation, and how summaries are displayed.

Upload FHIR bundles to the Clinical Knowledge Graph (CKG), trigger asynchronous summary generation, poll job status, and retrieve full or pre-visit summaries using REST endpoints.

For CKG Data Ingestion and summary retrieval details, see CKG Data Ingestion.

Web SDK

Show Patient Summary on the headed Web SDK patient profile from v3.3.0. Ingest FHIR into CKG, enable Patient Summary for your organization, and pass matching encounter.identifier and encounter.practitionerFhirId when you initialize and when you mount.

The Web SDK owns the Patient Summary UI. You do not call generate, status, or retrieve APIs for this headed workflow.