EUCAST v16 in clinical microbiology: what changed in January 2026 and why your AST analyzer is six months behind

EUCAST published version 16.0 of the clinical breakpoint tables in the first week of January 2026, with the explanatory webinar held January 20. By mid-spring, most clinical microbiology labs in Europe and a growing number outside it are actively reconciling their susceptibility-testing systems with the new tables. The work is not glamorous and it is not optional. The window between v16's publication and the day a vendor pushes a corresponding firmware update to your bench analyzer is somewhere between six and twelve months. During that window, the lab is responsible for the gap.

This piece walks through what actually changed in v16, what is still in consultation rather than finalized, and what a working lab should be doing right now to keep clinical reporting aligned with current breakpoints while the analyzer vendors catch up.

What v16 actually changes

Gepotidacin: new breakpoints, new pathogen list

The headline addition in v16 is new clinical breakpoints for gepotidacin against three pathogens relevant to uncomplicated urinary tract infection: Escherichia coli, Staphylococcus saprophyticus, and Enterococcus faecalis. Gepotidacin is a triazaacenaphthylene antibiotic — a novel class — approved for oral treatment of uncomplicated UTI. The introduction of breakpoints means clinical labs can now formally report S/I/R interpretations for gepotidacin where it is on the local formulary.

For most labs the practical implication is small in the short term, because the antibiotic is not yet on most antibiograms. But the rule of thumb for new agents holds: the breakpoint table changes before the vendor panels do. If your microbiology software cannot accept a custom breakpoint while the analyzer firmware is still on v15, you will be either ignoring gepotidacin or reporting it without an interpretation footer. Neither is acceptable.

Trimethoprim and trimethoprim-sulfamethoxazole: revised across multiple species

v16 revises trimethoprim and TMP-SMX (co-trimoxazole) breakpoints for several species. The revisions narrow the susceptible range for Enterobacterales and adjust the resistant cutoff. For labs with high TMP-SMX prescribing — typical of outpatient UTI workflows and respiratory infections — a revised breakpoint can move 5-15% of isolates between susceptible and intermediate, depending on local epidemiology.

The clinical-impact question is straightforward. A patient previously reported susceptible at MIC 4 with the v15 breakpoint may now be intermediate at the v16 breakpoint. The treatment recommendation changes. The antibiogram aggregate for the year changes. Antimicrobial stewardship decisions made on last quarter's data become harder to compare with this quarter's.

For labs that aggregate annual antibiogram data across the breakpoint transition, the clean approach is to recompute the prior year using the v16 breakpoint, document the methodology, and present both interpretations side-by-side until a full year of v16 data is available. This is the work that actually matters for stewardship — and the work most labs skip because their LIMS cannot reinterpret historical results against a new breakpoint table.

Carbapenems and ceftazidime-avibactam: still in consultation, not finalized

Worth noting precisely: the carbapenem revisions and ceftazidime-avibactam revisions for Gram-negative bacteria that were widely discussed in 2025 are still in public consultation as of v16 publication. The consultation window for those specific changes closed December 14, 2025 but the revised tables had not yet been formally published when v16 went live in January. They are expected in a v16.x dot release later in 2026.

The implication for labs: do not implement "v16 carbapenem changes" yet, because v16 itself does not contain them. Wait for the dot release or the explicit publication. Some commercial commentary in late 2025 conflated "EUCAST is reviewing carbapenems" with "v16 changes carbapenems." Those are not the same statement.

Quality control ranges and methods documents

v16 also revises QC ranges for several agent-organism combinations and updates the methods documents for disk diffusion, gradient strip MIC, and broth microdilution. Labs running EUCAST methodology should pull both the breakpoint tables and the methods documents — they update together and the methods document is where the practical instructions live. Running v16 breakpoints on v15 disk diffusion methodology is a documentation problem waiting to be found by the next ISO 15189 inspector.

Why the analyzer vendor lag matters

Clinical labs running automated AST systems — VITEK, Phoenix, MicroScan, Sensititre — depend on the vendor to push breakpoint updates as part of firmware or panel-card updates. The vendor cycle has historically run six to twelve months behind EUCAST publication. There are valid reasons (regulatory clearance for the panel update in the relevant markets, internal validation, manufacturing lead time on physical panel cards), but the consequence falls on the lab.

During the lag, the analyzer reports its interpretation against an outdated breakpoint table. The lab has three operational choices:

• Accept the analyzer's outdated interpretation and note the version mismatch in the report comment. Defensible only if the deviations are documented and clinical care is not affected. Hard to maintain across a high-volume bench.
• Manually re-interpret affected isolates against the v16 breakpoint and append a corrected interpretation. Practical for low-volume but breaks down at scale and creates two records of truth on the same isolate.
• Run a parallel interpretation layer in the LIMSthat takes the raw MIC from the analyzer and applies the current EUCAST breakpoint table independently of the analyzer's onboard rules. The analyzer stays in service, the report uses current breakpoints, and the audit trail is single-source.

The third option requires a LIMS that holds breakpoint tables as data, not as code. Most legacy LIMS hardcode interpretations and require a vendor patch for any breakpoint change. Modern LIMS — including our microbiology module — store EUCAST and CLSI breakpoint tables as versioned reference data, so the lab updates the table in software and the interpretation logic follows automatically. The analyzer firmware can lag without the report lagging.

The antibiogram problem

Aggregate antibiograms — the cumulative susceptibility report a lab produces annually for the antimicrobial stewardship team — sit on top of months of accumulated isolate data. A breakpoint change mid-year creates an interpretation discontinuity. Isolates from January 2026 onward may use v16 breakpoints; isolates from December 2025 used v15.

Three positions on this, all defensible:

1. Cut over on a hard date. Everything from the cutover uses v16. The annual antibiogram for 2026 mixes v15 (Jan-Mar maybe) and v16 (Apr-Dec). Document the cutover date and which breakpoints were active in which window.
2. Retroactively recalculate. Reinterpret all 2026 isolates against v16. Cleaner antibiogram. Requires the LIMS to hold raw MICs and reinterpret on demand.
3. Run parallel for a quarter. Issue clinical reports under v16 from cutover, but produce two antibiograms internally for stewardship — one v15-based, one v16-based — and present the differences. Heaviest workload, best decision quality.

Whatever the lab chooses, the choice should be documented and signed off by the laboratory director and the antimicrobial stewardship physician lead. An antibiogram that does not state which breakpoint version it uses is not a usable antibiogram.

What v16 does not change — and what often gets confused

EUCAST v16 is not a CLSI update. CLSI M100 issues its own annual revision (currently M100 35th edition) with overlapping but distinct breakpoints. Labs running CLSI methodology — common in the US — are not affected by EUCAST v16 and should not implement v16 breakpoints if the lab's reporting standard is CLSI. A lab running both methodologies for different reporting purposes (e.g., research vs clinical) needs to keep them clearly separated.

v16 is also not a methodology change for routine disk diffusion. The disk diameters, incubation conditions, and reading instructions are largely unchanged. The methods document was updated, but most of the change is editorial clarification rather than procedural revision. Operators do not need retraining on the bench technique — but the supervising microbiologist should walk the new methods document to catch the small clarifications that do appear.

The short checklist

1. Download v16.0 breakpoint tables and methods documents from eucast.org.
2. Identify the gepotidacin pathogens on your local formulary; configure breakpoints if relevant, otherwise document non-applicability.
3. Pull the TMP-SMX revision diff against v15 for the species your lab reports. Estimate the reclassification rate using last quarter's isolate data.
4. Confirm with your AST analyzer vendor when the v16 firmware update is scheduled. Ask for the ETA in writing.
5. Decide on the cutover plan for clinical reporting — analyzer-only, manual override, or LIMS interpretation layer.
6. Decide on the antibiogram approach — hard cutover, retroactive recalculation, or parallel run.
7. Document both decisions, get them signed by the lab director and stewardship lead, file under method validation.
8. Do not implement the carbapenem or ceftazidime-avibactam changes that were in consultation — they are not in v16.0.

Labs that handle this transition cleanly tend to share a common property: their LIMS treats breakpoints as versioned reference data rather than as built-in interpretation rules. That single architectural choice converts the EUCAST update from a vendor-firmware problem into a configuration problem. It costs nothing to discuss with a vendor when evaluating LIMS options. It costs months to retrofit when an update lands and the analyzer is six to twelve months behind.