φ(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

EMR conformance

The six vendor profiles the integration layer actually runs on — auth model, bulk export, write surface — rendered from the same capability table the connectors read (emr_profiles). This is data-driven conformance: a vendor quirk lives here as a row, never as an if in the client.

Probes the configured source and target profiles and records the evidence.
VendorAuth modelBulk exportWrite surface
Epic
configured source
configured target
 SMART Backend Services — RS384-signed JWT client assertion; public key registered with the client ID supported
Group-level Bulk Data Export only; requires a Group FHIR ID from Epic; rate-limited to once per 24 hours per group and client; every kickoff is a full re-extract
 Notes and observations writable; medication orders are read-only over FHIR REST (CDS Hooks suggestions only)
Oracle Health (Cerner) SMART Backend Services with MANDATORY explicit system/<Resource>.read scopes — wildcard scopes are not supported supported
Bulk Data Export supported at group level
 Narrower write surface; confirm against the instance CapabilityStatement
athenahealth OAuth2 client credentials — client ID and client secret (no JWT assertion) supported
Bulk export supported with vendor-specific constraints
 Confirm per API registration
eClinicalWorks SMART Backend Services JWT assertion supported
Supported; throughput limits apply
 Confirm per instance
MEDITECH Expanse SMART Backend Services JWT assertion supported
Supported on current Expanse releases
 Confirm per instance
NextGen Healthcare SMART Backend Services JWT assertion supported
NO Bulk Data Export in the vendor profile — the platform's bulk scheduler refuses this vendor at startup rather than silently falling back to paged search
 Confirm per instance

A vendor whose profile records no $export is refused by the bulk scheduler at startup — conformance is enforced, not merely displayed. Change the source or target in Source & target EMRs and this page follows.

SPEC 6.7: every connector is exercised against a per-vendor emulator reproducing these seams; Epic alone has also run against a live vendor sandbox.