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 serving healthcare provider organisations. Its clients wanted to see performance, payment and recovery data about their own accounts.
There was no mechanism for that, so the demand landed on an internal analytics team as a stream of individual requests — several a day, answered same-day at best, each one a manual export.
The problem
- Client visibility depended entirely on someone building a spreadsheet on request.
- The turnaround was a day at best, which made the data too old for some decisions.
- A dedicated analytics team's capacity was being consumed by repeat requests rather than analysis.
- Data covering multiple healthcare clients sat in one estate, so any self-service access had to guarantee isolation before it could be offered at all.
- Regulated data meant access needed to be evidenced, not just controlled.
What we built
A multi-tenant analytics portal
Eleven interactive data pages covering collection performance, payment data and account-level reporting.
Tenant-level data isolation
Enforced at the platform layer, so a client can only ever resolve their own data, with role-based access control within each tenant.
One-click exports to spreadsheet
Because the honest reality is that some users will always want the data in their own hands.
Full audit logging
Of access and activity, with session security appropriate to regulated healthcare data, deployed on a private network.
How we delivered it
- 1
Define the questions first
The twenty or so things clients were actually emailing to ask, which became the page structure.
- 2
Model the data
So each metric has one definition and traces back to source.
- 3
Build isolation and access control before the pages
Since retrofitting tenancy is the failure mode here.
- 4
Page by page
Reviewed with internal account teams who knew what clients meant.
- 5
Pilot with a small group of clients
Then extend.
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 portal and its source
- The data model and metric dictionary
- Tenancy and access configuration
- Audit-log structure
- Deployment documentation