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/dicom-extended-query-tags-overview.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
@@ -91,7 +91,7 @@ The following VR types are supported:
91
91
92
92
### List extended query tags
93
93
94
-
Lists of all extended query tag(s).
94
+
Lists of all extended query tags.
95
95
96
96
```http
97
97
GET .../extendedquerytags
@@ -229,7 +229,7 @@ GET .../operations/{operationId}
229
229
230
230
### Tag status
231
231
232
-
The [Status](#extended-query-tag-status) of extended query tag indicates current status. When an extended query tag is first added, its status is set to `Adding`, and a long-running operation is kicked off to reindex existing DICOM instances. After the operation is completed, the tag status is updated to `Ready`. The extended query tag can now be used in [QIDO](dicom-services-conformance-statement-v2.md#search-qido-rs).
232
+
The [Status](#extended-query-tag-status) of extended query tag indicates the current status. When an extended query tag is first added, its status is set to `Adding`, and a long-running operation is kicked off to reindex existing DICOM instances. After the operation is completed, the tag status is updated to `Ready`. The extended query tag can now be used in [QIDO](dicom-services-conformance-statement-v2.md#search-qido-rs).
233
233
234
234
For example, if the tag Manufacturer Model Name (0008,1090) is added, and in `Ready` status, hereafter the following queries can be used to filter stored instances by the Manufacturer Model Name.
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/dicom-register-application.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
@@ -18,28 +18,28 @@ In this article, you learn how to register a client application for the DICOM&re
18
18
1. In the [Azure portal](https://portal.azure.com), select **Microsoft Entra ID**.
19
19
1. Select **App registrations**.
20
20
21
-
[](media/register-application-one.png#lightbox)
21
+
[](media/register-application-one.png#lightbox)
22
22
23
23
1. Select **New registration**.
24
24
1. For **Supported account types**, select **Accounts in this organizational directory only**. Leave the other options as is.
25
25
26
-
[](media/register-application-two.png#lightbox)
26
+
[](media/register-application-two.png#lightbox)
27
27
28
28
1. Select **Register**.
29
29
30
30
## Application ID (client ID)
31
31
32
32
After you register a new application, you can find the **Application (client) ID** and **Directory (tenant) ID** from the **Overview** menu option. Make a note of the values for use later.
33
33
34
-
[](media/register-application-three.png#lightbox)
34
+
[](media/register-application-three.png#lightbox)
35
35
36
36
## Authentication setting: Confidential vs. public
37
37
38
38
Select **Authentication** to review the settings. The default value for **Allow public client flows** is **No**.
39
39
40
40
If you keep this default value, the application registration is a **confidential client application** and a certificate or secret is required.
41
41
42
-
[](media/register-application-five.png#lightbox)
42
+
[](media/register-application-five.png#lightbox)
43
43
44
44
If you change the default value to **Yes** for the **Allow public client flows** option in the **Advanced** setting, the application registration is a **public client application** and a certificate or secret isn't required. The **Yes** value is useful when you want to use the client application in your mobile app or a JavaScript app where you don't want to store any secrets.
45
45
@@ -48,15 +48,15 @@ For tools that require a redirect URL, select **Add a platform** to configure th
48
48
> [!NOTE]
49
49
> For Postman, select **Mobile and desktop applications**. Enter `https://www.getpostman.com/oauth2/callback` in the **Custom redirect URIs** section. Select **Configure** to save the setting.
50
50
51
-
[](media/register-application-five-bravo.png#lightbox)
51
+
[](media/register-application-five-bravo.png#lightbox)
52
52
53
53
## Certificates & secrets
54
54
55
55
Select **Certificates & secrets** and select **New client secret**.
56
56
57
-
Add and then copy the secret value.
57
+
Add, and then copy the secret value.
58
58
59
-
[](media/register-application-six.png#lightbox)
59
+
[](media/register-application-six.png#lightbox)
60
60
61
61
Optionally, you can upload a certificate (public key) and use the Certificate ID, a GUID value associated with the certificate. For testing purposes, you can create a self-signed certificate using tools such as the PowerShell command line, `New-SelfSignedCertificate`, and then export the certificate from the certificate store.
62
62
@@ -66,21 +66,21 @@ The following steps are required for the DICOM service. In addition, user access
66
66
67
67
1. Select the **API permissions** pane.
68
68
69
-
[](./media/dicom-add-apis-permissions.png#lightbox)
69
+
[](./media/dicom-add-apis-permissions.png#lightbox)
70
70
71
71
1. Select **Add a permission**.
72
72
73
73
Add a permission to the DICOM service by searching for **Azure API for DICOM** under **APIs my organization uses**.
74
74
75
-
[](./media/dicom-search-apis-permissions.png#lightbox)
75
+
[](./media/dicom-search-apis-permissions.png#lightbox)
76
76
77
77
The search result for Azure API for DICOM only returns if you've already deployed the DICOM service in the workspace.
78
78
79
79
If you're referencing a different resource application, select your DICOM API resource application registration that you created previously under **APIs my organization uses**.
80
80
81
81
1. Select scopes (permissions) that the confidential client application asks for on behalf of a user. Select **Dicom.ReadWrite**, and then select **Add permissions**.
82
82
83
-
[](./media/dicom-select-scopes-new.png#lightbox)
83
+
[](./media/dicom-select-scopes-new.png#lightbox)
Copy file name to clipboardExpand all lines: articles/healthcare-apis/dicom/dicom-service-v2-api-changes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ Failed validation of attributes not required by the API results in the file bein
26
26
A warning is given about each failing attribute per instance. When a sequence contains an attribute that fails validation, or when there are multiple issues with a single attribute, only the first failing attribute reason is noted.
27
27
28
28
There are some notable behaviors for optional attributes that fail validation:
29
-
* Searches for the attribute that failed validation returns the study/series/instance if the value is corrected in one of the few ways [mentioned below](#search-results-might-be-incomplete-for-extended-query-tags-with-validation-warnings).
29
+
* Searches for the attribute that failed validation returns the study/series/instance if the value is corrected in one of the few ways [mentioned here](#search-results-might-be-incomplete-for-extended-query-tags-with-validation-warnings).
30
30
* The attributes aren't returned when retrieving metadata via WADO `/metadata` endpoints.
31
31
32
32
Retrieving a study/series/instance always returns the original binary files with the original attributes, even if those attributes failed validation.
0 commit comments