Get the latest updates and changes in Suki for Partners developer platform. Subscribe to the release notes to receive monthly updates across products.
Loading release timeline…
No releases found
No timeline titles match this search or filter combination. Clear the search, set Products and Attention to All, or try a different title keyword.
Initial beta release of the Suki Form filling SDK so you can embed Form filling in the browser with a hosted iframe or React components. Clinicians fill medical forms by voice, and your app receives structured JSON through SDK callbacks and your partner webhook.
Learn more: Form filling SDK overview · Form filling SDK changelog
Form filling is now included in @suki-sdk/js and @suki-sdk/react. Import Form filling from your Web SDK package. You do not need a separate Form filling SDK install.
Learn more: Web SDK Form filling overview · Web SDK changelog
You can now continue the same clinical note across Suki ambient products, including the Ambient APIs, Mobile SDK, Headless Web SDK, and Headed Web SDK. Pass emr\_encounter\_id when creating an ambient session, then use the returned composition\_id as note\_id with the note-level Ambient APIs.
Learn more: ambient interoperability · How to use interoperability across Suki products
From Mobile SDK v2.7.0, the Mobile SDK supports ambient interoperability with Ambient APIs and the Web SDK. Pass SukiAmbientConstant.kEmrEncounterId on createSession so the session shares one clinical note for the patient visit. Resolve remote session conflicts, handle peer terminate, and list or read shared notes with the new note read APIs.
Learn more: Mobile SDK interoperability · Mobile SDK changelog
The Headed Web SDK now supports Medication orders generation during ambient sessions. Pass LOINC code 52471-0 in ambientOptions.sections to enable review in the note UI and structured JSON on note submit.
Learn more: Medication orders overview · Medication orders payload structure
The Structured data API and Encounter structured data API now return HCC codes alongside ICD10, IMO, and SNOMED for suggested diagnoses. Parse type: "HCC" entries from the diagnosis codes array to validate EMR context and support risk-adjustment workflows.
Learn more: Structured data API · Encounter structured data API
You now have the option to authenticate providers using a single authentication token for all clinicians. When you choose this option, you must send sdp\_provider\_id as a header on every API call so Suki can route each request to the correct clinician. This applies to Ambient, Dictation, and Form filling API requests.
The headed Web SDK can shrink to a compact, viewport-aligned widget during ambient sessions so clinicians keep focus on the EHR or chart while capture continues in the background.
Learn more: Minimized layout overview · Minimized layout implementation
Our new Suki Form filling API allows you to create and manage Form filling sessions, retrieve structured data, submit feedback, and get info about Medical form templates for nursing use cases and data collection during in-person visits or virtual patient encounters.
Learn more: Form filling API overview · Form filling API changelog
Minor bug fixes and stability improvements for the Headless Web SDK.
Initial beta release of the Suki Dictation SDK so you can embed clinical Dictation in the browser with a hosted iframe, in-field or scratchpad modes, and callbacks for transcript text from JavaScript or React.
Learn more: Dictation SDK overview · Dictation SDK changelog
Sign-in now goes through SukiAuthManager from @suki-sdk/core, the same model as our other SDKs. Configure the manager with partner credentials, environment, and provider details, then pass it when you start the Web SDK.
Pass optional visit and provider fields in ambientOptions when you start a session (for example visitType, encounterType, reasonForVisit, chiefComplaint, and providerRole) so note generation has better context.
Learn more: ambient implementation · AmbientOptions properties
When visitType is set in ambientOptions, the Web SDK uses it as the note title for each generated note in the patient note list instead of the generic Note label, so multiple notes from the same day are easier to distinguish.
Provide optional medication orders via SukiAmbientConstant.kOrdersInfo and MedicationOrderKeys.kMedicationOrders after session creation in the iOS SDK to include medications tied to a visit, such as those from your EHR.
Provide optional EMR info via SukiAmbientConstant.kEmrInfo after session creation in the iOS SDK, to include information about the EMR system that applies to the session, such as the vendor code or environment-specific label.
Added new endpoints to get the list of supported medication coding systems, dosage units, encounter relations, frequencies, medication timings, origins, and statuses.
Medication orders are now supported in the API. You can now send and retrieve medication orders for an ambient session to be used in the note generation process.
New endpoint to stream or download the original audio from an ambient session using a presigned URL. Use it for playback, note verification, or compliance storage.
Learn more: Audio streaming and download · Get session recording API
When a session completes or fails, Suki sends a POST to your callback URL, same as when using the direct API. Configure one webhook URL per partner during onboarding.
Learn more: Notification webhook
Pass existing diagnoses from the EMR in ambientOptions.diagnoses so the session merges them with what's discussed during the visit and avoids duplicate problems in the note.
Removed multilingual from Create ambient session calls. Multilingual support is always on, which simplifies integration.
useAmbientSession exposes sessionType so you can tell whether a session was submitted online or offline and adjust UI or handling.
Multilingual is on by default in the Web SDK. birthDate and gender on Patient are optional when that data is unavailable.
Use the sections property instead of prefill.noteTypeIds before upgrading.