A Multi-Tenant Self-Service Reporting Portal for Healthcare Clients
Every client question about collection performance became an email and a manual export. We built an eleven-page analytics portal with tenant isolation, audit logging and one-click exports.
- Service
- AI Business Applications
- Industry
- Revenue Cycle & Finance
- Region
- United States
- Engagement
- Lab-type ODC (dedicated team)
Outcomes
- 11 self-service data pages
- Tenant isolation + audit trail
- Repeat export requests eliminated
Stack
Python · SQL · Power BI · RBAC · Private network
Written byOriental Nippon Team
A US revenue-cycle operator serves healthcare provider organisations. Its clients wanted to see their own collection, payment and recovery performance, but there was no secure way to give it to them.
So every question became an email. Several a day reached the internal analytics team, each one answered with a manual export, same-day at best.
The problem
- Slow answers. A day was the fastest turnaround, which was too late for some decisions.
- Repeat work. Analysts spent their capacity on the same exports again and again.
- Shared data estate. Many clients' data sat together, so isolation had to be guaranteed before self-service was possible.
- Regulated data. Access had to be evidenced, not just controlled.
| Before | After | |
|---|---|---|
| How clients got data | Email request and manual export | Self-service portal |
| Turnaround | Same day at best | Real time |
| Data pages | n/a | 11 interactive pages |
| Access evidence | None | Full audit log of access and activity |
What we built
A multi-tenant portal
Eleven interactive data pages covering collection performance, payments and account-level reporting.
Separation at the platform layer, with role-based access inside each tenant.
One-click exports
Any page to a spreadsheet.
Audit logging and session security
Every access recorded, deployed on a private network for regulated healthcare data.
What happens when a client user opens a page:
Technology and the role it played
| Technology | Role in this project |
|---|---|
| Python and SQL | Data model and metric definitions |
| Power BI | The eleven interactive data pages and exports |
| Role-based access control | Permissions inside each tenant |
| Private network deployment | Keeps regulated data off the public internet |
How we delivered it
We did not start with a page design. We started with the inbox: the twenty or so questions clients kept emailing about became the structure of the portal.
- Requirements from real requests. Recurring questions turned into a page map.
- Model the data. One definition per metric, traced back to source.
- Isolation before pages. Tenancy, access control and audit logging built first.
- Page by page. Each reviewed with the internal account teams.
- Pilot, then extend. A small client group first, then wider release.
01Requirements from real requests
2 wks
Recurring questions turned into a page map
02Data modelling
3–4 wks
Metric definitions, lineage, warehouse layer
03Tenancy and access control
2–3 wks
Isolation, RBAC, session security, audit logging
04Portal build
5–7 wks
Eleven interactive data pages and exports
05Pilot and extension
3–4 wks
Small client group, then wider release
Risks and how we handled them
| Risk | How we handled it |
|---|---|
| One client seeing another's data | Tenant isolation built and tested before any page |
| Access that can't be evidenced | Full audit logging of access and activity |
| Pages nobody needed | Page map built from the questions clients actually emailed |
Outcome
Clients answer their own questions in real time instead of waiting for an email, and the analytics team no longer spends its days on repeat exports.
The audit trail and isolation model support the client's healthcare compliance obligations. They were a constraint we were given, not a feature we invented.
What the client keeps
- The portal and its source
- The data model and metric dictionary
- Tenancy and access configuration
- Audit-log structure
- Deployment documentation
Sources and further reading
- Architect multitenant solutions on Azure, Microsoft Azure Architecture Center
- Multi-Tenant Security Cheat Sheet, OWASP
- Logging Cheat Sheet, OWASP
- HIPAA for professionals, U.S. Department of Health & Human Services
Facing something similar? This is the kind of work our AI, Data Science & Automation team delivers every day. Talk to us about your stack.
