Coding Sepsis in ICD-10-CM

Updated December, 21, 2023

There has been a bit of confusion concerning the coding of sepsis and severe sepsis. One of the most confusing thing about coding sepsis for some is the fact that only one code for the organism is all that is required in many cases. When the term severe sepsis is present it can be a bit more difficult. Let’s begin by having a look at the actual coding guidance concerning sepsis.

Section I.C.1.d.1b

The coding of severe sepsis requires a minimum of two codes: first a code for the underlying systemic infection, followed by a code from subcategory R65.2, Severe sepsis. If the causal organism is not documented, assign code A41.9, Sepsis, unspecified organism, for the infection. Additional code(s) for the associated acute organ dysfunction are also required. Due to the complex nature of severe sepsis, some cases may require querying the provider prior to assignment of the codes.

Section I.C.1.d.1a

If a patient has sepsis and an acute organ dysfunction, but the medical record documentation indicates that the acute organ dysfunction is related to a medical condition other than the sepsis, do not assign a code from subcategory R65.2, Severe sepsis. An acute organ dysfunction must be associated with the sepsis in order to assign the severe sepsis code. If the documentation is not clear as to whether an acute organ dysfunction is related to the sepsis or another medical condition, query the provider.

Section I.C.1.d.4

If the reason for admission is both sepsis or severe sepsis and a localized infection, such as pneumonia or cellulitis, a code(s) for the underlying systemic infection should be assigned first and the code for the localized infection should be assigned as a secondary diagnosis. If the patient has severe sepsis, a code from subcategory R65.2 should also be assigned as a secondary diagnosis. If the patient is admitted with a localized infection, such as pneumonia, and sepsis/severe sepsis doesn’t develop until after admission, the localized infection should be assigned first, followed by the appropriate sepsis/severe sepsis codes.

Section I.C.1.d.2

Septic shock generally refers to circulatory failure associated with severe sepsis, and therefore, it represents a type of acute organ dysfunction.  For cases of septic shock, the code for the systemic infection should be sequenced first, followed by code R65.21, Severe sepsis with septic shock or code T81.12, Postprocedural septic shock. Any additional codes for the other acute organ dysfunctions should also be assigned. As noted in the sequencing instructions in the Tabular List, the code for septic shock cannot be assigned as a principal diagnosis. (official coding guidelines 2023)

As you can see, the guidance is very clear how we should be coding sepsis and when coding severe sepsis is acceptable. A few other key points to remember about sepsis include:

• A code from R65.2, Severe sepsis, should not be assigned unless severe sepsis or an associated acute organ dysfunction is documented.
• The term urosepsis is a nonspecific term and it is not the same as sepsis. Query for additional information
• If a patient has sepsis and associated acute organ dysfunction or multiple organ dysfunction (MOD), follow the instructions for coding severe sepsis.

More than ever before, ICD-10 coding is critical for getting the reimbursement you deserve under PDGM. Boost compliance, save your staff valuable time and reduce costs with Corridor’s outsourced coding and clinical documentation review

About Corridor

For over 30 years, Corridor has partnered with home-based care providers, delivering powerful solutions to support the unique challenges of caring for patients in the home. Our team of operating executives, clinicians, and nationally renowned industry experts have run provider organizations and resolved the same challenges you face.

To receive the most important industry updates, insights and news impacting home health and hospice, please make sure to sign up for our weekly newsletter.

Explore Corridor’s Solutions

Share This Story, Choose Your Platform!