You’re receiving this email because you’re currently using SMART on FHIR proxy feature in Azure Health Data Services, FHIR service.
SMART on FHIR proxy is retiring on 21 September 2026, transition to the SMART on FHIR (Enhanced) which uses Azure Health Data and AI OSS samples by that date. After 21 September 2026, applications relying on SMART on FHIR proxy will report errors in accessing the FHIR service.
SMART on FHIR (Enhanced) provides added capabilities compared to SMART on FHIR proxy and can be considered to meet requirements of SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
The following table lists the differences between SMART on FHIR proxy and SMART on FHIR (Enhanced).
|
Capability |
SMART on FHIR (Enhanced) |
SMART on FHIR proxy |
|
Supports Standalone Launch |
Yes |
No |
|
Supports EHR Launch |
Yes |
Yes |
|
Supports scope restrictions |
Yes |
No |
|
Relies on first party Azure products |
Yes, Azure products such as Azure API Management (APIM) need to be integrated. |
No |
|
Managed service |
The integration of Open-source sample with FHIR service is needed. |
Integrated as part of FHIR service. |
|
Microsoft Support |
Supported for FHIR service. Open-source sample support needs to be reported and monitored via GitHub. |
Supported for FHIR service. |
Required action
To avoid service disruptions, follow instructions listed on SMART on FHIR – Azure Health Data Services to migrate to the replacement option by 21st September 2026.
If you have questions, you can get answers from community experts in Microsoft Q&A. For technical support you can also create a support request.
