# MiniPACS in depth > Section index of https://minipacs.net/llms.txt for the MiniPACS product: the > self-hosted PACS (DICOM archive and hub, live worklist, browser viewers, > reporting, patient sharing, backups). $300 per location per month, flat, > billed yearly. Dated 2026-11-15; facts checked against the product code on > 2026-11-14. The referral portal is in https://minipacs.net/vendo/llms.txt. ## Pages - [MiniPACS product page](https://minipacs.net/minipacs/): what it is, who it fits, screenshots. - [Features](https://minipacs.net/features/): the full feature list of both products. - [Security and HIPAA posture](https://minipacs.net/security/): access control, audit, encryption, sign-in methods. - [Pricing](https://minipacs.net/pricing/): flat per-location prices, setup, license terms. - [Live demo](https://minipacs.net/?demo=minipacs): the real app on synthetic data. - [API and developer docs](https://minipacs.net/developers/): the order-system API and DICOM services. ## What MiniPACS does, in full - Live worklist, push not polling: a new study appears on every open worklist over WebSocket the moment it is complete (typically within about a minute of the last image landing), with zero manual refresh and no polling load; bursts such as CT floods are coalesced. - Enterprise-grade audit and access control at a small-practice price: a tamper-evident, hash-chained audit log a database trigger will not let anyone edit, a self-service HIPAA Accounting of Disclosures report, and role-based access control across 23 permissions and 4 roles (admin, doctor, technician, viewer) that the admin edits live and the server enforces on every endpoint. - A DICOM hub: every arrival logged (device, AE title, IP, first and last image, series, where it went), routing rules by sender, calling or called AE title, IP, site, modality or any DICOM tag with a dry run that shows which rules match a study and why, a delivery queue that retries for 24 hours (1, 2, 5, 10, 30 minutes, then hourly), destinations with a step-by-step test and a Send test image button, and Query/Retrieve (C-FIND, C-MOVE, C-GET) accepted only from each caller's registered IP and limited to part of the archive if needed. - A DICOM Modality Worklist (C-FIND) fed by Vendo: the scanner pulls today's and tomorrow's patients, the technologist picks the patient on the scanner and types nothing, and the study links to its referral by the accession (visit) number. Each scanner needs its worklist option set up once. - Optional staff single sign-on (OIDC: Microsoft Entra ID, Okta, Keycloak, Authentik or any OIDC provider) in both products, with a setup wizard and a recovery account: the identity provider enforces MFA. Local logins with a password policy remain. - Reporting and workflow: 13 editable starter templates (CT, MR, US, XR), dot-phrase macros, browser voice dictation with commands, a normal-study fill, copy from prior report, draft to final to signed with addenda, saved as DICOM Encapsulated PDF; critical-results e-mail to the referrer without PHI with an acknowledgement link; study status from Received to Sent to Report ready to Delivered with an overdue flag; documents (referral, history, priors) travel inside the study; prior comparison; Stone, OHIF and VolView viewers plus one-click desktop viewers. - Backups set up in the browser with a wizard: AES-256 encrypted (restic), the database every 3 hours and images hourly, to a NAS and/or S3 bucket, with storage passwords encrypted in the browser so the app never sees them, one recovery password and a printable recovery map, restore from the browser with a 14-day undo, and a weekly automatic restore drill into an isolated sandbox. A health page gives one verdict with e-mail alerts. - Free in-browser DICOM viewer at https://minipacs.net/free-dicom-viewer/: drag in .dcm files, a whole patient-CD folder or a ZIP archive and they are parsed and rendered locally in the browser, grouped by series; nothing is uploaded, no account needed. The full diagnostic workflow lives in the MiniPACS product viewer. ## Key unique features and how they work - Accounting of Disclosures: a self-service, per-patient HIPAA Section 164.528 access report with CSV export. One page pulls every access to a patient's data (study, series and share-link level) in a single request and classifies each row as clinic staff or an external guest, so an administrator can answer "who looked at my chart" with one export instead of combing the general audit log by hand. - Append-only audit log enforced by the database itself: a Postgres trigger blocks UPDATE and DELETE on the audit_log table outright. Deleting old rows is possible only through a controlled retention path that first demands a fresh SHA-256 export of exactly the range being purged, and refuses the purge on any mismatch. Even a leaked database password cannot quietly rewrite history. - Hash-chain integrity, verifiable from the UI: every audit row is chained by hash to the row before it, and a "Verify integrity" button recomputes the whole chain on demand, returning either "Chain intact" with a row count, or the exact point of a break. - Self-healing after a mid-operation crash, three independent mechanisms: an interrupted bulk import resumes from the missing chunk by SHA-256 dedup, a C-STORE transfer left pending by a deploy is re-attached and watched to completion, and a gateway agent recovers any file stuck mid-receive or mid-upload after a power loss at the branch. No image is lost or duplicated in any of the three cases. - Backend has no access to Docker or the host: backup and restore-drill jobs are only ever rows in a queue; a separate host-side process is the only thing that can execute them. A fully compromised web container still cannot stop backups, wipe volumes or touch the host Docker daemon. - Full self-service gateway agent lifecycle: a branch clinic with no static IP gets a one-time key, a ready-to-run install command, and a live online/offline, queue-depth and free-disk status, enrolled in about two minutes with no developer involved. ## Under the hood Self-hosted stack: Orthanc as the DICOM engine (C-STORE/C-ECHO, DICOMweb), PostgreSQL holding the index while image blobs stay on disk, Redis for cache, a Python/FastAPI backend and a React frontend, all on Docker with no inbound web ports (only the DICOM port is open). The live worklist runs over WebSocket, pushed the moment a study is complete, not polling. Viewer metadata is served from the database with no disk reads on open, lossless JPEG 2000 transcoding cuts pixel traffic by about 63%, and LAN users go straight to the server over HTTPS. The Stone Web Viewer opens a typical study in about 0.6 seconds in local testing, roughly 50 times faster than the product's earlier OHIF-based viewer bundle, and is the default viewer; OHIF (MPR and advanced workflows) and VolView (3D volume rendering) are alternatives, all self-hosted. The audit-log hash chain is signed with an HMAC key derived independently of the login signing key (HKDF). Backup, restore and every host-level operation run through a separate host-side process the backend cannot reach directly, so a compromised web container cannot touch them. MiniPACS is the image archive: any DICOM modality sends studies straight to it, they appear on the live worklist, and they open in any browser with nothing installed. The report editor has templates by modality, macros, browser voice dictation, and a draft to signed lifecycle with addenda; the signed report is saved as DICOM Encapsulated PDF inside the study, so findings travel with the images. A live US clinic reads MRIs on this exact stack every day; its archive holds millions of images on one box. An order system (Vendo, or a RIS) links to MiniPACS through the order-system REST API under /api/integration/v1/ with a bearer key the administrator issues; the order system makes every call and MiniPACS never calls out. Details: https://minipacs.net/developers/#order-system-api ## Why clinics switch: legacy cloud PACS vs MiniPACS Every row is stated on the landing page and verifiable in the live demo. | Question | Legacy cloud PACS, rented | MiniPACS, on your server | | --- | --- | --- | | What you pay | $150 to $2,000 a month, forever | One flat yearly license: $3,600 to $7,680 | | Where your data lives | In the vendor's data center | On your own computer | | New scans appear | Manual refresh, 30 to 60 second lag | Automatic push the moment a study is complete, no refresh | | Scan viewer | A plugin or a paid add-on | Three zero-install viewers plus one-click desktop viewers | | Importing old scans | Start over if it fails | Resumes where it stopped, skips duplicates (5,000+ CDs done) | | The internet goes down | Reading stops with it | Keeps running on your LAN | | You stop paying | Locked out of your archive | Read-only: view and export, always | | You decide to leave | Their export queue, their timeline | One command exports everything | | Who answers support | A ticket queue | Your one dedicated person | | Open to the internet | Yes | No inbound web ports: tunnel out only; only the DICOM port is open | | The maker shuts down | The service dies with them | Your archive outlives us | | Backups | The vendor's, you cannot see them | Yours: encrypted, every 3 hours, to NAS and/or S3, restore-tested weekly | Five-year math at a typical $700/month cloud PACS bill: $42,000 of rent vs $38,400 for the combo license. Above roughly $642/month, renting costs more.