a few more fixes

shellyhaverkamp · shellyhaverkamp · commit 45f8c4f69c96 · 2023-09-21T17:33:15.000-07:00
diff --git a/articles/healthcare-apis/fhir/migration-faq.md b/articles/healthcare-apis/fhir/migration-faq.md
@@ -1,6 +1,6 @@
 ---
-title: Migration strategies
-description: Learn how to migrate FHIR data from Azure API for FHIR to the Azure Health Data Services FHIR service. This article provides steps and tools for a smooth transition.
+title: Migration FAQ
+description: Find answers to your questions about migrating FHIR data from Azure API for FHIR to the Azure Health Data Services FHIR service.
 services: healthcare-apis
 ms.service: healthcare-apis
 ms.subservice: fhir
@@ -16,11 +16,11 @@ ms.date: 9/27/2023
 
 Azure API for FHIR will be retired on September 30, 2026.
 
-**1. Why is Microsoft retiring Azure API for FHIR?**
+**2. 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](https://learn.microsoft.com/azure/healthcare-apis/healthcare-apis-overview), that 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.
+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.
 
-**1. What are the benefits of migrating to Azure Health Data Services FHIR service?**
+**3. What are the benefits of migrating to Azure Health Data Services FHIR service?**
 
 AHDS FHIR service offers a rich set of capabilities such as:
 
@@ -31,13 +31,13 @@ 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
 
-**1. 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?**
+**4. 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?**
 
 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 (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.
 
-**1. What will happen after the service is retired on September 30, 2026?**
+**5. What will happen after the service is retired on September 30, 2026?**
 
 Customers won't be able to do the following:
 
@@ -49,22 +49,22 @@ Customers won't be able to do the following:
 
 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\>.
 
-**1.Where can customers go to get answers to their questions?**
+**6.Where can customers go to get answers to their questions?**
 
-There are multiple ways to get answers to questions.
+There are multiple ways to get your questions answered.
 
 - 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)
 
-1. For Issue type, select **Technical**.
+1. For **Issue type**, select **Technical**.
 
 1. For **Subscription**, select your subscription.
 
-1. For **Service**, select **My services**, then **Azure API for FHIR**
+1. For **Service**, select **My services**, then **Azure API for FHIR**.
 
-1. For **Summary**, type a description of your issue.
+1. For **Summary**, enter a description of your issue.
 
 1. For **Problem type**, select **Troubleshoot configuration issue**.
 
-1. For **Problem** subtype, my issue is not listed.
+1. For **Problem subtype**, select **My issue is not listed**.
diff --git a/articles/healthcare-apis/fhir/migration-strategies.md b/articles/healthcare-apis/fhir/migration-strategies.md
@@ -94,68 +94,6 @@ Only the capabilities that differ between the two products are called out above.
     -   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) Cutover from Azure API for FHIR to Azure Health Data Services FHIR Service
 
 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.
-
-## Appendix
-
-## Azure API for FHIR and Azure Health Data Services capabilities
-
-# FAQ
-
-(to be added as first response to Q&A page also)
-
--   When will Azure API for FHIR be retired?
-
-Azure API for FHIR will be retired on 30 September 2026.
-
--   Why are we 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](https://learn.microsoft.com/azure/healthcare-apis/healthcare-apis-overview), that 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
-
--   What are the benefits of migrating to Azure Health Data Services FHIR service?
-
-AHDS FHIR service offers a rich set of capabilities such as
-
--   Consumption-based pricing model where customers pay only for used storage & throughput
--   Support for transaction bundles
--   Chained search improvements
--   Improved ingress & egress of data with \$import, \$export including new features such as incremental import (preview)
--   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, as we migrate from Gen1 what are the steps for enabling SMART on FHIR in Gen2?
-
-SMART on FHIR proxy will be retiring, please transition to the SMART on FHIR (Enhanced) which uses Azure Health Data and AI OSS samples by **21 September 2026**. 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 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 30 September 2026?
-
-Customers will not be able to do the following:
-
--   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?
-
-You can 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 for answers to questions?
-
-Customers have multiple options to get answers to questions.
-
--   Get answers from community experts in Microsoft Q&A \<Link to Microsoft Q&A Page\><mailto:APIforFHIRtoAHDSFHIRMigrationQA@service.microsoft.com>
--   If you have a support plan and require technical support, please [contact us.](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest)
-1.  Under Issue type, select Technical.
-2.  Under Subscription, select your subscription.
-3.  Under Service, click My services, then Azure API for FHIR
-4.  Under Summary, type a description of your issue.
-5.  Under Problem type, Troubleshoot configuration issue
-6.  Under Problem subtype, my issue is not listed
-
-TODO when to use CSS vs use github issues
-
diff --git a/articles/healthcare-apis/fhir/toc.yml b/articles/healthcare-apis/fhir/toc.yml
@@ -132,7 +132,7 @@ items:
   items:
   - name: FHIR service FAQ
     href: fhir-faq.md
-    name: Migration FAQ
+  - name: Migration FAQ
     href: migration-faq.md
   - name: Supported features
     href: fhir-features-supported.md
