GITBOOK-421: change request with no subject merged in GitBook

Author: fedorov

SUMMARY.md

@@ -28,6 +28,7 @@
 * [Data versioning](data/data-versioning.md)
 * [Organization of data](data/organization-of-data/README.md)
   * [Files and metadata](data/organization-of-data/files-and-metadata.md)
+  * [DICOM stores](data/organization-of-data/dicom-stores.md)
   * [Clinical data](data/organization-of-data/clinical.md)
   * [Resolving CRDC Globally Unique Identifiers (GUIDs)](data/organization-of-data/guids-and-uuids.md)
   * [Deprecated functionality](data/organization-of-data/deprecated-functionality/README.md)

data/organization-of-data/dicom-stores.md

@@ -0,0 +1,52 @@
+# DICOM stores
+
+If you would like to access IDC data via [DICOMweb interface](https://www.dicomstandard.org/using/dicomweb), you have two options: 
+
+1. IDC-maintained DICOM store available via proxy
+2. DICOM store maintained by Google Healthcare
+
+In the following we provide details for each of those options.
+
+### IDC-maintained DICOM store via proxy
+
+This store contains all of the data for the current IDC data release. It does not require authentication. and is available via the following DICOMweb URL of the proxy (you can ignore the "viewer-only-no-downloads" part in the URL, it is a legacy constraint that is no longer applicable).
+
+DICOMweb URL:
+
+{% code overflow="wrap" %}
+```
+https://proxy.imaging.datacommons.cancer.gov/current/viewer-only-no-downloads-see-tinyurl-dot-com-slash-3j3d9jyp/dicomWeb
+```
+{% endcode %}
+
+**Limitations**:
+
+* since all requests go through the proxy, you may experience reduced performance as compared to direct access you can achieve using the store described in the following section
+* there are per-IP and overall daily quotas, as described in IDC [Proxy policy](../../portal/proxy-policy.md), that may not be sufficient for your use case
+
+### DICOM store maintained by Google Healthcare
+
+This store replicates all of the data from the `idc-open-data` bucket (see related discussion on why IDC uses multiple cloud buckets to organize the data in [this forum thread](https://discourse.canceridc.dev/t/what-is-the-difference-between-the-three-aws-buckets/459)), which is limited to the data available without commercial use constraints (i.e., under CC-BY license), and does not have the data that was flagged by TCIA as potentially containing patient faces. 
+
+DICOMweb URL:
+
+{% code overflow="wrap" %}
+```
+https://healthcare.googleapis.com/v1/projects/nci-idc-data/locations/us-central1/datasets/idc/dicomStores/idc-store-v20/dicomWeb
+```
+{% endcode %}
+
+This DICOM store is documented in [https://cloud.google.com/healthcare-api/docs/resources/public-datasets/idc](https://cloud.google.com/healthcare-api/docs/resources/public-datasets/idc). 
+
+{% hint style="danger" %}
+As of Jul 1, 2025, [Google documentation page](https://cloud.google.com/healthcare-api/docs/resources/public-datasets/idc) incorrectly instructs users to request access in order to be whitelisted and able to access the store. In reality, anyone logged in with a Google account is able to access the store!
+{% endhint %}
+
+**Limitations**:
+
+* most, but not all of the IDC data is available in this store
+* authentication is required
+
+## DICOMweb usage tutorials
+
+We do not yet have a dedicated IDC tutorial on this topic. In the meantime, you can consult the Google Healthcare documentation page for instructions: [https://cloud.google.com/healthcare-api/docs/how-tos/dicomweb](https://cloud.google.com/healthcare-api/docs/how-tos/dicomweb), or use any other tutorial/resource on the use of DICOMweb!

data/organization-of-data/files-and-metadata.md

@@ -6,7 +6,7 @@ We gratefully acknowledge [Google Public Data Program](https://console.cloud.goo
 
 Let's start with the overall principles of how we organize data in IDC.
 
-IDC brings you (as of v18) over 60 TB of publicly available DICOM images and image-derived content. We share those with you as DICOM files, and those DICOM files are available in cloud-based **storage buckets** - both in Google and AWS. 
+IDC brings you (as of v21) over 85 TB of publicly available DICOM images and image-derived content. We share those with you as DICOM files, and those DICOM files are available in cloud-based **storage buckets** - both in Google and AWS. 
 
 Sharing just the files, however, is not particularly helpful. With that much data, it is no longer practical to just download all of those files to later sort through them to select those you need. 
 
@@ -444,6 +444,3 @@ and similarly for AWS buckets, thus making it easy to transfer all instances in
 
 Because file names are more or less opaque, the user will not typically select files by listing the contents of a bucket. Instead, one should use either the IDC Portal or IDC BigQuery tables to identify items of interest and, then, generate a manifest of objects that can be passed to a utility like s5cmd.
 
-## DICOM Stores
-
-IDC utilizes a single Google Healthcare DICOM store to host all of the instances in the current IDC version. That store, however, is primarily intended to support visualization of the data using the OHIF and Slim viewers. At this time, we do not support access of the hosted data via DICOMWeb interface by IDC users. See more details in the [discussion here](https://discourse.canceridc.dev/t/dicomweb-access-to-hosted-collections/69), and please comment about your use case if you have a need to access data via the DICOMweb interface.