{ "package-id" : "hl7.fhir.uv.smart-app-launch", "title" : "Smart App Launch Implementation Guide", "canonical" : "http://hl7.org/fhir/smart-app-launch", "category" : "EHR Access", "list" : [ { "version" : "current", "date" : "n/a", "desc" : "Continuous Integration Build (latest in version control)", "path" : "http://build.fhir.org/ig/HL7/smart-app-launch", "status" : "ci-build" }, { "version" : "2.2.0", "path" : "http://hl7.org/fhir/smart-app-launch/STU2.2", "status" : "trial-use", "sequence" : "STU 2.2", "fhirversion" : "4.0.1", "date" : "2024-04-30", "current" : true, "desc" : "Surface branding information for endpoints and organizations. Enhance fhirContext to support canonical and identifier references." }, { "version" : "2.2.0-ballot", "path" : "http://hl7.org/fhir/smart-app-launch/2024Jan", "status" : "ballot", "sequence" : "STU 2.2", "fhirversion" : "4.0.1", "date" : "2023-12-19", "desc" : "Surface branding information for endpoints and organizations. Enhance fhirContext to support canonical and identifier references." }, { "version" : "2.1.0", "path" : "http://hl7.org/fhir/smart-app-launch/STU2.1", "status" : "trial-use", "sequence" : "STU 2.1", "fhirversion" : "4.0.1", "date" : "2023-04-18", "desc" : "Allow for more detailed fhirContext when launching apps. Allow PractitionerRole for fhirUser Document absolute URL requirement for smart-configuration links. Remove note on dynamic ports in redirect_uri. Add experimental support for SMART App State Persistence. Add Task profiles for describing app launch." }, { "version" : "2.1.0-ballot", "date" : "2022-12-04", "path" : "http://hl7.org/fhir/smart-app-launch/2023Jan", "status" : "draft", "sequence" : "STU 2.1", "fhirversion" : "4.0.1", "desc" : "Allow for more detailed fhirContext when launching apps. Allow PractitionerRole for fhirUser Document absolute URL requirement for smart-configuration links. Remove note on dynamic ports in redirect_uri. Add experimental support for SMART App State Persistence. Add Task profiles for describing app launch." }, { "version" : "2.0.0", "descmd" : "STU 2: The SMART App Launch 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.", "desc" : "STU 2: Revisions based on community feedback after wide adoption - see below for further details", "path" : "http://hl7.org/fhir/smart-app-launch/STU2", "sequence" : "STU 2", "fhirversion" : "4.0.1", "status" : "trial-use", "date" : "2021-11-26" }, { "version" : "1.1.0", "descmd" : "STU 2 Ballot #1: The SMART App Launch 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.` \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- Clarification on launch context scopes\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", "path" : "http://hl7.org/fhir/smart-app-launch/2021May", "sequence" : "STU 2", "fhirversion" : "4.0.1", "status" : "ballot", "date" : "2021-04-16" }, { "version" : "1.0.0", "fhirversion" : "3.0.1", "date" : "2018-11-13", "desc" : "Release 1.0.0 (STU)", "path" : "http://hl7.org/fhir/smart-app-launch/1.0.0", "status" : "trial-use", "sequence" : "STU 1" }, { "version" : "0.8.0", "fhirversion" : "3.0.1", "date" : "2017-07-29", "desc" : "STU Ballot", "path" : "http://hl7.org/fhir/smart-app-launch/0.8.0", "status" : "ballot", "sequence" : "STU 1" } ] }