Skip to content
Insights · Field Notes

The Five-Layer Diagnostic
as a weekly series.

Twenty-five essays across five layers of hospital performance. What leadership teams can't see, shouldn't tolerate, and can fix without adding a single FTE. Published weekly since September 2025.

  1. PRIME · The Encounter Layer

    Day One or Day Three.

    The single most predictive marker of a patient's downstream length of stay is not their clinical complexity, their age, or their comorbidity burden. It is whether a treatment plan has been documented by end of admission day one — or whether it takes until day three for the admission to acquire operational direction.

    9 min read →
  2. ORBIT · The Population Layer

    The Top 5 You Haven't Called.

    Your top five referring physicians drive roughly forty percent of your elective volume. You probably cannot name all five from memory, you almost certainly cannot produce their mobile numbers, and you have definitely not called them this quarter. The gap is one of the cheapest operational blind spots a department runs — and one of the most consequential.

    9 min read →
  3. ORBIT · The Population Layer

    Fingerpointing Is Data.

    When one function in a hospital blames another, most leadership teams treat the blaming as interpersonal conflict to be managed. The blaming is usually something else entirely: a reliable signal of where structural handoffs have become unowned gaps — and a precise pointer to the operational remediation that would close them.

    9 min read →
  4. ANCHOR · The People Layer

    Clinical M&M, Operational M&M.

    The morbidity-and-mortality review is universal. Every department in every teaching hospital runs one every month. The equivalent review for operational failures exists almost nowhere — and the asymmetry tells you more about what the profession takes seriously than any strategic document ever will.

    10 min read →
  5. CAPTURE · The Revenue Layer

    The Compensation Structure That Rewards What You Don't Want.

    Every other piece of CAPTURE-layer work — the coding rhythm, the nursing documentation, the ambulance-ramp handover, the human-fallout attention — can be undone by a compensation architecture that quietly rewards the opposite of what it says it rewards. The closing post in the series: the final operational variable.

    11 min read →
  6. FLOW · The Improvement Layer

    The Board Agenda That Tells You Everything.

    Pull the last six board or Geschäftsführung agendas. One of four signatures will dominate. The signature that dominates is the single cleanest diagnostic you can run on where your hospital actually sits — without asking anyone to describe themselves.

    10 min read →
  7. PRIME · The Encounter Layer

    The 60-Second Handover Test.

    If the receiving team cannot answer three specific questions about every patient within sixty seconds of the handover ending, you are paying twice for the same information — and the second payment is nearly always in patient-safety currency.

    10 min read →
  8. ORBIT · The Population Layer

    Pathways That Don't Survive Morning Round.

    Documented treatment protocols exist in every German hospital. The question is whether they survive first contact with the ordinary Tuesday ward round — and why the three structural moves that make them survive have nothing to do with the document itself.

    10 min read →
  9. ANCHOR · The People Layer

    What Staff Know That Reports Don't.

    Fifteen minutes of unannounced ward walking routinely surfaces operational problems that six months of controlling reports never surface — and the gap is not a failure of reporting but a structural feature of what reports can and cannot show.

    9 min read →
  10. CAPTURE · The Revenue Layer

    The Named Human Fallout of Every Miscoded Case.

    Every conversation about coding in this series has been a conversation about revenue. This one is about the four named humans — nurse, coder, clinician, controller — who each pay a specific cost when the coding fails, and what happens when those costs compound across three years.

    11 min read →
  11. FLOW · The Improvement Layer

    The Capital Request That Should Have Been a Rota Change.

    Most hospital capital requests are correctly described at the symptom level and incorrectly diagnosed. Four questions, asked before the business case is written, reroute a meaningful fraction of them to operational redesign — at a fraction of the cost.

    10 min read →
  12. PRIME · The Encounter Layer

    The Admission Door You Built by Accident.

    Why sharing one admission door between elective and emergency streams costs roughly a day of throughput per patient — and why three specific architectural moves can recover it without additional headcount.

    10 min read →
  13. ORBIT · The Population Layer

    Three Cohorts, Named.

    The single operational move that turns "we see complex patients" into a working strategy — and why naming just three, specifically and accountably, is more valuable than naming ten aspirationally.

    9 min read →
  14. ANCHOR · The People Layer

    Succession Theatre.

    The difference between hospitals that have named successors and hospitals whose named successors know they are named — and why the gap is the entire diagnostic.

    10 min read →
  15. CAPTURE · The Revenue Layer

    The First Words on the Ambulance Ramp.

    The paramedic's handover phrase determines what DRG you code six days later. Most hospitals never audit this interface — and systematically under-code the complex patients it describes.

    10 min read →
  16. FLOW · The Improvement Layer

    Weekend Discharge Isn't a Staffing Problem.

    Hospitals with weekend discharge rates below 25% assume the constraint is staff availability. It is architecture — specifically, authority, therapy access, and medication reconciliation.

    10 min read →
  17. ANCHOR · The People Layer

    The Three-Number Test.

    What leadership teams who cannot recite turnover, overtime, and sick leave from memory are actually admitting — and why those three numbers together describe the condition of your workforce more honestly than any engagement survey.

    9 min read →
  18. PRIME · The Encounter Layer

    Hunting, Not Judgment.

    The physician-time leak that nobody measures — and why the right response is operational hunting, not performance management.

    11 min read →
  19. ORBIT · The Population Layer

    The Top 10 You Cannot Name.

    Why most hospitals optimise for imaginary patients — and why the operational strategy only starts when you name the ten cohorts that actually show up.

    10 min read →
  20. FLOW · The Improvement Layer

    Why 70% of Hospital Improvements Die.

    Most hospital improvement programmes fail in the same phase, for the same reason — and the one operational rhythm that stops it is specific, installable, and almost never installed.

    12 min read →
  21. CAPTURE · The Revenue Layer

    The OPS Code Your Nursing Team Is Leaving on the Table.

    8-550 complex geriatric treatment is the single most under-captured code in German hospitals. A two-week documentation audit typically reveals six to eight figures annually in recoverable revenue — and the pattern repeats across ICU, stroke, and cardiac complex-treatment codes.

    11 min read →
  22. CAPTURE · The Revenue Layer

    The 24-Hour Coding Loop.

    11 min read →
  23. CAPTURE · The Revenue Layer

    Coding at Discharge Is Already Too Late.

    The clinical-coding rhythm that changes everything — and why most hospitals have never built it.

    10 min read →
  24. FLOW · The Improvement Layer

    The Gentlemen's-
    Agreements Test.

    10 min read →
  25. ANCHOR · The People Layer

    The Second Customer.

    9 min read →
Read as a complete series

The Five-Layer Diagnostic is designed as a complete operating system. ANCHOR (people) describes what leadership cannot see in the workforce. ORBIT (population) names what a hospital actually does. PRIME (encounter) fixes the admission, round, and handover rhythms. FLOW (improvement) holds changes in place. CAPTURE (revenue) converts clinical reality into accurate coding. Read in order for the argument; read by layer for the operational detail.

ANCHOR 5 posts
ORBIT 5 posts
PRIME 4 posts
FLOW 5 posts
CAPTURE 6 posts
Phase A · Operational Scoping

After twenty-five essays, the obvious question.

Phase A is the operational translation of what the insights argue. Four weeks, structural diagnosis across the five layers, specific recommendation. Ten engagements per quarter — currently booking Q3 2026.