Welcome to Nexus
What is Nexus?
Nexus is the culmination of over 20 years of practical experience working in the field of connecting Medical Imaging systems and solving real world interoperability issues and workflows. All the underlying technology has been proven with numerous modalities, PACS, VNA, RIS, EHR and lately many AI solutions.
Who is it for?
-
IT and PACS Managers
-
Small and Large Imaging Centres / Hospitals
-
Teleradiology companies
-
Machine Learning / Algorithm development
-
AI Orchestrating
-
AI & Imaging Companies technology stack
How does it work?
Nexus provides an easy Drag and Drop interface where a user can connect a series of Nodes together to form what we call a pipeline. A pipeline is like plumbing and can be split in as many ways as required to allow the flow of data between systems. Each Node has its own intuitive configuration which requires minimal technical expertise. The platform can have as many pipelines as you want, pipelines can be named and comments added to individual nodes to allow maximum collaboration and supportability between teams.
What kind of use cases is it for?
Well it's pretty limitless but here are some uses.
​
-
DICOM routing from modality to on-prem PACS and to cloud storage.
-
Proxy multiple DICOM modality worklists from a single modality
-
Proxy multiple PACS to a single viewing workstation.
-
Annoymise DICOM to an AI in the cloud, de-annoymise to push AI results back into the PACS and convert to HL7 to update a RIS,PACS or EHR.
-
DICOM Data migration, with data cleansing/fixing.
-
Fault tolerance and load balancing of DICOM imaging.
​
​
​
​
What else can it do?
Key Features
Operating system / architecture neutral
DICOM Connectivity
HL7 Connectivity
SQL Connectivity
​
Multiple DICOM listening port configuration
• Handles multiple streams of data on user definable range of ports.
• AET configuration and promiscuous connectivity
• SOP class and transfer syntax configuration Simple DICOM proxy
• Redirect CMOVE / CFIND requests to external system to provide a single point of communication to clients.
• Combine modality worklists. Multiple HL7 listening port configuration
• Handle multiple streams of HL7 data on user customisable ports. Multi-threaded DICOM file input
• Read a file source of DICOM data using multiple threads to rapidly read, process and forward files to a DICOM compatible system FTP DICOM file input
• Retrieve data from an FTP file source to process and send to a DICOM system HL7 File input
• Read HL7 V2 formatted files to modify and forward to HL7 compatible systems
DICOM modality output simulator
• The DICOM Simulator Node is designed for testing and benchmarking systems. It can be configured to create fictitious DICOM studies to be sent on at a configurable rate and allows the network to be tested before any inbound communications are required.
Intelligent DICOM / HL7 routing
• Ability to replicate DICOM streams through multiple processing pipelines.
• Routing based on meta data information in the DICOM header or AETs.
• Ability to switch on/off pathways.
• HL7 filtering based on DICOM queries to only permit known records to be processed. Versatile
DICOM meta data manipulation
• DICOM tag editing.
• Swap DICOM tags.
• Delete DICOM Tags.
• Mathematical operations on DICOM values. Intelligent DICOM anonymisation
• User customisable DICOM tag anonymisation.
• AET based anonymisation customisation.
• Pseudo-anonymisation options for registering trial participants.
• Intelligent re-UID options to maintain object references in the meta data DICOM Redaction
• Replaces incorrect or unwanted pixel information with a background colour.
DICOM image decompression
• Decompress pixel data in know formats (e.g. JPEG2000) for systems that may not handle this.
DICOM image transform processing
• Apply rotational and flip operations on pixel data in the processing pipeline. DICOM syntax conversion
• Convert between transfer syntaxes on the fly in communications between external systems. SQL database information recording
• Record key information in user customisable SQL database connections.
• Query on database to query for record in order to audit transferred information. DICOM reconciliation
• Update DICOM meta data with that found in an external database.
​
DICOM communications output
• Communicate with external DICOM archives or worklists.
• Retrieve data using CGET or CMOVE.
• Proxy query / retrieve / store requests.
• Error handling channel for caching data in the event of communications failures. HL7 communications output
• Communicate with external HL7 consumers to pass on routed and modified information.
DICOM File output
• Write processed DICOM objects to a file system.
• Optionally compress the objects.
• Configurable storage hierarchy. HL7 File output
• Write HL7 information to a file system as a .dat file for archiving or caching for delayed processing.
How does it work?
Nexus provides an easy Drag and Drop interface where a user can connect a series of Nodes together to form what we call a pipeline. A pipeline is like plumbing and can be split in as many ways as required to allow the flow of data between systems. Each Node has its own intuitive configuration which requires minimal technical expertise. The platform can have as many pipelines as you want, pipelines can be named and comments added to individual nodes to allow maximum collaboration and supportability between teams.
What kind of use cases is it for?
Well it's pretty limitless but here are some uses.
​
-
DICOM routing from modality to on-prem PACS and a copy to cloud storage.
-
Proxy multiple DICOM modality worklists from a single modality
-
Proxy multiple PACS to a single viewing workstation.
-
Annoymise DICOM to an AI in the cloud, de-annoymise to push AI results back into the PACS and convert to HL7 to update a RIS,PACS or EHR.
​
​
​
​
What else can it do?
Key Features
Operating system / architecture neutral
DICOM Connectivity
HL7 Connectivity
SQL Connectivity
​
Multiple DICOM listening port configuration
• Handles multiple streams of data on user definable range of ports.
• AET configuration and promiscuous connectivity
• SOP class and transfer syntax configuration Simple DICOM proxy
• Redirect CMOVE / CFIND requests to external system to provide a single point of communication to clients.
• Combine modality worklists. Multiple HL7 listening port configuration
• Handle multiple streams of HL7 data on user customisable ports. Multi-threaded DICOM file input
• Read a file source of DICOM data using multiple threads to rapidly read, process and forward files to a DICOM compatible system FTP DICOM file input
• Retrieve data from an FTP file source to process and send to a DICOM system HL7 File input
• Read HL7 V2 formatted files to modify and forward to HL7 compatible systems
DICOM modality output simulator
• The DICOM Simulator Node is designed for testing and benchmarking systems. It can be configured to create fictitious DICOM studies to be sent on at a configurable rate and allows the network to be tested before any inbound communications are required.
Intelligent DICOM / HL7 routing
• Ability to replicate DICOM streams through multiple processing pipelines.
• Routing based on meta data information in the DICOM header or AETs.
• Ability to switch on/off pathways.
• HL7 filtering based on DICOM queries to only permit known records to be processed. Versatile
DICOM meta data manipulation
• DICOM tag editing.
• Swap DICOM tags.
• Delete DICOM Tags.
• Mathematical operations on DICOM values. Intelligent DICOM anonymisation
• User customisable DICOM tag anonymisation.
• AET based anonymisation customisation.
• Pseudo-anonymisation options for registering trial participants.
• Intelligent re-UID options to maintain object references in the meta data DICOM Redaction
• Replaces incorrect or unwanted pixel information with a background colour.
DICOM image decompression
• Decompress pixel data in know formats (e.g. JPEG2000) for systems that may not handle this.
DICOM image transform processing
• Apply rotational and flip operations on pixel data in the processing pipeline. DICOM syntax conversion
• Convert between transfer syntaxes on the fly in communications between external systems. SQL database information recording
• Record key information in user customisable SQL database connections.
• Query on database to query for record in order to audit transferred information. DICOM reconciliation
• Update DICOM meta data with that found in an external database.
​
DICOM communications output
• Communicate with external DICOM archives or worklists.
• Retrieve data using CGET or CMOVE.
• Proxy query / retrieve / store requests.
• Error handling channel for caching data in the event of communications failures. HL7 communications output
• Communicate with external HL7 consumers to pass on routed and modified information.
DICOM File output
• Write processed DICOM objects to a file system.
• Optionally compress the objects.
• Configurable storage hierarchy. HL7 File output
• Write HL7 information to a file system as a .dat file for archiving or caching for delayed processing.