Lesson 07 — Ward base consumables flow in but don't bill out

That’s not a revenue leak. That’s the operational compromise.

The I/O signal — material movements in versus billed events out — is one of the most powerful diagnostics in the pack. It surfaces materials that enter the ward but never make it onto an invoice. The first interpretation is revenue leakage, and for many materials that interpretation is correct.

But a substantial fraction of the I/O gap is intentional: ward base consumables. Gauze, syringes, gloves, alcohol swabs, basic dressings. Materials that flow into the ward continuously, get consumed continuously, and are deliberately not billed per-event.

Why they don’t bill

Three operational reasons converge:

• The per-event admin cost exceeds the per-event revenue. Tracking each gauze pack to a specific patient encounter would require effort whose CHF cost exceeds the gauze’s billable value.
• Patient-mix unfairness. A patient who happens to need ten swabs during a routine encounter shouldn’t pay materially more than an otherwise-equivalent patient who needed eight. Per-event billing on commodities produces dispersion that doesn’t track clinical severity.
• Bundled into ward day rate. The ward day rate (and the case’s DRG) is calibrated to absorb base consumable cost. The hospital’s CFO knows the rate covers it; the billing system reflects that.

The result: gauze flows in, gauze gets used, gauze does not appear on the invoice. The I/O signal sees the input, doesn’t see the output, and flags it as leakage.

What changed in the analysis

The signal didn’t change. The reading changed:

1. A whitelist of base consumables lives as a per-tenant 50cents — items whose I/O gap is structural and expected. The signal still fires on them; the Explorer surfaces them with a “ward base consumable” badge instead of a leakage alert.
2. signal_revenue_leakage filters them out by default. Operators can include them when investigating specific patterns, but the default view excludes the structural noise.
3. thesis_revenue_leakage_unbilled reports two numbers: total I/O gap (the raw measure) and adjusted gap (after subtracting base consumables). The adjusted number is the one that gets the headline; the raw number is available for completeness.

The order matters. The first version of the thesis reported only the raw number, and CFOs read it as “this hospital is leaking N CHF a year in unbilled materials”. That number was technically correct and operationally misleading. The Wisdom is what corrected the framing.

What stays interesting

• A new item appearing in the I/O gap that isn’t on the base-consumable whitelist is a real leakage candidate. The whitelist is the noise filter; the actionable findings are everything outside it.
• A base consumable whose I/O gap is growing faster than ward census can indicate either over-stocking (procurement issue), under-use (clinical change), or theft. Trend matters even when absolute values are structurally non-billable.

Why this is in a Lessons journal

Because the I/O gap is the cleanest example of “the same data shape means different things at different scales”. A 5% gap on a high-value implant is revenue leakage. A 100% gap on a gauze pack is operating policy. The signal cannot distinguish them on shape alone. The Wisdom is what teaches it which is which.

Sources

• Wisdom: smebit_ward_base_consumables.yaml
• Provider: a hospital CFO with multi-site finance responsibility
• Anchor signals: signal_io_coefficient, signal_revenue_leakage
• Anchor thesis: thesis_revenue_leakage_unbilled
• Date Wisdom captured: 2026-05-08