Can AI agents automate Epic (EHR)?
Epic Systems · hybrid · healthcareehrenterprise
Yes for data access via a large, well-documented FHIR R4 surface (SMART on FHIR OAuth2, bulk export, free sandbox), but write coverage is thin and any production connection is gated on approval from both the Epic customer and Epic itself, so an agent cannot self-serve into a live system. UI-side automation is effectively hostile (Citrix/Hyperdrive), and no first-party MCP or iPaaS connectors exist — community FHIR MCP servers bridging to Epic endpoints are the current agent path.
Best path today: api · Overall automatability: 4/10
Modalities
| Modality | Status | Detail |
|---|---|---|
| API | yes | fhir-r4fhir-stu3fhir-dstu2hl7v2cds-hooksbulk-fhirsmart-on-fhiroauth2 coverage: partial · docs |
| SDK | unknown | official: unknown |
| MCP | yes | verdict: community-only fhir-mcp-server · maintained: True health-record-mcp · maintained: True |
| Integrations | no | |
| CLI | unknown | |
| Extensibility | yes | smart-on-fhir-embedded-appscds-hooks webhooks: unknown |
| Data access | export: bulk-fhir-export, hl7v2-feeds, clarity-sql-reporting-db, caboodle-data-warehouse · import: hl7v2, fhir-write-select-resources | |
| RPA / UI automation | hostile | hyperdrive-webcitrixwin32uipathautomation-anywhere Legacy Hyperspace selectors are dynamic/unreliable and Citrix-published Epic exposes no UI elements, forcing image/OCR/Computer Vision approaches; Hyperdrive (Chromium-embedded, replacing Hyperspace since 2022) changes the UI stack again and forces version churn. RPA vendors sell around this rather than through supported hooks. |
| Computer use | unknown | measured verdicts only — "unknown" means not yet probed by us |
Scores
| api | mcp | rpa | computer use | overall |
|---|---|---|---|---|
| 4 | 2 | 2 | — | 4 |
Evidence
| Fact | Tier | Source | Date |
|---|---|---|---|
modalities.api.kinds | declared | source | 2026-08-15 |
modalities.api.coverage | declared | source | 2026-08-15 |
modalities.api.coverage | declared | source | 2026-08-15 |
modalities.api.kinds | declared | source | 2026-08-15 |
modalities.api.auth | declared | source | 2026-08-15 |
deployment | declared | source | 2026-08-15 |
modalities.mcp.third_party | community | source | 2026-08-15 |
modalities.mcp.third_party | community | source | 2026-08-15 |
modalities.integrations.power_automate | declared | source | 2026-08-15 |
modalities.integrations.power_automate | declared | source | 2026-08-15 |
modalities.integrations.zapier | scraped | source | 2026-08-15 |
modalities.integrations.n8n | community | source | 2026-08-15 |
modalities.rpa.drivability | community | source | 2026-08-15 |
modalities.rpa.ui_stack | declared | source | 2026-08-15 |
modalities.rpa.vendor_support | scraped | source | 2026-08-15 |
modalities.data_access.export | community | source | 2026-08-15 |
modalities.api.exists | community | source | 2026-08-15 |
modalities.rpa.notes | declared | source | 2026-08-15 |
Last verified 2026-08-15 · volatility medium · JSON record