← Latest papers
📊 statistics

Selection and Collider Restriction Bias Due to Predictor Availability in Prognostic Models

This methodological note investigates and discusses how predictor availability in prognostic models can introduce selection and collider restriction bias.

Original authors: Marc Delord

Published 2026-02-20
📖 5 min read🧠 Deep dive

Original authors: Marc Delord

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a doctor trying to build a "crystal ball" to predict which patients are most likely to get sick in the future. You want to create a score that looks at a patient's age, blood pressure, and kidney function to tell you: "This person has a 20% chance of needing a kidney transplant in five years."

This paper argues that many of these "crystal balls" are actually cracked, not because the math is wrong, but because of who gets to look into the ball in the first place.

Here is the story of the problem, explained with a few simple analogies.

1. The "Missing Ingredient" Problem

To build your crystal ball, you need specific ingredients (data points). Let's say you need to know a patient's Kidney Function and their Urine Protein Levels.

In the real world, doctors don't test everyone for everything. They usually only test the urine protein if the kidney function looks suspicious or if the patient seems very sick.

  • The Flaw: If you build your prediction model using only the patients who already had their urine tested, you are only looking at the "sick" people. You are ignoring the "healthy" people who never got tested because they seemed fine.
  • The Result: Your model thinks the disease is much more common or severe than it actually is, because it's only looking at the tip of the iceberg.

2. The "Gatekeeper" Analogy

Imagine a nightclub (the hospital) where you want to predict who will get into a fight (the bad health outcome).

  • The Predictor: You want to use "How loud they are shouting" as a clue.
  • The Gatekeeper: The bouncer only lets people into the VIP room (where you can measure the shouting) if they look like they are already getting agitated.

If you only study the people in the VIP room to see who fights, you will conclude that everyone in the club is about to fight. Why? Because the bouncer (the medical system) filtered out all the calm people. You created a biased sample by only looking at the people the gatekeeper let in.

In medicine, the "gatekeeper" is the rule that says, "We only test for this specific marker if the patient looks sick."

3. The "Double-Edged Sword" (Collider Bias)

The paper introduces a tricky concept called Collider Restriction Bias. This is the most important part.

Imagine a traffic intersection where two roads meet.

  • Road A: The patient's actual kidney health (getting worse).
  • Road B: The doctor's gut feeling that the patient is at risk (due to other symptoms like diabetes).

Both Road A and Road B lead to the same stop sign: "Order the Urine Test."

The Urine Test is the "Collider." It is the point where two different causes meet.

  • If you only study people who have the urine test results, you are effectively standing at that intersection and only counting the cars that stopped there.
  • The Magic Trick: By forcing yourself to only look at people who stopped at the intersection, you accidentally create a fake connection between Road A and Road B. You might start thinking that "Loud Shouting" (Road A) causes "Fighting" (Road B), when in reality, they are just both reasons to stop at the bouncer's booth.

In the paper's example (the Kidney Failure Risk Equation), this happens because:

  1. Kidneys get worse \rightarrow Doctor orders a test.
  2. Patient looks very sick \rightarrow Doctor orders a test.

If you build a model using only the people who got the test, you distort the relationship between the symptoms and the outcome. You might think a specific symptom is a stronger warning sign than it really is, or you might miss the fact that the model doesn't work for healthy people who never got tested.

4. The Real-World Example: The Kidney Equation

The authors use a real tool called the KFRE (Kidney Failure Risk Equation). It's supposed to predict kidney failure.

  • The Problem: In the UK and US, doctors often forget to test the urine protein for patients with mild kidney issues. They only test the "sick" ones.
  • The Consequence: The model was built on data from the "sick" group. When doctors try to use it on a regular patient in a clinic, the model might say, "This person has a 50% risk!" when they actually have a 5% risk. The model is over-predicting danger because it was trained on a group of people who were already selected for being sick.

The Big Takeaway

The paper is a warning to scientists and doctors:

"Just because you have the data, doesn't mean you have the whole picture."

When building medical prediction tools, we often assume that the data we have (like blood tests) is available for everyone. But in reality, we only have data for the people the system decided to test. If we don't account for why those tests were ordered, our "crystal balls" will be broken, leading to wrong predictions and bad medical decisions.

The Solution?
We need to be smarter about how we design these models. We should either:

  1. Make sure we test everyone (not just the sick ones) to get a fair sample.
  2. Build simpler models that use data we know is available for everyone (like age and basic blood pressure), rather than complex tests that only the "sick" get.

In short: Don't let the way we choose our patients trick us into thinking we understand the whole story.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →