Documentation Gaps: When Your Note Does Not Support the Code You Billed

Documentation gaps run in two directions

When practices hear the phrase documentation gap, they often immediately think about audits, overcoding, and repayment risk. That is only half of the picture.

The goal should not be to make notes longer. The goal should be to make them accurate. A ten-page note filled with generic language is not necessarily better documentation than a concise note that clearly explains the patient's problems, the provider's assessment, the decisions made, and why those decisions were medically necessary.

Direction one: the note does not tell enough of the story

This is one of the most overlooked forms of revenue leakage. The provider may have performed the work necessary to support a higher level of service, but if that work is not reflected in the documentation, the coding team cannot safely assume it happened.

Time was spent, but never documented

Office and outpatient E/M services may be selected based on medical decision making or total time on the date of the encounter when the applicable requirements are met. That creates an important opportunity for providers whose encounters legitimately require substantial time. But the time has to be documented.

Imagine a provider spends 35 minutes reviewing records, evaluating the patient, counseling them, coordinating care, and documenting the encounter on the date of service. If the medical decision making supports the level independently, the absence of a time statement may not matter. But if time would have supported the appropriate level and none was documented, the coding team cannot simply estimate how long the provider probably spent. The opportunity disappears because the record does not support it.

That is why a simple total-time statement can be one of the easiest documentation improvements a practice can make — when time is being used for code selection. The key is not to document the same default number on every encounter. Document the actual total time when it is relevant and accurate.

Problems are listed, but not actually addressed

One of the most common documentation habits is also one of the least useful: a bare list of diagnoses. That tells the reader what conditions are associated with the patient. It does not tell the reader what the provider did about them today.

Medical decision making depends on the problems actually evaluated or addressed during the encounter, along with the data reviewed and analyzed and the risk of patient management. For each condition that matters to today's encounter, the note should help the reader understand what is happening with the problem, what the provider decided, and why.

“Imaging reviewed” may not tell the reviewer enough

Providers review an enormous amount of data: imaging, laboratory results, EKGs, prior records, specialist notes, hospital documentation. But documentation often reduces all of that work to “results reviewed.”

When an independent interpretation of a test is relevant to medical decision making and meets applicable coding requirements, the documentation should make clear that the provider personally interpreted the test and what that interpretation showed. “Personally reviewed chest X-ray. No focal infiltrate identified; mild bibasilar atelectatic changes noted” tells a reviewer much more than “X-ray reviewed.” The purpose is not to add unnecessary language. It is to make the clinical work visible.

Important clinical discussions never make it into the note

Some of the most important medical decision making happens outside the exam room. A provider may speak directly with a cardiologist about whether to admit a patient. A surgeon may discuss management with an emergency physician. Then everyone moves on to the next patient, and the conversation never gets documented.

If the discussion is relevant to the medical decision making and qualifies under the applicable E/M rules, the note should reflect it. A brief statement may be enough: “Discussed patient's worsening symptoms and treatment plan with Dr. Smith, cardiology. Agreed to discontinue current medication and arrange expedited follow-up.”

Direction two: the note says more than what happened

The opposite problem can be more dangerous. Instead of failing to capture work that occurred, the medical record appears to describe work that may not have been performed. This is often not intentional. It commonly develops from EHR design and documentation habits.

Copy-forward can blur one visit into the next

Copy-forward functionality can be incredibly useful. Providers should not have to retype an entire medical history every time a patient returns. The problem begins when yesterday's assessment becomes today's assessment without enough attention to what actually changed.

A condition may remain in the assessment even though it was not addressed today. A treatment plan may remain unchanged even though a different decision was made. Old symptoms may look current. And genuinely important new work may become buried inside paragraphs that look identical to the previous visit.

The issue is not simply that text was copied. The question is whether a reviewer can clearly tell what happened at today's encounter. If not, copy-forward has stopped saving time and started weakening the medical record.

Templates should prompt, not practice medicine

Templates can improve consistency and make documentation easier. They can also create documentation that is technically complete but clinically inaccurate.

A good template might ask: current status of condition. A problematic template may automatically state: condition stable, continue current medications. Those are very different things. The first prompts the provider to document. The second documents on the provider's behalf.

When templates routinely generate information that may not have been evaluated during the encounter, the medical record can begin to reflect the design of the software rather than the care delivered to the patient.

Coding the template instead of coding the visit

Long documentation does not automatically equal high-complexity medical decision making. A note may contain pages of imported laboratory results, a lengthy problem list, a complete history, and multiple template-generated sections. That does not mean the encounter supports a higher-level E/M service.

The code should follow the work performed and supported under the coding requirements, not the volume of text generated by the EHR.

Watch for notes that all look the same

Uniformity is one of the easiest warning signs to identify. Take two notes from the same provider on two completely different patients and put them side by side.

Some consistency is expected. Providers naturally use familiar phrasing, and chronic disease management often follows similar structures. But when large portions of unrelated encounters are essentially identical, the notes may no longer be describing individual patient care. That creates problems in both directions: the documentation may contain work that was not performed, and the genuinely important work that was performed may be hidden inside generic text.

How to audit your own documentation

You do not need to review hundreds of notes to find documentation patterns. In fact, a smaller, thoughtful sample is often more useful.

1. Start with 10 encounters per provider.Select ordinary encounters — not only complex cases or visits the provider remembers particularly well. You want to see what normal documentation habits look like.
2. Compare the note to the code. For each encounter, sort it into one of three buckets: the documentation supports the billed service, it may support more than was billed, or it does not clearly support what was billed.
3. Look at time documentation.If providers frequently select levels using time, check how consistently total time is documented — and the quality of those statements. A cloned statement with the same time on nearly every note creates a different problem.
4. Look for documentation uniformity. Compare notes across different patients, paying attention to assessment and plan language, statements about disease status, medication decisions, imported data, and repeated counseling statements.
5. Record the pattern, not just the individual error. If seven of ten notes fail to describe the status of chronic conditions, correcting those seven notes is not the long-term solution.

You are not trying to “catch” the provider. You are looking for patterns. “Provider routinely lists diagnoses without documenting how they were evaluated or managed” is teachable. So is “time-based services are being performed, but total time is inconsistently documented,” or “template-generated assessment language remains in the note even when the condition was not addressed.” Those findings tell you what needs to change.

Fix the documentation prospectively

Documentation improvement works best when it is practical. Giving providers a 40-page documentation manual rarely changes what happens during a busy clinic day. Instead, identify the two or three behaviors creating the largest problems and focus there.

• Make time easy to document. If time is relevant to code selection, create a simple workflow for recording actual total qualifying time. The goal is one accurate statement, not another paragraph.
• Give the assessment and plan a consistent structure. For each problem addressed: problem, status, decision, reason.
• Remove defaults that assert care. If a field describes clinical work, consider whether it should require an active selection rather than automatically populating.
• Re-audit after education. Give providers time to change their habits, then repeat the same audit several months later with a similar sample size.

The question is not “did the provider pass the audit?” The better question is “did the documentation habit improve?” That turns an audit from a grading exercise into an education tool.

Be careful with retrospective changes

When a closed note legitimately needs clarification, organizations should follow their formal amendment or addendum policies and preserve the integrity of the EHR audit trail. An addendum should clearly identify that it is an addendum or late entry, when it was entered, who entered it, what is being clarified, and that the clarification relates to work actually performed.

Documentation gaps rarely exist alone

Documentation is often the foundation beneath several other revenue cycle problems. If total time is not documented, an otherwise supportable E/M level may be missed. If the note does not clearly separate an E/M service from a procedure, modifier 25 may be difficult to support. If a procedure is documented in the note but the charge workflow never sees it, the practice may have a missed charge.

That is why documentation improvement affects more than coding. It affects charge capture, compliance, reimbursement, provider productivity reporting, and the quality of the data you use to run the practice.

The bottom line

A documentation audit should not only ask “did the provider document enough to defend this code?” It should also ask “did the documentation capture all of the work the provider actually performed?”

Those are two sides of the same problem. One protects the practice from billing more than the record supports. The other protects the practice from routinely billing less than the work supports.

The goal is not more documentation. The goal is better documentation — clear, individualized, clinically meaningful, and accurate enough that someone who was not in the room can understand exactly what happened and why. When the documentation accurately tells the story of the encounter, coding gets easier, audits become easier to defend, and fewer legitimate revenue opportunities are left behind.