DICOM storage and transport
Stay organized with collections
Save and categorize content based on your preferences.
HAI-DEF endpoints that deal with DICOM imaging, such as
Path Foundation
and
CXR Foundation,
are capable of retrieving their input data from
DICOM storage
systems that meet the following requirements:
DICOM standard storage
HAI-DEF endpoints require DICOM imaging to conform to the
DICOM standard. This includes defining all
required
Type-1 tags
and ensuring that tag values comply with their specified
Value Representation (VR)
and
Value Multiplicity (VM)
codes.
DICOMweb transport protocol
HAI-DEF endpoints require the DICOM storage system holding the imaging to
support the DICOMweb REST API
and more specifically JSON formatted
QIDO-RS and
WADO-RS
over HTTPS protocol.
The Uniform Resource Identifiers (URIs) must end with a valid DICOMweb suffix:
for example the URI for a
DICOM series
must end with a studies/${STUDY-UID}/series/${SERIES-UID} suffix.
Transfer syntax transcoding
HAI-DEF endpoints transcode their DIOCM inputs based on the
Transfer Syntax UID.
Refer to the respective serving API specification for details.
Private network accessibility
HAI-DEF endpoints operate within the secure Google Cloud private network as
Vertex AI prediction endpoints.
Therefore, if you plan to use HAI-DEF endpoints with DICOMWeb data links, the
DICOMWeb store has to be accessible from this private network. Refer to
Google Cloud private access options.
Authentication and authorization
The DICOMweb storage system either must support public access or accept
OAuth 2.0 bearer tokens for
authorization.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-11 UTC."],[[["\u003cp\u003eHAI-DEF endpoints for DICOM imaging require data from DICOM storage systems that adhere to the DICOM standard, including specific tags, values, and data formats.\u003c/p\u003e\n"],["\u003cp\u003eThese endpoints utilize the DICOMweb REST API, specifically QIDO-RS and WADO-RS over HTTPS, for data retrieval, requiring URIs with valid DICOMweb suffixes.\u003c/p\u003e\n"],["\u003cp\u003eHAI-DEF endpoints perform Transfer Syntax transcoding on DICOM inputs and need access to the DICOM storage system within the Google Cloud private network.\u003c/p\u003e\n"],["\u003cp\u003eFor authorization, the DICOM storage system needs either public access or the ability to accept OAuth 2.0 bearer tokens.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Cloud's DICOM store is the recommended storage solution; however, users can utilize curated test datasets or store images in Google Cloud Storage buckets as alternatives.\u003c/p\u003e\n"]]],[],null,["# DICOM storage and transport\n\nHAI-DEF endpoints that deal with DICOM imaging, such as\n[Path Foundation](/health-ai-developer-foundations/path-foundation/serving-api)\nand\n[CXR Foundation](/health-ai-developer-foundations/cxr-foundation/serving-api),\nare capable of retrieving their input data from\n[DICOM](https://cloud.google.com/healthcare-api/docs/concepts/dicom) storage\nsystems that meet the following requirements:\n| **Tip:** [Google Cloud DICOM store](https://cloud.google.com/healthcare-api/docs/concepts/dicom) is the recommended DICOM store. If you don't have a compatible DICOM store yet, try HAI-DEF endpoints with our [curated test datasets](/health-ai-developer-foundations/model-data/curated-test-data) or upload your image files, such as [PNG](https://en.wikipedia.org/wiki/PNG) or [JPEG](https://en.wikipedia.org/wiki/JPEG) files, to a [Google Cloud Storage (GCS)](https://cloud.google.com/storage) bucket. Some HAI-DEF endpoints such as [CXR Foundation](https://github.com/Google-Health/cxr-foundation/tree/master/python/serving/README.md) accept DICOM instances as binary files with `.dcm` extension stored in GCS buckets. Read more about [model data in GCS](/health-ai-developer-foundations/model-data/google-cloud-storage).\n\nDICOM standard storage\n----------------------\n\nHAI-DEF endpoints require DICOM imaging to conform to the\n[DICOM standard](https://www.dicomstandard.org/). This includes defining all\nrequired\n[Type-1 tags](https://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_7.4.html)\nand ensuring that tag values comply with their specified\n[Value Representation (VR)](https://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_6.2.html)\nand\n[Value Multiplicity (VM)](https://dicom.nema.org/dicom/2013/output/chtml/part05/sect_6.4.html)\ncodes.\n\nDICOMweb transport protocol\n---------------------------\n\nHAI-DEF endpoints require the DICOM storage system holding the imaging to\nsupport the [DICOMweb REST API](https://www.dicomstandard.org/using/dicomweb)\nand more specifically JSON formatted\n[QIDO-RS](https://www.dicomstandard.org/using/dicomweb/query-qido-rs) and\n[WADO-RS](https://www.dicomstandard.org/using/dicomweb/retrieve-wado-rs-and-wado-uri)\nover [HTTPS protocol](https://en.wikipedia.org/wiki/HTTPS).\n\nThe Uniform Resource Identifiers (URIs) must end with a valid DICOMweb suffix:\nfor example the URI for a\n[DICOM series](https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_c.7.3.html)\nmust end with a `studies/${STUDY-UID}/series/${SERIES-UID}` suffix.\n\nTransfer syntax transcoding\n---------------------------\n\nHAI-DEF endpoints transcode their DIOCM inputs based on the\n[Transfer Syntax UID](https://www.dicomlibrary.com/dicom/transfer-syntax/).\nRefer to the respective serving API specification for details.\n\nPrivate network accessibility\n-----------------------------\n\nHAI-DEF endpoints operate within the secure Google Cloud private network as\n[Vertex AI prediction endpoints](https://cloud.google.com/vertex-ai/docs/predictions/overview).\nTherefore, if you plan to use HAI-DEF endpoints with DICOMWeb data links, the\nDICOMWeb store has to be accessible from this private network. Refer to\n[Google Cloud private access options](https://cloud.google.com/vpc/docs/private-access-options).\n\nAuthentication and authorization\n--------------------------------\n\nThe DICOMweb storage system either must support public access or accept\n[OAuth 2.0 bearer tokens](https://www.rfc-editor.org/rfc/rfc6750) for\nauthorization."]]