Enable the Cloud Healthcare API and create a dataset and DICOM store using the gcloud CLI: gcloud healthcare dicom-stores create MY_STORE --dataset=MY_DATASET --location=us-central1
Authenticate with application default credentials and obtain an OAuth2 access token via gcloud auth print-access-token for use in HTTP headers
Store a DICOM instance with STOW-RS: POST https://healthcare.googleapis.com/v1/projects/PROJECT/locations/LOCATION/datasets/DATASET/dicomStores/STORE/dicomWeb/studies with Content-Type multipart/related; type=application/dicom and the DICOM P10 file as the body part
Query studies with QIDO-RS: GET .../dicomWeb/studies?PatientName=SMITH&limit=20 and parse the JSON response array of study-level attributes
Retrieve pixel data with WADO-RS: GET .../dicomWeb/studies/{studyUID}/series/{seriesUID}/instances/{instanceUID}/frames/1 with Accept: application/octet-stream
Known gotchas
The Cloud Healthcare API supports single-part STOW-RS in addition to multipart/related; use Content-Type: application/dicom for single-part to avoid multipart boundary construction errors
IAM role roles/healthcare.dicomEditor is required to store instances; roles/healthcare.dicomViewer is sufficient for read-only QIDO-RS and WADO-RS
QIDO-RS responses from the Cloud Healthcare API are returned as JSON (application/dicom+json) by default, not the DICOM multipart XML format; ensure the client accepts this media type
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp