Case Study 1 — The Standing Order: A Composite

Constructed. The practice, the patient, and the figures are not real. Standing orders that outlive their clinical reason are ordinary, and the pattern — repetitive testing on a recurring order with no contemporaneous documentation of necessity — is a documented enforcement priority.

This is the first case study in this book where the problem is not how a service was coded. The problem is that the service happened at all.**

Background

Section 19.5's ⚖️ Compliance Check named it in one sentence:

A standing order for a monthly panel, entered once, renewed automatically, generating tests nobody is reading.

Then it said the thing that makes it a compliance problem rather than a waste problem: the claim asserts medical necessity, every month, on every test.

The composite

Constructed.

An internal medicine practice. A patient with several chronic conditions, managed conscientiously, seen every three months.

At an encounter several years ago the physician entered a standing order for a monthly laboratory panel. At the time it was clearly appropriate — the patient had started a medication requiring close monitoring and the plan was to follow specific values closely for a few months.

The medication was discontinued eight months later.

The standing order was not.

What happened next

Nothing dramatic, which is the point.

The patient came in monthly for a blood draw. She assumed it was part of her care, because it was ordered by her physician and nobody ever told her otherwise. She is a conscientious patient; she never missed one.

The panel ran. The results posted. They were normal, or normal-for-her, every time.

And nobody read them — not in the sense of nobody opening the result, but in the sense that no clinical decision was ever made on the basis of one. The results entered the chart, were auto-acknowledged, and were never referenced in a note.

The claims paid. Every month. Clean, correctly coded, correctly billed by the reference laboratory, with the physician's identifier in the referring provider field.

What it looked like from each side

From the practice: nothing. No claim was submitted by the practice for the tests — the reference laboratory billed them. The practice's only involvement was a venipuncture and a standing order in the system.

From the laboratory: a recurring order from a physician, entirely ordinary.

From the payer: monthly testing on a chronic patient, which is common and is not by itself a finding.

From the patient: a routine, part of her care, plus a coinsurance amount every month for four years that she paid without question because her physician had ordered it.

She is the only party in this composite who paid for the failure, and she is the only one who had no way to know.

How it surfaced

A payer's utilization review, comparing testing frequency against documented clinical indications. Not an audit of the practice — an inquiry to the physician, asking for the documentation supporting monthly testing.

There wasn't any. Not because the practice had hidden it, but because there was nothing to document. The reason had ended four years earlier and nobody had gone back to the order.

What it cost

(Constructed.)

The laboratory faced repayment exposure for tests billed without documented medical necessity — even though the laboratory performed exactly what was ordered, correctly, every time. A laboratory generally bills based on the order it receives. It is not in a position to evaluate whether the ordering physician's clinical reasoning still holds.

The practice faced a documentation and utilization finding, a corrective action requirement, and the particular discomfort of a physician being asked to explain an order they did not remember entering.

The patient had paid four years of coinsurance on tests that should not have been performed. She was refunded some of it. What she was not refunded was four years of monthly blood draws.

What it shows

First, every other failure in this book is about a service that happened being described wrongly. This one is about a service that should not have happened. That is a different category, it is the category that medical necessity governs, and it is the one that Chapter 22 exists for.

Second, a standing order is a configuration that makes an assertion. This is the seventh in Part III — after auto-appended modifiers, a prefilled time default, reimplemented leveling logic, a modifier 59 macro, a fracture-care macro, and an automatic KX modifier. Every month, a claim went out asserting that this testing was reasonable and necessary. Nobody made that assertion. A system made it, on behalf of a physician, on the strength of a decision made four years earlier.

Third, the laboratory could not have caught it and the practice had no reason to look. The laboratory receives an order and fills it. The practice sees a patient every three months and does not review its own standing orders, because nothing prompts it to. The information required to notice was split between two organizations, and neither half is sufficient.

Fourth, "nobody read the results" is the diagnostic sign, and it is findable. A result that is never referenced in a note, month after month, is a result that is not informing care. That is queryable in most electronic records — and almost nobody queries it.

And fifth, the patient's cost is the one that does not appear in any settlement. She was refunded money. She was not refunded four years of Tuesday mornings, or the small ongoing anxiety of a person who believes she requires monthly monitoring. This is the third case study in four chapters where the person who behaved correctly is the one who paid, and by now that is a pattern the book is obligated to name rather than merely keep illustrating.

The lesson

A standing order is a decision that keeps being made after the person who made it has stopped thinking about it.

Four carry-forwards:

Standing orders need expiration dates. Not review reminders — expirations, which force a decision rather than inviting one. A standing order that expires is renewed deliberately or it stops.

Review recurring orders at a defined interval, and make the review a clinical one. The question is not "is this order still in the system." It is "what decision would a result change?" If the answer is none, the order should end.

Query for results that are never referenced. It is a report most electronic records can produce, it identifies exactly this pattern, and it costs nothing to run.

And ask the patient. "Do you know why you're having this drawn every month?" is a question anyone in the practice can ask, and in this composite it would have surfaced the problem in about fifteen seconds at any point across four years.

Discussion questions

1. The laboratory performed and billed exactly what was ordered. Should it bear repayment exposure? Argue both sides, then say what a laboratory could reasonably be expected to do.

2. This is the first failure in the book where the service itself, rather than its coding, was the problem. Does that make it a coder's concern at all? Where exactly does a coder's responsibility begin and end here?

3. Design the expiration mechanism for standing orders. What is the right interval, who renews, and what happens to the order in the meantime?

4. "Nobody read the results" is the diagnostic sign. Write the query that finds it, in plain language. What is the false-positive rate, honestly, and who reviews the output?

5. Three case studies in four chapters have featured a patient who did everything right and paid for a failure they could not see. Name the structural feature they share. Then say whether it is fixable, or only mitigable.