A KPI architecture for multi-site provider operations

Start with decisions, not dashboards

Define the recurring decisions that executives, regional leaders, and location operators must make. For each decision, record the measure, cadence, comparison, materiality threshold, owner, and evidence needed to act.

This prevents a KPI catalog from becoming an inventory of available fields. A measure belongs in the system when it supports a defined review or operating action.

• Executive performance and risk review
• Regional and location exception review
• Access and capacity planning
• Labor and productivity management
• Claims and revenue follow-up
• Data-quality and source-owner review

Preserve facts at their natural grain

Daily census, appointment availability, worked hours, claim transactions, posted revenue, and quality events do not describe the same thing. Each belongs in a fact structure with its own business keys, effective dates, correction behavior, and reconciliation controls.

Shared location, service-line, payer, provider, organizational, and calendar dimensions create comparison without pretending that unlike events have identical timing.

Create a governed semantic boundary

The semantic layer should hold reusable measures, approved relationships, time behavior, access rules, display context, and ownership. Reports then consume governed meaning rather than rebuilding it in each visual.

Every material measure should identify its numerator, denominator, grain, source authority, exclusions, refresh expectation, owner, and known limitations.

• One approved measure definition
• Role-aware access
• Visible source freshness
• Reconciliation status
• Exception ownership
• Release evidence

Design the review system

A dashboard is only one component. The operating system also needs a refresh record, failed-check queue, exception thresholds, review cadence, owner, and disposition path.

The strongest architecture connects a material variance to the source context and the person responsible for deciding what happens next.

Primary sources

• Microsoft: Power BI star schema guidance
• HHS: Minimum Necessary Requirement