What is a launch context?

...

• SMART on FHIR launch: see http://docs.smarthealthit.org/authorization/
• HSPC Reference API: see HSPC Logica Reference API
• HSPC Reference Auth: see HSPC Logica Reference Auth
• HSPC Sandbox Manager: see HSPC FHIR Sandbox Manager
• launching system: A system that issues a SMART on FHIR launch request to a SMART on FHIR app, typically an EHR or EHR simulator.

...

{"client_id":"bilirubin_chart","parameters":{"patient":"BILIBABY","need_patient_banner":false}}

• Note, at this time, client_id is not required.  Only 'parameters' is required, and at minimum, an empty object.

• 
  

  Code Block
  title Minimum Launch Context
  {"parameters":{}}

  
  

Step 2: Registering the launch context

The launch context is registered with the HSPC Reference API server by sending an HTTP POST to the /_services/smart/Launch endpoint.  The request must contain an access token for the HSPC Reference API server.  The launching system should obtain this token as part of the preconditions, for example, through a SMART on FHIR launch flow.

HTTP POST
Authorization:Bearer ...
Payload: {"client_id":"bilirubin_chart","parameters":{"patient":"BILIBABY","need_patient_banner":false}}

Step 3: Launch context is synchronized

The launch context is enriched with a launch_id that is the key to the launch context given to the downstream app.  The launch context must be synchronized between the HSPC Reference API server and the HSPC Reference Auth server.  This synchronization allows both servers to check the launch context for various APIs.  For example, the HSPC Reference Auth server can determine if a patient context has been established when issueing a patient-scope access token, and the HSPC Reference API server can remove results from a query that are not for the patient in context.

Step 4: Launch context is returned

{"launch_id":"GNpcsR","created_at":"Mon Nov 06 23:31:53 UTC 2017","created_by":"...","parameters":{"patient":"BILIBABY","need_patient_banner":false},"username":"none"}

...