Skip to main content
Download RadpicsAI mobile app QR Code
Download the AppScan to install RadpicsAI mobile App

©2025-26 RadpicsAI, all rights reserved

DICOM integration

DICOM and DICOMweb integration

Connect modalities, PACS and imaging applications: receive studies, give modalities their worklist, route studies by rule, and search and retrieve them over DICOMweb.

Book an Integration DemoContact our team
C-STORE · MWL C-FIND · DICOM Exchange · QIDO-RS · WADO-RS
Standards and connectivity

Supported DICOM services

Support differs by message type and direction. Interfaces for your systems and versions are confirmed during scoping.

DICOM

  • Receive studies from modalities and PACS (C-STORE SCP)
  • MWL Service: Modality Worklist for your modalities (MWL C-FIND SCP)
  • Send studies to other PACS or applications by rule (C-STORE SCU)
  • DICOM Exchange: move studies between PACS, sites and RadpicsAI cloud
  • Encrypted transport (TLS) for DICOM links

DICOMweb

  • DICOMweb search and retrieve (QIDO-RS, WADO-RS)
Storing studies over DICOMweb (STOW-RS) is not supported.
Use cases

Where teams use DICOM integration

RIS/PACS and imaging workflow connectivity

Hospitals · Imaging centres
The gap
Orders are re-typed at the modality, and studies reach PACS without the right patient or order.
How MiddleOffice helps
Modality Worklist gives modalities the scheduled order from MedCARE™ or your current RIS, and studies arrive in MedPACS™ or your PACS with that order attached.
Relies on
  • MWL Service
  • DICOM receive
  • DICOM send by rule

Multi-facility interoperability

Hospital networks · Teleradiology providers
The gap
Studies and orders must move between sites that run different systems.
How MiddleOffice helps
An on-site gateway at each facility connects to RadpicsAI cloud, and routing rules send studies to the right site or reading team.
Relies on
  • On-site DICOM gateway
  • DICOM Exchange between facilities
  • Rule-based study routing
  • Automatic radiologist assignment

AI applications in clinical workflows

Hospitals · AI and analytics vendors
The gap
Each AI pilot needs its own route to images and a way back into the reporting workflow.
How MiddleOffice helps
Studies are routed to the application by rule or retrieved through DICOMweb, and its output can be written back as a DiagnosticReport through the FHIR API. MiddleOffice moves the data; it does not analyse images.
Relies on
  • DICOM send by rule
  • DICOMweb search and retrieve
  • FHIR DiagnosticReport create
FAQ

Frequently asked questions

Which DICOM services are supported?

Receiving studies from modalities and PACS (C-STORE SCP), Modality Worklist for your modalities (MWL C-FIND SCP), sending studies to other PACS or applications by rule (C-STORE SCU), and DICOM Exchange between PACS, sites and RadpicsAI cloud. DICOM links can use encrypted transport (TLS).

Is DICOMweb supported?

Yes, for search and retrieve (QIDO-RS and WADO-RS). Storing studies over DICOMweb (STOW-RS) is not supported.

Can studies move between sites?

Yes. An on-site gateway at each facility connects to RadpicsAI cloud, and DICOM Exchange and routing rules send studies to the right site or reading team.

Can we keep our current PACS?

Yes. Studies can be stored in MedPACS™ or your PACS, and MedVIEWER™ can be added as a zero-footprint viewer alongside your existing PACS.

Which vendors and systems have you integrated with?

We do not publish vendor names without permission. Tell us your systems and versions, and we will confirm the interfaces available for each during scoping.

Connect your modalities and PACS

Tell us your modalities, PACS and sites, and we will confirm the DICOM services for each.
Book an Integration DemoContact our team