Verified steps

Map use-case requirements to protocol capabilities: DIMSE C-FIND supports complex attribute matching including Sequence attributes; QIDO-RS supports a subset of attributes as URL query parameters with server-defined matching semantics
Assess transport constraints: DIMSE requires a persistent TCP connection and DICOM Upper Layer Protocol; DICOMweb uses stateless HTTP/HTTPS and works over standard web proxies, load balancers, and CDNs without special firewall configuration
Compare retrieval granularity: C-MOVE is study/series/instance-granular and moves data to a registered destination AE; WADO-RS is a pull model that retrieves directly to the requesting HTTP client, which better suits web and cloud architectures
Evaluate security models: DIMSE relies on AE-title-based verification (not cryptographically strong without TLS); DICOMweb integrates with standard OAuth 2.0 / SMART on FHIR bearer token authorization
Consider implementation maturity: most established PACS have battle-tested DIMSE implementations, while DICOMweb support and conformance levels vary — review the target server's DICOMweb conformance statement before committing to a web-only integration

Known gotchas

QIDO-RS does not provide a standardized equivalent for every C-FIND matching key; in particular, Sequence-level attributes (e.g., RequestAttributesSequence) cannot be queried via QIDO-RS on most implementations
C-MOVE delivers images asynchronously to a pre-registered destination, making it unsuitable for on-demand browser-based viewers that need synchronous pull retrieval — WADO-RS is the correct choice for web viewers
DICOMweb's C-MOVE equivalent, WADO-RS, retrieves data to the caller; there is no DICOMweb equivalent for initiating a server-to-server push (the role C-MOVE fills) unless STOW-RS is used on the receiving server

github.com/GoogleCloudPlatform/healthcare-dicom-dicomweb-adapter · 5 steps · unrated

query and retrieve imaging studies via DICOMweb (QIDO-RS and WADO-RS)

Negotiate and transcode DICOM transfer syntaxes during C-STORE association to handle modality and PACS incompatibilities

dicom.nema.org · 5 steps · unrated

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

Evaluate the architectural tradeoffs between legacy DIMSE C-FIND/C-MOVE and modern DICOMweb QIDO-RS/WADO-RS for a new integration

Verified steps

Known gotchas

Related routes

Give your agent this knowledge — and 200+ more routes