Skip to content

Commit 59deba6

Browse files
Merge pull request #270995 from shellyhaverkamp/docs-editor/release-notes-2024-1712100431
Update release-notes-2024.md
2 parents 39a75fe + 1b3ef1f commit 59deba6

File tree

1 file changed

+18
-1
lines changed

1 file changed

+18
-1
lines changed

articles/healthcare-apis/release-notes-2024.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kgaddam10
66
ms.service: healthcare-apis
77
ms.subservice: workspace
88
ms.topic: reference
9-
ms.date: 03/13/2024
9+
ms.date: 04/02/2024
1010
ms.author: kavitagaddam
1111
ms.custom: references_regions
1212
---
@@ -15,6 +15,23 @@ ms.custom: references_regions
1515

1616
This article describes features, enhancements, and bug fixes released in 2024 for the FHIR® service, DICOM® service, and MedTech service in Azure Health Data Services.
1717

18+
## April 2024
19+
20+
### FHIR service
21+
22+
#### The bulk delete operation is generally available
23+
24+
The bulk delete operation allows deletion of FHIR resources across different levels, enabling healthcare organizations to comply with data retention policies while providing asynchronous processing capabilities. The benefits of the bulk delete operation are:
25+
26+
- **Execute bulk delete at different levels**: The bulk delete operation allows you to delete resources from the FHIR server asynchronously. You can execute bulk delete at different levels:
27+
- **System level**: Enables deletion of FHIR resources across all resource types.
28+
- **Individual resource type**: Allows deletion of specific FHIR resources.
29+
- **Customizable**: Query parameters allow filtering of raw resources for targeted deletions.
30+
- **Async processing**: The operation is asynchronous, providing a polling endpoint to track progress.
31+
32+
Learn more:
33+
- [Bulk delete in the FHIR service](./fhir/fhir-bulk-delete.md)
34+
1835
## March 2024
1936

2037
### DICOM service

0 commit comments

Comments
 (0)