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: sdk/healthdataaiservices/Azure.Health.Deidentification/CHANGELOG.md
+15-4Lines changed: 15 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,10 +11,21 @@
11
11
12
12
### Breaking Changes
13
13
14
-
- Changed `outputPrefix` behavior from including `jobName` to prefix replacement method
15
-
- Changed `Path` field to `Location` in `SourceStorageLocation` and `TargetStorageLocation`
16
-
- Deprecated `DocumentDataType`
17
-
- Deprecated `Path` and `Location` from `TaggerResult` model
14
+
- Changed method names in `DeidentificationClient` to match functionality:
15
+
- Changed the `Deidentify*` method names to `DeidentifyText*`.
16
+
- Changed the `CreateJob*` method names to `DeidentifyDocuments*`.
17
+
- Renamed the property `DeidentificationContent.Operation` to `OperationType`.
18
+
- Deprecated `DocumentDataType`.
19
+
- Changed the model `DeidentificationDocumentDetails`:
20
+
- Renamed `Input` to `InputLocation`.
21
+
- Renamed `Output` to `OutputLocation`.
22
+
- Changed the model `DeidentificationJob`
23
+
- Renamed `Name` to `JobName`.
24
+
- Renamed `Operation` to `OperationType`.
25
+
- Renamed the model `OperationState` to `OperationStatus`.
26
+
- Changed `Path` field to `Location` in `SourceStorageLocation` and `TargetStorageLocation`.
27
+
- Changed handling of `TargetStorageLocation.Prefix` to only include the provided value. Previously, the generated document locations would include the `DeidentificationJob.JobName` by default.
28
+
- Deprecated `Path` and `Location` from `TaggerResult` model.
- Tag: Will return a structure of offset and length with the PHI category of the related text spans.
54
-
- Redact: Will return output text with placeholder stubbed text. ex. `[name]`
55
-
- Surrogate: Will return output text with synthetic replacements.
56
-
-`My name is John Smith`
57
-
-`My name is Tom Jones`
54
+
### Operation Types
55
+
Given an input text, the de-identification service can perform three main operations:
56
+
-`Tag` returns the category and location within the text of detected PHI entities.
57
+
-`Redact` returns output text where detected PHI entities are replaced with placeholder text. For example `John` replaced with `[name]`.
58
+
-`Surrogate` returns output text where detected PHI entities are replaced with realistic replacement values. For example, `My name is John Smith` could become `My name is Tom Jones`.
58
59
59
-
**Job Integration with Azure Storage**
60
-
Instead of sending text, you can send an Azure Storage Location to the service. We will asynchronously
61
-
process the list of files and output the deidentified files to a location of your choice.
60
+
For more information about customizing the redaction format, see [Tutorial: Use a custom redaction format with the de-identification service][deid_redaction_format].
62
61
63
-
Limitations:
64
-
- Maximum file count per job: 1000 documents
65
-
- Maximum file size per file: 2 MB
62
+
### De-identification Methods
63
+
There are two methods of interacting with the de-identification service. You can send text directly, or you can create jobs
64
+
to de-identify documents in Azure Storage.
66
65
67
-
**Redaction Formatting**
66
+
You can de-identify text directly using the `DeidentificationClient`:
To learn about prerequisites and configuration options for de-identifying documents in Azure Storage, see [Tutorial: Configure Azure Storage to de-identify documents][deid_configure_storage].
76
+
Once you have configured your storage account, you can create a job to de-identify documents in a container.
We guarantee that all client instance methods are thread-safe and independent of each other ([guideline](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-service-methods-thread-safety)). This ensures that the recommendation of reusing client instances is always safe, even across threads.
91
+
All client instance methods are thread-safe and independent of each other ([guideline](https://azure.github.io/azure-sdk/dotnet_introduction.html#dotnet-service-methods-thread-safety)). This ensures that the recommendation of reusing client instances is always safe, even across threads.
74
92
75
93
### Additional concepts
76
94
<!-- CLIENT COMMON BAR -->
@@ -85,18 +103,17 @@ We guarantee that all client instance methods are thread-safe and independent of
85
103
86
104
## Examples
87
105
88
-
You can familiarize yourself with different APIs using [Samples](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/healthdataaiservices/Azure.Health.Deidentification/samples).
106
+
For sample code snippets illustrating common patterns used in the de-identification service, see the [samples][samples].
89
107
90
108
## Next steps
91
109
92
-
- Find a bug, or have feedback? Raise an issue with "Health Deidentification" Label.
93
-
110
+
- Find a bug, or have feedback? Raise an issue with the [Health Deidentification][github_issue_label] label.
94
111
95
112
## Troubleshooting
96
113
97
-
-**Unabled to Access Source or Target Storage**
98
-
- Ensure you create your deid service with a system assigned managed identity
99
-
- Ensure your storage account has given permissions to that managed identity
114
+
-**Unable to Access Source or Target Storage**
115
+
- Ensure you [assign a managed identity][deid_managed_identity] to your de-identification service
116
+
- Ensure you [assign appropriate permissions][deid_rbac] to the managed identity to access the storage account
100
117
101
118
## Contributing
102
119
@@ -117,5 +134,17 @@ additional questions or comments.
0 commit comments