Case Study 2 — Ninety Days That Belonged to Somebody Else: A Composite

DataField.Dev

Case Study 2 — Ninety Days That Belonged to Somebody Else: A Composite

Constructed. The two practices, the patient, and the figures are not real. The collision — two organizations both reporting global fracture care for the same fracture — is ordinary, and the reason it is ordinary is that neither organization can see the other's claim.

Background

Section 17.7 described the fracture-care decision as a genuine fork with no default: global fracture care, carrying a 090-day global period that swallows all follow-up, or an E/M plus a splint, carrying nothing.

Then §17.7's ⚠️ Where Claims Die said what happens when two physicians both choose the first one.

This is that, followed all the way through — including the part that lands on the patient.

What happened

Constructed.

Saturday. A man in his forties falls from a ladder and fractures his distal radius. He goes to an emergency department. The emergency physician examines him, obtains radiographs, reduces the fracture, applies a splint, and refers him to an orthopedic group for follow-up the following week.

The emergency group's billing system reports global fracture care with manipulation. It has done so for years. The macro was written when the group's coding lead — long since departed — reasoned that a reduction is fracture treatment, and a reduction is what happened.

Wednesday. The orthopedic surgeon sees him, confirms the reduction, applies a cast, and accepts him for management through healing. The orthopedic group reports global fracture care.

Two claims. One fracture. Two 090-day global periods.

What the payer did

The emergency group's claim was submitted Monday and adjudicated first. It paid.

The orthopedic group's claim denied, as a duplicate of a service already paid to another provider.

And then the second consequence, which nobody anticipated: the orthopedic group's subsequent visits — the two-week check, the cast change at four weeks, the final visit at ten weeks — also denied, as falling within a global period established by somebody else's claim.

   TIMELINE

   Sat   ED: reduce, splint, refer      → global fracture care  PAID
   Wed   Ortho: cast, accept management → global fracture care  DENIED (dup)
   +2wk  Ortho: follow-up               → DENIED (in global period)
   +4wk  Ortho: cast change             → DENIED (in global period)
   +10wk Ortho: final visit             → DENIED (in global period)

   The orthopedic group provided 90 days of care and was paid for none of it.

Who was right

The orthopedic group. Straightforwardly.

The emergency physician reduced and splinted a fracture and referred the patient away the same evening. They did not undertake ninety days of fracture management, and reporting global fracture care asserted that they had. The correct reporting for the emergency encounter was an E/M service plus the splint application and supply — §17.7's option (B), which is exactly the situation option (B) exists for.

And the emergency group was not being dishonest. A reduction is fracture treatment. The reasoning behind the macro was not stupid; it was incomplete. It answered "was a fracture treated?" when the question is "who is providing the definitive care?"

Why it took four months to resolve

Neither group could see the other's claim. This is the structural fact underneath the whole story.

The orthopedic group's biller worked the first denial as a duplicate, could not find a duplicate in her own system, and appealed. The appeal was denied. She worked it again. She called the payer, who told her a global fracture care service had been paid to another provider — but would not, at first, tell her which one.

Meanwhile the follow-up denials accumulated, each one arriving weeks after the visit, each one looking like a separate problem, each one entering the work queue as a new item. Chapter 29 §29.4's denial-classification discipline is the difference between recognizing this as one root cause and working it as five unrelated denials — and this practice worked it as five.

By the time the two groups spoke to each other, four months had passed and the orthopedic group's timely filing window for a corrected claim had closed on the earliest visits.

Where the patient came in

Not at the start. At the end, which is the worst place.

The orthopedic group's billing system, having exhausted the payer, moved the balances to patient responsibility — which is what most systems do, automatically, when a payer denies and appeals are exhausted.

He received statements for care his insurance should have paid for, four months after the fact, for a fracture that had healed. He called the orthopedic office, who told him it was an insurance problem. He called his insurer, who told him it was a provider problem. Both statements were true and neither was useful.

The balances were eventually written off. He had spent six hours on the telephone, and he told everyone he knew that both organizations had billed him incorrectly — which was, from where he sat, exactly what happened.

What it shows

First, a global period is a claim on the future, and it is asserted against a patient rather than against a practice. When the emergency group reported fracture care, it did not merely bill a service. It reserved ninety days of that patient's follow-up, including follow-up it had no intention of providing and no knowledge that anyone else would.

Second, the collision is invisible from inside either organization. Neither group's system contains the other's claim. There is no shared queue, no alert, and no mechanism. The payer is the only party who can see it, and the payer sees it as a duplicate rather than as a coordination failure.

Third, a denial reason that says "duplicate" can mean "somebody else's claim." Billers are trained to look internally for duplicates. This one was external, and the four months are mostly explained by the time it took to stop looking in the wrong place. Chapter 28 §28.4's discipline — read the CARC and RARC together, and ask what the payer actually saw — is the whole shortcut.

Fourth, the automatic move to patient responsibility is the failure that turns an administrative dispute into a person's afternoon. The system did what it was configured to do. Nothing in the configuration asked whether the denial was the patient's fault, and Chapter 28 §28.10 argues that this one check — is this balance genuinely the patient's? — belongs in front of every automated transfer.

And fifth, both organizations were competent. This is the fourth case study in a row where that is true. Chapter 15's practice was competent, Chapter 16's hospital was competent, Chapter 17's orthopedic group was competent. The failures in modern revenue cycle are overwhelmingly not failures of care or of skill. They are failures of coordination, configuration, and nobody owning the seam.

The lesson

Reporting global fracture care claims ninety days of a patient's care. Do not claim what you are not providing.

Four carry-forwards:

Write the rule down, by setting. In an emergency department, in urgent care, in a primary care office: when is fracture care reported and when is it an E/M plus a splint? It is one paragraph, it resolves a recurring dispute, and almost nobody has it.

Never let a macro make the fracture-care decision. It is a judgment about who is managing the patient, and no macro has that information.

When a denial says "duplicate" and you cannot find one, look outward. Ask the payer which provider and which date. They will usually tell you, and it collapses four months into one call.

And put a check in front of the automatic transfer to patient responsibility. The patient in this composite did nothing, owed nothing, and spent six hours on it. He is also the only party in the story who will remember it in five years.

Discussion questions

The emergency group's macro was based on real reasoning: a reduction is fracture treatment. Write the one sentence that makes the reasoning complete, and say where that sentence should live.
Neither organization could see the other's claim, and there is no mechanism that would let them. Is this solvable? Sketch what a solution would require, and say honestly whether it is worth building.
The orthopedic group worked five denials as five problems. Design the classification rule that would have collapsed them into one. What would the biller have had to notice?
The balances moved to patient responsibility automatically. Write the check you would put in front of that transfer. What does it cost, and what does it catch besides this?
Four consecutive case studies now feature competent organizations failing at a seam. Is that the book being fair, or the book making an argument? If it is an argument, state it, and say whether you find it persuasive.