Merge pull request #285919 from KendalBond007/DICOMeditsBatch3_Aug24

DICOMeditsBatch3_Aug24

Author: Court72

articles/healthcare-apis/dicom/enable-diagnostic-logging.md

@@ -1,124 +1,123 @@
 ---
 title: Enable diagnostic logging in the DICOM service - Azure Health Data Services
 description: This article explains how to enable diagnostic logging in the DICOM service.
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: conceptual
 ms.date: 10/13/2023
-ms.author: mmitrik
+ms.author: buchvarun
 ---
 
 # Enable audit and diagnostic logging in the DICOM service
 
-In this article, you'll learn how to enable diagnostic logging in DICOM service and be able to review some sample queries for these logs. Access to diagnostic logs is essential for any healthcare service where compliance with regulatory requirements is a must. The feature in DICOM service enables diagnostic logs is the [Diagnostic settings](../../azure-monitor/essentials/diagnostic-settings.md) in the Azure portal. 
+In this article, you'll learn how to enable diagnostic logging in DICOM® service and be able to review some sample queries for these logs. Access to diagnostic logs is essential for any healthcare service where compliance with regulatory requirements is required. The feature in DICOM service that enables diagnostic logs is the [Diagnostic settings](../../azure-monitor/essentials/diagnostic-settings.md) in the Azure portal. 
 
 ## Enable logs
 
 1. To enable logging DICOM service, select your DICOM service in the Azure portal.
 2. Select the **Activity log** on the left pane, and then select **Diagnostic settings**.
 
-   [ ![Screenshot of Azure activity log.](media/dicom-activity-log.png) ](media/dicom-activity-log.png#lightbox)
+   [![Screenshot of Azure activity log.](media/dicom-activity-log.png)](media/dicom-activity-log.png#lightbox)
 
 3. Select **+ Add diagnostic setting**.
 
-   [ ![Screenshot of Add Diagnostic settings.](media/add-diagnostic-settings.png) ](media/add-diagnostic-settings.png#lightbox)
+   [![Screenshot of Add Diagnostic settings.](media/add-diagnostic-settings.png)](media/add-diagnostic-settings.png#lightbox)
 
 4. Enter the **Diagnostic settings name**.
 
-   [ ![Screenshot of Configure Diagnostic settings.](media/configure-diagnostic-settings.png) ](media/configure-diagnostic-settings.png#lightbox)
+   [![Screenshot of Configure Diagnostic settings.](media/configure-diagnostic-settings.png)](media/configure-diagnostic-settings.png#lightbox)
 
-5. Select the **Category** and **Destination** details for accessing the diagnostic logs.
+5. Select the **Category** and **Destination** details for accessing the diagnostic logs:
 
    * **Send to Log Analytics workspace** in the Azure Monitor. You need to create your Logs Analytics workspace before you can select this option. For more information about the platform logs, see [Overview of Azure platform logs](../../azure-monitor/essentials/platform-logs-overview.md).
-   * **Archive to a storage account** for auditing or manual inspection. The storage account you want to use needs to be already created.
+   * **Archive to a storage account** for auditing or manual inspection. The storage account you want to use needs to already be created.
    * **Stream to an event hub** for ingestion by a third-party service or custom analytic solution. You need to create an event hub namespace and event hub policy before you can configure this step.
-   * **Send to partner solution** that you're working with as partner organization in Azure. For information about potential partner integrations, see [Azure partner solutions documentation](../../partner-solutions/overview.md)
+   * **Send to partner solution** that you're working with as a partner organization in Azure. For information about potential partner integrations, see [Azure partner solutions documentation](../../partner-solutions/overview.md)
 
      For information about supported metrics, see [Supported metrics with Azure Monitor](.././../azure-monitor/essentials/metrics-supported.md).
 
 6. Select **Save**.
 
-
    > [!Note] 
-   > It might take up to 15 minutes for the first Logs to show in Log Analytics. Also, if the DICOM service is moved from one resource group or subscription to another, update the settings once the move is complete. 
+   > It might take up to 15 minutes for the first Logs to appear in Log Analytics. Also, if the DICOM service is moved from one resource group or subscription to another, update the settings once the move is complete. 
  
    For information on how to work with diagnostic logs, see [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md)
 
 ## Log details
-The log schema used differs based on the destination. Log Analytics has a schema that differs from other destinations. Each log type has a schema that differs.
+The log schema used differs based on the destination. Log Analytics has a schema that differs from other destinations. Each log type has a different schema.
 
 ### Audit log details
 
 #### Raw logs
 
-The DICOM service returns the following fields in the audit log as seen when streamed outside of Log Analytics: 
+The DICOM service returns the following fields in the audit log as seen when streamed outside of Log Analytics.
 
 |Field Name  |Type  |Notes  |
 |---------|---------|---------|
-|correlationId|String|Correlation ID
-|operationName|String|Describes the type of operation (for example, Retrieve, Store, Query, etc.) 
-|time|DateTime|Date and time of the event. 
-|resourceId|String| Azure path to the resource.
-|identity|Dynamic|A generic property bag containing identity information (currently doesn't apply to DICOM).
-|location|String|The location of the server that processed the request.
-|uri|String|The request URI.
-|resultType|String| The available values currently are Started, Succeeded, or Failed.
-|resultSignature|Int|The HTTP Status Code (for example, 200)
-|type|String|Type of log (it's always MicrosoftHealthcareApisAuditLog in this case).
-|level|String|Log level (Informational, Error).
+| correlationId | String | Correlation ID |
+| operationName | String | Describes the type of operation (for example, Retrieve, Store, Query, etc.) |
+|time | DateTime | Date and time of the event. |
+|resourceId | String | Azure path to the resource. |
+|identity | Dynamic | A generic property bag containing identity information (currently doesn't apply to DICOM). |
+| location | String | The location of the server that processed the request. |
+| uri | String | The request URI. |
+| resultType | String | The available values currently are Started, Succeeded, or Failed. |
+| resultSignature | Int | The HTTP Status Code (for example, 200) |
+| type | String | Type of log (it's always MicrosoftHealthcareApisAuditLog in this case). |
+| level | String | Log level (Informational, Error). |
 
 
 #### Log Analytics logs
 
-The DICOM service returns the following fields in the audit sign-in Log Analytics: 
+The DICOM service returns the following fields in the audit sign-in Log Analytics.
 
 |Field Name  |Type  |Notes  |
 |---------|---------|---------|
-|CorrelationId|String|Correlation ID
-|OperationName|String|Describes the type of operation (for example, Retrieve, Store, Query, etc.) 
-|TimeGenerated [UTC]|DateTime|Date and time of the event. 
-|_ResourceId|String| Azure path to the resource.
-|Identity|Dynamic|A generic property bag containing identity information (currently doesn't apply to DICOM).
-|Uri|String|The request URI.
-|ResultType|String| The available values currently are Started, Succeeded, or Failed.
-|StatusCode|Int|The HTTP Status Code (for example, 200)
-|Type|String|Type of log (it's always AHDSDicomAuditLogs in this case).
-|Level|String|Log level (Informational, Error).
-|TenantId|String| Tenant ID.
+| CorrelationId | String | Correlation ID |
+| OperationName | String | Describes the type of operation (for example, Retrieve, Store, Query, etc.) |
+| TimeGenerated [UTC] | DateTime | Date and time of the event. |
+| _ResourceId | String | Azure path to the resource. |
+| Identity | Dynamic | A generic property bag containing identity information (currently doesn't apply to DICOM). |
+| Uri | String | The request URI. |
+| ResultType | String | The available values currently are Started, Succeeded, or Failed. |
+| StatusCode | Int | The HTTP Status Code (for example, 200) |
+| Type|String | Type of log (it's always AHDSDicomAuditLogs in this case). |
+| Level | String | Log level (Informational, Error). |
+| TenantId | String | Tenant ID. |
 
 
 ### Diagnostic log details
 
 #### Raw logs
 
-The DICOM service returns the following fields in the audit log as seen when streamed outside of Log Analytics: 
+The DICOM service returns the following fields in the audit log as seen when streamed outside of Log Analytics.
 
 |Field Name  |Type  |Notes  |
 |---------|---------|---------|
-|correlationId|String|Correlation ID
-|operationName|String|Describes the type of operation (for example, Retrieve, Store, Query, etc.) 
-|time|DateTime|Date and time of the event. 
-|resultDescription|String|Description of the log entry. An example is a diagnostic log with a validation warning message when storing a file.
-|resourceId|String| Azure path to the resource.
-|identity|Dynamic|A generic property bag containing identity information (currently doesn't apply to DICOM).
-|location|String|The location of the server that processed the request.
-|properties|String|Additional information about the event in JSON array format. Examples include DICOM identifiers present in the request.
-|level|String|Log level (Informational, Error).
+| correlationId | String | Correlation ID |
+| operationName | String | Describes the type of operation (for example, Retrieve, Store, Query, etc.) |
+| time | DateTime | Date and time of the event. |
+| resultDescription | String | Description of the log entry. An example is a diagnostic log with a validation warning message when storing a file. |
+| resourceId | String | Azure path to the resource. |
+| identity | Dynamic | A generic property bag containing identity information (currently doesn't apply to DICOM). |
+| location | String | The location of the server that processed the request. |
+| properties | String | Additional information about the event in JSON array format. Examples include DICOM identifiers present in the request. |
+| level | String | Log level (Informational, Error). |
 
 #### Log Analytics logs
 
-The DICOM service returns the following fields in the audit sign-in Log Analytics: 
+The DICOM service returns the following fields in the audit sign-in Log Analytics.
 
 |Field Name  |Type  |Notes  |
 |---------|---------|---------|
-|CorrelationId|String|Correlation ID
-|OperationName|String|Describes the type of operation (for example, Retrieve, Store, Query, etc.) 
-|TimeGenerated|DateTime|Date and time of the event. 
-|Message|String|Description of the log entry. An example is a diagnostic log with a validation warning message when storing a file.
-|Location|String|The location of the server that processed the request.
-|Properties|String|Additional information about the event in JSON array format. Examples include DICOM identifiers present in the request.
-|LogLevel|String|Log level (Informational, Error).
+| CorrelationId | String | Correlation ID |
+| OperationName | String | Describes the type of operation (for example, Retrieve, Store, Query, etc.) |
+| TimeGenerated | DateTime | Date and time of the event. |
+| Message | String | Description of the log entry. An example is a diagnostic log with a validation warning message when storing a file. |
+| Location | String | The location of the server that processed the request. |
+| Properties | String | Additional information about the event in JSON array format. Examples include DICOM identifiers present in the request. |
+| LogLevel | String | Log level (Informational, Error). |
 
 ## Sample Log Analytics queries
 

articles/healthcare-apis/dicom/export-files.md

@@ -1,12 +1,12 @@
 ---
 title: Export DICOM files by using the export API of the DICOM service
 description: This how-to guide explains how to export DICOM files to an Azure Blob Storage account.
-author: mmitrik
+author: varunbms
 ms.service: azure-health-data-services
 ms.subservice: dicom-service
 ms.topic: how-to
 ms.date: 10/30/2023
-ms.author: mmitrik
+ms.author: buchvarun
 ---
 
 # Export DICOM files
@@ -23,7 +23,7 @@ There are three steps to exporting data from the DICOM service:
 
 The first step to export data from the DICOM service is to enable a system-assigned managed identity. This managed identity is used to authenticate the DICOM service and give permission to the storage account used as the destination for export. For more information about managed identities in Azure, see [About managed identities for Azure resources](../../active-directory/managed-identities-azure-resources/overview.md).
 
-1. In the Azure portal, browse to the DICOM service that you want to export from and select **Identity**.
+1. In the Azure portal, browse to the DICOM service that you want to export from, and select **Identity**.
 
    :::image type="content" source="media/dicom-export-identity.png" alt-text="Screenshot that shows selection of Identity view." lightbox="media/dicom-export-identity.png":::
 
@@ -63,9 +63,9 @@ The export API exposes one `POST` endpoint for exporting data.
 POST <dicom-service-url>/<version>/export
 ```
 
-Given a *source*, the set of data to be exported, and a *destination*, the location to which data is exported, the endpoint returns a reference to a new, long-running export operation. The duration of this operation depends on the volume of data to be exported. For more information about monitoring progress of export operations, see the [Operation status](#operation-status) section.
+Given a *source*, the set of data to be exported, and a *destination* (the location to which data is exported), the endpoint returns a reference to a new, long-running export operation. The duration of this operation depends on the volume of data to be exported. For more information about monitoring progress of export operations, see the [Operation status](#operation-status) section.
 
-Any errors encountered while you attempt to export are recorded in an error log. For more information, see the [Errors](#errors) section.
+Any errors encountered while attempting to export are recorded in an error log. For more information, see the [Errors](#errors) section.
 
 #### Request
 
@@ -95,15 +95,15 @@ The request body consists of the export source and destination.
 The only setting is the list of identifiers to export.
 
 | Property | Required | Default | Description |
-| :------- | :------- | :------ | :---------- |
+| -------- | -------- | ------- | ----------- |
 | `Values` | Yes      |         | A list of one or more DICOM studies, series, and/or SOP instance identifiers in the format of `"<StudyInstanceUID>[/<SeriesInstanceUID>[/<SOPInstanceUID>]]"` |
 
 #### Destination settings
 
 The connection to the Blob Storage account is specified with `BlobContainerUri`.
 
 | Property             | Required | Default | Description |
-| :------------------- | :------- | :------ | :---------- |
+| -------------------- | -------- | ------- | ----------- |
 | `BlobContainerUri`   | No       | `""`    | The complete URI for the blob container |
 | `UseManagedIdentity` | Yes      | `false` | A required flag that indicates whether managed identity should be used to authenticate to the blob container |
 
@@ -142,7 +142,7 @@ Content-Type: application/json
 
 #### Response
 
-The export API returns a `202` status code when an export operation is started successfully. The body of the response contains a reference to the operation, while the value of the `Location` header is the URL for the export operation's status (the same as `href` in the body).
+The export API returns a `202` status code when an export operation is started successfully. The body of the response contains a reference to the operation. The value of the `Location` header is the URL for the export operation's status (the same as `href` in the body).
 
 Inside the destination container, use the path format `<operation id>/results/<study>/<series>/<sop instance>.dcm` to find the DCM files.
 
@@ -178,11 +178,11 @@ Content-Type: application/json
 
 ## Errors
 
-If there are any user errors when you export a DICOM file, the file is skipped and its corresponding error is logged. This error log is also exported alongside the DICOM files and the caller can review it. You can find the error log at `<export blob container uri>/<operation ID>/errors.log`.
+If there are any user errors exporting a DICOM file, the file is skipped and its corresponding error is logged. This error log is also exported alongside the DICOM files, and the caller can review it. You can find the error log at `<export blob container uri>/<operation ID>/errors.log`.
 
 #### Format
 
-Each line of the error log is a JSON object with the following properties. A given error identifier might appear multiple times in the log as each update to the log is processed *at least once*.
+Each line of the error log is a JSON object with the following properties. A given error identifier might appear multiple times in the log, as each update to the log is processed *at least once*.
 
 | Property     | Description |
 | ------------ | ----------- |