Skip to content

Commit 7fb0ea2

Browse files
authored
Update docs
1 parent acafc71 commit 7fb0ea2

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/healthcare-apis/dicom/external-metadata.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ ms.author: kabalas
1111

1212
# External metadata
1313

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

1616
## Limiations
1717

1818
- 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.
2020
- Only study level tags are supported.
2121
- External metadata tags cannot be updated or deleted.
2222
- The following VR types are supported:
@@ -66,11 +66,11 @@ Body:
6666
> Only study level tags are supported.
6767
> If the tag already exists, it will update the value of the existing tag for the study.
6868
> 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.
7070
7171
### Retrieve metadata (for study, series, or instance)
7272

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.
7474

7575
```http
7676
GET {dicom-service-url}/{version}/studies/{study}/series/{series}/instances/{instance}/metadata
@@ -86,7 +86,7 @@ Content-Type: application/dicom
8686
8787
### Search (QIDO-RS)
8888

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.
9090

9191
```http
9292
GET {dicom-service-url}/{version}/studies?00191100=PersonName

0 commit comments

Comments
 (0)