schema, or a mix of both. This page shows how to integrate Form filling with the Suki Web SDK in a browser-based JavaScript or React application.
For dynamic and mixed forms, Form filling in the Web SDK requires v3.3.1 or later.
SukiAuthManager and a FormFillingClient. In React, wrap your tree with FormFillingProvider, then render FormFilling when the clinician should fill forms. In JavaScript, call await formFillingClient.start({ ... }) when they are ready.
Static, dynamic, and mixed forms
Pass the forms for the session in theforms array. Each entry is either a Suki defined medical form template or a partner-defined schema:
-
For dynamic forms, match results with
partner_form_id(the same value as theidyou pass on that form). Do not rely on array order. -
form_template_idsis deprecated, but still works when you omitforms. Preferforms: [{ form_template_id }]for new work. If you passforms(including an empty array), it is the only source of context andform_template_idsis ignored. The same rule applies to JavaScriptstart({ forms: [] })and ReactFormFillingwithforms={[]}.
Prerequisites
Before you start, complete the Web SDK prerequisites. Get yourpartnerId from Partner onboarding. Pass a partnerToken (JWT from your identity provider) with that Partner ID to sign in.
You also need:
- Forms for the session: Pass
forms. Use a Sukiform_template_idfor template entries (ask Suki support for the IDs, or see templates). Use aschemafor your own forms. - Encounter ID: Pass it as
correlation_idso callbacks and webhooks match the right record.
Integration guides
Choose the guide for your stack:JavaScript
Integrate Form filling in a browser-based JavaScript app with the Web SDK.
React
Integrate Form filling in a browser-based React app with the Web SDK.
form_template_ids, correlation_id, and callbacks, refer to the Configuration guide in the Form filling SDK section.