Sepsis is a dysregulated host response to infection that leads to life-threatening organ dysfunction. Accurate ICD-10 coding for sepsis is essential because it affects clinical data, severity reporting, quality metrics, reimbursement, and compliance with payer and regulatory expectations. Misuse of sepsis codes drives denials, inaccurate case mix indices, and downstream revenue cycle delays.
This guide explains the ICD-10-CM code for Sepsis, unspecified organism, when to use it, clear exclusion scenarios, related codes to consider, billing best practices, and audit-focused documentation tips to improve coding accuracy and reimbursement outcomes for revenue cycle management (RCM) teams.
The ICD-10-CM Code for Sepsis, unspecified organism is A41.9.
Sepsis, unspecified organism denotes a clinical diagnosis of sepsis—systemic inflammatory response with suspected or confirmed infection that results in organ dysfunction—where the treating clinician documents sepsis but does not identify the causative organism in the record. In the ICD-10-CM classification, A41.9 is the default code when sepsis is documented without organism-specific detail and when no more precise A40–A41 series code applies. Use of this code implies systemic infection severe enough to meet clinical sepsis criteria, but without organism identification captured in documentation or lab results at the time of coding.
Use Sepsis, unspecified organism when a patient meets sepsis clinical criteria (infection plus organ dysfunction) and initial cultures, PCR, or other microbiology testing are pending or negative, and the clinician documents "sepsis" without specifying an organism. Assign A41.9 when no organism-specific A41 code applies and there is explicit clinician documentation of sepsis.
Use Sepsis, unspecified organism on the initial ED or admission claim when cultures have been obtained but results remain pending and the attending documents sepsis. Update codes on subsequent claims or discharge coding if an organism is later identified and documented; the initial use of A41.9 is appropriate for claims filed before specificity is available.
Use Sepsis, unspecified organism for outpatient encounters or follow-ups when the clinician documents a diagnosis of sepsis in the problem list or visit note and the record does not provide organism-specific information. This can apply to care coordination, wound checks, or antibiotic management visits referencing a prior sepsis event without further specificity.
Do not use Sepsis, unspecified organism when the record names the causative organism (for example, Staphylococcus aureus, Escherichia coli, MRSA). Instead, use the appropriate organism-specific sepsis code from the A40–A41 series (organism-specific A41.x code) to reflect clinical specificity and support correct DRG assignment.
Do not rely solely on Sepsis, unspecified organism when the clinician documents severe sepsis or septic shock. Use the R65.20 or R65.21 codes for severe sepsis with or without septic shock along with the underlying infection code (organism-specific A41.x or A41.9) per coding guidelines. Simple assignment of A41.9 without the R65 codes underreports severity and risks downcoding.
Do not code Sepsis, unspecified organism for localized infections (for example, uncomplicated cellulitis, localized pneumonia) that do not meet sepsis criteria. Use the appropriate site-specific infection code (e.g., pneumonia, urinary tract infection) and only code sepsis if clinician documentation indicates systemic involvement and organ dysfunction.
| Condition | Code | When It Is Used | When It Is Not Used |
|---|---|---|---|
| Sepsis, unspecified organism | A41.9 | When clinician documents sepsis but no organism is identified or documented; cultures pending or negative | When organism is identified or when severe sepsis/septic shock is separately documented without accompanying R65 code |
| Sepsis due to Staphylococcus aureus | A41.0 | When clinical documentation names Staphylococcus aureus as the causative organism for sepsis | When organism is not identified or when documentation only states "sepsis" without organism detail |
| Severe sepsis without septic shock | R65.20 | When clinician documents severe sepsis (sepsis with acute organ dysfunction) without septic shock; assign alongside the underlying infection code | When only sepsis is documented without evidence of organ dysfunction or when septic shock is present |
| Severe sepsis with septic shock | R65.21 | When clinician documents severe sepsis with septic shock; assign with the causative infection code (organism-specific or A41.9) | When sepsis is present without organ dysfunction or when documentation lacks explicit septic shock language |
Ensure progress notes, problem lists, and discharge summaries explicitly state "sepsis" and describe organ dysfunction (e.g., hypotension requiring vasopressors, acute kidney injury with creatinine rise). Explicit clinician statements support the medical necessity for inpatient level of care and defend case mix and DRG assignments.
Establish a workflow to update codes when culture, PCR, or pathology results return. If an organism is identified during the stay, replace A41.9 with the organism-specific code and add R65 codes if severe sepsis or septic shock is documented. Timely reconciliation prevents missed revenue and post-payment adjustments.
Document therapies and physiological data that justify sepsis care intensity: vasopressors, mechanical ventilation, fluid resuscitation, lactate values, and antibiotic escalation. Coders should link these interventions to sepsis documentation to substantiate medical necessity and reduce payer challenges.
Leverage CombineHealth.ai's AI-powered platform to flag documentation inconsistencies, suggest organism-specific codes when microbiology results are present, and surface missing R65 codes when organ dysfunction is documented. Automated validation reduces coding errors and improves first-pass acceptance.
Regularly review sepsis cases for coding accuracy, denial patterns, and documentation gaps. Provide targeted education to clinicians on required sepsis documentation and to coders on evolving payer expectations. Use audit findings to refine templates and clinical documentation improvement (CDI) prompts.
Coding for sepsis has direct impact on revenue cycle outcomes:
Accurate ICD-10 coding is critical for healthcare revenue cycle performance. CombineHealth.ai's AI-powered platform helps RCM teams ensure coding accuracy, reduce denials, and optimize reimbursement through intelligent denial management and claim validation. CombineHealth.ai's intelligent platform provides automated claim scrubbing and coding validation to catch errors before submission, reducing denials and improving first-pass acceptance rates.
Q1: What is the ICD-10 code for sepsis?
The ICD-10-CM code for Sepsis, unspecified organism is A41.9. This code applies when a clinician documents sepsis but the causative organism is not identified in the record or when cultures are pending.
Q2: When should I use Sepsis, unspecified organism versus related codes?
Use Sepsis, unspecified organism (A41.9) when sepsis is documented without organism specificity. Use organism-specific A40–A41 codes when the clinician names the pathogen. For severe sepsis or septic shock, add the appropriate R65.20 or R65.21 codes alongside the infection code per coding guidelines.
Q3: What documentation is required when coding for sepsis?
Documentation should include an explicit clinician statement of sepsis, evidence or description of organ dysfunction (e.g., hypotension, altered mental status, acute renal failure), relevant interventions (vasopressors, intubation), and microbiology results when available. Clear temporal linkage between infection and organ dysfunction strengthens coding defensibility.
Q4: What are common denial reasons when coding for sepsis?
Common denials arise from lack of organism specificity when required, missing severe sepsis/septic shock codes when organ dysfunction is documented, and insufficient clinical documentation to support the diagnosis. See our guide on denial management for strategies to reduce these denials: See our guide on denial management