Revenue Cycle Insider

Primary Care:

Document the Diagnostic Journey

Focus on capturing clinical reasoning in primary care.

A patient presents with fatigue. Initial testing does not identify a clear cause. The patient returns weeks later with persistent symptoms, new findings, and a need for further evaluation. The workup continues — but does the medical record clearly explain why?

In primary care, unresolved symptoms are common. The challenge is not only determining the next clinical step; it is documenting the reasoning that supports continued evaluation, additional testing, referrals, and follow-up care.

Each encounter should contribute to the patient’s diagnostic story by describing symptom progression, clinical findings, and the rationale for next steps.

Throughout the diagnostic process, one principle remains essential: Document the thought process, not just the symptom.

Rely on the Why When Tracking Diagnostic Workups Over Time

When symptoms persist without a definitive diagnosis, follow-up encounters should add new information rather than simply repeat the original complaint. Documentation should show how the clinician is reassessing the problem based on symptom changes, treatment response, and diagnostic findings.

For example, an initial visit may document three weeks of fatigue. A subsequent visit may note persistent symptoms despite interventions, new exertional dyspnea, and worsening fatigue with unintentional weight loss, prompting expanded evaluation or referral.

This progression provides a clearer clinical picture than repeatedly documenting, “Patient still tired,” without explaining what has been evaluated or what happens next. Effective follow-up notes should show what has changed, what remains unresolved, and how the workup is evolving.

Senior male patient experiencing headache while female doctor records symptoms

Document the Thought Process

A symptom-based diagnosis, such as fatigue, may accurately describe the patient’s condition; however, the assessment should also explain the clinical reasoning behind continued evaluation.

Documentation should identify relevant conditions being considered, why additional evaluation is needed, and how new information changes the diagnostic plan.

For example: “Persistent fatigue despite normal CBC. Differential includes thyroid dysfunction, sleep disorder, depression, and an autoimmune process. Additional laboratory evaluation is warranted to further narrow the differential and determine appropriate next steps. Follow-up is needed to review results and reassess symptoms.”

This type of documentation demonstrates the clinical questions being evaluated and supports medical necessity by showing that additional evaluation is directed toward unresolved clinical concerns rather than repeating previously completed work.

Normal or inconclusive test results do not necessarily end the diagnostic process. Instead, they may narrow the differential and guide next steps. Documentation should explain why additional testing, referral, or monitoring remains appropriate despite negative findings.

Report Unresolved Symptoms Like This

When the provider has not yet established a definitive diagnosis, report what is known — not what is suspected. ICD-10-CM guidelines support coding signs and symptoms when they represent the highest level of diagnostic certainty at the time of the encounter. Providers should avoid assigning a suspected condition as an established diagnosis in the outpatient setting.

For unresolved symptoms, the documented symptom is often the most appropriate code for the encounter.

Examples include:

  • R53.83 (Other fatigue)
  • R10.9 (Unspecified abdominal pain)
  • R05.3 (Chronic cough)
  • R42 (Dizziness and giddiness)

These codes accurately reflect the patient’s condition while the diagnostic evaluation remains in progress.

Persistent symptoms remain appropriate for coding when they continue to be evaluated, managed, or monitored during the diagnostic process. The absence of a confirmed diagnosis does not prevent appropriate coding.

Accurate symptom coding, combined with clear documentation of the diagnostic process, reflects the patient’s current clinical status without prematurely assigning an unconfirmed diagnosis.

Move Beyond Copy-and-Paste Documentation

Efficient documentation does not mean repeating the same note at every follow-up visit. While carrying forward relevant history and prior findings is appropriate, each encounter should reflect the patient’s current status and explain why continued evaluation or management is needed.

A copied-forward note may show that a symptom exists; a thoughtfully updated note shows why care continues.

A strong follow-up note should answer four key questions:

  1. What is happening now?
  2. What has already been done?
  3. What questions remain unanswered?
  4. Why is further evaluation needed?

When you document these elements, the medical record demonstrates an active evaluation rather than a repeated complaint. Persistent symptoms, new findings, inconclusive results, and escalation of the workup help show why continued evaluation is appropriate.

The most effective documentation captures not only what was observed, but also how the provider’s assessment evolves as new information becomes available.

Clinical Scenario: Documenting the Diagnostic Journey Over Time

The following scenario illustrates how documentation and coding evolve during an unresolved diagnostic workup:

Visit

Clinical Changes

Documentation of Clinical Reasoning

Example ICD-10-CM Code(s)

Initial Visit

Fatigue and intermittent dizziness for 4 weeks

Symptoms documented; CBC/CMP ordered to evaluate possible causes; follow-up planned to reassess symptoms and review findings

R53.83
R42

Follow-Up Visit

Symptoms persist; initial laboratory results normal

Persistent symptoms documented; differential expanded based on ongoing concerns; additional testing ordered

R53.83
R42

Subsequent Visit

New exertional shortness of breath

New symptom changes broaden evaluation; referral initiated based on evolving clinical picture

R53.83
R42
R06.02 (Shortness of breath)

This scenario demonstrates that documentation can show meaningful progress even before the provider establishes a diagnosis. Each encounter adds new information through symptom changes, test results, treatment response, or an expanded differential diagnosis.

Although a definitive diagnosis has not yet been established, the record clearly shows an active evaluation rather than a repeated complaint. Coding remains focused on the documented symptoms while the provider continues to investigate the underlying cause.

The Diagnostic Journey Is the Story

In primary care, unresolved symptoms often require multiple encounters before a definitive diagnosis emerges. Effective documentation connects clinical decision-making and accurate coding by capturing symptom progression, relevant findings, treatment response, and the rationale for next steps.

Documentation establishes the clinical reasoning behind care, while accurate coding reports what is known at the time of the encounter. Together, these elements create a record that reflects the patient’s clinical journey and the provider’s assessment.

The most valuable documentation shows how new information shapes evaluation and decision-making. By capturing this process, providers support continuity of care, medical necessity, and accurate coding.

The guiding principle remains simple: Document the thought process, not just the symptom.

Donna Walaszek, CCS-P, Northampton Area Pediatrics, Northampton, Massachusetts

Other Articles of

July 2026

View All
Subscribe to newsletter