Skip to main content
Suki for Partners (also referred to as Suki Platform) is a developer platform that makes it easy to bring Ambient Clinical Intelligence (ACI) into your healthcare applications. Use Suki’s production-ready and to add AI-powered clinical documentation, voice interactions, structured clinical data, and more to your product without building the underlying speech, language, and AI infrastructure yourself. This lets you focus on creating better clinical workflows while Suki handles the intelligence, including the underlying speech recognition, clinical language understanding, note generation, and AI infrastructure, behind them.

​
Build clinical workflows with Suki for Partners

Build clinical AI into your healthcare applications with Suki. Choose the capabilities that fit your workflow, from documenting patient visits to completing medical forms and supporting clinical coding.
  • Ambient documentation: Turn patient-clinician conversations into structured clinical notes that clinicians can review and edit, reducing manual documentation work.
  • Form filling: Populate medical form fields from the visit conversation, helping clinicians complete required documentation with less manual entry.
  • Dictation: Convert speech into text as clinicians speak, making it easier to enter notes directly into the chart or capture thoughts in a .
  • Patient summaries: Bring relevant information from existing patient records into a concise pre-visit summary, helping clinicians prepare for appointments. Summaries are built from data ingested into CKG.
  • E/M Coding: Generate recommended Evaluation and Management codes from a completed note to support coding review and revenue cycle workflows. Use E/M Coding with an ambient session or through the standalone E/M Coding APIs.
  • Flexible integration: Embed Suki’s , build custom experiences with , or integrate directly through to fit your application’s needs.
  • Clinical intelligence: Support clinical documentation and coding workflows with and coding, -based note sections, , and more than 80 languages.
  • Combine these capabilities to create workflows that fit your product, your clinicians, and your existing systems.
  • You keep your UI, branding, and workflows. Suki handles the clinical AI infrastructure behind your product.

​
Get started

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

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.

Install Plugins

Add the Suki Cookbook plugin to run short integration recipes in your codebase.

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.

Secure Your Credentials

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

Understand Core Workflows

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

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.

Explore Features and Guides

After one path works, add context, webhooks, interoperability, and deeper product guides.
Build some of the popular clinical workflows with Suki like capturing patient-provider conversations, filling medical forms, and dictating notes etc. Choose the capabilities you need and integrate them using Suki’s SDKs, APIs, or a combination of both. Start with the workflow guides to understand how each capability works and how it fits into your application. Then follow the Quickstart to build your first working integration.

Ambient Documentation (Interoperable)

Capture patient-provider conversations and draft structured clinical notes.

Form Filling

Turn visit conversation into structured medical form fields.

Dictation

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

Patient Summary

Generate encounter and pre-visit summaries from FHIR data.

​
Why Suki for Partners

Suki for Partners is a developer platform for integrating Suki’s Ambient Clinical Intelligence (ACI) into your applications. It provides the APIs, SDKs, and infrastructure you need to build AI-powered clinical workflows into EHRs, telehealth platforms, digital health applications, and revenue cycle management (RCM) solutions.
Suki for Partners is purpose-built for clinical applications. It is not a general-purpose speech or LLM API adapted for healthcare.
Use Suki’s APIs and SDKs to add capabilities such as clinical documentation, voice interactions, and structured clinical data to your application. Suki handles the underlying speech recognition, clinical language understanding, note generation, and AI infrastructure, so you can focus on building your product rather than developing these capabilities from scratch.

​
Build the experience your product needs

Use Suki’s SDKs to integrate supported UI components and workflows, or use the APIs to build your own interface and control the entire user experience. You decide how Suki appears in your application, from using Suki branding to delivering a fully white-labeled experience under your own brand. Regardless of how you integrate, you retain control of your application’s UI, workflows, and branding. Suki provides the clinical intelligence, AI models, security, compliance, and platform infrastructure that power those experiences. Whether you are extending an existing product or building a new clinical application, Suki for Partners gives you the building blocks to integrate clinical AI into your development workflow. A few things that distinguish Suki for Partners from its competitors:
  • 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.
  • 50+ patents- Suki believes in the power of innovation and has a strong patent portfolio in the field of Ambient Clinical Intelligence. This makes us a leader in the field of Clinical AI and workflows.
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. Diagram: your application connects through SDKs and APIs to the Suki platform for Ambient AI services, and separately to your FHIR / EHR systems. Diagram: your application connects through SDKs and APIs to the Suki platform for Ambient AI services, and separately to your FHIR / EHR systems.

​
Typical developer workflow

Most Ambient, Form filling, and Dictation integrations follow the same session lifecycle: Diagram: choose SDK or API, authenticate, start session, capture audio, AI processing on the Suki platform, then receive notes, forms, or transcripts. Diagram: choose SDK or API, authenticate, start session, capture audio, AI processing on the Suki platform, then receive notes, forms, or transcripts. Choose the SDK, API, or a combination of both that best fits your application and integration requirements.

​
What can you build

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

Automate Clinical Documentation

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

Fill Your Medical Forms

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

Add Real-Time Dictation

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

Generate Patient Summaries for encounters

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.

Assist Your Revenue Cycle Workflows

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

Organize Your Clinical Notes by Patient Problems

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

Support 80+ Languages During Capture

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

Customize Your Clinical 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.
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.

Last modified on November 5, 2026