Skip to content

Commit 168b9c0

Browse files
authored
Update de-identified-export.md
1 parent 99b63b5 commit 168b9c0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/healthcare-apis/fhir/de-identified-export.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ You will need to create a container for the de-identified export in your ADLS Ge
5454
> It is common practice to name the container `anonymization`. The JSON file within the container is often named `anonymizationConfig.json`.
5555
5656
## Manage Configuration File in ACR
57-
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](https://docs.microsoft.com/en-us/azure/healthcare-apis/fhir/convert-data#host-and-use-templates).
57+
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#host-and-use-templates).
5858
1. Push the configuration files to your Azure Container Registry.
5959
2. Enable Managed Identity on your FHIR service instance.
6060
3. Provide access of the ACR to the FHIR service Managed Identity.

0 commit comments

Comments
 (0)