Access Token Response "access_token": "xyz...", "patient": "123", "fhirContext": ["DiagnosticReport/123", "Organization/789"] --> array of relative resource References to any resource type other than "Patient" or "Encounter". Move "Appointment" out of the table of launch context (can cover it via this new fhirContext mechanism) Would we deprecate the more specific params like "patient"? No, would keep these, and would not deprecate or duplicate them in the fhirContext array. (i.e., we'd prohibit Patient and Encounter). It is not prohibited to have more than one reference to a given type of resource. Could (and how would) a client request context like a DiagnosticReport? Yes, by asking for a scope like "launch/diagnosticreport" or "launch/organization" (i.e., lowercased FHIR resource types ). In spec, include rationale for separating out these properties (i.e. the aim is to allow flexibility; maintain backwards compatibility; keep a predictable JSON structure)