HIPAA-Safe Reporting for a Multi-Facility Treatment Provider
How a multi-facility outpatient substance abuse treatment provider replaced a stack of hand-maintained spreadsheets with an automated data lake and a live leadership dashboard — without ever putting protected health information in front of the people reading the report.
Delivered in partnership with another firm. The client and our delivery partner are unnamed here pending final approval.
Engagement Snapshot
- Industry. Healthcare — outpatient substance abuse treatment, multiple facilities across three legal entities
- Engagement. Data foundation and leadership reporting, delivered in partnership with another firm
- Scope. Strong Start alignment session, HIPAA-conscious data lake, OCR of payer remittance documents, de-identified leadership dashboard
- Constraint. Protected health information could never reach the leadership reporting layer
The Challenge
Leadership needed a clear, reliable picture of how the business was performing across every facility — clinical outcomes, patient census, insurance claims, revenue, and provider productivity — because that picture drove monthly staffing and bonus decisions.
Assembling it was a manual monthly effort spread across several departments and three legal entities, and the finished report was printed for a binder that leadership reviewed only a couple of times a year. Getting it was slow, hard to trust, and impossible to scale.
- The data leadership relied on lived in disconnected systems. The clinical and EHR system, the insurance clearinghouse, and the accounting system each held one piece of the picture, and none of them talked to the others. The clinical system already produced most of the non-financial data, which made the financial side the real gap.
- The report was stitched together by hand across roughly twenty-five to thirty spreadsheets. Two departments each maintained their own stack, and the KPI report had a stack of its own on top of those. Staff entered treatment details when a service was delivered, then returned days or weeks later to add insurance outcomes once a claim was processed. That two-pass process was slow, easy to get wrong, and impossible to scale as the organization grew.
- There was no single source of truth for leadership. No one had one place to see how each facility was doing — clinically, operationally, and financially — in time for the monthly review.
- Payment remittance data was locked inside PDFs. When payers sent remittance documents showing what was paid or denied on a claim, staff opened each PDF and retyped the figures into tracking spreadsheets. It was a tedious step and a common source of transcription errors on numbers that drove revenue reporting.
- All of it had to protect patient privacy. Any reporting solution had to keep protected health information fully separate from the high-level reports leadership would see, while keeping the underlying numbers accurate and defensible.
The Solution
We began with a Strong Start — a focused working session that aligned the client's leadership and our team on the highest-value problems and left the room with a clear plan to build against. We started from the end state, the report leadership actually needed, and worked backwards to wire up the data behind it. From there we delivered a data foundation that connects and reconciles the existing systems, and a live dashboard that turns that data into real-time insight.
- A data lake that unifies the disparate systems. We built a data lake that pulls from the clinical system, the insurance clearinghouse, and the accounting system and reconciles them automatically, matching each treatment service to its eventual claim outcome without anyone touching a spreadsheet. Where the source data was messy or incomplete, we built logic to reconcile it intelligently.
- Automated reading of remittance PDFs. We added optical character recognition to read payment and denial figures directly out of payer remittance documents and feed them straight into the pipeline. Staff no longer copy, paste, or retype these numbers. The figures flow into the same reconciliation process automatically, faster and with far less risk of a transcription mistake.
- A privacy-safe reporting layer by design. The pipeline produces two outputs. A fully identified report lets the billing team do their day-to-day claims work in place of the old manual spreadsheets. A de-identified, aggregated summary feeds the leadership dashboard, where only facility and month-level totals appear and patient identifiers never do. That separation was built into the architecture from day one.
- A live leadership dashboard. Leadership now has real-time, on-demand insight into performance across every facility: patient outcomes and completions, census trends, claim and reimbursement performance, income against expenses, and provider productivity. It is filterable by facility or across the whole organization, and it is ready whenever a decision needs to be made — including the monthly staffing and bonus review.
The Architecture: Two Outputs, One Pipeline
The privacy boundary is the point. Identified data goes only where the work requires it, and the reporting surface leadership uses is aggregated before it ever renders.
clinical / EHR clearinghouse accounting remittance PDFs
┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
└─────┬─────┘ └─────┬─────┘ └─────┬─────┘ └─────┬─────┘
└───────────────────┴───────────────────┴─────────────────┘
│ (OCR extraction)
┌─────────────▼──────────────┐
│ Data Lake + Reconciliation │ service matched to
│ (service ↔ claim outcome) │ its claim outcome
└─────────────┬──────────────┘
┌──────────┴───────────┐
┌───────────▼──────────┐ ┌────────▼─────────────────┐
│ Identified Report │ │ De-identified Aggregate │
│ billing team only │ │ facility + month totals │
└───────────────────────┘ └────────┬─────────────────┘
│
┌───────────▼────────────┐
│ Leadership Dashboard │ no PHI
└─────────────────────────┘
The Outcome
- The spreadsheet stack is gone. A manual, error-prone reconciliation process was replaced with an automated data lake, retiring the twenty-five to thirty hand-maintained spreadsheets.
- Leadership has one reliable, real-time view. Clinical, operational, and financial performance across every facility, in place for staffing and bonus decisions rather than printed for a binder.
- Manual entry is out of payment reconciliation. Payer remittance PDFs are read automatically, cutting a slow, error-prone task for the billing team.
- Privacy protection is structural, not procedural. Patient privacy is enforced by the architecture, so leadership reporting is fast and useful without ever exposing protected health information.
Why It Works
Healthcare reporting projects usually fail in one of two directions. Either the privacy requirement stalls the whole thing, or someone ships a useful dashboard by quietly routing identified data somewhere it should not be. Neither is acceptable, and neither is necessary.
We start from the decision the report has to support, design the privacy boundary before we design the pipeline, and then automate the reconciliation the staff were doing by hand. That is why the leadership dashboard is both trustworthy and safe to look at: the identified data stays with the billing team who need it to work claims, and everything above that line is aggregated before anyone sees it.
For regulated industries, that discipline is the whole engagement. Clean, reconciled data is what makes a dashboard worth reading, and a privacy boundary built at the foundation is what makes it defensible.
Get in touch · Virgent AI · Full-service strategy and AI development partner
