φ(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
Data Orchestration
Orchestration Connected systems Patient link set Practitioner crosswalk Permission lattice What each system holds Run ledger Ingest & mapping QA Data Store
System
Control panel Model monitoring Components
Governance
Registry & preflight Fairness screen Ambient consent gate Source attributes Retention Audit
Documentation
System documentation Implementation & setup guide Feature documentation Model documentation System architecture EMR connections Orchestration & identity Emulators & non-PHI setup Compliance & responsibility Attribution

Control panel

The System Administrator's seat. Everything on the platform can be controlled from here — the live model, the outbound feeds, the import hold, the integrity checks — and none of it quietly: full control is not exemption, and every switch thrown on this page lands on the audit trail under your name.

Runtime settings that do not belong to a single subsystem. Assistant settings live in Assistant and EMR connection settings in Integrations — each beside the controls they describe.

SettingValueConstraint
Suggested-prompt examples
Example patient (short name)
example_patient
 must name a real patient
Example patient (full name)
example_patient_full
 must name a real patient
Example patient MRN
example_patient_mrn
 must name a real patient
Example claims patient
example_claims_patient
 must name a real patient
Only changed keys are written and audited; unchanged values are left untouched.

Where the rest of the platform is configured

Setting groupWhere it livesWhy there
Answer length, active model, retrieval and live-call switches Assistant Beside the switches they describe.
Model slot bindings, registration, enablement Model registry Binding a model is an audited decision, not a saved field.
Source and target EMR connections Integrations · Source & target EMRs Beside the pause and resume controls.
Users, roles and permissions Access Read-only here: your identity provider is the authority.
Holdings inventory and integrity checks Data Store Reporting surface, not a control.

Vendor corpora

Each of the fifteen emulated systems has its own store, as rows. A record is in a vendor's corpus because there is a row saying so — which is what lets a delivery put one there: a run reads out of the source, lands it in the PHI AI store, and writes it into the target, and from then on the target's own counts, search and chart include it. Every visitor's movements are their own and are deleted when their session starts, so the demo resets for every visit.

materialised 169,566 chart-holdings · 3,148,076 records held across the 18 connected systems.

Idempotent — running it again adds nothing twice.