Update DICOMhawk's API Interface to mimic a real PACS Server

[anshikasharmaa1517]

Currently, we do not have a dedicated interface for different pacs servers. So, having multiple interfaces for it, would work well.

[RicYaben]

Hey @anshikasharmaa1517 can you update the description of this? otherwise will close until we can touch the API

[kirmada1509]

Hi @RicYaben, I'm interested in picking this up for the upcoming GSoC cycle.

To make the emulation more realistic, I'm looking at implementing handlers for C-GET and C-MOVE requests using pynetdicom, and ensuring the metadata responses match what a standard PACS like orthanc would return.

I've already set up the environment locally via Docker. Should I start by drafting a proposal for the API changes here, or would you prefer a small proof-of-concept PR first?

[RicYaben]

Hi @kirmada1509, all those things you mentioned are already part of the code, as far as I know.

For future reference:

• pynetdicom does not make the server more realistic, there are no dicom viewers/servers using python
• Orthanc is not written in Python, and is not a certified product. This is not a feature of DICOMhawk, but a legacy misunderstanding of how DICOM is used (or should be used)
• The API is not the problem, and I would suggest against developing it further; we cannot have a web portal announcing ORTHANC and serving an OSIRIX app
• This is a DICOM honeypot, not PACS or H7, lets stick to the basics until we get this done

We can revisit it in the future with @anshikasharmaa1517 comment: multiple interfaces for different applications, but right now is not a priority.