Available now

DICOM router · Router family — mid tier

XyDromatics Core Router — store-and-forward DICOM routing.

Every received instance is sealed to a durable encrypted spool, matched against your priority routing rules, and forwarded to its destinations with restart-surviving retry and dead-letter — so an image we accept is an image we deliver, never accept-and-drop.

On top of the store-and-forward core, Core Router adds per-destination transforms on an isolated copy, load-failover for unreliable peers, a manual hold queue for studies that need a human, and a PHI-free operational analytics window.

Request a demo See the product Compare the tiers

At a glance

Availability: Available now
Classification: Non-device software · §520(o)(1)(D)
Role: Store-and-forward DICOM router
Web console: HTTP :5130
DICOM SCP: CORE_RTR : 11130
Platforms: Windows · Linux
Best for: Durable routing, edge / unreliable links, per-destination transforms

Full regulatory posture →

The problem it solves

A router that drops an image is worse than no router.

A simple forwarder

A pass-through forwarder relays each association in the moment. When the far side is slow, unreachable, or the service restarts mid-transfer, the study in flight is simply gone — acknowledged to the sender but never delivered onward.

The same one destination, one rule, one shape means you cannot send a de-identified copy to the cloud and the full study to the archive from a single inbound stream.

With Core Router

Each instance is sealed to a durable encrypted spool before it is acknowledged, then drained to every matched destination on its own schedule. Retry survives restarts; anything undeliverable lands in dead-letter rather than vanishing.

Priority rules fan one study to many destinations, and a per-destination transform runs on a clone — so each peer receives exactly the shape it should, with no cross-contamination.

What it does

Guaranteed delivery, with the routing intelligence around it.

A durable store-and-forward core, priority routing with per-destination transforms, resilient delivery to DIMSE and DICOMweb peers, a review queue, and the security an enterprise expects.

Durable store-and-forward

Once we acknowledge an image, we own delivering it.

Seal-then-ack: every received instance is written to a durable, encrypted spool before the association is acknowledged
A background drain forwards off the receiving association, so a slow or unreachable destination never blocks intake
Restart-surviving retry with backoff — the spool and its queue outlive a service restart or a host reboot
Dead-letter on exhaustion instead of silent loss: guaranteed delivery, never accept-and-drop

Rule-driven routing + per-destination transforms

Match once, then shape the copy each destination receives.

Priority routing rules decide which destinations each study is fanned to
A per-destination transform pipeline runs on a CLONE of the dataset, so one destination’s changes never bleed into another’s
Reversible de-identification and burned-in-pixel redaction for destinations that must not receive PHI
Tag coercion and normalization to satisfy a downstream system’s expectations
Order reconciliation against an authoritative order — correct a study’s tags (e.g. Study Description) from an external provider’s Modality Worklist, fetched by an initiating C-FIND with no HL7 ingest; patient-identity and laterality mismatches are flagged for review, never silently changed
Native lossless transfer-syntax transcode when a destination needs a different encoding

Resilient delivery

Keep images moving when a link or a peer goes bad.

Load-failover with a per-destination circuit breaker that trips a failing peer out of rotation
Load-balanced destination pools with outbound study affinity — a whole study sticks to one pool member, with per-member health and automatic failover
A cold-standby fallback chain takes over so delivery continues while the primary recovers
An optional C-ECHO heartbeat verifies a peer is alive before committing traffic to it
Outbound DICOMweb (STOW-RS) delivery to cloud and AI destinations, alongside classic DIMSE C-STORE
Inbound DICOMweb (STOW-RS) ingest — a modality, gateway, or viewer can push studies over HTTP into the same routing pipeline as a C-STORE (a token / mutual-TLS machine door, off by default)

Review & insight

A place for the studies that need a human, and a window on the flow.

A manual-review hold queue: divert studies for inspection, and release re-enters them into the routing rules
Disposal is confirm-gated — nothing leaves the queue destructively by accident
A PHI-free 7-day operational analytics window, with archive-to-lake for longer-horizon reporting
Standards-correct source-AE provenance carried in the PS3.3 Original Attributes Sequence, so it survives the wire to the receiver

Queryable study cache (local Query/Retrieve)

Run Query/Retrieve at a site with no archive — no VNA required.

An optional bounded, sealed cache of recently-received studies answers DIMSE C-FIND / C-MOVE on its own listener, plus DICOMweb QIDO-RS / WADO-RS
A cache, not an archive: studies age out on a TTL and size cap and eviction is a hard delete — for sites with no retention obligation
Sealed at rest, gated on licence validity (no separate feature key), and access-controlled so the read-only support role never sees cached PHI

Secure & enterprise-ready

Encrypted end to end, access-controlled, and audited.

DICOM-TLS / mTLS on the wire for both received and forwarded traffic
Encryption at rest with customer-keyed key-escrow on the spool and configuration
LDAP sign-in with RBAC and custom roles for who can route, hold, and administer
A hash-chained, tamper-evident HIPAA audit trail
Remote support through SynthGateway; ships as a Windows MSI and a Linux package

DICOM-only, by design. Core Router routes images and nothing else. Serving HL7, hosting a Modality Worklist, and order generation are intentionally out of scope — they live in Core MWL and the Encounter Engine — so the router stays a focused, pure-DICOM store-and-forward engine. For order reconciliation it can query an external provider’s worklist by an outbound C-FIND, but it never ingests or serves HL7 or a worklist of its own.

See it

Store-and-forward routing, on screen.

Live captures from a running installation — click any screen to enlarge it.

Configuration

Listeners, destinations and routing rules — durable store-and-forward with per-rule transforms and load-failover, set up from one page.

Queues

What is waiting, what is sending and what failed — with retry and hold, and identifiers masked by role.

Hold queue

Studies held by rule until you release them — review, release or discard.

Monitor

Live associations, listener state and destination health as they change.

Availability

Available now — Windows and Linux.

Core Router ships today as a Windows MSI and a Linux package, with everything on this page in the box: the durable store-and-forward spool, priority routing with per-destination transforms, load-failover delivery to DIMSE and DICOMweb peers, the manual hold queue, and the operational analytics window.

It is general-purpose, non-device software (FD&C Act §520(o)(1)(D)) — the mid tier of the Router family, for facilities that need guaranteed delivery and per-destination shaping without running an HL7 or worklist server. Get in touch for a demo and a licence.

Request a demo All products

Documentation

The controlled-document set.

Every Core Router deployment ships with the documents below, all managed under SynthQMS document control. The DICOM Conformance Statement is publicly available; the rest are shared under mutual NDA.

Document	Title	Notes
Pending	Hardware & Software Requirements (Core Router)	Sizing, OS support, dependencies
DOC-2026-530	DICOM Conformance Statement (Core Router)	Public — full SOP class + transfer-syntax matrix
Pending	EULA Annex (Core Router)	Annex to the Synthology Master EULA (DOC-2026-063)
Pending	Penetration Test Results (Core Router)	Available under NDA
Pending	QA Runner Manual (Core Router)	Internal QA + customer-validated test runs
DOC-2026-593	End User Guide (Core Router)	Operator + administrator workflows
DOC-2026-594	Installation Guide (Core Router)	Includes MSI deploy + Linux tarball install

Additional documents

Core Router-specific documents beyond the standard set. Items marked Pending are tracked for authoring under SynthQMS change control.

Document	Title	Notes
DOC-2026-592	Product Datasheet (Core Router)	Product overview + specifications

An image you accept is an image you deliver.

XyDromatics Core Router seals every instance to a durable encrypted spool, routes it by your rules, and forwards it with restart-surviving retry and dead-letter — never accept-and-drop. Available now on Windows and Linux.

Request a demo All products