SMART App Launch
2.2.0 - STU 2.2 International flag

This page is part of the Smart App Launch Implementation Guide (v2.2.0: STU 2.2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Table of Contents

.. 0 Table of Contents
... 1 Overview
... 2 Apps
.... 2.1 App Launch: Launch and Authorization
.... 2.2 App Launch: Scopes and Launch Context
.... 2.3 Persisting App State (Experimental)
.... 2.4 Task profile for requesting SMART launch (Experimental)
... 3 Backend Services
... 4 Client Authentication
.... 4.1 Client Authentication: Asymmetric (public key)
.... 4.2 Client Authentication: Symmetric (shared secret)
... 5 Token Introspection
... 6 Conformance
... 7 Best Practices
... 8 User-access Brands and Endpoints
.... 8.1 User-access Brand Examples
... 9 Examples
.... 9.1 Example App Launch for Public Client
.... 9.2 Example App Launch for Asymmetric Client Auth
.... 9.3 Example App Launch for Symmetric Client Auth
.... 9.4 Example Backend Services Flow
.... 9.5 Example Id Token
.... 9.6 Example JWS generation for Asymmetric Client Auth
... 10 References
... 11 Artifacts Summary
.... 11.1 User Access Brands Bundle Profile
.... 11.2 User Access Brand (Organization) Profile
.... 11.3 User Access Endpoint Profile
.... 11.4 User Access Category Value Set
.... 11.5 Lab with Locations Nationwide
.... 11.6 Regional Health System With Independently Branded Affiliates
.... 11.7 Different EHRs for different sub-populations displayed in a unified card
.... 11.8 Two co-equal brands
.... 11.9 SMART App State
.... 11.10 App State Server CapabilityStatement
.... 11.11 Example App State
.... 11.12 TaskEhrLaunch
.... 11.13 TaskStandaloneLaunch
.... 11.14 SMART on FHIR terminology.
.... 11.15 Codes for tasks to application launches
.... 11.16 Launch Types for tasks to application launches
.... 11.17 Example Task for Standalone Launch
.... 11.18 Example Task for EHR Launch