Training · SOPs
How 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.
First checks
Work through the workflow before escalating blindly.
- Define the purpose of the SOP.
- Write the task sequence in plain operational language.
- Name the owner after each handoff.
- Add stop and escalation rules.
- Assign an owner and review date.
Ownership questions
- Who approves the process?
- Who maintains the SOP?
- Who reviews it after upgrades or staffing changes?
- Who decides whether visual training material is permitted?
Avoid making the problem worse
Common failure patterns
- Patient screenshots in public or external tools.
- Credentials in training material.
- Screenshots that hide weak ownership instructions instead of clarifying them.
When to escalate
Questions about privacy, screenshots and training-environment use should follow the organization’s compliance, security and education policies.
Related resources
Continue with the closest workflow tool.
Workflow Training & SOP Support→Ownership worksheet→Training topic→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.