Skip to content

Commit 7b51991

Browse files
authored
Update smart-on-fhir-proxy-migration.md
1 parent e4f4c12 commit 7b51991

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

articles/healthcare-apis/includes/smart-on-fhir-proxy-migration.md

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,7 @@ ms.author: kesheth
99
ms.custom: "include file"
1010
---
1111

12-
13-
SMART on FHIR proxy will be retiring, transition to the SMART on FHIR (Enhanced) which uses [Azure Health Data and AI OSS samples](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/tree/main/samples/smartonfhir) by September 2026.
14-
After September 2026, applications relying on SMART on FHIR proxy will report errors in accessing the FHIR service.
15-
16-
SMART on FHIR (Enhanced) provides additional capabilities compared to SMART on FHIR proxy. SMART on FHIR(Enhanced) can be considered to meet requirements with [SMART on FHIR Implementation Guide (v 1.0.0)](https://hl7.org/fhir/smart-app-launch/1.0.0/) and [§170.315(g)(10) Standardized API for patient and population services criterion.](https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#ccg)
12+
SMART on FHIR (Enhanced) provides more capabilities compared to SMART on FHIR proxy. SMART on FHIR(Enhanced) can be considered to meet requirements with [SMART on FHIR Implementation Guide (v 1.0.0)](https://hl7.org/fhir/smart-app-launch/1.0.0/) and [§170.315(g)(10) Standardized API for patient and population services criterion.](https://www.healthit.gov/test-method/standardized-api-patient-and-population-services#ccg)
1713
The following table lists the difference between SMART on FHIR proxy and SMART on FHIR (Enhanced).
1814

1915
|Capability|SMART on FHIR (Enhanced)|SMART on FHIR proxy|
@@ -26,9 +22,9 @@ The following table lists the difference between SMART on FHIR proxy and SMART o
2622

2723
### Migration Steps from SMART on FHIR Proxy to SMART on FHIR (Enhanced)
2824
* Step 1: Set up FHIR SMART user role
29-
Follow the steps listed under section [Manage Users: Assign Users to Role](/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal). Any user added to SMART user role will be able to access the FHIR Service if their requests comply with the SMART on FHIR implementation Guide.
25+
Follow the steps listed under section [Manage Users: Assign Users to Role](/azure/active-directory/fundamentals/active-directory-users-assign-role-azure-portal). Any user added to SMART user role is able to access the FHIR Service, if their requests comply with the SMART on FHIR implementation Guide.
3026
* Step 2: Deploy SMART on FHIR sample under [Azure Health Data and AI OSS samples](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/tree/main/samples/smartonfhir)
31-
* Step 3: Update endpoint of the FHIR service url to '{{BASEURL_FROM_APIM}}/smart'.
32-
* Step 4: Uncheck the SMART on FHIR proxy setting under Authentication blade in Azure Portal for FHIR service.
27+
* Step 3: Update endpoint of the FHIR service url to '{{BASEURL_FROM_APIM}}/smart.'
28+
* Step 4: Uncheck the SMART on FHIR proxy setting under Authentication blade for the FHIR service.
3329

3430
If you have questions, you can get answers from community experts in [Microsoft Q&A](https://aka.ms/SMARTonFHIRproxydeprecation). For technical support, you can also create a [support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).

0 commit comments

Comments
 (0)