Go-Live · Stabilization
What 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.
First checks
Work through the workflow before escalating blindly.
- Describe the workaround without patient information.
- Identify the intended standard workflow.
- Classify why staff are using the workaround.
- Count how often it recurs by broad category.
- Assign an owner to approve, replace or retire it.
Ownership questions
- Who owns the standard workflow?
- Who may approve a temporary workaround?
- Who owns training reinforcement?
- Who escalates suspected defects?
Avoid making the problem worse
Common failure patterns
- Normalizing unofficial workarounds indefinitely.
- Creating clinical workarounds outside governance.
- Collecting patient examples when a no-PHI description is sufficient.
When to escalate
Security, patient-safety, access and suspected production-defect workarounds should be escalated immediately through authorized channels.
Related resources
Continue with the closest workflow tool.
First 10 Shifts kit→Post-go-live workflow guide→Post-go-live support→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.