{
"version": "2.0.0",
"date": "2021-10-30",
"desc": "STU 2: The SMART on FHIR v1 IG has been widely adopted for clinician- and patient-facing app integration into EHRs and other FHIR data systems. Based on community feedback, the [Argonaut Project](https://confluence.hl7.org/display/AP/Argonaut+Project+Home) has undertaken a 2020 effort to revise and improve the SMART App Launch IG. A key area of focus in adding support for \"granular permissions,\" e.g. to provide access to resources at the category level in addition to the type level. This would allow apps to request narrower access, like \"all vital signs\" rather than \"all observations.\"\n\nEnhancements and Clarifications to the SMART App Launch specification (see Jira change request [FHIR-30578](https://jira.hl7.org/browse/FHIR-30578) for a log of changes included in the ballot):\n\n- Clarification on launch context scope\n- New scope syntax for granular permissions\n- `POST`-based authorization\n- Addition of PKCE to authorization requirements\n- Profile token introspection\n- Guidance for communicating permissions to end users\n- Update discovery properties to support these changes.\n\nSeveral new pages have been added to this version of SMART App Launch Implementation Guide. A new *Overview* page has been been added to introduce the reader to the guide. The *Backend Services* pages has been moved from [FHIR Bulk Data Access](http://hl7.org/fhir/uv/bulkdata/) to consolidate the patterns for client authorization. There are new pages to define two patterns for client authentication -*Asymmetric (public key)* and *Symmetric (shared secret)*. The *Token Introspection* page documents how to support token introspection and there is and informative *Best Practices* page. Finally, the *Launch and Authorization* page has been extensively rewritten to make it clearer, and more reader friendly.",
"path": "http://hl7.org/fhir/smart-app-launch/STU2",
"sequence": "STU 2",
"fhirversion": "4.0.1",
"status": "trial-use"
},
Healthedata1
commented
3 years ago