Apr 14, 2026
Written By Elizabeth Cifers
If documentation issues had personalities, the overlap between exam and test narratives would be the one that quietly causes problems and then acts surprised when a denial appears. It doesn’t seem dramatic or like an obvious mistake. However, it is one of the most common (and most preventable) reasons documentation becomes hard to defend. At the core of the problem is something surprisingly straightforward: the same story is being told twice.
The exam documents a clinical finding, such as macular edema, and then the diagnostic test interpretation repeats that same finding, often using almost identical language. At first glance, this might seem efficient because the information is accurate. However, from a payer or auditor’s perspective, the issue is not whether the statement is correct but what the diagnostic test actually added. And that question is more important than most people realize.
CMS has been very consistent in its expectations that diagnostic tests must provide information used to diagnose or treat the patient and guide management. In other words, the test needs to add something new. It cannot simply repeat what was already determined during the clinical exam. When documentation shows that the test only confirmed findings already known, it becomes hard to justify why the test was necessary in the first place—or why it should be paid separately. This is where overlap becomes a risk.
What makes this especially challenging is that, clinically, the exam and the test are naturally linked. Of course, the OCT will relate to what you observe in the macula, and the fluorescein angiogram will correspond with vascular findings. The goal isn't to separate them so completely that they seem unrelated, but to allow each part of the documentation to serve its own purpose clearly and distinctly.
One way to think about this is that each part of the visit has its own “home.” The exam is where you document what you observed directly. It is your clinical evaluation: what you saw, and what you identified at the slit lamp or on fundus exam. It stands on its own as your direct interaction with the patient.
The interpretation of a diagnostic test, however, is not just a second version of the exam. It is your analysis of the objective data produced by the test. It should reflect what the technology shows you—often in more detail, sometimes in ways that aren't visible clinically, and ideally in a way that enhances your understanding of the patient’s condition.
When those two “homes” begin to overlap, the documentation becomes unclear. And when clarity is gone, defensibility usually follows.
A subtle but important distinction involves how correlation is considered. Documentation often states, “findings correlate with exam,” which is correct, but only when there is something meaningful to connect. If the interpretation simply restates the exam finding, there’s no new information to support a link. This results in a circular explanation: the exam supports the test, and the test supports the exam, but neither adds insight beyond the other.
A more effective approach is to allow the test to refine, quantify, or expand on the clinical picture. Instead of simply restating “macular edema,” the interpretation could describe the presence of intraretinal fluid, its location, its extent, and whether it has improved or worsened compared to prior imaging. Only then does correlation become meaningful because the test provides information that can be applied to decision-making.
This is also where documentation starts to show value in a way that auditors understand. The test is no longer just in the chart; it is actively guiding care.
Of course, EHRs don't always make this simple. Copy-forward features and templated language can unintentionally obscure the boundaries between sections. Auditors are particularly vigilant about this because identical language across sections raises concerns about whether each component was genuinely performed and interpreted as required.
Efficiency matters in a busy retina clinic. No one suggests that documentation should become needlessly lengthy or burdensome. However, there is a difference between being efficient and being repetitive. Repetition does not improve documentation; it undermines the argument that each service served a unique and essential purpose.
A helpful way to pause and recalibrate is to ask a few simple questions before finalizing the note. Does the exam clearly describe what was observed clinically? Does the test interpretation explain what the data shows, adding detail or perspective? And does the assessment and plan reflect how that combined information is being used to manage the patient? When each of those answers is yes—and when each section sounds just different enough to confirm it—the documentation begins to come together as both clinically accurate and defensible.
Ultimately, separating exam and test narratives isn't about adding more words; it's about creating clarity. It's about ensuring each part of the visit contributes its piece to the overall story. The exam identifies the problem, the test deepens or refines understanding of that problem, and the plan uses that information to support patient care.
When that story is clear, the documentation does exactly what it's supposed to—support the care provided and hold up when someone else reads it later.
If something here seems familiar, it might be worth a closer look. ECC can assist with that.
.png)
.jpg)
