SMART on FHIR: what's new, what's next?
summary
Covers what SMART App Launch 2.0 actually adds: PKCE required to stop intercepted codes, asymmetric client authentication via JWS public keys so apps can rotate keys and reuse them across EHRs, and granular scopes with FHIR search params that map CRUD and filter observations by category. Also documents token introspection for multi-server ecosystems, describes Patient Access Brands for searchable endpoint branding, and a small SMART App State API (≈256KB) for app-specific config; V1 remains the regulated baseline.
AI-written summary · about
chapters (11)
- 0:00Introduction and overview
- 1:02SMART App Launch 2.0 overview
- 2:08Improved scopes in SMART 2.0
- 7:04Asymmetric client authentication
- 12:21PKCE security enhancements
- 19:47Token introspection explained
- 22:59Upcoming SMART projects
- 26:50Patient access brands project
- 29:18SMART App State API
- 34:16EHR adoption expectations
- 44:31Q&A session
