In Basket · Ownership
How should an In Basket pool owner be defined?
Define operational accountability separately from individual message handling. The local model should identify the primary role responsible for monitoring the pool, backup coverage, message categories in scope, aging thresholds, escalation rules and who approves changes to pool membership or routing.
First checks
Work through the workflow before escalating blindly.
- List the message categories expected in the pool.
- Name the primary monitoring role.
- Define backup coverage.
- Set operational aging thresholds.
- Document the escalation path for unowned or misrouted work.
Ownership questions
- Who monitors the pool every day?
- Who covers absences?
- Who owns exceptions?
- Who may approve routing or membership changes?
Avoid making the problem worse
Common failure patterns
- Assuming everyone in a pool owns everything equally.
- Closing messages to improve counts.
- Moving protected content to side spreadsheets.
When to escalate
Suspected routing, access or configuration issues belong with the authorized application/IT team. Patient-specific clinical decisions stay with the clinical chain.
Related resources
Continue with the closest workflow tool.
In Basket overload guide→In Basket workflows→Ownership worksheet→Boundary: Your organization’s approved policy, configuration, security controls and escalation process always control. HelpEpic is independent workflow guidance, not clinical advice or official Epic support. Never send HelpEpic patient names, DOBs, MRNs, screenshots, records, passwords, tokens or confidential internal information.