Vendor Neutral Archive Software: the Best VNA for Multi-Site Radiology Groups
A vendor neutral archive earns its cost when you already run more than one archive, which is what usually happens to a group that grows by acquisition. The number that decides the project is not the license but the migration, priced per study rather than per terabyte. What the federal contract record shows, and the four things multi-site buyers should check that single-site buyers never do.
By the Radiological.ai team
August 2026 · 8 min read
Worklist
Structured report
DraftRun the assistant to draft this report for review.
Illustrative sample · not a real patient study, not a diagnosis
Decision support for qualified clinicians. Radiological.ai does not provide a diagnosis and is not a substitute for professional judgment.
The short answer: a multi-site radiology group needs a vendor neutral archive when it runs more than one PACS, expects to change PACS, or reads for facilities it does not own. A single-site practice on one PACS usually does not, and gets most of the benefit by negotiating bulk DICOM export into the PACS contract instead. When you do buy one, the number that decides the project is not the license. It is migration, which is priced per study rather than per terabyte, and it is the reason archives outlive the systems that created them.
The vendor neutral archive was invented to solve a specific, expensive problem: every PACS replacement dragged a full image migration behind it. Store the studies in a neutral format once, the argument goes, and the next PACS change becomes a software project rather than a data project. That argument is sound. It is also frequently sold to organizations whose actual problem is something else.
For a group running several sites, the question sharpens in a useful way, because multi-site operations expose which problem you really have within about a year.
Do multi-site radiology groups need a vendor neutral archive?
Often yes, but for a different reason than the one in the brochure. The standard pitch is about avoiding lock-in at some future replacement. The reason multi-site groups actually end up buying is that they already have more than one archive, usually without having decided to.
It happens like this. You acquire a practice that runs a different PACS. You start reading for a hospital that sends studies but keeps its own archive. You open a site that came with an imaging system nobody wants to rip out in year one. Now priors live in three places, the comparison study a radiologist needs is on a system they do not have a seat on, and somebody is manually pushing DICOM between them. That is a consolidation problem, and it is the problem a VNA is genuinely good at.
The signals that you have it, rather than a hypothetical future version of it:
- Radiologists routinely ask someone to fetch a prior from another system
- You run two or more PACS instances and have no plan to get to one
- You read for facilities that will not give you access to their archive
- A payer, health system partner or state requirement obliges you to retain studies independently of any vendor
- Your last PACS migration ran long, and the memory of it is shaping the next contract
If none of those are true and you read from one PACS at one or two sites, a separate archive is more architecture than the problem needs. Spend the effort on export terms instead.
What is the difference between a VNA and a PACS?
PACS stores and displays images for the radiologists who read them, with the reading tools attached. A vendor neutral archive stores the same images in a standard, long-term format that is not tied to the PACS that produced them, so the archive survives a PACS change. PACS is a clinical workflow product; a VNA is infrastructure. Most groups that have both run the PACS on top of the archive rather than beside it.
They are two layers of the same stack, and there is a third, the universal viewer, that shows studies to clinicians outside radiology. Which layer you are replacing changes the shortlist completely, and the independent rankings are segmented that way on purpose. The enterprise imaging and vendor neutral archive software comparison works through all three layers, who ranks first in each, and what the federal contract record shows for each. If the reading platform itself is what is failing, that is PACS software compared by study volume instead.
How much does a vendor neutral archive cost?
No vendor in this category publishes list pricing, so the public contract record is the most honest anchor available. Searching prime federal awards on USAspending.gov for the exact term "vendor neutral archive", award type codes A through D, covering award start dates from October 1 2016 through August 24 2026, returns 7 awards totaling $1,109,975, with a median of $89,347 and a 75th percentile of $186,639. The same method on "enterprise imaging" returns 4 awards totaling $1,501,526 with a median of $427,074, and on "picture archiving and communication" returns 48 awards totaling $68,836,793 with a median of $250,438.
Read those three numbers together rather than separately. The archive is consistently the smaller line item, roughly a third of the median full platform procurement, because it sits underneath the thing that costs more. The compile date is August 24 2026 and every figure is reproducible against the same public API. Per-award statistics drift a little between pulls while the totals stay stable, which is why the date matters.
Migration is the number that is missing from all of that, and it is usually the one that decides whether the project happens. It scales with study count, not with storage size, which surprises people who budgeted from a terabyte figure. Commonly quoted industry rates run about $0.05 to $0.50 per study, with the top of that range reflecting proprietary source formats that have to be decoded before they can be written out neutrally. An 18,000-study archive therefore lands somewhere near $900 to $9,000. Decades of accumulated imaging across several acquired practices runs well past $40,000. Get the rate per study in writing, and get it before you sign the archive contract rather than after.
What to ask for, in this order:
| What to ask for | Why it decides the real cost |
|---|---|
| The migration rate per study, and who pays if the source format is proprietary | This is the largest single line in most VNA projects and the one most often quoted as "to be scoped" |
| How storage is billed as studies age out of active reading | The archive keeps growing after a study stops being read, so an operating line sized for today grows on its own |
| The uplift cap on renewal, in writing | An uncapped annual increase on a line that grows with volume compounds twice |
| Cost per additional site and per sending facility | This is the number that scales for a multi-site group and it is rarely in the headline quote |
| What a migration out to a competitor would cost, quoted now | If they will not quote it, the archive is not as neutral as the category name suggests |
That last row is the one people skip and later regret. Because an archive is billed as a growing operating line rather than a one-time purchase, it behaves much more like cloud infrastructure than like a software license, and it benefits from the same discipline: someone should be watching the monthly trend rather than reading the invoice once a year. Groups that already track their cloud and SaaS spend continuously tend to catch archive growth while it is still a conversation rather than a budget problem. The wider mechanics of renewal uplift are covered in the contract terms worth negotiating, and radiology software pricing by category works through the full federal dataset.
Who are the main vendor neutral archive vendors?
The names that recur across independent rankings and the federal contract record include Agfa HealthCare, Sectra, Fujifilm, Philips, Merative, Intelerad, Hyland and Carestream. In the 2026 Best in KLAS awards announced on February 4, 2026, Agfa HealthCare ranked first in the Vendor Neutral Archive (VNA) category at 89.8 percent, its second consecutive win there, and first in Universal Viewer (Imaging) with its XERO Viewer at 92.1 percent, a third consecutive win.
One detail from the contract data is worth carrying into the first call: the largest recipients of federal awards naming a vendor neutral archive are frequently integrators rather than the archive vendors themselves. Thundercat Technology leads at $509,222, ahead of Alvarez LLC at $331,437 and Aycan Medical Systems at $269,316. If a reseller ends up on the paper, that changes who holds discount authority, who owns the renewal clause and who you escalate to when an interface breaks at two in the morning. Ask early who the counterparty will actually be.
What multi-site groups should check that single-site buyers do not
Four things, and none of them appear in a standard demo.
Whether priors surface automatically across sites. This is the whole point for a distributed group and it is the thing most likely to be technically true and operationally useless. Ask to watch a radiologist at site A open a study whose prior was acquired at site C, on a normal connection, without anyone preparing anything in advance.
How a new site or sending facility is onboarded. Ask for the elapsed time and the interface work involved, then ask for a reference customer who has done it in the last year. Groups grow by acquisition, and an archive that makes each addition a project will quietly cap how fast you can grow.
Whether the archive is neutral in the direction that matters. If the VNA comes from the same vendor as your PACS, it is convenient, cheaper to integrate and often the right call at smaller scale. It also hands back the one property you were paying for. That can be a good trade. It should be a knowing one, which means getting the competitor migration quote described above.
What happens to retention obligations across state lines. Multi-site groups frequently operate under more than one state's retention rules, and the archive is where that obligation lands. Confirm that retention can be set per facility rather than as one global policy, because a single longest-common-denominator setting is an expensive way to comply.
The decision, in one line
Buy a vendor neutral archive when you already have more than one archive or a firm reason you will, not because a future migration might be painful. Price the migration per study before anything else, cap the renewal uplift, and make the neutrality real by getting the exit quote in writing while you still have leverage. Once the images are handled, the next bottleneck is almost always the report rather than the archive, which is where structured radiology reporting and an assistant that drafts into your template start to matter. Radiological.ai works alongside whatever archive and PACS you land on: it reads the study, flags suspected findings for a second look, prioritizes the worklist and drafts the report for review, and the responsible radiologist reviews, edits and signs every study.
See Radiological.ai read a study
The assistant flags suspected findings for review, prioritizes the worklist so urgent studies surface first, and drafts the structured report into your template. You review, edit and sign every study.