Sepsis coding changes could redefine CDI, coding and quality alignment

Sepsis has always been complex. What's changing now is how we define, measure and report that complexity. The ripple effects could extend far beyond coding. Proposed ICD-10-CM sepsis changes point toward a potential shift to modern clinical definitions. These proposals remain under review and could take effect as early as October 2027. Changes include revisions across A41 sepsis codes, restructuring of the R65 category and the elimination of R65.20 (severe sepsis without septic shock).

On paper this looks like a coding update. In practice it exposes a deeper issue healthcare organizations have been navigating for years: persistent misalignment between clinical definitions, coding systems and quality reporting frameworks.
 

The alignment gap isn’t new, but it’s widening

Sepsis sits at the intersection of three competing frameworks:

• Clinical definitions increasingly aligned to Sepsis-3
• Coding conventions rooted in ICD-10-CM guidelines
• Center for Medicare & Medicaid Services (CMS) quality programs that continue to rely on SIRS-based criteria

Sepsis-3 redefined sepsis as life-threatening organ dysfunction caused by a dysregulated host response to infection. It eliminated the severe sepsis distinction entirely. Yet CMS quality measures still rely on older constructs that operationally separate sepsis from severe sepsis.

The result is a system where clinicians, clinical documentation integrity (CDI) teams, coders and quality leaders often work from different rulebooks. This creates variation in physician documentation, query practices, coding interpretation, mortality reviews and audit outcomes. This gap always existed, but sepsis coding updates may make it harder to ignore. 

At the 2026 ACDIS Conference, CDI, coding and physician leaders repeatedly cited the operational strain of balancing Sepsis-3 clinical practice, ICD-10-CM coding guidance and CMS quality measures—showing up as documentation variability, denial risk, SEP-1 abstraction challenges and inconsistent coding-versus-quality interpretations.
 

Why removing R65.20 matters

The proposed elimination of R65.20 is more than a code deletion. It represents a conceptual shift. Historically, R65.20 allowed organizations to capture sepsis with organ dysfunction while maintaining alignment with legacy coding and diagnosis-related group (DRG) structures. Its proposed removal reflects Sepsis-3 alignment. Organ dysfunction is inherent to sepsis rather than a separate severity tier.

That shift introduces several operational considerations: 

• How will severity be represented within Medicare Severity Diagnosis-Related Groups (MS-DRGs) assignment?
• What happens to historical trend data built on current definitions?
• How will payers interpret documentation variability during transition?
• What does consistency look like across coding, quality and audit review?

For many organizations, this is less about code replacement and more about maintaining consistency in how you define and measure sepsis over time.
 

The operational impact goes beyond coding

When definitions change, downstream processes follow. Without corresponding updates from CMS quality programs, your organization may need internal guidance to keep reporting and operations consistent, such as:

• Defining internal sepsis criteria for reporting and analytics
• Standardizing provider education and documentation expectations
• Updating query strategies to reflect new coding structures
• Reconciling differences between coded data and quality metrics

These aren't just documentation decisions. They affect reimbursement, public reporting and internal performance tracking.
 

A familiar pressure point for healthcare leaders

This situation reflects a broader pattern across healthcare where systems evolve at different speeds. Clinical practice advances based on emerging evidence. Coding systems adapt to capture that evolution. Quality programs often lag to maintain measurement stability. When those timelines don't align, your organization absorbs the operational complexity.

Sepsis is one of the clearest examples of this challenge. The coexistence of Sepsis-2, Sepsis-3 and ICD-10-CM guidance already creates operational friction. These proposed sepsis coding updates accelerate the need to address it.
 

Predictability becomes the priority

For leaders across CDI, HIM and finance, the concern isn't just accuracy. It's predictability. Consistency in how your team documents and codes sepsis directly impacts case mix index, reimbursement and quality scores. It also affects audit defensibility, denial rates and internal benchmarking. When definitions shift without alignment, variability increases. This brings both financial and compliance risk. 
 

Prepare for future changes

The direction appears clear. ICD-10-CM sepsis changes are moving closer to contemporary clinical definitions. What remains uncertain is how quickly regulatory and quality frameworks will follow. Organizations that adapt successfully will focus on early interdisciplinary alignment across CDI, coding, quality and physician leadership.

You can implement clear provider education tied to both clinical and coding expectations. Internal operational guidance will help bridge gaps between coding and quality reporting and proactive monitoring of trends will help you maintain continuity during the transition. 

Ultimately, these proposals highlight a broader challenge of defining and measuring a complex condition using systems that don't fully align. We're here to help you navigate these changes and support your clinical teams in delivering exceptional care.

Melody N. Timmons, MSHIM, RHIA, CCS, CCDS