Ryan Gomez

r.gomez

System Administrator

You stay on this screen — each role sees it as their own permissions allow. The assistant thread and the patient in context start fresh.

Working archetypes — combinations people really hold

One role at a time — each role on its own

Purpose of use

Treatment Payment Health care operations Patient request Legal Research

Asserted per action, never kept as a mode. The highlighted purpose is this role's default; the assistant and release screens ask for one explicitly.

Patient in context

None. Opening a chart sets one; lists then narrow to that patient until it is closed.

Permissions all

Every permission, including the control panel no other role sees. Full control is not exemption: every action still lands on the audit trail under your name.

Integration

sources: 1: Epic
targets: 1: Epic writable

Reads are bounded by the source's granted scopes, writes by the target's own CapabilityStatement, and both by this role here. The narrowest of the three wins; nothing is unioned. see the lattice

Patient link set

Which chart in which system is this person. Each row is one system's own identifier for the patient in context — typed by an operator from that system, not derived from a name, a birth date or an MRN — and a delivery crosses only on a row a human has verified. Every add, verification and rejection is on the audit trail under identity.*.

Who is this for?

This feature works on a patient, and no patient is in context. Pick one — the selection is recorded, and it follows you until you clear it or switch roles.

Recently seen patients shown — or search above. The full roster is in Patients & charts.

Synthetic patients; real identity mechanics. The platform's PatientMapping carries the same three facts — the two ids and who verified them.