ORTHANC(8)

πŸ‘‘ ORTHANC(8) β€” like, the manual page, but make it make sense πŸ’–

okay bestie, welcome to the Orthanc man page. This is the System Administration Utilities corner of the internet and we're about to have a whole moment. Sit down, hydrate, let's go. 🫢


✨ NAME ✨

Orthanc β€” a lightweight, RESTful DICOM server for healthcare and medical research. That's it, that's the girl. πŸ’…


🌸 SYNOPSIS 🌸

Orthanc [OPTION]... [CONFIGURATION]

πŸ¦‹ DESCRIPTION πŸ¦‹

Orthanc: lightweight, RESTful DICOM server for healthcare and medical research. Say it with me now. πŸ“£

So the CONFIGURATION argument? It can be a single file OR a directory. And if it's a directory, every single JSON file inside it gets merged together. Iconic behavior honestly. If you don't hand it a configuration path on the command line at all, then a set of default parameters just gets used, no biggie, she improvises. ✨

If you want the full instructions on how to actually use Orthanc, go read the Orthanc Book at https://orthanc.uclouvain.be/book/. It's giving documentation. πŸ“š

⚠️ PAY ATTENTION BESTIE. The order of the options MATTERS. Options are read left to right. So for real, options like --verbose can reset the value of other log-related options that were read before it. Left to right. That's the law. 😭

And if you're trying to debug DICOM communications, the recommended set of options is:

--verbose --trace-dicom --logfile=dicom.log

Write that down. Put it in your notes app. πŸŽ€


πŸ’– Command-line options: πŸ’–

  • --help β€” display this help and exit. She's helpful like that. πŸ’β€β™€οΈ
  • --logdir=[dir] β€” the directory where the log files get stored. By default? The log is dumped to stderr. 🫠
  • --logfile=[file] β€” the file where Orthanc's log gets stored. Again, by default the log is dumped to stderr. πŸ“„
  • --config=[file] β€” creates a sample configuration file and then exits. And if file is -, it dumps to stdout instead. Cute, right? ✨
  • --errors β€” prints the supported error codes and exits. πŸ”
  • --verbose β€” be verbose in logs. She's talking now. πŸ—£οΈ
  • --trace β€” highest verbosity in logs, for debug. She's screaming. πŸ”₯
  • --upgrade β€” allows Orthanc to upgrade the version of the database. > 🚨 BEWARE: the database will become incompatible with former versions of Orthanc. No take-backs. No undo button. Think before you press. πŸ’€
  • --no-jobs β€” don't restart the jobs that were stored during the last execution of Orthanc. She's letting them sleep in. 😴
  • --openapi=[file] β€” writes the OpenAPI documentation and exits. If file is -, it dumps to stdout. πŸ“
  • --cheatsheet=[file] β€” writes the cheat sheet of REST API as CSV and exits. If file is -, it dumps to stdout. Yes bestie, a literal cheat sheet. πŸŽ€
  • --version β€” output version information and exit. πŸ‘‘

πŸŽ€ Fine-tuning of log categories: πŸŽ€

Like, per-category control? We love options. Every category here gets a verbose version and a trace version, where trace = highest verbosity. Matching set, slay. πŸ’…

  • --verbose-generic β€” be verbose in logs of category "generic"
  • --trace-generic β€” use highest verbosity for logs of category "generic"
  • --verbose-plugins β€” be verbose in logs of category "plugins"
  • --trace-plugins β€” use highest verbosity for logs of category "plugins"
  • --verbose-http β€” be verbose in logs of category "http"
  • --trace-http β€” use highest verbosity for logs of category "http"
  • --verbose-sqlite β€” be verbose in logs of category "sqlite"
  • --trace-sqlite β€” use highest verbosity for logs of category "sqlite"
  • --verbose-dicom β€” be verbose in logs of category "dicom"
  • --trace-dicom β€” use highest verbosity for logs of category "dicom"
  • --verbose-jobs β€” be verbose in logs of category "jobs"
  • --trace-jobs β€” use highest verbosity for logs of category "jobs"
  • --verbose-lua β€” be verbose in logs of category "lua"
  • --trace-lua β€” use highest verbosity for logs of category "lua"

🌈 Exit status: 🌈

  1. 0 β€” if success. πŸŽ‰ We ate.
  2. -1 β€” if error. 😭 And bestie, have a look at the logs.

πŸ’œ AUTHOR πŸ’œ

Written by Sebastien Jodogne <s.jodogne@orthanc-labs.com>. Yes, the main character. πŸ‘‘


  • Copyright Β© 2012-2016 Sebastien Jodogne, Medical Physics Department, University Hospital of Liege (Belgium)
  • Copyright Β© 2017-2023 Osimis S.A. (Belgium)
  • Copyright Β© 2024-2026 Orthanc Team SRL (Belgium)
  • Copyright Β© 2021-2026 Sebastien Jodogne, ICTEAM UCLouvain (Belgium)
  • Licensing GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
  • This is free software: you are free to change and redistribute it.
  • There is NO WARRANTY, to the extent permitted by law.

okay that's the whole thing, you made it to the end, I'm so proud of you πŸ₯Ήβœ¨ Go forth and run your DICOM server, bestie. πŸ’…

This was the Orthanc page, version 1.12.11, dated April 2026, hanging out in section 8 of the manual. mwah πŸ’–

πŸ“¦ where this page comes from