DICOM to Google Cloud
Send DICOM to Google Cloud Healthcare
Route studies from your modalities and PACS into a Google Cloud Healthcare DICOM store — and query, retrieve, and edit them once they are there. Rule-based, HL7-aware, with store-and-forward retry.
The basics
How do you get DICOM into Google Cloud Healthcare?
Google Cloud Healthcare exposes a DICOM store that speaks DICOMweb — STOW-RS to store, QIDO-RS to search, WADO-RS to retrieve — behind Google authentication. Modalities and most legacy PACS do not speak that: they speak classic DICOM C-STORE, with an AE title and a port. Something has to sit between them and translate, handle the credentials, and retry when the link is unavailable.
That is what RadFuzion does. It receives studies over standard DICOM from any modality or PACS, applies your routing rules, and stores them into the Google Cloud DICOM store over DICOMweb — while also letting you query, retrieve, and edit what is already in the store.
Why RadFuzion
More than a one-way uploader
Getting images up is the easy half. Working with them afterwards, and surviving a bad network day, is what separates a migration script from a production path.
Receive DICOM, store to the cloud
Modalities send by C-STORE exactly as they always have. RadFuzion handles DICOMweb, authentication, and the Google-specific details, so nothing on the modality side changes.
Query and retrieve back out
Search the Google DICOM store and pull studies back for viewing, prior comparison, or correction — including into the browser viewer.
Store-and-forward with retry
When the link or the store is unavailable, studies are held locally and forwarded automatically once it recovers, instead of failing at the modality.
Under the hood
Google Cloud DICOM capabilities
- check_circleSTOW-RS store to Google Cloud Healthcare
- check_circleQIDO-RS query against the DICOM store
- check_circleWADO-RS retrieve for viewing and priors
- check_circleReceive from modalities by C-STORE
- check_circleRule-based routing to one or many stores
- check_circleHL7-driven routing decisions
- check_circleTag correction before or after upload
- check_circleEdit studies already in the store
- check_circleTransfer-syntax conversion and compression
- check_circleStore-and-forward retry on outage
- check_circleRoute to multiple clouds at once
- check_circleCentral management across sites
Migrating an existing archive
A migration is the same pipeline pointed at an old archive instead of a modality: query the source PACS, retrieve, optionally correct metadata in flight, and store into the Google DICOM store — with retry, so a multi-week transfer survives interruptions without losing its place.
Metadata is usually the real work. Studies accumulated over a decade carry inconsistent descriptions, station names, and identifiers; loading them unchanged means inheriting that mess in the new archive. Routing rules and RadMatch normalize descriptions to your exam codes as studies pass through, so the cloud copy is cleaner than the original.
FAQ
Google Cloud DICOM questions
How do I send DICOM from a modality to Google Cloud Healthcare?add
Point the modality at RadFuzion as a normal DICOM destination using C-STORE. RadFuzion receives the study and stores it into the Google Cloud Healthcare DICOM store over STOW-RS, handling authentication and retry. Nothing changes on the modality.
Can I query and retrieve studies back out of a Google DICOM store?add
Yes. RadFuzion queries the store with QIDO-RS and retrieves with WADO-RS, so studies can be pulled back for viewing, prior comparison, or correction — including into the browser-based viewer.
What happens if the connection to Google Cloud drops?add
Studies are held locally and forwarding retries automatically until the store is reachable again. The modality still gets a successful C-STORE, so acquisition is never blocked by a cloud or network problem.
Can I edit a study that is already in the Google DICOM store?add
Yes. RadFuzion can retrieve the study, correct its tags — Accession, MRN, study description, and so on — and write the corrected study back, which is otherwise awkward once an exam has been archived to the cloud.
Can studies go to Google Cloud and another destination at the same time?add
Yes. One routing rule can target several destinations, so a study can land in a Google DICOM store, an on-prem PACS, and an AI pipeline from a single inbound send.
Can it migrate an existing PACS archive into Google Cloud?add
Yes. RadFuzion can query and retrieve from the existing archive and store into the Google DICOM store, correcting metadata in flight, with retry so a long-running migration recovers from interruptions.
See cloud routing running
Open the live preview to see rule-based routing, cloud query/retrieve, and tag editing against sample studies.