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/external-metadata.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Store external metadata in the DICOM service in Azure Health Data Services
3
-
description: Learn how to store, retrieve, and query external metadata that are not part of the DICOM files in the DICOM service
3
+
description: Learn how to store, retrieve, and query external metadata that aren't part of the DICOM files in the DICOM service
4
4
author: kabalas
5
5
ms.service: azure-health-data-services
6
6
ms.subservice: dicom-service
@@ -11,15 +11,15 @@ ms.author: kabalas
11
11
12
12
# External metadata
13
13
14
-
The external metadata feature allows users to store metadata or additional information about the DICOM files that is not part of the DICOM file. This fuctionality is accomplished by using STOW-RS to store the metadata by passing the additional information in the header.
14
+
The external metadata feature allows users to store metadata or additional information about the DICOM files that isn't part of the DICOM file. This fuctionality is accomplished by using STOW-RS to store the metadata by passing the additional information in the header.
15
15
16
16
## Limitations
17
17
18
18
- External metadata is only supported in latest api version. i.e. Version 2 or above
19
19
- External metadata is only supported in [DICOM® service with Azure Data Lake Storage](dicom-data-lake.md)
20
20
- Only tags which don't conform with standard DICOM protocol tags such as [private tags](https://dicom.nema.org/dicom/2013/output/chtml/part05/sect_7.8.html) are supported to be as external metadata.
21
21
- Only study level tags are supported.
22
-
- External metadata tags cannot be updated or deleted.
22
+
- External metadata tags can't be updated or deleted.
23
23
- The following VR types are supported:
24
24
25
25
| VR | Description | Single Value Matching | Range Matching | Fuzzy Matching |
@@ -44,8 +44,8 @@ The external metadata feature allows users to store metadata or additional infor
44
44
45
45
> [!NOTE]
46
46
> Sequential tags, which are tags under a tag of type Sequence of Items (SQ), are currently not supported.
47
-
> We do not index external metadata tags if the value is null or empty.
48
-
> There is no ability to add private creator as part of external metadata tags.
47
+
> We don't index external metadata tags if the value is null or empty.
48
+
> There's no ability to add private creator as part of external metadata tags.
49
49
50
50
### Store (STOW-RS)
51
51
@@ -67,7 +67,7 @@ Body:
67
67
> Only study level tags are supported.
68
68
> If the tag already exists, it updates the value of the existing tag for the study.
69
69
> If the tag already exists with different VR, then it will results in an error.
70
-
> Once a tag is created, its Value Representation (VR) is fixed and must comply with the standard for that specific VR. If there is an issue with one of the tags, then it fails the whole transaction.
70
+
> Once a tag is created, its Value Representation (VR) is fixed and must comply with the standard for that specific VR. If there's an issue with one of the tags, then it fails the whole transaction.
71
71
72
72
### Retrieve metadata (for study, series, or instance)
73
73
@@ -97,7 +97,7 @@ Content-Type: application/dicom
97
97
98
98
> [!NOTE]
99
99
> Only study level tags are supported.
100
-
> If there is an extended query tag with the same tagPath, but if the header `msdicom-request-meta` is set to `true`, then value from the external metadata is used to filter or to be included as part of response data.
100
+
> If there's an extended query tag with the same tagPath, but if the header `msdicom-request-meta` is set to `true`, then value from the external metadata is used to filter or to be included as part of response data.
0 commit comments