Skip to content

Commit 14bd01a

Browse files
committed
author update; markdown cleanup and edits
1 parent 47dd771 commit 14bd01a

File tree

4 files changed

+21
-21
lines changed

4 files changed

+21
-21
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ ms.date: 10/13/2023
99
ms.author: buchvarun
1010
---
1111

12-
# Enable audit and diagnostic logging in the DICOM® service
12+
# Enable audit and diagnostic logging in the DICOM service
1313

14-
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.
14+
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.
1515

1616
## Enable logs
1717

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ Content-Type: application/json
178178

179179
## Errors
180180

181-
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`.
181+
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`.
182182

183183
#### Format
184184

articles/healthcare-apis/dicom/get-access-token.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
22
title: Get an access token for the DICOM service in Azure Health Data Services
33
description: Find out how to secure your access to the DICOM service with a token. Use the Azure command-line tool and unique identifiers to manage your medical images.
4-
author: mmitrik
4+
author: varunbms
55
ms.service: azure-health-data-services
66
ms.subservice: dicom-service
77
ms.custom:
88
ms.topic: how-to
99
ms.date: 10/13/2023
10-
ms.author: mmitrik
10+
ms.author: buchvarun
1111
---
1212

1313
# Get an access token
1414

15-
To use the DICOM&reg; service, users and applications need to prove their identity and permissions by getting an access token. An access token is a string that identifies a user or an application and grants them permission to access a resource. Using access tokens enhances security by preventing unauthorized access and reducing the need for repeated authentication.
15+
To use the DICOM&reg; service, users and applications need to prove their identity and permissions by getting an access token. An access token is a string that identifies a user or an application, and grants them permission to access a resource. Using access tokens enhances security by preventing unauthorized access and reducing the need for repeated authentication.
1616

1717
## Use the Azure command-line interface
1818

@@ -27,8 +27,8 @@ To assign roles and grant access to the DICOM service:
2727
1. Register a client application in Microsoft Entra ID that acts as your identity provider and authentication mechanism. Use Azure portal, PowerShell, or Azure CLI to [register an application](dicom-register-application.md).
2828

2929
1. Assign one of the built-in roles for the DICOM data plane to the client application. The roles are:
30-
- **DICOM Data Owner**. Gives full access to DICOM data.
31-
- **DICOM Data Reader**. Allows read and search operations on DICOM data.
30+
- **DICOM Data Owner**. Gives full access to DICOM data
31+
- **DICOM Data Reader**. Allows read and search operations on DICOM data
3232

3333
## Get a token
3434

@@ -46,7 +46,7 @@ To get an access token using Azure CLI:
4646

4747
#### Store a token in a variable
4848

49-
The DICOM service uses a `resource` or `Audience` with uniform resource identifier (URI) equal to the URI of the DICOM server `https://dicom.healthcareapis.azure.com`. You can obtain a token and store it in a variable (named `$token`) with the following command:
49+
The DICOM service uses a `resource` or `Audience`, with uniform resource identifier (URI) equal to the URI of the DICOM server `https://dicom.healthcareapis.azure.com`. You can obtain a token and store it in a variable (named `$token`) with the following command.
5050

5151
```cURL
5252
$token=$(az account get-access-token --resource=https://dicom.healthcareapis.azure.com --query accessToken --output tsv)
@@ -56,13 +56,13 @@ $token=$(az account get-access-token --resource=https://dicom.healthcareapis.azu
5656

5757
* If you're using a local installation, sign in to the Azure CLI with the [az login](/cli/azure/reference-index#az-login) command. To finish authentication, follow the on-screen steps. For more information, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
5858

59-
* If prompted, install Azure CLI extensions on first use. For more information, see [Use extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
59+
* If prompted on first use, install Azure CLI extensions. For more information, see [Use extensions with the Azure CLI](/cli/azure/azure-cli-extensions-overview).
6060

6161
* Run [az version](/cli/azure/reference-index#az-version) to find the version and dependent libraries that are installed. To upgrade to the latest version, run [az upgrade](/cli/azure/reference-index#az-upgrade).
6262

6363
## Use a token with the DICOM service
6464

65-
You can use a token with the DICOM service [using cURL](dicomweb-standard-apis-curl.md). Here's an example:
65+
You can use a token with the DICOM service [using cURL](dicomweb-standard-apis-curl.md). Following is an example.
6666

6767
```cURL
6868
-X GET --header "Authorization: Bearer $token" https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com/v<version of REST API>/changefeed

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

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
11
---
22
title: Import DICOM files into the DICOM service
33
description: Learn how to import DICOM files by using bulk import in Azure Health Data Services.
4-
author: mmitrik
4+
author: varunbms
55
ms.service: azure-health-data-services
66
ms.subservice: dicom-service
77
ms.topic: quickstart
88
ms.date: 10/05/2023
9-
ms.author: mmitrik
9+
ms.author: buchvarun
1010
---
1111

1212
# Import DICOM files (preview)
1313

1414
Bulk import is a quick way to add data to the DICOM&reg; service. Importing DICOM files with the bulk import capability enables:
1515

16-
- **Backup and migration**: For example, your organization might have many DICOM instances stored in local or on-premises systems that you want to back up or migrate to the cloud for better security, scalability, and availability. Rather than uploading the data one by one, use bulk import to transfer the data faster and more efficiently.
16+
- **Backup and migration**. For example, your organization might have many DICOM instances stored in local or on-premises systems, which you may want to back up or migrate to the cloud for better security, scalability, and availability. Rather than uploading the data one by one, use bulk import to transfer the data faster and more efficiently.
1717

18-
- **Machine learning development**: For example, your organization might have a large dataset of DICOM instances that you want to use for training machine learning models. With bulk import, you can upload the data to the DICOM service and then access it from [Microsoft Fabric](get-started-with-analytics-dicom.md), [Azure Machine Learning](/azure/machine-learning/overview-what-is-azure-machine-learning), or other tools.
18+
- **Machine learning development**. For example, your organization might have a large dataset of DICOM instances that you want to use for training machine learning models. With bulk import, you can upload the data to the DICOM service and then access it from [Microsoft Fabric](get-started-with-analytics-dicom.md), [Azure Machine Learning](/azure/machine-learning/overview-what-is-azure-machine-learning), or other tools.
1919

2020
## Prerequisites
2121

@@ -40,19 +40,19 @@ Before you perform a bulk import, you need to enable a system-assigned managed i
4040

4141
You need to enable bulk import before you import data.
4242

43-
#### Use the Azure portal
43+
### Use the Azure portal
4444

4545
1. In the Azure portal, go to the DICOM service and then select **Bulk Import** from the left pane.
4646

4747
1. On the **Bulk Import** page, in the **Bulk Import** field, select **Enabled**. Select **Save**.
4848

4949
:::image type="content" source="media/import-enable.png" alt-text="Screenshot that shows the Bulk Import page with the toggle set to Enabled." lightbox="media/import-enable.png":::
5050

51-
#### Use an Azure Resource Manager template
51+
### Use an Azure Resource Manager template
5252

5353
When you use an Azure Resource Manager template (ARM template), enable bulk import with the property named `bulkImportConfiguration`.
5454

55-
Here's an example of how to configure bulk import in an ARM template:
55+
Following is an example of how to configure bulk import in an ARM template.
5656

5757
``` json
5858
{
@@ -82,13 +82,13 @@ Within the new resource group, two resources are created:
8282

8383
DICOM images are added to the DICOM service by copying them into the `import-container`. Bulk import monitors this container for new images and adds them to the DICOM service. If there are errors that prevent a file from being added successfully, the errors are copied to the `error-container` and an error message is written to the `error-queue`.
8484

85-
#### Grant write access to the import container
85+
### Grant write access to the import container
8686

8787
The user or account that adds DICOM images to the import container needs write access to the container by using the `Data Owner` role. For more information, see [Assign Azure roles using the Azure portal](../../role-based-access-control/role-assignments-portal.yml).
8888

89-
#### Upload DICOM images to the import container
89+
### Upload DICOM images to the import container
9090

91-
Data is uploaded to Azure Storage containers in many ways:
91+
Data is uploaded to Azure Storage containers in many ways.
9292

9393
- [Upload a blob with Azure Storage Explorer](../../storage/blobs/quickstart-storage-explorer.md#upload-blobs-to-the-container)
9494
- [Upload a blob with AzCopy](../../storage/common/storage-use-azcopy-blobs-upload.md)

0 commit comments

Comments
 (0)