On , a single spark in the basement of the John E. Hurst & Company building in Baltimore ignited a blaze that would eventually consume 1,500 buildings. The tragedy of that day wasn’t a lack of effort.
When the call went out, fire departments from Washington, D.C., Philadelphia, and even New York City loaded their engines onto flatbed railcars and raced to the scene. They had the water. They had the men. They had the will.
But when they arrived, they discovered a catastrophic technicality: their hoses would not fit the Baltimore hydrants. The threads were different.
While the city burned, hundreds of the bravest men in the country stood by with high-capacity pumps that were useless because the coupling between the source and the delivery was off by a fraction of an inch.
The Anatomy of the Whiteboard Lie
We see this same fire every January in the world of healthcare reporting. We call it a “deadline crisis,” but that’s a polite lie. The real failure happened months earlier, in the quiet spaces between departments, where the couplings didn’t match.
I recently sat in a conference room where the “Whiteboard Lie” was on full display. On the wall was a dry-erase pipeline from a strategy meeting held the previous September. It was a beautiful thing: five tidy boxes, four crisp arrows, and the initials of every department head assigned to their respective stations.
It looked like a Roman aqueduct-sturdy, linear, and inevitable. On the table sat the reality: a printout showing 312 encounters that should have qualified for MIPS reporting, but only 190 that actually made it into the registry.
The missing 122 encounters represent a 39% data leak in the administrative “arrows.”
Nobody in that room could tell me where the other 122 went. They looked at the boxes. The billing manager pointed to the “Coding” box; the clinical lead pointed to the “Intake” box. But the data didn’t die in a box. It died in the arrows. It died in the handoffs that nobody owns because they aren’t “steps”-they are the seams.
Data is Not Water
I force-quit my reporting software seventeen times this morning because it kept hanging on a validation error that shouldn’t exist. It’s a rhythmic, digital insolence that reminds me why we fail: we assume that if we perform the tasks, the data will naturally flow.
It doesn’t flow. It has to be pushed, and every time you hand it to someone else, you lose a handful.
The first invisible failure happens at the front desk, usually during a Tuesday morning rush. It’s the “Field Skipped” handoff. A patient arrives, the waiting room is six deep, and the registrar skips the tobacco screening or the updated medication list because “we’ll get it in the back.”
But the back assumes the front did it. The EHR doesn’t flag it as a hard stop because the clinic manager didn’t want to slow down patient flow. That single skipped click isn’t a failure of clinical care-the patient still gets treated-but it is a fatal break in the reporting chain. The data was never born, so it can’t be reported.
The Paradox of the Heroic Workaround
Then there is the “Heroic Workaround.” I see this most often with clinicians who are, ironically, too good at their jobs. They find the EHR’s measure-specific template cumbersome, so they write a brilliant, detailed clinical note in a free-text field.
To a human, it’s a masterpiece of diagnostic reasoning. To a reporting engine, it’s a void. They saved the patient, but they “killed” the encounter for the auditors.
To understand why this is so pervasive, you have to look at how the machinery actually functions. In a standard
environment, the data extraction usually relies on “tagged” events. If the tag isn’t there, the registry doesn’t see it.
It’s a binary world. You could perform the most complex neurology consult in the history of the state, but if the CPT code isn’t linked to the specific Quality ID during the billing handoff, that encounter evaporates.
The Preservation of the Data-Soul
The billing department thinks their job is to get the claim paid. The clinical department thinks their job is to heal. Neither sees the “third job”: the preservation of the data-soul of that encounter for the year-end submission.
“You can see the data failing just by watching a clerk’s shoulders. When they encounter a ‘data wall’-a required field they don’t have the answer for-they find a way to bypass the requirement. That physical recoil is the sound of a handoff snapping.”
– Phoenix C.-P., Body Language Coach
Phoenix argues that the way a team “carries” a file says more about their success than their documented workflow. If the handoff feels like a burden, the data will be dropped.
Snapshots and Secret Steps
The third failure is the “Premature Snapshot.” This happens in or when the administration wants to see “how we’re doing.” They pull a report, see a 61% score, and feel a false sense of security or a misplaced sense of panic.
But that report was pulled before the last encounters were closed or before the billing lag was accounted for. The handoff here is between the data’s current state and the decision-maker’s perception. We start making strategic shifts based on incomplete ghosts.
The Sarah Problem
Finally, there is the “Staff Departure Export.” This is the most painful one. Every practice has that one person-let’s call her Sarah-who knows the “secret steps.” She knows that to get the Promoting Interoperability data out of the old server, you have to export it to a CSV, rename the header, and then upload it to a specific portal.
Then Sarah leaves for a better job in . Nobody documents those three minutes of work because it’s just a “small thing Sarah does.” Come January, the box on the whiteboard labeled “Submission” is still there, but the bridge to get the data into that box is gone.
We respond to these failures by moving the deadline. We say, “Next year, we start in October!” But starting earlier just means you’re watching the fire burn for a longer period. It doesn’t change the fact that your hoses don’t fit the hydrants.
If the front desk is still skipping fields and the doctors are still writing masterpieces in free-text, it doesn’t matter if you start on or . The gaps are still there.
A Radical Obsession with Seams
The solution isn’t more boxes. It’s a radical obsession with the seams. It’s about looking at the person who does the billing and asking, “What do you need from the doctor that the doctor doesn’t know you need?” It’s about looking at the doctor and asking, “What is the EMR doing that makes you want to hide your data in a text box?”
When I look at Prime Well Med Solutions and their approach to the anatomy of a submission, I see an acknowledgment of these interior gaps. They aren’t just looking at the final number; they’re looking at the sixteen different specialties and the individual measure sets that live or die in the arrows.
They understand that a cardiologist’s handoff looks different than a radiation oncologist’s.
Stop Staring at the Boxes
We have to stop drawing pipelines that look like clean, straight lines. Real healthcare data is a messy, sprawling thing that leaks at every joint. The organizations that survive the “January Fire” are the ones that stopped staring at the boxes and started checking the threads on the couplings.
They realized that the most important work doesn’t happen inside the department; it happens in the hallway, in the handoff, and in the unspoken agreement that the data is just as important as the claim.
Traditional View:
Focus on the Boxes (Departments/Tasks)
Modern View:
Focus on the Arrows (The Handoffs/Seams)
If you’re still staring at a 61% score and wondering where the rest of your year went, don’t look at the calendar. Look at the arrows. Look at the moments where one person finished their job and assumed the next person had everything they needed.
Usually, they didn’t. Usually, the data is still sitting on a desk or buried in a note, waiting for a bridge that was never built.
I’m done with the whiteboard arrows. From now on, I’m looking at the seams. It’s less pretty to draw, but it’s the only way to keep the city from burning.