The Whole Story Matters: Documentation in Risk Adjustment

The Whole Story Matters: Documentation in Risk Adjustment

Article Reference Code: NAMAS.05.29.2026

Written by: Dannilla Morgan, CPC, CBCS

The reliability of clinical documentation is crucial as it creates a fundamental connection between a patient’s true health condition and the data that represents it within the risk adjustment framework. As the sector shifts away from volume-based metrics, the focus has transitioned to documentation integrity, which guarantees that the medical record accurately and verifiably reflects clinical reality. This transition necessitates moving from a “problem list” approach to a “problem addressed” standard, where every diagnosis recorded must have active clinical participation during the visit. This interaction is confirmed through the observation of signs or symptoms, the analysis of diagnostic results, an evaluation of the current state of the disease, and a definitive treatment plan. When these components are included, the documentation generates a clear clinical footprint that substantiates the complexity of the patient’s health condition and safeguards the organization against risks related to under-recording or submitting inaccurate data.

While Electronic Health Record templates and automated coding tools play a crucial role in maintaining high productivity, they also bring specific risks such as note bloat and replicated documentation. When clinical notes are identical across various visits due to auto-filled macros, it becomes challenging to determine the actual care provided on a specific date, which raises significant concerns for auditors. To address this, providers should be trained in the strategy of editing by exception, where templates offer a structural framework but the narrative is personalized to reflect the unique patient interaction for that day. This method ensures that the patient’s health narrative remains clear and distinct, rather than obscured by repetitive, generic information. For the coder, this entails acting as the initial line of defense to ensure that the clinical narrative genuinely supports the codes proposed by automated systems, emphasizing clinical substance over mere dependence on templates.

Precision in clinical terminology is fundamental to accuracy and a crucial protection against allegations of upcoding. Lack of clarity in documentation often results in the use of unspecified codes, which do not accurately capture the true severity and acuity of a patient’s condition, directly affecting healthcare resource distribution. For instance, documenting specific manifestations, like peripheral neuropathy related to Type 2 Diabetes or detailing the precise stage of Chronic Kidney Disease, offers a verified representation of clinical reality that generic entries cannot provide. This degree of specificity is essential for maintaining compliance with the latest ICD-10-CM guidelines and ensuring that the risk score accurately reflects the care delivered. Ongoing education for providers about these technical requirements is vital to bridge the gap between clinical intent and codeable data.

Education for providers should be positioned as a collaborative effort in data integrity, rather than an administrative burden. To assist coders, providers do not need to master the complexities of coding but should aim to become more effective narrators of the clinical encounter. Educational strategies should incorporate feedback loops with “before and after” examples, specialty-specific specificity cheat sheets, and training on the stand-alone note rule. When providers realize that a well-documented note endorses the intensity of their service and safeguards against recoupment, they are more inclined to focus on documentation integrity. This collaboration transforms the coder’s role from investigative work to data validation, ensuring that the medical record remains a truthful and ethical account of the care delivered.

In healthcare organizations, corporate compliance must prioritize accuracy as the main metric, even amidst high production pressures. Large-scale operations frequently encounter the “payment in good faith” misconception, where organizations mistakenly believe that a paid claim equates to a compliant claim; however, insurers will reclaim funds if an audit uncovers that the documentation did not support the code. Compliance measures must empower coders to leverage their expertise to validate automated suggestions rather than merely clearing a queue to achieve productivity targets. By cultivating a culture where accuracy is the core of the revenue cycle, leadership can shield individual coders from burnout and protect the organization from serious regulatory repercussions, such as False Claims Act allegations. Ultimately, documentation integrity serves as the foundation for a sustainable health program, ensuring that the patient’s medical history is conveyed with the utmost accuracy and ethical standards.

Provider Education: Documentation that Tells the “Whole Story”
1. The “Remission” Revolution (New Code: E11.A) Starting in late 2025, the ICD-10-CM introduced the code E11.A, which refers to Type 2 diabetes mellitus in remission. This code is specifically for patients who no longer require glucose-lowering medication and maintain near-normal glycemic levels. Documentation Requirement: It is essential to explicitly use the term “remission” in your documentation. The “Resolved” Trap: It is important to note that “resolved” is not synonymous with remission according to guidelines. If you document “diabetes resolved,” coders may need to ask for clarification or may be unable to assign the correct code. Clinical Indicators: Although coders cannot rely solely on lab results, documentation of remission is generally supported by an HbA1c level of less than 6.5% maintained for at least three months after discontinuing all antidiabetic medications.
2. The “With” Guideline: Automatic Linkage The ICD-10-CM guidelines assume a causal relationship between diabetes and certain chronic conditions. According to the “with” guideline, conditions such as Chronic Kidney Disease (CKD), Neuropathy, and Retinopathy are linked to diabetes unless you specifically state that they are unrelated. Best Practice: To ensure the highest level of accuracy, use linking language. Example: Instead of listing “Diabetes” and “CKD Stage 3” separately, document it as: “Type 2 Diabetes with Stage 3 CKD.” Impact: This ensures the coder uses a combination code (e.g., E11.22), which more accurately reflects the patient’s systemic disease burden and complexity.
3. Combination Coding and Multiple Complications Effective risk adjustment necessitates a comprehensive assessment of the patient’s overall health status. Utilization of Multiple Codes: It is essential to assign all pertinent codes from the categories E08–E13 to accurately represent all related conditions. Code Sequencing: The codes should be organized based on the primary reason for the patient’s visit. For example, if the patient presents with a diabetic foot ulcer, the code for the ulcer (E11.621) should take precedence in the coding hierarchy.

Case Scenarios: Applying the 2026 Guidelines
Clinical Status	Ineffective Documentation	FY 2026 Compliant Documentation
Success post-surgery	“History of DM2; resolved after gastric bypass. A1c 5.8.”	“Type 2 Diabetes in remission following bariatric surgery. Patient currently off all glycemic meds.”
Active Management	“Diabetes. Also has neuropathy. Stable on Metformin.”	“Type 2 Diabetes with diabetic polyneuropathy; continuing Metformin and Gabapentin.”
CKD Connection	“Diabetes and Stage 4 CKD.”	“Type 2 Diabetes with Stage 4 CKD.“

 

In risk adjustment, your documentation serves as the sole evidence of the complexity of the care you provide. For a diagnosis to be included in a patient’s risk profile, it must be actively addressed and clearly supported in the note for that specific date of service. The Coder-Provider Partnership: We don’t want you to code; we want you to describe. When you use specific terms like “In Remission” or link conditions using “With,” you provide the “clinical footprint” we need to follow the official FY 2026 guidelines.

 

---

Contact Dannilla LinkedIn by Clicking her Name Below:

Dannilla Morgan, CPC, CBCS

Dannilla Morgan is an experienced medical coder/ Risk Adjustment Coder with over five and a half years in the field, focusing on high-stakes Risk Adjustment Coding. As a dual-certified professional (CPC, CBCS), she has a deep understanding of ICD-10-CM guidelines and regulatory frameworks. Her expertise encompasses various risk adjustment models, including CMS-HCC, HHS-HCC, and RxHCC, where she emphasizes the crucial connection between clinical documentation integrity and accurate code abstraction.

Recognized as a leader within the AAPC, Dannilla has been selected as an AAPC Emerging Leader for the 2026-2027 cycle. She currently serves as the President of the AAPC Carmel, NY Chapter and is an active mentor and published author within the organization. In addition to her role at a local chapter, she advocates for the coding community as the founder and r of “The Risk Adjustment Coder’s Lounge,” a professional network of over 8,000 Healthcare professionals.

Driven by her dedication to the field’s evolution, Dannilla is currently pursuing a Bachelor of Science in Health Information Management (HIM) at Southern New Hampshire University and an extern in Revenue Cycle Management and Compliance with Turner Experts Consulting Services. Her work is marked by a strong work ethic and a commitment to maintaining the accuracy of medical coding practices while promoting professional growth for coders across the nation.

---

NAMAS BLOG Disclaimer:

The NAMAS Blog features content written by both NAMAS staff and guest contributors. Guest contributors may present opinions or perspectives that differ from those officially instructed or encouraged by NAMAS. We believe in providing space for a range of informed viewpoints to foster dialogue, reflection, and deeper understanding within the auditing and compliance community.

Some contributors may use artificial intelligence (AI) tools in the development of their content. The decision to incorporate AI is left to the discretion of the author and does not reflect an endorsement or directive from NAMAS.

If you have questions, comments, or concerns about a specific blog post, we encourage you to contact the individual author directly. Their name and contact information are provided at the end of each post.