Validating healthcare AI

Transportability: Will a Prediction Model Work in a Population It Never Saw?

Transportability is the question of whether a prediction model that performed well where it was built will still perform where it is used, on people it never saw in training. You do not know until you check, and the check costs less than the failure.

Transportability is the question of whether a prediction model that performed well where it was built will still perform where it is used, on people it never saw in training. You do not know until you check, and the check costs less than the failure. A model can rank patients correctly in a new hospital yet quote risks that are systematically too high or too low, the most common and most fixable way it breaks. You usually have three repair options short of starting over: recalibrate, update, or refit. (This piece is educational, not medical advice; decisions about your own care belong with your own clinician.)

I have both borrowed models and built one. With EASY Diabetes, the decision-support system I co-developed and put through EASY-1, a registered randomized controlled trial (NCT03258268), the recurring lesson was that a model behaves like a local instrument. Move it to a place with a different patient mix and different documentation habits, and it can read wrong for reasons that have nothing to do with flawed math.

Why does a good model misbehave somewhere new?

Two distinct shifts do most of the damage, and they call for different responses, so it helps to name them separately.

The first is case-mix shift. The new population differs in the distribution of the very predictors the model uses. A model trained at a specialist referral center, where many patients are already sick, meets a community clinic where most are not. The relationships it learned may still hold, but the crowd it scores is composed differently, so the average risk it should output has moved. Discrimination often survives, because ranking sicker above healthier is robust. Calibration slips, because the model keeps pricing risk against the old baseline rate.

The second is spectrum shift, sometimes called the spectrum effect. Here the makeup of who has the condition changes, and the count is only part of it. A model that separates advanced disease from clear health looks impressive, but move it to a setting full of early, ambiguous cases and its apparent accuracy falls, because the easy contrasts are gone and the predictor-outcome relationships themselves can bend. Some of my own research examined how the link between insulin sensitivity and insulin response differs across populations. The takeaway is plain: a relationship measured in one group is not a safe default for another, because the underlying biology is not identical.

A third, quieter shift lives in the data pipeline. A variable measured carefully at the training site may be sparsely recorded at the new one, coded under a different definition, or drawn from a different instrument, so the model sees the same field name and a different thing behind it. That failure has nothing to do with patients and everything to do with plumbing; it is easy to miss because the code still runs.

How do you tell which shift you are facing?

You measure, on the new population, the two properties that fail independently. Discrimination, whether the model still orders patients correctly, is captured by the C-statistic. Calibration, whether the reported risks match the rates that actually occur, is best read from a calibration plot rather than a single number.

The pattern is diagnostic. If discrimination holds but the calibration plot is tilted or shifted, you are likely facing case-mix shift, and a light repair should suffice. If discrimination itself has dropped, the predictor-outcome relationships have changed, which points to spectrum shift or a genuine difference in mechanism, and a light repair will not be enough. If an input has gone missing or changed meaning, fix that data problem before judging the model at all.

Evidence should scale with distance. When the new population closely resembles the development one, transfer is a reasonable starting assumption. When it sits well outside the studied range, the model has to earn trust before use.

Recalibrate, update, or refit?

Once you know the shift, the menu is short.

Recalibration is the lightest touch. You keep the model's predictors and their relative weights and adjust only the overall level, and sometimes the spread, so reported risks match observed rates. Correcting the intercept fixes a model that is uniformly too high or too low, the classic signature of case-mix shift, while adjusting the slope handles risks that are too extreme or too timid. It is cheap, needs little outcome data, and preserves what the original model learned. Its limit is that it cannot repair relationships that have actually changed; it only re-levels the ones you have.

Model updating goes a step further. You keep the structure but revise it against local data, re-estimating some coefficients, adding a predictor that matters locally, or letting a variable's effect change where the evidence supports it. This recovers more performance than recalibration when a few relationships have genuinely shifted, while still borrowing the original model's strength. The cost is more local data and more care, because every parameter you free up is one you can overfit.

Refitting, or building anew, is the heavy option. You use the new population's data to estimate the model from the ground up, sometimes keeping only the choice of predictors. It is warranted when discrimination has collapsed, when case mix and spectrum are both far from the original, or when the outcome definition differs. It buys the best local fit at the highest cost, and risks trading a well-validated borrowed model for a locally overfit one that has never been tested anywhere else.

The through line is to spend the least intervention that fixes the observed failure. Rebuilding a model whose only problem was a shifted baseline throws away hard-won stability for nothing.

When to trust a borrowed model, and when to rebuild

Trust a borrowed model when the population resembles the one it learned from, the inputs mean the same thing in your data, and a check on your own patients shows discrimination and calibration both holding. Reach for recalibration or updating when discrimination survives but the numbers are off, the common case that rarely justifies starting over. Rebuild when the relationships have changed, when the spectrum of disease is genuinely different, or when you cannot reliably supply the inputs at the moment of decision.

A model that fails to transport has not failed as science; it answered a question about one population and was asked about another. The work is to measure the distance and match the repair to it. A prediction is only as portable as the resemblance between where it was learned and where it is used, and you can test that resemblance before anyone's care depends on it.

References and sources

  1. Debray framework for external validation (reproducibility vs transportability, case-mix)
  2. Van Calster et al. Calibration the Achilles heel of predictive analytics (BMC Medicine 2019)
  3. Riley et al. Evaluation of clinical prediction models part 2 external validation (BMJ 2024)
  4. Methodological guidance for evaluation and updating of clinical prediction models (BMC Med Res Methodol 2022)

How this was researched. This explainer is built from the primary sources listed above and reflects Dr. Tojjar's own critical appraisal of that evidence. It explains and evaluates research and does not provide medical care.

This article is for general education and is not medical or professional advice. For guidance about your own health, talk with a qualified clinician.

Cite this article

Tojjar, D. (2024). Transportability: Will a Prediction Model Work in a Population It Never Saw. Dr. Damon Tojjar. https://readingtheevidence.org/articles/transportability-of-prediction-models/

Back to all insights