Understand the clinic app, then complete the task.

These guides follow the signed-in workspace: Dashboard, Patients, Integrations, Templates, Reports, Team, and Settings. The public website and clinic workspace stay separate from this documentation portal.

Start with the responsibility you have.

The same clinic workflow looks different to a provider, an owner, a security reviewer, and a developer.

  • I provide care

    Find patients, verify source data, generate reports, and complete clinical review.

    Provider guide
  • I run the clinic

    Set up the workspace, team, integrations, templates, billing, and security controls.

    Clinic setup guide
  • I evaluate security

    Understand tenant isolation, authentication, patient-data handling, and audit evidence.

    Security guide
  • I build integrations

    Create clinic-scoped keys and work with the TypeScript SDK or HTTP API.

    Developer guide

The web app follows the path of a report.

Open a step to read the guide for that screen. The Dashboard brings the current state together.

  1. PatientsWho is this report for?
  2. IntegrationsWhere does the approved source information come from?
  3. TemplatesWhat belongs in the report and how should it look?
  4. ReportsWhat should the provider review, approve, and deliver?
  5. Team and SettingsWho can do the work and which clinic rules apply?
Understand the clinic app

Browse the documentation

Start with the task you are trying to complete.

Learn Orvexa

Use the clinic app

Manage the clinic

Build with Orvexa

Three rules explain most of Orvexa AI.

Templates control the report
Clinic teams choose the sections, approved data fields, design, and required clinical input before a template is published.
Providers make the clinical decision
Orvexa AI prepares a draft. A healthcare provider reviews the source values and approves the finished PDF.
Clinic boundaries stay intact
Connections, templates, team membership, billing, and activity records remain scoped to one clinic workspace.