Approve Disclaimer

Use the Approve Disclaimer screen to present a mandatory legal message that must be acknowledged before the doctor continues.
The app loads this screen automatically during onboarding, login, or appointment workflows when the backend determines that a new disclaimer requires acceptance.
The screen blocks all navigation until the doctor confirms.

This screen includes:

A static disclaimer tailored to the doctor’s profile or organization.
A single Ok button that records acknowledgment.
No editable controls, input fields, or secondary actions.
Redirect logic that ensures this screen appears only when acceptance is required

Workflow

The doctor signs in or accesses a workflow that requires updated terms.
The backend checks the doctor’s acceptance history.
If a disclaimer is pending, the app redirects to this screen.
The doctor reviews the message and selects Ok.
After acknowledgment, the backend records consent.
The session continues and no further prompts appear until a new disclaimer is required.

Validations

These scenarios describe how the app evaluates the Approve Disclaimer requirement.

Scenario	App Behavior	SDK Output	Example
The doctor already accepted the current disclaimer.	The app bypasses this screen and continues normally.	No disclaimer fragment in the page object.	—
A disclaimer is required but not acknowledged.	The app blocks navigation and displays the disclaimer screen.	Page object with mandatory disclaimer components.
The doctor selects Ok but network issues prevent submission.	The app displays an inline retry message.	Transport-level error; no state change.	—
The doctor attempts to navigate without confirming.	The app ignores the request and keeps the disclaimer visible.	No-op update; acknowledgment required.	—

Actions

These scenarios describe how the app processes doctor actions on the Approve Disclaimer screen.

Scenario	App Behavior	SDK Output	Example
The doctor selects Ok.	The app records acceptance, dismisses the screen, and continues the workflow.	Update set confirming acknowledgment.
The doctor retries after a failed acknowledgment.	The app resends the confirmation.	Update set with confirmation on success.	—

Endpoint Resources