Based on zulip discussion , we should improve clarity  / readability By separate out an "Overview" page from the main body of the App Launch specification. We'd include background, use cases, descriptions of the main actors, and the high-level sequence diagrams on this overview page, and leave the detailed protocol documentation on the remaining pages. Surface the " major steps " and actors  of the authz process at the top of the detail page, including an explicit step for discover. For example (still to be agreed upon in a subsequent FHIR-I call) we'd call out steps like: App registers to obtain a client id App discovers a server's authorization capabilities App requests authorization (EHR or Standalone Launch) EHR evaluates the request, prompting end-user input App exchanges auth code for a token App uses the token to access the FHIR API App uses a refresh token — FHIR-I Discussion Vassil notes: IHE uses "Transactions" as a higher level unit of specification, encapsulating (potentially) multiple messages Bas: we can explain steps like "EHR Launch" and "Standalone Launch" in terms of the actors involved Next week: Bas to bring a specific set of "major steps" to vote on Gino: As a meta point, we may want to avoid setting conventions "by proxy" (e.g., by pointing to conventions as established by IHE). Bas: Agreed; this is what I'm focused on specific examples here, not just "rewrite to match IHE".