Medical bill review prep time: the steps before the opinion

What are the steps to prepare a medical bill review?

Preparation is six steps in a fixed order: find every billing page, group the bills and merge duplicates, type every charge line, add the fee schedule and UCR columns, check the sheet against the source pages, and hand it to the expert. Each step depends on the one before it.

1. Find every billing page. Look at every page of the record. There is no index and no reliable way to tell a billing page from a treatment note without looking.
2. Group the bills by provider and date, and merge duplicates. The same charge often appears on more than one document, such as a ledger and a claim form, and it should become one row. How duplicate charges are merged is covered in its own article.
3. Type every charge line. Each charge becomes a row: date of service, provider, code and billed amount. When a bill has no CPT code, that line needs its own handling before it can be priced.
4. Add the fee schedule and UCR columns. Put the comparison figures next to each row. The Medicare rate lookup and the NJ PIP UCR lookup show the basis for each figure.
5. Check the sheet against the source pages. The expert will not re-verify the rows, so this check is the last one the data gets.
6. Hand the sheet to the expert. The opinion starts here and takes a few hours.

How long does each prep step take?

On the 3,000-page case, as I remember it, no single step dominated. Finding the billing pages, typing the rows, adding the columns and checking the sheet each took roughly the same share of the three to four days. I did not record hours per step, so this page gives none.

The total did vary with the case. A small case with two providers and 200 pages is a couple of hours. The longest case I prepared by hand ran to about 5,000 pages and took about a week, mostly because of the number of providers. Prep time tracks the page count and the number of providers, because every page has to be looked at before it can be ruled out.

That relationship is the part worth sitting with. The opinion on a 3,000-page case is not meaningfully harder than the opinion on a 300-page case. The reasoning is the same, the benchmarks are the same, the report is a similar length. What changed by a factor of ten is the assembly. Page count sets the delivery date, and page count has nothing to do with the part that requires expertise.

Every expert in this field has felt that and most have stopped noticing it, the way you stop noticing a commute. It is also why large referrals get quoted long turnarounds, or declined.

What does a 3,000-page case actually cost?

One case I prepared by hand had more than twenty provider bills across roughly 3,000 pages of scanned PDFs. Out of those 3,000 pages, about 150 were billing pages. Everything else was records, correspondence and duplicates. Finding those 150 meant paging through all 3,000, because there is no index and no reliable way to tell a billing page from a treatment note without looking at it.

The 150 billing pages produced more than 1,000 rows in a spreadsheet. Every charge line on every bill, every EOB and every ledger became a row: date of service, provider, code and billed amount, with columns waiting alongside for the fee schedule figure and the UCR benchmarks.

Three to four days, start to finish. None of it was analysis.

Why can the expert not start until the sheet is finished?

The opinion cannot begin until the sheet is done. Expert bill review splits cleanly into two jobs, assembly and opinion, and only the second needs the expert. Assembly comes first, so the expert waits behind it.

The first job is assembly. Locate the bills inside the record, capture every charge line accurately, and put the comparison figures next to them. It is careful work and it has to be right, but a trained assistant can do it, which is exactly why experts hire one as soon as their caseload makes it impossible to keep doing it themselves.

The second job is the opinion. The expert reads the recommended amounts against the fee schedule and the UCR benchmarks, decides what the charges should have been, and narrates that reasoning in a report she signs. That is the work the referring attorney is paying for. Software can help her write up a conclusion she has already reached, which is a different thing from reaching it.

The problem is the order. Job two cannot start until job one is finished. So the expert sits behind three or four days of data entry before she can spend three hours doing the thing she is qualified to do.

What does a transcription error cost?

Writing 1,000 rows by hand over three to four days produces errors. Not because the preparer is careless, but because attention is not a constant across several days and a thousand repetitions. I was good at this, and from memory (I kept no count) roughly one sheet in ten came back to me for correction. The most common correction was a missing bill.

There are two ways it goes wrong, and they cost very different amounts.

The error you catch yourself. You spot the transposed amount or the wrong date of service, you fix it, you redo the affected section. Time extends. Nobody outside the room ever knows. This is the visible, survivable failure, and it is why “the prep took three to four days” was always an understatement. It took that plus the loops.

The error nobody catches. The expert does not re-verify 1,000 rows against 150 source pages. That would defeat the entire point of having a preparer, and no expert has the hours for it. So an error in the sheet becomes an error in the recommended amount, and it rides into the signed report. The person who finds it is the referring attorney, after the report has been delivered.

That second failure is not a spreadsheet problem. The expert looks unreliable to the firm that sends her work, the report comes back for correction, and the next referral is smaller or does not arrive. In this business the cost of a wrong report is measured in future cases, not in rework hours.

Why is a missing bill worse than a wrong number?

A wrong number has a chance of being noticed. A figure that looks strange next to the fee schedule invites a second look, and an experienced reviewer has caught bad rows that way.

A bill that never made it onto the sheet has no such chance. There is nothing on the page to look wrong. It is not a row with a mistake in it, it is an absence, and an absence cannot be spot-checked. When you are hunting 150 billing pages inside 3,000, that is the mistake waiting to happen: not a mistyped amount, a provider whose bills you paged straight past at hour six.

That is why the one step I never skipped was searching every page for bills, rather than trusting an index.

This distinction should drive how any automated version of this work is designed, and it drives ours.

What changes when the assembly is automated?

Desk does the first job. It reads the full record, identifies the billing pages, extracts every charge line, and returns the spreadsheet with fee schedule and UCR benchmark columns already populated. The expert opens a sheet she did not have to build.

What that removes is the page-count penalty, the days of paging through a record to find the bills. The expert’s own work is unchanged: she still reads the numbers, forms the opinion, writes the report and signs it. Nothing signs itself, and the review step is not optional.

The practical effect is on capacity rather than on quality. An expert who can return a large report in days instead of weeks can accept referrals she used to decline. The opinion does not change. The calendar does. How AI review is built and where it fails is covered in AI medical bill review: what the model can and cannot do.

What happens when the system is not sure?

The design principle is deliberate: the cheap error is an extra row, and the expensive error is a missing bill, so the system is built to make the cheap one.

When a page is ambiguous, it goes in. When confidence on a line is low, the line is flagged in the sheet rather than dropped from it. The result is that a reviewer occasionally deletes something that should not have been captured, which takes seconds, instead of discovering months later that something was never captured at all, which cannot be fixed by looking harder at the sheet.

This is also the honest answer to the question every buyer asks, which is what happens when the system is wrong. The answer is that the expert catches it, the same way the expert has always been the last line, except that now she is reviewing a sheet she did not build at hour thirty of building it. The reasoning behind that design is the subject of why we are called System 2.

Where this does not help

We sell the thing described above, so treat the recommendation accordingly, and here is the case where it does not hold.

If your typical case is 40 pages with two providers, prep is not your bottleneck. You can build that sheet in twenty minutes and the arithmetic never favors changing anything. The work described here matters when page counts run into the thousands, when a single case has a dozen or more providers, or when you are already declining referrals because you cannot promise a date. Below that, an expert working alone with a spreadsheet is a perfectly good system, and we would rather say so than sell into a bad fit.