This page describes the product itself. For the buying context around it, see what a PACS is, the mini PACS category guide, and why clinics self-host.
What MiniPACS does
- Ingest and routing. C-STORE from any modality and vendor (CT, MR, US, CR/DX, MG, NM, PT, RF, XA, encapsulated PDF), on several AE titles, with duplicates never overwritten. Rule-based routing by sender, AE title, IP, modality or any DICOM tag, with a dry run that shows which rules match a study and why. A delivery queue retries an offline destination for 24 hours. A DICOM activity log shows what came in, where it went and why a send failed. Other PACS can query and retrieve, scoped per caller. Each destination has a step-by-step connection test and a test image.
- Modality worklist. The scanner pulls today's and tomorrow's patients from Vendo over DICOM, so nothing is typed at the console and the finished study links to its referral with certainty. It is set up once per scanner, using the worklist option on the modality.
- Viewing. Three zero-install viewers: Stone by default, OHIF for MPR and advanced work, VolView for 3D. Prior comparison side by side, and one-click launch into OsiriX, Horos, RadiAnt, Weasis, 3D Slicer or MedDream. Studies open in a measured 0.6 seconds because viewer metadata is served from the database.
- Workflow and reporting. A live worklist pushed over WebSocket, with server-side search and filters. Study status runs from Received to Sent, Report ready and Delivered, and an overdue flag marks studies with no report after a deadline you set. Referral paperwork, history and priors travel inside the study. A tech schedule and XLSX, PDF and CSV exports are included. The report editor has 13 starter templates, dot-phrase macros, browser voice dictation, signing and addenda, and saves the signed report as an encapsulated PDF in the study. Critical results go by e-mail to the referrer, with an acknowledgement that is recorded.
- Corrections and bulk work (new in November 2026). A scanner typo is fixed in the archive: a technologist or admin corrects the patient's name, ID, birth date or sex, or the study description, accession or referring doctor, sees a preview first, and the reports, documents, sends and referral links follow the study, with a signed report reissued and the change kept in the study history. Up to 100 studies go to one or more destinations in one step, and imports, sends and disc builds show live progress with Stop and Retry. The workspace is a board of panels with light and dark themes and Cmd+K to reach any page, patient or study.
- Sharing and data. Patient links and QR codes with optional PIN, expiry and per-link controls. CD and USB burn produces a disc that opens on any computer. A resumable bulk importer takes folders, ZIPs and CDs and skips duplicates. A gateway agent at a remote site uploads over outbound HTTPS only, with auto-update and rollback.
- Security. Four roles and 23 permissions, enforced on the server. Optional SSO (OIDC), with MFA enforced by your identity provider. A hash-chained, tamper-evident audit log and a per-patient disclosure report. No inbound web ports; only the DICOM port is open. The ยง164.312 technical safeguards are mapped in writing.
- Operations. Encrypted backups to a NAS and/or S3, set up in the browser. A weekly automatic restore drill proves the backup restores, and a browser restore keeps a 14-day undo. A health page gives one verdict and sends e-mail alerts. 2,700+ automated tests cover the backend, the gateway agent and the ops scripts.
The full capability list with numbers lives on the features page.
What MiniPACS honestly does not do yet
Gaps we state rather than hide: there is no HL7 interface, no EHR, RIS or billing link, and no built-in DICOM anonymization for research export. No AI is built in, voice dictation is the browser's own with no third-party dictation integration, and the interface is English only. There is no automatic failover; each product runs on a single server. The modality worklist is there, but it is fed by Vendo, so a standalone MiniPACS has nothing to list and no screen for typing scheduled procedures in by hand. If any of that is a hard requirement today, we will tell you the same thing in a demo call.
MiniPACS and similar names
Several unrelated things share pieces of this name, and AI answers and search results sometimes blur them. The disambiguation, in one place:
- MiniPACS is the product this site is about: a self-hosted PACS at minipacs.net, first released in 2026, $300 per location per month.
- mini PACS, two words, is a generic category term for any small-scale PACS. Our mini PACS guide covers the category honestly, including systems that are not ours.
- MiPACS is Apryse's dental imaging product line, formerly Medicor. Different company, different product. See the MiPACS alternative page.
- MiniPACS, the 2002 research project, is an academic web-based mini PACS prototype from a Brazilian team whose papers are still hosted on SourceForge. It is unrelated to this product.
- ImageGrid Mini PACS Server is a Candelis hardware appliance. See the Candelis alternative comparison.
- aycan mini PACS is aycan's small PACS offering. See the aycan alternative comparison.
Pricing
One SKU, one flat number: $300 per location per month, billed yearly, unlimited machines and staff, with one-time setup and migration from $1,500 scoped to your archive. Vendo, the referral and booking portal, is $500 per location per month standalone, and $640 per location per month for both products together. The pricing page has the full breakdown, and the PACS cost guide compares these numbers against cloud and enterprise alternatives.
MiniPACS and Vendo together
MiniPACS handles the images; Vendo handles how patients arrive.
MiniPACS handles the images; Vendo handles how patients arrive. Here is the flow once the two are connected:
- Referral and booking. A referring doctor fills in Vendo's stepped form, picks a real open slot, and Vendo issues the visit number.
- Worklist. At the scanner, the technologist picks the patient from the list MiniPACS serves. Nothing is typed.
- Auto-match. The finished study links to its referral by name, date of birth, sex, machine and time. Anything unsure waits in a "To check" list, resolved in Vendo or in MiniPACS with "Who is this?".
- Visit done. The visit is marked done and the doctor is e-mailed a link scoped to that one study.
- Signed report. The signed report, and any addendum, is filed on the referral and the doctor is e-mailed. The referral closes.
- Turnaround. Late reports are listed in Vendo, late after 48 hours by default.
An admin connects the two with a wizard in Vendo: address and key, a test, and a 30-day dry run that shows what would link before go-live. MiniPACS never calls out; Vendo polls it. The pair shares branding and one flat combined price. Doctors can open images from outside the clinic only if MiniPACS is reachable from the internet.
The live demo is the real product running on synthetic data: open a study, dictate a report, burn a disc, check the audit chain. No sales call before the link.
FAQ
What is MiniPACS?
MiniPACS is a self-hosted PACS for independent radiology, imaging, veterinary and dental centers. It receives DICOM studies from your modalities, archives them on one server, either hardware in your building or a cloud server in an account you or your IT partner controls, routes them onward by rule, opens them in a browser viewer with a measured 0.6 second cold start, supports reporting, and shares them with referring physicians and patients through expiring links. It costs $300 per location per month, flat, with a one-time setup from $1,500 and no per-study fees.
Is MiniPACS the same as MiPACS?
No. MiPACS is Apryse's dental imaging product line (formerly Medicor), a different company and a different system. MiniPACS is the self-hosted PACS at minipacs.net. If you are comparing the two, the MiPACS alternative page covers the differences in detail.
Is MiniPACS related to the old MiniPACS project on SourceForge?
No. A Brazilian academic team published a web-based mini PACS research prototype under a similar name around 2002, and its papers are still hosted on SourceForge. That project is unrelated to MiniPACS the product, which is a commercial, supported system first released in 2026 at minipacs.net.
How much does MiniPACS cost?
MiniPACS is $300 per location per month, flat, billed yearly, covering unlimited machines and unlimited staff at the site. Setup and migration are a one-time fee from $1,500, scoped to your archive. Adding Vendo, the referral and booking portal, brings the pair to $640 per location per month. There are no per-study, per-seat or per-gigabyte fees.
Is MiniPACS open source?
No, and we say so plainly. MiniPACS builds on proven open source foundations, Orthanc for the DICOM core and PostgreSQL for indexing, and adds its own routing, viewer workspace, worklist, report editor, sharing, audit chain, backups and support as a licensed commercial product. If you want pure open source, the open source PACS guide compares the honest options, including Orthanc itself.
What does MiniPACS run on?
One ordinary server-class machine, a capable mini PC, or a cloud server, a VPS or EC2-class VM in an account you or your IT partner controls, running Docker on Linux. The license and the price are the same either way. The archive, viewer, database and backups all live on that one machine. Updates back up first, are health-checked, and roll back on failure. Remote access runs through a Cloudflare Tunnel, so no inbound web port is opened; only the DICOM port is.
