This project is built up on the great work done by GRAIL (https://github.com/grailbio/go-netdicom)

• Dicompot is a fully functional DICOM server with a twist.
• Please note: C-STORE attempts are blocked for your "protection", but logged.

(Ubuntu 22.04 LTS)

• sudo apt install golang
• git clone https://github.com/nsmfoo/dicompot.git
• cd dicompot
• go install server/dicompot.go

(macos 13.5 )

• brew install golang
• git clone https://github.com/nsmfoo/dicompot.git
• cd dicompot
• go install server/dicompot.go

• cd $HOME/go/bin
• ./dicompot
• ./dicompot -help, for the different options that is available
• The server will log to the console and also to a file called dicompot.log (JSON)
• Works well with screen, if you like to run it in the background

• findscu -P -k PatientName="*" IP PORT
• getscu -P -k PatientName="*" IP PORT

Both commands are part of the DICOM Toolkit - DCMTK

• Also tested with Horos (https://horosproject.org/)

1. git clone https://github.com/nsmfoo/dicompot.git

2. cd dicompot

3. docker build -t dicompot:latest .

docker run --rm --read-only --net="host" --name="dicompot" --detach --tty --interactive --publish=11112:11112 dicompot:latest

• --rm: remove container after it stops
• --read-only: mount container as read-only
• --net="host": set container network as host
• --name="dicompot": set container name as dicompot
• --detach: run in the background hint: use docker attach dicompot to re-attach STDIN/STDOUT back to the container
• --tty: allocate a pseudo-tty for the container
• --interactive: make the container interactive

• docker logs dicompot

If the server instance, terminates with the message: "signal: killed", try increasing the amount of avalible memory and try again. (dmesg, should give you more information)

• Enforce AET (So people can brute force away)
• Auto generate meta data in DICOM files (for use in dicompot)
• Block certain IP's (Geo based, amount of connections etc)
• Code cleanup

I'm in no way a DICOM expert. If you find something strange... it probably is. This is also the first GO code I ever touched, so in the same way, if something looks strange it probably is. That being said any help and/or suggestions are more than welcome.