FHIR Documentation

Complete reference for eClinicalWorks SMART on FHIR integration

Current Blocker

Practice activation is the current blocker for going live. See the Practice Activation guide for the required steps to enable your app in a practice's eCW instance.

Key Facts

RS384 Only

Signing algorithm

PKCE Required

S256 challenge

250 calls/min

Per practice code

90-day refresh

Token lifetime

1h / 5m tokens

Standalone / Backend

FHIR R4

US Core 3.1.1 + 6.1.0

Authentication & Authorization

Standalone Launch
OAuth 2.0 authorization code flow with PKCE for browser-based apps launched outside the EHR.
Backend Services
System-to-system auth using signed JWTs for bulk data export and automated workflows.
Practice Activation
Step-by-step guide to getting a practice to enable your app in their eCW instance.
Scopes
Complete reference for SMART on FHIR scopes — launch, identity, patient, user, and system.

API Resources & Mapping

55+ resources
Read APIs
34 USCDI v1 + 55 USCDI v3 FHIR resources — Patient, Encounter, Observation, and more.
20 operations
Write APIs
Create, Update, and Delete operations for Patient, Coverage, Encounters, and more. Requires contracted access.
USCDI Mapping
How USCDI v1 and v3 data classes map to FHIR R4 resources, including SDOH and reproductive health.
FHIR Endpoints
Base URL structure, discovery endpoints, per-practice codes, and rate limiting policies.