Search, filter, sort, columns and export
List-first DataViews keep shareable non-sensitive view state in the URL and personal presentation preferences in the user profile.
The product system
One operating model. Twenty-eight connected modules.
The module map shows where work happens, who owns it, and how each surface contributes to dental occupancy, patient experience, enterprise control, or trustworthy evidence.
0128connected modules
021central list system
03URLrestorable work state
Module matrix
From operational event to enterprise evidence.
This is the public functional map. Detailed permissions, states, integrations, and release evidence are reviewed privately during diligence or enterprise discovery.
| Domain | Module | Primary function | Primary users | Actual screen |
|---|---|---|---|---|
| Control plane | Platform administration | Tenant onboarding, plans, entitlements, service health, governed support | Platform owner | |
| Organization | Group, region & clinic hierarchy | Delegated configuration, location time zones, policies, scope and drill-down | Group and regional leaders | |
| Workforce | Team, shifts & clinical roles | People, schedules, time off, cost attributes, coverage and shared resources | Clinic and regional operations | |
| Patient operations | Patient workspace | Profile, timeline, household context, preferences, consent, work and follow-up | Front desk and coordinators | |
| Demand | Waitlist & patient preferences | Declared availability, travel, provider, appointment, contact and language preferences | Scheduling teams | |
| Recovery | Cancellation capture | Manual, schedule-change and connector-originated openings with clinic context | Clinic operations | |
| Recovery | Matching & fill engine | Eligibility, consent, fit, ranking, approval, offer, hold and one-winner confirmation | Schedulers and managers | |
| Network | Cross-location fill | Policy-controlled matching across sibling clinics with distance and scope controls | Groups and regions | |
| Scheduling | Calendar & command centre | Day, week, month and agenda views, lifecycle work, confirmation risk and handover | Clinic teams | |
| Coordination | Collaboration & acknowledgement | Announcements, urgent notices, notes, tasks, handover, ownership and acknowledgement | Every operational tier | |
| Automation | Journeys & escalation | Role-routed reminders, follow-ups, ownership, SLA ladders, stop rules and governed automation | Operations and experience teams | |
| Documents | Forms & managed content | Packets, status, signatures, document safety, presentation and writeback boundaries | Clinic and patient teams | |
| Communications | Bilingual journeys | Templates, reminders, outreach, responses, delivery evidence, quiet hours and consent classes | Patients and staff | |
| Intelligence | Occupancy & retention | Patient cadence, trip wires, light-window forecasts, action queues and controlled campaigns | Operations and growth | |
| Economics | ROI & found-profit | Idle-chair cost, recovered production, attribution, holdouts, costs and management reporting | Owners and finance | |
| Experience | Patient experience | NPS/CSAT, reviews, complaints, follow-up ownership and multi-location trends | Experience leaders | |
| Readiness | Payments & eligibility | Deposit, refund, payment-link and eligibility boundaries through governed providers | Billing coordinators | |
| Governance | Privacy & compliance | Consent, DSAR, PIA, transfers, incidents, evidence, retention and policy controls | Privacy and security | |
| Integration | PMS and provider connectors | Normalized schedules, reconciliation, exceptions, health and manual fallback | Integration administrators | |
| Reliability | Health, errors & recovery | Copyable safe references, queues, telemetry, replay-safe recovery and support evidence | Support and IT | |
| Identity | Profiles & delegated access | Appearance, language, sessions, notifications, role-aware view-as and audit banner | Every workforce user | |
| Enterprise | SSO, SCIM & SIEM control planes | Verified-domain identity, provisioning, recovery access and evidence export boundaries | Enterprise IT | |
| Commercial | Plans, seats & usage | Entitlements, exceptions, licensed capacity, metering and account lifecycle | Platform and group owners | |
| Developer | API, webhooks & data platform | Versioned contracts, partner surfaces, BI export and connector observability | Engineering and partners | |
| Brand | White-label delivery | Inherited brands, patient identity continuity, managed assets, domains, senders and attribution | Groups, regions and clinics | |
| Patient | Response portal & help | Branded offer, preference, form, feedback and outreach-response journeys | Patients and support | |
| Knowledge | Contextual help & support | Screen-specific bilingual guidance, central help catalogue, examples, next steps and Markdown export | Every user | |
| Growth | Public marketing & SEO | Privacy-separated public content, bilingual discovery and approved distribution | Commercial teams |
A consistent interaction contract
Every module answers the same operational questions.
Where am I? What needs attention? What may I do? What happened? What is blocked? What comes next? Shared DataView, drill-down, URL state, help, error references, and history patterns keep those answers consistent.
Rows, cards and metrics open evidence
Authorized detail drawers and paths retain the originating scope, filters, and Back-button contract.
CRUD and transitions are role-aware
The same record exposes different actions according to role, scope, lifecycle state, policy, and current source authority.
Errors become recoverable work
Safe references, retry rules, exception queues, ownership, and timelines replace vague failure messages.
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.
Module coverage
The public matrix traces the connected control, operational, patient, evidence and growth modules.
Product evidence: Product specification §8Consistent lists
Shared search, filter, sort, column, segment, export and pagination behavior reduces module-specific surprises.
Product evidence: Screen experience contractRestorable drill-down
Rows, cards and metrics lead to authorized evidence while preserving the return path and shareable screen state.
Product evidence: Screen experience contractRole-aware actions
Available transitions depend on the actor, organization scope, record lifecycle and governing policy.
Product evidence: Role-action matrixRecoverable failure
Query retry, ambiguous mutation warnings, safe references and history destinations turn failure into owned work.
Product evidence: Screen experience contract · Security 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.