Merge pull request #285614 from KendalBond007/DICOMedits_Aug24

General DICOM edits and cleanup

Author: v-shils

articles/healthcare-apis/dicom/api-versioning-dicom-service.md

@@ -35,7 +35,7 @@ The OpenAPI Doc for the supported versions can be found at the following url:
 `<service_url>/v<version>/api.yaml`
 
 ## DICOM Conformance Statement
-All versions of the DICOM APIs conform to the DICOMweb™ Standard specifications, but different versions might expose different APIs.  See the specific version of the conformance statement for details:
+All versions of the DICOM APIs conform to the DICOMweb™ Standard specifications, but different versions might expose different APIs. See the specific version of the conformance statement for details:
 
 * [DICOM Conformance Statement v1](dicom-services-conformance-statement.md)
 * [DICOM Conformance Statement v2](dicom-services-conformance-statement-v2.md)
@@ -79,6 +79,6 @@ Example:
 [ApiVersion("1.0-prerelease", Deprecated = true)]
 ```
 
-[ ![Screenshot of the API supported and deprecated versions.](media/api-supported-deprecated-versions.png) ](media/api-supported-deprecated-versions.png#lightbox)
+[![Screenshot of the API supported and deprecated versions.](media/api-supported-deprecated-versions.png)](media/api-supported-deprecated-versions.png#lightbox)
 
 [!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

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

@@ -11,9 +11,9 @@ ms.author: mmitrik
 
 # Enable data partitioning
 
-Data partitioning allows you to set up a lightweight data partition scheme to store multiple copies of the same image with the same unique identifier (UID) in a single DICOM instance. 
+Data partitioning allows you to set up a lightweight data partition scheme to store multiple copies of the same image with the same unique identifier (UID) in a single DICOM® instance. 
 
-Although UIDs should be [unique across all contexts](http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_9.html), it's common practice for healthcare providers to write DICOM files to portable storage media and then give them to a patient. The patient then gives the files to another healthcare provider, who then transfers the files into a new DICOM storage system. Therefore, multiple copies of one DICOM file do commonly exist in isolated DICOM systems. Data partitioning provides an on-ramp for your existing data stores and workflows. 
+Although UIDs should be [unique across all contexts](http://dicom.nema.org/dicom/2013/output/chtml/part05/chapter_9.html), it's common practice for healthcare providers to write DICOM files to portable storage media and give them to a patient. The patient then gives the files to another healthcare provider, who transfers the files into a new DICOM storage system. As a result, multiple copies of one DICOM file commonly exist in several isolated DICOM systems. Data partitioning provides an on-ramp for your existing data stores and workflows.
 
 ## Limitations
 
@@ -60,7 +60,7 @@ GET /partitions
 After partitions are enabled, STOW, WADO, QIDO, delete, export, update, and worklist requests must include a data partition URI segment after the base URI, with the form `/partitions/{partitionName}`, where `partitionName` is:
 
  - Up to 64 characters long.
- - Any combination of alphanumeric characters, `.`, `-`, and `_`, to allow both DICOM UID and GUID formats, as well as human-readable identifiers.
+ - Any combination of alphanumeric characters, `.`, `-`, and `_` (to allow both DICOM UID and GUID formats), as well as human-readable identifiers.
 
 | Action  | Example URI                                                         |
 | ------- | ------------------------------------------------------------------- |
@@ -94,4 +94,6 @@ A partition is a unit of logical isolation and data uniqueness.
 | ------------- | ------ | -------------------------------------------------------------------------------- |
 | PartitionKey  | int    | System-assigned identifier.                                                       |
 | PartitionName | string | Client-assigned unique name, up to 64 alphanumeric characters, `.`, `-`, or `_`.  |
-| CreatedDate   | string | The date and time when the partition was created. |
+| CreatedDate   | string | The date and time when the partition was created. |
+
+[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure-data-lake.md

@@ -18,9 +18,9 @@ After deployment completes, you can use the Azure portal to see the details abou
 
 ## Prerequisites
 
-- **Deploy an Azure Health Data Services workspace**.  For more information, see [Deploy a workspace in the Azure portal](../healthcare-apis-quickstart.md).
-- **Create a storage account with a hierarchical namespace**.  For more information, see [Create a storage account to use with Azure Data Lake Storage Gen2](/azure/storage/blobs/create-data-lake-storage-account).
-- **Create a blob container in the storage account**.  The container is used by the DICOM service to store DICOM files.  For more information, see [Manage blob containers using the Azure portal](/azure/storage/blobs/blob-containers-portal).
+- **Deploy an Azure Health Data Services workspace**. For more information, see [Deploy a workspace in the Azure portal](../healthcare-apis-quickstart.md).
+- **Create a storage account with a hierarchical namespace**. For more information, see [Create a storage account to use with Azure Data Lake Storage Gen2](/azure/storage/blobs/create-data-lake-storage-account).
+- **Create a blob container in the storage account**. The container is used by the DICOM service to store DICOM files. For more information, see [Manage blob containers using the Azure portal](/azure/storage/blobs/blob-containers-portal).
 
 > [!NOTE]
 > The Azure Data Lake Storage option is only available for new instances of the DICOM service. After the option becomes generally available, we plan to offer a migration path for existing DICOM service instances.
@@ -65,7 +65,7 @@ After deployment completes, you can use the Azure portal to see the details abou
 
 ## Deploy the DICOM service with Data Lake Storage by using an ARM template
 
-Use the Azure portal to **Deploy a custom template** and then use the sample ARM template to deploy the DICOM service with Azure Data Lake Storage. For more information, see [Create and deploy ARM templates by using the Azure portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
+Use the Azure portal to **Deploy a custom template**. Then use the sample ARM template to deploy the DICOM service with Azure Data Lake Storage. For more information, see [Create and deploy ARM templates by using the Azure portal](../../azure-resource-manager/templates/quickstart-create-templates-use-the-portal.md).
 
 ```json
 {
@@ -212,13 +212,13 @@ Use the Azure portal to **Deploy a custom template** and then use the sample ARM
 
 ### Connectivity
 
-To be alerted to store health and connectivity failures, please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
+To receive alerts regarding store health and connectivity failures please sign up for [Resource Health alerts](/azure/service-health/resource-health-alert-monitor-guide).
 
 ### 424 Failed Dependency
 
 When the response status code is `424 Failed Dependency`, the issue lies with a dependency configured with DICOM and it may be the data lake store.
 The response body indicates which dependency failed and provides more context on the failure. For data lake storage account failures, an error code is provided which was received when attempting to interact with the store. For more information, see [Azure Blob Storage error codes](/rest/api/storageservices/blob-service-error-codes).
-Note that a code of `ConditionNotMet` typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate such a situation is to use the DICOM API to DELETE the instance to remove the index and then reupload the modified file. This will enable you to continue to reference and interact with the file through DICOM APIs.
+Note that a `ConditionNotMet` code typically indicates the blob file has been moved, deleted or modified without using DICOM APIs. The best way to mitigate this situation is to use the DICOM API to DELETE the instance, to remove the index and then reupload the modified file. This enables you to continue to reference and interact with the file through DICOM APIs.
 
 ## Next steps
 [Receive resource health alerts](/azure/service-health/resource-health-alert-monitor-guide)

articles/healthcare-apis/dicom/deploy-dicom-services-in-azure.md

@@ -13,10 +13,10 @@ ms.custom: mode-api
 
 In this quickstart, you learn how to deploy the DICOM® service by using the Azure portal.
 
-After deployment completes, you can use the Azure portal to see the details about the DICOM service, including the service URL. The service URL to access your DICOM service is ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. Make sure to specify the API version as part of the URL when you make requests. For more information, see [API versioning for the DICOM service](api-versioning-dicom-service.md).
+After deployment completes, you can use the Azure portal to see the details about the DICOM service, including the service URL. The service URL used to access your DICOM service is ```https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com```. Make sure to specify the API version as part of the URL when you make requests. For more information, see [API versioning for the DICOM service](api-versioning-dicom-service.md).
 
 > [!NOTE]
-> The DICOM service with Azure Data Lake Storage is generally available. This capability provides greater flexibility and control over your imaging data. Learn more: [Deploy the DICOM service with Azure Data Lake Storage](deploy-dicom-services-in-azure-data-lake.md)
+> The DICOM service with Azure Data Lake Storage is generally available. This capability provides greater flexibility and control over your imaging data. For more information, see [Deploy the DICOM service with Azure Data Lake Storage](deploy-dicom-services-in-azure-data-lake.md)
 
 ## Prerequisites
 

articles/healthcare-apis/dicom/dicom-configure-azure-rbac.md

@@ -16,19 +16,19 @@ In this article, you'll learn how to use [Azure role-based access control (Azure
 
 To grant users, service principals, or groups access to the DICOM data plane, select the **Access control (IAM)** blade. Select the **Role assignments** tab, and select **+ Add**.
 
-[ ![Screenshot of DICOM access control.](media/dicom-access-control.png) ](media/dicom-access-control.png#lightbox)
+[![Screenshot of DICOM access control.](media/dicom-access-control.png)](media/dicom-access-control.png#lightbox)
 
 
 In the **Role** selection, search for one of the built-in roles for the DICOM data plane:
 
-[ ![Screenshot of add RBAC role assignment.](media/rbac-add-role-assignment.png) ](media/rbac-add-role-assignment.png#lightbox)
+[![Screenshot of add RBAC role assignment.](media/rbac-add-role-assignment.png)](media/rbac-add-role-assignment.png#lightbox)
 
 You can choose between:
 
 * DICOM Data Owner:  Full access to DICOM data.
 * DICOM Data Reader: Read and search DICOM data.
 
-If these roles aren't sufficient for your need, you can use PowerShell to create custom roles.  For information about creating custom roles, see [Create a custom role using Azure PowerShell](../../role-based-access-control/tutorial-custom-role-powershell.md).
+If these roles aren't sufficient for your need, you can use PowerShell to create custom roles. For information about creating custom roles, see [Create a custom role using Azure PowerShell](../../role-based-access-control/tutorial-custom-role-powershell.md).
 
 In the **Select** box, search for a user, service principal, or group that you want to assign the role to.
 

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

@@ -12,7 +12,7 @@ ms.custom: mode-api
 
 #  Manage medical imaging data with the DICOM service and Azure Data Lake Storage
 
-The [DICOM® service](overview.md) provides cloud-scale storage for medical imaging data using the DICOMweb standard. The integration of the DICOM service with Azure Data Lake Storage means you gain full control of your imaging data and increased flexibility for accessing and working with that data through the Azure storage ecosystem and APIs.  
+The [DICOM® service](overview.md) provides cloud-scale storage for medical imaging data using the DICOMweb standard. The integration of the DICOM service with Azure Data Lake Storage means you gain full control of your imaging data. It provides increased flexibility for accessing and working with that data through the Azure storage ecosystem and APIs.  
 
 By using Azure Data Lake Storage with the DICOM service, organizations are able to:
 
@@ -21,7 +21,7 @@ By using Azure Data Lake Storage with the DICOM service, organizations are able
 - **Unlock new analytics and AI/ML scenarios** by using services that natively integrate with Azure Data Lake Storage, including Azure Synapse, Azure Databricks, Azure Machine Learning, and Microsoft Fabric. 
 - **Grant controls to manage storage permissions, access controls, tiers, and rules**. 
 
-Another benefit of Azure Data Lake Storage is that it connects to [Microsoft Fabric](/fabric/get-started/microsoft-fabric-overview). Microsoft Fabric is an end-to-end, unified analytics platform that brings together all the data and analytics tools that organizations need to unlock the potential of their data and lay the foundation for AI scenarios. By using Microsoft Fabric, you can use the rich ecosystem of Azure services to perform advanced analytics and AI/ML with medical imaging data, such as building and deploying machine learning models, creating cohorts for clinical trials, and generating insights for patient care and outcomes.
+Another benefit of Azure Data Lake Storage is that it connects to [Microsoft Fabric](/fabric/get-started/microsoft-fabric-overview). Microsoft Fabric is an end-to-end, unified analytics platform that brings together all the data and analytics tools. Organizations then have a unified way to unlock the potential of their data, and lay the foundation for AI scenarios. By using Microsoft Fabric, you can use the rich ecosystem of Azure services to perform advanced analytics and AI/ML with medical imaging data. This could include building and deploying machine learning models, creating cohorts for clinical trials, and generating insights for patient care and outcomes.
 
 To learn more about using Microsoft Fabric with imaging data, see [Get started using DICOM data in analytics workloads](get-started-with-analytics-dicom.md).
 
@@ -51,7 +51,7 @@ In addition to DICOM data, a small file to enable [health checks](#health-check)
 
 ## Permissions
 
-The DICOM service is granted access to the data like any other service or application accessing data in a storage account. Access can be revoked at any time without affecting your organization's ability to access the data. The DICOM service needs the ability to read, write, and delete files in the provided file system. This can be provided by granting the [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) role to the system-assigned or user-assigned managed identity attached to the DICOM service.
+The DICOM service is granted access to the data like any other service or application accessing data in a storage account. Access can be revoked at any time without affecting your organization's ability to access the data. The DICOM service needs the ability to read, write, and delete files in the provided file system. This can be provided by granting the [Storage Blob Data Contributor](/azure/role-based-access-control/built-in-roles#storage-blob-data-contributor) role to the system-assigned, or user-assigned managed identity attached to the DICOM service.
 
 ## Access tiers
 
@@ -61,8 +61,8 @@ To learn more about access tiers, including cost tradeoffs and best practices, s
 
 ## Health check
 
-The DICOM service writes a small file to the data lake every 30 seconds, following the [Data Contract](#data-contracts) to ensure it maintains access. Making any changes to files stored under the `healthCheck` sub-directory might result in incorrect status of the health check.
-If there is an issue with access, status and details are displayed by [Azure Resource Health](../../service-health/overview.md). Azure Resource Health specifies if any action is required to restore access, for example reinstating a role to the DICOM service's identity.
+The DICOM service writes a small file to the data lake every 30 seconds, following the [Data Contract](#data-contracts) to ensure it maintains access. Making any changes to files stored under the `healthCheck` subdirectory might result in incorrect status of the health check.
+If there's an issue with access, status and details are displayed by [Azure Resource Health](../../service-health/overview.md). Azure Resource Health specifies if any action is required to restore access, for example reinstating a role to the DICOM service's identity.
 
 ## Limitations