Independent Epic workflow resource for healthcare teamsNo patient information · Not affiliated with Epic Systems Corporation
In Basket operations

Epic In Basket Overload: Workflow Triage

A workflow-focused way to break down In Basket overload, unclear pool ownership, aging messages and repeat work without making clinical decisions.

Useful for: Clinical operations, nurses, providers, pool managers, application teams and practice administrators.

What this often looks like

Common symptoms

Messages are aging because ownership is unclear

Clarify ownership and the expected next handoff before creating more work.

Multiple people assume someone else is handling the same item

Clarify ownership and the expected next handoff before creating more work.

Coverage rules are inconsistent during absences

Clarify ownership and the expected next handoff before creating more work.

Staff use side lists because the official queue feels unmanageable

Clarify ownership and the expected next handoff before creating more work.

First checks

Work through these before escalating blindly.

  1. Separate message volume from ownership problems
  2. Identify which message types belong to individuals versus pools
  3. Confirm coverage rules for vacation, leave and after-hours work
  4. Define aging thresholds and escalation paths by operational category
  5. Look for duplicate or unnecessary handoffs before asking staff to work faster

Ownership questions

  • Who owns each message type?
  • Which pool is accountable when an individual is unavailable?
  • What age or status requires escalation?
  • Which items should never be handled outside the approved workflow?
Avoid making the problem worse

Do not use a workaround as the default process.

  • Making patient-specific clinical decisions through HelpEpic
  • Moving work to unofficial spreadsheets as a permanent fix
  • Deleting or closing work simply to reduce counts
  • Changing pool configuration without authorized governance
Security and privacy boundary. Do not send HelpEpic patient names, DOBs, MRNs, insurance identifiers, screenshots, records, passwords, tokens or other confidential information. Access, outages, security incidents, protected configuration changes and patient-specific clinical decisions belong with your organization’s authorized teams.