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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,12 @@ ms.author: kabalas
11
11
12
12
# External metadata
13
13
14
-
The external metadata feature allows to store the metadata or additional information about the DICOM files that is not part of the DICOM file. For e.g, using the same (STOW-RS), you can 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 is not part of the DICOM file. This is accomplished by using STOW-RS to store the metadata by passing the additional information in the header.
15
15
16
16
## Limiations
17
17
18
18
- External metadata is only supported in latest api version. i.e Version 2 or above
19
-
- Only private dicom tags are supported to be as external metadata.
19
+
- 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.
20
20
- Only study level tags are supported.
21
21
- External metadata tags cannot be updated or deleted.
22
22
- The following VR types are supported:
@@ -66,11 +66,11 @@ Body:
66
66
> Only study level tags are supported.
67
67
> If the tag already exists, it will update the value of the existing tag for the study.
68
68
> If the tag already exists with different VR, then it will results in an error.
69
-
> All the tag values must follow the standard for their respective VR. If there is an issue with one of the tags, then it will fail the whole transaction.
69
+
> 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 will fail the whole transaction.
70
70
71
71
### Retrieve metadata (for study, series, or instance)
72
72
73
-
The [Retrieve metadata (for study, series, or instance)](dicom-services-conformance-statement-v2.md#retrieve-metadata-for-study-series-or-instance) transaction allows to retrieve the external metadata along with other metadata. The external metadata is retrieved along with other tags by setting the `msdicom-request-meta` header to `true`. An example request follows.
73
+
The [Retrieve metadata (for study, series, or instance)](dicom-services-conformance-statement-v2.md#retrieve-metadata-for-study-series-or-instance) transaction allows users to retrieve the external metadata along with other metadata. The external metadata is retrieved along with other tags by setting the `msdicom-request-meta` header to `true`. An example request follows.
74
74
75
75
```http
76
76
GET {dicom-service-url}/{version}/studies/{study}/series/{series}/instances/{instance}/metadata
@@ -86,7 +86,7 @@ Content-Type: application/dicom
86
86
87
87
### Search (QIDO-RS)
88
88
89
-
The [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs) transaction allows to query external metadata similar to other tags. The external metadata can be queried by setting the `msdicom-request-meta` header to `true`. An example request follows.
89
+
The [Search (QIDO-RS)](dicom-services-conformance-statement-v2.md#search-qido-rs) transaction allows users to query external metadata similar to other tags. The external metadata can be queried by setting the `msdicom-request-meta` header to `true`. An example request follows.
90
90
91
91
```http
92
92
GET {dicom-service-url}/{version}/studies?00191100=PersonName
0 commit comments