Buyer guide / Imaging integration

How to choose a DICOM router.

Choose a DICOM router by testing the imaging pathway you need to operate. A feature list is useful, but the decisive questions are whether your studies reach the intended destinations, retain their clinical context and remain manageable when something goes wrong.

Essential and desirable DICOM router functionality

Before comparing suppliers, identify which capabilities are mandatory for your service and which are desirable. Ask each supplier to demonstrate them using representative studies and workflows.

Essential DICOM router functionality and what to look for
Essential functionalityWhat to look for
On-the-fly DICOM tag morphingModify, map and normalise DICOM metadata during routing—for example, patient identifiers, accession numbers and institution names—to meet receiving-system requirements.
Large DICOM study streamingBegin forwarding incoming images before the complete study has arrived. Demonstrate performance with large studies and concurrent transfers, and show how study completeness is checked.
An easy-to-use interface, without programming or scriptingConfigure everyday routing rules and tag transformations through a clear graphical interface, without programming or scripting. Ask which tasks still require supplier assistance.
Flexible, rules-based routingRoute studies using DICOM attributes and source information, with support for multiple destinations, schedules and urgent-study prioritisation.
Reliable delivery and recoveryQueue studies when destinations are unavailable, retry failed transfers and make incomplete or unsuccessful deliveries visible to operators.
Clear monitoring and audit trailsShow what was received, where it was sent, what was changed and whether delivery succeeded, with searchable logs and actionable alerts.
Compatibility and securityDemonstrate support for the required DICOM objects and transfer syntaxes, secure connections and appropriate access controls. Supply a current DICOM conformance statement.

Desirable functionality—depending on your workflow

  • Relevant prior retrieval: automatically retrieve previous examinations using agreed patient and study criteria.
  • HL7, FHIR and DICOMweb integration: connect imaging transfers with orders, patient updates, results and modern applications.
  • AI workflow orchestration: route suitable studies to AI services and return outputs to the intended clinical systems.
  • De-identification: apply configurable anonymisation or pseudonymisation for research, trials and AI workflows.
  • High availability and scaling: maintain service during maintenance or failures and accommodate increasing volumes.
  • Safe configuration changes: test routing and transformation rules before activation, with configuration backup and rollback.

Ask for a practical demonstration: change a DICOM tag, stream a large study, configure a route without programming or scripting, interrupt a destination and show recovery. Confirm which capabilities are included in the quoted licence.

01

1. Inventory the real endpoints

List modalities, PACS, VNAs, workstations, AI services and receiving organisations. Collect available conformance statements and interface specifications. Include less common objects such as structured reports, presentation states, radiotherapy data or whole slide images where relevant.

02

2. Describe the routing decisions

Write down which studies should go where and why. Include copies to multiple destinations, scheduled routes, prior retrieval, transformations and any preparation required before AI processing. Ask the supplier to demonstrate representative decisions using your requirements.

03

3. Test identity and information flow

Establish the authoritative patient and order identifiers, then trace them through each hand-off. Test mismatches, corrections and report return. If HL7 or FHIR is involved, confirm the actual messages, resources and mappings against the interface specifications.

04

4. Examine interruptions and recovery

Ask what happens when a destination is unavailable, a connection drops or a study is incomplete. Request a demonstration of how operators identify an exception, investigate delivery and reconcile the result. Agree ownership of monitoring, support and recovery.

05

5. Measure a representative workload

Use realistic study sizes, object types and concurrent transfers. Record the hardware, network, source and destination constraints alongside results. Published throughput numbers are only meaningful when the test conditions resemble the environment you intend to run.

06

6. Agree acceptance and lifecycle costs

Record the workflows, validation evidence and responsibilities required for sign-off. Ask about licensing, hosting, implementation, interface changes, upgrades, support and exit arrangements. Confirm the proposed product and deployment match the evidence supplied.

Common questions

Before we connect.

What is a DICOM router?

A DICOM router receives medical imaging data and directs it between modalities, PACS, archives and other destinations according to configured rules. It can form part of a broader pathway for transformation, prior retrieval, clinical information exchange and AI processing.

What should a useful router demonstration include?

An end-to-end study transfer, a routing decision, a required transformation, a destination failure and recovery, and confirmation that the receiving system can retrieve and interpret the result.

How should we compare suppliers?

Give each supplier the same workflow, object types, volumes and acceptance criteria. Compare the demonstrated outcome, operational effort, integration responsibilities and total proposed costs.

How does Nexus fit into an imaging workflow?

Nexus is Pukka-j’s healthcare interoperability and orchestration platform. It connects DICOM, DICOMweb, HL7 and FHIR workflows around routing, retrieval, transformation and report return. Explore the Nexus product page, then bring your systems and requirements to a demonstration discussion.

Explore the connected pathway

Related products and guidance.

Talk to Pukka-j

Arrange a Nexus demonstration.

Tell us about your organisation, existing systems and the outcome you need. We’ll help map the next step.

Request a discussion