- Install the Suki Web SDK package for your framework (JavaScript or React).
- Initialize the SDK by creating a
SukiAuthManagerfrom@suki-sdk/corewith yourpartnerTokenand provider fields. - Mount the SDK UI into your application using the
encounterobject.
Prerequisites
For the rest of this documentation, we assume the following setup is complete:-
You have received your
partnerIdfrom Suki. - Your host URLs are on the Suki allowlist.
- Your partner configuration in the Suki Platform points to your correct JWKS endpoint.
- Your JWT token contains the key that you specified as your User identifier field.
Steps
1
Install the Suki SDK Package
Install the Suki Web SDK package in your project. Choose the appropriate package based on your framework.For detailed setup instructions, refer to the Installation guide.
2
Initialize the SDK
Initialize the Suki SDK by creating
SukiAuthManager from @suki-sdk/core with the following required fields:partnerIdRequired - YourpartnerIdfrom Suki.partnerTokenRequired - YourpartnerTokenfrom Suki.providerNameRequired - The full name of the provider.providerOrgIdRequired - The organization ID of the provider.
authManager into initialize() in JavaScript or init() in React.Run initialization once, usually from your app entry point, so your app can sign in to Suki and use Web SDK features.Import
@suki-sdk/core and @suki-sdk/js, create SukiAuthManager with your partnerToken and provider fields, then call initialize({ authManager }). Do this in your main application file (for example index.js or app.js).main.js
3
Mount the SDK UI
After initializing the Web SDK, mount the Suki UI into your application using the
encounter object. This object provides patient context for Ambient documentation and transcription.Encounter and patient IDs:
-
patient.identifieris required.encounter.identifieris optional. Both must be strings of at most 36 characters (). Longer values can fail during composition or ambient setup. -
From Web SDK v3.2.0, if you set
encounter.identifier, use a UUID. The Web SDK maps that value toemr_encounter_idfor ambient interoperability and encounter note retrieval. - Non-UUID values can break past-note loading even when ambient session start, pause, and submit still work. See Patient, Encounter type definitions for more information.
If you face any issues while mounting the SDK UI, make sure you are using the correct package and framework.
main.js
Verify your integration
After you record and stop your first ambient session, you should see:- The generated clinical note automatically appears in the mounted
SukiAssistantUI panel. - Sections are organized according to your LOINC configuration.
- The transcript is available within the UI.