Try Stream free for 30 days. $149/month. Annual billing at $99/month. 30-day free trial, no credit card required. Try it on your next visit →
How It Works Features
Specialties
Primary Care Direct Primary Care Pediatrics SNF & Long-Term Care About Blog Pricing FAQ Log In Start free trial →
← Back to Blog
practice-operationsehr-design
Part 2 of 3 Revenue & Coding

Your Denials Start in the Note

Jacob Kantrowitz MD, PhD · · 7 min read

The denial arrives three weeks after the visit. By then the encounter is cold. Your biller pulls the chart, tries to figure out why the payer rejected it, and discovers the note doesn’t clearly support what was billed. Now someone has to reconstruct a visit the provider barely remembers, decide whether it’s worth the effort to appeal, and either resubmit or write it off. The patient has long since left. The cash that should have arrived weeks ago is still not here.

It feels like a billing problem. It reads like a billing problem — it surfaced in the billing office, weeks downstream, in the world of payer portals and remittance codes. But most documentation-driven denials aren’t decided at submission. They’re decided at documentation. By the time the claim goes out, the outcome is already baked in. The note either supports the service or it doesn’t, and if it doesn’t, the denial was authored weeks earlier, in the exam room, in the moments after the visit — you just didn’t know it yet.

The note is the evidence, and thin evidence loses

A clean claim is a small argument: this service was medically necessary, for this specific problem, at this level of complexity, and here is the documentation that proves it. The note is the evidence in that argument. When a payer reviews a claim, the note is what they’re reviewing. If the note doesn’t establish medical necessity, doesn’t carry a specific enough diagnosis, doesn’t link the problem to the plan, or doesn’t contain the elements that support the level billed, the argument fails — no matter how appropriate the care actually was.

This is the uncomfortable part. The care can be completely justified and the claim can still lose, because the claim isn’t adjudicated on the care. It’s adjudicated on the record of the care. A provider can make exactly the right decision for exactly the right reasons and still generate a denial, if the documentation doesn’t make the reasoning legible to someone reading it weeks later with no memory of the visit.

Not every denial starts in the note — plenty are administrative. Eligibility lapses, prior-authorization gaps, timely-filing misses, coordination-of-benefits tangles: these are real, and they have nothing to do with what the provider documented. But the documentation-driven denials — medical necessity not established, diagnosis too unspecified to support the service, the problem addressed but not clearly tied to the assessment, insufficient documentation for the level — are a meaningful share of the total, and they are the ones the note controls completely. Those are the denials you can prevent before they happen, because they’re written into the record at the point of care.

Digitizing didn’t fix denials. It changed their character.

There’s an instructive pattern in what happens when a practice moves from paper to a modern record. You’d expect denials to fall, and in one sense they do — a whole category disappears. On paper, notes got denied because the payer literally couldn’t read them. Illegibility was a real and common denial reason for decades.

Go digital and illegibility denials vanish. But in the practices we’ve watched make that transition, the denials don’t disappear so much as shift. The note is now perfectly legible — and the payer can suddenly see exactly what isn’t there. The unspecified diagnosis where a specific one was available. The service billed without documentation that establishes why it was necessary. The complexity that justified the level, present in the visit but absent from the record.

Legibility was the paper era’s problem. Specificity is the digital era’s problem. Making the note readable exposed the next layer: a readable note that still doesn’t say enough. And a readable note that doesn’t say enough gets denied on the merits, not on the handwriting.

Denials tax you three ways

The reason denials deserve more attention than they usually get is that the denied dollars are only the first of three costs, and often the smallest.

The lost revenue. The claim was rejected. Some portion is recoverable on appeal; some isn’t. Either way, revenue you earned is now revenue you might not collect.

The labor to rework it. Every denied claim that gets reworked costs staff time — pulling the chart, diagnosing the rejection, gathering documentation, appealing, resubmitting. That’s your billing team’s day, spent recovering money you should have collected the first time instead of doing work that moves the practice forward.

The claims you never rework at all. This is the quiet one. A meaningful share of denied claims are simply written off, because the dollar value doesn’t justify the effort to appeal. The revenue is real, the care was delivered, and it’s abandoned because chasing it costs more than it returns. Nobody decides to lose that money. It just leaks.

And underneath all three: delay. Every denial pushes cash further out. Days in accounts receivable climb. The practice waits weeks or months for money it earned at the visit — money it’s already spent, in staff and rent and supplies, to deliver the care that generated the claim.

The root cause is the note’s structure

Why does the note so often fail to carry the specificity and linkage a clean claim requires? For the same reason it fails at so much else: it’s the wrong structure for the job.

A traditional note is an undifferentiated block of text organized by time. The diagnosis lives in one place, the assessment in another, the plan in a third, and the connective tissue a payer needs — this specific problem drove this specific decision, which justified this specific service — is implied across paragraphs rather than made explicit anywhere. The medical necessity is in the clinician’s head. It may even be on the page, scattered. But it isn’t structured as an argument, and a claim is an argument.

We’ve written elsewhere about why organizing the record by problem rather than by time changes what documentation can do. Clean claims are one of the clearest payoffs. When each problem carries its own thread — its own diagnosis at the right specificity, its own assessment, its own plan, its own linkage from finding to decision to service — the elements a payer looks for stop being scattered through prose and start being structurally present. Specificity becomes the natural state of the record rather than an afterthought a rushed clinician has to remember to add. The linkage between problem and plan is explicit because the problem is the organizing unit. The argument the claim needs to make is already assembled, because the record was built as arguments about problems in the first place.

This isn’t about documenting for the payer

It’s worth being clear about what this is not. It is not an argument for documenting defensively, padding notes to satisfy payers, or writing for the auditor instead of for the patient. That instinct produces exactly the bloated, box-checking notes that make the record worse for everyone who has to read it next.

The point is nearly the opposite. A note that clearly captures the problem, the reasoning, and the plan — captured because that’s what good clinical documentation is — happens to be the same note that supports a clean claim. The clinical record and the billable record were never supposed to be two different documents. The reason they’ve drifted apart is that the note’s structure serves neither well. Fix the structure so it serves the clinical purpose properly, and the billing purpose comes along for free, because a record that accurately represents the care is a record that supports the claim for that care.

The denial you prevent is worth more than the one you win

The entire apparatus of denial management — the tracking, the appeals, the resubmissions, the write-off decisions — exists to recover value after it’s been lost. It’s necessary work, and it will always be necessary for the administrative denials that have nothing to do with the note. But for the documentation-driven denials, the whole downstream apparatus is treating a problem that was created upstream, at the point of care, in the structure of the record.

The denial you prevent costs nothing to work, delays no cash, and never lands on your biller’s desk. It’s worth more than the denial you win. And you prevent it in the exam room, weeks before it would have arrived — by building a record that says enough, about the right things, in a shape that makes the care legible to whoever reads it next. Including the payer.


Stream is the AI documentation platform built on the ideas in our book — notes organized around medical problems, so specificity and medical necessity are captured at the point of care instead of reconstructed weeks later. Built for independent primary care, by primary care physicians. See how it works or talk to a clinician.