A VNA (Vendor Neutral Archive) is the enterprise library for medical images: one store, standard formats, no single vendor holding the keys. It exists because departmental PACS systems lock studies into a proprietary garden. That lock-in is the problem. Neutrality is the product.
If you meant PACS the workbench — store, retrieve, hang a study — that is PACS and DICOM. If you meant DICOM the language (file / protocol) — that is what is DICOM. This page is the archive that outlives either.
Vendor lock-in, in one corridor
A radiology PACS from vendor A and a cardiology PACS from vendor B do not share a patient. Swap A’s viewer and you buy a migration, because the pixels and the private tags live inside A’s database. The data is yours on paper and theirs in practice.
A VNA takes those studies in, strips or maps the private junk, and files them as standard DICOM (and, where needed, other objects) behind a standard interface. You can change the workbench without moving the library. That is data ownership, not a bigger SAN.
- Buy the best departmental viewer without a second migration.
- Give IT one archive to run, not twelve.
- Give a clinician one longitudinal record — every “-ology,” one patient.
The VNA is a statement of who owns the history. The last scanner vendor is not the answer.
Workbench vs library
A PACS is the specialist’s workbench: today’s list, hanging protocols, report in the next ten minutes. A VNA is the master library: every department, every year, a format that will still open when the workbench brand changes. They partner. The VNA does not replace the PACS any more than a university library replaces a lab bench.
| Attribute | Traditional PACS | VNA |
|---|---|---|
| Primary goal | Departmental speed — read, report, hang | Enterprise consolidation and lifecycle |
| Data control | Vendor-shaped; private tags are normal | Vendor-independent; standard objects you own |
| Scope | One “-ology” | The enterprise — every department, every site |
| Interoperability | Inside one vendor’s garden | Any standards-compliant viewer or PACS |
| Migration | Paid again when the PACS brand changes | Storage is already decoupled; the viewer unplugs |
| Scale | Grows inside the department | Built for decades and petabytes |
| Horizon | Today’s diagnostic list | The record you still have in fifteen years |
The workbench is for now. The library is for forever. Separating them is the point: a faster PACS does not have to also be your legal archive, and your legal archive does not have to hang a trauma series.
Three parts under the hood
- Ingestion. Accepts studies from any PACS or modality. Tag morphing replaces private metadata with a house standard so the next viewer can find the patient. This is where lock-in dies.
- Storage. Object store, tiered: hot for this week’s CT, warm for last quarter, cold for the legal keep. Lifecycle rules (retain, purge, legal hold) sit here, not in each departmental PACS.
- Interoperability. DICOM and HL7 (and DICOMweb) so an EHR, a new PACS, or a web viewer can query the same patient without a one-off interface.
That split — library underneath, workbench on top — is why you can upgrade radiology’s PACS and leave cardiology’s history where it is. The new PACS plugs in. The old studies never move.
Where it earns the rack
A merger. The acquired clinic’s PACS is an island. Point ingestion at it; the VNA standardizes and files. The six-month migration becomes a connection. A patient from the clinic shows last year’s clinic CT next to this week’s hospital MR. Incomplete history is a clinical risk, not an IT inconvenience.
A research / AI set. One query (“adult brain MR, ten years”), de-identify on the way out, consistent DICOM. Without a VNA that is a tour of departmental silos and a summer of cleaning. The VNA is the lake; the model is a subscriber.
Telehealth. A specialist two cities away needs the history, not a PDF of the last report. A web viewer on the VNA is the whole record, not a file on a bounce box.
FAQ
Do I rip out the PACS?
Usually no. Keep the workbench for the daily list. Let the VNA be the system of record. Two platforms, two jobs. The expensive mistake is buying a second archive because the first one is branded.
Is this the same as “cloud PACS”?
No. Cloud is where the disks live. Neutrality is whether you can leave the vendor. You can have a locked-in cloud PACS and a VNA in your own room. Do not confuse the two RFPs.
What about imaging software to buy?
A VNA is one box on that stack (archive), not the buyer’s catalogue. That list is medical imaging software.
PYCAD builds the imaging side of this when the archive has to live in a clinic app. Case studies.