Repeated Game
Surge Capacity Mutual Aid
Surge Capacity Mutual Aid is a Repeated Game scenario. The core lesson: Mutual aid coalitions are sustained by repeated interaction, not just signed agreements. When some hospitals quietly decline requests they are obligated to honor, the pattern only becomes visible across multiple rounds. Five hospitals in a regional coalition have a mutual aid agreement requiring each to accept diverted patients when a member declares a surge event. Over the past 18 months, two hospitals have declared surge events and received patient transfers from partners. DecisionPlay maps the players, payoffs, and equilibrium dynamics that shape how this situation typically resolves.
The situation
Five hospitals in a regional coalition have a mutual aid agreement requiring each to accept diverted patients when a member declares a surge event. Over the past 18 months, two hospitals have declared surge events and received patient transfers from partners. Three hospitals have never declared a surge event and have declined several informal transfer requests, each time citing a specific operational constraint. The coalition coordinator's annual report shows the pattern clearly: two hospitals give, three decline. The board is meeting to discuss whether to enforce the agreement.
Background
Mutual aid agreements in healthcare are sustained by repeated interaction. Each hospital faces a choice in each surge event: honor the agreement or cite a local constraint and decline. In a one-shot game, declining is individually rational. In a repeated game, defection in one period creates a reputation effect that erodes trust and invites reciprocal defection in future rounds. The coalition's value depends on each member believing the others will reciprocate. When some members repeatedly decline, the hospitals that have honored requests begin to question whether the agreement is real.
What this reveals
Why mutual aid agreements erode quietly
Mutual aid coalitions fail through accumulated defection, not through dramatic exits. Each hospital that declines a request has a locally defensible reason. The pattern only becomes a crisis at the annual report level, when the cumulative record shows who has borne the obligation and who has not. Repeated games have a built-in corrective: making the history visible to all players. What defectors fear most is a public record, not an abstract penalty.
How to counter it: Ask your coalition coordinator to share acceptance and decline histories across all members on a quarterly basis, not just annually. The corrective effect of visibility is strongest when the record is recent and specific.
A question to sit with
What shared obligation in your network or coalition is currently tracked only at the annual level, where the pattern of compliance would look very different if reviewed quarterly?
Frequently asked questions
- What game theory concept does Surge Capacity Mutual Aid illustrate?
- Surge Capacity Mutual Aid illustrates Repeated Game. Mutual aid coalitions are sustained by repeated interaction, not just signed agreements. When some hospitals quietly decline requests they are obligated to honor, the pattern only becomes visible across multiple rounds.
- What is the situation in Surge Capacity Mutual Aid?
- Five hospitals in a regional coalition have a mutual aid agreement requiring each to accept diverted patients when a member declares a surge event. Over the past 18 months, two hospitals have declared surge events and received patient transfers from partners. Three hospitals have never declared a surge event and have declined several informal transfer requests, each time citing a specific operational constraint.
- What does Surge Capacity Mutual Aid reveal about how people decide?
- Why mutual aid agreements erode quietly. Mutual aid coalitions fail through accumulated defection, not through dramatic exits. Each hospital that declines a request has a locally defensible reason. The pattern only becomes a crisis at the annual report level, when the cumulative record shows who has borne the obligation and who has not. Repeated games have a built-in corrective: making the history visible to all players. What defectors fear most is a public record, not an abstract penalty.
- How do you avoid the trap in Surge Capacity Mutual Aid?
- Ask your coalition coordinator to share acceptance and decline histories across all members on a quarterly basis, not just annually. The corrective effect of visibility is strongest when the record is recent and specific.
- What is the research behind Surge Capacity Mutual Aid?
- Mutual aid agreements in healthcare are sustained by repeated interaction. Each hospital faces a choice in each surge event: honor the agreement or cite a local constraint and decline. In a one-shot game, declining is individually rational.
- How long does Surge Capacity Mutual Aid 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: surge-capacity, mutual-aid, coalition, patient-flow