◈ CoverageCalc

Insurance coverage

Example PPO plan · Illustrative

An EOB's patient responsibility, a pre-adjudication estimate, and a provider's balance due are different. Actual plan benefits and accumulators require verified payer information.

Connect Epic MyChart

Colin’s records must be connected through an authorized patient or valid parent/guardian proxy account. An Epic SMART on FHIR registration and a supported hospital endpoint are required.

Production redirect URI: https://coveragecalc.com/callback.html. Exact URI must be registered with Epic. The actual authorization workflow should use a vetted SMART client library, PKCE, state validation and a trusted backend before handling real data.

Required integration steps

1. Register CoverageCalc in Epic's developer program and configure scopes and redirect URI.
2. Identify the correct healthcare organization's FHIR base URL and SMART discovery metadata.
3. Implement OAuth authorization code with PKCE and secure token handling.
4. Fetch authorized Patient, Encounter, Condition, Procedure, Coverage and available EOB/Claim/DocumentReference resources.
5. Ingest actual itemized bills separately when billing details are absent from FHIR.
6. Enforce patient/proxy permissions for Colin and implement secure server-side processing.

Epic FHIR data lineage

Based on your uploaded Epic DocumentReference.Read (Clinical Notes) R4 specification. Source-supported fields are separated from pending billing and payer mappings.

Clinical note evidence preview

Demonstration of how a linked note will appear after an authorized Epic fetch. The example below is fictional and is not retrieved from MyChart.