How we returned 100+ hours a month to a 40-member RCM team.
A 50-practice operation. Six different EHRs. Weekly KPIs, monthly report cards, quarterly benchmarking, annual analysis. All of it drowning the team's calendar. We built the automation that gave them their hours back, and watched what they did with them.
This is what happens when RCM operators build their own automation.
Gravitas is an AI-automation consultancy for US healthcare RCM. We are not a tech company that learned RCM. We are a team of RCM operators (billing, AR, appeals, credentialing) with 10+ years of operator depth, combined with the engineering discipline to build HIPAA-grade automation that holds up in production.
Today we serve US-based RCM operations managing claims across 30+ US payers, including BCBS plans in multiple states and California IPAs. Our team operates inside their AR, appeals, credentialing, and reporting workflows daily. Not as a vendor watching dashboards. As the people writing the queries and tuning the models.
This case study is about one of those workflows: the reporting backbone. The system that runs weekly KPIs, monthly financial report cards, quarterly benchmarking, and annual analytics across 50 practices on six different EHRs. The system that, before automation, was eating a 40-member team's calendar and pushing the actual revenue work to the bottom of the queue.
A 40-member team running reports for 50 practices, across six EHRs.
The math doesn't work. Every week, every month, every quarter, every year, the same reports get run. By hand. From six different portals. While the actual revenue work waits.
A cloud-native pipeline that runs while the team sleeps.
An RPA bot logs into each EHR portal nightly. Downloads the CSVs. Drops them in cloud storage. A function ingests them, deduplicates at row level, and lands them in the warehouse. A REST API serves the metrics. A React app turns them into the same reports the team used to build by hand, refreshed every morning.
minimal
Every Monday morning, the week's numbers are already there.
| KPI Descriptions | WoW | |
|---|---|---|
| 1.1 | Patient Visits (Office Only Visits) | ▲ 4.2% |
| 2.2 | Total Amount Billed | ▲ 7.8% |
| 3.1 | Payment Posted | ▲ 12.3% |
| 4.1 | Amount Over 90 Days Old (By Date of Service) | ▼ 2.1% |
| 4.3 | Total Amount A/R Balance (By Date of Service) | ▼ 1.4% |
The two-hour monthly report. Now built automatically.
| # | Statistic | Notes | YoY |
|---|---|---|---|
| 1 | Total Charges | A measure of total productivity. Includes total charges of each individual provider and any other charges. | ▲ 6.4% |
| 1a | Avg Daily Charges (ADC) | Total charges divided by number of calendar days. Tracks average productivity for the practice. | ▲ 6.1% |
| 2 | Total Payments (Receipts) | Total Payments | ▲ 9.2% |
| 3 | Copayments Collected | Co-payment collections | ▲ 3.7% |
| 4 | Total Refunds | Total refunds (insurance and patients). | ▼ 0.8% |
| 5 | Total A/R | Amount outstanding and owed to the practice. | ▼ 5.3% |
| 6 | Total Over 90 Days | From aging report. Tracks overdue collection trends. | ▼ 11.6% |
| 7 | % Over 90 | From A/R aging report. Another way to track overdue collection trends. | ▼ 4.2% |
| 8 | Gross Collection Ratio | Total payments divided by total charges. Measures how well you are billing and collecting. | ▲ 2.1% |
| 10 | Net Income | Total receipts minus total operating expenses (actual). What is left to pay the physicians. | ▲ 8.4% |
| 11 | Total Encounters | Total Office + Hospital encounters. | ▲ 4.9% |
| Office | |||
| Hospital | |||
| RPV | Revenue Per Visit | Total Payment / Total Encounters | ▲ 4.1% |
Where the money's leaking. With benchmarks built in.
Reports got automated. The team got reassigned. Collections went up.
The time savings are the mechanism. The revenue lift is the result. When the 40-member team stopped running reports, the AR analysts got freed up for AR follow-up. Recovery per collector went up immediately.
In their own words.
The voices behind the numbers. One CEO running the books. Two physicians running the patient floor. Same automation, three different ways of saying what changed.
Your reports are the loudest deadline in your week. We'll take them.
A 30-minute call to walk one of your recurring report packages, the one that eats the most time. If the build math works, we scope the sprint together. If it doesn't, you've spent 30 minutes and you understand your team's report load better than you did this morning.
Book a Working Session