What a small imaging center actually needs
A hospital buys a PACS as one module in an enterprise imaging program. A small center (one to three locations, MRI, CT, X-ray or ultrasound, often no in-house IT) buys it to get through the day. That changes the checklist: fewer integrations, more of the work done without help.
- Every scanner sends to it. DICOM C-STORE from any modality and vendor, with a connection test per device, and a scanner worklist so nobody retypes the patient at the console.
- A browser viewer, nothing installed. Radiologists read from any workstation or from home; referring doctors open a link.
- A live study list. New studies appear on their own, with status from received to reported to delivered and a flag on anything overdue.
- Reporting built in. Templates, macros, dictation, signing and addenda, with the signed report kept inside the study so it travels with every send and disc.
- Routing to outside readers. Rules that send each study where it belongs, retry when a reader is offline, and show why a send failed.
- Sharing that replaces most CDs. Patient links with a PIN and an expiry, plus a disc that opens on any computer when a CD is still demanded.
- Backups you can prove. Encrypted copies off the server and a restore that is tested, not assumed.
- HIPAA technical safeguards. Unique logins, automatic logoff, encryption, an audit log nobody can rewrite, and a report of who opened a patient's records.
- A price that does not grow with volume. A center that adds a scanner should not get a bigger bill for the same software.
The three ways to buy a PACS for a small center
Every option on the market is one of three shapes. The software inside them varies, but the shape decides who holds the archive, what happens when the internet drops, and how the bill moves.
| Cloud PACS subscription | Self-hosted PACS (MiniPACS) | |
|---|---|---|
| Where the archive lives | On the vendor's servers | On a server the center controls: on site or in its own cloud account |
| Price shape | Monthly fee, often per study or per gigabyte | $300 per location per month, flat, unlimited studies |
| Internet goes down | Reading stops | Reading continues on the local network |
| Leaving | The vendor's export, on the vendor's schedule | The archive is already yours; free full export in standard DICOM |
| Who runs the server | The vendor | Installed and updated remotely for the center; the center owns the box |
The third shape, a mini PACS appliance, is a small server with archive and viewer software sold as one box. It shares the self-hosted advantages but often ties the center to that vendor's hardware and a desktop viewer. The mini PACS guide compares the servers, and cloud PACS vs onsite runs the five-year math.
See the whole day in the MiniPACS live demo: a study arriving, the browser viewer, a signed report and a patient link, on synthetic data. No sales call before the link.
What a PACS should cost a small center
Small-center cloud PACS plans usually land between about $150 and $2,000 a month, and the cheaper ones charge per study. The per-study shape looks small at first and grows with every scanner the center adds. A flat fee does the opposite: it costs the same in a slow month and a busy one.
- Per-study math. At $2 a study, 150 studies a month is $300, the same as MiniPACS. At 600 studies a month the per-study bill is $1,200; the flat fee is still $300.
- Honest exception. Under about 100 studies a month, a per-study plan can genuinely be cheaper. The cost calculator shows the break-even with your own numbers.
- One-time work. MiniPACS setup and migration start at $1,500, scoped to the old archive. The yearly license includes every update, security patches installed for you, and support from one dedicated engineer.
- If payment ever lapses. MiniPACS goes read-only: viewing, export and sharing keep working, and the center is never locked out of its own images.
For a wider view of the market, the PACS cost guide breaks prices down by deployment and the pricing index lists every published vendor price with its date.
Questions to ask every PACS vendor
- Is the price on your website? If it is "contact us", ask for the per-study, per-seat and per-gigabyte lines in writing.
- Who holds the archive, and what does leaving cost? Ask for the export format and how long a full export takes.
- What happens when our internet drops? Ask whether radiologists on site can still read.
- Can we see it without a sales call? A live demo on synthetic data answers more than a slide deck.
- How are backups tested? A backup that has never been restored is a hope, not a backup.
- Who answers the phone when a scanner stops sending? Ask for a named person and a response time.
- What do you not do? A vendor that names its limits (for MiniPACS: no HL7, no automatic failover, no vendor-hosted cloud) is easier to plan around.
Switching from an old PACS
- 1Plan: one 15-minute callPick the server (one the center already has, a mini PC, or a Linux VM in its own cloud account) and a date for the switch.
- 2Install: remote, no open portsMiniPACS is installed over a secure tunnel. No port is opened on the clinic router; the scanners reach the DICOM port on the local network.
- 3Migrate: the old archive moves in bulkOver DICOM from the old PACS, or from discs, ISOs, folders and ZIPs. An interrupted import resumes where it stopped and skips duplicates.
- 4Go live: scanners and readers pointed at the new addressModalities, report templates and referring offices are set up. The old PACS can keep running side by side until the last study has moved.
Where MiniPACS fits, and where it does not
MiniPACS fits independent imaging centers, mobile X-ray operators, ambulatory surgery centers, and dental and veterinary practices that want to own their archive at a flat price. It is in production at a working US clinic that reads MRIs on it every day, and it carries more than 2,700 automated tests that run on every change. With Vendo beside it, referring doctors send orders and book open slots online, the scanner pulls the patient from a worklist, and the signed report is filed back on the referral, for $640 per location per month for the pair.
It is not the fit for a hospital that needs an HL7 interface to its RIS or EHR, for a center that wants the vendor to host everything, or for a site that requires automatic failover to a second server. MiniPACS is built, sold and supported by one engineer; who makes MiniPACS is stated plainly, and every price is on the pricing page.
FAQ
What is the best PACS for a small imaging center?
The best PACS for a small imaging center is the one that covers the whole day (store, view, report, route to readers, share with patients and referrers, back up) at a price that does not grow with volume, and that lets the center keep its archive if it ever leaves. For a one-to-three location center without a full-time PACS administrator, that usually means a browser-based system with flat pricing. MiniPACS is built for exactly that buyer: self-hosted on one server the center controls, $300 per location per month flat, no per-study fees. Centers that need an HL7 interface to a hospital RIS or EHR should pick an enterprise system instead.
How much does a PACS cost for a small imaging center?
Cloud PACS subscriptions for small centers usually run from about $150 to $2,000 a month, and many charge per study, so the bill rises with volume. MiniPACS is $300 per location per month flat, billed yearly ($3,600 a year), with unlimited machines, staff and studies, plus a one-time setup and migration fee from $1,500. At $2 a study, a per-study plan costs the same $300 at 150 studies a month and more above that; under about 100 studies a month a per-study plan can be cheaper.
Is a cloud PACS or a self-hosted PACS better for a small center?
A cloud PACS means nothing to install and the vendor runs the servers, but the vendor holds the archive, reading depends on the internet line, and the bill usually grows with study volume. A self-hosted PACS keeps the archive on a server the center controls, keeps working on the local network when the internet drops, and costs the same every month, but someone has to own the server and its backups. MiniPACS takes the self-hosted route and handles the hard parts for the center: remote installation, updates that roll back on failure, encrypted backups with a weekly automatic restore drill.
Does a small imaging center need a RIS as well as a PACS?
Not always. A RIS traditionally handles orders, scheduling and billing; the PACS stores and shows the images. Many small centers only need the order and scheduling half, done online with the referring offices, plus a PACS. MiniPACS with the Vendo referral portal covers referrals, booking, the scanner worklist, images and the signed report. Neither product does billing or claims, and neither has an HL7 interface.
What hardware does a small imaging center need for a PACS?
For MiniPACS, one server: a Windows or Linux machine the center already has, a mini PC from an electronics store placed behind the front desk, or a Linux virtual machine in the center's own cloud account. Storage is sized to the archive. Staff need only a browser; nothing is installed on reading workstations.
Can a small center switch PACS without losing its archive?
Yes, if the new system can take the old archive in bulk. MiniPACS migrates from the old PACS over DICOM (push or query/retrieve) and from discs, ISOs, folders and ZIPs with a resumable importer that skips duplicates; more than 5,000 CDs and 14,000 studies have already gone through it. The old PACS can keep running side by side until the move is finished.
