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.