φ(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 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 System architecture EMR connections Emulators & non-PHI setup Compliance & responsibility Attribution
Repository

Source patient import

Add to the corpus, one patient at a time: search the source EMR, pull the patient over the per-patient read path, and their record joins your Patients & charts — imported, encrypted, indexed and audited. Bulk population runs stay on the integration side; this is the front-desk moment a new patient walks in.

Source EMR lookup — pull one patient now

Between bulk runs, new patients exist at the source that PHI AI has not seen. Search the source EMR directly and import an individual patient over the per-patient read path — the same path bulk-less vendors force for entire populations.

An individual import runs read → encrypt → store → index for one patient and lands in your session's sandbox: the patient appears in Patients & charts, the import is audited (ingest.patient_imported), and the next reconciliation on the Bulk import manager counts them.