OP OperixHealthcare Operations Docs
HR1-style shell Coverage
Buyer-grade product docs

Overview

Multi-clinic clinic operations, AI review workflows, communications, billing, pharmacy, and cPanel installer guidance in one generated docs surface.

Generated docsHR1-style shellCoverage appendixStatic delivery
Pages28

Generated static pages in this documentation set.

Modules17

Operational and platform areas mapped into coverage.

Source Files395

Routes, views, requests, tests, and supporting files referenced in the appendix.

Tests Linked32

Feature and supporting tests tied back to documented modules.

Platform One URL, many clinics

Central identity and memberships sit in the platform database while each clinic keeps its own operational data.

AI Draft-only copilot

AI actions are redacted, queued, permission-gated, reviewable, and never write back without a human decision.

Communications Twilio-first outbound hub

Email ships now, while SMS and WhatsApp move through a provider-aware queue with opt-out enforcement.

Resilience Readiness-first UX

Dashboards and AI entrypoints degrade to readiness cards when schema, queue, or demo data are incomplete.

Evidence Searchable static docs

Docs ship with search, coverage, self-serve screenshots, demo flow, and developer notes generated from one script.

Product story

What Changed In This Documentation Upgrade

Operix documentation now mirrors the app's platform direction instead of living as hand-edited marketing pages.

  • Public signup, Microsoft and Google SSO, clinic switching, health, and provisioning are documented as first-class buyer flows.
  • AI surfaces are framed as reviewable staff copilots, not autonomous clinical agents.
  • Twilio-backed communications, opt-out enforcement, audit exports, and platform access policy are described as product features instead of loose technical notes.
  • Coverage pages tie each documented module back to real routes, Blade views, requests, tests, and implementation files.
  • Demo flow now starts at public signup and owner onboarding, then drops into the clinic tenant story and AI review loop.
Public self-serve signup
Public signup and SSO entry now share the same platform shell as admin provisioning.
Platform clinic switcher
Platform shell with clinic memberships, switching, and provisioning.
Tenant dashboard readiness
Tenant dashboard with readiness, AI, and operations cards.
Suggested order

Where To Start

Buyers, implementers, and developers do not need the same entrypoint. Start in the order that matches the conversation you are having.

Buyer demo

Open Demo Flow

Implementer

Read Platform And Clinics

Admin

Open Settings And Roles

Developer

Open Developer Reference

Static delivery

Everything in this folder is static output. Re-run the generator whenever platform, module, or docs evidence changes.

See build commands
Buyer walkthroughDemo Flow

Lead with public signup, clinic launch, readiness, and AI review.

ArchitecturePlatform And Clinics

See the central-versus-tenant split, self-serve launch, and provisioning story.

Product layerAI Copilot

Understand the draft-only, review-first AI operating model.

EngineeringDeveloper Reference

Open build commands, route split, and regression shortcuts.