RadFuzion DICOM conformance overview

The DICOM services, SOP classes, transfer syntaxes and DICOMweb transactions RadFuzion supports, the AE titles, ports and TLS ports it uses, and what it doesn’t support today. Use it to check RadFuzion against your PACS, modalities and cloud store.

This page is an overview. The full RadFuzion DICOM Conformance Statement, in the DICOM PS3.2 format, lists every service with its matching and return keys, status codes and options: download the PDF. To check a specific system, ask sales.

Applies to RadFuzion 7.0.0 · Last reviewed

Application entities

RadFuzion runs three separate DICOM listeners. Each can also open a DICOM TLS port beside its plain one. Every AE title and port is configurable; these are the defaults.

RadFuzion application entities and default settings
Application entityDefault AE titleDefault portTLS port (off by default)Default stateWhat it does
Main receiverRADFUZION104 (11104 on Linux)2762OnReceives studies with C-STORE, answers C-ECHO and, when turned on, Storage Commitment and MPPS requests. It can also listen on more ports with the same AE title. Optional access rules limit it to listed calling AE titles (optionally from set IP addresses or ranges), to associations addressed to it, or to storage only. Outbound associations use a separate calling AE title (RADFUZION by default), which a destination can override. C-MOVE sub-operations from the image cache use the Q/R AE title.
Image cache Query/RetrieveRADFUZION_QR1111311115OffLets workstations find and pull recently forwarded studies from RadFuzion’s image cache with C-FIND, C-MOVE or C-GET. With pass-through on, it also answers from your archives, and pulls from them what the cache doesn’t have.
Modality Worklist (RadList)RADFUZION_MWL50105011OffAnswers Modality Worklist C-FIND queries from HL7 and manually entered orders, and, when turned on, takes MPPS from modalities.

Supported DICOM services

SCU means RadFuzion starts the request; SCP means it answers one. RadFuzion supports these services over the DICOM network.

DICOM services RadFuzion supports as SCU and SCP
ServiceSOP class UIDAs SCUAs SCPNotes
Verification (C-ECHO)1.2.840.10008.1.1YesYesSCP on all three AEs. As SCU: destination health checks (every 60 seconds by default) and the Test Connection button.
Storage (C-STORE)Each object’s own storage SOP classYesYesSCP: the main receiver accepts every storage SOP class, including private ones, and stores each instance as received; query and worklist requests sent to it are refused. Rule tag changes are later written into RadFuzion’s copy before it is forwarded. SCU: forwarding to DICOM destinations, sending each file under its own SOP class, and C-MOVE and C-GET sub-operations from the image cache. An image is never sent with its pixel data dropped.
Study Root Query/Retrieve – FIND1.2.840.10008.5.1.4.1.2.2.1YesYesSCU: study- and series-level queries to PACS and archives, for search, for RadFetch priors, and for rules that send a study to the archive that already has it. SCP: the image cache, at study, series and image level, with lists of UIDs and wildcards; up to 1,000 study or series matches per query by default. With pass-through on, each query also goes to the archives you choose, and their answers are merged with the cache’s, one per study.
Study Root Query/Retrieve – MOVE1.2.840.10008.5.1.4.1.2.2.2YesYesSCU: retrieves a study or series into RadFuzion’s receiver (or a move AE set per source). SCP: from the image cache, or with pass-through on, from the first archive that has what the cache lacks (pulled straight through, never routed); the move destination must be on the Q/R move list and set up as a DICOM destination.
Study Root Query/Retrieve – GET1.2.840.10008.5.1.4.1.2.2.3NoYesSCP: the image cache, and with pass-through on, the archives too. Offered by default whenever the Q/R AE is on, and can be switched off.
Modality Worklist – FIND1.2.840.10008.5.1.4.31Test toolYesRadList. Filters on accession, patient ID, name, birth date, scheduled date and time, station AE, performing physician and modality. SCU only in the Modality Simulator, a troubleshooting tool a person runs.
Modality Performed Procedure Step (N-CREATE, N-SET)1.2.840.10008.3.1.2.3.3YesYesRadList, off by default. SCP on the worklist AE and the main receiver: keeps each procedure step and shows it in RadList, and can mark the order started, then take it off the worklist once completed. SCU: passes every message on, in order, to the RIS or PACS you choose, and keeps retrying while it is down.
Storage Commitment Push Model (N-ACTION, N-EVENT-REPORT)1.2.840.10008.1.20.1YesYesSCP on the main receiver, off by default: confirms an image once it is stored, or only once every one of its destinations has accepted it, and replies on the same association or a new one to the requester. SCU per DICOM destination, off by default: asks the destination to confirm each exam forwarded to it, and shows Committed or Not committed, with Ask again for exams not confirmed in time.

Objects RadFuzion can create and send: Secondary Capture pages from SR reports, classic MR and CT images from Enhanced MR and CT, and Encapsulated PDF from uploaded PDFs.

Transfer syntaxes

Receiving

The main receiver accepts the first transfer syntax the sender proposes for each presentation context and stores the images as received. A presentation context with no transfer syntax is rejected.

Query, retrieve and worklist

The Q/R and worklist AEs accept Explicit VR Little Endian and Implicit VR Little Endian. For C-GET, the storage contexts also accept JPEG-LS Lossless, JPEG 2000 Lossless, JPEG Lossless SV1 and RLE Lossless.

Sending

By default images are forwarded in the transfer syntax they arrived in. A routing rule can convert them to one of the targets below. If converting an image fails, the original is sent instead and the fallback is logged.

Transfer syntaxes a routing rule can convert to
Transcode targetTransfer syntax UIDCompression
Explicit VR Little Endian1.2.840.10008.1.2.1None
Implicit VR Little Endian1.2.840.10008.1.2None
JPEG 2000 Lossless1.2.840.10008.1.2.4.90Lossless
JPEG Lossless, SV11.2.840.10008.1.2.4.70Lossless
RLE Lossless1.2.840.10008.1.2.5Lossless
HTJ2K Lossless1.2.840.10008.1.2.4.201Lossless (multi-frame sent as JPEG 2000 Lossless)
HTJ2K Lossless RPCL1.2.840.10008.1.2.4.202Lossless (multi-frame sent as JPEG 2000 Lossless)
JPEG Baseline1.2.840.10008.1.2.4.50Lossy (images over 8 bits sent as JPEG Extended)

JPEG Baseline is lossy. A rule’s transcode applies to every destination the exam is sent to, so use it only when none of them needs the original pixel data. HTJ2K is used for single-frame images; multi-frame images are sent as JPEG 2000 Lossless instead.

DICOMweb and cloud stores

RadFuzion is a DICOMweb client and a DICOMweb server. As a client it sends with STOW-RS, searches with QIDO-RS and retrieves instances with WADO-RS. Amazon S3 and Google Cloud Storage buckets are supported as object storage, written as .dcm files, not as DICOMweb.

As a client

DICOMweb services RadFuzion connects to, as a client
ServiceTransactionsAuthentication
Google Cloud Healthcare API (DICOM store)STOW-RS, QIDO-RS, WADO-RSA service-account JSON key, or Application Default Credentials when none is given (OAuth scope cloud-healthcare).
Azure Health Data Services (DICOM service)STOW-RS, QIDO-RS, WADO-RSMicrosoft Entra ID client credentials: tenant, client ID and client secret. Data partitions are supported.
Other DICOMweb serversSTOW-RS, QIDO-RS, WADO-RSA bearer token, or HTTP Basic user name and password.

As a server

Off by default. It runs on the web interface’s own port under /dicomweb (HTTPS when the web interface uses HTTPS). Each client system gets its own API key, sent as a bearer token, in an X-RadFuzion-ApiKey header or as the HTTP Basic password, and can be allowed to store, to search and retrieve, or both. Responses are DICOM JSON or XML, and every request is written to the Access Log.

DICOMweb transactions RadFuzion answers, as a server
ServiceTransactionsAuthentication
Store (STOW-RS)POST /studies, POST /studies/{study}Studies stored this way are completed and routed exactly like C-STORE, with the client’s name as the sender and DICOMWEB as the called AE title.
Search (QIDO-RS)Studies, series and instancesSearches the image cache, the same scope as the Q/R AE. A study is searchable once it has been forwarded and cached, about two minutes after it arrives. Up to 1,000 matches per search by default, paged with offset.
Retrieve (WADO-RS)Study, series and instance; metadata; framesExplicit VR Little Endian by default, as stored with transfer-syntax=*, or in another transfer syntax the client asks for. Exams still waiting to be forwarded can be retrieved too. Metadata is DICOM JSON or XML.

More on DICOM to Google Cloud and DICOM to Azure.

Associations, security and character sets

Associations

  • Up to 4 associations at a time to any one remote node for queries, retrieves and health checks (configurable).
  • Forwarding runs up to 8 exams at once by default and batches each send.
  • A failed send is retried; an unreachable destination has its exams held and sent once it answers again.
  • Warning statuses from a receiving SCP count as success.
  • RadFuzion’s listeners close a connection that sends no association request within 30 seconds, end associations idle for 5 minutes (configurable) and refuse a caller over the association limit at once.

Security

  • DICOM TLS (TLS 1.2 or 1.3) on its own port for the receiver, Q/R and worklist, with optional client certificates (mutual TLS). Off by default.
  • Outbound TLS per DICOM destination and Q/R source, checking the server by system trust or a pinned certificate, and sending a client certificate when the server asks for one. Revocation (CRL or OCSP) is not checked.
  • The main receiver can accept only listed calling AE titles (optionally from set IP addresses or ranges), only associations addressed to it, or storage only. Off by default; refused senders are logged and counted.
  • The Q/R AE only accepts calling AE titles on its allow list. An empty list lets no one in.
  • The worklist AE can be limited to an allow list of calling AE titles (open by default).

Character sets

  • Worklist responses use ISO_IR 100 (Latin-1), or ISO_IR 192 (UTF-8) when a name needs it. HL7 orders are read in the character set MSH-18 names.
  • Query/Retrieve responses, queries RadFuzion sends and DICOMweb searches use ISO_IR 192 (UTF-8) for text outside ASCII.
  • Received images are stored as received, with their Specific Character Set unchanged. Rule tag changes are later written into RadFuzion’s copy before it is forwarded.

Not supported today

If your workflow depends on one of these, talk to us before you plan around RadFuzion.

  • C-GET as SCU
  • Patient Root Query/Retrieve, as SCU or SCP
  • DICOMweb search of an archive: the DICOMweb server serves the image cache only
  • Removal of text burned into the pixel data while routing (de-identification changes header tags only; the optional Pixel PHI add-on makes a reviewed, redacted copy that a person downloads or sends to a destination)
  • Certificate revocation checks (CRL or OCSP) on TLS connections
  • DICOMweb server: rendered, thumbnail and bulk data resources, and CORS for browser apps on other sites

DICOM conformance questions

Does RadFuzion have a DICOM conformance statement?

Yes. The RadFuzion DICOM Conformance Statement follows the DICOM PS3.2 format and can be downloaded as a PDF from the DICOM conformance overview page. It covers every DICOM and DICOMweb service, the attributes each one matches and returns, status codes, transfer syntaxes, character sets, security, de-identification and the objects RadFuzion creates.

Which DICOM services does RadFuzion support?

RadFuzion supports Verification (C-ECHO), Storage (C-STORE) and Storage Commitment Push Model as both SCU and SCP. It queries and retrieves from PACS and archives with Study Root C-FIND and C-MOVE, serves C-FIND, C-MOVE and C-GET over its own image cache (and, with pass-through, your archives), answers Modality Worklist C-FIND queries through RadList, and takes MPPS from modalities and passes it on to the RIS. Patient Root Query/Retrieve and C-GET as SCU are not supported today.

Can RadFuzion send its audit log to our SIEM?

Yes. RadFuzion keeps an access log of sign-ins, exams opened, searches, exports and setting changes, and can send each event to your Syslog server or SIEM as it happens, as JSON or as IHE ATNA DICOM audit messages, over TLS, TCP or UDP. Events wait while the server is down and are sent in order once it is back.

Does RadFuzion support DICOMweb?

Yes, as a client and as a server. As a client, RadFuzion sends with STOW-RS and searches and retrieves with QIDO-RS and WADO-RS, to the Google Cloud Healthcare API, the Azure DICOM service and other DICOMweb servers. As a server, on the web interface’s own port under /dicomweb, other systems can send studies with STOW-RS and search and retrieve with QIDO-RS and WADO-RS, including metadata and frames, each with its own API key. Searches serve the image cache.

Does RadFuzion support DICOM TLS?

Yes. The DICOM receiver, Query/Retrieve and Modality Worklist can each open a TLS port beside the plain one (2762 for the receiver), using TLS 1.2 or 1.3 and optionally requiring client certificates. Each DICOM destination and Q/R source has its own TLS switch and checks the server by system trust or a pinned certificate. Certificate revocation (CRL or OCSP) is not checked. The plain ports stay available for devices that don’t support TLS.

Check RadFuzion against your systems

Walk through your PACS, modalities and cloud store with us.