App Behavior

---

Use the Air Doctor Doctor App to expose doctor-facing medical operations inside your platform while the Air Doctor server defines clinical workflows, permissions, and state transitions.

The Doctor App operates as a server-driven doctor runtime. The SDK interprets authenticated session context and hypermedia metadata to determine which screens, actions, and transitions remain available at any moment.

Integration level selection defines where the runtime executes and how much responsibility the partner assumes. Across all supported Doctor App levels, the server remains the source of truth for medical correctness and role enforcement.

important

The Air Doctor server defines clinical workflows, permissions, validations, and screen composition.
Client applications render server instructions and do not encode clinical or operational rules.

The Doctor App and Patient App rely on the same Open API, authentication model, and hypermedia conventions. This shared foundation ensures consistent behavior across roles and devices.

---

What the Doctor App Provides

The Doctor App exposes doctor-facing operational capabilities that remain consistent across supported integration levels.

🔹

Session Authority

Establish authenticated doctor sessions and enforce role-based access at runtime.

🔹

Appointment Control

Display and manage appointment state, actions, and lifecycle transitions.

🔹

Server-Defined Screens

Resolve and render doctor screens based on routes, permissions, and server metadata.

🔹

Live State Consistency

Synchronize appointment and session updates across devices without client-managed logic.

---

Doctor Runtime Model

The Doctor App SDK applies server-defined behavior based on active session context and resolved routes.

Runtime authority

The SDK applies server rules automatically after initialization.
The client does not bypass permissions or workflow transitions.

Runtime Event	SDK Action	Result
Doctor authenticates	Establish session context	Enable authorized routes and screens.
Session expires	Clear runtime state	Redirect to authentication.
Route resolves	Load screen definition	Render permitted content only.
Doctor triggers an action	Execute hypermedia action	Validate, navigate, or open dialogs.
Appointment state updates	Refresh runtime state	Update visible content immediately.

The SDK enforces transitions exactly as defined by the server response.

---

Core Functional Areas

The Doctor App groups functionality into runtime areas that operate under a shared session and permission context.

Area	Purpose
User Management	Handle authentication, MFA, session transitions, and role checks.
Appointments	Display live appointment data, session controls, and status changes.
Clinical Tools	Provide chat, video, localization, and role-dependent utilities.

Permissions and state remain consistent across all screens.