Dicom protocol vs rest api

Hello,

I would like to have a better understanding on how the dicom protocol is working.

From what I read here: Understanding DICOM with Orthanc — Orthanc Book documentation
there is a “c-store” function is executed when you want to import dicom using the dicom protocol.
When using this last one, does it mean there is no interaction with the rest api exposed by orthanc ?
I see a ressource on the rest api on /modalities/{id}/store-straight, so I’m confused.

When using the upload dicom feature in the orthanc dashboard, what is used “under the hood” ? the rest api on POST /instances ? or /modalities/{id}/store-straight ? or something else ?

Thanks for the clarifications,
Br,
Fred

Hello,

The actual C-Store operation does not involve HTTP and is purely performed through the DICOM TCP/IP protocol.

However, the triggering of the operation in Orthanc is done through a REST API call.

This means that, when you choose “Send to modality”, the Orthanc Explorer web GUI makes a REST request to the Orthanc backend that, in turn, triggers the DICOM C-Store operation,

If Orthanc were a fat client application, you could imagine that a button would trigger the C-Store with no HTTP call involved, but Orthanc is “just” a server whose functionality is exposed through the REST API.

HTH

Benjamin

Note that this route is to instruct Orthanc to push a DICOM file to another DICOM modality via C-Store.
So, this is, in no way, equivalent to a POST to /instances that ingests a DICOM file into Orthanc itself.