ICD-10 Code B96.2: E. coli as the Cause of Diseases Classified Elsewhere — Complete Coding & Billing Guide

ICD-10-CM code B96.2 identifies Escherichia coli [E. coli] as the causative bacterial agent in an infectious disease that is classified and coded under a different ICD-10 chapter. It is a non-billable header code — meaning it cannot be submitted on a claim as written. Coders must assign one of its five specific subcodes (B96.20–B96.29) to capture the precise E. coli strain identified by laboratory testing. This guide covers correct subcode selection, documentation requirements, sequencing rules, and the billing pitfalls most likely to trigger a denial or audit flag.

What Does ICD-10 Code B96.2 Mean?

B96.2 is a category-level (header) code within ICD-10-CM Chapter 1, under the subsection “Bacterial and Viral Infectious Agents” (B95–B97). It signals that Escherichia coli is the identified organism responsible for an infection that is itself coded in another chapter — for example, a urinary tract infection (N39.0), bacterial sepsis (A41.51), or E. coli pneumonia (J15.5).

Key attributes at a glance:

• Not valid for billing — B96.2 alone will be rejected by payers; a 5th-character subcode is always required
• Always an additional code — never the principal or primary diagnosis
• Organism-specificity — used only when E. coli has been confirmed as the infectious agent, typically by culture
• Effective in FY 2026 — no description changes from prior fiscal year; valid through September 30, 2026 per the CMS ICD-10-CM FY2026 release

What Conditions and Diagnoses Does B96.2 Cover?

A B96.2x subcode applies whenever E. coli is documented as the causative organism for an active infectious condition, regardless of the body site. Common clinical presentations include:

• Urinary tract infections and complicated UTIs (including pyelonephritis and urosepsis)
• Bacterial sepsis and bloodstream infections (bacteremia)
• Neonatal infections, including neonatal sepsis and meningitis
• Gastrointestinal illness, including traveler’s diarrhea and hemorrhagic colitis (Shiga toxin-producing strains)
• Wound infections and surgical site infections with documented E. coli
• Healthcare-associated pneumonia caused by gram-negative organisms, confirmed as E. coli
• Intra-abdominal infections such as peritonitis or abscess with positive E. coli culture

What Does B96.2 Specifically Exclude?

The B96.2 category does not apply in these situations:

• E. coli intestinal infections reported under A04.0–A04.4 — those codes already incorporate the organism identity
• Sepsis due to Escherichia coli, which has its own specific code: A41.51 (this is sequenced as the principal diagnosis, with B96.2x as additional only when further organism specificity is needed per facility policy)
• Neonatal E. coli infection with its own combination code (P36.4) — a B96.2x subcode would be redundant here
• Conditions for which the ICD-10-CM Tabular instructs “code first” the underlying disease without a B96.2x pairing

When Is a B96.2 Subcode the Right Choice?

Selecting a B96.2x code correctly requires satisfying a defined set of clinical and documentation criteria. Follow this decision sequence:

1. Confirm organism identification — A urine culture, blood culture, wound culture, or comparable laboratory report must name Escherichia coli as the causative agent. Clinical suspicion alone is insufficient.
2. Identify the primary infectious condition — Determine the infection site (UTI, sepsis, pneumonia, etc.) and assign the appropriate ICD-10 code for that condition first.
3. Verify the primary code has no built-in organism specificity — If the primary code already specifies E. coli (e.g., A41.51 for sepsis, P36.4 for neonatal sepsis), a B96.2x subcode is generally not required as an additional code unless the payer or facility requires further strain documentation.
4. Determine the E. coli strain — Review the lab report to distinguish STEC O157 (B96.21), other specified STEC (B96.22), unspecified STEC (B96.23), or non-STEC E. coli (B96.29 or B96.20).
5. Assign the most specific subcode available — Never report the parent B96.2 header; always report to the 5th character.

How Do the B96.2 Subcodes Differ From Each Other?

Subcode	Description	Key Clinical Distinction	Billable?
B96.20	Unspecified E. coli	Lab confirms E. coli; strain type not documented	Yes
B96.21	STEC O157	Culture or PCR confirms Shiga toxin-producing E. coli serotype O157:H7	Yes
B96.22	Other specified STEC	STEC confirmed, specific non-O157 serotype identified	Yes
B96.23	Unspecified STEC	STEC confirmed by toxin assay; serotype not determined	Yes
B96.29	Other E. coli (non-STEC)	Confirmed E. coli, not Shiga toxin-producing; specific strain documented	Yes

In practice, coders frequently encounter B96.20 as the default when providers note “E. coli” on the chart without referencing strain type. Before defaulting to B96.20, query whether the lab report distinguishes toxin production — auditors commonly flag B96.20 when the underlying culture result clearly indicates a STEC strain.

What Documentation Is Required to Support a B96.2x Code?

What Must the Provider Document in Clinical Notes?

Proper support for any B96.2x subcode requires these elements in the medical record:

1. A provider-documented diagnosis that names E. coli as the causative organism — not just a positive culture result in isolation
2. The infection site or condition (e.g., “UTI due to E. coli,” “E. coli sepsis”) explicitly linking the organism to the clinical condition
3. Treatment initiation consistent with bacterial infection (antibiotics targeted to gram-negative organisms confirm clinical significance)
4. For STEC codes (B96.21–B96.23), laboratory confirmation of Shiga toxin production via culture, PCR, or enzyme immunoassay
5. For B96.22, the specific serotype must be documented; without it, B96.23 (unspecified STEC) is correct

Which Lab Results Support This Code?

Supporting laboratory findings that coders should locate in the chart include:

• Urine, blood, wound, or CSF culture with organism identification naming E. coli
• Sensitivity and susceptibility report (also used to support antimicrobial resistance codes such as Z16.12 for ESBL-producing strains)
• Shiga toxin assay (EIA or PCR) for STEC distinction
• Serotyping report identifying the O-antigen group (e.g., O157) for B96.21 or B96.22
• Urinalysis with findings consistent with infection (supportive but not independently sufficient)

What Is the Documentation Standard for Inpatient vs. Outpatient Settings?

Setting	Standard	Key Difference
Inpatient	UHDDS guidelines — code all conditions that affect care, even if not the primary reason for admission	B96.2x should be coded if E. coli is documented and influences treatment, even if the UTI or sepsis is primary
Outpatient	Code only confirmed diagnoses — do not code based on signs/symptoms or suspected organisms	B96.2x requires a confirmed culture result and provider attestation before assignment

How Does B96.2 Affect Medical Billing and Claims?

Because B96.2x codes are always sequenced as additional diagnoses, they do not function as standalone reason-for-visit codes. Their billing impact is indirect but meaningful:

• They can shift a claim into a higher-severity MS-DRG in inpatient settings, particularly when paired with sepsis (MS-DRGs 867–869)
• Payers may use B96.2x presence to validate medical necessity for broad-spectrum IV antibiotic regimens
• Some Medicare Administrative Contractors (MACs) track organism codes to identify antimicrobial stewardship compliance and may scrutinize antibiotic choice against documented pathogen
• Submission of the non-billable B96.2 header (without a 5th character) will result in an immediate claim rejection or edit failure under most clearinghouses

What CPT Codes Are Commonly Billed With B96.2x?

CPT Code	Description	Typical Pairing Context
87088	Culture, bacterial; urine	UTI with E. coli, outpatient
87040	Culture, bacterial; blood	Bacteremia or sepsis workup
87184	Antibiotic sensitivity test	Documenting ESBL or resistance
87507	Infectious agent detection, GI pathogen panel	STEC/O157 gastrointestinal infections
99232–99233	Subsequent hospital care	Inpatient management of E. coli sepsis
99291–99292	Critical care	Severe sepsis or septic shock encounters

Are There Prior Authorization or Coverage Restrictions?

• Most payers do not require prior authorization specifically for B96.2x as an additional code
• When paired with extended IV antibiotic therapy (e.g., ertapenem, pip-tazo), some commercial payers may require clinical criteria documentation or step therapy verification
• Outpatient infusion claims using B96.2x as a supporting diagnosis should confirm payer LCD (Local Coverage Determination) requirements for the primary infection code
• ESBL-producing E. coli cases should also include Z16.12 (resistance to extended-spectrum beta-lactamase antibiotics) to support medical necessity for carbapenem therapy

What Coding Errors Should You Avoid With B96.2?

These are the most frequently flagged errors in coding audits involving B96.2 and its subcodes:

1. Submitting B96.2 (the header) as the billable code — always drill down to B96.20 through B96.29
2. Coding B96.2x as the principal diagnosis — this code category is instructed for use as an additional code only; the primary infection drives sequencing
3. Using B96.29 when B96.21 is indicated — if the lab report specifies STEC O157, B96.21 is the correct code; using B96.29 (“other E. coli”) understates clinical specificity
4. Assigning B96.2x without a positive culture — clinical suspicion or symptom-only documentation does not support this code; culture or equivalent confirmatory testing must be on file
5. Omitting Z16.12 for ESBL-producing strains — failing to report antimicrobial resistance alongside B96.2x is a recurring audit finding in antibiotic stewardship reviews
6. Duplicating with combination codes — codes like A41.51 (sepsis due to E. coli) already incorporate organism identity; adding B96.2x when it is redundant creates claim inconsistency and may trigger review

What Do Auditors Look for When Reviewing B96.2 Claims?

During coding audit preparation, reviewers typically focus on:

• Presence of a culture report in the medical record to support the organism code
• Correct sequencing — infection code leading, B96.2x following
• Whether the STEC-vs-non-STEC distinction was properly made based on lab documentation
• Consistency between the antibiotic prescribed and the organism/resistance reported
• Whether the parent code (B96.2) was erroneously submitted instead of a specific subcode
• Documentation of provider attestation that E. coli was clinically significant, not merely a contaminant or colonizer

How Does B96.2 Relate to Other ICD-10 Codes?

Understanding the diagnosis code specificity hierarchy around B96.2 helps coders avoid both under-coding and redundancy.

Related Code	Relationship	Key Distinction
A41.51	Sepsis due to E. coli — combination code	Replaces B96.2x as primary dx in sepsis; B96.2x additional only if strain specificity needed
A04.0	Enteropathogenic E. coli intestinal infection	A04.0 fully specifies E. coli GI infection; B96.2x not required
A04.3	Enterohaemorrhagic E. coli — STEC-related GI illness	Use A04.3 for STEC GI illness; B96.21–B96.23 used when STEC causes a non-GI infection
P36.4	Sepsis of newborn due to E. coli	Combination neonatal code; B96.2x typically not added
J15.5	Unspecified E. coli pneumonia	Use with B96.2x when provider documents E. coli as the pathogen
N39.0	UTI, site not specified	Pair with B96.2x when E. coli confirmed as the causative organism
Z16.12	Resistance to extended-spectrum beta-lactamase	Add when lab confirms ESBL-producing E. coli

What Is the Correct Code Sequencing When B96.2x Appears With Other Diagnoses?

Per the ICD-10-CM Official Coding Guidelines, Section I.C.1, the sequencing rule for B96 category codes is:

1. Sequence the condition first — the clinical infection (UTI, pneumonia, sepsis) is always the principal or primary diagnosis
2. Add B96.2x as an additional code to identify the E. coli organism
3. Add Z16.xx if antimicrobial resistance is documented — this follows B96.2x in the additional code string
4. Do not sequence B96.2x before any other active, treated condition — it functions exclusively as a supplementary organism identifier

Real-World Coding Scenario — How B96.2x Is Applied in Practice

Patient Encounter: A 68-year-old female is admitted to the hospital with fever, chills, and flank pain. Urinalysis shows pyuria, and blood cultures return positive for Escherichia coli. The attending physician documents “urosepsis due to E. coli” in the discharge summary. The microbiology lab report confirms E. coli, non-STEC, with sensitivity results noted. No ESBL resistance is identified.

Correct Code Application

• A41.51 — Sepsis due to Escherichia coli (principal diagnosis — the combination code captures both the sepsis and organism)
• N10 — Acute pyelonephritis (secondary condition supporting the infectious source)
• B96.29 — Other E. coli as the cause of diseases classified elsewhere (additional — provides strain specificity; non-STEC confirmed by lab)

Common Mistake in This Scenario

• Incorrect: Coding only N39.0 (UTI) as the principal diagnosis when the provider documented sepsis
• Why it fails: The documented principal condition is sepsis, not an uncomplicated UTI; downgrading to N39.0 misrepresents severity, undervalues the claim under MS-DRG logic, and misrepresents the patient’s acuity in the medical record
• Also incorrect: Omitting B96.29 entirely when the lab confirms non-STEC E. coli — doing so leaves organism specificity undocumented and reduces the clinical data value of the record

Frequently Asked Questions About ICD-10 Code B96.2

Is ICD-10 Code B96.2 Valid for Billing in 2026?

ICD-10 code B96.2 is not valid for billing as a standalone code in FY 2026. It is a non-billable header category, and claims submitted with B96.2 (without a 5th character) will be rejected. Coders must select one of its five subcodes — B96.20 through B96.29 — based on E. coli strain documentation.

Can B96.2x Be Used as a Primary Diagnosis?

B96.2x codes cannot function as the primary or principal diagnosis. Per the ICD-10-CM Official Coding Guidelines, these codes are designated for use as additional codes only, identifying the causative organism for an infection that is itself coded in another ICD-10 chapter.

What Is the Difference Between B96.20 and B96.29?

B96.20 designates unspecified E. coli when the laboratory confirms E. coli but the documentation does not specify the strain type. B96.29 is used for other E. coli — confirmed as non-Shiga-toxin-producing but with a specific strain noted in the lab report. When the chart does not specify a strain, B96.20 is the appropriate fallback, but coders should query the provider or lab before defaulting.

When Should I Add Z16.12 Alongside a B96.2x Code?

Z16.12 (resistance to extended-spectrum beta-lactamase antibiotics) should be added as an additional code when the laboratory susceptibility report identifies the E. coli isolate as ESBL-producing. This code supports medical necessity for carbapenem or other reserve antibiotic therapy and is a common omission flagged in revenue cycle compliance audits.

Does B96.2x Apply to Colonization or Just Active Infection?

B96.2x applies only to active, clinically significant infection — not to colonization or asymptomatic carriage. If E. coli is identified on culture but the provider documents colonization only, do not report a B96.2x code. Reporting an organism code without a corresponding active condition constitutes overcoding and is an audit risk.

How Do I Code an ESBL E. coli UTI?

For an ESBL-producing E. coli urinary tract infection, the correct code string is: N39.0 (UTI, site not specified) + B96.29 (other E. coli as the cause) + Z16.12 (ESBL resistance). If the UTI has progressed to sepsis, replace N39.0 with A41.51 as the principal diagnosis.

What Is the Difference Between B96.21 and A04.3?

B96.21 identifies STEC O157 as the causative organism in a non-gastrointestinal infectious condition (e.g., hemolytic uremic syndrome, sepsis). A04.3 is used specifically for STEC-associated gastrointestinal infection (enterohemorrhagic colitis). The two codes are not interchangeable; the clinical presentation and primary condition determine which applies.

Key Takeaways

Every coder working with E. coli-related diagnoses should internalize these core points:

• B96.2 is never billable on its own — always assign a 5th-character subcode (B96.20–B96.29)
• B96.2x is always an additional code — the underlying infection leads in sequencing
• Strain specificity matters — STEC vs. non-STEC distinction changes the subcode and affects clinical data integrity
• Culture documentation is non-negotiable — no positive culture, no organism code
• ESBL resistance requires Z16.12 — omitting this is a top audit flag in antimicrobial stewardship reviews
• Combination codes may make B96.2x redundant — check whether the primary infection code already captures E. coli identity before adding the B96 code
• For deeper guidance on sequencing and organism coding, refer to the ICD-10-CM Official Coding Guidelines, Section I.C.1, published annually by CMS