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.

  • NationwideEvery accredited healthcare organisation can connect.
  • Peer-to-peer, encryptedImages travel directly, never through a central server.
  • Consent as the gateOutside your own walls nothing happens without a legal basis.

The case

One patient, an unknown history.

A patient's history is scattered across hospitals and diagnostic centres throughout the country. Whoever wants to bring it together today phones, waits and meanwhile decides without the full picture — while care demands speed. Two moments from practice.

The night · emergency department

Deciding now, without the whole picture.

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

  2. A call to the on-duty radiology there. Waiting for a call back, a fax or a secure e-mail.

  3. The images arrive — with luck — by a detour. The team has already had to decide.

The morning · radiology

Duplicate work nobody sees coming.

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

  2. Nobody knows that two other organisations have already imaged this patient.

  3. The examination is done again: extra radiation, extra cost, a comparison that never gets made.

That is why DCMX

DCMX

With DCMX the earlier study sits next to the new scan within three minutes — directly from organisation to organisation, encrypted, and only after the legal basis has been checked. And in the regular workflow the network flags in advance that imaging exists elsewhere, so nobody has to ring around and nothing is done twice.

Fictional scenarios, for illustration.

The approach

One nationwide network. Two steps to connect.

DCMX is the national network that accredited healthcare organisations connect to. No central image store, but a network of routers that know each other, trust each other and query each other directly. Connecting takes two steps, each valuable on its own.

01

Install DICOM:Router

An image router in your own network, for your own image flows: rule-based routing between modalities, PACS and archive, de-identification and local search. Fully on its own, with no dependency on the network.

02

Activate DCMX functionality

The same router enrols with DCMX; that makes the network functions available: federated search and retrieval at other organisations, the consent gate and the registers. In parallel with step 1, at your own pace.

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.

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

For PACS and EHR vendors

Integrating is one URL. The PACS button opens, for the patient on screen, a small window with the studies available elsewhere for this patient — with your own patient number; the router translates the rest.

https://<router>/webhook?patientid={PatientID}
Routes Active
  • CT_SCANNER_1 PACS_MAIN TLS
  • MRI_* ARCHIVE TLS
  • ECHO_2 PACS_MAIN TLS

Illustrative rendering of the management console.

How it works

From modality to archive: one router, five steps. Scroll along.

  1. 01Receiving

    Every modality delivers to one address.

    CT, MRI and ultrasound send their images with C-STORE over TLS to DICOM:Router. One AE title, one port, one place to manage; the modalities see nothing of what sits behind it.

  2. 02Rules

    Routing on rules, not on handwork.

    The rules engine looks at AE title, modality and DICOM tags and decides per study where it goes: the CT to the PACS, every MRI to the archive. Rules are versioned and can be dry-run before they go live.

  3. 03Delivery

    Delivered, even when it does not work the first time.

    Every study passes through a queue with retries. If the PACS drops out for a moment, the router holds the images and delivers them as soon as it can — nothing gets lost, everything can be traced.

  4. 04DCMX link

    The door to the national network is built in.

    The same router enrols with DCMX, sets up the encrypted tunnels and guards the consent gate and the registers. Whatever the organisation shares and retrieves passes this one point.

  5. 05Autonomous

    Locally autonomous: routing always carries on.

    If the network connection drops, everything inside the organisation keeps running. The DCMX link is a door, not a load-bearing wall.

    Illustrative rendering; system names are examples.

The national network

Image data from across the country.

DCMX coordinates and guards consent; the image data travels directly from organisation to organisation. Scroll along with one federated request — from question to register.

  1. 01The question

    One question, from Hospital A.

    Does imaging of this patient exist elsewhere? The request leaves with the hospital's own patient number; the router translates it through the EHR into the national citizen number (BSN). Name and date of birth do not travel.

  2. 02Coordination

    DCMX points the way, not the images.

    The DCMX Root Servers — run redundantly, so the network never hangs on one machine — know the connected organisations and confirm who is who. They see no images and no patient data — only who is a member and who may talk to whom.

  3. 03Consent

    Every organisation decides for itself.

    The question reaches the other organisations' routers directly, over encrypted tunnels. Each router checks its own EHR for standing consent. Hospital C and Diagnostic Centre B: yes. Clinic D has nothing for this patient.

  4. 04Image data

    Directly, encrypted, router to router.

    The images flow peer-to-peer from C and B to A — never through DCMX. On arrival they receive Hospital A's patient number and a provenance mark, so where they came from stays visible.

  5. 05Recorded

    In the register, on both sides.

    Hospital A records what it received; C and B what they disclosed — under the same reference, so two registers describe one event. Three minutes after the question, the images sit next to the new scan.

    • Image data to the requesting organisation · encrypted, peer-to-peer
    • Question from router to router · encrypted tunnel
    • Coordination & consent (DCMX)

    Fictional scenario for illustration; organisations and references are invented.

Connect

Connecting to DCMX.

The network is being built. This is what connecting looks like — and if you are a hospital, diagnostic centre or vendor, we would like to hear from you.

  1. 01

    Introduction and assessment

    Together we look at your situation and at the conditions for joining as an accredited healthcare organisation.

  2. 02

    Install DICOM:Router

    In your own network, connected to PACS and EHR. Usable for internal routing straight away.

  3. 03

    Enrol with DCMX

    The router announces itself; once approved it receives its certificate and sets up the encrypted tunnels.

  4. 04

    Live on the network

    Federated search and retrieval, the consent gate and the registers are active.

DCMX is an initiative of SKY Medical Group, Enschede, the Netherlands.

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