> ## 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.

# Suki Developer Platform Glossary

> Browse glossary terms by category, letter, and search. Use the category and letter filters to narrow the list

<div className="hp-wrap glossary-hp-wrap">
  <div className="sdk-overview-container">
    <h1 className="sdk-overview-main-title">Glossary</h1>

    <p className="sdk-overview-text">
      Welcome to the Suki Developer Platform Glossary. If you are new here and not sure what a term means? Search and filter below, or open A-Z letter pages under <strong>Documentation > Resources > Glossary</strong> to learn more about each term.
    </p>

    <div className="suki-glossary-hub" data-suki-glossary-root data-disable-read-time="true" data-applied-glossary-categories="" data-glossary-letter="all" role="region" aria-label="Suki glossary">
      <div data-suki-glossary-confusions className="suki-glossary-confusions-mdx">
        <Expandable title="Commonly confused terms">
          <ResponseField name="Ambient Session vs Encounter">
            An **Encounter** is the clinical visit context (patient, provider, appointment). An **ambient session** is one recording instance Suki uses to capture audio and generate a note for that visit.
          </ResponseField>

          <ResponseField name="Session ID (Web SDK) vs Encounter ID">
            **Session ID (Web SDK)** is the Web SDK **ambient session** identifier (`ambientId` / `activeAmbientId`). **Encounter ID** on the Web SDK **Note Submission** payload is your EHR visit identifier (maps to **EMR Encounter ID**). They are not interchangeable.
          </ResponseField>

          <ResponseField name="Session ID (Ambient APIs) vs Session ID (Web SDK)">
            **Session ID (Ambient APIs)** is `ambient_session_id` from Create ambient session, used for session-scoped Ambient API calls. **Session ID (Web SDK)** is `ambientId` / `activeAmbientId` in the Headed Web SDK. Both identify one ambient recording session in their own product.
          </ResponseField>

          <ResponseField name="Note ID (Ambient APIs) vs Note ID (Web SDK)">
            **Note ID (Ambient APIs)** is the interoperable note identifier: Create ambient session returns `composition_id`, and you pass that value as `note_id` to note-level Ambient APIs. **Note ID (Web SDK)** is `noteId` on Web SDK note submission payloads (`onNoteSubmit` / `note-submission:success`).
          </ResponseField>

          <ResponseField name="Encounter ID vs EMR Encounter ID">
            **Encounter ID** is the Ambient API `encounter_id` field used to group re-ambient sessions for the same note. **EMR Encounter ID** is your EMR or EHR visit identifier (`emr_encounter_id`) that makes notes interoperable across modalities. Do not treat them as the same field.
          </ResponseField>

          <ResponseField name="Partner Token vs Suki Token">
            Your identity provider issues the **Partner Token** (JWT). Suki login returns a **Suki Token** access token you use for REST and SDK calls.
          </ResponseField>

          <ResponseField name="Partner ID vs Provider ID">
            **Partner ID** identifies your organization in Suki. **Provider ID** identifies the clinician or user within that organization.
          </ResponseField>

          <ResponseField name="Form filling vs Form filling API">
            **Form filling** is the workflow that populates Medical form templates from conversation. The **Form filling API** is the REST product for programmatic Form filling sessions.
          </ResponseField>

          <ResponseField name="Form filling SDK vs Form filling API">
            The **Form filling SDK** embeds Form filling in the browser with a hosted iframe and SDK callbacks. The **Form filling API** is the REST and WebSocket product when you build the full workflow in your own code.
          </ResponseField>

          <ResponseField name="Form filling Session vs Ambient Session">
            Both APIs may return a session ID as `ambient_session_id`, but a **Form filling Session** belongs to the **Form filling API**. An **ambient session** belongs to the Ambient API for clinical note generation.
          </ResponseField>

          <ResponseField name="Form filling Session Context vs Session Context">
            **Form filling Session Context** seeds patient, provider, and **Medical form template** data for a **Form filling Session**. **Session Context** is metadata for an **ambient session** that guides note generation.
          </ResponseField>

          <ResponseField name="Patient Summary vs Ambient Session">
            **Patient Summary** prepares clinicians with chart context before a visit using FHIR data in **CKG**. An **ambient session** captures conversation during the visit to generate a clinical note.
          </ResponseField>

          <ResponseField name="Full Summary vs Pre-Visit Summary">
            A **Full Summary** is the complete Patient Summary object for chart review. A **Pre-Visit Summary** is the schedule-preview section of that same summary for UI display before the appointment.
          </ResponseField>

          <ResponseField name="Transcription Session vs Ambient Session">
            A **Transcription Session** captures speech-to-text for Dictation. An **ambient session** captures conversation for full clinical note generation with LOINC sections.
          </ResponseField>

          <ResponseField name="Headed SDK vs Headless SDK">
            The **Headed SDK** (Web SDK) ships pre-built UI components such as **Note Editor** and **Note Archive**. The **Headless SDK** exposes hooks and types so you build your own UI.
          </ResponseField>

          <ResponseField name="Dictation vs Ambient Session">
            **Dictation** is voice-to-text capture, often through the Dictation SDK. An **ambient session** runs the broader ambient workflow that produces structured clinical notes.
          </ResponseField>

          <ResponseField name="Ambient API vs Form filling API">
            The **Ambient API** creates clinical notes from conversations. The **Form filling API** fills Suki **Medical form template** schemas with structured form output.
          </ResponseField>

          <ResponseField name="Structured Data vs Clinical Note">
            A **Clinical Note** is narrative documentation organized into LOINC sections. **Structured Data** is extracted, field-level information (diagnoses, medications, vitals) formatted for EHR integration.
          </ResponseField>
        </Expandable>
      </div>

      <div data-suki-glossary-mount aria-live="polite" />
    </div>
  </div>
</div>