DICOM Router
The DICOM router built for cloud PACS and HL7 workflows
RadFuzion is a cloud-native DICOM router: rule-based routing across Google Cloud, DICOMweb, Azure, S3, and traditional PACS — driven by the HL7 orders your other routers ignore.
The basics
What is a DICOM router?
A DICOM router receives imaging studies over the DICOM protocol and automatically forwards them to the right destinations based on configurable rules — by modality, AE title, station, body part, or HL7 order. It is the traffic controller of a medical imaging network, making sure every study reaches the correct PACS, archive, cloud store, or reading workstation.
Where a PACS stores and displays images, a DICOM router moves them: it sits in front of and between systems, applying routing rules, editing tags, and bridging protocols. RadFuzion does that across both traditional on-prem PACS and modern cloud stores from a single ruleset.
Why RadFuzion
A DICOM router that speaks cloud and HL7
Legacy routers forward classic DICOM between on-prem nodes and stop there. RadFuzion adds the two things modern imaging networks actually need.
Routes to the cloud, not just PACS
Send, query, and edit studies across Google Cloud Healthcare DICOM stores, DICOMweb, Azure, and S3 — alongside traditional DICOM PACS. One ruleset spans on-prem and cloud.
An HL7 brain drives the rules
RadFuzion reads HL7 ORM/ORU orders and uses them to drive routing, prior prefetch, modality worklist, and reporting. Most DICOM routers ignore HL7 entirely.
Rule-based, tag-aware routing
Route by modality, AE title, station, body part, or order data. Normalize and rewrite DICOM tags in flight — remap Accession/MRN, merge or split studies — so downstream systems get clean metadata.
Under the hood
DICOM routing capabilities
- check_circleC-STORE / C-FIND / C-MOVE
- check_circleDICOMweb: QIDO-RS · WADO-RS · STOW-RS
- check_circleGoogle Cloud Healthcare DICOM
- check_circleAzure & Amazon S3 destinations
- check_circleHL7 ORM / ORU ingestion
- check_circleModality Worklist (MWL) provider
- check_circleDICOM tag morphing & coercion
- check_circleStudy merge / split
- check_circleRule-based multi-destination routing
- check_circleCompression & transfer-syntax conversion
- check_circleStore-and-forward with retry
- check_circleCentral management across sites
FAQ
DICOM router questions
What is a DICOM router?add
A DICOM router receives imaging studies over the DICOM protocol and automatically forwards them to the right destinations based on configurable rules — by modality, AE title, station, body part, or HL7 order. It is the traffic controller that gets each study to the correct PACS, archive, cloud store, or workstation.
How is a DICOM router different from a PACS?add
A PACS stores and displays images; a DICOM router moves them. The router sits in front of and between systems, applying routing rules, editing tags, and bridging protocols so studies land in the right place. RadFuzion routes across both traditional PACS and cloud stores from one place.
Can a DICOM router send to cloud storage, not just PACS?add
RadFuzion can. Most legacy DICOM routers only speak classic DICOM to on-prem PACS. RadFuzion also sends, queries, and edits studies across Google Cloud Healthcare DICOM stores, DICOMweb, Azure, and S3 — so you can route between on-prem and cloud from a single ruleset.
Can the router use HL7 orders to drive routing?add
Yes. RadFuzion reads HL7 ORM/ORU messages and uses order data to drive routing, prefetch of priors, modality worklist, and reporting. Most DICOM routers ignore HL7 entirely — this is the "HL7 brain" that sets RadFuzion apart.
Can it edit or morph DICOM tags while routing?add
Yes. RadFuzion normalizes and rewrites DICOM attributes in flight — remapping Accession, MRN, and station values, and merging or splitting studies — so downstream systems receive clean, consistent metadata regardless of what the modality sent.
Does RadFuzion support C-STORE, C-FIND, and C-MOVE?add
Yes. RadFuzion is a full DICOM node supporting C-STORE, C-FIND, and C-MOVE for query/retrieve against any conformant PACS or archive, alongside DICOMweb (QIDO-RS, WADO-RS, STOW-RS) for cloud endpoints.
See the router move real studies
Open the live preview to watch rule-based routing, query/retrieve, and HL7-driven workflow run on sample data — no PHI, no signup.