5 min read

Cerner Integration

ArkCloud has not yet exchanged data with any Oracle Health (Cerner) system. A Rehab administrator can configure a read-only hospital record import connection with an Oracle Health profile, not yet verified against an Oracle Health system; the hospital must provision 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 Cerner exchange data with ArkCloud now.

What exists in the code

Hospital record import with an Oracle Health 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 ORACLE_HEALTH 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. Not yet verified against an Oracle Health system: it has been tested only against ArkCloud's own synthetic Oracle-style test profile, and the hospital must provision ArkCloud's client first. See Outside records.

EHR sync connector for Oracle Health (not usable)

lib/ehr/connectors/cerner-connector.ts defines reads for Patient, Encounter, Practitioner, Appointment, Coverage, Account and ChargeItem. 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.

Authentication

Hospital record import signs a short-lived JWT client assertion (SMART Backend Services, lib/ehr/smart-backend-auth.ts); it has run only against the public SMART Health IT reference sandbox (synthetic data, 2026-10-03), never against an Oracle Health tenant. The unused EHR sync connector requests a token with the OAuth 2.0 client_credentials grant and has never been exercised either.

Inbound EHR webhook receiver

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

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

Not built

Verification against any Oracle Health system: no Oracle Health organisation has provisioned ArkCloud's client

Patient, coverage, encounter or charge sync from Cerner into billing (the 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, balances or statements to Cerner (lib/ehr/write-back-service.ts throws "not yet implemented")

SMART on FHIR launch from PowerChart

FHIR DSTU2 support

HL7 v2 feeds from Cerner: there is no MLLP listener (see HL7 v2 messaging)

CCL scripting or scheduled CCL extracts

Any Soarian adapter

What it would take

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

A system account registered in the Oracle Health developer console.
The hospital provisioning 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 Oracle Health 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).
Authentication verified against Oracle Health's current authorisation requirements, and write-back implemented.
Field mapping, error handling and tests against an Oracle Health 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 provisioned 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 from Cerner. 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 Cerner-specific work would be scoped as a project; there is no packaged Cerner integration to switch on.

Contact support

HL7 v2 messaging FHIR EMR Integration Epic Integration