What Orthanc actually is
Orthanc is a lightweight, open-source DICOM server built for hospitals and researchers who need a real DICOM engine without a commercial PACS license. It speaks C-STORE, DICOMweb and Stone rendering, ships a plugin system, and has a large community behind it. As a piece of DICOM infrastructure it is excellent, and it is not a toy: production imaging stacks run on it, including MiniPACS's own. Orthanc and the MiniPACS application share one Postgres database underneath, in disjoint tables, so this is not a marketing analogy. The engine really is Orthanc.
What Orthanc does not try to be is a finished clinic application. It has no worklist built for a front desk, no concept of staff roles, no audit log a compliance officer can hand to an auditor, and no support line. That is by design, not a shortcoming: Orthanc's maintainers built a DICOM server for people who already know how to build the rest. Orthanc is the engine, not the car, and it was never meant to be both.
Where DIY Orthanc stalls in a real clinic
Standing up Orthanc yourself gets a clinic a working DICOM receiver in an afternoon: point a modality at it, watch a C-STORE land, open the study in Orthanc Explorer or a Stone viewer. That part is genuinely fast, and it is why so many clinics start there. It rarely survives contact with the next six items, which are the parts that show up weeks later, not on day one.
- Users and roles. A tech, a radiologist and a front-desk admin need different screens and different permissions. Orthanc's own interface is not built for that split.
- Audit log. HIPAA's audit-controls requirement wants a way to record and examine who touched what study, when and from where. An append-only, exportable log that satisfies it is something to build, not something Orthanc ships.
- Backups. Encrypted, automated, tested backups are a project of their own: a passphrase-gated AES-256 job, a restore drill, an off-site copy.
- HIPAA paperwork. Business associate agreements, a written risk assessment, annual staff training, a contingency plan with a yearly restore test. None of it is code, all of it is required, and Orthanc's docs do not cover it.
- Upgrades. Security patches and version bumps land on someone's plate every month, forever, on top of their actual job.
- Support. When the worklist stalls at 8am and a radiologist is waiting, "post on the forum and wait" is not a support plan.
None of that is a knock on Orthanc. A hospital IT department with a DICOM engineer on staff can build all of it and often does. A radiology clinic with a front desk and a handful of readers usually cannot, and that gap is where DIY installs quietly stop being maintained.
An alternative that keeps the engine
MiniPACS does not replace Orthanc. It runs Orthanc as the DICOM engine underneath a clinic-facing product: a worklist that opens studies in about 2 seconds in any browser, reports attached to the study as DICOM so they travel with it on export, users and roles, an append-only audit log with CSV export, automatic encrypted backups, session controls (15-minute auto-logoff, instant revocation), and Vendo, a referral portal that lands referrals straight onto the same worklist. The disk, the backups and the audit log stay on the clinic's own server, the same self-hosted posture DIY Orthanc starts from.
The difference is who is responsible for the parts around the engine. With DIY Orthanc, the clinic is. With MiniPACS, updates and patches are installed remotely, priority support is a phone call with one dedicated person, and the read-only fallback keeps studies viewable even if a payment lapses. See the full product for the complete picture.
| DIY Orthanc | MiniPACS | |
|---|---|---|
| Setup | Self-configured, self-maintained | Remote install over a secure tunnel, from $1,500 one time |
| Day-to-day UI | Orthanc Explorer, built for engineers | Worklist built for a front desk, opens in about 2 seconds |
| Users & audit | Not built in | Roles plus an append-only, CSV-exportable audit log |
| Backups | A project to build yourself | Automatic, AES-256, passphrase-gated |
| HIPAA paperwork | The clinic's job alone | Built-in safeguards plus a documented matrix to work from |
| Referral portal | Not part of Orthanc | Vendo, referrals land straight on the worklist |
| Support | Community forum | Phone and email, one dedicated person, written into the license |
| Price | Free software, paid in staff time | $300/month flat per location, unlimited staff and machines |
Who should still run raw Orthanc
Being honest about fit matters more than winning every comparison. A hospital or research group with a DICOM engineer on staff, a custom pipeline to build, or a need to modify Orthanc's plugin internals directly is better served running Orthanc itself and building exactly what they need on top. Orthanc's plugin system exists for that kind of work, and no packaged product will beat a purpose-built integration for a team that has the engineering time to build one. Sending a bug report or a plugin fix upstream to Orthanc is also a better use of that team's time than switching engines, and MiniPACS benefits from that same upstream project every time it does.
MiniPACS is for the other case: a clinic that needs the worklist, the users, the audit log and the backups solved on day one, without hiring for it. If DIY Orthanc got a clinic as far as "the server accepts studies" and then stalled on everything after that, that is the exact gap MiniPACS closes. For the wider question of where the images live, see cloud PACS vs onsite; for PACS basics, see what is PACS.