φ(ai) PHI AI
Menu
Clinical workspace
Patients & charts PHI AI assistant Signature queue Ambient documentation Imaging worklist Summarization Inbox triage Patient instructions
Revenue & records
Claims & billing Prior auth & appeals Documentation gaps Release of information Sensitive categories
Population
Cohort builder No-show risk Scheduling optimization Trial pre-screening Quality measures Ingest & mapping QA Data Store
Integration
Source & target EMRs Source patient import Bulk import manager Streaming data Bulk export manager Streaming export
System
Control panel Model monitoring
Governance
Registry & preflight Fairness screen Ambient consent gate Source attributes EMR conformance Retention Audit
Documentation
System documentation Implementation & setup guide Feature documentation Model documentation System architecture EMR connections Emulators & non-PHI setup Compliance & responsibility Attribution
Ryan GomezRole
Signed in — Ryan 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
DocumentationDocs
System documentation Implementation & setup guide Feature documentation Model documentation System architecture EMR connections Emulators & non-PHI setup Compliance & responsibility Attribution
Repository

← Control panel

Model configuration

Scheduling optimizer — the registry entry behind the scheduling capability slot. Every change saved here is an audited event (system.model_updated) naming the fields that changed; lifecycle moves stay on the Control panel.

scheduling
capability slot — fixed at registration
enabled
lifecycle status
built-in
ships with the platform

Identity & endpoint

Kind (optimization) and slot are fixed at registration — a different kind or slot is a different model.

Tracking & governance attached to this model

  • Per-invocation audit: every inference this model serves writes model.inference naming it — see the audit trail.
  • Monitoring: its slot's live metrics, drift recognition and alerts are on Model analytics & monitoring; alerts never close themselves.
  • Lifecycle: enable, disable, activate and delete stay on the Control panel, each an audited event under the operator's name.

This model's audit history — your session

No lifecycle or configuration events for this model in your session yet. Changes you make land here — and on the audit trail.