Orthanc deleting new dicoms

General
1

I have a unique setup where I am using Orthanc to transfer DICOMs from a CT scan station to Azure Blob Storage. When the DICOMs get to Azure, they are immediately removed from the landing folder (using a blob trigger) and moved to another dated folder to be processed by a machine learning model. The issue is that Orthanc seems to keep a record of the DICOMs, and sometimes it transfers the DICOMs to Azure and immediately deletes them with the log message that the blob is already stored. When this happens, it deletes multiple DICOMs at the same time with the same message, even though these are new scans. I need help to turn off this feature that deletes the DICOMs

I0709 07:52:09.137148 main.cpp:353] Incoming Store request from AET C3S-CERETOM02 on IP 172.22.66.103, calling AET ORTHANC
I0709 07:52:09.152771 PluginsManager.cpp:161] (plugins) Azure Blob Storage: creating attachment 71d48b81-6ddc-446c-9b88-91b6518c1f30 of type 1
I0709 07:52:09.230959 PluginsManager.cpp:161] (plugins) Azure Blob Storage: deleting attachment 71d48b81-6ddc-446c-9b88-91b6518c1f30 of type 1
I0709 07:52:09.262208 ServerContext.cpp:653] Already stored
T0709 07:52:09.262208 CommandDispatcher.cpp:735] (dicom) Status Detail:

Dicom-Data-Set

Used TransferSyntax: Little Endian Implicit

(0000,1031) US (no value available) # 0, 0 MoveOriginatorMessageID

T0709 07:52:09.262208 CommandDispatcher.cpp:758] (dicom) Received Command:
===================== INCOMING DIMSE MESSAGE ====================
Message Type : C-STORE RQ
Presentation Context ID : 3
Message ID : 1
Affected SOP Class UID : CTImageStorage
Affected SOP Instance UID : 2.16.840.114379.3000.573.20240709.1074920.5.1.134
Data Set : present
Priority : medium
Move Originator AE Title :
======================= END DIMSE MESSAGE =======================
I0709 07:52:09.262208 main.cpp:353] Incoming Store request from AET C3S-CERETOM02 on IP 172.22.66.103, calling AET ORTHANC
I0709 07:52:09.277767 PluginsManager.cpp:161] (plugins) Azure Blob Storage: creating attachment 9b6490ed-4d25-4692-8ee9-eacad6a2d3d5 of type 1
I0709 07:52:09.355925 PluginsManager.cpp:161] (plugins) Azure Blob Storage: deleting attachment 9b6490ed-4d25-4692-8ee9-eacad6a2d3d5 of type 1
I0709 07:52:09.402782 ServerContext.cpp:653] Already stored
T0709 07:52:09.402782 CommandDispatcher.cpp:735] (dicom) Status Detail:

2

Hi,

First note: you should not expect any normal behavior if another script is deleting files in the Orthanc storage.

If Orthanc deletes the files, that’s because they are considered as duplicates because of ID collisions (check Orthanc identifiers — Orthanc Book documentation). You can set "OverwriteInstances" to false but, that just means that Orthanc will not store what you consider as “new scans”.

HTH,

Alain