⌘K
All guides
User Journeys· 15 min

EHR Vendor: SMART on FHIR Integration

Integrate an EHR with SMART on FHIR: patient and provider launch, bulk export, and TEFCA connectivity.

  1. 1

    Discover SMART configuration

    Fetch the SMART discovery document to confirm supported capabilities: EHR launch, standalone launch, and confidential/public client types.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s https://api.parkerapex.com/fhir/R4/.well"text-cyan-300">-known/smart"text-cyan-300">-configuration | "text">-amber-300 font">-semibold">jq '.capabilities'
  2. 2

    Register your OAuth client

    Register a SMART client with your redirect URIs and requested scopes. Patient-facing apps use patient/*.read scopes; provider-facing apps use user/*.read plus launch context scopes.

    bash
    https://developers.parkerapex.com/tokens
  3. 3

    Test patient and provider launch

    Use the SMART Launcher to simulate EHR launch (launch + iss parameters) and standalone launch against sandbox data before pointing your app at production.

    bash
    https://developers.parkerapex.com/smart"text-cyan-300">-launcher
  4. 4

    Implement bulk export

    Kick off system-level $export for population sync, poll the status endpoint, then download NDJSON files. Track long-running jobs in the Bulk Export Tracker.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s "https://api.parkerapex.com/fhir/R4/\$export" \
  "text-cyan-300">-H "Authorization: Bearer YOUR_TOKEN" \
  "text-cyan-300">-H "Accept: application/fhir+json" "text-cyan-300">-H "Prefer: respond">-async" "text-cyan-300">-D -
  5. 5

    Connect to TEFCA exchange

    For network-level document query and retrieve, follow the TEFCA/KONZA integration path: purpose-of-use enforcement, XCA retrieve, and exchange logging are handled by the gateway.

    bash
    https://developers.parkerapex.com/tefca

Related