06.17
Clinic intelligence
Executive summary
Clinic intelligence gives owners and managers the operational picture: chair occupancy, recall performance, roster, compliance state and AI usage, with trends and insights. Metrics are computed by deterministic engines from snapshots taken on a schedule, not by asking a model. Telemetry feeding it is PHI-free by policy (TENANT-09).
Overview
- ProductionOperate · Clinic intelligenceShow a clinic how it is running without exposing patient data in aggregate views.
Pipeline
- A scheduled job writes KPI snapshots per clinic.
- Score, trend and insight engines compute indicators over operational, recall, occupancy, roster, compliance and AI metrics.
- The dashboard reads snapshots; nothing is computed from raw clinical text.
Data owned
- KPI snapshots
- Holds
- Per-clinic periodic metrics
| Store | Holds |
|---|---|
| KPI snapshots | Per-clinic periodic metrics |
Models and engines
This module makes no model calls. Everything it computes is deterministic code.
Guardrails
- Aggregates require an explicit clinic-scope route contract (TENANT-10).
- Telemetry carries no patient identifiers.
Rollout and status
- ProductionKPIs, trends, insightsSnapshot cron
Interfaces
- Consumes
- What
- Operational events and AI usage
- Emits
- What
- Dashboards and insights
| Direction | What |
|---|---|
| Consumes | Operational events and AI usage |
| Emits | Dashboards and insights |
SOURCE OF TRUTH
server/services/clinicIntelligence/server/services/kpiAggregator.ts