link fixes

Author: shellyhaverkamp

articles/healthcare-apis/fhir/convert-data-azure-data-factory.md

@@ -19,7 +19,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.
+1. Deploy an instance of the [FHIR service](fhir-portal-quickstart.md). The FHIR service is used to invoke the [`$convert-data`](convert-data-overview.md) 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.
 
@@ -190,7 +190,7 @@ Successful pipeline executions result in the transformed FHIR R4 bundles as JSON
 
 ### Errors
 
-Errors encountered during conversion, as part of the pipeline execution, result in error details captured as JSON file in the configured error destination ADLS Gen2 storage account and container. For information on how to troubleshoot `$convert-data`, see [Troubleshoot $convert-data](troubleshoot-convert-data.md).
+Errors encountered during conversion, as part of the pipeline execution, result in error details captured as JSON file in the configured error destination ADLS Gen2 storage account and container. For information on how to troubleshoot `$convert-data`, see [Troubleshoot $convert-data](convert-data-troubleshoot.md).
 
 :::image type="content" source="media/convert-data/convert-data-with-azure-data-factory/pipeline-errors.png" alt-text="Screenshot showing Azure Data Factory errors." lightbox="media/convert-data/convert-data-with-azure-data-factory/pipeline-errors.png":::
 

articles/healthcare-apis/fhir/convert-data-configuration.md

@@ -135,8 +135,6 @@ 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/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
 
 1. In your resource group, go to your **Container Registry** instance, and then select the **Access control (IAM)** tab.
@@ -169,8 +167,6 @@ 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/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.
 
 > [!NOTE]

articles/healthcare-apis/fhir/convert-data-faq.md

@@ -32,8 +32,6 @@ 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/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.  
 >

articles/healthcare-apis/fhir/deidentified-export.md

@@ -56,7 +56,7 @@ You need to create a container for the deidentified export in your ADLS Gen2 acc
 
 ## Manage Configuration File in ACR
 
-We recommend 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).  
+We recommend that you host the export configuration files on Azure Container Registry(ACR).  
 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.
@@ -83,4 +83,4 @@ We recommend that you host the export configuration files on Azure Container Reg
 
 Export data(export-data.md)
 
-[!INCLUDE [FHIR trademark statement](./includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/fhir/import-data.md

@@ -315,7 +315,7 @@ Here are the error messages that occur if the `import` operation fails, along wi
 
 ## Next steps
 
-[Convert your data to FHIR](convert-data.md)
+[Convert your data to FHIR](convert-data-overview.md)
 
 [Configure export settings and set up a storage account](configure-export-data.md)