Skip to content

Commit f283891

Browse files
jad0126jad0126
committed
small fixes
1 parent 04db010 commit f283891

2 files changed

Lines changed: 19 additions & 19 deletions

File tree

‎articles/healthcare-apis/deidentification/languages-supported.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.date: 10/23/2025
1111
#customer intent: As a user of this service, I want to know what languages I can use for de-identification of patient data, so that I can improve privacy.
1212
---
1313

14-
# Languages supported by the Azure Health Data Services de-identification service
14+
# Language support for the Azure Health Data Services de-identification service
1515

1616
The Azure Health Data Services de-identification service currently works in four languages, and includes six language-locale pairings. To tag, redact, or replace unstructured textual data for purposes of de-identification, you can use the languages listed in the following table.
1717

@@ -26,7 +26,7 @@ The Azure Health Data Services de-identification service currently works in four
2626

2727
The following table provides examples of inputs and outputs you can expect, according to the type of de-identification operation you want to do (such as redaction or surrogation).
2828

29-
| Operation | Language-Locale pair | Input | Output |
29+
| Operation | Language-locale pair | Input | Output |
3030
|-------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
3131
| Redaction | en-US | `Kimberly Brown is a 34 y.o. female presenting with bilateral eye discomfort. Last seen by her PCP 2/6/2025 Dr. Orlo at Contoso Clinics Downtown Bellevue PCP` | `[patient] is a [age] y.o. female presenting with bilateral eye discomfort. Last seen by her PCP [date] [doctor] at [hospital] PCP.` |
3232
| Redaction | fr-CA | `André, âgé de 45 ans, a été admis à l'Hôpital de Laval le 23 avril 2025 après une évaluation avec Dr Jeanne Dubuc.` | `[patient], âgé de [age], a été admis à l'[hospital] le [date] après une évaluation avec [doctor].` |

‎articles/healthcare-apis/deidentification/reliability-health-data-services-deidentification.md‎

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -12,15 +12,15 @@ ms.date: 09/27/2024
1212

1313
# Reliability in the Azure Health Data Services de-identification service
1414

15-
This article describes reliability support in the de-identification service. For a more detailed overview of reliability principles in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
15+
This article describes reliability support in the Azure Health Data Services de-identification service. For a more detailed overview of reliability principles in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
1616

1717
## Cross-region disaster recovery
1818

1919
[!INCLUDE [introduction to disaster recovery](~/reusable-content/ce-skilling/azure/includes/reliability/reliability-disaster-recovery-description-include.md)]
2020

2121
Each de-identification service is deployed to a single Azure region. If an entire region isn't available or performance is significantly degraded:
2222

23-
- The control plane functionality of Azure Resource Manager is limited to read-only during the outage. Your service metadata (such as resource properties) is always backed up outside of the region by Microsoft. After the outage is over, you can read and write to the control plane.
23+
- The control plane functionality of Azure Resource Manager is limited to read-only during the outage. Microsoft always backs up your service metadata (such as resource properties) outside the region. After the outage is over, you can read and write to the control plane.
2424

2525
- All data plane requests, such as de-identification or job API requests, fail during the outage. No customer data is lost, but there's the potential for job progress metadata to be lost. After the outage is over, you can read and write to the data plane.
2626

@@ -50,7 +50,7 @@ To complete this tutorial:
5050

5151
You need two instances of a de-identification service in different Azure regions for this tutorial. The tutorial uses the East US and West US 2 regions, but feel free to choose your own regions.
5252

53-
To make management and clean-up simpler, you use a single resource group for all resources in this tutorial. Consider using separate resource groups for each region/resource to further isolate your resources in a disaster recovery situation.
53+
To make management and clean-up simpler, you use a single resource group for all resources in this tutorial. Consider using separate resource groups for each region or resource to further isolate your resources in a disaster recovery situation.
5454

5555
Run the following command to create your resource group.
5656

@@ -64,7 +64,7 @@ Follow the steps at [Quickstart: Deploy the de-identification service](/azure/he
6464

6565
Note the service URL of each de-identification service. You need this information when you deploy Azure Front Door in the next step.
6666

67-
### Create a front door
67+
### Create a deployment
6868

6969
A multiregion deployment can use an active-active or active-passive configuration. An active-active configuration distributes requests across multiple active regions. An active-passive configuration keeps running instances in the secondary region, but doesn't send traffic there unless the primary region fails.
7070

@@ -75,7 +75,7 @@ You can enable these configurations in Azure Front Door. For more information on
7575
You now create a profile in Azure Front Door to route traffic to your services. Run [`az afd profile create`](/cli/azure/afd/profile#az-afd-profile-create).
7676

7777
> [!NOTE]
78-
> If you want to deploy Azure Front Door Standard instead of Premium, substitute the value of the `--sku` parameter with `Standard_AzureFrontDoor`. You can't deploy managed rules with a WAF policy if you choose the Standard tier. For a detailed comparison of the pricing tiers, see [Azure Front Door tier comparison](/azure/frontdoor/standard-premium/tier-comparison).
78+
> If you want to deploy Azure Front Door Standard instead of Premium, substitute the value of the `--sku` parameter with `Standard_AzureFrontDoor`. You can't deploy managed rules with a web application firewall (WAF) policy if you choose the Standard tier. For a detailed comparison of the pricing tiers, see [Azure Front Door tier comparison](/azure/frontdoor/standard-premium/tier-comparison).
7979
8080
```azurecli-interactive
8181
az afd profile create --profile-name myfrontdoorprofile --resource-group my-deid --sku Premium_AzureFrontDoor
@@ -111,14 +111,14 @@ az afd origin-group create --resource-group my-deid --origin-group-name myorigin
111111
|Parameter |Value |Description |
112112
|-------------------------------------|---------------|-------------------------------------------------------------------------------------|
113113
|`origin-group-name` |`myorigingroup`|Name of the origin group. |
114-
|`probe-request-type` |`GET` |The type of health probe request that is made. |
114+
|`probe-request-type` |`GET` |Type of health probe request that is made. |
115115
|`probe-protocol` |`Https` |Protocol to use for health probe. |
116-
|`probe-interval-in-seconds` |`60` |The number of seconds between health probes. |
117-
|`probe-path` |`/health` |The path relative to the origin that is used to determine the health of the origin. |
118-
|`sample-size` |`1` |The number of samples to consider for load balancing decisions. |
119-
|`successful-samples-required` |`1` |The number of samples within the sample period that must succeed. |
120-
|`additional-latency-in-milliseconds` |`50` |The extra latency in milliseconds for probes to fall into the lowest latency bucket. |
121-
|`enable-health-probe` |not applicable | Switch to control the status of the health probe. |
116+
|`probe-interval-in-seconds` |`60` |Number of seconds between health probes. |
117+
|`probe-path` |`/health` |Path relative to the origin that is used to determine the health of the origin. |
118+
|`sample-size` |`1` |Number of samples to consider for load balancing decisions. |
119+
|`successful-samples-required` |`1` |Number of samples within the sample period that must succeed. |
120+
|`additional-latency-in-milliseconds` |`50` |Extra latency in milliseconds for probes to fall into the lowest latency bucket. |
121+
|`enable-health-probe` |Not applicable |Switch to control the status of the health probe. |
122122

123123
### Add origins to the origin group
124124

@@ -134,7 +134,7 @@ az afd origin create --resource-group my-deid --host-name <service-url-east-us>
134134
|`origin-name` |`deid1` |Name of the origin. |
135135
|`origin-host-header` |`<service-url-east-us>` |The host header to send for requests to this origin. |
136136
|`priority` |`1` |The priority. Set this parameter to 1 to direct all traffic to the primary de-identification service.|
137-
|`weight` |`1000` |Weight of the origin in specified origin group for load balancing. Must be between 1 and 1000. |
137+
|`weight` |`1000` |Weight of the origin in specified origin group for load balancing. Must be between `1` and `1000`. |
138138
|`enabled-state` |`Enabled` |Whether to enable this origin. |
139139
|`https-port` |`443` |The port used for HTTPS requests to the origin. |
140140

@@ -162,11 +162,11 @@ az afd route create --resource-group my-deid --profile-name myfrontdoorprofile -
162162
|`supported-protocols` |`Https` |List of supported protocols for this route. |
163163
|`link-to-default-domain` |`Enabled` |Whether this route is linked to the default endpoint domain. |
164164

165-
Allow about 15 minutes for this step to complete. It takes some time for this change to propagate globally. After this period, your Azure Front Door is fully functional.
165+
Allow about 15 minutes for this step to finish. It takes some time for this change to propagate globally. After this period, your Azure Front Door profile is fully functional.
166166

167-
### Test the front door
167+
### Test the profile
168168

169-
When you create the Azure Front Door profile, it takes a few minutes for the configuration to be deployed globally. After this period, you can access the host you created.
169+
When you create the Azure Front Door profile, it takes a few minutes for the configuration to be deployed globally. After this period, you can access the host that you created.
170170

171171
To get the host name of the Azure Front Door endpoint, run [`az afd endpoint show`](/cli/azure/afd/endpoint#az-afd-endpoint-show). It looks like `abddefg.azurefd.net`.
172172

@@ -203,7 +203,7 @@ In the preceding steps, you created Azure resources in a resource group. If you
203203
az group delete --name my-deid
204204
```
205205

206-
This command might take a few minutes to complete.
206+
This command might take a few minutes to finish.
207207

208208
### Initiate recovery
209209

0 commit comments

Comments
 (0)