> ## 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 to Suki developer platform 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 vs Encounter ID">
            **Session ID** is the Web SDK **Ambient Session** identifier (`ambientId` / `activeAmbientId`). **Encounter ID** is your EHR visit identifier on the **Note Submission** payload. They are not interchangeable.
          </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 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="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>