Building ambient AI across multiple surfaces: A developer guide

Healthcare applications are built on many surfaces: web portals, mobile apps, back-end services, and clinicians move between them all day. Adding Ambient Clinical Intelligence (ACI) to an application shouldn't force developers into a single integration path, or force clinicians into a single device.

At Suki, our mission is to make healthcare technology invisible and assistive, so clinicians can focus on what truly matters: patient care. Suki's Platform extends that mission to developers: with it, you can power your application with ACI Skills across ambient documentation, form filling, RCM, clinical operations, and clinical reasoning, using the surfaces that fit your product, not the other way around.

Headless, Headed, or Both

The Platform offers two ways to build, and most partners end up using a combination of both.

Headless products: Our APIs, Web SDK, and Mobile SDK are for teams building custom UI/UX workflows. Use the APIs when you want to build the system yourself, including audio capture. Use the SDKs when you want prebuilt audio capture and offline support out of the box, while keeping full control of the experience your users see.

Headed products: Leverage Suki's design directly, or themed in your company's colors. With the Headed WebSDK, you implement modular widgets in your application to build Ambient, Dictation, and Form Filling use cases, producing production-ready workflows without designing them from scratch.

Because these products are modular and interconnected, they work in sync. Partners often implement a hybrid approach across their hardware, headed widgets on the web, headless SDKs on mobile, and APIs on their servers, with every surface interconnected and producing the same consistent data.

A Visit That Moves With the Provider

Here's what this looks like in practice.

A provider starts a session on their desktop, where they see a pre-visit summary and record a monologue for the patient they're about to see. They then walk into the exam room with their mobile phone and continue the same session, ambiently capturing the conversation with the patient, staying present and focused on the patient instead of a screen.

When the visit ends, the ambient artifacts are available on web or mobile, per your implementation. Our webhook notifies your server the moment those artifacts are ready, so they can also be stored for compliance purposes, including the audio and transcript.

One session, three surfaces, no seams. That is the interconnected part of the Platform: the same session, the same data shapes, and the same skills, whether you reach them through an API, an SDK, or a widget.

Up and Running in Hours

All of this can be stood up in a few hours with your coding agent of choice. Our documentation ships with MCP support built in, so agents like Claude Code or Cursor can read the docs, scaffold the integration, and get you to a working ambient session the same day you start.

If you're interested in building with Suki's ACI Platform, reach out to our team, we'd love to see what you build.