Skip to main content
UpdatedAdded Medication orders (LOINC 52471-0) as a supported note section to enable Medication orders in the note generation process for the Headed Web SDK.
Quick summary
Note sections divide into standard parts such as “Chief Complaint,” “Physical Exam,” and “Assessment and Plan.” Suki uses codes to identify each section, which ensures seamless integration with your EHR system.
Last updated:August 2026
Note sections is supported by: APIs, Web SDK, Mobile SDK, Headless Web SDK
Note sections divide clinical notes into standard parts such as “Chief Complaint,” “Physical Exam,” and “Assessment and Plan.” This organized structure make clinical notes easier to read and ensures seamless integration with your EHR system. Suki uses codes to identify each section. Because LOINC is widely adopted in healthcare, notes labeled this way map consistently across EHR systems and partner applications. When you specify the note sections, you get the following benefits:
  • Better organization: Content is automatically sorted into the right sections.
  • EHR ready: Notes match the format your EHR expects.
  • Industry standard: LOINC codes are recognized across healthcare systems.
  • Customizable: Choose only the sections you need for your workflow.

​
How note sections improve clinical documentation

Note sections help Suki produce documentation that clinicians can review and submit with less restructuring. Without note sections, generated content is harder to place in the chart. With the right LOINC set, providers spend less time moving text between sections and more time confirming clinical accuracy.

​
How note sections work

When you start an , you specify which sections you want in your note by providing their LOINC codes. Suki listens to the conversation and automatically organizes what’s discussed into those sections. Example: If you specify “Chief Complaint” (10154-3), “History of Present Illness” (10164-2), and “Physical Exam” (29545-1), Suki will:
  • Put information about why the patient is visiting into the Chief Complaint section.
  • Organize the patient’s story into the History of Present Illness section.
  • Capture exam findings into the Physical Exam section.
The generated note includes each section with its LOINC code, making it easy to map directly to your EHR’s structure.

​
SOAP vs a clinical note

A clinical note is the document Suki generates for the visit. A SOAP note is one way that document can be structured. SOAP is not a separate Suki product. When you use ambient note generation, Suki always returns a clinical note. You choose the layout by passing LOINC-coded sections from below. SOAP is a common template for that note.
If you are using Problem-Based Charting (PBC) instead of SOAP, the note is organized around problems instead of SOAP template headings.

​
Supported note sections

Use this table to configure more options in your product UI for ambient note generation. Each row is a clinical section Suki supports out of the box. You request a section by its LOINC code, not by free-text title. This table is for reading and first-time setup. For pickers and validation at runtime, call GET /api/v1/info/loincs. If this table and the Info API disagree, use the Info API. What that means in practice:
  • LOINC code is the stable identifier you send in session context or SDK options (for example 10154-3 for Chief Complaint).
  • Section common name is the clinical label partners and EHRs usually recognize. Suki uses the LOINC you pass to place conversation content into that section.
  • You can request any combination from the list below. You do not need every section for every visit. Match the list to your note template and specialty workflow.
If you pass a LOINC code that is not in the the list below, that section will not be generated in your clinical note. It is your responsibility to keep your configuration aligned with these supported codes.
We update this table as we add new sections to the ambient note generation process. If you do not see a section you need, please check back later.

​
Choosing your sections

Select sections that match your clinical workflow and EHR requirements. Here are some common configurations:
Start with a few essential sections and add more as needed. Adjust your note section configuration anytime based on what works best for your workflow.

​
Build note sections into your product

If your product supports note sections, understand how they fit into the Ambient workflow before you add them to your UI. Pass LOINC-coded note sections when you create the ambient session. Suki uses these sections to structure the generated clinical note around the content your chart expects. The workflow is:
  1. Choose the note sections your product needs.
  2. Pass the LOINC codes when you create the ambient session.
  3. Complete the recording and end the session.
  4. Retrieve the generated note and its sections.
  5. Map the returned sections to the appropriate fields in your EHR.
The API and SDK implementation varies by product, but the workflow remains the same. How you pass note sections depends on the product you use:
  • Ambient APIs: Send sections as { "loinc": "…" } in Seed ambient session Context or Update ambient session Context before End.
  • Web SDK: Pass LOINC codes in ambientOptions.sections when you mount.
  • Mobile SDK: Pass LOINC sections with SukiAmbientConstant.kSections in setSessionContext after you create the session.
  • Headless Web SDK: Pass sections through Headless ambient / session hooks and context APIs (see the Headless tab below).
When you build note sections well, clinicians can:
  • See a note layout that matches what Suki will generate.
  • Review and edit by section after the visit.
  • Use section-level editing on a focused section after the note is ready. You can use Dictation APIs for final edits.
If you pass a LOINC code that is not supported, that section will not be generated. Use GET /api/v1/info/loincs to confirm which codes are valid before you send context.

​
Configure note sections

Use these product paths to pass note sections. To populate or validate LOINC pickers from live catalogs, refer to Use Ambient Info APIs in your product guide for recommendations. Recommended defaults for a first integration: Chief Complaint (10154-3), History of Present Illness (10164-2), Physical Exam (29545-1), and Assessment and Plan (51847-2). Start small, then add specialty sections from the tables above. Build the note template and review experience in your product. Suki generates the clinical note based on the LOINC-coded sections you provide, while your app controls how those sections are presented in the chart. Help users choose the right sections for each workflow. For example, provide guidance on when to add additional sections and avoid asking users to select sections they do not need.
These patterns apply when you build your own ambient experience with the Ambient APIs or the Headless modalities. The headed Web SDK already provides Ambient UI, so you do not recreate these patterns there.
Before the visit Let the clinician (or your specialty defaults) choose which sections this visit needs. Use a note template, section picker, provider defaults, or specialty-specific sets. Send the chosen LOINCs in session context before End. During Ambient Run create, context, stream, and End as usual. Do not invent section text while the visit is still in progress. Wait for generation to finish. After the visit When status is completed, load content and map each item in summary[] by loinc_code. Show your EHR section title in the UI. Keep LOINC as the stable join key for save, sign, and optional section Speak.
Start with essential sections, then add specialty-specific ones. Use the supported note sections table and the common configurations above.You do not need every section for every visit. Match the list to your note template and specialty workflow.
Provider defaults, specialty templates, or a per-visit picker all work.Send the chosen LOINCs in session context before End. You can update sections with PATCH context while the session is still open, before End.
After generation, map summary[] by loinc_code. Show your EHR title in the UI. Keep LOINC as the stable key for write-back and later Dictation focus.
If Ambient generates no content for a requested LOINC, the response depends on which content API you call.
  • Session content skips empty sections. Encounter content still lists them, even when the body is blank.
  • Keep every requested LOINC in your template map either way. That lets the clinician still open that section later to type, edit, or dictate into it.
No. Ambient generates the structured note for the LOINCs you configured. Section Speak is Dictation on a focused field in your UI after status is completed.Bind focus to a LOINC or field id yourself. Dictation APIs do not take a LOINC target. See Dictation basic usage.

​
LOINC codes, display titles, and the join key

When you build note sections into your app, keep the following concepts separate. They look related, but serve different purposes. What to wire in your product
  1. Build a note template / section picker (or specialty defaults) using supported LOINCs.
  2. Pass those LOINCs with the ambient session before End, using the product path above.
  3. After completed, map content by loinc_code, show your EHR titles, and write back with the same map. Optionally add section Speak on a focused field.
Start with a small SOAP set, then add specialty sections as your workflow needs them. Adjust the configuration anytime based on what works best for your chart.
Do not pass unsupported LOINC codes, and do not invent Ambient text for empty sections. Send sections before End, then join on loinc_code.
Click the tabs below to see the implementation details for your integration path.
Pass LOINC codes in the Context API body, then read section content from the content APIs after generation.

Choose LOINC Sections

Pick the section codes that match your note template. Start with a small set such as Chief Complaint (10154-3), History of Present Illness (10164-2), Physical Exam (29545-1), and Assessment and Plan (51847-2).

Create the Ambient Session

Create the session with the ambient sessions API. Keep the ambient_session_id for context and content calls.

Send Sections in Session Context

POST (or PATCH) context and include a sections array of { "loinc": "<code>" } objects.
Python
Use Seed ambient session Context when you have the complete context. Use Update ambient session Context to change only selected fields. Send either request before you end the session.

Stream Audio and Complete the Session

Stream visit audio, then complete the ambient session so Suki can generate the note for the sections you configured.

Read Generated Sections

After ending the session, poll Ambient session status until it returns completed. Then retrieve Ambient session content and map each item in summary by loinc_code into your EHR fields.
After generation, each section typically includes:
  • Section name: Readable title (for example, “Chief Complaint”).
  • Content: Text extracted from the conversation for that section.
  • LOINC code: Standard identifier your integration uses for EHR mapping.
Use those LOINC codes as the stable keys when you write content into your note template.
Last modified on August 20, 2026