redirects

shellyhaverkamp · shellyhaverkamp · commit de108e9a3de6 · 2024-05-03T11:23:27.000-07:00
diff --git a/articles/healthcare-apis/.openpublishing.redirection.healthcare-apis.json b/articles/healthcare-apis/.openpublishing.redirection.healthcare-apis.json
@@ -516,17 +516,17 @@
           "source_path_from_root": "/articles/healthcare-apis/fhir/configure-azure-rbac-for-fhir.md",
           "redirect_url": "/azure/healthcare-apis/configure-azure-rbac",
           "redirect_document_id": false
-      },
+    },
       {
           "source_path_from_root": "/articles/healthcare-apis/data-transformation/convert-data.md",
-          "redirect_url": "/azure/healthcare-apis/fhir/overview-of-convert-data",
+          "redirect_url": "/azure/healthcare-apis/fhir/convert-data-overview",
           "redirect_document_id": false
-      },
+    },
       {
-          "source_path_from_root": "/articles/healthcare-apis/fhir/convert-data.md",
-          "redirect_url": "/azure/healthcare-apis/fhir/overview-of-convert-data",
-          "redirect_document_id": true
-      },
+            "source_path_from_root": "/articles/healthcare-apis/fhir/frequently-asked-questions-convert-data.md",
+            "redirect_url": "/azure/healthcare-apis/fhir/convert-data-faq",
+            "redirect_document_id": true
+    },
       {
           "source_path_from_root": "/articles/healthcare-apis/fhir/bulk-importing-fhir-data.md",
           "redirect_url": "/azure/healthcare-apis/fhir/configure-import-data",
diff --git a/articles/healthcare-apis/fhir/convert-data-azure-data-factory.md b/articles/healthcare-apis/fhir/convert-data-azure-data-factory.md
@@ -20,7 +20,7 @@ In this article, we detail how to use [Azure Data Factory (ADF)](../../data-fact
 Before getting started, do these steps:
 
 1. Deploy an instance of the [FHIR service](fhir-portal-quickstart.md). The FHIR service is used to invoke the [`$convert-data`](overview-of-convert-data.md) operation.
-2. By default, the ADF pipeline in this scenario uses the [predefined templates provided by Microsoft](configure-settings-convert-data.md#default-templates) for conversion. If your use case requires customized templates, set up your [Azure Container Registry instance to host your own templates](configure-settings-convert-data.md#host-your-own-templates) to be used for the conversion operation. 
+2. By default, the ADF pipeline in this scenario uses the [predefined templates provided by Microsoft](convert-data-configuration.md#default-templates) for conversion. If your use case requires customized templates, set up your [Azure Container Registry instance to host your own templates](convert-data-configuration.md#host-your-own-templates) to be used for the conversion operation. 
 3. Create storage accounts with [Azure Data Lake Storage Gen2 (ADLS Gen2) capabilities](../../storage/blobs/create-data-lake-storage-account.md) by enabling a hierarchical namespace and container to store the data to read from and write to.
 
    You can create and use either one or separate ADLS Gen2 accounts and containers to:
diff --git a/articles/healthcare-apis/fhir/convert-data-configuration.md b/articles/healthcare-apis/fhir/convert-data-configuration.md
@@ -37,7 +37,7 @@ To access and use the default templates for your conversion requests, ensure tha
 > 3. Use your registered templates in your API calls.
 > 4. Verify that the conversion behavior meets your requirements.
 >
-> For more information on hosting your own templates, see [Host your own templates](configure-settings-convert-data.md#host-your-own-templates) 
+> For more information on hosting your own templates, see [Host your own templates](convert-data-configuration.md#host-your-own-templates) 
 
 ## Customize templates
 
@@ -135,7 +135,7 @@ To reference specific template versions in the API, be sure to use the exact ima
 
 2. Change the **Status** to **On** and select **Save** to enable the system-managed identity in the FHIR service.
 
-:::image type="content" source="media/convert-data/configure-settings-convert-data/fhir-managed-identity-enabled.png" alt-text="Screenshot of the FHIR pane for enabling the managed identity feature." lightbox="media/convert-data/configure-settings-convert-data/fhir-managed-identity-enabled.png":::
+:::image type="content" source="media/convert-data/convert-data-configuration/fhir-managed-identity-enabled.png" alt-text="Screenshot of the FHIR pane for enabling the managed identity feature." lightbox="media/convert-data/convert-data-configuration/fhir-managed-identity-enabled.png":::
 
 ### Step 4: Provide Azure Container Registry access to the FHIR service managed identity
 
@@ -169,7 +169,7 @@ To use the Azure portal:
 3. Select **Add** and then, in the dropdown list, select your registry server. 
 4. Select **Save**. 
 
-   :::image type="content" source="media/convert-data/configure-settings-convert-data/fhir-acr-add-registry.png" alt-text="Screenshot of the Artifacts screen for registering an Azure Container Registry with a FHIR service." lightbox="media/convert-data/configure-settings-convert-data/fhir-acr-add-registry.png":::
+   :::image type="content" source="media/convert-data/convert-data-configuration/fhir-acr-add-registry.png" alt-text="Screenshot of the Artifacts screen for registering an Azure Container Registry with a FHIR service." lightbox="media/convert-data/convert-data-configuration/fhir-acr-add-registry.png":::
 
 You can register up to 20 ACR servers in the FHIR service.
 
diff --git a/articles/healthcare-apis/fhir/convert-data-faq.md b/articles/healthcare-apis/fhir/convert-data-faq.md
@@ -32,7 +32,7 @@ However, the `$convert-data` operation itself isn't an ETL pipeline.
 
 There's an example published in the [Azure Data Factory template gallery](../../data-factory/solution-templates-introduction.md#template-gallery) named **Transform HL7v2 health data to FHIR R4 format and write to ADLS Gen2**. This template transforms HL7v2 messages read from an Azure Data Lake Storage (ADLS) Gen2 or an Azure Blob Storage account into the FHIR R4 format. It then persists the transformed FHIR bundle JSON file into an ADLS Gen2 or a Blob Storage account. When you’re in the Azure Data Factory template gallery, you can search for the template.
 
-:::image type="content" source="media/convert-data/frequently-asked-questions-convert-data/azure-data-factory-template-gallery.png" alt-text="Screenshot of the Azure Data Factory Template Gallery." lightbox="media/convert-data/frequently-asked-questions-convert-data/azure-data-factory-template-gallery.png"::: 
+:::image type="content" source="media/convert-data/convert-data-faq/azure-data-factory-template-gallery.png" alt-text="Screenshot of the Azure Data Factory Template Gallery." lightbox="media/convert-data/convert-data-faq/azure-data-factory-template-gallery.png"::: 
 
 > [!IMPORTANT]
 > The purpose of this template is to help you get started with an ETL pipeline. Any steps in this pipeline can be removed, added, edited, or customized to fit your needs.  
@@ -67,17 +67,17 @@ The outcome of FHIR conversion is a FHIR bundle as a batch.
 
 ## Can I customize a default Liquid template? 
 
-Yes. You can use the [FHIR Converter Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-health-fhir-converter) to customize templates according to your specific requirements. The extension provides an interactive editing experience and makes it easy to download Microsoft-published templates and sample data. The FHIR Converter extension for Visual Studio Code is available for HL7v2, C-CDA, and JSON Liquid templates. FHIR STU3 to FHIR R4 Liquid templates are currently not supported. For more information, see [Configure settings for $convert-data using the Azure portal](configure-settings-convert-data.md).
+Yes. You can use the [FHIR Converter Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-health-fhir-converter) to customize templates according to your specific requirements. The extension provides an interactive editing experience and makes it easy to download Microsoft-published templates and sample data. The FHIR Converter extension for Visual Studio Code is available for HL7v2, C-CDA, and JSON Liquid templates. FHIR STU3 to FHIR R4 Liquid templates are currently not supported. For more information, see [Configure settings for $convert-data using the Azure portal](convert-data-configuration.md).
 
 ## After I customize a template, can I reference and store various versions?
 
-Yes. It’s possible to store and reference custom templates. For more information, see [Configure settings for $convert-data by using the Azure portal](configure-settings-convert-data.md).
+Yes. It’s possible to store and reference custom templates. For more information, see [Configure settings for $convert-data by using the Azure portal](convert-data-configuration.md).
 
 ## If I need support with troubleshooting, where can I go?
 
 Depending on the version of `$convert-data` you’re using, you can:
 
-* Use the [troubleshooting guide](troubleshoot-convert-data.md) for the FHIR service in Azure Health Data Services version of the `$convert-data` operation.
+* Use the [troubleshooting guide](convert-data-troubleshoot.md) for the FHIR service in Azure Health Data Services version of the `$convert-data` operation.
 
 * Open a [support request](../../azure-portal/supportability/how-to-create-azure-support-request.md) for the FHIR service in Azure Health Data Service FHIR Services version of the `$convert-data` operation.
 
@@ -87,9 +87,9 @@ Depending on the version of `$convert-data` you’re using, you can:
 
 [Overview of $convert-data](convert-data-overview.md)
 
-[Configure settings for $convert-data using the Azure portal](configure-settings-convert-data.md)
+[Configure settings for $convert-data using the Azure portal](convert-data-configuration.md)
 
-[Troubleshoot $convert-data](troubleshoot-convert-data.md)
+[Troubleshoot $convert-data](convert-data-troubleshoot.md)
 
 [!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
  
diff --git a/articles/healthcare-apis/fhir/convert-data-overview.md b/articles/healthcare-apis/fhir/convert-data-overview.md
@@ -60,7 +60,7 @@ A `$convert-data` operation call packages the health data for conversion inside
 > 3. Use your registered templates in your API calls.
 > 4. Verify that the conversion behavior meets your requirements.
 >
-> For more information on hosting your own templates, see [Host your own templates](Configure-settings-convert-data.md#host-your-own-templates) 
+> For more information on hosting your own templates, see [Host your own templates](convert-data-configuration.md#host-your-own-templates) 
 
 #### Sample request
 
@@ -118,11 +118,11 @@ The outcome of FHIR conversion is a FHIR bundle as a batch.
 
 ## Next steps
 
-[Configure settings for $convert-data using the Azure portal](configure-settings-convert-data.md)
+[Configure settings for $convert-data using the Azure portal](convert-data-configuration.md)
 
-[Troubleshoot $convert-data](troubleshoot-convert-data.md)
+[Troubleshoot $convert-data](convert-data-troubleshoot.md)
 
-[$convert-data FAQ](frequently-asked-questions-convert-data.md)
+[$convert-data FAQ](convert-data-faq.md)
 
 [!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
  
diff --git a/articles/healthcare-apis/fhir/de-identified-export.md b/articles/healthcare-apis/fhir/de-identified-export.md
@@ -56,7 +56,7 @@ You need to create a container for the de-identified export in your ADLS Gen2 ac
 
 ## Manage Configuration File in ACR
 
-It's recommended that you host the export configuration files on Azure Container Registry(ACR). It takes the following steps similar as [hosting templates in ACR for $convert-data](configure-settings-convert-data.md#host-your-own-templates).  
+It's recommended that you host the export configuration files on Azure Container Registry(ACR). It takes the following steps similar as [hosting templates in ACR for $convert-data](convert-data-faq.md#host-your-own-templates).  
 1. Push the configuration files to your Azure Container Registry.
 2. Enable Managed Identity on your FHIR service instance.
 3. Provide access of the ACR to the FHIR service Managed Identity.
