Operational workflow questions healthcare teams actually ask.
Short, independent answers for referrals, portal routing, records, In Basket ownership, scheduling, training, go-live stabilization and escalation. Every answer stays at the workflow level: no patient information, no credentials and no invented organization-specific configuration.
Start with the operational problem.
Why are referrals delayed after an Epic migration?
Treat the delay as a handoff problem before assuming the entire referral process is broken. Separate order entry, required information, authorization, workqueue ownership, scheduling readiness and patient-contact follow-up. Then identify the first point where the expected owner or status transition no longer matches the local post-migration process.
Referrals · WorkqueuesWhat should I check when a referral is stuck in a workqueue?
Start by identifying the exact next action and the accountable owner. A referral can be visible in a workqueue yet still stall because the readiness criteria, aging rule, backup owner or exception path is unclear. The goal is to determine whether the item is waiting appropriately or has lost ownership.
Referrals · AuthorizationWho should own a referral after authorization is complete?
There is no universal owner because local workflows vary. The organization should define the event that marks authorization as complete, the receiving role or queue, the expected handoff time and the exception path when scheduling or referral readiness is still incomplete.
Front Desk · PortalHow should front desk staff classify portal requests?
Classify the request before routing it. Common operational categories include account or access help, proxy or caregiver access, message-status questions, records requests, billing questions, technical errors and requests that require clinical review. Each category should have one approved destination and a clear stop point for the front desk.
Portal · HandoffsWhy do portal requests keep bouncing between teams?
Repeated routing usually signals unclear request classification or ownership rather than a need for more destinations. Define the request type, one accountable receiving team, the information required before handoff and the exception route when the request falls outside normal ownership.
Records · RoutingWhere should scanned records be routed?
Use the organization’s documented routing standard by document type and receiving team. A good local standard defines who classifies the document, where it is sent, who acknowledges it, what proves the handoff completed and where rejected or misclassified items go.
Records · ExternalWhy are outside records not visible to the receiving team?
Separate storage from routing. A record can exist in the system but still fail operationally if the receiving team does not know it arrived, the document type is inconsistent, the destination is wrong or no one owns acknowledgment. Map the intake-to-receipt handoff before creating another copy.
In Basket · OwnershipHow 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.
In Basket · AgingWhy are messages aging in an In Basket pool?
Aging can come from volume, unclear ownership, missing backup coverage, misrouting or an undefined escalation threshold. Measure which categories are aging before asking staff to work faster. The operational fix depends on whether the queue is overloaded or simply unowned.
Training · OnboardingWhat should a new employee learn first in an Epic workflow?
Teach the work in the order the employee encounters it: the highest-frequency tasks, the owner after each handoff, the queues or pools they are responsible for, what not to do, and where exceptions go. Navigation matters, but the local operating model should come before rare features.
Training · AccessHow can I tell training confusion from an access problem?
Ask whether the user understands the approved workflow and whether the expected function or destination is actually available to them. If the process is clear but a required feature, queue or function is unavailable, treat it as an access/support issue rather than repeating training.
Escalation · OperationsWhat should be included in a workflow escalation?
A useful escalation explains the operational goal, expected handoff, actual behavior, current owner, age or impact, and checks already completed. It should classify the issue without adding unnecessary patient detail. The goal is to give the receiving team enough context to act without making them rediscover the workflow.
Scheduling · HandoffsWhat should I check when scheduling is waiting on another team?
Identify the exact readiness event scheduling is waiting for. Then identify which team owns that prerequisite, how readiness is communicated, and the exception path when the expected handoff does not arrive. Avoid treating referral readiness, authorization readiness and appointment capacity as the same problem.
Authorization · SchedulingWhy are authorization and scheduling waiting on each other?
This usually means the readiness rule or ownership boundary is ambiguous. Define what authorization needs before it can proceed, what scheduling needs before it can accept the request, and which role owns the case while those prerequisites are incomplete.
Go-Live · StabilizationWhat should we do when the same workaround keeps appearing after go-live?
Treat recurrence as a signal that the issue needs classification and governance. Determine whether the workaround compensates for a training gap, unclear local ownership, access problem, policy gap or suspected defect. A repeated workaround should not quietly become the permanent process.
Go-Live · TriageHow do we classify a go-live issue as training, access, workflow or defect?
Classify by the nature of the blocker, not by frustration level. Training means the approved process is available but not understood. Access means the user cannot reach what their authorized role requires. Workflow means local ownership or handoff is unclear. A suspected defect means the approved process is understood but the system does not behave as expected.
Practice Management · Standard WorkHow can a practice manager reduce repeated Epic workflow questions?
Group repeated questions by workflow and role, then turn the highest-frequency questions into short approved job aids with named owners and escalation points. The goal is not to eliminate questions; it is to stop paying the cost of rediscovering the same operational answer every week.
Training · SOPsHow do we build a useful local SOP without patient screenshots?
Write the SOP around the task, owner, destination, decision point, exception and escalation route. Most workflow guidance does not require a patient screenshot. If a visual is essential, use organization-approved training environments or properly authorized de-identified materials under local policy.
Results · OwnershipHow should non-clinical ownership for results follow-up be documented?
Document operational ownership without making clinical decisions. The local workflow should specify which role or pool receives the result-related task, who monitors completion, how coverage works, and when an item leaves routine operations for a clinician or authorized escalation channel.
Revenue Cycle · WorkqueuesHow should a revenue-cycle workqueue backlog be triaged operationally?
Break the backlog into operational categories before applying one broad productivity response. Separate missing information, unclear ownership, routing issues, policy exceptions and repeat rework. Then define an owner and aging rule for each category.
Escalation · ITWhen should a workflow issue be sent to internal IT or the application team?
Escalate when the blocker is no longer a question of local ownership or training. Access provisioning, authentication, outages, security incidents, interfaces, suspected defects, protected configuration and production changes belong with authorized internal teams.
Operations · OwnershipWhat should be included in a workflow ownership map?
A useful ownership map names the request or task type, primary owner, backup owner, expected handoff, aging or exception trigger, and escalation destination. Keep it role-based and operational so staff can use it without patient information.
Operations · Duplicate WorkHow do healthcare teams reduce duplicate workflow tasks?
Duplicate work often appears when staff cannot tell whether the original handoff succeeded. Improve visibility of the current owner, completion signal and aging rule before adding more reminders. A clear escalation path should replace the habit of recreating the task.
Training · Super UsersHow should super users help staff without creating unofficial process?
Super users are strongest when they reinforce approved workflows, identify recurring questions and improve documented standard work. They should not become an alternate production-support or governance channel for access, configuration, security, clinical decisions or permanent undocumented workarounds.
Operations · StandardizationHow do we standardize an Epic-related workflow across multiple locations?
Standardize the core handoff first, then document legitimate local exceptions. Define the task, primary role, receiving owner, completion signal, aging trigger and escalation path that should be consistent. Avoid forcing different staffing models into identical instructions when the underlying ownership genuinely differs.