App Behavior
Understand how the Doctor App SDK drives UI behavior at runtime—handling session flow, screens, and context-driven transitions. This page helps you align your integration with platform logic.
What the Doctor App SDK Does
- Render screens dynamically based on session and route state.
- Manage authentication, role checks, and visibility rules.
- Apply server-defined UI behavior—such as enabling buttons or redirecting flows.
- Reflect updates to appointments in real time.
Core Functional Modules
| Module | Purpose |
|---|---|
| User Management | Control login, authentication, MFA, and session transitions. |
| Appointments | Display live appointment data, status updates, and session controls. |
| Other Tools | Expose localization, chat, video, and role-dependent utilities. |
Runtime Event Flow
| Event | SDK Response | Result |
|---|---|---|
| User signs in | Set session context | Unlock restricted screens |
| Session expires | Clear session state | Redirect to login |
/doctor/* route matches | Render embedded screen | Show UI based on context |
| User triggers an action | Execute metadata-defined behavior | Trigger navigation, popup, or verify |
| Appointment data changes | Refresh current view | Display updated content automatically |
Architecture
The diagram shows how your client app interacts with the Doctor App SDK runtime:
+----------------------+ SDK-Managed Rendering +-------------------------+
| |----------------------------->| |
| Your Host App | | Doctor App SDK Core |
| |<-----------------------------| |
+----------------------+ UI Events, State +-------------------------+
^ |
|<-------------------------------------------------------+
| Backend-Driven Rules (session, roles, config) |