Digital PathologySolutions
Blog

Foundation models for histology: what actually transferred, and what did not

Twelve months after adopting a foundation-model backbone across our indication heads, here is an honest technical account of what we gained and what it cost us.

Marek KowalskiCTO & Co-Founder
11 min read
Darkened GPU server aisle with subtle purple indicators

A year ago we migrated every indication head in the platform off bespoke CNN backbones and onto a shared foundation-model encoder pretrained on roughly 180 million tiles drawn from public and partner-contributed cohorts. The headline improvement on internal benchmarks was real. The migration itself was harder than we expected, and the engineering cost is worth writing about in detail.

What transferred cleanly

Representation quality transferred. Tasks that previously required 50,000 annotated tiles per indication now reach equivalent performance on roughly a tenth of that. More importantly, the representations are stable across scanners in a way that end-to-end CNN backbones never quite achieved for us.

What did not

Calibration did not transfer. The foundation backbone produces well-separated features but its downstream classifiers tend to be overconfident on out-of-distribution tiles. We addressed this with a per-indication temperature calibration step run against a held-out multi-site calibration cohort, which is now part of our release pipeline.

Memory footprint also did not transfer quietly. The foundation encoder is roughly four times the size of the CNN backbones it replaced. On our standard inference node that meant rewriting the batching layer to use feature caching and scheduling.

Where we landed

On balance the migration paid for itself within six months, but not through raw accuracy. The real return was development velocity: shipping a new indication head is now a two-to-four week exercise for a small team, rather than a three-to-six month one. That is the number that matters to our partners.

Share this post

Written by

Marek Kowalski

CTO & Co-Founder

You may also like.

Stay in the loop.

Subscribe or reach out and we’ll get back to you within one business day.

Digital Pathology Solutions is committed to protecting your privacy. We use your personal data solely for managing your inquiry and providing the information you requested.

Learn more in our Privacy Policy.

By clicking "Submit", you consent to Digital Pathology Solutions storing and processing the personal data you have provided above in order to deliver the requested content to you.

I'm not a robot
reCAPTCHA