Sepsis coding guidelines remain one of the most complex areas in hospital reimbursement. With updates to ICD-10-CM and evolving clinical criteria, accurately coding sepsis, severe sepsis, and septic shock directly impacts DRG assignment, Medicare payments, and audit risk. This guide breaks down the clinical indicators, sequencing rules, and documentation requirements you need to code sepsis correctly in 2026.
We'll walk through the diagnostic criteria, compare sepsis categories with real chart examples, explain sequencing logic for complicated cases, and show you how to avoid the most common coding errors that trigger denials.
Clinical definitions: sepsis, severe sepsis, and septic shock
Sepsis is a life-threatening organ dysfunction caused by a dysregulated host response to infection. The clinical definition shifted with the Sepsis-3 consensus in 2016, but coding rules haven't always kept pace with bedside terminology.
In ICD-10-CM, you still need to distinguish between three conditions:
- Sepsis (codes A41.x, A40.x): Documented systemic infection with SIRS criteria or organ dysfunction.
- Severe sepsis (no longer a distinct code set as of October 2020): Now coded as sepsis with acute organ dysfunction, using additional codes for the organ failure.
- Septic shock (codes R65.21): Sepsis with circulatory and cellular/metabolic dysfunction, typically requiring vasopressors despite adequate fluid resuscitation.
The 2020 ICD-10-CM update eliminated "severe sepsis" as a code category. You now code sepsis (A41.x or A40.x) plus any associated acute organ dysfunction codes. Septic shock remains a separate add-on code (R65.21) sequenced after the underlying sepsis code.
What counts as organ dysfunction
Documentation must explicitly link the organ dysfunction to sepsis. Common manifestations include:
- Acute kidney injury (N17.x)
- Acute respiratory failure (J96.0x)
- Hepatic failure (K72.0x)
- Encephalopathy (G93.41)
- Coagulopathy (D65, D68.x)
- Thrombocytopenia (D69.6)
The physician must state "sepsis with acute kidney injury" or "AKI due to sepsis." Lab values alone don't establish causation. If the documentation says "sepsis and AKI," query whether the AKI is related to sepsis or a pre-existing condition.
Sepsis coding guidelines: sequencing rules that determine DRG assignment
Sequencing sepsis correctly is where most coding errors occur. The principal diagnosis drives your DRG, and sepsis cases follow specific logic.
Rule 1: If sepsis meets the definition of principal diagnosis, code sepsis first. The principal diagnosis is the condition established after study to be chiefly responsible for the admission. If the patient is admitted primarily for management of sepsis, the sepsis code (A41.x or A40.x) is sequenced first.
Rule 2: If sepsis develops after admission, it's never the principal diagnosis. Code the reason for admission first, then add sepsis as a secondary diagnosis.
Rule 3: Septic shock sequencing. When septic shock is documented, code the underlying sepsis first (A41.x or A40.x), then R65.21 (septic shock) as an additional code. If severe sepsis language appears, treat it as sepsis with organ dysfunction and code accordingly.
Rule 4: Organ dysfunction sequencing. Code sepsis first, then add codes for each documented organ dysfunction. The organ dysfunction codes are always secondary, even if clinically severe.
Example: pneumonia with sepsis
A 72-year-old is admitted with fever, hypotension, and altered mental status. Chest X-ray confirms pneumonia. Blood cultures grow Streptococcus pneumoniae. Documentation states "sepsis due to pneumococcal pneumonia with acute kidney injury."
Correct coding sequence:
- A40.3 (Sepsis due to Streptococcus pneumoniae)
- J13 (Pneumonia due to Streptococcus pneumoniae)
- N17.9 (Acute kidney injury, unspecified)
The sepsis code comes first because it meets the principal diagnosis definition. The pneumonia is coded as the infectious source. AKI is an associated organ dysfunction.
Example: septic shock on admission
A 58-year-old presents with urosepsis, requiring vasopressors in the ED. Documentation states "septic shock secondary to E. coli UTI."
- A41.51 (Sepsis due to Escherichia coli)
- R65.21 (Severe sepsis with septic shock)
- N39.0 (Urinary tract infection, site not specified)
Even though the code description says "severe sepsis with septic shock," you still need the underlying sepsis code first. R65.21 cannot be a principal diagnosis.
Documentation requirements for compliant sepsis coding
Sepsis audits focus on documentation quality. If the record doesn't clearly establish sepsis, the code won't hold up under review.
Minimum documentation elements:
- Physician statement of "sepsis," "septicemia," or "septic shock"
- Identified or suspected source of infection
- Clinical evidence supporting systemic infection (labs, cultures, imaging)
- For organ dysfunction: explicit statement linking the dysfunction to sepsis
SIRS criteria (temperature, heart rate, respiratory rate, WBC count) support clinical suspicion but don't replace physician documentation. If the physician documents SIRS without using the word "sepsis," don't assume sepsis. Query for clarification.
When to query for sepsis
Send a query when:
- Clinical indicators suggest sepsis but the physician hasn't documented it
- Documentation says "possible sepsis" or "sepsis protocol initiated" without confirmation
- Organ dysfunction is present but not linked to sepsis
- Documentation uses outdated terms like "severe sepsis" without clarifying organ involvement
Don't query for sepsis based solely on antibiotic use or positive cultures. Localized infections (pneumonia, UTI, cellulitis) aren't automatically sepsis unless the physician documents systemic involvement.
For organizations managing high volumes of sepsis cases, physician query management processes standardize when and how coders escalate documentation gaps.
Common sepsis coding errors that trigger denials
Most sepsis denials stem from four coding mistakes.
Error 1: Coding sepsis without physician documentation
Coders sometimes infer sepsis from clinical indicators like elevated lactate, hypotension, or sepsis order sets. If the physician hasn't documented sepsis explicitly, you can't code it. Clinical indicators support a query, not a code.
Error 2: Incorrect sequencing when sepsis is present on admission
If a patient is admitted for another condition and sepsis is incidentally present, the other condition may still be the principal diagnosis. Example: a patient admitted for hip fracture who also has a chronic decubitus ulcer with documented sepsis. If the fracture is the reason for admission and the focus of care, the fracture is sequenced first.
The question is always: what was the reason, after study, for the admission?
Error 3: Missing organ dysfunction codes
Coders often capture the sepsis code but miss associated organ dysfunction, which lowers severity and reimbursement. If documentation states "sepsis with respiratory failure," both codes are required. Missing the J96.0x code underrepresents acuity.
Error 4: Using outdated "severe sepsis" language
Some physicians still document "severe sepsis" because the term remains in clinical use. As of October 2020, there's no ICD-10-CM code for "severe sepsis" without septic shock. When you see "severe sepsis," look for organ dysfunction and code sepsis (A41.x) plus the dysfunction codes. If septic shock is present, add R65.21.
To catch these errors before claims go out, regular coding quality audits help identify patterns in sepsis miscoding and guide coder education.
Sepsis and DRG impact: why accurate coding matters financially
Sepsis DRGs carry significantly higher reimbursement than infection-only DRGs. For MS-DRG grouping, septicemia (DRGs 870–872) pays substantially more than respiratory or urinary infections.
Example DRG comparison for Medicare:
- MS-DRG 871 (Septicemia without MV >96 hours with MCC): approximately $15,200 national average
- MS-DRG 193 (Simple pneumonia with MCC): approximately $9,800 national average
Undercoding sepsis as pneumonia alone leaves $5,400 on the table per case. Multiply that across 50 or 100 sepsis admissions annually, and the revenue impact is measurable.
Accurate organ dysfunction coding also affects CC/MCC capture. Acute kidney injury, respiratory failure, and encephalopathy add complication severity that shifts DRG assignment and increases payment.
For hospitals managing complex inpatient volumes, outsourcing to experienced teams ensures consistent sepsis capture. Inpatient coding specialists trained in sepsis documentation and sequencing reduce variability and denials.
2026 sepsis coding updates and ongoing compliance considerations
ICD-10-CM updates effective October 1, 2025 didn't introduce major changes to sepsis code structure, but CMS continues refining DRG weights based on claims data. Septicemia DRGs saw slight weight adjustments in FY 2026, reflecting updated cost data.
Two compliance trends to watch:
Increased scrutiny from Recovery Audit Contractors (RACs). Sepsis remains a high-dollar audit target. RACs challenge cases where documentation doesn't support the sepsis diagnosis or where sequencing appears incorrect. Strong physician documentation and compliant coding are your best defense.
More granular organ dysfunction reporting. Quality programs like SEP-1 (the CMS sepsis core measure) tie sepsis recognition and treatment to hospital performance scores. While SEP-1 is a clinical measure, coding accuracy affects how sepsis cases are identified in claims data for quality reporting.
Staying current with AHA Coding Clinic guidance is non-negotiable. Coding Clinic regularly publishes clarifications on sepsis sequencing, especially for complex cases involving multiple infections or post-procedural sepsis.
Frequently asked questions
Can you code sepsis based on SIRS criteria alone?
No. SIRS criteria (fever, tachycardia, tachypnea, elevated WBC) are clinical indicators that may prompt a physician to evaluate for sepsis, but they don't replace physician documentation. The provider must explicitly document sepsis or septicemia. If SIRS is documented without sepsis, code only the SIRS (R65.10 or R65.11) if applicable, and consider querying for sepsis if clinical context supports it.
How do you code sepsis if the causative organism is unknown?
Use A41.9 (Sepsis, unspecified organism) when the physician documents sepsis but cultures are negative or pending, and no specific organism is identified. This is common when empiric antibiotics are started before culture results return. If an organism is later identified, update the code to the specific A41.x or A40.x code for that pathogen.
What's the difference between bacteremia and sepsis for coding purposes?
Bacteremia (R78.81) means bacteria are present in the bloodstream but doesn't imply systemic infection or organ dysfunction. Sepsis requires documentation of a systemic inflammatory response to infection. A positive blood culture alone doesn't justify a sepsis code. The physician must document sepsis. If documentation says "bacteremia" without sepsis, code only the bacteremia and the underlying infection source.
Do you code sepsis if documentation says "sepsis protocol" or "treated as sepsis"?
Not without clarification. Initiating a sepsis protocol or treating a patient as if they have sepsis doesn't confirm the diagnosis. Query the physician to document whether the patient has sepsis based on clinical findings. Treatment protocols are risk mitigation strategies and don't replace diagnostic documentation.
How do you sequence sepsis when it's present on admission but not the reason for admission?
Code the condition that occasioned the admission as the principal diagnosis, then add sepsis as a secondary diagnosis. Example: a patient admitted for elective surgery who also has documented sepsis from a chronic wound. The surgical procedure or its indication is the principal diagnosis, and sepsis is secondary. If the surgery is postponed and the admission becomes focused on treating sepsis, query whether sepsis should be the principal diagnosis.
Get sepsis coding right the first time
Sepsis coding demands precision. Missed organ dysfunction codes, incorrect sequencing, or weak documentation cost you reimbursement and increase audit risk. When your team is stretched thin or sepsis volumes spike, errors creep in.
MedCodex Health specializes in high-acuity inpatient coding, including complex sepsis cases. Our certified coders know sepsis sequencing rules inside out, query appropriately when documentation gaps exist, and consistently capture the organ dysfunction that drives accurate DRG assignment. If sepsis coding is eating up your team's time or your denial rates are climbing, MedCodex Health offers a no-risk coding pilot. You'll see the quality difference in your first batch of charts.