arrow_backRadFuzion field notes
RadFuzion R logoCloud Imaging10 min read

C-STORE vs STOW-RS for cloud PACS

Both store DICOM images. C-STORE does it over a negotiated DICOM association; STOW-RS does it with an HTTPS POST. The difference shapes your firewall, your security and how you know an upload worked.

RadFuzion TeamUpdated
C-STORE in, STOW-RS out
The site speaks DIMSE. The cloud speaks HTTPS.
  1. On site
    Modalities and PACS
    C-STORE over an association. AE titles, port 104 or 11112, presentation contexts.
  2. Gateway
    Store, then forward
    Writes each study to disk, applies rules, holds it if the cloud is unreachable.
  3. Cloud store
    STOW-RS over HTTPS
    POST with a bearer token. Answers 200, 202 or 409, with a result per instance.
Simplified. The gateway can also send C-STORE to on-site PACS at the same time.
In this article12

What is the difference between C-STORE and STOW-RS? C-STORE is the classic DICOM way to send an image: the sender opens an association with the receiver, negotiates what it will send, and transfers each instance with a status in reply. STOW-RS is the DICOMweb way: the sender makes an HTTPS POST of one or more instances, authenticated with a token, and the server answers with an HTTP status and a result for each instance. Cloud DICOM stores such as Google's and Azure's take DICOMweb, while modalities send C-STORE, so something in between has to translate.

This article explains both, compares them on the points that matter in a cloud project, and shows how a gateway connects a site's modalities to a cloud store.

Summary

The short answer

  • Use C-STORE inside the site, between modalities, PACS and workstations. It is what those devices send and receive.
  • Use STOW-RS to reach a cloud DICOM store. Google Cloud Healthcare API and the Azure Health Data Services DICOM service both accept it, and it travels over ordinary outbound HTTPS.
  • Put a gateway between them so modalities need no internet access and the cloud credentials live in one place.

DIMSE

How C-STORE works

C-STORE belongs to the Storage Service Class, defined in DICOM PS3.4 Annex B, with the message exchange in PS3.7 and the network protocol in PS3.8. A transfer runs in three steps:

  • Associate. The sender (the SCU) connects to the receiver's host and port and names itself and the receiver by AE title. It proposes presentation contexts: each pairs a SOP class, such as CT Image Storage, with the transfer syntaxes it can send, such as Explicit VR Little Endian or JPEG 2000 Lossless. The receiver (the SCP) accepts or rejects each context.
  • Store. For each instance, the sender sends a C-STORE request on an accepted context and waits for a response with a status: 0000 for success, Bxxx (and a few 01xx codes) for a warning, and Axxx, Cxxx or most 01xx and 02xx codes for a failure.
  • Release. When the study is sent, the association is closed.

The strengths: modalities, PACS and workstations all speak it, the negotiation catches unsupported objects before any data moves, and each instance gets its own answer. The limits: identity is an AE title and an IP address rather than a credential, traffic is unencrypted unless both ends configure DICOM TLS, and the protocol is built for networks where the sender can reach the receiver's port directly.

DICOMweb

How STOW-RS works

STOW-RS is the Store transaction of the DICOMweb Studies Service, defined in PS3.18 section 10.5. The sender makes an HTTP POST to the store's /studies resource. The body is usually multipart/related; type="application/dicom", with each part a complete DICOM file, so one request can carry many instances. Authentication is ordinary HTTP: cloud stores expect an OAuth 2.0 bearer token in the Authorization header.

The response is where STOW-RS differs from C-STORE in practice. According to PS3.18 section 10.5.3, 200 means every instance was stored, 202 means some were stored and others had warnings or failures, and 409 means none were stored, for example because of an unsupported SOP class or a Study UID mismatch. 400 is bad syntax and 415 an unsupported media type. The body lists stored instances in the Referenced SOP Sequence (0008,1199) and failed ones in the Failed SOP Sequence (0008,1198), each with a failure reason. A sender that reads just the HTTP status can believe a study arrived when some of it did not.

Comparison

Side by side

C-STORE and STOW-RS compared
AspectC-STORESTOW-RS
Protocol familyDIMSE, the classic DICOM network protocolDICOMweb, the DICOM RESTful web services
TransportDICOM Upper Layer over TCP, commonly port 104 or 11112HTTP over TLS (HTTPS), normally port 443
Who you areCalling and called AE titles, plus the IP address the receiver expectsAn OAuth 2.0 bearer token or other HTTP authentication
Before sendingAssociation negotiation: the receiver accepts or rejects each SOP class and transfer syntaxNo negotiation per object; the server reports what it stored after the upload
Unit of workOne C-STORE request and response per instance, many per associationOne POST that can carry many instances as multipart/related parts
ResultA status code per instance (for example 0000, Bxxx, Axxx, Cxxx)An HTTP status per request (200, 202, 409, 400, 415) plus a per-instance list in the body
EncryptionNone unless DICOM TLS is configured on both endsTLS as part of HTTPS
StandardPS3.4 Annex B, PS3.7, PS3.8PS3.18, section 10.5

The rest of DICOMweb

QIDO-RS and WADO-RS

STOW-RS has two companions. QIDO-RS searches: a GET such as /studies?AccessionNumber=A123 returns matching studies as DICOM JSON, the web counterpart of C-FIND. WADO-RS retrieves: a GET for a study, series or instance returns the objects, and the Accept header can ask for a transfer syntax. It plays the role C-MOVE and C-GET play in DIMSE, without the archive opening a connection back to the requester, as it does for C-MOVE.

Together they let a site search what is already in the cloud, check whether a study arrived, and pull images back for viewing or correction, all over the same HTTPS path and credentials as the upload.

Networking

Firewalls and networks

DIMSE expects the sender to reach the receiver's port directly, so sending C-STORE across the internet usually means a VPN or a private link. Retrieval with C-MOVE is harder still, because the archive opens a new association back to the requester, so the requester's port must be reachable too.

STOW-RS needs one outbound HTTPS connection from the gateway to the cloud endpoint, the same kind of traffic as any other cloud service. Nothing needs to be opened inbound to send images. Two things still need checking with your network team: a proxy that inspects TLS or limits request size can break large uploads, and long transfers need idle and request timeouts that allow for them.

Security

Authentication on Google Cloud and Azure

Google Cloud Healthcare API

Google's DICOM stores accept a subset of DICOMweb, including Store, Search and Retrieve, as described in its DICOM conformance statement and DICOMweb guide. Requests carry an OAuth 2.0 access token, typically obtained for a service account or through Application Default Credentials, as covered in Google's authentication overview. The identity also needs an IAM role that allows DICOMweb writes on the store, such as Healthcare DICOM Editor.

Azure Health Data Services DICOM service

The Azure DICOM service also supports a subset of DICOMweb, including Store, Retrieve and Search, per its conformance statement and overview. Access uses Microsoft Entra ID with OAuth 2.0. Microsoft's authentication and authorization page covers the authorization-code and client-credentials flows and the DICOM Data Owner and DICOM Data Read roles; the access token guide shows how to request a token for testing.

On both platforms tokens expire, typically after about an hour, so a long upload can outlive the token it started with. A sender has to request a fresh token and resend, rather than treat the 401 as a failed study.

Throughput

Performance, without the benchmarks

Published throughput numbers depend so heavily on links, object sizes and server load that they say little about your site. The design differences are more useful:

  • Round trips. C-STORE waits for a response per instance. On a high-latency link, a study of many small instances can spend much of its time waiting. Several associations in parallel help. STOW-RS can put many instances in one request, and several requests can run in parallel.
  • Large objects. Breast tomosynthesis, whole-slide and long ultrasound objects are better sent one per request or per association, with timeouts sized for them.
  • Compression. Lossless compression reduces the bytes on the wire with either protocol, if the receiver accepts the transfer syntax.
  • Server-side limits. Cloud stores and proxies apply request-size and time limits. Find them before go-live, not when a large study fails in production.

Bridging

How a gateway bridges the two

A gateway, usually the site's DICOM router, receives C-STORE from modalities on the local network, writes each study to its own disk, and sends it on to the cloud over STOW-RS. That gives a site several things at once:

  • Modalities keep sending to a local AE title over the LAN. They need no internet access, and the only change is adding the gateway as a destination.
  • Cloud credentials are stored in one place, not on every device.
  • Studies can be corrected on the way: tags fixed, compression changed, descriptions normalized.
  • When the internet link or the cloud store is unavailable, studies wait on the gateway instead of failing at the modality.

The trade-off to understand: the modality's C-STORE succeeds when the gateway has the study, not when the cloud does. From then on the gateway's queue is the record of what is still to be delivered, so it has to be monitored.

Delivery

Reliability: retries, holds and results

What to look for in any gateway that sends STOW-RS:

  • Per-instance accounting. Read the Failed SOP Sequence, not just the HTTP status, and count each instance as stored or failed.
  • Already-stored handling. A resent instance may be answered as already existing. That means the store kept its copy, so a resend after a tag correction may change nothing in the cloud.
  • Holds while unreachable. Network and DNS failures should hold studies and replay them when the store is back, not use up a fixed number of retries.
  • Token refresh. A 401 partway through should lead to a new token and a retry.
  • Isolation. One object the store rejects should not block the rest of the study.

Architecture

Hybrid setups

A move to the cloud usually runs hybrid for a while. A routing rule can send each study to the on-site PACS over C-STORE and to the cloud store over STOW-RS at the same time, so a migration can run without a single cutover. A local copy also keeps recent studies available on site if the internet link drops. Object storage such as Amazon S3 or a Google Cloud Storage bucket is a different thing: it holds DICOM files but does not answer DICOMweb queries, so use it for archive copies rather than as a store you search.

RadFuzion

Where RadFuzion fits

RadFuzion is the gateway in this picture. It receives C-STORE on site and sends STOW-RS to the Google Cloud Healthcare API, the Azure Health Data Services DICOM service or any DICOMweb server:

  • Google Cloud: a service-account JSON key, or Application Default Credentials when the key is left blank. The connection test checks that the identity can write.
  • Azure: a Microsoft Entra app registration (tenant ID, client ID and client secret), with an optional data partition. RadFuzion does not use managed identities.
  • Other DICOMweb servers: a bearer token or a username and password.
  • Cloud store results: answers from Google, Azure and other DICOMweb stores are read instance by instance, including 200 and 202 answers that list failed instances and 409 answers. Only the instances a store didn’t take are marked failed and sent again, instances it already has are reported as already there, and a failing batch to Google or Azure is retried one instance at a time.
  • Holds: when a cloud store is unreachable, studies wait and go out when it recovers. Cloud destinations are checked every 15 minutes by default.
  • Search and retrieve: QIDO-RS and WADO-RS let you search Google, Azure and DICOMweb stores from RadFuzion and pull studies back, and RadFetch can pull priors from them.
  • Both directions: RadFuzion is also a DICOMweb server, so other systems can send to it with STOW-RS, routed like C-STORE, and search and retrieve recent studies from its image cache with QIDO-RS and WADO-RS.

On the C-STORE side, DICOM TLS is available on its own port (2762 for the receiver) and per destination, for devices that support it. Plain C-STORE traffic should stay on the local network or inside a VPN. The details are on the DICOM conformance page, with setup guides for Google Cloud Healthcare and Azure Health Data Services, and the DICOM router page for the routing rules.

See it in your workflow

Keep modalities on C-STORE and send the cloud STOW-RS.

RadFuzion receives studies over C-STORE on site and sends them to Google Cloud Healthcare, Azure or any DICOMweb store over STOW-RS, holding them while the cloud is unreachable.