### New endpoints * **Note-level ambient endpoints**: You can now retrieve accumulated content, context, and structured data for a note across ambient sessions while using the interopertability feature. Use `composition_id` from [Create ambient session](/api-reference/ambient-sessions/create) as `note_id`. * GET [/api/v1/ambient/note/{note_id}/content](/api-reference/ambient-content/note-content) * GET [/api/v1/ambient/note/{note_id}/context](/api-reference/ambient-content/note-context) * GET [/api/v1/ambient/note/{note_id}/structured-data](/api-reference/ambient-content/note-structured-data) * **List encounter notes**: You can now list all notes linked to an EMR encounter for cross-modality ambient workflows. * GET [/api/v1/ambient/encounter/{emr_encounter_id}/notes](/api-reference/ambient-content/list-encounter-notes) ### Enhancements * **Create ambient session**: You can now pass `emr_encounter_id` to enable cross-modality ambient interoperability. The response now includes `composition_id`, which you use as `note_id` with the note-level ambient endpoints. The `multilingual` parameter is deprecated. Multilingual support is enabled by default for all ambient sessions. * POST [/api/v1/ambient/session/create](/api-reference/ambient-sessions/create) Learn more in the [How to use ambient across modalities](/documentation/how-to/ambient-clinical-notes/use-ambient-across-modalities) documentation. ### Enhancements * **HCC codes**: You now get [HCC codes](https://www.aapc.com/resources/what-is-hierarchical-condition-category?srsltid=AfmBOopcl-dIWrRrQFq58LGS72p58BakTdoWdEHv0P9z89c3XBXuJAOY) in the **Structured data API** and **Encounter structured data API** output for an ambient session and encounter. * GET [/api/v1/ambient/session/{ambient_session_id}/structured-data](/api-reference/ambient-content/structured-data) * GET [/api/v1/ambient/encounter/{encounter_id}/structured-data](/api-reference/ambient-content/encounter-structured-data) * Use HCC codes in the structured data output to validate the diagnosis codes in the EMR context. ```json JSON theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}} { "structured_data": { "diagnoses": { "values": [ { "codes": [ { "code": "A00.0", "description": "Acute myocardial infarction", "type": "ICD10" }, { "code": "R05.2", "description": "Hypertension, unspecified", "type": "ICD10" }, { "code": "65", "description": "CMS-HCC model category 65", // HCC code in the format `CMS-HCC model category

`
                                  "type": "HCC"
                              }
                          ]
                      }
                  ]
              }
          }
      }
      ```

      
        If an ICD-10-CM HCC diagnosis code does not map to an HCC model category, Suki looks for general HCC codes that match the diagnosis description. If no match is found, the diagnosis is returned without an HCC code.



    
      ### Enhancements

      * Suki now supports **Single Auth Token authentication**: your backend can use one shared `partner_token` for all clinicians instead of a per-user token.
        The shared token proves your organization is authorized, but it does not identify who is signed in. If you use this model, you **must** send `sdp_provider_id`
        on every API call so Suki can route each call to the correct clinician.

      Learn more in the [Provider authentication](/api-reference/provider-authentication) documentation.

      ```json JSON theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
      {
          "sdp_suki_token": "your-suki-token", // sdp_suki_token required for all API calls
          // Required with Single Auth Token auth: send sdp_provider_id on Register, Login, and every API call
          "sdp_provider_id": "doc1234567890"
      }
      ```
    

    
      ### New endpoints

      * **Info endpoints**: Added new endpoints to get the list of supported medication coding systems, dosage units, encounter relations, frequencies, medication timings, origins, and statuses.

        * GET [/api/v1/info/orders/coding-systems](/api-reference/info/orders-coding-systems)
        * GET [/api/v1/info/orders/dosage-units](/api-reference/info/orders-dosage-units)
        * GET [/api/v1/info/orders/encounter-relations](/api-reference/info/orders-encounter-relations)
        * GET [/api/v1/info/orders/frequencies](/api-reference/info/orders-frequencies)
        * GET [/api/v1/info/orders/medication-timings](/api-reference/info/orders-medication-timings)
        * GET [/api/v1/info/orders/origins](/api-reference/info/orders-origins)
        * GET [/api/v1/info/orders/statuses](/api-reference/info/orders-statuses)

      ### Enhancements

      * **Medication orders**: You can now send and retrieve medication orders for an ambient session and encounter using the following endpoints.

        **Structured data endpoints**: These endpoints return the structured data for an ambient session and encounter.

        * GET [/api/v1/ambient/session/{ambient_session_id}/structured-data](/api-reference/ambient-content/structured-data)
        * GET [/api/v1/ambient/session/{ambient_session_id}/encounter-structured-data](/api-reference/ambient-content/encounter-structured-data)

        **Context API**: This endpoint allows you to update the ambient session context with new EMR context and medication orders.

        * POST [/api/v1/ambient/session/{ambient_session_id}/context](/api-reference/ambient-sessions/update-context)

        **Content API**: This endpoint returns the content for an ambient session and encounter.

        * GET [/api/v1/ambient/session/{ambient_session_id}/content](/api-reference/ambient-content/content)
        * GET [/api/v1/ambient/session/{ambient_session_id}/encounter-content](/api-reference/ambient-content/encounter-content)

      **Payload structure**:

      ```json JSON theme={"theme":{"light":"github-dark","dark":"material-theme-darker"}}
      {
          "structured_data": {
              "orders": {
                  "medication_orders": {
                      "values": [
                          {
                              "drug_name": "Drug Name",
                              "status": "Status",
                              "medication_code": "Medication Code",
                              "medication_code_type": "Medication Code Type"
                          }
                      ]
                  }
              }
          }
      }
      ```

      
        When you send medication orders to the context API, the medication orders are validated against the EMR context. If the medication orders are not valid, the context API will return an error.

        Learn more in the [Medication orders](/documentation/concepts/ambient-clinical-notes/medication-orders) documentation.



  
    
      ### New endpoints

      * **Audio streaming and download**: We've added a new endpoint for audio streaming and download from ambient sessions. Stream or download the audio recording from an ambient session.

        * GET [/api/v1/ambient/session/{ambient_session_id}/recording](/api-reference/ambient-content/recording)

      Learn more in the [Audio streaming and download](/documentation/how-to/audio-streaming/audio-streaming-download) documentation.
    
  

  
    
      ### Deprecated

      * **Multilingual support**: The `multilingual` parameter is deprecated in the `Create Ambient Session` endpoint. When you call create ambient session API, the multilingual support is now **set to true by default**.
    
  

  
    
      ### New endpoints

      * **Audio Dictation API**: Added support for real-time audio transcription. Create transcription sessions, stream transcription data, and end sessions to get final transcripts. This enables use cases like Dictation, real-time captioning, and transcript generation.

        * POST [/api/v1/transcription/session/create](/api-reference/audio-transcription/create-session)
        * POST [/api/v1/transcription/session/{transcription_session_id}/end](/api-reference/audio-transcription/end-session)
        * GET [/ws/transcribe](/api-reference/audio-transcription/stream-transcription)
    
  

  
    
      ### Enhancements

      * **Code examples**: Added code examples in Python and TypeScript for all APIs, making it easier to integrate with the platform regardless of your preferred programming language.
    
  

  
    
      ### New endpoints

      * **Info endpoints**: Introduced three new info endpoints to provide supported enum values, helping you validate context data before submission and ensuring data consistency.

        * GET [/api/v1/info/encounter-types](/api-reference/info/encounter-types)
        * GET [/api/v1/info/visit-types](/api-reference/info/visit-types)
        * GET [/api/v1/info/provider-roles](/api-reference/info/provider-roles)

      * **API reference guidelines**: Added a new [API reference guidelines](/api-reference/api-guidelines) page to help you understand API status tags, versioning, and documentation standards.

      ### Enhancements

      * **Enhanced API documentation**: Significantly restructured and enhanced API reference documentation for better developer experience, clearer organization, and improved discoverability.

      * **Problem-based charting guide**: Completely rewritten the Problem-Based Charting (PBC) guide with a clearer structure and more detailed explanations of the processing pipeline.

      * **Audio streaming authentication**: Added detailed authentication guidance for both browser and non-browser clients in the Audio streaming API reference documentation.

      * **Enhanced context support**: Updated the [Ambient session context APIs](/api-reference/ambient-sessions/context) to support a new `VisitContext` schema, including fields like `chief_complaint` and `visit_type`. The provider context has also been enhanced to support `provider_role`.

      ### Removed support

      * **SNOMED codes**: SNOMED codes are no longer supported for the diagnosis context
      * **Paused state**: Paused state is no longer supported for ambient sessions