> ## Documentation Index
> Fetch the complete documentation index at: https://developer.suki.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# July 2026

> July 2026 release notes for Suki APIs and SDKs

This release adds **Interoperability across Suki products for ambient workflows** so you can continue the same clinical note across the Ambient APIs, Mobile SDK, Headless Web SDK, and Headed Web SDK. It also introduces the **Suki Form filling SDK (Beta)** for JavaScript and React, so you can embed Suki's Form filling experience in your web application without building the full Form filling API workflow yourself.

## What's new

<Update label="July 2026 - New" tag="LATEST" tags={["New Features"]}>
  ### New features

  <Badge icon="cube" size="sm" color="gray">Form Filling SDK v0.1.0</Badge>

  **Form filling SDK <Badge icon="sparkles" color="yellow" size="xs">Beta</Badge>**: We're introducing the **Suki Form filling SDK (Beta)** a
  JavaScript and React library that lets you embed Suki's Form filling experience directly in your web application, without building the complete Form filling API workflow yourself.
  It handles authentication, loads Suki's hosted Form filling interface, and returns structured form data when a clinician completes an assessment.

  **The Form filling SDK provides the following out of the box:**

  * JavaScript and React SDKs for embedding Form filling in your application.
  * Automatic authentication using **`SukiAuthManager`**.
  * Support for launching a **single form** directly or letting clinicians choose from **multiple forms**.
  * Session callbacks, including `onSubmit`, for receiving structured results in your application.
  * Support for partner webhooks to deliver results to your backend after processing completes.

  **Installation**

  Install **`@suki-sdk/core`** and the Form filling SDK package for your framework:

  <CodeGroup>
    ```shell JavaScript theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
    npm install @suki-sdk/core @suki-sdk/form-filling
    ```

    ```shell React theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
    npm install @suki-sdk/core @suki-sdk/form-filling-react
    ```
  </CodeGroup>

  **Configuration**

  Create a **`FormFillingClient`**, sign in with your partner credentials, and call **`start()`** with your **`form_template_ids`** and **`correlation_id`**.

  ```javascript JavaScript theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
  import { SukiAuthManager } from "@suki-sdk/core";
  import { FormFillingClient } from "@suki-sdk/form-filling";

  const authManager = new SukiAuthManager({
    partnerId: "YOUR_PARTNER_ID", // required
    partnerToken: "YOUR_PARTNER_TOKEN", // required
    environment: "staging",
    loginOnInitialize: true,
  });

  const client = new FormFillingClient({ authManager });

  await client.start({
    rootElement: document.getElementById("suki-form-container"),
    form_template_ids: ["YOUR_TEMPLATE_ID"],
    correlation_id: "YOUR_ENCOUNTER_ID",
    onSubmit: (result) => {
      console.log(result.structured_data.generated_values);
    },
  });
  ```

  <Tip>
    Give the container a fixed height before starting a session. Template IDs are different between staging and production environments. If you need a fully custom UI or server-side audio capture, use the [Form filling API](/form-filling-api-reference/overview) instead.
  </Tip>

  **Why it matters**: Ship voice-driven clinical form workflows inside your existing web app with less UI work, while still receiving structured JSON in the browser and on your server through callbacks and partner webhooks.

  Learn more in the [Form filling SDK introduction](/form-filling-sdk/introduction), [Quickstart](/form-filling-sdk/quickstart), and [API reference](/form-filling-sdk/api-reference/overview).

  ***

  <span id="ambient-interoperability-across-suki-products" />

  <Badge icon="code" size="sm" color="blue">API v1.6.0</Badge>

  **Ambient interoperability across Suki products**: You can now use **ambient interoperability** to continue the same clinical note across Suki ambient products, including the Ambient APIs, Mobile SDK, Headless Web SDK, and Headed Web SDK. Start an ambient session in one product and continue, re-ambient, or retrieve the same note from another.

  To enable ambient interoperability, include **`emr_encounter_id`** when creating an ambient session. The [Create ambient session](/api-reference/ambient-sessions/create) API now also returns a **`composition_id`**, which you use as the **`note_id`** for note-level Ambient APIs.

  **Use cases of ambient interoperability**

  * You can continue the same ambient note across the Ambient APIs, Mobile SDK, Headless Web SDK, and Headed Web SDK.
  * Access the latest accumulated note content, including edits made from headed products.
  * Retrieve aggregated note context and structured clinical data across multiple ambient sessions.
  * You can list all ambient notes associated with an EMR encounter.

  **New and updated APIs**

  * <Badge color="blue" size="sm">POST</Badge> [/api/v1/ambient/session/create](/api-reference/ambient-sessions/create): Create an ambient session with **`emr_encounter_id`** and receive **`composition_id`**.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/ambient/encounter/{emr_encounter_id}/notes](/api-reference/ambient-content/list-encounter-notes): List all notes associated with an EMR encounter.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/ambient/note/{note_id}/content](/api-reference/ambient-content/note-content): Retrieve accumulated note content.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/ambient/note/{note_id}/context](/api-reference/ambient-content/note-context): Retrieve aggregated note context.
  * <Badge color="green" size="sm">GET</Badge> [/api/v1/ambient/note/{note_id}/structured-data](/api-reference/ambient-content/note-structured-data): Retrieve aggregated diagnoses, orders, and other structured clinical data.

  **Why it matters**

  You can now build a single ambient integration that works across Suki products for the same clinical encounter. Users can seamlessly move between headed and headless experiences while continuing to work on the same clinical note.

  Learn more in [Ambient interoperability](/documentation/concepts/ambient-clinical-notes/ambient-interoperability), [How to use interoperability across Suki products](/documentation/how-to/ambient-clinical-notes/use-ambient-across-modalities).
</Update>

## What's enhanced

<Update label="July 2026 - Enhanced" tags={["Enhancements"]}>
  ### Enhancements

  <Badge icon="mobile" size="sm" color="purple">Mobile SDK v2.7.0</Badge>

  **Mobile SDK interoperability with other Suki products**: From Mobile SDK **v2.7.0**, the Mobile SDK supports ambient interoperability with Ambient APIs and the Web SDK. Pass `SukiAmbientConstant.kEmrEncounterId` and `SukiAmbientConstant.kSessionId` (Session Group ID / `encounter_id`) when you call `createSession` so the session shares one clinical note for the patient visit.

  You can now:

  * Resolve a remote session conflict with `cancelRemoteAmbientSession` or `endSessionRemotely`, then retry `createSession`.
  * Handle `SessionEvent.sessionTerminatedByPeer` when another Suki product ends the live session. Update the UI only. Do not call local `end()`, `cancel()`, or `clear()`.
  * List and read shared note content with `listEncounterNotes`, `getNoteContext`, `getNoteContent`, `getNoteStructuredData`, and `encounterContent`.

  **Why it matters**: Start ambient capture on iOS and continue, re-ambient, or retrieve the same clinical note from Ambient APIs or the Web SDK without building a separate note identity layer.

  Learn more in the [Mobile SDK interoperability](/mobile-sdk/ambient-guides/ambient-interoperability) guide, [Ambient interoperability](/documentation/concepts/ambient-clinical-notes/ambient-interoperability), and [How to use interoperability across Suki products](/documentation/how-to/ambient-clinical-notes/use-ambient-across-modalities).

  ***

  <Badge icon="cube" size="sm" color="green">Web SDK v3.2.0</Badge>

  **Web SDK interoperability with other Suki products**: From Web SDK **v3.2.0**, the Web SDK supports ambient interoperability with Ambient APIs, Mobile SDK, and Headless Web SDK. Pass a stable encounter identifier as `encounter.identifier` when you create the ambient session. That value maps to `emr_encounter_id` and lets the Web SDK share one clinical note for the patient visit.

  You can now:

  * Open a clinical note that started on Mobile SDK, Headless Web SDK, or Ambient APIs.
  * Review, edit, and submit the shared note in the headed Web SDK UI.
  * Start an ambient session in the Web SDK and continue or re-ambient it from another ambient product.

  Provide patient details on `encounter.patient` so the Web SDK can show the patient profile. If the note started on a headless product first, seed patient context before you open the Web SDK.

  **Why it matters**: Build one ambient workflow across headed and headless products for the same clinical encounter, and finish review and submit in the Web SDK without creating a separate note.

  Learn more in the [Web SDK interoperability](/web-sdk/guides/ambient-interoperability) guide, [Ambient interoperability](/documentation/concepts/ambient-clinical-notes/ambient-interoperability), and [How to use interoperability across Suki products](/documentation/how-to/ambient-clinical-notes/use-ambient-across-modalities).

  ***

  <Badge icon="cube" size="sm" color="green">Web SDK v3.2.0</Badge>

  **Form filling in the Web SDK**: From Web SDK **v3.2.0**, Form filling is included in **`@suki-sdk/js`** and **`@suki-sdk/react`**. If you already use the Web SDK, import **`FormFillingClient`** (and, in React, **`FormFillingProvider`**, **`FormFilling`**, and **`useFormFilling`**) from your Web SDK package. You do not need to install **`@suki-sdk/form-filling`** or **`@suki-sdk/form-filling-react`** separately. Use the standalone Form filling SDK packages only when you want Form filling without the rest of the Web SDK.

  **Why it matters**: Add hosted Form filling to an existing Web SDK app without a second package install or a full Form filling API integration.

  Learn more in the [Web SDK Form filling overview](/web-sdk/form-filling-overview), [JavaScript integration](/web-sdk/guides/form-filling-javascript), and [React integration](/web-sdk/guides/form-filling-react) guides.
</Update>