The Two Versions of Your Practice
Ask an owner to describe how a claim moves through the practice and you’ll get a clean answer: the visit happens, the note gets signed, the charge goes in, the claim goes out, the payment posts. Five steps, tidy, the version on the training wiki. Then watch what actually happens to a hundred real claims and you’ll find something messier: notes that sit for three days, a charge that waited on a question nobody chased, a claim that bounced and came back twice, a payment that landed in a category called “review” and stayed there.
Every practice runs two versions of itself. The one the owner describes, and the one the timestamps record. Process intelligence is just the discipline of looking at the second one, and the whole method fits in a sentence: your systems already write down when everything happens, so the real process can be rebuilt from the record instead of from anyone’s memory of it.
What It Actually Is, Minus the Jargon
Every action in a practice management system leaves a timestamp. Appointment created. Visit completed. Note signed. Charge entered. Claim submitted. Payment posted. Line those events up for a single visit and you have that visit’s true journey, with the length of every step and every wait in between. Do it for ten thousand visits and you have the practice’s real operating map: the path most visits take, the detours some take, and the exact spots where time pools and cash sits.
No interviews. No consultant with a clipboard shadowing your front desk for a week. No whiteboard session where everyone describes the process they wish they ran. The map is built from what the system already recorded while everyone was just doing their jobs, which is why it shows the real thing instead of the polite version.
Three Things the Map Shows That No Report Does
Where time pools between steps. Reports measure the steps. The map measures the gaps between them, and the gaps are where your cash actually waits. The days between visit and signed note. Between signed note and charge. Between charge and submission. Most practices have never seen these intervals as numbers, because no standard report frames the empty space between two events, and that empty space is usually the largest untimed delay in the building.
The loops. A healthy claim moves forward exactly once. The map lights up the claims that go in circles: submitted, rejected, fixed, resubmitted, sometimes three and four laps, and it shows which payers and which codes the loops cluster around. Rework is the most expensive walking your process does, because you pay staff to do the same claim twice while the cash waits for all the laps to finish.
The variants. The same intake handled five ways by five people shows up as five different paths with five different completion rates. That’s human variability made visible and priced, which turns “we should probably standardize” from a values conversation nobody wins into an arithmetic one that answers itself.
The Poor Man’s Version, This Afternoon
You don’t need to buy anything to feel this work. Three timestamps and a spreadsheet. For last month’s visits, pull the visit date, the note-signed date, and the claim-submitted date. Compute the two gaps. Sort longest-first. Read the top twenty rows.
Two things happen when you do this. You find your first concrete fix, because the top of that list is never random; it clusters around a provider, a visit type, or a day of the week, and the cluster names the problem. And you learn the reflex that matters more than any single fix: time the gaps, not the steps. Once you start seeing the waits between events instead of just the events, you can’t unsee them, and that shift in attention is worth more than the exercise itself.
Where to Point It First
Three places earn the first look. The visit-to-cash chain, because it times the exact journey your money takes and ranks the waits by cost. The denial loop, because rework is the priciest thing your process does on repeat. And intake, because the map shows where referred patients fall out between first call and first visit, which is future revenue leaking before it ever became revenue. Each one hands you a ranked list of fixes, and each fix arrives already justified by its own timing data, so you’re never guessing about what to work on next.
Where to Start
Run the three-timestamp exercise this week; it costs an hour and a spreadsheet. If the top of your sorted list surprises you, that’s the two versions of your practice disagreeing, and the timestamps are the honest one. Then grab 30 minutes with us. Prep nothing. We’ll show you real process maps from operating practices, the pooled time and the loops lit up, and you’ll see how far the seeing goes past a three-column spreadsheet.