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 encounter.
Use this endpoint to get the associated with the specified .

Diagnosis codes in structured data

When Problem-Based Charting (PBC) is enabled, each diagnosis in structured_data.diagnoses.values can include ICD10, IMO, SNOMED (when available), and HCC codes in the codes array. HCC values are derived from the ICD-10-CM code using the CMS-HCC V28 model. The description for HCC entries uses the format CMS-HCC model category <code>. HCC codes are returned in structured data output only. Do not send them in session context. For a comparison of ICD-10 and HCC codes and how Suki returns them, refer to Diagnosis codes FAQs.

Code examples

Authorizations

sdp_suki_token
string
header
required

Suki access token for the authenticated provider. Obtain this by calling Login or Register with a valid partner_token. Pass the suki_token value from the JSON response as the sdp_suki_token header on REST requests and non-browser WebSocket upgrades. Browser WebSocket clients pass the token in Sec-WebSocket-Protocol instead. Tokens expire after one hour; call Login again to refresh.

Headers

sdp_provider_id
string

Optional - Stable identifier for the active provider. Omit for standard partners whose partner_token identifies the user. Required for Bearer partners and Single Auth Token authentication where multiple providers share one partner_token. Use the same provider_id you sent on Login or Register.

Example:

"provider-123"

Path Parameters

encounter_id
string
required

UUID for the patient encounter (visit). Use the encounter_id from session create or the UUID you assigned when grouping multiple sessions under one visit.

Response

Request succeeded.

Response body for the /encounter/{encounter_id}/structured-data endpoint

structured_data
object
Last modified on June 30, 2026