Welcome to Suki for Partners

Suki for Partners is Suki’s developer platform for embedding Ambient Clinical Intelligence into healthcare applications with production-ready APIs and SDKs

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: Capture patient-provider conversations and draft structured clinical notes.
• Form filling: Extract visit conversation into structured medical form fields.
• Dictation: Stream speech-to-text in real time for inline editing and scratchpad entry.
• Patient summaries: Generate concise pre-visit summaries from FHIR data bundles.
• Modular integration: Combine hosted UI components, headless React hooks, or REST APIs.
• Clinical intelligence: Access ICD-10/HCC coding, LOINC note sections, Problem-Based Charting, and 80+ multilingual support.

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

Core workflows

Choose what you are building first. Each workflow serves a different purpose. Read the overview to understand the workflow and refer to the quickstart to build the minimum path. Choose an SDK or API after you pick a workflow.

Ambient Documentation

Capture patient-provider conversations and draft structured clinical notes.

OverviewQuickstart

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

Form Filling

Turn visit conversation into structured medical form fields.

OverviewQuickstart

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

Dictation

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

OverviewQuickstart

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

Patient Summary

Generate encounter and pre-visit summaries from FHIR data.

OverviewQuickstart

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

Ambient notes can work across Mobile SDK, Web SDK, Headless Web SDK, and Ambient APIs when you pass shared encounter identifiers. That is part of Ambient, not a separate capability. Refer to Ambient interoperability.

Get started

Follow these steps to integrate Suki into your application. Start with a workflow and a quickstart.

Start Your Integration

1. Choose a Workflow

   Pick Ambient documentation, Form filling, Dictation, or Patient Summary from Core workflows. Open Overview to understand the workflow.

   View Core Workflows
2. Choose an SDK or API

   Decide how much UI Suki should own, then open the matching integration path.

   Choose an Integration
3. Complete Partner Onboarding

   Obtain your partner credentials and configure your integration environment.

   Partner Onboarding
4. Set Up Authentication

   Configure partner authentication so your application can securely access Suki APIs and SDKs.

   Set Up Authentication
5. Build the Minimum Path

   Follow the product quickstart until one end-to-end flow works on staging. Add context, webhooks, and other options only after that succeeds.

   Quickstart

Why Suki

Suki is a purpose-built clinical AI platform, not a general-purpose speech or LLM API adapted for healthcare. Suki for Partners gives you production-ready APIs and SDKs to embed Ambient Clinical Intelligence into your application without building speech recognition, clinical language understanding, note generation, and supporting infrastructure yourself.

You keep full control of your application’s user interface, workflows, and branding while Suki manages the clinical intelligence, AI models, security, compliance, and platform services.

Whether you are building EHRs, telehealth platforms, care management systems, hardware solutions, or revenue cycle applications, Suki helps you add Ambient Clinical Intelligence with less development effort.

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.

Most developers also choose Suki for Partners for these platform benefits:

Production-ready Platform

Integrate Ambient documentation, Form filling, and Dictation using production-ready SDKs and APIs instead of building and maintaining AI infrastructure yourself.

Healthcare-ready Infrastructure

Build on a platform designed for healthcare applications with enterprise security, compliance, and operational reliability.

Continuously Improving AI

Benefit from ongoing improvements to speech recognition, clinical language understanding, and platform capabilities without updating your own AI stack.

Focus on Your Application

Build your application’s user interface, workflows, and integrations while Suki manages the clinical AI platform.

Flexible Integration Options

Choose the integration approach that fits your application, including Web SDK, Headless Web SDK, Mobile SDK, Dictation SDK, Form filling SDK, and REST APIs.

Backward-Compatible Platform

Integrate with a platform that continues to evolve while maintaining backward compatibility across supported SDKs and APIs.

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 or API from the available workflows that best fits your application and integration requirements.

Requirement	Recommended integration	UI	Availability
Embed a pre-built Ambient UI in a web application	Web SDK	Pre-built	GA
Build a custom React Ambient experience	Headless Web SDK	Custom	Beta
Build a native iOS Ambient application	Mobile SDK	Custom	GA
Add speech-to-text to a web application	Dictation SDK	Pre-built	Beta
Capture structured medical forms by voice	Form filling SDK	Pre-built	Beta
Build a server-side Ambient integration	Ambient REST APIs	Custom	GA
Generate patient summaries from FHIR data	Patient Summary API	Custom	Beta
Build a custom Form filling experience	Form filling APIs	Custom	GA
Build an interoperable note workflow	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.

Subscribe to Release notes for new APIs, SDKs, and platform capabilities.

Explore SDKs and APIs

Select a workflow to see the available SDKs and APIs for that workflow.

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.

QuickstartAPI OverviewPartner Authentication

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.

QuickstartWeb SDK OverviewImplementation

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.

QuickstartHeadless Web SDK OverviewCompare Integration Options

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.

QuickstartMobile SDK OverviewCreate Session

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.

QuickstartAPI OverviewAuthentication

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.

QuickstartForm Filling SDK OverviewJavaScript Integration

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.

OverviewJavaScript IntegrationReact Integration

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.

QuickstartAPI OverviewPartner Authentication

For streaming audio and WebSocket behavior, see Dictation streaming.

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.

QuickstartDictation SDK OverviewJavaScript Integration

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.

OverviewJavaScript IntegrationReact Integration

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.

QuickstartAPI OverviewAuthentication

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.

Patient SummaryWeb SDK OverviewEncounter