FHIR Intermediate Course SMART-ON-FHIR Simulators

• A user has established an EHR session and wants to launch an specialized SMART-ON-FHIR compatible app
• The URLs of all approved apps have been previously registered with the EHR authorization server.
• Could be a single-patient app (context: a patient record), or a user-level app (context: multiple patients - pop. health, appointments) an appointment manager or a population dashboard).
• The EHR initiates a “launch sequence” by opening a new simulator instance (or iframe) pointing to the app’s registered launch URL
• Some context (patient,user,encounter) to the EHR is passed along to the app as part of the launch URL.
• The app later will include this context handle as a request parameter when it requests authorization to access resources.

Our app just show the context and calculates the patient average weight based on the existing measures from the FHIR server

• A a provider selects an app from outside the EHR, - example: tapping an app icon on a mobile phone home screen.
• This app will launch from its registered URL without a launch id.
• The app discovers the EHR authorization server’s OAuth authorize and token endpoint URLs by querying their .well-known/smart-configuration.json file.
• The app obtains launch context and request authorization to access FHIR resources
• The app then can declare its launch context requirements by adding specific scopes to the request it sends to the EHR’s authorization server.
• The authorize endpoint will acquire the context the app needs and make it available.

This app displays a list of the patient's allergies - the user will select it

• A patient selects an app from a PHR portal or Mobile Phone
• This app will launch from its registered URL without a launch id.
• The app discovers the authorization server’s OAuth authorize and token endpoint URLs by querying their .well-known/smart-configuration.json file.
• The app obtains launch context and request authorization to access FHIR resources
• The app then can declare its launch context requirements by adding specific scopes to the request it sends to the EHR’s authorization server.
• The authorize endpoint will acquire the context the app needs and make it available.
• Remember that this mode does not require a provider context, just the patient

This app displays a list of the patient's allergies - the patient is logged in

• A patient selects an app from a PHR portal or Mobile Phone
• This app will launch from its registered URL without a launch id.
• The app discovers the authorization server’s OAuth authorize and token endpoint URLs by querying their .well-known/smart-configuration.json file.
• The app obtains launch context and request authorization to access FHIR resources
• The app then can declare its launch context requirements by adding specific scopes to the request it sends to the EHR’s authorization server.
• The authorize endpoint will acquire the context the app needs and make it available.
• Remember that this mode does not require a provider context, just the patient

This app displays a list of the patient's medication - the patient is logged in