Module 2
Why Context Matters in Quality Improvement
Comparing frameworks side by side is useful, but it raises an obvious question: how do you actually choose? The answer is context. The same problem can call for a different approach depending on where you're working, who's on your team, and what resources you have.
Lean and the Model for Improvement are two of the more popular approaches in health care, but they're far from the only ones. Teams also draw on Six Sigma, Operational Excellence, Agile, and others. Context helps narrow the field, including:
- Setting: EDs, outpatient clinics, schools, EMS systems, rural critical access hospitals, telehealth platforms, or community mental health centers.
- Culture: Staff engagement, leadership support, psychological safety, openness to change, and the team's history with improvement efforts (positive or negative).
- Structure: Staffing models, workflows, EMR capabilities, available resources, governance, and reporting relationships.
For PMHCA programs specifically, the Model for Improvement is often a great starting point. It's the framework most widely used across health care, developed and promoted by the Institute for Healthcare Improvement (IHI), and its small-scale PDSA cycles are built to flex around local context rather than assume it away.
A test that works in a well-resourced urban children's hospital may require substantial adaptation in a rural critical access hospital or a school-based setting, and the Model for Improvement's rapid, low-stakes testing makes that adaptation possible without a major upfront investment.
Context is not a barrier to QI — it is a design parameter.
Audience-Specific Example
Context in Practice: Different Settings, Same QI Approach
Every team below shares the same aim: to reduce the time it takes to connect a young patient who screens positive to follow-up behavioral health care. What changes isn't the goal; it's what test each team can actually run, given their setting, culture, and structure.
| Audience | Scenario / Application | Key Takeaway |
|---|---|---|
School-Based Clinician / School Nurse |
No embedded behavioral health staff, so the team tests a shared referral-tracking sheet and a monthly check-in call with a local group of therapists to close the loop on referrals. |
Same goal, but the test has to work across organizational lines, using tools they don't control. QI here depends on trust and simple, shared tools rather than internal systems. |
Hospital-Based Clinic |
On-site behavioral health staff let the team test an EMR alert that flags positive screens for an immediate internal warm handoff, rather than a mailed referral. |
Same goal, reached faster because the infrastructure already exists. Fewer collaborators mean a quicker test-and-learn cycle. |
EMS System |
With no pediatric psychiatric facility nearby, the team tests a direct communication pathway to a telehealth crisis line while a patient awaits transport. |
Same goal, but the "connection to care" must occur before a facility handoff is even possible; the constraint becomes the design. |
Rural Critical Access Hospital |
Without an EMR-integrated option, the team tests a paper-based screening tool paired with a fax referral pathway to the nearest behavioral health center. |
Same goal, reached with a low-tech test; and it works: 88% screening compliance shows simplicity is a feature, not a limitation. |
Large Pediatric ED |
With more infrastructure available, the team tests an EMR-integrated tracking system and a real-time dashboard across nursing, social work, and psychiatry. |
Same goal, but achieving it means coordinating more disciplines; more resources also mean more collaborators to align. |