> ## 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.
# Ambient Documentation Overview
> Start here for Ambient documentation: when to use visit capture and note generation, how Ambient differs from Form filling and Dictation, and where to go next
Ambient documentation lets providers turn a patient-provider conversation during an encounter into a structured clinical note. Your application captures visit audio, and Suki transcribes and organizes what was said into LOINC-coded note sections. Your application can then review, edit, and submit the note to your EHR or use it in downstream workflows.
[Choose an SDK or API](/documentation/get-started/integration-decision-guide) to build your workflow, then build the minimum path with the [Quickstart guides](/documentation/get-started/quick-start). Add session context, interoperability, and webhooks after that works.
These definitions come from the opening copy on this page.
| Term | Meaning |
| :- | :- |
| Ambient clinical notes | Turns the visit conversation into a structured clinical note with LOINC-coded sections. |
| Ambient session | A single recording instance for a patient encounter. One encounter can include one or more sessions. |
| Form filling | Maps visit conversation into field values on medical forms, not a full clinical note. |
| Audio Dictation | Converts provider speech into text for a field or UI target while a session is active. |
## When to use Ambient documentation
Use Ambient documentation when you need:
* Structured clinical notes from patient-provider conversation without typing the note during the encounter.
* LOINC-coded sections, optional structured data, and transcript content you control in your application. Capture and review across Ambient APIs, Web SDK, Mobile SDK, or Headless Web SDK, including shared notes across modalities.
## Developer workflow
The Ambient developer workflow is shared by Ambient APIs, Web SDK, Mobile SDK, and Headless Web SDK. The only difference is who owns each step.
```mermaid actions={false} theme={"theme":{"light":"one-light","dark":"material-theme-darker"}}
flowchart LR
A[Start Ambient
session for the visit] --> B[Stream visit
audio to Suki]
B --> C[End session and
generate note]
C --> D[Retrieve structured
clinical note]
D --> E[Provider reviews
and edits]
E --> F[Approve or submit
to EHR]
style A fill:#FFF394,stroke:#333,color:#000
style B fill:#FFF394,stroke:#333,color:#000
style C fill:#FFF394,stroke:#333,color:#000
style D fill:#FFF394,stroke:#333,color:#000
style E fill:#FFF394,stroke:#333,color:#000
style F fill:#FFF394,stroke:#333,color:#000
```
Start an ambient session for the visit. Provide patient details, note sections, and provider information. Suki returns a session ID. With Web SDK or Headless Web SDK, start through the SDK controls or hooks.
Stream audio while the visit runs. Ambient APIs stream over WebSocket on `/ws/stream`. Web SDK, Mobile SDK, and Headless Web SDK handle capture for you.
End the ambient session when that recording finishes. Suki analyzes the transcript, extracts clinical content, and organizes it into the sections you requested.
Retrieve the note with LOINC-coded sections, optional structured data, and the transcript when you need it. Let the provider review, edit, and submit into the EHR workflow.
The steps above stay the same across the offered modalities what changes is how much you build yourself and how much Suki builds for you. With Ambient APIs, your application creates the session, streams audio, and handles content retrieval and you manage the UI. With Web SDK, Suki provides more of the capture and review UI and you manage less. Does not matter which modality you use, your application still decides where the approved note lands and how you write it back.
If you are designing the full clinician workflow, note strategy, and EHR handoff, refer to the [Ambient documentation guide](/documentation/concepts/ambient-clinical-notes/ambient-documentation) to learn more about the workflow and how to implement it.
## Related guides
Workflow decisions, capture strategy, note quality settings, and EHR handoff.
Continue the same clinical note across Ambient APIs, Web SDK, and Mobile SDK.
Start Ambient and store session and note IDs for your product UI.
Stream visit audio on `/ws/stream` for Ambient API integrations.
## Resources
Refer to these guides when you are ready to integrate:
Orient to Ambient and Dictation Partner APIs, auth, and core resources.
Create a session, stream audio, and retrieve ambient content end to end.
Browser capture and review UI from Suki for Ambient documentation.
Custom React UI with ambient hooks for session and recording control.
## Next steps
**[Ambient documentation](/documentation/concepts/ambient-clinical-notes/ambient-documentation)** - Workflow decisions, capture path, and EHR handoff.
**[Create an ambient session](/documentation/how-to/ambient-clinical-notes/create-ambient-session)** - Start Ambient and store session and note IDs.
**[Ambient API quickstart](/api-reference/quickstart)** - Authenticate, create a session, stream audio, and retrieve the note.
**[Integration decision guide](/documentation/get-started/integration-decision-guide)** - Choose Ambient APIs, Web SDK, Mobile SDK, or Headless Web SDK.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.