SukiAmbientConstant.kEmrEncounterId when you create the session. Use getEncounterInfo or listEncounterNotes to get noteId values, then call the note-level methods.
How to list and read shared notes
status(for:), content(for:), transcript(for:), and getStructuredData(for:) retrieve the processing status or generated content for a single ambient recording session. Each method requires a sessionId.
To list or retrieve clinical notes shared across Suki products, use the note read APIs described below. Depending on the API, pass one of the following:
- An EMR encounter id.
- A
noteId. - The Ambient API
encounter_id(the same value you pass askSessionId) asencounterIdforencounterContent.
SukiStatus. These APIs use the same token provider configured for the ambient session APIs.
For more information, refer to Ambient interoperability.
Note read methods
The following are the note read methods supported by the Mobile SDK.method
Returns an overview of the shared notes for an EMR encounter. Use this when you need note status, sessions, and available artifacts before you call note-level or session-level retrieve APIs.
method
Lists notes for an EMR encounter so you can discover shared notes across products.
method
Reads note-level context for a shared clinical note.
method
Reads note content (suggestions) for a shared clinical note.
method
Reads structured note data for a shared clinical note.
method
Reads encounter-level content for the Ambient API
encounter_id. This is not an EMR encounter lookup.Note read method signatures
The following are the method signatures for the note read APIs in the Mobile SDK.Swift
Encounter info types
Swift
Get encounter info
Swift
List encounter notes and get note content
Swift
Get note content after encounter info
Swift