Records · External
Why 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.
First checks
Work through the workflow before escalating blindly.
- Confirm the record was received through an approved channel.
- Confirm document classification.
- Identify the intended receiving team.
- Confirm the acknowledgment step.
- Check the exception route for unclassified or rejected items.
Ownership questions
- Who receives external records?
- Who classifies them?
- Who is expected to act on them?
- Who owns records that cannot be matched to the normal workflow?
Avoid making the problem worse
Common failure patterns
- Uploading or scanning multiple copies.
- Using unapproved personal storage.
- Sharing patient documents outside authorized channels.
When to escalate
If records are classified and routed according to the approved procedure but remain unavailable, escalate to the authorized HIM or application team.
Related resources
Continue with the closest workflow tool.
Outside-records guide→External records topic→Records workflows→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.