The Simulation Library

Six scenario types. Five intake stages. Role-based exercises using fictional patients and real-world workflow complexity — not sanitized textbook examples.

Why Simulation Beats Slide-Based Training for Building Real Judgment

There's a gap between knowing the right answer on a training quiz and making the right call under pressure in a real workflow. Slide-based e-learning fills the first half of that gap — it gets coordinators to the right answer in a controlled scenario where every variable is presented clearly and the stakes are zero.

Simulation training fills both halves. It presents a scenario with realistic complexity — incomplete information, competing priorities, volume pressure, ambiguous verification results — and requires an active decision. Then it debriefs the decision, identifying what was correct, what was missed, and why.

That debrief is where judgment gets built. Coordinators don't just learn that they made an error — they learn to recognize the pattern that led to the error, so they can catch it the next time before it becomes a denial.

Generic E-Learning vs. IAA Simulation Training

Generic E-Learning

  • Teaches definitions and steps
  • Idealized, clean scenarios
  • Passive content consumption
  • Knowledge recognition quiz
  • Certificate of completion
  • No feedback on decision quality
  • No follow-up accountability

IAA Simulation Training

  • Builds judgment and pattern recognition
  • Realistic operational complexity
  • Active decision-making under pressure
  • Debrief with root-cause analysis
  • Measurable accuracy improvement
  • Immediate, specific decision feedback
  • 30-day follow-up and accountability

Six Scenario Types. Every Intake Stage Covered.

Each scenario type is built around the real decision points where intake accuracy breaks down — using fictional patient data and realistic workflow complexity. Scenarios are customized for each client based on their specific gap profile.

Stage 1 — Referral Intake

The Incomplete Referral

A faxed referral arrives with missing diagnosis codes, unclear medication dosing, and a prescriber name that doesn't match the NPI lookup. The coordinator must decide: accept, pend, or reject — and document the decision correctly. Variations include physician office follow-up, referral source escalation, and time-sensitive drug scenarios.

Stage 2 — Insurance Verification

The Dual Coverage Problem

A patient has both commercial insurance and Medicare Part B. The automated verification returns a clean eligibility result for one payer — but coordination of benefits isn't addressed. The coordinator must determine the correct primary/secondary designation, identify coverage limitations, and confirm infusion therapy is covered under the correct benefit before proceeding.

Stage 3 — Prior Authorization

The Misrouted PA

A prior authorization is submitted through the automation routing tool, which selects the incorrect payer portal based on the plan code. The PA is approved — but for the wrong benefit tier, without the required clinical documentation, and with an authorization number that won't match the eventual claim. The coordinator must catch the mismatch before start-of-care.

Stage 4 — Clinical/Pharmacy Handoff

The Handoff That Almost Worked

The intake coordinator completes verification and prior auth and passes the case to pharmacy — but the handoff documentation is missing the infusion rate, the prescribing physician's verbal order confirmation, and the patient's weight (required for weight-based dosing). Pharmacy prepares the order based on available data. The coordinator must recognize and correct the handoff gap before the order is released.

Stage 5 — Start-of-Care

The Date Discrepancy

The prior authorization was approved with a specific start date. The patient's actual start-of-care occurs three days later due to a nursing scheduling issue. The coordinator must determine whether the authorization is still valid, whether a date extension is required, and how to document the discrepancy in a way that protects the claim — without delaying patient therapy.

AI Oversight Scenario

The Confident Wrong Answer

An AI-assisted benefits verification tool returns a clean eligibility result and a prior authorization pathway recommendation. The coordinator reviews the output — which looks complete and correct. But buried in the plan details is a specialty pharmacy carve-out that the tool didn't flag, which means the authorization pathway it recommended will produce a denied claim. The coordinator must catch what the automation missed.

What a Simulation Session Looks Like

Here's a narrative walkthrough of one scenario from the Prior Authorization module — to give you a concrete sense of how IAA simulation sessions run.

Scenario: The Misrouted Prior Authorization

The setup: A referral arrives for a patient with a commercial plan from a regional payer — let's call it Fictional Commercial Plan A. The coordinator enters the patient into the intake system and the automated PA routing tool selects the correct payer portal based on the plan code. So far, everything looks normal.

The problem: The patient is enrolled in a high-deductible health plan with a specialty pharmacy carve-out. The automated routing tool identified the plan correctly but didn't check for carve-out provisions — because that logic isn't in its rule set. It submitted the PA to the medical benefit. The PA is approved. The authorization number is valid. The system shows green.

The coordinator receives the approved PA and is asked to proceed. In the simulation, they must review the authorization details before marking the case as PA-complete. Most coordinators in an untrained team mark it complete without reviewing the benefit tier.
The trained coordinator spots the mismatch — the authorization number format doesn't match what they expect from this payer's medical benefit authorizations, or the approved therapy duration is shorter than clinically expected. Something doesn't add up.
They escalate and confirm — calling the payer to verify the benefit tier and confirming there's a specialty pharmacy carve-out. The medical benefit authorization is valid for a different therapy type. A new PA is required under the specialty pharmacy benefit.
The debrief — participants walk through what the untrained coordinator would have missed, why the automation returned a false-positive, and what pattern to look for next time. The debrief is where the judgment gets cemented.

Without simulation: The coordinator trusts the green status and the case moves forward. The claim is denied. The billing team works it for 30–60 days. Revenue recovery is partial at best.

With simulation: The coordinator recognizes the pattern — because they've practiced this scenario. The error is caught before start-of-care. No denial. No billing rework.

How IAA Simulation Sessions Are Structured

Every session follows a consistent structure — whether it's a weekly Retainer session or a VIP Intensive day.

1. Brief

Kemal presents the scenario setup — patient context, referral details, payer information. The team receives the same information they'd have in a real workflow.

2. Execute

Participants work through the scenario — making decisions, documenting their reasoning, and escalating where appropriate. Time constraints are real.

3. Debrief

Kemal walks through the decision points, identifies what was missed and why, and articulates the pattern the team should recognize next time. This is where judgment is built.

4. Apply

Participants leave with specific, actionable adjustments to their personal workflow — not general takeaways, but concrete changes to make Monday morning.

See How Simulation Training Would Apply to Your Team

Book a free intake workflow overview. Kemal will walk through one of your team's actual accuracy challenges and show you how simulation training would address it.