Emergency department use is a blunt signal. Sometimes it reflects unavoidable acute need, but often it reflects a system failure: early warning signs were missed, escalation pathways did not work, or staff lacked the tools to stabilize distress safely in the community. For commissioners and Medicaid oversight, âwe went to the EDâ is not just a utilization metricâit can indicate gaps in risk management, clinical coordination, and support design. Providers strengthening evidence within IDD outcomes and impact and aligning operational readiness with IDD service models and pathways can treat avoidable ED use as an outcome domain: measurable, improvable, and auditable.
What âavoidable ED useâ means in operational terms
Avoidable ED use typically includes presentations driven by unmanaged escalation (behavioral distress, preventable medication issues, dehydration, constipation, untreated pain, anxiety crises) where earlier intervention could have stabilized the situation. Defensible measurement does not blame individuals; it tests whether the service had reliable detection, decision-making, and escalation controls. The outcome target is not âzero ED visits,â but âfewer avoidable ED visits and faster stabilization with less restrictive intervention.â
Two oversight expectations providers must anticipate
Expectation 1: Escalation pathways must be reliable and evidenced. Oversight bodies commonly expect providers to show how staff recognize deterioration or escalation, what triggers escalation, who is contacted, and how decisions are recorded. âWe tried our bestâ is not defensible without a documented pathway.
Expectation 2: Crisis planning must protect rights and avoid restrictive drift. Regulators and funders frequently scrutinize whether services default to restrictive responses under pressure. Providers must evidence that crisis responses are proportionate, time-limited, reviewed, and linked to learning and prevention.
What to measure to prove crisis prevention
Useful measures include: number of crisis events per person-month; proportion stabilized without ED transfer; time from first warning sign to escalation; frequency of missed escalation triggers; repeat ED presentations within 7â30 days; and quality-of-life stability indicators following crisis events. Importantly, providers should track the ânear missesâ where escalation worked earlyâbecause these demonstrate prevention capacity, not just crisis frequency.
Operational Example 1: Early warning sign detection embedded into daily routines
What happens in day-to-day delivery
Staff use a simple early warning checklist tailored to the person: sleep disruption, appetite change, withdrawal, increased pacing, refusal patterns, pain indicators, or communication changes. These indicators are checked at consistent times (for example, morning routine and evening wind-down) and recorded in a structured note that flags changes automatically for the shift lead. When thresholds are metâsuch as two consecutive days of poor sleep plus increased agitationâthe escalation pathway begins: additional monitoring, environmental adjustments, and clinical liaison if needed.
Why the practice exists (failure mode it addresses)
This practice prevents âsilent deterioration,â where early warning signs are normalized or noted informally but not acted on until crisis occurs. Many ED transfers stem from missed patterns rather than sudden events.
What goes wrong if it is absent
Staff interpret changes as âjust a bad dayâ and do not escalate. Minor pain becomes severe distress, constipation becomes acute discomfort, anxiety spirals into unsafe behavior, or dehydration triggers avoidable medical presentation. The service appears reactive and inconsistent across shifts.
What observable outcome it produces
Providers can evidence faster escalation when warning signs appear, fewer severe crises, and increased stabilization in the community. Audit samples show a clear trail: early signs identified, actions taken, and outcomes tracked.
Operational Example 2: A structured escalation pathway with clear roles and time limits
What happens in day-to-day delivery
The service uses a stepwise escalation pathway with time-bound actions: Step 1 (within 30 minutes) implement agreed de-escalation supports and consult the behavior support plan; Step 2 (within 60â90 minutes) notify a supervisor and consider clinical consultation; Step 3 (within 2â4 hours) activate a crisis support resource (mobile crisis team where available, on-call clinician, or telehealth), and document decision rationale; Step 4 assess whether ED transfer is clinically necessary. Each step includes a requirement to document what was tried, what worked, and what risk remains.
Why the practice exists (failure mode it addresses)
The failure mode is âescalation ambiguity,â where staff are unsure when to call for help or rely on ad hoc judgment. Ambiguity creates delays and increases the likelihood of ED transfer as the only visible option.
What goes wrong if it is absent
Some staff escalate too late; others escalate too early without trying stabilizing supports. Families and system partners receive inconsistent communication. In extreme cases, staff use restrictive interventions longer than necessary because escalation support is unavailable or poorly defined.
What observable outcome it produces
Organizations can show improved timeliness of escalation, fewer prolonged incidents, and a higher proportion of crises stabilized without ED transfer. Documentation also becomes audit-ready: decisions are traceable and consistent across staff teams.
Operational Example 3: Post-crisis review that turns events into prevention
What happens in day-to-day delivery
Within 72 hours of a significant crisis or ED visit, the team completes a structured post-crisis review: what triggered escalation, what early warning signs were present, what interventions were attempted, and what barriers delayed stabilization. The review produces two outputs: (1) an updated prevention plan (environmental changes, routine adjustments, clinical follow-up) and (2) a staff learning note that clarifies future responses. Where patterns suggest systemic issuesâsuch as repeated constipation-related distressâthe provider adjusts proactive health monitoring and care coordination.
Why the practice exists (failure mode it addresses)
This practice prevents ârepeat crises with no learning,â a common failure mode where ED visits become routine because no structured reflection turns events into changed practice.
What goes wrong if it is absent
ED visits recur for the same reasons: unmanaged pain, medication side effects, staff misunderstanding of triggers, or weak coordination with primary care. The service becomes trapped in a reactive cycle that drives cost, risk, and burnout.
What observable outcome it produces
Providers can evidence reduced repeat ED use within 30 days, improved stability indicators, and clearer prevention controls. Governance can track whether post-crisis actions were completed and whether they reduced future events.
Governance: demonstrating defensible crisis prevention
To demonstrate credible outcomes, crisis prevention should be reviewed in governance using both utilization and reliability metrics: ED visits (avoidable vs unavoidable where defensible), time-to-escalation, stabilization rates, repeat presentations, and restrictive intervention review findings. Governance minutes should record service-level actionsâtraining refreshers, escalation pathway changes, clinical liaison improvementsâand schedule re-audits. This shows oversight bodies that the provider understands system reality and is actively reducing avoidable risk.
Conclusion
Reducing avoidable ED use in IDD services is achievable when early warning detection, escalation reliability, and post-crisis learning are built into daily operations. By measuring these controls and linking them to outcomesâstability, safety, and rights protectionâproviders can evidence real impact that stands up to Medicaid and state scrutiny.