Steps

Deploy the dicomweb-adapter Docker image (gcr.io/cloud-healthcare-containers/healthcare-api-dicom-dicomweb-adapter-dicomweb) as a sidecar or standalone container accessible to legacy PACS equipment
Configure the adapter with the Cloud Healthcare API DICOMweb endpoint URL and a service account key or Workload Identity binding that has the roles/healthcare.dicomEditor IAM role
Register the adapter's host, port, and AE title in legacy PACS as a remote DICOM node; the adapter acts as a DIMSE SCP accepting C-FIND and C-STORE from the legacy system
Send a C-FIND request from the legacy PACS to the adapter's AE title; the adapter translates it to a QIDO-RS HTTP request to the Cloud Healthcare API and returns DIMSE C-FIND responses
For C-MOVE, configure the adapter's destination AE mapping so that DICOM instances retrieved from the cloud DICOMweb service are forwarded to the correct legacy PACS via C-STORE

Known gotchas

The adapter translates a subset of C-FIND matching keys to QIDO-RS parameters; complex queries using Sequence-level matching keys that have no QIDO-RS equivalent will return incomplete or empty results — verify supported query keys in the adapter's documentation
The adapter does not persist DICOM data locally; it is a stateless translation proxy, so the underlying Cloud Healthcare API must be available for every query — plan for adapter availability and cloud connectivity
Service account credentials embedded in the container configuration pose a secret management risk; prefer Workload Identity (GKE) or environment variable injection from a secrets manager rather than mounting a JSON key file into the container

Plan and execute a PACS-to-PACS migration using DICOM C-MOVE with throttling and integrity verification

pubmed.ncbi.nlm.nih.gov · 5 steps · unrated

Deploy Azure DICOM service within Azure Health Data Services and configure DICOMcast to sync imaging metadata to a FHIR service

learn.microsoft.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Use the Google Cloud Healthcare API DICOM adapter to bridge legacy DIMSE C-FIND and C-MOVE calls to the cloud DICOMweb backend

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?