DCMX DICOM:Router
Coming soon
National network under construction, launch to follow

DCMX – national network for medical image exchange

Your images. The whole country. One network.

The national network for secure medical image exchange, powered by DICOM:Router.

A night in the emergency department

One patient, an unknown history.

The medical history is scattered across hospitals and diagnostic centres throughout the country. That is exactly what makes it so hard to bring everything together quickly: phone calls, waiting, and deciding without the full picture.

  1. Arrival at the emergency department: the earlier CT study sits at an organisation eighty kilometres away.

  2. The care team requests the study through DCMX: directly, encrypted, and only after the legal basis has been checked.

  3. The images sit alongside the new scan. The team takes the right medical decisions straight away.

Fictional scenario, for illustration.

The answer

DCMX

Image data from across the country can be viewed straight away and, if you wish, stored locally for later reference. DCMX coordinates; the image data travels directly from organisation to organisation: peer-to-peer, encrypted, and only after the legal basis has been checked.

IMAGE DATA · PEER-TO-PEER · ENCRYPTED

A Tuesday morning in radiology

The same question, without the rush.

Acute care is the sharpest use case, not the only one. The same question comes up in the regular workflow: has imaging of this patient been made elsewhere before? DCMX can flag that of its own accord, before the examination is picked up — without anyone having to ring around to find out.

  1. The patient appears on the worklist for a follow-up examination.

  2. A notification: two other organisations hold earlier imaging of this patient.

  3. The radiologist retrieves one of them. That choice stays with the person, not with the network.

Fictional scenario, for illustration.

Notification Alert

Earlier examinations found

2 organisations · 3 examinations

  • CT · Abdomen 12-03-2024 Hospital C
  • CT · Abdomen 07-11-2022 Hospital C
  • MR · Abdomen 22-06-2021 Diagnostic Centre B

A signal only, no images yet. Retrieval remains the clinician’s choice.

Consent

Both use cases hang on the same gate: outside your own organisation nothing happens without consent. Which model applies determines what is allowed — and that difference is what makes one use case possible alongside the other.

Consent

Standing

Registered in advance, until the patient withdraws it.

Also covers
Situations where the patient is not present.
Use case
The regular workflow. The only model a prior-imaging alert can rely on.

Consent

Ad hoc

Given on the spot by a patient who is present.

Covers
The visit in which it was given.
Use case
The front desk: emergency department, outpatient clinic, reception. The patient decides in the moment.

Not consent

Emergency access

An exception ground, for when consent cannot be obtained.

Covers
This one patient, briefly, with a recorded reason.
Use case
Acute care. A deliberate choice by an authorised clinician — never by a system.

Emergency access is counted separately everywhere, precisely because it is not consent.

The national network

Image data from across the country.

DCMX coordinates and guards consent; the image data travels directly from organisation to organisation.

Map of the Netherlands with the DCMX network Image data travels peer-to-peer between organisations; DCMX coordinates and guards consent. A green line shows the encrypted image data flowing to the requesting organisation. DCMX Requesting organisation Map of the Netherlands with the DCMX network Image data travels peer-to-peer between organisations: Hospital C, Clinic D, Hospital A as the requesting organisation, and Diagnostic Centre B. DCMX coordinates and guards consent from the centre. Two green lines show the encrypted image data flowing to the requesting organisation. DCMX COORDINATION & CONSENT + + + + Hospital C Clinic D Hospital A Requesting organisation Diagnostic Centre B

In every organisation

DICOM:Router, the engine in your own network.

Every DCMX connection starts with DICOM:Router: software that orchestrates your local image flows. Rule-based routing between modalities, PACS and archive, with the DCMX link built in.

Locally autonomous: routing always keeps running
Routes Active
  • CT_SCANNER_1 PACS_MAIN TLS
  • MRI_* ARCHIVE TLS
  • ECHO_2 PACS_MAIN TLS

Illustrative rendering of the management console.

Diagram of DICOM:Router CT scanner, MRI and ultrasound send image data via C-STORE over TLS to DICOM:Router. DICOM:Router routes by AE title, modality and tag to PACS and Archive. The DCMX link is built in. DCMX DCMX LINK BUILT IN CT scanner CT_SCANNER_1 MRI MRI_1 Ultrasound ECHO_2 C-STORE · TLS DICOM:Router rule-based routing BY AE TITLE · MODALITY · TAG PACS PACS_MAIN Archive ARCHIVE

DCMX in four promises.

Available

Image data from across the country can be viewed straight away, at the moment it counts.

Reliable

Your local image flows keep running, even without a connection to the national network.

Secure

Image data travels directly and end-to-end encrypted between organisations, never through a central server.

Bounded

Outside the organisation nothing happens without consent — and the model that applies determines what is allowed.

Contact

Want to talk about connecting?

The network is being built. If you are a hospital, diagnostic centre or vendor and want to know what connecting involves — or would rather help shape it — we would like to hear from you.

Your message reaches us directly and does not pass through a third party. We use your details only to reply.