A national revenue cycle organization processes 16× more claims per hour
By moving adjudication to the database layer and running it in scheduled off-peak batches, the organization handled higher claim volumes at lower cost, without increasing headcount.

Overview
The client processes claims on behalf of hospital systems across the United States. As claim intake grew, the work around each claim grew with it: more adjudicator time, longer queues and more rework.
The organization needed to process higher volumes without its costs rising at the same rate. Key Software’s Claims Auto Adjudication moved adjudication logic into the database layer and ran it in scheduled batches outside business hours, so throughput could rise without adding load to production systems during the day.
The challenge
Cost grew with every claim
Each increase in claim intake required more adjudicator time. The average claim needed 4.42 manual touches.
Adjudication competed with production systems
Runs executed against live environments during business hours, which constrained throughput to about 1.5K claims per hour.
Volume peaks became backlogs
Busy periods pushed the median claim age to 13 days, and 45% of claims needed rework after manual adjudication.
The solution
A configurable rule library at the database layer
Rules apply directly to claims data in the database, without screen-level scripts or UI bots.
Claims selected by criteria or by list
Each run targets the right claims, through configurable inclusion and exclusion criteria or from a defined list.
Repricing, reprocessing and denial correction
Rules reprice open claims, reprocess paid claims and correct rule-based denials.
Off-peak batch scheduling
Runs are scheduled outside business hours, so production systems keep their full capacity during the day.
The results
Results compare the client’s operation before and after Key Software’s Claims Auto Adjudication.
- Claims processed per hour: 1.5K → 25K
- Manual touches per claim: 4.42 → 2.2
- Median claim age: 13 days → 3 days
- Share of claims touched by the automation engine: 30% → 65%
- Claims failing on first pass: 13% → 5%
- Claims needing rework after adjudication: 45% → 24%
With adjudication running off-peak, the organization absorbed volume increases without a matching increase in headcount, while improving adjudication outcomes and reducing total cost of operations by 50%.
Why it worked
Non-linear scaling
Throughput rises without a proportional increase in adjudicators.
Production environment unconstrained
Off-peak runs leave live systems untouched during business hours.
Processing time optimized
Intake peaks are absorbed by the batch cycle instead of turning into backlogs.



