Provider EHR Workspace

SMART on FHIR — EHR launch

Launch this app the way a real EHR would, from the reference SMART App Launcher — the same open-source launcher Epic and Cerner test against.

Click Open SMART App Launcher below — this app’s launch URL is already filled in, nothing to type
Pick any provider and any patient on the launcher’s own screens
Click Launch — this app loads embedded inside the launcher’s page (its “simulate launch within the EHR UI” mode), the way a real EHR would iframe a launched app rather than navigating away

Open SMART App Launcher →

The embedded app shows a banner naming the launched patient. Launched data is displayed for the current session only, never persisted. For real Epic sandbox identities via SMART Backend Services instead, click any Epic patient in the scenarios below.

Patient scenarios

Epic sandbox (real FHIR reads via SMART Backend Services)

Order Entry: Jane Doe

Patient (pat-8849-jane-doe) · Coverage (cov-comm-ppo-bcbsil) · NPI 1234567890

Plan type

Preset orders

Or type any CPT / HCPCS / J-code

Debug: simulate hard-stop trigger (contraindicated/non-covered scenario)Debug: simulate denial on PAS submit (structured reason codes, CMS-0057-F, 45 CFR 156.223)Expedited request (urgent). Selects the expedited decision clock.Route PAS through a clearinghouse that checks conformance and PAS version first.

Epic Backend Services (SMART client-confidential-asymmetric)

In production, DTR pre-population pulls clinical context from the provider’s EHR. Clicking a name under “Epic sandbox” above performs that call for real against Epic’s public FHIR sandbox, using SMART Backend Services (RS384-signed client assertion, published JWKS).

Click an Epic sandbox patient above to fetch their real record here.