Operations, claims, labor
Explicit grain, date, owner, cadence, and correction behavior.
Synthetic reference
A healthcare operations analytics system you can inspect.
A fully synthetic reference path across six locations, 42 fact rows, operations, claims, workforce, governed measures, quality controls, Microsoft Fabric, Power BI, and Snowflake.
Evidence boundary
Every organization, location, identifier, record, and value is synthetic. This demonstration contains no PHI, personal information, clinical recommendation, or client outcome.
Reference architecture
From source contracts to accountable review
The same operating contract is implemented through Microsoft and Snowflake paths so the platform decision can follow evidence.
Land and reconcile
Keys, completeness, ranges, totals, freshness, and failed-check routing.
Shared analytical meaning
Location and date dimensions, bounded facts, measures, access, and lineage.
Power BI and review
Executive and operating exceptions with owners and release evidence.
Metric dictionary
Definitions remain attached to authority and ownership.
| Measure | Definition | Authority | Owner |
|---|---|---|---|
| Occupancy rate | Occupied capacity divided by available capacity | Daily location operations | Operations owner |
| Visit completion rate | Completed visits divided by scheduled visits | Daily location operations | Access owner |
| Paid to allowed | Paid amount divided by allowed amount for paid claims | Claims summary | Revenue-cycle owner |
| Productive utilization | Productive hours divided by worked hours | Workforce summary | Workforce owner |
| Overtime rate | Overtime hours divided by worked hours | Workforce summary | Workforce owner |
Validated controls
Quality checks run before publication
- Every fact row references a known synthetic location.
- Occupied capacity cannot exceed available capacity.
- Completed visits cannot exceed scheduled visits.
- Claim counts and financial amounts cannot be negative.
- Productive, overtime, and agency hours cannot exceed worked hours.
- Source date and grain remain visible through the modeled path.
Implementation paths
One workload contract, two established platform paths
Microsoft Fabric and Power BI
OneLake landing, Fabric warehouse or lakehouse modeling, deployment pipelines, governed semantic models, and Power BI review.
Read the Fabric implementation noteSnowflake and Power BI
Controlled stages, SQL transformations, independent compute, role-aware serving, reconciliation, and a governed Power BI semantic boundary.
Read the Snowflake implementation notePortable analytical model
A dimensional SQL reference keeps the source, fact, dimension, and measure boundary inspectable across the two paths.
Download the modelQuality and metric evidence
Starter controls and a metric dictionary record what is tested, what each measure means, and where interpretation remains necessary.
Download the quality checksUse this as the first technical briefing.
Permadyn Analytics can walk through the workload contract, both platform paths, and the controls that turn source records into reviewable operating evidence.
Request the briefing