ICD-10 Codes for Extended-Spectrum Beta-Lactamase(ESBL) Producing Organisms

In the vast, intricate landscape of modern healthcare, a silent and relentless pandemic unfolds not in the headlines, but within the petri dishes and electronic health records of hospitals worldwide. This is the pandemic of antimicrobial resistance (AMR), a formidable challenge where microbes that once succumbed to common antibiotics have evolved sophisticated defenses, rendering our most trusted weapons obsolete. At the forefront of this battle stands a particularly cunning adversary: the Extended-Spectrum Beta-Lactamase (ESBL) producing organism. These bacteria possess a remarkable ability to disarm a wide range of penicillin and cephalosporin antibiotics, cornering clinicians into using last-resort, often more toxic and expensive, treatments.

For the medical coder, the ESBL phenomenon presents a parallel challenge—a complex puzzle of terminology, microbiology, and official coding guidelines. The simple question, “What is the ICD-10 code for ESBL?” belies a labyrinth of clinical nuance and administrative precision. Is ESBL itself the diagnosis? Is it a modifier of an infection? How does it interact with codes for sepsis, pneumonia, or urinary tract infections? Accurate coding for ESBL is not merely an abstract exercise in data entry; it is a critical function that directly impacts patient safety, public health surveillance, antimicrobial stewardship programs, and hospital reimbursement. This article aims to be the definitive guide, demystifying the ICD-10 codes for ESBL by delving deep into the science, the guidelines, and the practical scenarios that coders face every day. We will navigate this complex terrain together, transforming uncertainty into mastery.

2. Understanding the Science: What Exactly is ESBL?

To code a condition accurately, one must first understand its essence. ESBL is not a bacterium itself, nor is it a disease. It is an enzyme—a protein catalyst produced by certain bacteria that confers resistance to antibiotics.

The Beta-Lactam Breakthrough and Bacterial Revenge

The story begins with the beta-lactam ring, a four-atom structure common to the most prolific class of antibiotics ever discovered: penicillins, cephalosporins, monobactams, and carbapenems. For decades, these “beta-lactam” antibiotics were miracle drugs, saving countless lives by inhibiting the formation of the bacterial cell wall, causing the bacterium to swell and burst. However, bacteria are evolutionary survivors. In response, they developed beta-lactamases—enzymes that hydrolyze, or break open, the critical beta-lactam ring, rendering the antibiotic inert. Think of the beta-lactam ring as a key, and the bacterial cell wall as a lock. Beta-lactamase is the tool that breaks the key before it can ever turn the lock.

Initially, these enzymes were only effective against penicillins. But through the relentless selective pressure of antibiotic overuse and the remarkable ability of bacteria to share genetic material, these enzymes evolved. The “Extended-Spectrum” in ESBL refers to this expanded capability. ESBLs are a variant of beta-lactamases that have mutated to hydrolyze a much broader spectrum of beta-lactam antibiotics, including later-generation penicillins (e.g., piperacillin) and critically important cephalosporins (e.g., ceftriaxone, cefotaxime, and ceftazidime). This evolution was a devastating countermove in the arms race between humans and microbes.

The Molecular Mechanics of ESBL

The power of ESBLs lies primarily in their ability to target third-generation cephalosporins, which are workhorse antibiotics for treating serious infections like meningitis, sepsis, and hospital-acquired pneumonia. The most common types of ESBL enzymes are derived from the TEM and SHV families, but the CTX-M group has become the most prevalent worldwide, particularly in community settings. The gene encoding for these enzymes is often located on plasmids—small, mobile pieces of DNA that can be easily transferred not only between bacteria of the same species but also between different species. This plasmid-mediated transfer is the engine behind the rapid and widespread dissemination of ESBL resistance.

Common ESBL-Producing Pathogens: A Rogues’ Gallery

While many bacteria can acquire the ability to produce ESBL, the vast majority of clinical infections are caused by members of the Enterobacteriaceae family:

• Escherichia coli (E. coli): The most common culprit, particularly in community-onset urinary tract infections (UTIs).

• Klebsiella pneumoniae: A frequent cause of hospital-acquired infections, including pneumonia, bloodstream infections, and UTIs.

• Proteus mirabilis: Often associated with complicated UTIs and healthcare-associated infections.

When these organisms test positive for ESBL production, they are designated as ESBL-E. coli, ESBL-K. pneumoniae, etc. This specificity is crucial for clinical management and, as we will see, for precise ICD-10 coding.

3. The Clinical Impact of ESBL: Why Accurate Coding Matters

The emergence of ESBL-producing organisms has fundamentally altered the clinical landscape, making accurate ICD-10 coding more important than ever.

Therapeutic Challenges and Treatment Options

When a laboratory confirms an ESBL-producing organism, it immediately narrows the field of effective antibiotics. Standard third-generation cephalosporins become unreliable, creating a significant risk of treatment failure if prescribed empirically. Clinicians are forced to turn to alternative agents, which often come with significant trade-offs:

• Carbapenems (e.g., meropenem, imipenem): These are often considered the drugs of choice for serious ESBL infections. However, they are broad-spectrum agents that require intravenous administration and are a last line of defense against many Gram-negative bacteria. Their overuse drives the emergence of even more dangerous resistance, such as carbapenem-resistant Enterobacteriaceae (CRE).

• Beta-lactam/beta-lactamase inhibitor combinations (e.g., piperacillin-tazobactam): In some cases, these may be effective, but resistance can occur.

• Other options: Non-beta-lactam antibiotics like fluoroquinolones, aminoglycosides, or trimethoprim-sulfamethoxazole may be used if the organism is susceptible. However, ESBL-producing organisms often carry resistance genes to these other classes as well, creating multidrug-resistant (MDR) profiles.

The Domino Effect: Increased Morbidity, Mortality, and Healthcare Costs

The consequences of ESBL infections extend far beyond the initial treatment choice. Studies consistently show that infections caused by ESBL-producing organisms are associated with:

• Delayed Effective Therapy: The time between culture collection and ESBL confirmation can be 48-72 hours. If the initial empiric antibiotic was ineffective, this delay can lead to clinical deterioration.

• Increased Morbidity and Mortality: The combination of delayed therapy and the inherent virulence of these organisms leads to higher rates of treatment failure, prolonged illness, and increased mortality.

• Prolonged Hospital Stays: Patients with ESBL infections often have significantly longer lengths of stay compared to those with susceptible infections.

• Significant Economic Burden: The need for more expensive antibiotics, longer hospitalizations, and more intensive management results in dramatically higher healthcare costs.

This is where the coder’s role becomes vital. By accurately capturing the ESBL designation, the coded data feeds into:

• Antimicrobial Stewardship Programs: Accurate data allows these programs to track local resistance patterns and guide empiric therapy guidelines.

• Hospital Epidemiology: Infection control teams use this data to identify and contain outbreaks.

• Quality Metrics and Reimbursement: ESBL status can impact severity of illness scores, which influence DRG assignment and risk-adjusted outcome measures.

• Public Health Surveillance: National and global health agencies rely on aggregated coded data to monitor the alarming trend of AMR.

4. Deciphering the ICD-10-CM Code Set for ESBL

The ICD-10-CM manual provides specific codes to capture the presence of ESBL-producing organisms. These codes are found in Chapter 1: Certain Infectious and Parasitic Diseases (A00-B99), under the category B95-B97, Bacterial and viral infectious agents.

The Primary Code: B96.20 – Unspecified ESBL

• B96.20 – Extended spectrum beta lactamase (ESBL) resistance, unspecified
  This code is used when the medical record documentation states that an infection is caused by an ESBL-producing organism, but the specific type of bacterium (e.g., E. coli, Klebsiella) is not identified as the cause of the current infection, or the documentation is non-specific (e.g., “ESBL UTI” without naming the organism). It is a “catch-all” code when greater specificity is not available.

Specific Organism Codes: B96.21, B96.22, B96.23

For precise coding, ICD-10-CM offers codes for the most common ESBL producers. These codes should be used whenever the specific organism is documented.

• B96.21 – Extended spectrum beta lactamase (ESBL) resistance, Escherichia coli [E. coli]
  This code is for infections or colonization where the causative/colonizing agent is specifically identified as ESBL-producing E. coli.

• B96.22 – Extended spectrum beta lactamase (ESBL) resistance, Klebsiella pneumoniae
  This code is for infections or colonization where the causative/colonizing agent is specifically identified as ESBL-producing K. pneumoniae.

• B96.23 – Extended spectrum beta lactamase (ESBL) resistance, other specified bacterial agent
  This code is used for other, less common ESBL-producing bacteria that are specifically identified, such as Proteus mirabilis, Klebsiella oxytoca, or Salmonella species.

Crucial Note: The codes in the B96.2- category are never used as a principal diagnosis. They are additional codes used to provide information about the infectious agent’s resistance properties. They must always be reported alongside the code for the actual infection or condition.

The Crucial Role of the Microbiology Lab

The definitive assignment of an ESBL code rests entirely on the laboratory report. Coders must review microbiology results to confirm:

1. The identity of the organism (e.g., Escherichia coli).

2. The antimicrobial susceptibility testing (AST) results, which will explicitly state “ESBL Positive,” “ESBL Producer,” or something similar.

The lab may use phenotypic tests (e.g., combination disk test, broth microdilution) or molecular tests (e.g., PCR) to confirm ESBL production. The coder’s job is to translate this lab-confirmed data into the appropriate B96.2- code.

5. The Art and Science of Sequencing: A Step-by-Step Guide

The correct sequencing of codes—which code to list first—is governed by the ICD-10-CM Official Guidelines for Coding and Reporting. The following scenarios illustrate the proper application.

Scenario 1: ESBL-E. coli Urinary Tract Infection

• Presentation: A 65-year-old female presents with dysuria, frequency, and fever. Urine culture is obtained.

• Laboratory Report: “>100,000 CFU/mL Escherichia coli. ESBL Positive. Resistant to ceftriaxone, ciprofloxacin; Sensitive to nitrofurantoin, meropenem.”

• Physician Documentation: “Acute cystitis due to ESBL-producing E. coli. Will treat with nitrofurantoin.”

Coding:

1. N30.00 – Acute cystitis without hematuria (Principal Diagnosis)

2. B96.21 – Extended spectrum beta lactamase (ESBL) resistance, Escherichia coli [E. coli] (Additional Code)

Rationale: The acute cystitis is the reason for the encounter. The B96.21 code provides essential detail about the infectious agent’s resistance profile.

Scenario 2: ESBL-K. pneumoniae Hospital-Acquired Pneumonia

• Presentation: A 72-year-old male on a ventilator in the ICU develops a new fever and purulent sputum. A bronchoalveolar lavage (BAL) is performed.

• Laboratory Report: “BAL culture: Heavy growth Klebsiella pneumoniae. ESBL Positive.”

• Physician Documentation: “Ventilator-associated pneumonia (VAP) due to ESBL Klebsiella pneumoniae.”

Coding:

1. J95.851 – Ventilator-associated pneumonia (Principal Diagnosis)

2. B96.22 – Extended spectrum beta lactamase (ESBL) resistance, Klebsiella pneumoniae (Additional Code)

Rationale: The VAP is the condition treated during this encounter. The ESBL code adds critical information about the organism’s resistance.

Scenario 3: ESBL Colonization vs. Infection

This is a critical distinction. Colonization means the organism is present in or on the body but is not causing any signs or symptoms of disease. Infection means the organism is present and causing an adverse immune response or tissue damage.

• Scenario 3A: Colonization

  • Presentation: A patient is admitted for elective total hip replacement. A pre-admission nasal and perirectal swab is performed as part of a surveillance program for multidrug-resistant organisms (MDRO).

  • Laboratory Report: “Surveillance perirectal swab: ESBL-producing Escherichia coli isolated.”

  • Clinical Note: “Patient found to be colonized with ESBL-E. coli. No signs of active infection. Will proceed with surgery as planned.”

  • Coding: Z22.321 – Carrier of Extended Spectrum Beta Lactamase (ESBL) Escherichia coli [E. coli]. No infection code is assigned because there is no active infection.

• Scenario 3B: Infection

  • If the same colonized patient later develops a UTI with the same organism, you would then code the UTI (e.g., N39.0) with B96.21 as an additional code.

Scenario 4: The Complex Patient with Multiple Conditions

• Presentation: A patient with a history of ESBL colonization is admitted with urosepsis.

• Laboratory Report: Blood and urine cultures grow ESBL-E. coli.

• Physician Documentation: “Sepsis and acute pyelonephritis due to ESBL E. coli.”

Coding:

1. A41.51 – Sepsis due to Escherichia coli [E. coli] (Principal Diagnosis for sepsis due to a specified bacterium)

2. N10 – Acute pyelonephritis (Additional code for the associated UTI)

3. B96.21 – Extended spectrum beta lactamase (ESBL) resistance, Escherichia coli [E. coli] (Additional code to specify the resistance)

Rationale: The coding guidelines instruct that when the causal organism is specified, the code from category A40-A41 should be used. The B96.21 code is still required to specify the resistance profile of that specified organism. Note that you would not use B96.20 in this case, as the organism is specified.

 ICD-10-CM Code Selection Guide for ESBL

6. Documentation: The Bedrock of Accurate Coding

The accuracy of coding is inextricably linked to the quality of clinical documentation. Vague or inconsistent terminology creates ambiguity and risk.

• Poor Documentation: “UTI, patient has ESBL.” (Is the organism known? Is this a historical colonization or the cause of the current UTI?)

• Excellent Documentation: “Acute pyelonephritis due to ESBL-producing Escherichia coli, confirmed by urine culture.” (Clear condition, specific organism, confirmed by lab.)

Coders must be trained to recognize insufficient documentation. Phrases like “history of ESBL” are particularly problematic. Does this mean the patient is a known carrier (Z22.321) or that the current infection is caused by a historically documented ESBL organism (B96.2-)? The documentation must link the resistance to the current condition.

Engaging in Provider Queries: Best Practices

When documentation is unclear, the coder must initiate a formal query. A well-constructed query is non-leading and presents clinical facts.

• Example of a Good Query:
  “Dear Dr. Smith, The microbiology report for Mr. Jones’s blood culture is positive for Escherichia coli, which is noted to be ESBL-positive. Your note documents ‘Sepsis.’ For accurate code assignment, could you please clarify the causal relationship? Is the sepsis due to the ESBL-producing Escherichia coli?”

This query provides the facts and allows the physician to make a clinical determination, resulting in clear, auditable documentation.

7. The Intersection with DRGs and Quality Reporting

<a name=”ms-drg-impact”></a>Impact on MS-DRG Assignment and Reimbursement

In the inpatient setting, codes are used to assign a Medicare Severity-Diagnosis Related Group (MS-DRG), which determines the fixed payment for the hospitalization. ESBL codes play a significant role in this process by impacting the patient’s Complexity Level.

Infections caused by multidrug-resistant organisms like ESBL are considered more complex and resource-intensive to treat. The addition of a B96.2- code to an infection can:

• Increase the patient’s Risk of Mortality (ROM) and Severity of Illness (SOI) scores.

• Cause a case to “bump up” to a higher-weighted, higher-paying MS-DRG. For example, a simple pneumonia (MS-DRG 177) could move to a more complex respiratory infection DRG (MS-DRG 176) with the addition of a major Complication/Comorbidity (MCC) like an ESBL infection, significantly impacting reimbursement.

ESBL and Hospital-Acquired Infection (HAI) Reporting

ESBL infections, particularly those that are hospital-onset, are closely monitored as indicators of healthcare quality and patient safety. Accurate coding is essential for:

• Internal Quality Metrics: Hospitals track HAIs to target infection prevention efforts.

• Public Reporting: In many countries, rates of certain HAIs are publicly reported.

• Pay-for-Performance Programs: Programs like the Centers for Medicare & Medicaid Services (CMS) Hospital-Acquired Condition Reduction Program can financially penalize hospitals with high HAI rates.

Precise coding with B96.2- codes allows for the accurate identification and tracking of these serious infections, making coders key players in a hospital’s quality and safety infrastructure.

8. FAQs: Answering Common Questions on ESBL Coding

Q1: Can I code for ESBL if the physician hasn’t documented it, but the lab report is positive?
A: The ICD-10-CM Official Guidelines, Section IV.A.1, state that for reporting purposes, the code(s) that identifies the diagnosis must be based on “medical record documentation and diagnostic test results.” The lab report is part of the medical record. However, the physician must link the organism to a clinical condition (e.g., document the infection). If the lab report is the only source, it is best practice to query the physician for confirmation and clinical correlation to ensure the ESBL organism is being treated as the cause of the infection.

Q2: What is the difference between Z22.321 (Carrier) and B96.21 (ESBL E. coli)?
A: Z22.321 is used when the patient is colonized (the organism is present but not causing disease). B96.21 is an additional code used to specify the resistance of an organism that is causing a current, active infection. You would not use both for the same encounter for the same organism.

Q3: How do I code for an infection with a pan-sensitive E. coli?
A: You would only code the infection itself (e.g., N39.0). You would not assign a code from the B96 series, as there is no specified resistance to report. If the physician documents the organism, you could use B96.20 as an additional code only if it’s part of the causal organism’s identification, but the primary focus is the infection code.

Q4: What if the documentation says “possible ESBL” or “ESBL suspected”?
A: Do not code suspected conditions. Codes should only be assigned for confirmed diagnoses. “Possible,” “probable,” “suspected,” and “rule out” are not coded as if they exist. Wait for final, confirmed lab results and physician documentation.

Q5: Are there codes for other types of beta-lactamase resistance, like AmpC or carbapenemase (KPC)?
A: Yes. The ICD-10-CM system has codes for other resistance mechanisms. For example:

• AmpC beta-lactamase: R78.81 (Bacteremia) is not the correct code. There is no specific code for AmpC; you would use the infection code and the code for the specific resistant organism if known, potentially using Z16.- codes for resistance to specific antibiotics, but this is an area of complexity requiring careful guideline review.

• Carbapenemase resistance: Codes like B96.82 (KPC), B96.83 (NDM-1), and B96.84 (Other carbapenemase resistance) are available and follow the same coding principles as ESBL codes.

9. Conclusion and Additional Resources

Accurate ICD-10 coding for ESBL-producing organisms is a critical skill that bridges clinical care, public health, and healthcare finance. It requires a foundational understanding of microbiology, meticulous attention to laboratory data, and strict adherence to official coding guidelines and sequencing rules. By precisely capturing this information, medical coders provide the essential data that drives antimicrobial stewardship, informs infection control, ensures appropriate reimbursement, and ultimately contributes to the global fight against antimicrobial resistance.

Conclusion Summary:

• ESBL coding demands precision, using specific organism codes (B96.21-B96.23) over the unspecified code (B96.20) whenever possible.

• These codes are always additional diagnoses, sequenced alongside the code for the active infection or condition.

• Clear clinical documentation and a collaborative relationship with providers through the query process are fundamental to coding accuracy and integrity.

Additional Resources:

• CDC: Antibiotic Resistance Threats in the United States, 2024: https://www.cdc.gov/drugresistance/index.html (Provides the latest data and context on ESBL and other resistant threats.)

• ICD-10-CM Official Guidelines for Coding and Reporting: https://www.cms.gov/medicare/coding-billing/icd-10-codes/2025-icd-10-cm (The definitive source for coding rules; review annually.)

• American Health Information Management Association (AHIMA): https://www.ahima.org (Offers resources, practice briefs, and education on coding best practices.)

• Society for Healthcare Epidemiology of America (SHEA): https://shea-online.org (Provides clinical guidelines on managing MDROs, including ESBL.)

 

Date: September 28, 2025
Author: The  Medical Coding & Clinical Advisory Team
Disclaimer: The information contained in this article is for educational and informational purposes only and is not intended as a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of your physician or other qualified health provider with any questions you may have regarding a medical condition or treatment. The codes and guidelines referenced are based on the most current information available at the time of writing and are subject to change. Always consult the official ICD-10-CM Coding Guidelines and your facility’s coding policies for definitive guidance.