MajwareMAJWARE
Free templateEditable7 systems7 interfaces

Vendor Neutral Archive (VNA) Architecture Diagram

A vendor neutral archive (VNA) consolidates images from every department into one standards-based store that the hospital controls. This diagram shows a typical enterprise imaging design: radiology and cardiology PACS forward studies to the VNA, specialty departments upload photos and video through DICOMweb, an enterprise viewer reads from the VNA, the EHR links to images, and a replica sits off-site for disaster recovery.

Open & edit in Diagram Builder →Download SVG

Free, no sign-up. The builder runs in your browser; nothing is uploaded.

Vendor Neutral Archive (VNA) Architecture Diagram: Radiology PACS, Cardiology PACS, Specialty Imaging, VNA, Enterprise Viewer, EHR / EMR, Cloud DR
Vendor Neutral Archive (VNA) Architecture Diagram — 7 systems and 7 labelled interfaces. Free to use in your own documentation.

What this diagram shows

The VNA becomes the long-term system of record, which means a PACS can be replaced without another full data migration.

Components

Radiology PACS

Runs the radiology reading workflow and forwards finished studies to the VNA.

Cardiology PACS / CVIS

Echo, cath lab and nuclear cardiology images, often from a different vendor.

Specialty imaging

Dermatology photos, endoscopy, wound care and other encounter-based images, wrapped as DICOM or submitted with STOW-RS.

VNA

Stores everything in open formats, applies tag morphing so each source fits the enterprise model, and manages retention.

Enterprise viewer

One zero-footprint viewer for every department, reading from the VNA over DICOMweb.

EHR / EMR

Feeds patient updates to the VNA and embeds image links in the patient chart.

Cloud DR

An off-site replica of the archive for disaster recovery.

How the data flows

  1. Ingest from PACS

    Departmental PACS forward studies with C-STORE, usually once the study is finalised.

  2. Ingest non-DICOM

    Photos and video are uploaded with STOW-RS or converted to DICOM (for example VL Photographic Image objects) with the order or encounter attached.

  3. Normalise

    The VNA applies tag morphing — site prefixes, Issuer of Patient ID, procedure codes — so studies from different sources match the enterprise patient.

  4. Keep in sync

    ADT updates and merges from the EHR keep VNA demographics current; IHE IOCM carries deletions and corrections from PACS.

  5. Access

    The enterprise viewer searches and retrieves with QIDO-RS and WADO-RS; the EHR launches it in patient context with a URL.

  6. Protect

    The VNA replicates to the off-site copy over an encrypted link.

Interfaces in this diagram

Every connection in the diagram, ready to copy into an interface register or test plan.

#FromToProtocolDetail
1Radiology PACS (DICOM)→VNA (Enterprise Archive)DICOMC-STORE
2Cardiology PACS (CVIS / Echo)→VNA (Enterprise Archive)DICOMC-STORE
3Specialty Imaging (Photos · Endoscopy)→VNA (Enterprise Archive)DICOMwebSTOW-RS
4VNA (Enterprise Archive)→Enterprise Viewer (Zero-footprint)WADO-RS—
5EHR / EMR (Image links)→VNA (Enterprise Archive)HL7ADT
6EHR / EMR (Image links)→Enterprise Viewer (Zero-footprint)HTTPImage link
7VNA (Enterprise Archive)→Cloud DR (Off-site copy)VPNReplication

Design considerations

  • Agree which system owns deletions and corrections. Without IOCM or an equivalent, the VNA keeps images that PACS has deleted.
  • Use Issuer of Patient ID (0010,0021) when several sites share an MRN range.
  • Capture order or encounter context for non-DICOM images at the point of capture — it is very hard to add later.
  • Plan retention by data type; adult, paediatric and mammography imaging often have different legal retention periods.
  • Test the DR copy by restoring studies, not only by checking replication status.

Related reference

Frequently asked questions

What is a vendor neutral archive?

A VNA is an enterprise image archive that stores DICOM and non-DICOM content in standard formats, independent of any single PACS vendor. It lets a hospital share images across departments and replace viewing applications without migrating the archive.

What is the difference between a VNA and a PACS?

PACS is built around the radiology reading workflow; a VNA is built around long-term, multi-department storage and access. Many hospitals run both: PACS for reading and short-term cache, the VNA as the long-term system of record.

How do non-DICOM images get into a VNA?

Either they are converted to DICOM (for example VL Photographic Image objects or encapsulated PDF) and stored with C-STORE or STOW-RS, or they are stored as documents through IHE XDS. Order or encounter metadata should be captured at the same time.

What is tag morphing?

Tag morphing is rule-based modification of DICOM header values as images enter or leave the archive — for example adding a site prefix to patient IDs or normalising study descriptions — so data from different sources fits one enterprise model.

Make it match your site

Rename systems, add your AE titles and message types, then export PNG, SVG or PDF — or send a colleague a share link.

Open in Diagram Builder →

More architecture templates

All 12 templates →
PACS Architecture Diagram — preview
Imaging

PACS Architecture

Modalities, RIS worklist, PACS image manager, diagnostic and web viewers, and long-term VNA archive.

7 systems · 7 interfaces

Radiology Workflow Diagram (RIS–PACS) — preview
Imaging

Radiology Workflow

End-to-end order-to-report workflow: CPOE order, worklist, acquisition, PACS, reading and reporting.

6 systems · 7 interfaces

DICOM Modality Worklist (MWL) Workflow Diagram — preview
Imaging

Modality Worklist

How an HL7 order becomes a DICOM worklist entry, plus MPPS status and storage to PACS.

5 systems · 5 interfaces