Slicer PACS integration

We are looking into how feasible it is to pull patients from the clinical PACS system into Slicer for research purposes. Do we use DICOM browser for this, is it as simple as putting in the IP address of the server into the browser?

I appreciate any feedback, documentation as I will pass this to our radiology system admins for them to evaluate.

1 Like

Hi Murat -

DICOM networking (technically DIMSE) is supported by Slicer for query and retrieve using CGET or CFIND/CMOVE if you set up the IP address, port, and AETITLE correctly on both the Slicer and PACS side. This usually means to you need to get the blessing and help of the radiology network administrators, and access policies vary from site to site. Some people may be reluctant to allow research software on their network or they worry about bogging down the network or servers.

I typically suggest debugging first with dcmtk command line tools and then just copying the settings into Slicer and everything should just work because we use dcmtk under the hood.

Sending to PACS (CSTORE) is not enabled in Slicer in part because most sites prohibit research data in the clinical pacs. For people who need to push it’s a single command line (storescu in dcmtk). It sounds like you don’t need that.


Thanks Steve. That’s all I needed.

If you have done it successfully, can you share it here?

So, is it complete now? If yes, then please send it here…I’m still confused about it.

Slicer works as described above. DICOM networking is a complex topic, but well described (for example in this book). Once you know the concepts they can be applied in the slicer environment.

@Robert_Leo @timeanddoctor

Just to clarify, we needed those information to check with our clinical radiology IT department. In the end, we couldn’t do it due to audit trail requirements and a lot of compliance issues. For us, it is logistically easier to get clinical imaging core extract the data in bulk after IRB approval, and we take it from there.

1 Like