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

Run ledger

Every exchange this session has run, and what each one actually did. A run is the record, not the intention: each step carries the bound that decided it, the reason, and the audit hash it was written under — so a refusal is as legible as a delivery, and neither can be edited after the fact.

No runs yet in this session. Wire an exchange on Orchestration, check the preflight, and execute it — it lands here.

Runs live in this session's sandbox: yours are nobody else's, and they are gone when the session resets — which is also when the vendor corpora go back to their starting state.