Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A revenue-cycle operation producing reporting for a large number of hospital client facilities.
The reports had been built over years on a legacy reporting platform and an enterprise application's native reporting. They worked, but each facility's requirements had been met by producing another variant, and the set had fragmented.
The problem
- Reports were static, so any question beyond the printed answer meant a new request.
- The same measure was defined differently in different reports, which made comparison between facilities unreliable.
- Producing and distributing the set was manual and recurring.
- Facility-specific requirements had been handled by proliferation rather than by parameterisation.
What we built
Thirty-plus reports rebuilt
On a modern BI stack — financial, batch performance, stair-step recovery, invoice summary, detailed invoices, month-end, ACH, aging and acknowledgement reporting — each tailored to the requirements of the facilities that use it.
A single definition per measure
So a number means the same thing across the set.
Automated refresh, export and distribution
With output emailed and placed in shared document storage on schedule.
How we delivered it
- 1
Inventory the existing set
Every report, its consumers, and what it actually answers.
- 2
Reconcile the definitions
Which is where most of the real work sat, and record the decisions.
- 3
Rebuild in waves
Grouped by consumer so a facility's set changes once rather than repeatedly.
- 4
Parallel-run old and new
For a cycle, comparing outputs before retiring anything.
- 5
Automate production and delivery
Once the content was agreed.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The report definitions
- The semantic model and metric dictionary
- Refresh and distribution configuration
- The reconciliation decision log from the rebuild