Skip to Main Content
InterSystems Ideas

Have an idea, suggestion, or something that doesn’t work as expected in InterSystems products or services? Share it here on the InterSystems Ideas Portal.

The Ideas Portal is where community members can propose improvements, report bugs, and help influence the product roadmap across InterSystems products and the overall developer experience. 22% of submitted ideas are implemented by InterSystems or members of the Developer Community.

💡 Ideas and bugs are both welcome, no matter how big or small. You can submit feature requests, usability improvements, workflow suggestions, and bug reports. Whether you’re an experienced expert or just getting started, your fresh perspective is valuable.

🛠️ About bugs and fixes. If you have access to InterSystems WRC, please submit bugs there for immediate action. Bug reports submitted through the Ideas Portal are reviewed and tracked, but do not guarantee immediate resolution.

Start by sharing what could be better - the community and our teams will help take it from there.

Status Future consideration
Created by Enrico Parisi
Created on Jun 13, 2025

Make DICOM iteroperability adapter usable in Mirror configuration/environment

IRIS (for Health, HS HC, HS) DICOM interoperability adapters use the filesystem to store raw messages, the directory used can be configured in the StorageLocation production settings, obviously this is a big issue in mirrored environments if/when a mirror failover occur.

Having an High Availability shared directory between mirror members is expensive/complicated from MANY point of view (resources, configuration, maintenance, backup, security, etc.).

When an async DR is in place things are even much more complicated.

As it stands, using IRIS DICOM interoperability in mirror configuration it's a nightmare.

I understand that in some use cases the size of DICOM raw messages is significant (sometimes GBs each) and storing them in the database may impact performance and other aspects, however there are use cases where the DICOM raw messages are tiny (max 1K)

A real use case we have implemented and deployed of tiny raw DICOM messages is when IRIS is used to orchestrate archiving of studies between AETs, we use commands like CFIND, CMOVE etc. and never download a study in IRIS. In our system the biggest DICOM raw message file in 1K, no big deal to have it stored in a Global Stream in the database.

Unfortunately in IRIS it's not possible to change the IRIS DICOM raw message storage from File Stream to Global Stream.

The idea is to provide the option to use global streams stored in the database instead of external files to store DICOM raw messages, this would solve the issue in mirror configurations.

If size is a concerns, add a proper warning in the documentation that using Global Stream in some scenario may impact system performance.

The benefit of this idea is to allow using a IRIS mirror configuration for IRIS DICOM interoperability "out of the box", without the need to implement an High Availability shared directory for storing DICOM raw messages and works nicely "out of the box" even when using Async mirror members for Disaster Recovery.

  • ADMIN RESPONSE
    Aug 27, 2025

    Thank you for submitting the idea. The status has been changed to "Future consideration".

    Stay tuned!

  • Daniel Palevski
    Aug 6, 2025

    @Stefan Wittmann - should this be assigned to you?