In community-based care, “care coordination” is often described as a principle rather than an engineered process. Yet avoidable emergency department use and preventable readmissions usually trace back to the same operational gaps: missed follow-up, unclear escalation routes, fragmented responsibility, and medication confusion. This article sets out practical, repeatable workflows for Primary Care & Care Coordination, designed to align with Quality Assurance, Oversight & Accountability expectations across U.S. systems.
Why Avoidable ED Use Persists in Community-Based Care
Most providers do not lack commitment or effort. What they often lack is a coordination system that assumes real-world constraints: overstretched primary care, inconsistent portals, partial information, and variable staff experience. When coordination relies on informal knowledge or individual judgement alone, predictable failure points emerge.
Common drivers of avoidable escalation include:
- Vague escalation guidance (“call the doctor if worried”) with no defined thresholds
- Multiple staff contacting clinics independently, creating duplication and confusion
- One-way communication with no confirmation or closure loop
- Medication changes after urgent care or ED visits that are never reconciled
- Follow-up appointments booked but not attended or supported
Effective coordination treats these issues as design problems, not performance issues.
The Core Design Principle: Close the Loop
Coordination only protects people when actions are completed and verified. Sending a message, leaving a voicemail, or flagging a note is not enough. A defensible coordination workflow follows a simple logic: initiate contact, confirm receipt, confirm plan, implement actions, and verify completion.
Without closure, organizations accumulate “coordination debt” — unresolved actions that quietly increase risk until a crisis occurs.
Workflow 1: Tiered Same-Day Escalation for Deterioration
Community providers often see deterioration first: new confusion, rapid functional decline, repeated falls, dehydration, medication side effects, or escalating behavioral risk. Staff need a clear pathway that removes guesswork.
Tiered escalation structure
- Tier A: Emergency now — explicit criteria requiring 911 (e.g. stroke signs, chest pain, severe respiratory distress, unresponsiveness).
- Tier B: Urgent clinical same day — contact primary care or urgent clinical line (e.g. sudden confusion, multiple falls, suspected adverse drug reaction).
- Tier C: Non-urgent within 48–72 hours — schedule review, labs, or medication check.
Each tier must define: who contacts primary care, how contact is made, what information is shared, and what verification is required.
Operational Example 1: Embedded “Red Flag” Deterioration Prompts
A provider supporting older adults in HCBS identifies wide variation in staff escalation decisions. Some escalate too late; others escalate unnecessarily. The organization introduces structured “red flag” prompts embedded into daily notes and shift handovers.
How it operates: staff select from a defined list of red flags (new confusion, refusal of fluids, new falls, acute pain, new medication within 7 days). Each flag automatically maps to a Tier A, B, or C response. For Tier B and above, a supervisor review is mandatory within 24 hours.
Why it exists: it standardizes escalation across experience levels and reduces reliance on individual judgement alone.
Risk addressed: delayed clinical review leading to ED escalation.
Workflow 2: Post-ED Follow-Up Assurance
Care transitions are one of the most consistent drivers of readmissions. Discharge instructions often do not translate into daily routines, especially when multiple providers are involved.
Operational Example 2: The 72-Hour Post-ED “Four Checks” Process
A community-based provider implements a structured post-ED workflow for high-risk individuals.
- Check 1: Documentation capture — discharge paperwork and medication changes logged within 24 hours.
- Check 2: Primary care notification — structured summary sent to the PCP requesting confirmation of active medications and monitoring needs.
- Check 3: Follow-up booked — appointment confirmed and attendance supported.
- Check 4: Plan adjustment — temporary service changes documented (extra visits, hydration prompts, falls prevention).
Supervisors verify closure of all four checks before the case is marked complete.
Workflow 3: Medication Coordination as an Ongoing Process
Medication-related harm is a leading cause of avoidable ED use. Community providers often see side effects and adherence issues long before clinicians do, but that intelligence must be structured to be usable.
Operational Example 3: Monthly “Medication Signals” Review
A provider identifies high-risk medication classes common in its caseload: anticoagulants, insulin, opioids, benzodiazepines, antipsychotics, and strong anticholinergics.
How it operates: staff collect standardized signals during routine visits (sedation, dizziness, confusion, falls, appetite change, missed doses). When thresholds are met, the coordinator sends a concise summary to primary care requesting review. Supervisor sign-off confirms that any clinician response is implemented.
Risk addressed: adverse drug events escalating into emergency presentations.
Oversight Expectations Providers Must Design For
Expectation 1: Demonstrable reduction of avoidable utilization
Payers, counties, and managed care organizations increasingly expect providers to evidence processes designed to reduce avoidable ED use for defined cohorts. This does not require medical causation claims, but it does require clear workflows and trend review.
Expectation 2: Accountability, not just activity
Oversight bodies expect to see who did what, when, and with what outcome. A coordination log without closure verification is not defensible.
Governance and Assurance at Scale
Coordination systems fail when leaders assume they will run themselves. Effective assurance includes:
- Monthly sampling of coordination cases for closure quality
- Quarterly trend review of repeat escalation drivers
- Competency checks on escalation thresholds and information sharing
- Clear operating notes for high-volume primary care partners
From Informal Coordination to System Capability
Care coordination is not an abstract ideal. It is a system capability built from triggers, workflows, verification, and governance. Providers that engineer coordination in this way reduce avoidable escalation, support primary care continuity, and create defensible evidence of quality and accountability.