Platform owner
Tenants, plans, governance, health, support, and privacy-safe aggregates
Enterprise operating model
A control plane above the work—not inside every clinic task.
Provision organizations, delegate responsibility, preserve clinic context, compare performance, and intervene through governed access without turning the platform owner into a daily operator.
01Platformcommercial + service control
02Grouppolicy + portfolio
03Cliniclocal execution
Four-tier hierarchy
Platform → group → optional region → clinic.
Policy and visibility flow downward only where allowed. Operational data remains tenant-isolated, while higher roles receive scoped rollups, drill-down, and exception ownership.
00
Franchise / group
Brand, policy, regions, clinics, entitlements, and portfolio outcomes
Optional region
Clinic comparison, coordination, exceptions, and shared resources
Location / clinic
People, chairs, schedules, patients, daily work, and outcomes
Enterprise capabilities
Built for organizations with real operating complexity.
Location time zones, branding, access, integrations, entitlements, evidence, and reporting are modeled as first-class scope—not added as global settings later.
Clinic-local operations
Schedules and rules follow each location’s IANA timezone; cross-location views preserve timezone context and DST-safe interpretation.
Higher roles configure lower scope
Group leaders establish allowed policy; regions and clinics override only fields explicitly delegated to them.
Support without invisible impersonation
Time-boxed, reasoned, audited delegated access makes the effective role and scope unmistakable and easy to exit.
SSO, SCIM and recovery boundaries
Verified domains, provisioning, group mapping, deprovisioning, seat checks, recovery administration, and audit evidence form the local control plane.
Plans, seats, usage and exceptions
Platform-owned entitlements and tenant exceptions govern access without hard-coding commercial logic into each screen.
Roll up, then drill down
Group and regional metrics connect to authorized clinic evidence while protecting small cohorts and patient identity.
Organization fit
One system can meet different operating models.
The architecture supports a single clinic, a growing group, a regional network, or a strategic platform owner without forcing every customer into the same governance model.
| Independent clinic | One location | Local execution | Clinic brand | Calendar, recovery, patients, workforce, ROI | |
|---|---|---|---|---|---|
| Growing group | Multiple clinics | Group policy + delegation | Group with overrides | Comparison, cross-location, roles, brand, economics | |
| Regional network | Regions + clinics | Regional coordination | Regional inheritance | Coverage, exceptions, performance, shared resources | |
| Strategic platform | Multiple tenants | Separate control plane | Governed white-label | Provisioning, plans, health, support, identity, and aggregates |
Evidence-led product tour
See the system in action.
Captured from the working product with synthetic demonstration data. Use the thumbnails like an ecommerce product gallery; every view explains what to notice and the documentation that governs it.
1 / 4Select a thumbnail to explore
Full topic drill-down
What this part of the product covers.
Each topic connects the public promise to a real screen and the relevant product evidence. Detailed technical records remain available during an appropriate private review.
Hierarchy
Platform, tenant, optional region and clinic remain explicit authorization and configuration boundaries.
Product evidence: Product specification §6 · Architecture recordLocal time
Clinic-local scheduling uses each location’s IANA time zone while cross-location views keep context visible.
Product evidence: Product specification §9.3 · Product specification §9.7Delegation
Higher tiers set policy; lower tiers override only fields explicitly delegated to them.
Product evidence: Product specification §9.3 · Role-action matrixIdentity and support
Enterprise identity and time-boxed view-as preserve a visible, auditable effective role.
Product evidence: Product specification §19 · Security recordCommercial control
Plans, seats, entitlements and exceptions are governed centrally rather than scattered through features.
Product evidence: Product specification §9.2 · Architecture recordA serious operating review
See the product as a system—not a collection of screens.
Bring your organization structure, cancellation economics, integration landscape, branding requirements, and diligence questions. We will map the operating boundary and the evidence available today.