When “Reasonable” and “Necessary” Get Fought in the Same Breath

In a medical-damages dispute, two questions get asked in the same breath: was this treatment necessary? and was the charge for it reasonable? They sound like one question. They are almost always answered by two different people, using two different methods, who never compare notes — a physician or IME examiner on necessity, and a billing analyst, a bill-review vendor, or a legal nurse consultant on the charges. That division of labor is so standard that almost no one questions it. It is also the single biggest structural weakness in how medical bills get litigated.

I say that as someone who spent years on the payer side, where the two questions are not separable. A utilization reviewer deciding whether to authorize and pay a claim answers necessity and reasonableness in one motion, against one record, because in claims adjudication they are the same inquiry seen from two angles. Splitting them is an artifact of how litigation support evolved, not a reflection of how the analysis actually works.

The conventional division of labor

The standard setup looks like this. The clinical question — was the care medically necessary and related to the injury — goes to a physician, often through an IME or a records review. The money question — were the charges correct and reasonable — goes to a coder, a bill-review service, or an LNC who tabulates the charges and compares them to a fee benchmark. Two engagements, two reports, two methods, and eventually two witnesses. Each is competent within its lane. The problem is the space between the lanes.

Necessity is logically prior to reasonableness

Start with the most basic point: a service that was not medically necessary has no reasonable value — not a reduced value, no value, as a charge attributable to the injury. But a pure bill-review pass does not ask whether the service was necessary; it asks whether the charge matches the benchmark for that code. So a line that should be zeroed out on necessity grounds instead gets “repriced” to its benchmark amount and carried forward as if it belonged in the total. The charge review, done in isolation, quietly validates services the clinical review would have rejected. The two analyses have to be sequenced — necessity first, reasonableness on what survives — or the numbers do not mean what they claim to mean.

Over-utilization is a necessity question wearing a charge costume

Consider sixty chiropractic visits on a low-speed soft-tissue claim. A bill-review vendor sees sixty correctly-coded manipulations and prices them at the benchmark rate; on a pure charge analysis they may all look “reasonable,” because each individual charge is in line. The problem is not the per-unit price. It is that the documentation shows functional plateau by the twelfth visit — which means the next forty-eight were not necessary, and a charge for an unnecessary visit is exposure, not value. Only a reviewer applying necessity logic to the volume catches this. A charge analyst working from the fee schedule alone cannot, because nothing about the individual line is wrong. Over-utilization is invisible to charge review and obvious to necessity review, and it is one of the largest sources of inflated medical specials there is.

A charge for a service that was never necessary has no reasonable value at all.

Relatedness cuts across both

Then there is apportionment — the pre-existing or unrelated component. A claimant with degenerative disease documented before the collision accrues care afterward that treats, in part, the pre-existing condition. That care is simultaneously not related to the injury (a clinical judgment) and not reasonably charged to this claim (a charge judgment). The two findings have to agree. If the necessity report apportions thirty percent to pre-existing pathology while the charge report prices the entire course at benchmark with no apportionment, the reports contradict each other — and the contradiction is the first thing opposing counsel exploits. Relatedness is exactly the kind of question that lives in the seam between the lanes and gets dropped by both.

Coding integrity needs the chart

Even the parts that look purely clerical require both competencies. Was the level-four office visit supported by the documented history, exam, and decision-making, or should it be a level three? Did the manipulation actually involve the three-to-four regions the code claims, or one-to-two? Was imaging guidance billed separately when it was bundled into the injection code? These are coding questions whose answers live in the clinical record. A coder without fluent clinical reading cannot resolve them; a physician without coding fluency does not know to ask. The integrity check only works when one reviewer holds both halves.

The seam is what the other side litigates

Here is the practical consequence. When necessity and reasonableness come from two separate engagements, they produce two documents with two methods and two sets of assumptions — and any daylight between them is an attack surface. The cross-examiner does not have to defeat either opinion on its merits; they only have to show the jury that the necessity expert and the charge expert do not agree about the same record. Two reports can be played against each other. A single coherent opinion, in which the reasonable-value figure already reflects the necessity and relatedness findings, cannot be split that way, because there is no seam to pry.

What the bundled competency looks like

The alternative is one reviewer who does both in a single pass: applies utilization-criteria necessity logic to the record, identifies what was necessary and related, and then prices only that surviving care against a stated charge benchmark — the billed figure being, as a companion piece lays out, the least informative number on the page. The result is a single reasonable-value opinion that has already netted out the unnecessary, the unrelated, and the miscoded. That is what a Medical Charge & Necessity Review is: necessity, relatedness, coding integrity, and charge reasonableness combined in one physician-authored work product rather than split across a clinician and an analyst. For a plaintiff team it yields a clean, defensible floor for the specials. For a defense or carrier reader it yields a documented exposure figure with the apportionment already built in.

Who actually has this combination

The reason the split persists is that the combination is genuinely uncommon. Physicians are not trained in coding and charge benchmarking; coders and bill-review analysts are not licensed to opine on medical necessity. The people who sit naturally at the intersection are physicians who have done payer-side utilization work, where necessity and payment are decided together, thousands of times. That is the background the bundled review is built on — and on the litigation side, where the two questions are still usually handed to two different vendors, it is the wedge.

None of this replaces a testifying expert. The bundled review is non-testifying, attorney-directed work product; where a sworn charge opinion is required, it is carried to a US-credentialed coding expert or a testifying physician. The point is not who testifies. It is that the analysis underneath the testimony should be one coherent thing — because the other side fights reasonableness and necessity in the same breath, and a report that answers them separately is already losing an argument it did not know it was having.