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.

​

Release Notes (Suki Documentation)

​

Page location and naming

• Path: updates/{month}{year}-release-notes.mdx (e.g. mar2026-release-notes.mdx)
• Frontmatter: title (e.g. “March 2026”), description, sidebarTitle, rss: true

​

Page structure

1. Lead paragraph (no heading): One short summary of the release.
2. Sections (use as needed):
   • ## What's new — new features
   • ## What's enhanced — enhancements
   • ## What's changed — deprecations or behavior changes
   • ## What's removed — removed APIs or options
3. Anchor before each <Update>: <span id="kebab-case-anchor" /> for deep links.
4. Update blocks: One <Update> per logical change. Use tag="LATEST" only on the single newest update.

​

Per-item format (inside each <Update>)

<Badge size="sm" color="...">Product Version</Badge>

**Feature or change title**: Short paragraph describing what changed and how to use it.

**Why it matters**: One line explaining the benefit to the developer or user.

Learn more in the [Link text](../documentation/overview) documentation.

​

Badge

• API: <Badge size="sm" color="blue">API v1.x.x</Badge>
• Web SDK: <Badge size="sm" color="green">Web SDK 2.x.x</Badge>
• Headless Web SDK: <Badge size="sm" color="orange">Headless Web SDK 0.x.x</Badge>

​

Section heading inside <Update>

​

Link

• Use a relative path from updates/ (e.g. ../web-sdk/guides/ambient-problem-based-charting#existing-patient-diagnoses).
• Prefer a closing line with a markdown link whose target is relative to updates/ (for example ../web-sdk/guides/...), ending with “documentation.” or ”… guide.”

​

Style

• No em dashes; use commas or colons.
• Professional, developer-focused tone.
• One change per badge + bold title + body + “Why it matters” + link.

​

Example (single enhancement item)

<Badge size="sm" color="green">Web SDK 2.1.2</Badge>

**Existing patient diagnoses for Problem-Based Charting**: You can now pass the patient's existing diagnoses (e.g. from the EMR) into an ambient session using the `diagnoses` block in `ambientOptions`. The session merges them with what's discussed during the visit so you avoid duplicate problems in the note. Use this when you have at least one PBC section (`isPBNSection: true`); each diagnosis needs one **ICD10** code.

**Why it matters**: Seed the problem list from the EMR and get one merged note without duplicates when the provider or patient discusses those problems.

Learn more in the [Existing patient diagnoses](../web-sdk/guides/ambient-problem-based-charting#existing-patient-diagnoses) guide.

​

Reference

• Full release-note format and LATEST badge rule: AGENTS.md → “Release Notes” and “Release Note Page Format”.