final fixes

shellyhaverkamp · shellyhaverkamp · commit d88606522fb1 · 2023-09-22T15:22:36.000-07:00
diff --git a/articles/healthcare-apis/azure-api-for-fhir/index.yml b/articles/healthcare-apis/azure-api-for-fhir/index.yml
@@ -5,7 +5,7 @@ summary: Azure API for FHIR is a managed, standards-based, compliant API for cli
 
 metadata:
   title: Azure API for FHIR Documentation - tutorials, how-to guides
-  description: Azure API for FHIR is a managed, standards-based, compliant API for clinical health data that enables solutions for actionable analytics and machine learning. 
+  description: This service will be retired on September 30, 2026. 
   services: healthcare-apis
   ms.service: healthcare-apis
   ms.subservice: fhir
@@ -29,7 +29,10 @@ landingContent:
         links:
           - text: Migrate to Azure Health Data Services
             url: ../fhir/migration-strategies.md
-
+      - linkListType: learn
+        links:
+          - text: Migration FAQ
+            url: ../fhir/migration-faq.md
   - title: Access Azure API for FHIR
     linkLists:
       - linkListType: concept
diff --git a/articles/healthcare-apis/fhir/fhir-faq.md b/articles/healthcare-apis/fhir/fhir-faq.md
@@ -13,9 +13,11 @@ ms.custom: references_regions
 
 # Frequently asked questions about FHIR service
 
+[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+
 This section covers some of the frequently asked questions about the Azure Health Data Services FHIR service (hereby called FHIR service).
 
-## FHIR service: The Basics
+## FHIR service: The basics
 
 ### What is FHIR?
 
@@ -25,15 +27,15 @@ The Fast Healthcare Interoperability Resources (FHIR - Pronounced "fire") is an
 
 Yes, the data is stored in managed databases in Azure. The FHIR service in Azure Health Data Services doesn't provide direct access to the underlying data store.
 
-## How can I get access to the underlying data?
+### How can I get access to the underlying data?
 
 In the managed service, you can't access the underlying data. This is to ensure that the FHIR service offers the privacy and compliance certifications needed for healthcare data. If you need access to the underlying data, you can use the [open-source FHIR server](https://github.com/microsoft/fhir-server).  
 
 ### What identity provider do you support?
 
 We support Microsoft Azure Active Directory as the identity provider.
 
-## Can I use Azure AD B2C with the FHIR service?
+### Can I use Azure AD B2C with the FHIR service?
 
 No, we don't support B2C in the FHIR service. If you need more granular access controls, we recommend looking at the [open-source FHIR proxy](https://github.com/microsoft/fhir-proxy). 
 
@@ -45,14 +47,12 @@ For more information, see [Supported FHIR features](fhir-features-supported.md).
 
 ### What is the difference between Azure API for FHIR and the FHIR service in the Azure Health Data Services?
 
-FHIR service is our implementation of the FHIR specification that sits in the Azure Health Data Services, which allows you to have a FHIR service and a DICOM service within a single workspace. Azure API for FHIR was our initial GA product and is still available as a stand-alone product. The main feature differences are:
+Azure API for FHIR was our initial generally available product and is being retired as of September 30, 2026. The Azure Health Data Services FHIR service supports additional capabilities such as: 
+
+- [Transaction bundles](https://www.hl7.org/fhir/http.html#transaction).
+- [Incremental Import](configure-import-data.md)
+- [Autoscaling](fhir-service-autoscale.md) enabled by default
 
-* FHIR service has a limit of 4 TB, and Azure API for FHIR supports more than 4 TB.
-* FHIR service support additional capabilities as 
-** [Transaction bundles](https://www.hl7.org/fhir/http.html#transaction).
-** [Incremental Import](configure-import-data.md).
-** [Autoscaling](fhir-service-autoscale.md) is enabled by default.
-* Azure API for FHIR has more platform features (such as customer managed keys, and cross region DR) that aren't yet available in FHIR service in Azure Health Data Services.
 
 ### What's the difference between the FHIR service in Azure Health Data Services and the open-source FHIR server?
 
diff --git a/articles/healthcare-apis/fhir/migration-faq.md b/articles/healthcare-apis/fhir/migration-faq.md
@@ -16,6 +16,10 @@ ms.date: 9/27/2023
 
 Azure API for FHIR will be retired on September 30, 2026.
 
+## Are new deployments of Azure API for FHIR allowed?
+
+Due to the transition from Azure API for FHIR to Azure Health Data Services, after April 1, 2025 customers won't be able to create new deployments of Azure API of FHIR. Until April 1, 2025 new deployments are allowed.
+
 ## Why is Microsoft retiring Azure API for FHIR?
 
 Azure API for FHIR is a service that was purpose built for protected health information (PHI), meeting regional compliance requirements. In March 2022, we announced the general availability of Azure Health Data Services, which enables quick deployment of managed, enterprise-grade FHIR, DICOM, and MedTech services for diverse health data integration. See below for detailed benefits of migrating to Azure Health Data Services FHIR service. With this new experience, we’re retiring Azure API for FHIR.
@@ -31,28 +35,20 @@ AHDS FHIR service offers a rich set of capabilities such as:
 - Events to trigger new workflows when FHIR resources are created, updated or deleted
 - Connectors to Azure Synapse Analytics, Power BI and Azure Machine Learning for enhanced analytics
 
-## SMART on FHIR Proxy is planned for deprecation in Gen2. When we migrate from Gen1, what are the steps for enabling SMART on FHIR in Gen2?
+## What are the steps to enable SMART on FHIR in Azure Health Data Service FHIR service?
 
-SMART on FHIR proxy will be 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 in accessing the FHIR service.
+SMART on FHIR proxy will be 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.
 
 SMART on FHIR (Enhanced) provides added capabilities than SMART on FHIR proxy and can be considered to meet requirements with SMART on FHIR Implementation Guide (v 1.0.0) and §170.315(g)(10) Standardized API for patient and population services criterion.
 
 ## What will happen after the service is retired on September 30, 2026?
 
-After September 20, 2026 customers won't be able to:
+After September 30, 2026 customers won't be able to:
 
 - Create or manage Azure API for FHIR accounts
 - Access the data through the Azure portal or APIs/SDKs/client tools
 - Receive service updates to Azure API for FHIR or APIs/SDKs/client tools
 - Access customer support (phone, email, web)
 - Where can customers go to learn more about migrating to Azure Health Data Services FHIR service?
 
-Start with \<Link to Azure Docs migration guidance \> to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. Please be advised that the migration from Azure API for FHIR to Azure Health Data Services FHIR service involves data migration as well updating the applications to use Azure Health Data Services FHIR service. You can find more documentation on the step-by-step approach to migrating your data and applications in this migration tool \<Link to github repo\>.
-
-## Where can customers go to get answers to their questions?
-
-Check out these resources if you need further assistance:
-
-- Get answers from community experts in Microsoft Q&A \<Link to Microsoft Q&A Page\>
-
-- If you have a support plan and require technical support, [contact us](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
+Start with [migration strategies](migration-strategies.md) to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. Note that the migration from Azure API for FHIR to Azure Health Data Services FHIR service involves data migration as well updating the applications to use Azure Health Data Services FHIR service. You can find more documentation on the step-by-step approach to migrating your data and applications in this [migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md).
diff --git a/articles/healthcare-apis/fhir/migration-strategies.md b/articles/healthcare-apis/fhir/migration-strategies.md
@@ -67,36 +67,42 @@ First, create a migration plan. We recommend the migration patterns described in
 | Lift and shift    | The simplest pattern. Ideal if your data pipelines can afford longer downtime.                                                                                                                    | Choose the option that works best for your organization: Configure a workflow to [\$export](https://learn.microsoft.com/azure/healthcare-apis/azure-api-for-fhir/export-data) your data on Azure API for FHIR, and then [\$import](https://learn.microsoft.com/azure/healthcare-apis/fhir/configure-import-data) into Azure Health Data Services FHIR Service. The [Github repo](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md) provides tips on running these commands, as well as a script to help automate creating the \$import payload.  Or, create your own tool to migrate the data using \$export and \$import. |
 | Incremental copy  | Continuous version of lift and shift, with less downtime. Ideal for large amounts of data that take longer to copy, or if you want to continue running Azure API for FHIR during the migration.  | Choose the option that works best for your organization. We created an [OSS migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md) to help with this migration pattern. Or, create your own tool to migrate the data incrementally.                                                                                                                                                                                                                                                                                                                                                                                                                            
 
-## Use the OSS migration tool
-
-If you decide to use the OSS migration tool, review and understand the migration tool’s capabilities and limitations.
--   Prepare Azure API for FHIR server
-    -   Identify data to migrate.
-        -   Take this opportunity to clean up data or FHIR servers that you no longer use.
-        -   Decide if you want to migrate historical versions or not. See below “Deploy a new Azure Health Data Services FHIR Service server” for more information.
-    -   If you’re planning to use the migration tool:
-        -   See “Azure API for FHIR preparation” (link to github below) for additional things to note.
--   Deploy a new Azure Health Data Services FHIR Service server
-    -   Deploy an Azure Health Data Services Workspace first
-    -   Then deploy a Azure Health Data Services FHIR Service server ([Deploy a FHIR service within Azure Health Data Services \| Microsoft Learn)](https://learn.microsoft.com/azure/healthcare-apis/fhir/fhir-portal-quickstart)
-        -   Configure your new Azure Health Data Services FHIR Service server. If you’d like to use the same configurations that you had in Azure API for FHIR for your new Azure Health Data Services FHIR Service server, see a recommended list of what to check for here (link to Github section [Migration Tool Documentation.docx](https://microsoft.sharepoint.com/:w:/t/msh/Eb7WohSv_6JNlG1xAI8TyvoBbAPfhxnPzr4wv9py1InEww?e=QeSbo3&nav=eyJoIjoiMTUwODIzNzMifQ)) Configure settings that are needed “pre-migration”.
-
-## 3) Migrate data
-
--   Choose the migration pattern that works best for your organization. 
-    -   If you are using OSS migration tools, please follow instructions on Github.
-    - 
-## 4) Migrate applications and reconfigure settings
-
--   Migrate applications that were pointing to the old FHIR server.
-    -   Change the endpoints on your applications so that they point to the new FHIR server’s URL.
-        -   (insert link on how to find the new server’s URL)
-    -   Set up permissions again for these apps.
-        -   <https://learn.microsoft.com/azure/storage/blobs/assign-azure-role-data-access>
--   Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server “post-migration” (Insert link below)
-    -   If you’d like to doublecheck to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](https://learn.microsoft.com/azure/healthcare-apis/fhir/use-postman#get-capability-statement) to compare and contrast the two servers.
--   Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)
-
-## 5) Cut over to Azure Health Data Services FHIR Services
+### OSS migration tool considerations
+
+If you decide to use the OSS migration tool, review and understand the migration tool’s [capabilities and limitations](https://github.com/Azure/apiforfhir-migration-tool/incremental-copy-docs/Appendix.md).
+#### Prepare Azure API for FHIR server
+Identify data to migrate.
+- Take this opportunity to clean up data or FHIR servers that you no longer use.
+
+- Decide if you want to migrate historical versions or not. See below “Deploy a new Azure Health Data Services FHIR Service server” for more information.
+
+- If you’re planning to use the migration tool see “Azure API for FHIR preparation” (link to github below) for additional things to note.
+
+Deploy a new Azure Health Data Services FHIR Service server. 
+- First, deploy an Azure Health Data Services workspace.
+  
+- Then deploy a Azure Health Data Services FHIR Service server ([Deploy a FHIR service within Azure Health Data Services \| Microsoft Learn)](https://learn.microsoft.com/azure/healthcare-apis/fhir/fhir-portal-quickstart)
+  
+- Configure your new Azure Health Data Services FHIR Service server. If you’d like to use the same configurations that you had in Azure API for FHIR for your new Azure Health Data Services FHIR Service server, see a recommended list of what to check for in the [migration T\tool documentation](https://microsoft.sharepoint.com/:w:/t/msh/Eb7WohSv_6JNlG1xAI8TyvoBbAPfhxnPzr4wv9py1InEww?e=QeSbo3&nav=eyJoIjoiMTUwODIzNzMifQ)) Configure settings that are needed before you migrate.
+
+## Step 3: Migrate data
+
+Choose the migration pattern that works best for your organization. If you're using OSS migration tools, follow the instructions on [Github](https://github.com/Azure/apiforfhir-migration-tool).
+
+## Step 4: Migrate applications and reconfigure settings
+
+Migrate applications that were pointing to the old FHIR server.
+
+- Change the endpoints on your applications so that they point to the new FHIR server’s URL.
+
+- Set up permissions again for [these apps](https://learn.microsoft.com/azure/storage/blobs/assign-azure-role-data-access).
+
+- Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server after migration.
+
+- If you’d like to doublecheck to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](https://learn.microsoft.com/azure/healthcare-apis/fhir/use-postman#get-capability-statement) to compare and contrast the two servers.
+
+- Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)
+
+## Step 5: Cut over to Azure Health Data Services FHIR Services
 
 After you’re confident that your Azure Health Data Services FHIR Service server is stable, you can begin using Azure Health Data Services FHIR Service to satisfy your business scenarios. Turn off any remaining pipelines that are running on Azure API for FHIR, delete data from the intermediate storage account that was used in the migration tool (if you used it), delete data from your Azure API for FHIR server, and decommission your Azure API for FHIR account.
diff --git a/articles/healthcare-apis/includes/healthcare-apis-azure-api-fhir-retirement.md b/articles/healthcare-apis/includes/healthcare-apis-azure-api-fhir-retirement.md
@@ -8,7 +8,7 @@ ms.author: jasteppe
 ---
 
 > [!IMPORTANT]
-> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration guidance](../fhir/migration-strategies.md) to transition to Azure Health Data Services FHIR service by that date. Due to the transition of Azure API for FHIR to Azure Health Data Services, new deployments won't be allowed beginning April 1, 2025. 
+> **Azure API for FHIR will be retired on September 30, 2026.** Follow the [migration strategies](../fhir/migration-strategies.md) to transition to Azure Health Data Services FHIR service by that date. Due to the transition of Azure API for FHIR to Azure Health Data Services, new deployments won't be allowed beginning April 1, 2025. 
 
 [Azure Health Data Services FHIR service](../healthcare-apis-overview.md) is the evolved version of Azure API for FHIR that enables customers to manage [FHIR](../fhir/overview.md), DICOM, and MedTech services with integrations into other Azure services.
  
