ESBL Detection and Confirmation: Phenotypic, Molecular, and Reporting Guidelines

Hello. Last lesson separated a carbapenem MIC from evidence of a carbapenemase. The same distinction is central here: an ESBL test investigates a resistance mechanism; an AST result describes the measured response to a particular drug. This lesson develops a practical ESBL confirmation workflow and shows how to communicate its findings without automatically rewriting susceptibility results. Allow about 40 minutes, including the short video and selected readings.

What does an ESBL result establish?

An extended-spectrum β-lactamase (ESBL) is an enzyme that can hydrolyze expanded-spectrum cephalosporins—such as cefotaxime and ceftazidime—and usually aztreonam. Common ESBL families include CTX-M and particular variants of TEM and SHV. The variant matters: finding a TEM or SHV gene name alone does not establish that its encoded enzyme has an extended spectrum.

Many clinically important ESBLs are inhibited by clavulanate. That gives the laboratory an experimental question: Does adding clavulanate restore the activity of a cephalosporin against this isolate? It is a different question from Does this isolate meet the susceptible breakpoint for that cephalosporin?

Read the detection discussion and Table 2 in Extended-spectrum β-lactamases: an update on their characteristics, epidemiology and detection. The table compares CLSI and EUCAST approaches; the paragraphs immediately after it explain why confirmation and clinical AST reporting are no longer necessarily coupled.

The table describes classical confirmation methods, not a rule that every Enterobacterales isolate must receive the same ESBL test. Organism suitability matters. In particular, an organism with an inducible chromosomal AmpC β-lactamase may need a different confirmatory approach from one used for E. coli or Klebsiella pneumoniae: AmpC activity can obscure the effect of clavulanate. Use the current version of your laboratory’s adopted CLSI or EUCAST procedure, including its organism and method restrictions, rather than extending a rule from one species to all Enterobacterales.

Reading a clavulanate combination test

In a combination-disk test, a standardized lawn from a pure isolate receives matched pairs of disks: cefotaxime alone and cefotaxime with clavulanate; ceftazidime alone and ceftazidime with clavulanate. After incubation, measure each inhibition-zone diameter. Compare each drug only with its own clavulanate-containing partner:

For the conventional combination-disk criterion shown in the review, an increase of at least 5 mm for either matched pair supports ESBL production. Both pairs do not have to meet the threshold. Testing both matters because an enzyme may affect cefotaxime and ceftazidime differently. In a broth-based combination test, a qualifying decrease is at least three twofold MIC dilutions—an eightfold reduction—for either cephalosporin when clavulanate is added. For example, a change from 16 to 2 mg/L is eightfold. These are confirmation criteria, not the clinical susceptible breakpoints for the drugs.

Watch the brief measurement explanation in “Extended-spectrum beta-lactamase (ESBL) test” by Amer Al-Jawabreh. Use it to reinforce which disk diameters are paired; rely on the adopted, current standard for the full procedure and quality-control requirements.

Now examine the supplied two-panel disk-diffusion image. Its printed diameters let us interpret the result without guessing from the appearance of the zones.

In panel A, cefotaxime increases from 21 to 27 mm, a 6 mm gain; ceftazidime increases from 13 to 25 mm, a 12 mm gain. Either pair meets the conventional positive criterion, so this is a positive phenotypic ESBL confirmation result, provided the isolate, test conditions, and controls are valid.

In panel B, ceftazidime changes from 30 to 28 mm and cefotaxime from 34 to 35 mm. Neither pair gains 5 mm: ESBL production is not demonstrated by this test. That wording is more defensible than “this organism has no ESBL.” A negative clavulanate test has limitations, especially when another β-lactamase masks the synergy.

Before acting on either panel, check the matters that made earlier automated results trustworthy: pure culture and correct identification, standardized inoculum, valid disks and medium, appropriate incubation and zone measurement, and acceptable quality controls. An automated “ESBL” alert is likewise a prompt to review the organism, panel method, and evidence—not, by itself, proof of a particular enzyme.

When phenotype and gene detection disagree

Clavulanate synergy is strong evidence for a phenotype, but it does not identify a gene. Conversely, PCR or another molecular assay detects the genes included in its target set; it does not directly measure cephalosporin hydrolysis, enzyme expression, or an MIC. A positive result for a well-characterized ESBL gene such as a covered blaCTX-M target supplies gene-level evidence. A negative blaCTX-M-only result cannot exclude an ESBL encoded by an uncovered gene or variant. Distinguishing an ESBL-producing TEM or SHV variant from a narrower-spectrum one may require variant-specific analysis rather than a generic family-level result.

Read the review’s rapid-test and molecular-test discussion with these different meanings of “positive” in mind.

A clavulanate-negative, blaCTX-M-positive finding calls for review, not immediate rejection of one result. Confirm that the molecular result belongs to the same pure isolate; check phenotypic QC, identification, and whether AmpC or another mechanism could mask synergy. If the gene was detected directly in a positive blood culture containing more than one organism, do not automatically assign it to a subsequently isolated species without supporting evidence.

The opposite discordance—clavulanate-positive, targeted-gene-negative—may simply mean that the gene panel missed the responsible ESBL family or variant. It may also reflect a misleading phenotypic result, including interactions among β-lactamases and permeability changes. Recheck purity and assay coverage, then choose an appropriate repeat, alternative phenotypic method, or broader molecular characterization according to the consequence of the result. Neither “PCR negative” nor “automated ESBL positive” settles every mechanism question.

Detection is not a reporting override

Historically, laboratories using older cephalosporin breakpoints could use ESBL confirmation to alter how a range of β-lactams was reported. Do not carry that historical blanket conversion forward as a default rule. With adopted current organism–drug breakpoints, report the verified MICs or zones and their interpretations under the applicable CLSI or EUCAST standard and its version. An ESBL-positive result does not, by itself, change every tested susceptible cephalosporin or aztreonam result to “resistant.”

That does not make mechanism detection irrelevant. It may serve infection-control or epidemiological purposes and, in some settings, inform therapeutic discussion. This is a matter to agree locally with the antimicrobial stewardship team: decide which isolates to confirm, which method to use, whether and how to communicate a confirmed mechanism, and how to handle clinically consequential susceptible results. An in-vitro susceptibility category is not, on its own, a recommendation to use that drug for every infection.

For the reporting nuance, read the focused section “Testing and reporting recommendations for multidrug-resistant gram-negative bacilli” in Overview of changes in the Clinical and Laboratory Standards Institute Performance Standards for Antimicrobial Susceptibility Testing: M100 32nd and 33rd editions. It explains the shift after breakpoint revision and why a later CLSI comment renewed discussion of ESBL testing. Because this article discusses particular editions, treat it as an explanation of the policy change, not a substitute for checking the current edition used by your laboratory.

Here is a concise way to present a consequential result to classmates: a pure E. coli isolate has a valid 6 mm cefotaxime–clavulanate zone gain and a separately verified cephalosporin MIC. The gain supports phenotypic ESBL production. The MIC receives its own category under the laboratory’s current, documented breakpoints. A mechanism comment or prompt discussion with the clinical team may be appropriate under local policy; neither the comment nor the enzyme finding licenses silently changing the measured AST category. If the ESBL test and an automated result disagree, investigate before releasing a mechanistic claim.

Takeaways

ESBL confirmation, gene detection, and susceptibility reporting answer three different questions. Clavulanate-associated restoration of cefotaxime or ceftazidime activity supports a classical ESBL phenotype; a covered molecular target identifies a gene, subject to target and variant limits; an MIC or zone interpreted with current organism–drug criteria supplies the clinical AST category. Keep those findings distinct, verify discordances, and document the standard and local reporting policy you apply.

The next lesson considers colistin, where the difficulty shifts from confirming an enzyme to deciding whether the AST method itself gives a reliable result.