> ## 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. # Note Sections (LOINC Codes) > LOINC standardized clinical note sections supported by Suki for EHR integration **Updated** Added Medication orders (LOINC **`52471-0`**) as a supported note section to enable Medication orders in the note generation process for the Headed Web SDK.

Note sections divide clinical notes into standard parts such as "Chief Complaint," "Physical Exam," and "Assessment and Plan." Suki uses LOINC codes to identify each section, which ensures seamless integration with your EHR system.

**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 LOINC 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. | What you configure | How the note gets better | | ------------------------------------- | ------------------------------------------------------------------- | | The LOINC sections for the visit | Conversation content is sorted into the sections your chart expects | | Only the sections your workflow needs | Notes stay focused and easier to review | | Standard LOINC identifiers | Your app can map sections into EHR fields without custom renaming | 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 ambient session, 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. ```mermaid actions={false} theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}} %%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#FFE148','primaryTextColor':'#111827','primaryBorderColor':'#FFE148','lineColor':'#FFE148','secondaryColor':'#FFF394','tertiaryColor':'#FFFADE','mainBkg':'#FFF394','secondBkg':'#FFFADE','tertiaryBorderColor':'#FFE148','border1':'#FFE148','border2':'#FFE148','arrowheadColor':'#FFE148','fontFamily':'Inter, system-ui, sans-serif','fontSize':'14px','nodeBorder':'#FFE148','edgeLabelBackground':'#FFE148','clusterBkg':'#FFFADE','clusterBorder':'#FFE148','defaultLinkColor':'#FFE148','titleColor':'#111827','nodeTextColor':'#111827'}}}%% flowchart LR A[Start Session
with LOINC Codes] --> B[Suki Listens
to Conversation] B --> C[Suki Organizes Content
into Specified Sections] C --> D[Generated Note
with LOINC Codes] style A fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#111827 style B fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#111827 style C fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#111827 style D fill:#FFF394,stroke:#FFE148,stroke-width:2px,color:#111827 ``` **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. ## Supported Note sections Use this table to configure 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. 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 this list. You do not need every section for every visit. Match the list to your note template and specialty workflow. If you pass a code that is not in this table, that section will not be generated. Keep your configuration aligned with the codes below. | SR No. | LOINC CODE | Section Common Name | | ------ | ---------- | -------------------------- | | 1 | 39238-1 | Anticipatory Guidance | | 2 | 42348-3 | Advanced Directives | | 3 | 48765-2 | Allergies | | 4 | 51848-0 | Assessment | | 5 | 51847-2 | Assessment and Plan | | 6 | 10154-3 | Chief Complaint | | 7 | 61144-2 | Diet | | 8 | 55128-3 | Disposition | | 9 | 46239-0 | Discussion Notes | | 10 | 10157-6 | Family History | | 11 | 47420-5 | Functional Status | | 12 | 8648-8 | Hospital Course | | 13 | 10164-2 | History of Present Illness | | 14 | 11369-6 | Immunizations | | 15 | 61150-9 | Interval History | | 16 | 10160-0 | Medications | | 17 | 10190-7 | Mental Status Exam | | 18 | 11348-0 | Past Medical History | | 19 | 11358-9 | Past Psychiatric History | | 20 | 10167-5 | Past Surgical History | | 21 | 69730-0 | Patient Instructions | | 22 | 29545-1 | Physical Exam | | 23 | 18776-5 | Plan | | 24 | 11450-4 | Problem List | | 25 | 47519-4 | Procedure | | 26 | 56822-0 | Response to Therapy | | 27 | 30954-2 | Results | | 28 | 78486-8 | Risk Assessment | | 29 | 10187-3 | Review of Systems | | 30 | 29299-5 | Reason for Visit | | 31 | 29762-2 | Social History | | 32 | 75325-1 | Symptoms and Stressors | | 33 | 61146-7 | Therapy Goals | | 34 | 8716-3 | Vitals | | 35 | 11334-0 | Development History | | 36 | 52471-0 | Medication Orders | ## Choosing your sections Select sections that match your clinical workflow and EHR requirements. Here are some common configurations: | Configuration | Description | | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------- | | **Basic SOAP Note** | Chief Complaint (10154-3), History of Present Illness (10164-2), Physical Exam (29545-1), and Assessment and Plan (51847-2) | | **Comprehensive Visit** | Add Medications (10160-0), Allergies (48765-2), Problem List (11450-4), and Review of Systems (10187-3) | | **Specialty-Specific** | Choose sections relevant to your specialty (e.g., Mental Status Exam (10190-7) for psychiatry, Vitals (8716-3) for primary care) | Start with a few essential sections and add more as needed. Adjust your configuration anytime based on what works best for your workflow. ## How to use Note sections in your application In every integration path, the workflow is the same: choose the LOINC sections your clinical note needs, pass them with the ambient session, complete capture, then map the returned sections into your EHR. The API or SDK implementation changes by product. Click the tabs below to see the implementation details for your integration path. Pass LOINC codes in the [Context API](/api-reference/ambient-sessions/context) body, then read section content from the content APIs after generation. 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 session with the ambient sessions API. Keep the `ambient_session_id` for context and content calls. POST (or PATCH) context and include a `sections` array of `{ "loinc": "

" }` objects.

        ```python Python theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
        payload = {
            "sections": [
                {"loinc": "10154-3"},  # Chief Complaint
                {"loinc": "10164-2"},  # History of Present Illness
                {"loinc": "29545-1"},  # Physical Exam
                {"loinc": "51847-2"},  # Assessment and Plan
            ],
            # Include patient, provider, and visit fields as needed
        }
        ```

        Use [Seed ambient session Context](/api-reference/ambient-sessions/context) when you have the complete context. Use [Update ambient session Context](/api-reference/ambient-sessions/update-context) to change only selected fields. Send either request before you end the session.



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

      
        After ending the session, poll [Ambient session status](/api-reference/ambient-content/status) until it returns `completed`. Then retrieve [Ambient session content](/api-reference/ambient-content/content) and map each item in `summary` by `loinc_code` into your EHR fields.



  
    Configure sections in `ambientOptions.sections` when you mount the SDK. The headed UI captures audio; your app receives sectioned note content on submit.

    
      
        Select the LOINC codes your EHR template expects. For Problem-Based Charting, mark exactly one section with `isPBNSection: true`. Refer to [Problem-Based Charting](/api-reference/capabilities/problem-based-charting).
      

      
        When you call `mount`, set `ambientOptions.sections` to the LOINC list.

        ```javascript JavaScript theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
        sdkClient.mount({
          rootElement: document.getElementById("suki-root"),
          encounter: encounterDetails,
          ambientOptions: {
            sections: [
              { loinc: "10154-3" }, // Chief Complaint
              { loinc: "10164-2" }, // History of Present Illness
              { loinc: "29545-1" }, // Physical Exam
              { loinc: "51847-2" }, // Assessment and Plan
            ],
          },
        });
        ```

        Refer to [Ambient implementation](/web-sdk/guides/ambient-implementation) for full mount options.
      

      
        Providers capture and submit the session in the Web SDK. Suki generates the note using the sections you configured.
      

      
        Handle `onNoteSubmit` (React) or `note-submission:success` (JavaScript and React). Each section includes content and a `loinc_code` you can map into the chart. Refer to [Note management](/web-sdk/guides/note-management).
      
    
  

  
    Pass LOINC sections with `SukiAmbientConstant.kSections` in `setSessionContext` after you create the session.

    
      
        Select the LOINC codes that match your mobile charting workflow. You only need to provide codes; the SDK resolves section titles.
      

      
        Call `createSession(withSessionInfo:)` and store the returned `sessionId`. Refer to [Create session](/mobile-sdk/ambient-guides/create-session).
      

      
        Call `setSessionContext(with:)` and include `kSections` as an array of code dictionaries.

        ```swift Swift theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
        let contextDetail: [String: AnyHashable] = [
            SukiAmbientConstant.kSections: [
                [SukiAmbientConstant.kCode: "10154-3", SukiAmbientConstant.kCodeType: "loinc"],
                [SukiAmbientConstant.kCode: "10164-2", SukiAmbientConstant.kCodeType: "loinc"],
                [SukiAmbientConstant.kCode: "29545-1", SukiAmbientConstant.kCodeType: "loinc"],
                [SukiAmbientConstant.kCode: "51847-2", SukiAmbientConstant.kCodeType: "loinc"]
            ],
            // Add patient, visit, diagnosis, or orders context as needed
        ]

        do {
            try SukiAmbientCoreManager.shared.setSessionContext(with: contextDetail) { result in
                switch result {
                case .success:
                    print("Note sections updated")
                case .failure(let error):
                    print("Unable to update note sections: \(error)")
                }
            }
        } catch {
            print("Unable to set session context: \(error)")
        }
        ```

        Refer to [Provide clinical context](/mobile-sdk/ambient-guides/provide-clinical-context#additional-context-parameters) for field names and types.
      

      
        Start recording, capture the visit, then call `end()` to stop recording and trigger note generation.
      

      
        Check processing with `status(for:)`. When processing completes, call `content(for:)` with the valid `sessionId` to retrieve the generated clinical note suggestions. Refer to [Session status and content retrieval](/mobile-sdk/ambient-guides/session-status-and-content-retrieval).
      
    
  

  
    Create the session with ambient hooks, then pass LOINC sections through `setSessionContext` on `useAmbientSession` before you submit.

    
      
        Pick the LOINC codes your custom UI and EHR template need. Keep the list small for pilots, then expand as workflows stabilize.
      

      
        Use `useAmbient` to create the session, then `useAmbientSession` with the returned `ambientSessionId`. Call `start()` when recording begins. Refer to [Ambient session hook](/headless-web-sdk/guides/hooks/ambient-session-hook).
      

      
        Call `setSessionContext` after `start()` and before `submit()`. Include `sections` as `{ loinc: string }[]`.

        ```tsx React theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
        await setSessionContext({
          sections: [
            { loinc: "10154-3" }, // Chief Complaint
            { loinc: "10164-2" }, // History of Present Illness
            { loinc: "29545-1" }, // Physical Exam
            { loinc: "51847-2" }, // Assessment and Plan
          ],
          // Optional: patient, provider, visit, diagnoses
        });
        ```

        Refer to [Session context](/headless-web-sdk/api-reference/types/session-context) for the full type.
      

      
        Call `submit()` when capture is done. Your app owns the recording UX; the Headless Web SDK owns upload and session lifecycle.
      

      
        The Headless Web SDK hooks submit the session, but they do not return generated note content. From your backend, use the same `ambientSessionId` with [Ambient session status](/api-reference/ambient-content/status). When the status is `completed`, call [Ambient session content](/api-reference/ambient-content/content) and map items in `summary` by `loinc_code`. For pause and submit patterns, refer to [Session integration patterns](/headless-web-sdk/guides/integration-patterns).



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.