Skip to content

Commit de95667

Browse files
committed
Learn Editor: Update migration-faq.md
1 parent 55d19ba commit de95667

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/healthcare-apis/fhir/migration-faq.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ AHDS FHIR service offers a rich set of capabilities such as:
3939

4040
SMART on FHIR proxy is retiring. Organizations need to transition to the SMART on FHIR (Enhanced), which uses Azure Health Data and AI OSS samples by **September 21, 2026**. After September 21, 2026, applications relying on SMART on FHIR proxy will report errors when accessing the FHIR service.
4141

42-
SMART on FHIR (Enhanced) provides more capabilities than SMART on FHIR proxy, and meets requirements in the SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
42+
SMART on FHIR (Enhanced) provides more capabilities than SMART on FHIR proxy and meets requirements in the SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
4343

4444
## What will happen after the service is retired on September 30, 2026?
4545

@@ -59,3 +59,5 @@ Check out these resources if you need further assistance:
5959

6060
- Get answers from community experts in [Microsoft Q&A](/answers/questions/1377356/retirement-announcement-azure-api-for-fhir).
6161
- If you have a support plan and require technical support, [contact us](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
62+
63+

0 commit comments

Comments
 (0)