You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/de-identified-export.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ You will need to create a container for the de-identified export in your ADLS Ge
54
54
> It is common practice to name the container `anonymization`. The JSON file within the container is often named `anonymizationConfig.json`.
55
55
56
56
## 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](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.md#host-your-own-templates).
58
58
1. Push the configuration files to your Azure Container Registry.
59
59
2. Enable Managed Identity on your FHIR service instance.
60
60
3. Provide access of the ACR to the FHIR service Managed Identity.
0 commit comments