Principal Agent
Readmission Hot Potato
Readmission Hot Potato is a Principal Agent scenario. The core lesson: When a hospital discharges patients to a post-acute facility, both parties have different information and different incentives. The gap between them often lands back in the ED 30 days later. A hospital case management team is under pressure to reduce average length of stay and avoid penalty-triggering readmissions. A skilled nursing facility in the same network has a preferred partner agreement that includes a 30-day readmission guarantee. DecisionPlay maps the players, payoffs, and equilibrium dynamics that shape how this situation typically resolves.
The situation
A hospital case management team is under pressure to reduce average length of stay and avoid penalty-triggering readmissions. A skilled nursing facility in the same network has a preferred partner agreement that includes a 30-day readmission guarantee. Over the past quarter, the SNF's admissions coordinator has declined several patients citing staffing constraints, while the hospital has discharged others before the SNF's formal acceptance was in writing. Two patients readmitted within 30 days came through this arrangement. Finance is asking who is responsible.
Background
The relationship between a hospital discharge team and a post-acute partner is a principal-agent problem. The hospital is the principal: it wants length of stay reduced and readmission penalties avoided. The SNF is the agent: it wants to admit only patients it can safely manage given its own staffing and capabilities. The SNF has private information the hospital cannot observe in real time, namely, its actual bed capacity, staff acuity competency, and coverage for the next 48 hours. Each party optimizes on its own target. The patient experiences the gap between them.
What this reveals
Why care transitions produce preventable readmissions
Principal-agent problems in care transitions arise because the principal and agent have different information and different incentives. The hospital wants the bed; the SNF wants a patient it can manage. When discharge happens before the SNF has verified it can actually accept the patient, both parties are optimizing on their own targets and the patient moves through the gap between them. Fixing the process means fixing the information exchange, not just assigning blame after the readmission.
How to counter it: Require written SNF acceptance before any transfer order is placed, not after. The audit trail also protects both parties: if the hospital has a signed acceptance and the patient readmits, the guarantee triggers cleanly.
A question to sit with
In your care transition processes, at what point is patient acceptance by a post-acute partner confirmed in writing, and when does the discharge order actually go in?
Frequently asked questions
- What game theory concept does Readmission Hot Potato illustrate?
- Readmission Hot Potato illustrates Principal Agent. When a hospital discharges patients to a post-acute facility, both parties have different information and different incentives. The gap between them often lands back in the ED 30 days later.
- What is the situation in Readmission Hot Potato?
- A hospital case management team is under pressure to reduce average length of stay and avoid penalty-triggering readmissions. A skilled nursing facility in the same network has a preferred partner agreement that includes a 30-day readmission guarantee. Over the past quarter, the SNF's admissions coordinator has declined several patients citing staffing constraints, while the hospital has discharged others before the SNF's formal acceptance was in writing.
- What does Readmission Hot Potato reveal about how people decide?
- Why care transitions produce preventable readmissions. Principal-agent problems in care transitions arise because the principal and agent have different information and different incentives. The hospital wants the bed; the SNF wants a patient it can manage. When discharge happens before the SNF has verified it can actually accept the patient, both parties are optimizing on their own targets and the patient moves through the gap between them. Fixing the process means fixing the information exchange, not just assigning blame after the readmission.
- How do you avoid the trap in Readmission Hot Potato?
- Require written SNF acceptance before any transfer order is placed, not after. The audit trail also protects both parties: if the hospital has a signed acceptance and the patient readmits, the guarantee triggers cleanly.
- What is the research behind Readmission Hot Potato?
- The relationship between a hospital discharge team and a post-acute partner is a principal-agent problem. The hospital is the principal: it wants length of stay reduced and readmission penalties avoided. The SNF is the agent: it wants to admit only patients it can safely manage given its own staffing and capabilities.
- How long does Readmission Hot Potato take to play?
- About 8 min, at core difficulty, across 1 decision points. It runs in your browser with no account and no sign-in.
Keep exploring
More Healthcare Ops scenarios, or browse all scenarios. New to this? Start with how DecisionPlay works or the game theory glossary.
Topics: care-transitions, readmissions, post-acute, case-management