SMART on FHIR Server Cheat Sheet - onc-healthit/inferno-community GitHub Wiki

EHR FHIR Support

SMART-on-FHIR

Allscripts

Registration optional (required for authorization) | OAuth Support | Public and Confidential Clients

Signing Up

Developer Signup Documentation

Sandboxes Available

SMART Sandbox

No registration required | OAuth support

Customize Sandbox

Highlights

  • SMART App Server
    • Standards Supported
      • Supports DSTU2 and STU3
    • Launch Types
      • Provider EHR Launch
      • Provider Standalone Launch
      • Patient Standalone Launch
      • Backend Service
      • CDS Hooks Service

Sandboxes Available

Provider EHR Launch

  1. Select Provider EHR Launch as the Launch Type
  2. Select a patient
  3. Provide your SMART-on-FHIR Launch URI in the launch pane
  4. Select Launch

Provider Standalone Launch

Patient Standalone Launch

Cerner

Registration optional (required for authorization) | OAuth Support

Open Sandbox

Secure Sandbox

Creating an Account

Cerner Account Creation Page

Registering an App

Cerner Homepage Image Cerner Register Cerner Patient Scope

Epic

Registration Optional (required for authorization) | OAuth Support

  • Sandbox web services are unsecured
  • Can register for ID and secret to call secured services

Endpoints

You can also test out their FHIR API in the browser.

Creating an Account

Users can log in via OpenID from a number of account providers including Google, Yahoo, AOL. A credit card is required for identity verification. Epic Credit Card Charge Image

Adding an application

Once logged in a user can create an application by filling out a form Epic Add an App Image Epic Add an App Image 2 Epic Add an App Image 3

Submissions are not instantly activated and must be registered and approved in a multistep process.

HSPC

Registration Required | OAuth Support | Dynamic Registration | Manual Registration

Creating an account

HSPC Login URL

Creating a sandbox

HSPC Create Sandbox

Sandbox Homepage

HSPC Sandbox Homepage

Notes

  • The SMART Sandbox hyperlink is http as the https site does not deliver the static files :(

  • client_id and client_secrets are not validated by the server. Options are present for simulating authentication errors.

  • Although the endpoints listed on the site indicate https the 'iss' param given is http and does not match (works if you use http)

  • Should we be testing Provider Standalone Launch Sequence?