ArkCloud Health
5 min read

Epic Integration

ArkCloud has not yet exchanged data with any Epic system. A Rehab administrator can configure a read-only hospital record import connection with an Epic profile, built to Epic's SMART Backend Services requirements but not yet verified against an Epic system; the hospital must register and activate ArkCloud's client before it can work. The EHR sync API still answers "EHR sync is not available". This page says what exists, what does not, and how practices that use Epic exchange data with ArkCloud now.

What exists in the code

Hospital record import with an Epic profile (Rehab, not yet verified)

A Rehab administrator configures one connection per hospital on the Hospital connections screen (/rehab/settings/integrations/outside-records), choosing the EPIC profile, and checks it against the hospital (its CapabilityStatement and a SMART Backend Services token). Staff then import a patient's records read-only; everything imported arrives as proposals a licensed clinician reviews, and nothing reaches the chart unreviewed. Built to Epic's SMART Backend Services requirements (a per-connection JWKS URL) but not yet verified against an Epic system: it has been tested only against ArkCloud's own synthetic Epic-style test profile. See Outside records.

EHR sync connector for Epic (not usable)

lib/ehr/connectors/epic-connector.ts reads Patient, Encounter, Practitioner, Appointment and Coverage, with Bundle pagination. lib/ehr/connector-registry.ts registers it, but the EHR connection API (/api/ehr) answers every test, sync or lookup with 501 "EHR sync is not available", so the code never runs for a user.

SMART Backend Services authentication

Hospital record import signs a short-lived JWT client assertion (RS384 or ES384) with a private key and exchanges it at the hospital's token endpoint (lib/ehr/smart-backend-auth.ts). It never sends a client secret. It has run only against the public SMART Health IT reference sandbox (synthetic data, 2026-10-03), never against a real Epic token endpoint.

Electronic referrals (Rehab)

A separate Rehab feature receives FHIR R4 referrals from a referring EHR over SMART Backend Services and is configured by a Rehab administrator. It has been contract-tested against a simulated partner only; no Epic site has exchanged a referral with it. See FHIR.

Inbound EHR webhook receiver

/api/ehr/webhooks?connectionId=... verifies an HMAC-SHA256 signature against a per-connection secret and resolves the tenant. No screen sets that secret, so nothing can use it today.

Verification: record import is tested against ArkCloud's own synthetic Epic-style test profile only. No test exercises any Epic connection against an Epic system.

Not built

Verification against any Epic system: no Epic organisation has registered or activated ArkCloud's client
Patient, coverage or encounter sync from Epic into billing (the 6-hourly EHR sync job does not use record import connections)
Retrieval of images (DICOM or DICOMweb): imaging reports and study metadata only; images stay at the source
Write-back of payments or balances to Epic (lib/ehr/write-back-service.ts throws "not yet implemented")
SMART on FHIR launch from Hyperspace, single sign-on from Epic, or in-basket messages
MyChart integration of any kind (not implemented)
An App Orchard / Epic Showroom listing or any Epic certification
HL7 v2 feeds from Epic: there is no MLLP listener (see HL7 v2 messaging)

What it would take

This is a list of gaps, not a delivery commitment. Before hospital record import could run against a real Epic system:

  • Registration of ArkCloud's backend app with Epic, and a client id.
  • The hospital activating ArkCloud's client for its environment and agreeing to release records to the practice, with the agreements between the organisations (and a BAA where required) in place.
  • A run against an Epic sandbox or system, recorded as evidence.

Before the EHR sync API could stop answering 501, the product would need at least:

  • A sync job that loads the registered connectors (the scheduled EHR sync does not use them).
  • Access tokens actually obtained by the sync FHIR client, and write-back implemented.
  • Field mapping, error handling and tests against an Epic sandbox.

Exchanging data today

Outside records (Rehab)

Staff upload records a hospital sent them - a FHIR R4 bundle, a C-CDA document or a PDF - and a clinician reviews what is proposed for the chart. A hospital record import connection can also be configured, once the hospital has activated ArkCloud's client.

Outside records

Claims and remittance

Claims go out and 999, 277CA and 835 files come back through your clearinghouse's SFTP mailbox, independent of any EHR.

Clearinghouse

File and CSV imports

An administrator can create Amazon S3, SFTP or manual-upload connections under Settings → Integrations → Connections for extracts produced by your Epic team. Connections can be set up and tested, but file pipelines are not available: inbound files are not imported into ArkCloud and exports are not generated or delivered.

Custom integrations

Implementation work

For anything else, contact support. Any Epic-specific work would be scoped as a project; there is no packaged Epic integration to switch on.

Contact support

Related Topics

HL7 v2 messagingFHIREMR Integration OverviewCerner Integration