SMART on FHIR Server Cheat Sheet

SMART-on-FHIR

SMART Sandbox

No registration required | OAuth support

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

• Open Server
  • DSTU2: https://r2.smarthealthit.org
  • STU3: https://r3.smarthealthit.org
• Protected
  • DSTU2: https://launch.smarthealthit.org/v/r2/fhir
  • STU3: https://launch.smarthealthit.org/v/r3/fhir

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

• Endpoint: https://fhir-open.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/:resource[?:parameters]
• Read-only resources

Secure Sandbox

• Available with registration

• readable and writable resources

• Provider Endpoint: https://fhir-ehr.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/:resource[?:parameters]

• Patient: https://fhir-myrecord.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/:resource[?:parameters]

Creating an Account

Epic

Registration Optional (required for authorization) | OAuth Support

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

Endpoints

• Provides a List of Open and Production Endpoints

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.

Adding an application

Once logged in a user can create an application by filling out a form

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

HSPC

Registration Required | OAuth Support | Dyanmic Registration | Manual Registration

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?