Intents are quite open-ended and have not been not widely tested. This makes it hard for us to determine that they should be more flexible. Per https://build.fhir.org/ig/HL7/smart-app-launch/scopes-and-launch-context.html#launch-intent , > Note that SMART makes no effort to standardize intent values. Intents simply provide a mechanism for tighter custom integration between an app and a SMART EHR. The meaning of intent values must be negotiated between the app and the EHR. Note that even Android OS manages with a "start activity" API that includes only a single intent ( https://developer.android.com/reference/android/content/Context#startActivity(android.content.Intent ). If some concept of "multiple intents" is required, implementers today can try: defining "combined intents" using space-separated intents in a single string using extension parameters in the access token context (e.g., "__intentArray") We may consider further standardization based on real-world feedback.