Merge pull request #286560 from KendalBond007/FHIReditsBatch11_Sep24

FHIReditsBatch11_Sep24

Author: Jill Grant

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

@@ -14,7 +14,7 @@ ms.date: 9/27/2023
 
 ## When will Azure API for FHIR be retired?
 
-Azure API for FHIR will be retired on September 30, 2026.
+Azure API for FHIR® will be retired on September 30, 2026.
 
 ## Are new deployments of Azure API for FHIR allowed?
 
@@ -28,28 +28,29 @@ Azure API for FHIR is a service that was purpose built for protected health info
 
 Azure Health Data Service FHIR service offers a rich set of capabilities such as:
 
-- Consumption-based pricing model where customers pay only for used storage and throughput
-- Support for transaction bundles
-- Chained search improvements
-- Improved ingress and egress of data with \$import, \$export including new features such as incremental import
-- 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
+- Consumption-based pricing model where customers pay only for used storage and throughput.
+- Support for transaction bundles.
+- Chained search improvements.
+- Improved ingress and egress of data with `$import`, and `$export`, including new features such as incremental import.
+- 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.
 
 ## What are the steps to enable SMART on FHIR in Azure Health Data Service FHIR service?
 
-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.
+The 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.
 
-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.
+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.
 
 ## What will happen after the service is retired on September 30, 2026?
 
 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?
+- 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 [migration strategies](migration-strategies.md) to learn more about Azure API for FHIR to Azure Health Data Services FHIR service migration. The migration from Azure API for FHIR to Azure Health Data Services FHIR service involves data migration and updating the applications to use Azure Health Data Services FHIR service. Find more documentation on the step-by-step approach to migrating your data and applications in the [migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/lift-and-shift-resources/Liftandshiftresources_README.md).
 
@@ -60,4 +61,4 @@ Check out these resources if you need further assistance:
 - Get answers from community experts in [Microsoft Q&A](/answers/questions/1377356/retirement-announcement-azure-api-for-fhir).
 - If you have a support plan and require technical support, [contact us](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
 
-
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

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

@@ -14,15 +14,15 @@ ms.date: 9/27/2023
 
 [!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-Azure Health Data Services FHIR service is the next-generation platform for health data integration. It offers managed, enterprise-grade FHIR, DICOM, and MedTech services for diverse health data exchange. 
+Azure Health Data Services FHIR® service is the next-generation platform for health data integration. It offers managed, enterprise-grade FHIR, DICOM, and MedTech services for diverse health data exchange. 
 
 When you migrate your FHIR data from Azure API for FHIR to Azure Health Data Services FHIR service, your organization can benefit from improved performance, scalability, security, and compliance. Organizations can also access new features and capabilities that aren't available in Azure API for FHIR. 
 
 Azure API for FHIR will be retired on September 30, 2026, so you need to migrate your FHIR data to Azure Health Data Services FHIR service as soon as feasible. To make the process easier, we created some tools and tips to help you assess your readiness, prepare your data, migrate your applications, and cut over to the new service.
 
 ## Recommended approach
 
-To migrate your data, follow these steps:
+To migrate your data, follow these steps.
 
 - Step 1: Assess readiness
 - Step 2: Prepare to migrate
@@ -36,10 +36,10 @@ Compare the differences between Azure API for FHIR and Azure Health Data Service
 |Capabilities|Azure API for FHIR|Azure Health Data Services|
 |------------|------------------|--------------------------|
 |**Settings**|Supported: <br> • Local RBAC <br> • SMART on FHIR Proxy|Planned deprecation: <br> • Local RBAC (9/6/23) <br> • SMART on FHIR Proxy (9/21/26)|
-|**Data storage Volume**|More than 4 TB|Current support is 4 TB (Open an [Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md) if you need more than 4 TB)|
-|**Data ingress**|Tools available in OSS|$import operation|
+|**Data storage Volume**|More than 4 TB|Current support is 4 TB. Open an [Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md) if you need more than 4 TB|
+|**Data ingress**|Tools available in OSS|`$import` operation|
 |**Autoscaling**|Supported on request and incurs charge|Enabled by default at no extra charge|
-|**Search parameters**|Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported  <br> • Sorting supported by first name, last name, birthdate and clinical date|Bundle type supported: Batch and transaction  <br> • Selectable search parameters  <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields|
+|**Search parameters**|Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported  <br> • Sorting supported by first name, family name, birthdate and clinical date|Bundle type supported: Batch and transaction  <br> • Selectable search parameters  <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields|
 |**Events**|Not Supported|Supported|
 |**Infrastructure**|Supported: <br> • Customer managed keys <br> • Cross region DR (disaster recovery)  <br>|Supported: <br> • PITR (point in time recovery)  <br> • [Customer managed keys](configure-customer-managed-keys.md) <br> Upcoming: <br> • Availability zone support|
 
@@ -53,18 +53,18 @@ Compare the differences between Azure API for FHIR and Azure Health Data Service
 
 - **Azure Health Data Services FHIR service does not support local RBAC and custom authority**. The token issuer authority needs to be the authentication endpoint for the tenant that the FHIR Service is running in.
 
-- **The IoT connector is only supported using an Azure API for FHIR service**. The IoT connector is succeeded by the MedTech service. You need to deploy a MedTech service and corresponding FHIR service within an existing or new Azure Health Data Services workspace and point your devices to the new Azure Events Hubs device event hub. Use the existing IoT connector device and destination mapping files with the MedTech service deployment.
+- **The IoT connector is only supported using an Azure API for FHIR service**. The IoT connector is succeeded by the MedTech service. You need to deploy a MedTech service and corresponding FHIR service within an existing or new Azure Health Data Services workspace, and point your devices to the new Azure Events Hubs device event hub. Use the existing IoT connector device and destination mapping files with the MedTech service deployment.
 
 If you want to migrate existing IoT connector device FHIR data from your Azure API for FHIR service to the Azure Health Data Services FHIR service, use the bulk export and import functionality in the migration tool. Another migration path would be to deploy a new MedTech service and replay the IoT device messages through the MedTech service.
 
 ## Step 2: Prepare to migrate
 
-First, create a migration plan. We recommend the migration patterns described in the table. Depending on your organization’s tolerance for downtime, you may decide to use certain patterns and tools to help facilitate your migration.
+First, create a migration plan. We recommend the migration patterns described in the following table. Depending on your organization’s tolerance for downtime, you may decide to use certain patterns and tools to help facilitate your migration.
 
 |Migration pattern|Details|How?|
 |-----------------|-------|----|
-|**Lift and shift**|The simplest pattern. Ideal if your data pipeline can afford longer downtime.|Choose the option that works best for your organization: <br> • Configure a workflow to [\$export](../azure-api-for-fhir/export-data.md) your data on Azure API for FHIR, and then [\$import](configure-import-data.md) into Azure Health Data Services FHIR service. <br> • The [GitHub repo](https://github.com/Azure/apiforfhir-migration-tool/blob/main/lift-and-shift-resources/Liftandshiftresources_README.md) provides tips on running these commands, and a script to help automate creating the \$import payload.  <br> • 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. <br> • We created an [OSS migration tool](https://github.com/Azure/apiforfhir-migration-tool/tree/main/FHIR-data-migration-tool-docs) to help with this migration pattern. <br> • Or create your own tool to migrate the data incrementally.|
+|**Lift and shift**|The simplest pattern. Ideal if your data pipeline can afford longer downtime.|Choose the option that works best for your organization: <br> • Configure a workflow to [$export](../azure-api-for-fhir/export-data.md) your data on Azure API for FHIR, and then [$import](configure-import-data.md) into Azure Health Data Services FHIR service. <br> • The [GitHub repo](https://github.com/Azure/apiforfhir-migration-tool/blob/main/lift-and-shift-resources/Liftandshiftresources_README.md) provides tips on running these commands, and a script to help automate creating the `$import` payload.  <br> • 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. <br> • We created an [OSS migration tool](https://github.com/Azure/apiforfhir-migration-tool/tree/main/FHIR-data-migration-tool-docs) to help with this migration pattern. <br> • Create your own tool to migrate the data incrementally.|
 
 ### OSS migration tool considerations
 
@@ -80,7 +80,7 @@ Identify data to migrate.
 Deploy a new Azure Health Data Services FHIR Service server.
 - First, deploy an Azure Health Data Services workspace.
 
-- Then deploy an Azure Health Data Services FHIR Service server. More information: [Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
+- Then deploy an Azure Health Data Services FHIR Service server. More information is found here: [Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md).
 
 - Configure your new Azure Health Data Services FHIR Service server. If you need to use the same configurations as you have in Azure API for FHIR for your new server, see the recommended list of what to check for in the [migration tool documentation](https://github.com/Azure/apiforfhir-migration-tool/blob/main/FHIR-data-migration-tool-docs/Appendix.md). Configure the settings before you migrate.
 
@@ -96,12 +96,14 @@ Migrate applications that were pointing to the old FHIR server.
 
 - Set up permissions again for [these apps](/azure/storage/blobs/assign-azure-role-data-access).
 
-- Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server after migration.
+- After migration, reconfigure any remaining settings in the new Azure Health Data Services FHIR service server.
 
-- If you’d like to double check 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](use-postman.md#get-the-capability-statement) to compare and contrast the two servers.
+- If you’d like to double check that the Azure Health Data Services FHIR service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](use-postman.md#get-the-capability-statement) to compare the two servers.
 
-- Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)
+- 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 necessary, delete data from your Azure API for FHIR server, and decommission your Azure API for FHIR account.
+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. If necessary, delete data from the intermediate storage account that was used in the migration tool. Delete data from your Azure API for FHIR server, and decommission your Azure API for FHIR account.
+
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]