Learning from Disagreement: Clinician Overrides as Implicit Preference Signals for Clinical AI in Value-Based Care
This paper proposes a formal framework that reframes clinician overrides of AI recommendations as implicit preference signals, introducing a dual-learning architecture and override taxonomy to train reward models aligned with patient outcomes in value-based care while mitigating suppression bias caused by varying clinician capabilities.
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 trying to teach a robot chef how to cook the perfect meal. In the past, if the robot suggested adding salt and the chef said, "No, that's too much," the robot would think, "Oh, I must be wrong. I'll stop suggesting salt."
This paper argues that this is the wrong way to learn. Instead of seeing the chef's "No" as a mistake, we should see it as a secret message about why they said no.
Here is the simple breakdown of the paper's ideas:
1. The "No" is Actually a Treasure Map
In hospitals, doctors often ignore or change what computer systems suggest. Usually, tech companies think this is a failure—a sign the computer is annoying or wrong.
This paper says: Stop treating it as a failure. Treat it as a rich data signal.
- The Old Way: "The doctor rejected the AI's advice. The AI is bad."
- The New Way: "The doctor rejected the advice. Why? Was the advice actually wrong? Or did the doctor just not feel confident enough to do it? Or was the hospital's rules different?"
Every time a doctor changes a recommendation, they are giving the AI a labeled lesson: "In this specific situation, with this specific doctor, I prefer this action over that one."
2. The Three Types of Chefs (The "Capability" Problem)
The paper uses a story about three different doctors (or chefs) to explain why we can't just count "Yes" and "No" votes equally. Imagine a recommendation to start a new heart medication:
- Chef A (The Master): Knows the recipe perfectly. Checks the ingredients, sees it's safe, and says, "Yes, let's do it." This is a reliable "Yes."
- Chef B (The Apprentice): Knows the recipe is good but has never cooked it alone. They are scared they'll mess it up, so they say, "No, let's call the head chef (a specialist) instead." This is a rejection, but it's not because the recipe is bad. It's because the chef lacks the skill to execute it.
- Chef C (The Robot): Says "Yes" to everything without thinking. This looks like agreement, but it's actually empty data.
The Trap: If you just count the votes, you see 2 "Yes" and 1 "No." You might think the recipe is great. But if you look closer, the "No" came from a chef who was scared, and the "Yes" from the robot was meaningless. If you don't separate these, the AI might learn to stop suggesting the recipe entirely because "too many people said no," even though the recipe is actually perfect.
The paper calls this "Suppression Bias." It's when the AI stops suggesting good, difficult things because the people who aren't skilled enough to do them keep saying "No."
3. The Two-Brain Solution
To fix this, the paper suggests the AI needs to learn with two brains at the same time, not just one:
- Brain 1 (The Reward Model): Learns what the best medical action is.
- Brain 2 (The Capability Model): Learns how skilled each specific doctor is at doing that action.
The AI runs a loop:
- "Did Dr. Smith say no? Is it because the idea was bad (Brain 1), or because Dr. Smith isn't ready to do it yet (Brain 2)?"
- If it's a skill issue, the AI doesn't change its mind about the recipe; instead, it gives Dr. Smith a cheat sheet (a checklist or a step-by-step guide) to help them feel confident.
- As Dr. Smith gets better, the AI stops giving them the cheat sheet and treats them like a Master Chef.
4. Why This Only Works in "Value-Based" Care
The paper argues this system works best in a specific type of hospital payment model called Value-Based Care.
- The Old Way (Fee-for-Service): Doctors get paid for every visit. If they refer a patient to a specialist, they get paid more. So, they might refer patients even when they could treat them themselves. The AI learns the wrong lessons here.
- The New Way (Value-Based): Doctors get paid based on results (e.g., "Did the patient get better in 3 months?").
- In this world, if a doctor refers a patient unnecessarily, the patient might get worse or wait too long, and the hospital loses money.
- This creates a clear "scorecard." The AI can look back 30 or 90 days later and see: "The doctor who said 'No' and referred the patient had a bad outcome. The doctor who said 'Yes' and treated them had a great outcome."
Because the results are visible and tied to the money, the AI can finally learn the truth: "Okay, the 'No' from the scared doctor was a mistake. The 'Yes' was the right move."
5. The "Flywheel" Effect
The paper describes a magical cycle that happens when you do this right:
- The AI suggests a treatment.
- Doctors give feedback (overrides).
- The AI learns who is skilled and who needs help, and it adjusts its suggestions.
- Doctors get better at doing the treatments because the AI helps them.
- Because doctors are better, they say "Yes" more often, and the AI learns even faster.
It's like a snowball rolling down a hill: the more you use the system, the smarter it gets, and the better the doctors become.
Summary
This paper says: Don't ignore the "No."
When a doctor changes an AI's mind, it's not a system failure. It's a complex conversation between the AI, the doctor's skill level, and the hospital's rules. If we build AI that understands why the doctor said "No" (is it a skill gap? a rule change? or a real medical disagreement?), we can create systems that don't just give advice, but actually help doctors get better at their jobs.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.