Case Study 1 — The Rest of the Vial: A Composite

Constructed. The practice and the figures are not real. The pattern — waste reported by formula rather than by observation — is a documented enforcement area, and the detection method is the one thing in this book that finds a billing error using no medical records at all.

Background

Section 20.4 ended a list of rules with a sentence that reads like a technicality:

"We always bill the rest of the vial" is a formula, and §20.4 exists because formulas are not observations.

This is what the formula produces over three years.

The composite

Constructed.

A specialty practice administering injectable drugs at volume. Competent billing, low denial rate, and — the part that matters — a written internal policy about drug waste, adopted years earlier by someone acting in good faith.

The policy said, in substance: when a vial is opened for a patient, bill the administered amount on the drug line and the remainder on a JW line.

That is correct for single-dose vials. It is the rule, stated plainly.

The practice applied it to every vial.

What went wrong, in three ways

Multi-dose vials. A multi-dose vial holds doses for more than one patient. Its remainder is not waste — it goes back on the shelf and is used the next day. Every JW line reported from a multi-dose vial asserted a discard that did not happen.

Doses that used the whole vial. When the administered dose consumed the entire container, there was nothing left. The billing system, following the policy, generated a JW line anyway — computed as "vial size minus dose," which in these cases was zero, and which some claims carried as a rounded-up unit.

And a genuine misunderstanding about what a "vial" is. Some drugs are supplied in packages containing several vials. The policy's author had meant "container." The system had implemented "package."

Why nobody noticed

The JW lines paid. Waste is payable, correctly, when it occurs. There was no edit, no denial, and no correspondence.

The claims were internally consistent. Administered units plus discarded units equaled the vial size — which is exactly the arithmetic check §20.4 recommends, and it passed, because the system was computing both numbers from the same assumption. A check that both sides of an equation derive from cannot detect that the assumption is wrong.

Coders were not making the decision. The waste line was generated by the system from the drug line. Nobody was reading a vial size and forming a judgment, which is the entire failure and which is one more instance of something this book has now said about a configuration in every part of it.

And the policy existed in writing, which made it look like a control. A written policy that implements the wrong rule is not a control. It is a wrong rule with a document.

How it was found

Not from any medical record.

A payer's program integrity unit compared, for a set of drugs, the total units billed by the practice against the total units the practice could plausibly have purchased, using publicly available information about how those drugs are packaged.

The billed units exceeded any plausible purchase volume, consistently, by roughly the amount the formula was inventing.

Then the request went to the practice's purchasing records — invoices, not charts. The two numbers did not reconcile, and the gap was the JW lines.

No chart was ever reviewed. This is worth sitting with: an entire finding, quantified and defensible, from claims data and invoices.

What it cost

(Constructed.) Three years of overpayment on the invalid waste lines, repaid with interest, plus a corrective action plan requiring the practice to demonstrate a compliant process.

And a second cost that is not a number. The practice had a written drug waste policy, followed it faithfully, and was found to have overbilled for three years. Its people had done exactly what they were told, which makes remediation harder rather than easier — you cannot fix this by telling the staff to be more careful, because carefulness is what produced it.

What it shows

First, a formula is not an observation. Waste is a physical event that either happened or did not. A system computing "vial size minus dose" is not reporting what happened; it is reporting what would have happened if an assumption held, and the assumption held for some vials and not others.

Second, JZ would have prevented this. Not by itself, but by forcing the question. A modifier meaning "zero discarded" requires somebody to determine that zero was discarded — and a determination is exactly what a formula skips. This is the argument for mandatory documented negatives in a single example, and Chapter 17 §17.7 made the same argument from the documentation side.

Third, the arithmetic check passed and was worthless. Administered plus discarded equaled the vial size, every time, because both numbers came from the same assumption. A reconciliation between two figures derived from one source proves nothing — and this is a general lesson that applies well beyond drug billing, to every "the numbers tie out" comfort in a revenue cycle.

Fourth, the detection used purchasing records. Chapter 15's Case Study 2 found a problem by summing documented time against the hours in a day. This one found a problem by comparing units billed against units purchasable. Both are physical constraints, both are checkable without any chart, and both are available to the organization itself.

And fifth, a written policy is not a control if the policy is wrong. The practice's policy was the proximate cause and simultaneously the thing that made everyone confident. Ask what a policy asserts, not whether it exists.

The lesson

Waste is an observation, not a calculation. If nobody looked at what was left, nobody knows what was discarded.

Four carry-forwards:

Reconcile units billed against units purchased. Monthly, on your highest-volume drugs. It requires no charts, both numbers already exist in your systems, and it is the second technique in this book you can run in an afternoon — after Chapter 15's time summation and Chapter 17's modifier frequency report.

Never compute a JW line from a formula. The waste line's units come from what was discarded. If your system generates it, verify what it is generating it from, and verify it against a container rather than a package.

Use JZ deliberately. It is a required attestation and it is also a forcing function: you cannot attest that nothing was discarded without determining that nothing was discarded, which is the whole point.

And audit your own written policies against the rule. Not whether they are followed — whether they are right. In this composite, compliance with the policy was excellent.

Discussion questions

1. The practice followed its own written policy faithfully and overbilled for three years. Where does responsibility sit — with the policy's author, the system's implementer, the coders, or the practice? Defend a specific answer.

2. The arithmetic check passed every time and proved nothing. Name two other places in this book where a reconciliation could pass while both sides are wrong.

3. The detection used purchasing records rather than charts. What other billing questions could be answered from inventory data? Are any of them worth building?

4. The chapter argues JZ is a forcing function. Is a mandatory attestation a good general mechanism, or does it eventually become another box that gets checked? Argue both, then say what determines which it becomes.

5. Compare this with Chapter 19's Case Study 2, where an optional field caused an underpayment. Here an automatic field caused an overpayment. State the design principle that covers both.