Ylenia Rotalinti, Johan Ordish, Xiaoxuan Liu, Ben Glocker, Alastair Denniston, Peter Wright, Christopher Yau, Aditya Kale, David Grainger, Richard Branson
5 min
Artificial Intelligence as a Medical Device (AIaMD) must maintain performance throughout its entire lifecycle. However, healthcare environments are dynamic, and the data used to train these models often change over time—a phenomenon known as 'drift.' This paper, developed by an expert working group at the UK Medicines and Healthcare products Regulatory Agency (MHRA), addresses the urgent need for a unified framework to identify, assess, and manage these changes to ensure patient safety.
The authors classify drift into three distinct statistical subtypes, each with unique clinical implications:
Identifying drift is not merely a technical challenge; it is a regulatory and ethical necessity. The authors argue that drift should be treated as an expected aspect of the total product lifecycle (TPLC). By analyzing the velocity and magnitude of drift, manufacturers and regulators can move beyond simple performance metrics to implement proportionate responses, such as model recalibration or retraining. This approach supports the development of Predetermined Change Control Plans (PCCPs), which allow for transparent and safe model updates in response to real-world data shifts.
Alex: That last one seems like the most important. A small drop in accuracy means something very different depending on what the AI is being used for.
Sam: Precisely. The paper uses the analogy of dashboard warning lights. A small drop might be like an engine running slightly warm — worth monitoring, but not a reason to stop. But if the model's errors start affecting patient safety, or if they fall disproportionately on a particular group of patients, that's the gauge hitting the red zone. You pull over.
Alex: So the response is meant to be proportionate, not just automatic.
Sam: Right. And that's where the regulatory framework comes in. The authors want this kind of monitoring built into what they call a "Total Product Lifecycle" approach. The idea is that you don't just test an AI tool before it launches and then leave it alone. You plan for change from the very beginning, using something they call a "Predetermined Change Control Plan." That's essentially a written agreement, made in advance, about what kinds of changes are expected, how they'll be detected, and what the response will be.
Alex: It turns what could be a chaotic, reactive situation into something more like a maintenance schedule.
Sam: That's a good way to put it. And it matters for trust as well. If hospitals and regulators know that a manufacturer has a clear, transparent plan for handling drift, they can have more confidence in the tool — even knowing that it will change over time.
Alex: So the paper is really making the case for a different way of thinking about medical AI altogether. Not a static product you approve once, but something more like a living system that needs ongoing oversight.
Sam: That's the core of it. And the authors are candid that this is still developing. The field doesn't yet have universal standards for what counts as an acceptable threshold, or how frequently monitoring should happen. But by naming the problem clearly — by giving regulators and manufacturers a shared vocabulary for talking about drift — the paper argues we're in a much better position to build that governance over time.
Alex: A shared vocabulary sounds like a modest starting point, but it's probably the necessary one.
Sam: It often is. You can't manage what you can't describe. And in a field where the stakes are patient safety, getting the description right is genuinely important work.
Alex: Thanks for listening to ResearchPod.