Info
Encounter Information
Get encounter information to look up notes, sessions, and artifact availability for an EMR encounter
Listen to this pageabout 1 min
GET
Gets resolved note → session hierarchy for an EMR encounter.
Use this endpoint to get an overview of all ambient sessions and artifacts associated with an .
Pass the same
emr_encounter_id you used when creating interoperable ambient sessions. The value can be a UUID or non-UUID string and must be at most 36 characters.
The response provides read-only metadata for the visit, including:
- Note IDs
- Session IDs
- Timestamps
- Session statuses
- Available artifacts
GET endpoints to retrieve those artifacts when they are listed in the response. For example, if artifacts includes content, transcript, or recording, use the corresponding GET endpoint to fetch the data.
Cross-modality ambient workflows require
emr_encounter_id when you create a session. Without it, notes are not interoperable across modalities. Refer to Ambient interoperability for more details.Code examples
- Python
- TypeScript
Authorizations
Suki access token (suki_token) from Login or Register. Expires after one hour.
Headers
Optional for standard partners.
Required for:
- Bearer authentication. Use the same
provider_idreturned by the Login or Register API. - Single Auth Token authentication. Include the same
provider_idon every request assdp_provider_id.
Example:
"provider-123"
Path Parameters
EMR encounter id (UUID or non-UUID, at most 36 characters). Same value you pass as emr_encounter_id on Ambient session create for interoperable workflows.
Maximum string length:
36Response
Success Response
Resolved note → session hierarchy for an EMR encounter.
Notes with sessions and artifact availability for the EMR encounter.
Last modified on September 29, 2026