NewERA reconciliation now reports parsed claims, denied exposure, and data-quality issues.
Epic FHIR integration

Epic integration built as a control plane — not a connection claim.

COMING SOON — CONNECTOR FOUNDATION BUILT, NOT YET CONNECTED

DenialOS implements the Epic connector foundation: FHIR R4 SMART Backend Services signing, token-exchange primitives, public JWKS publication, contract-scoped adapter routing, and non-executing write-back planning. Live connectivity to an Epic tenant remains unproven until your app registration, credentials, and UAT evidence exist.

Request the activation checklist See denial management
Implemented today

The parts that must be correct before clinical data is read.

Reading PHI out of an EHR is the easy part to demo and the hard part to govern. These primitives are implemented and covered by the platform test suite.

FHIR R4 retrieval mapping

Adapter-pack validation and canonical mapping from FHIR R4 resources into the DenialOS canonical model, with read-only scope by construction.

SMART Backend Services

Signed JWT client-assertion construction, token-exchange primitives, and public JWKS publication. No user redirect, no interactive OAuth.

Contract-scoped adapter routing

Connector profiles bind a contract to an adapter. Routing, provenance, and source hashing are enforced at the boundary rather than in each integration.

Checkpoint and reconciliation

Retrieval is checkpointed and reconciled so a re-run is replay-safe and a partial pull is visible rather than silently accepted.

Document-exchange safety checks

Attachment and document exchange passes through safety checks before anything is admitted to a case.

Non-executing write-back planning

Write-back is planned and modelled only. Nothing is written to an Epic tenant, and no write capability is claimed.

Activation path

What has to be supplied from your side.

Every step below requires Epic-side or customer-side evidence. DenialOS cannot self-certify any of them, which is exactly why the connection is marked unvalidated until they are complete.

Register a SMART Backend Services application in your Epic environment and record the required FHIR R4 scopes
Provision credentials and JWKS configuration against the DenialOS connector profile
Run sandbox retrieval against a provisioned tenant and retain the evidence
Complete customer UAT on retrieval mapping and case attachment
Enable the connection only after the production gate is satisfied
Explicitly not claimed

No production Epic integration. No live Epic connectivity. No write-back executed against Epic. No HIPAA or SOC 2 certification. No autonomous payer calling. No recovery guarantee.

Status disclosure

DenialOS separates implemented runtime behaviour from sandbox validation, customer UAT, and production enablement. This page does not upgrade the integration beyond the evidence the platform actually holds.

Governed by a public capability ledger

Integration status is recorded in a machine-readable capability ledger and enforced by an automated public-site verification gate, so a marketing page cannot quietly outrun the evidence.

Engineering evidence

Verified by the platform suite, not by a slide.

The connector foundation is exercised by the same suite that gates the rest of the platform: 60 files / 222 tests in the standard suite and 98 files / 346 tests in the isolated database suite, plus TypeScript checks, a clean migration replay, schema verification, and a production build. Those numbers describe tested behaviour in an isolated environment — they are not a claim of production activation.