What to Consider Before Choosing a New PACS

A step-by-step guide to choosing a new PACS system: requirements, integration, true cost, cloud fit, vendor questions, and a pre-decision checklist.

By Trisha Seal — October 5, 2026. Trisha writes about PACS support models, migrations, and vendor evaluation drawn from RAD365's vendor-agnostic PACS Support work for hospitals, imaging centers, and Critical Access Hospitals. RAD365 does not read or interpret studies.

Choosing a new PACS system is not a single IT purchase. It is a commitment that shapes how images move, how clinicians work, and what your organization spends for years. Most hospitals live with a PACS decision long after the contract is signed, so the questions you ask now matter more than the demo you see.

The stakes are rising. Coherent Market Insights estimates the global PACS market at USD 4.75 billion in 2026 and projects it to reach USD 7.03 billion by 2033, a 5.8% compound annual growth rate. More vendors and more options make careful evaluation more important, not less. This guide walks through the decision in the order most teams should follow it.

Start With Your Own Requirements, Not the Vendor List

Before you look at any vendor, write down what your organization actually needs. List the modalities you run today and plan to add, the study volume you expect over the next five years, and every site that will share images. Include specialties beyond radiology. Telemis recommends checking whether a PACS can serve pathology, cardiology, dermatology, and the operating room, because separate image silos create cost and confusion later.

Next, describe your growth plan. Pixeon stresses real scalability as a core criterion: a system should handle rising volume and new sites without a forklift upgrade. If an acquisition or new imaging center is likely, say so now and test every vendor against it.

Then Weigh Integration and Openness

A PACS lives inside a larger system. It needs clean connections to your RIS, your EHR, and directory services such as LDAP or Active Directory so orders, patient data, and user access stay consistent. Ask each vendor to show live integrations, not slides.

Openness matters just as much. Telemis advises choosing a PACS that works with third-party AI tools rather than tying you to one vendor's catalog. Proprietary formats and closed integrations are how lock-in starts; our guide to PACS vendor lock-in warning signs explains what to watch for. Ask about standards-based storage, data export rights, and whether a vendor-neutral archive is supported.

Viewer performance belongs here too. A diagnostic-grade viewer should open large studies without lag, and secure image sharing should work across sites and for teleconsultation. Test both with your own data during the evaluation.

Calculate True Cost Over Several Years

The quote is only the beginning. Pixeon recommends looking at total cost of ownership, including hardware, add-on modules, and updates. Telemis warns about per-user licensing that grows quietly as departments add staff. Ask every vendor to itemize storage expansion, interface fees, upgrade costs, and support charges, then model those costs at your projected volume and site count. Our breakdown of the real price of PACS support covers the ongoing side of that equation.

Where possible, push for transparent, flat, site-wide licensing. It makes budgeting predictable and removes the penalty for giving more clinicians access.

Decide on Cloud or On-Premise Fit, Briefly

Pixeon lists cloud versus on-premise flexibility as a key criterion, and the right answer depends on your network, security requirements, and IT staffing. We cover the operational differences in detail in Cloud PACS vs. On-Premise PACS, so here the key point is simple: decide which model fits how your team actually operates before you compare vendors, not after.

Compare Vendors Side by Side

What to evaluate	Questions to ask the vendor
Clinical scope	Which specialties beyond radiology do you support today, in production?
Integration	Can you show live RIS, EHR, and LDAP/Active Directory integrations at a similar site?
Openness	Can we use third-party AI tools and export all data in standard formats?
Licensing	Do you offer flat, site-wide licensing, and what triggers extra fees?
Scalability	What does the contract cost if our volume and sites double?
Viewer performance	Can we test large studies on our own network before signing?
Support	What are your written response times, and can we speak with references?

Before You Sign: A Short Checklist

Written requirements covering modalities, specialties, sites, and five-year growth
Demonstrated integrations with your RIS, EHR, and directory services
Contractual rights to your data in standard formats
An itemized multi-year total cost of ownership
A migration plan for prior studies, with parallel access during cutover
A clear answer on who supports the system after go-live

A PACS Decision Is Also a Support Decision

The new system will need hands-on support during migration and every day after. Pixeon recommends weighing vendor longevity and regional support strength, and that applies to whoever keeps the PACS running. Some organizations rely on the vendor, some on internal staff, and some on a vendor-agnostic partner. If a migration is on your roadmap, RAD365's PACS migration services are one option to plan alongside the vendor decision.

RAD365 is an operations and workflow partner providing PACS Support and the Radiology Workflow Manager only. It does not read or interpret studies, and it does not provide preliminary reads, dictation, or reporting.

Frequently Asked Questions

PACS Basics & Cost

What is a PACS system and why does the choice matter long-term?

A PACS (picture archiving and communication system) stores, retrieves, displays, and shares medical images across a hospital or imaging network. Most organizations keep a PACS for many years, and it connects to the RIS, EHR, modalities, and archive, so the choice shapes workflow, cost, and future flexibility long after go-live.

How much does a new PACS system typically cost?

Cost varies widely with study volume, number of sites, licensing model, deployment type, and the modules included. Rather than comparing sticker prices, compare total cost of ownership over several years, including hardware, storage growth, add-on modules, integration work, upgrades, and support.

What components are required for a complete PACS system?

A complete PACS typically includes image acquisition from modalities, a database and workflow engine, short- and long-term storage or an archive, diagnostic and clinical viewers, integration interfaces to the RIS and EHR, security and user management, and backup and disaster recovery.

How long does a typical PACS replacement project take from decision to go-live?

Timelines depend on scope, data volume, integrations, and the number of sites. Many projects run for months, covering contracting, interface builds, data migration, testing, training, and a staged cutover. Planning migration and parallel support early reduces the risk of delays.

Evaluating Vendors and Technical Fit

What is a vendor-neutral archive, and why does it matter when choosing a PACS?

A vendor-neutral archive (VNA) stores images in standard formats that any compliant system can read, separate from a single vendor's viewer or workflow. It matters because it makes a future PACS change far easier and keeps image data accessible across departments and systems.

Should a new PACS integrate directly with the hospital's EHR/HIS?

Yes. Direct integration with the EHR or HIS, along with the RIS and directory services such as LDAP or Active Directory, keeps orders, patient data, and user access consistent and avoids manual reentry between systems.

Does PACS vendor market share matter, or is it a weak signal on its own?

Market share shows that a vendor is established, but it says little about how well its product fits your workflow, integrations, or budget. Treat it as one input alongside references, support track record, roadmap, and openness to standards.

Should a new PACS support specialties beyond radiology, like cardiology or pathology?

If your organization images in cardiology, pathology, dermatology, or the operating room, a PACS that can handle those specialties avoids separate silos. Telemis recommends evaluating clinical scope beyond radiology as part of selection.

How important is cloud flexibility when selecting a new PACS today?

Cloud options can change how infrastructure, scaling, and disaster recovery are handled, while on-premise keeps more direct control. Pixeon lists cloud versus on-premise flexibility as a core criterion; the right fit depends on your network, security requirements, and IT staffing.

True Cost and Scalability

What hidden costs tend to show up after a PACS purchase?

Common surprises include per-user or per-module fees, storage expansion, interface charges, upgrade costs, hardware refreshes, data migration, and ongoing support. Ask vendors to itemize these in writing before signing.

How does PACS pricing typically scale with study volume or added sites?

Many contracts price by study volume, by site, by user, or by a combination. Model your expected growth in studies and locations over several years and ask each vendor to show what the contract costs at those future levels.

Can hospitals negotiate flat, site-wide licensing instead of per-user PACS fees?

Often, yes. Telemis highlights transparent, flat licensing as a selection criterion to avoid per-user cost surprises. Raise licensing structure early in negotiations, before the final quote is set.

How big is the PACS market, and what does that growth mean for buyers?

Coherent Market Insights estimates the global PACS market at USD 4.75 billion in 2026, projected to reach USD 7.03 billion by 2033 at a 5.8% CAGR. A growing market means more options and competition, but also more need to compare offerings carefully.

Migration, Support, and Long-Term Fit

What should a hospital check about a PACS vendor's support track record before signing?

Ask for references from similar organizations, written response times by severity, regional support coverage, upgrade history, and how the vendor handles escalations. Pixeon recommends weighing vendor longevity and regional support strength.

How does PACS vendor lock-in happen, and how can it be avoided during selection?

Lock-in happens through proprietary image formats, closed integrations, restrictive data export terms, and bundled AI or viewer tools. Avoid it by requiring standards-based storage, contractual data access, and openness to third-party AI and viewers.

What happens to workflow continuity and patient data during a PACS switch?

A well-planned switch migrates prior studies, validates data integrity, keeps interfaces running, and often runs old and new systems in parallel during cutover so clinicians can still access history while the new system goes live.

Who manages the PACS system day-to-day after it's purchased and installed?

Day-to-day management usually falls to a PACS administrator or hospital IT team, sometimes supported by the vendor or a managed PACS support partner that handles monitoring, tickets, user access, and interface issues.

Does choosing a new PACS also mean choosing a new PACS support partner?

Not necessarily, but it is the right moment to decide. The new system needs support during migration and after go-live, so evaluate whether vendor support, internal staff, or a vendor-agnostic support partner best fits your environment.