Microsoft FHIR Server implementation
summary
Microsoft adds SMART on FHIR support to its Azure FHIR service to meet 21st Century Cures certification by passing Inferno tests: it uses Azure API Management to rewrite scopes (dot-for-slash) and inject FHIR-user context, puts a FHIR user claim in the access token so the server enforces patient-scoped queries, builds an expression-tree filter layer so data-layer queries return only allowed resources, implements ES384 signing for bulk-export tokens to match Inferno, and adds dataAbsentReason population (with measurable perf cost); samples and scripts live on GitHub and the managed service will absorb these features.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 1:02Overview of US Core and G10 requirements
- 3:08Solution architecture and components
- 5:15Azure AD limitations with SMART on FHIR
- 7:21Fine-grained access control implementation
- 10:10Scope syntax translation challenges
- 11:13Bulk data export encryption issues
- 13:01Handling missing data requirements
- 14:27Documentation and open-source samples
- 15:27Q&A session
related talks
16mExtending your FHIR Server with Proxy Services
45mSMART on FHIR: Introduction
41mSMART on FHIR
37mSMART on FHIR
34mFHIR Projects
45mSMART on FHIR: what's new, what's next?
01h 48mSMART V1 +V2 Granular Controls
01h 04mApisecure, 14 & 15 March 2023 - Grahame Grieve, Principal at Health Intersections Pty Ltd.
