Features Overview

Suki for Partners provides APIs and SDKs that let you embed Ambient Clinical Intelligence (ACI) into your healthcare application. You can integrate individual clinical workflows or combine them to support different stages of a patient encounter. The platform brings together clinical documentation, speech recognition, structured form capture, coding, medication orders, patient data summaries, and shared platform services. These capabilities let you build clinical workflows without developing your own speech recognition, clinical language processing, or AI infrastructure. This page provides an overview of the capabilities available in Suki for Partners, how they fit into your application, and which APIs and SDKs support each feature.

Explore Suki for Partners

Suki for Partners provides four primary clinical workflows, additional capabilities that extend those workflows, and shared services that support your integration. Start with the area that matches what you want to build:

• ACI capabilities: Explore the clinical AI and platform building blocks behind Suki for Partners.
• Clinical workflows: Integrate Ambient, Form filling, Dictation, and Patient Summary into your application.
• Ambient capabilities: Extend Ambient with note configuration, personalization, multilingual support, structured clinical data, medication orders, and more.
• E/M Coding: Recommend Evaluation and Management codes with Ambient or from an existing clinical note.
• Form filling and Dictation: Capture structured clinical information in forms or convert clinician speech into real-time text.
• Patient Summary: Generate clinical summaries from patient records stored in the Clinical Knowledge Graph.
• Interoperability: Share an ambient note across supported Suki products and workflows.
• Platform services: Integrate authentication, audio streaming, webhooks, provider preferences, and feedback.

ACI capabilities

Ambient Clinical Intelligence (ACI) is the clinical AI layer behind Suki for Partners. It brings together the capabilities needed to capture clinical conversations, generate documentation, recognize speech, process clinical information, and support downstream workflows. These capabilities work together across Suki’s clinical workflows. Depending on the integration, a workflow may use one or more ACI capabilities. Use the following cards to explore the main building blocks and jump to the documentation for the corresponding workflow or capability.

Feature availability

Suki for Partners provides different APIs and SDKs for integrating its clinical workflows and capabilities. The following table shows which products are available and their current release status. Use the feature tables in the sections below to see which products support individual capabilities.

Clinical workflows

Clinical workflows are the primary capabilities you integrate into your healthcare application. Each workflow addresses a different clinical documentation or information need. You can integrate these workflows independently or combine them to support different stages of a patient encounter.

Combining clinical workflows

You can combine multiple workflows to support a broader clinical experience. For example, your application can:

• Generate a Patient Summary before an appointment to give the clinician relevant patient history.
• Use Ambient during the visit to capture the conversation and generate the clinical note.
• Use Form filling to populate structured medical forms from the conversation.
• Use Dictation to capture additional text while the clinician reviews or edits the documentation.
• Request recommended E/M codes after the visit to support coding and revenue cycle workflows.

These workflows can be integrated independently. You do not need to implement all of them to use Suki for Partners. Refer to Available workflows for common workflow combinations.

Ambient capabilities

After integrating the Ambient workflow, you can use additional capabilities to control note generation, provide clinical context, and retrieve structured information from the encounter. These capabilities extend Ambient and support different clinical documentation, charting, and downstream workflows. For more information about recommending Evaluation and Management codes, see E/M Coding.

E/M Coding

E/M Coding recommends Evaluation and Management codes for a clinical visit. It supports revenue cycle management (RCM) workflows by providing coding recommendations after the clinical documentation is available. You can integrate E/M Coding in two ways, depending on where your clinical note comes from:

• With Ambient: Request E/M codes as part of an ambient session and retrieve them with the generated note.
• As a standalone capability: Submit an existing clinical note through the standalone E/M Coding APIs without creating an ambient session.

Choose the integration path that matches how your application creates or manages clinical notes.

E/M Coding with Ambient

Use this integration when your application generates the clinical note through an ambient session. Enable E/M Coding when you create the ambient session, provide the required patient, provider, and visit context, and retrieve the recommended codes with the generated note. Refer to Generate E/M codes with Ambient for more information.

Standalone E/M Coding

Use this integration when your application already has a completed clinical note and does not need an ambient session to generate it. Submit the note sections and optional context to the standalone E/M Coding APIs. Check the coding session status and retrieve the recommended codes when processing finishes. This path does not require an ambient session, Form filling, or Dictation. Refer to Explore the standalone E/M Coding APIs for more information.

Form filling

Form filling converts information from patient-provider conversations into structured medical form fields. Use Form filling when your application needs to capture specific clinical information in predefined forms or partner-defined fields rather than generate a complete clinical note. You can use Suki-defined medical form templates or provide your own field definitions through dynamic schemas. For implementation details, refer to Form filling overview.

Dictation

Dictation converts clinician speech into text in real time. Use Dictation when clinicians need to enter specific wording into chart fields, editors, or scratchpads. It can support text entry alongside Ambient and Form filling workflows. You can embed Dictation directly into an input or provide a floating panel that lets clinicians capture text and place it where needed. For implementation details, refer to Dictation overview.

Patient Summary

Patient Summary generates concise clinical summaries from patient records ingested into the Clinical Knowledge Graph (CKG). Use Patient Summary to give clinicians relevant patient history and encounter context before a visit. Your application can ingest FHIR R4 data and request summaries for scheduled appointments. For implementation details, refer to Patient Summary overview.

Interoperability

Interoperability lets supported Suki products that use Ambient work with the same clinical note for a patient visit. Use interoperability when your application needs to capture, continue, or review a note across multiple Suki products without creating separate notes for the same encounter. With interoperability, you can:

• Start a note in one supported product and continue it in another.
• Re-ambient an existing note.
• Review or retrieve the same note across supported products.
• Map encounter and note identifiers between product-specific fields.

Common workflow combinations include using Patient Summary before Ambient or Form filling, and using Dictation after Ambient or Form filling to capture exact wording during editing. Refer to Available workflows for more information.

Platform services

Platform services provide the shared functionality used across Suki for Partners integrations. They support authentication, audio streaming, workflow notifications, provider preferences, and feedback. For implementation guidance, refer to Partner authentication, Audio streaming, and Webhooks.

Choosing an integration

Suki for Partners supports API-based and SDK-based integrations. The right option depends on the workflow you are building and how much of the user experience you want to implement in your application.

• Use APIs when you want to manage the integration, application UI, and workflow behavior yourself.
• Use SDKs when you want to embed supported Suki functionality into your application.
• Use Headless Web SDK when you need the supported Ambient integration without the standard hosted interface.

Feature availability can differ between APIs and SDKs, so check the availability listed for each capability before choosing an integration. For guidance on selecting an integration, refer to Recommended integrations and Integration overview.