Skip to main content
GET
cURL
Updated:
  • Diagnosis output now includes HCC codes alongside ICD10, IMO, and SNOMED.
  • You now get Medication orders in the structured data output for an ambient session.
Use this endpoint to get the cumulative associated with the specified . Retrieve diagnosis codes after Session status is completed. The codes are generated by then and do not change, so one request is enough.

Diagnosis codes in structured data

When Problem-Based Charting (PBC) is enabled, each diagnosis in structured_data.diagnoses.values includes a flat codes array:
Each code object contains type, code, and description. The array can also contain IMO and SNOMED entries.
Parse codes as an array. codes.values is not part of the partner contract.

Code types

Following are the code types Suki can return in the codes array:
  • HCC entries use description in the format CMS-HCC model category <code>, such as CMS-HCC model category 65. HCC codes are returned only in structured data. Do not send HCC codes in session context.
  • ICD-10 is not always returned. If your UI displays ICD chips, display them only when codes[] contains an entry with type set to ICD10. Continue to display diagnosis_note when codes are incomplete.
To load the generated note into a chart, refer to Load the note. For more information about ICD-10 and HCC codes, see Diagnosis codes.
  • An ICD-10-CM diagnosis may not have an HCC code if it does not map to an HCC model category.
  • After an ambient session completes, use the session endpoint to retrieve its content. If a note spans multiple ambient sessions, use Note structured data.
  • For the complete workflow, refer to Load the note guide.

Code examples

Authorizations

sdp_suki_token
string
header
required

Suki access token (suki_token) from Login or Register. Expires after one hour.

Headers

sdp_provider_id
string

Optional for standard partners.

Required for:

  • Bearer authentication. Use the same provider_id returned by the Login or Register API.
  • Single Auth Token authentication. Include the same provider_id on every request as sdp_provider_id.
Example:

"provider-123"

Path Parameters

ambient_session_id
string
required

UUID for the ambient session. Use the ambient_session_id returned from Create Ambient Session, or the UUID you supplied in that request.

Response

Request succeeded.

Response body for the /session/{ambient_session_id}/structured-data endpoint

structured_data
object
Last modified on August 20, 2026