The Challenge
A statewide healthcare organization operating more than 50 clinics had data sitting in separate systems for each location — all on different servers, each named differently. Leadership could analyze performance at an individual clinic level, but assembling an enterprise view required weeks of manual report-pulling across each practice. Without a unified picture, they couldn't compare clinic performance, identify which locations were underperforming, or see where revenue was slipping before it was too late.
What They Built
Eric built a nightly-refresh Power BI control-tower dashboard aggregating data from 50+ clinics across 15 groups, then extended the platform into operations by embedding patient imaging flags, eligibility checks, and performance alerts directly into frontline clinical workflows.
Eric's first step was a deliberate departure from standard analytics project sequencing: instead of gathering data requirements, he interviewed every executive and operator to understand what decisions they actually needed to make. That conversation-first approach produced a KPI framework grounded in operational reality — production, write-offs, adjustments, appointments, and encounters — normalized across all 15 clinic groups and 50+ practices despite different system names, schemas, and data structures.
The data integration layer connected all 50+ clinic systems into a centralized Azure and SQL Server infrastructure with nightly automated refresh. Every dashboard view was wireframed against how leaders actually read and acted on data — not against how BI tools default to displaying it. Once the reporting layer was stable and trusted, the platform moved into operations: front desk staff received daily patient lists flagging who needed specific imaging before their appointment, intake staff received eligibility status checks to prevent unrecoverable billing write-offs, and site managers received performance alerts. What began as a reporting problem became an early-warning system that prevented revenue from leaking before it was too late to act.
AI Role
Estimated cost avoidance from revenue leakage caught before it materialized — including write-offs from missing imaging and failed eligibility checks
Infrastructure
• Microsoft Azure (cloud data infrastructure) • Power BI (analytics and dashboard layer) • SQL Server (structured data storage and integration layer) • Nightly ETL pipelines (automated refresh from 50+ separate clinic systems)
Integration Points
• 50+ clinic source systems connected via ETL to centralized Azure/SQL Server data layer • Power BI dashboards pulling from unified normalized KPI data model • Patient imaging and eligibility flags delivered via daily workflow lists to front desk and intake staff • Performance alert system connected to site manager notification workflows
Mid-market healthcare organizations — clinic groups, regional health systems, specialty practice networks — that have data in multiple locations but can't see across them. Especially relevant if leadership is still relying on manual report-pulling to answer basic performance questions, or if revenue is leaking through workflow gaps that nobody's measuring.