onSubmit runs in the browser when structured data is ready, but it may not run if the clinician closes the tab before processing finishes.
The example receives a Partner notification webhook after Suki completes backend processing, verifies the request, and fetches structured data to save to your EHR. Webhook session_id maps to ambient_session_id in the SDK. Webhook encounter_id maps to correlation_id when you pass your encounter UUID at session start.
JavaScript
Verify every request with Signature verification. Use
session_id as an idempotency key. Refer to Get Form filling structured data for production URLs and auth headers.Next steps
Refer to EHR handoff to mapstructured_data to your EHR fields
Refer to Session workflow for browser vs server delivery
Refer to Webhook quickstart for endpoint setup and testing