Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into updatePicsARS

Author: siddomala

articles/healthcare-apis/dicom/dicom-data-lake.md

@@ -57,6 +57,12 @@ The DICOM service is granted access to the data like any other service or applic
 
 You can manage costs for imaging data stored by the DICOM service by using Azure Storage access tiers for the data lake storage account. The DICOM service only supports online access tiers (either hot, cool, or cold), and can retrieve imaging data in those tiers immediately. The hot tier is the best choice for data that is in active use. The cool or cold tier is ideal for data that is accessed less frequently but still must be available for reading and writing.
 
+Using the data lake, users can manage their storage costs efficiently by moving files between Hot, Cool and Cold tiers based on their usage patterns. For example, users can move files from Hot tier to Cool or Cold tiers after an initial time period. This may reduce long-term storage costs if the files which are moved, are accessed infrequently after a period of initial use.
+
+Users can add a lifecycle policy that automatically moves files to the Cool or Cold tier after a certain number of days. If a file is accessed after being moved, the policy can bring it back to the Hot tier. To implement this policy, users need to enable access tracking, which allows the Azure to monitor and respond to file access patterns.
+
+:::image type="content" source="media/data-lake-storage-tier.png" alt-text="Screenshot showing how to efficiently manage data lake storage using Life cycle management policies." lightbox="media/data-lake-storage-tier.png":::
+
 To learn more about access tiers, including cost tradeoffs and best practices, see [Azure Storage access tiers](/azure/storage/blobs/access-tiers-overview)
 
 ## Health check

articles/healthcare-apis/dicom/media/data-lake-storage-tier.png

@@ -52,7 +52,7 @@ Query parameters allow you to filter the raw resources you plan to delete. To su
 |Query parameter        | Default Value   |  Description|
 |------------------------|---|------------|
 |_hardDelete|False|Allows you to hard delete a resource. If you don't pass this parameter or set hardDelete to false, the historic versions of the resource are still available.|
-|_purgeHistory|False|Allows you to delete history versions associated with resource. It will not delete current version of the resource and soft deleted resources.|
+|_purgeHistory|False|Allows you to delete history versions associated with resource. It will not delete current version of the resource and soft deleted resources. Note: When _purgeHistory used with the _hardDelete parameter set to true, it permanently deletes all versions associated with the resource.|
 |FHIR service supported search parameters||Allows you to specify search criteria and resources matching the search criteria are deleted. For example: `address:contains=Meadow subject:Patient.birthdate=1987-02-20`|
 
 All the query parameters are optional.