Merge pull request #263574 from shellyhaverkamp/smh-dicom-rnJan

Add bulk update to release notes

Author: Stacyrch140

articles/healthcare-apis/dicom/toc.yml

@@ -84,4 +84,4 @@ items:
 - name: DICOM service open-source projects
   href: references-for-dicom-service.md
 - name: FAQ
-  href: dicom-services-faqs.yml
+  href: dicom-services-faqs.yml

articles/healthcare-apis/release-notes.md

@@ -4,9 +4,9 @@ description: Find out about new capabilities and enhancements released monthly f
 services: healthcare-apis
 author: kgaddam10
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: workspace
 ms.topic: reference
-ms.date: 1/3/2023
+ms.date: 1/18/2023
 ms.author: kavitagaddam 
 ms.custom: references_regions
 ---
@@ -22,12 +22,25 @@ This article provides details about the features and enhancements made to Azure
 
 ## January 2024
 
+### DICOM service
+
+**Bulk update of files in the DICOM service is generally available**
+
+The bulk update operation enables you to change imaging metadata for multiple files stored in the DICOM service. For example, bulk update enables you to modify DICOM attributes for one or more studies in a single, asynchronous operation. You can use an API to perform updates to patient demographics and avoid the cost of repeating time-consuming uploads.
+
+Beyond the efficiency gains, the bulk update capability preserves a record of the changes in the change feed and persists the original, unmodified instances for future retrieval.
+
+Learn more:
+
+- [Bulk update DICOM files](dicom/update-files.md)
+
 ### FHIR service
+
 **Storage size support in FHIR service beyond 4TB** 
 
-By default each FHIR instance is limited to storage capacity of 4TB. To provision a FHIR instance with storage capacity beyond 4TB, [create support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with Issue type 'Service and Subscription limit (quotas)'.
+By default each FHIR instance is limited to storage capacity of 4TB. To provision a FHIR instance with storage capacity beyond 4TB, [create a support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with the Issue type 'Service and Subscription limit (quotas)'.
 > [!NOTE]
-> Due to issue in billing metrics for storage. Customers opting for more than 4TB storage capacity will not be billed for storage till the issue is addressed.
+> Due to an issue with billing metrics for storage, customers opting for more than 4TB storage capacity won't be billed for storage until the issue is addressed.
 
 ## December 2023