EMR Integration
ArkCloud does not synchronise data with any EMR or EHR system today: every EHR sync operation answers "EHR sync is not available". Two Rehab features can be configured by a Rehab administrator: read-only hospital record import over FHIR R4, and the FHIR referral exchange. Neither has been verified with an EHR vendor; record import has run only against a public reference sandbox with synthetic data, and the referral exchange only against a simulated partner. This page summarises the state of each system and how practices exchange data with ArkCloud now.
| Capability | Status | What that means here |
|---|---|---|
| Two-way EHR synchronisation (Epic, Oracle Health, MEDITECH) | Not available | ArkCloud does not synchronise with, or write back to, a hospital EHR, and has no MyChart integration. Every EHR sync operation is refused. |
| Importing records from a hospital system (FHIR) | Not independently verified | Built: a read-only import from a hospital's FHIR R4 service into proposals a clinician reviews. Each hospital must register ArkCloud first; it has been tested only against ArkCloud's own test profiles and a public test server, never against an Epic or Oracle Health system.Requires: A connection your Rehab administrator sets up with each hospital. |
| Electronic referrals from a referring EHR (FHIR) | Not independently verified | Built: referrals received over FHIR R4 from a referring organisation's system arrive on Rehab's Electronic referrals screen for a person to review, and status updates go back to the referrer. Each organisation sets up its own connection, and it has never been proven with a real referring partner.Requires: A referral-exchange connection your Rehab administrator sets up with the referring organisation. |
| HL7 v2 interface (ADT, SIU, DFT feeds) | Not available | There is no HL7 interface: no listener, no inbound feed and nothing sent. A message library exists that an administrator can use to check or build a single message. |
State by system
Epic
Read-only hospital record import with an Epic profile, built to Epic's SMART Backend Services requirements and tested only against ArkCloud's own synthetic Epic-style test profile; not yet verified against an Epic system. EHR sync answers "EHR sync is not available".
Cerner / Oracle Health
Read-only hospital record import with an Oracle Health profile, tested only against ArkCloud's own synthetic Oracle-style test profile; not yet verified against an Oracle Health system. EHR sync answers "EHR sync is not available".
Meditech
Planned. A MEDITECH hospital record import connection can be recorded, but where the hospital offers only SMART app launch it is shown as unsupported; nothing has been tested.
Hospital record import (Rehab)
A Rehab administrator configures one FHIR R4 connection per hospital (SMART Backend Services) and staff import a patient's records read-only, as proposals a licensed clinician reviews. Run only against the public SMART Health IT reference sandbox with synthetic data; each hospital must activate ArkCloud's client before a real connection exists.
HL7 v2
A message parser and generator library an administrator can call through the HL7 API. No MLLP listener or sender.
FHIR
A FHIR R4 read facade over ArkCloud's own data for signed-in users. Not callable by an external system.
FHIR referral exchange (Rehab)
Receives FHIR R4 referrals from a referring EHR once a Rehab administrator configures the partner. Contract-tested against a simulated partner only; no partner connection has been proven.
Not built
Exchanging data today
Outside records (Rehab)
Staff upload records a hospital sent them - a FHIR R4 bundle, a C-CDA document or a PDF - or import them over a configured hospital connection, and a clinician reviews what is proposed for the chart.
Outside recordsClaims and remittance
Claims go out and 999, 277CA and 835 files come back through your clearinghouse's SFTP mailbox, independent of any EMR.
ClearinghouseFile and CSV imports
An administrator can create Amazon S3, SFTP or manual-upload connections under Settings → Integrations → Connections for extracts from the EMR. 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 integrationsImplementation work
For anything else, contact support. EMR-specific work is scoped as a project; there is no packaged EMR integration to switch on.
Contact support