You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/enable-diagnostic-logging.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ ms.date: 10/13/2023
9
9
ms.author: buchvarun
10
10
---
11
11
12
-
# Enable audit and diagnostic logging in the DICOM® service
12
+
# Enable audit and diagnostic logging in the DICOM service
13
13
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.
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`.
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/get-access-token.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
2
title: Get an access token for the DICOM service in Azure Health Data Services
3
3
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
5
5
ms.service: azure-health-data-services
6
6
ms.subservice: dicom-service
7
7
ms.custom:
8
8
ms.topic: how-to
9
9
ms.date: 10/13/2023
10
-
ms.author: mmitrik
10
+
ms.author: buchvarun
11
11
---
12
12
13
13
# Get an access token
14
14
15
-
To use the DICOM® 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® 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.
16
16
17
17
## Use the Azure command-line interface
18
18
@@ -27,8 +27,8 @@ To assign roles and grant access to the DICOM service:
27
27
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).
28
28
29
29
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
32
32
33
33
## Get a token
34
34
@@ -46,7 +46,7 @@ To get an access token using Azure CLI:
46
46
47
47
#### Store a token in a variable
48
48
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.
* 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).
58
58
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).
60
60
61
61
* 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).
62
62
63
63
## Use a token with the DICOM service
64
64
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.
66
66
67
67
```cURL
68
68
-X GET --header "Authorization: Bearer $token" https://<workspacename-dicomservicename>.dicom.azurehealthcareapis.com/v<version of REST API>/changefeed
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/import-files.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,21 @@
1
1
---
2
2
title: Import DICOM files into the DICOM service
3
3
description: Learn how to import DICOM files by using bulk import in Azure Health Data Services.
4
-
author: mmitrik
4
+
author: varunbms
5
5
ms.service: azure-health-data-services
6
6
ms.subservice: dicom-service
7
7
ms.topic: quickstart
8
8
ms.date: 10/05/2023
9
-
ms.author: mmitrik
9
+
ms.author: buchvarun
10
10
---
11
11
12
12
# Import DICOM files (preview)
13
13
14
14
Bulk import is a quick way to add data to the DICOM® service. Importing DICOM files with the bulk import capability enables:
15
15
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.
17
17
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.
19
19
20
20
## Prerequisites
21
21
@@ -40,19 +40,19 @@ Before you perform a bulk import, you need to enable a system-assigned managed i
40
40
41
41
You need to enable bulk import before you import data.
42
42
43
-
####Use the Azure portal
43
+
### Use the Azure portal
44
44
45
45
1. In the Azure portal, go to the DICOM service and then select **Bulk Import** from the left pane.
46
46
47
47
1. On the **Bulk Import** page, in the **Bulk Import** field, select **Enabled**. Select **Save**.
48
48
49
49
:::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":::
50
50
51
-
####Use an Azure Resource Manager template
51
+
### Use an Azure Resource Manager template
52
52
53
53
When you use an Azure Resource Manager template (ARM template), enable bulk import with the property named `bulkImportConfiguration`.
54
54
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.
56
56
57
57
```json
58
58
{
@@ -82,13 +82,13 @@ Within the new resource group, two resources are created:
82
82
83
83
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`.
84
84
85
-
####Grant write access to the import container
85
+
### Grant write access to the import container
86
86
87
87
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).
88
88
89
-
####Upload DICOM images to the import container
89
+
### Upload DICOM images to the import container
90
90
91
-
Data is uploaded to Azure Storage containers in many ways:
91
+
Data is uploaded to Azure Storage containers in many ways.
92
92
93
93
-[Upload a blob with Azure Storage Explorer](../../storage/blobs/quickstart-storage-explorer.md#upload-blobs-to-the-container)
94
94
-[Upload a blob with AzCopy](../../storage/common/storage-use-azcopy-blobs-upload.md)
0 commit comments