Nexus / DICOM routing

DICOM routing built around your imaging workflow.

A DICOM router receives medical imaging data and directs it between scanners, PACS, archives and other destinations. Nexus combines routing with transformation and workflow orchestration, so image movement can follow the needs of your imaging service.

01

Connect modalities and archives

Use Nexus between source modalities, PACS and receiving systems to manage the flow of DICOM data. Start with the sending and receiving conformance statements, supported object types and transfer syntaxes. Agree the connectivity and validation required for each route.

02

Route by workflow rules

Different studies can need different destinations. Define routes using DICOM metadata and workflow context, including paths for reporting, archive migration or AI processing. Agree when a study should be copied, transformed, retrieved or held for investigation.

03

Keep clinical context connected

Image delivery is one part of the pathway. Nexus also supports clinical information exchange through HL7 and FHIR, prior retrieval and report return. Map patient and order identifiers across the pathway so images and results reach the intended clinical record.

04

Plan operations before go-live

Bring expected study volumes, peak periods, network constraints and destination requirements to the design discussion. Agree handling of interrupted transfers, maintenance windows, reconciliation and support responsibilities, then test representative studies against the receiving systems.

Common questions

Before we connect.

Is Nexus a DICOM router or a PACS?

Nexus is the interoperability and orchestration layer for routing, retrieving and transforming data. Nexus PACS is a separate product for cloud image management, viewing, storage and sharing. Nexus can connect an existing PACS without requiring the whole product portfolio.

Can a DICOM router support imaging AI?

Nexus can route imaging into an AI workflow and return outputs to connected systems. The implementation depends on the AI service, accepted input and output formats, identity mapping and the receiving clinical workflow.

What should we bring to a demonstration?

Bring a diagram of your systems, the source and destination names, DICOM conformance statements where available, expected volumes and the workflow problem. Use synthetic or appropriately de-identified examples when discussing data.

Explore the connected pathway

Related products and guidance.

Talk to Pukka-j

Discuss your DICOM routing workflow.

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

Request a discussion