Case Study 2 — Three Days and a Corporate Chart: A Composite

Constructed. The health system, the practices, and the figures are not real. The failure — a rule that reaches "wholly owned or operated" entities, applied by an organization that had grown faster than anyone's mental model of it — is ordinary, and it is Chapter 20's Case Study 2 at institutional scale.

Background

Section 26.8 stated the rule and then added a clause that is easy to read past:

Outpatient services furnished by a hospital — OR A WHOLLY OWNED OR OPERATED ENTITY — within three days before an inpatient admission are, in defined circumstances, bundled into the inpatient claim.

The clause is the case study.

The composite

Constructed.

A regional health system. Over several years it acquires physician practices — a common strategy, well executed, and entirely lawful.

By the end of the acquisition period it owns a substantial number of outpatient sites, some converted to provider-based departments and some operating as owned physician practices under a different structure.

The system's billing is competent and it is departmental. The hospital's business office bills hospital claims. The acquired practices bill their own professional claims, largely on the systems and workflows they had before acquisition, because that is how acquisitions actually work.

What nobody connected

The three-day payment window reaches owned entities.

When a patient received outpatient services at one of the acquired sites and was admitted to the system's hospital within three days, those services were, in defined circumstances, supposed to be bundled into the inpatient claim rather than billed separately.

They were billed separately, because:

The practice did not know it was inside the window. From the practice's point of view it had provided an outpatient service and billed for it, exactly as it had for years.

The hospital did not know the practice existed in this sense. Its bundling logic looked at services furnished by the hospital's own departments, which is where the rule is usually implemented.

And nobody held both facts. The ownership structure lived in finance and legal. The bundling logic lived in a billing system. The two had never been introduced.

The scale problem

(Constructed.)

Any single instance is small. An office visit or a diagnostic study, billed separately when it should have been bundled.

The volume is what makes it a case study. A system with many owned sites and a hospital with many admissions produces a steady rate of patients who touch both within three days — and the rate is higher than intuition suggests, because a patient who is admitted has frequently been seen outpatient shortly before. That is what the rule is about.

Over the period, the accumulated separately billed services were substantial.

How it surfaced

A payer's data.

(Constructed.) The payer's own analytics identify outpatient claims from entities it associates with the admitting hospital's ownership, falling within three days of an inpatient admission, billed separately.

The payer knew the ownership structure — because the system had reported it, correctly, through enrollment and disclosure processes.

Chapter 23's Case Study 1 ended the same way: an organization informed a payer of a change it had not implemented in its own systems. This is that, at the level of an entire corporate structure.

What it cost

(Constructed.)

Repayment of the improperly separated services, across the review period.

And a remediation project that was genuinely hard, for a reason worth naming: the fix requires the hospital's admission data and the practices' service data to be compared, in near real time, against an ownership list that changes.

Three components:

An accurate, maintained list of owned and operated entities — which sounds trivial and is not, in an organization that acquires and divests.

A mechanism to hold outpatient claims from those entities long enough to see whether an admission follows within three days.

And a process for the diagnostic versus non-diagnostic distinction, including the attestation mechanism for unrelated non-diagnostic services.

What it shows

First, the rule is about a corporate relationship, and corporate relationships change faster than billing systems. Chapter 20's Case Study 2 was a practice that became a supplier without noticing. This is a health system that became a different kind of entity, repeatedly, over several years — and the billing logic reflected the organization as it was at implementation.

Second, "wholly owned or operated" is a legal phrase doing operational work, and nobody in either billing office was positioned to interpret it. The people who knew the ownership structure did not know the billing rule; the people who knew the billing rule did not know the ownership structure. Chapter 23's Case Study 1 had the same shape between two departments; this one has it between two professions.

Third, the payer knew. It knew because the system had told it. An organization can be in a position where the most complete picture of its own structure is held by a counterparty — which is uncomfortable and is a direct consequence of enrollment and disclosure obligations working correctly.

Fourth, the remediation was harder than the violation. The improper claims were easy to describe and repay. Preventing recurrence required a maintained ownership list, a claim-holding mechanism, and a clinical distinction — and the first of those three is a governance problem that no billing system solves.

And fifth, this is the second time in this book that a growth decision created a compliance obligation nobody assigned. Chapter 20's practice stocked braces. This system acquired practices. Both were good decisions, made for good reasons, by people who were not asked "what does this change about how we bill?" — and the question has an answer, every time, and almost nobody asks it.

The lesson

Every acquisition, conversion, closure, and divestiture changes what your claims should say. Somebody has to be assigned to say what.

Four carry-forwards:

Maintain a current list of owned and operated entities, and give it to billing. Not to finance only — to the people whose logic depends on it. It is the single artifact this entire composite turns on.

Put "what does this change about how we bill?" on the transaction checklist. Chapter 23's Case Study 1 said the same about a conversion; this says it about an acquisition, and the answer is never "nothing."

Implement the window against the list, not against the hospital's departments. The rule reaches owned entities, and a bundling check that looks only at internal departments is implementing a narrower rule than the one that governs.

And know that the payer has the picture. Enrollment and disclosure obligations mean your counterparty's model of your organization may be more current than your own systems' — which is an argument for reconciling the two deliberately rather than discovering it in a recoupment.

Discussion questions

1. The ownership structure was in finance and legal; the bundling logic was in a billing system. Who should own the connection? Name a role, and say whether it exists in organizations you know.

2. The remediation required a maintained ownership list. Why is that a governance problem rather than a technical one?

3. The payer had a more current picture of the system's structure than the system's own billing logic did. Is that surprising? What does it follow from?

4. Compare this with Chapter 20's Case Study 2, where a practice became a DMEPOS supplier without noticing. What is the same, and what does scale change?

5. "What does this change about how we bill?" has an answer for every acquisition, conversion, closure, and divestiture. Why is it almost never asked — and what would have to be true for it to become routine?