Revised the section to be clearer by specifying what is sent in the EHR's initial call to the app versus what is later returned in the EHR authorization server's token response:   When the clinic staff takes action on the work queue item, the EHR… launches the information requester's SMART App, sending a launch context parameter reflecting: the `.id` of the Patient it received in the `.for` element of the Task resource--which references the Data Source system's Patient resource the Task.identifier value--which the SMART app will use to present the right questions for the patient and medication. This value is later returned to the app in the access token response from the EHR authorization server For example, the EHR redirects to: https://my-pharmacy-smart-app.com? launch=123& iss=htttp://my-ehr.com/fhir responds to the app's authorization request in the launch sequence with an OAuth 2.0 access token response that includes the Patient.id and appContext values. For example: {    access_token:"secret-token-xyz",    expires-in:"3600",    patient:"specialty-rx-patient-1",    appContext:"launch-context-id-01345005",    ... } sets the Task `status` to `in-progress`