PACS, VNA, and DICOM routers: where your product fits

  • A PACS manages radiology workflow and display, while a VNA stores enterprise imaging data across multiple clinical departments.
  • Third-party cloud products receive images from a PACS, a VNA, or a DICOM router rather than connecting to individual modalities.
  • Hospitals push studies outward over standard DICOM C-STORE or DICOMweb rather than permitting inbound queries into clinical networks.
  • Every sending system requires a vendor DICOM conformance statement detailing supported Storage SOP classes and transfer syntaxes.

In a hospital, modalities capture images. A Picture Archiving and Communication System (PACS) stores and displays them, while a Vendor Neutral Archive (VNA) may hold a long-term copy. A product that receives studies from a hospital usually connects to the PACS, the VNA, or a router, not to each scanner.

When you build a cloud imaging product, you do not need to wire into dozens of scanners. Instead, you interface with one central system that forwards studies out. Understanding how these systems divide work helps you ask the right questions during technical onboarding.

PACS vs VNA: what does each system do?

A Picture Archiving and Communication System (PACS) handles day-to-day image display and storage for a specific department like radiology. It pairs image storage with clinical viewing tools, hanging protocols, and radiologist reporting queues. A Vendor Neutral Archive (VNA) consolidates imaging data from many departments into a single long-term repository using standard formats.

Historically, hospitals bought proprietary PACS suites that coupled their index, archive, and diagnostic viewer into one bundle. Moving millions of studies to a new PACS vendor required costly data migrations. As clinical photography, cardiology, and pathology generated digital records, hospitals adopted enterprise imaging strategies to manage all clinical multimedia in one archive.

The HIMSS-SIIM collaborative defines enterprise imaging as a unified strategy across a healthcare organization. It captures, indexes, stores, and analyzes all clinical imaging to enhance the electronic health record. To prevent vendor lock-in, hospitals began deconstructing the traditional PACS. They separated the archive layer from the viewing and workflow layers, giving rise to the standalone VNA.

In practice, the boundary between a modern PACS and a VNA is often blurry. No formal standard defines “PACS” or “VNA” as official product classes. Many PACS vendors now package archive capabilities that function like a VNA, and hospital staff often use the terms interchangeably.

What do the modality, RIS, and HIS do?

Imaging modalities are the physical medical devices that capture diagnostic scans, such as CT, MRI, and ultrasound scanners. Once an operator completes an examination, the modality transmits the acquired images using a DICOM C-STORE operation, as defined in DICOM PS3.4 Annex B.

Upstream clinical systems coordinate the patient information that modalities attach to these images. A Hospital Information System (HIS) registers patient demographics and tracks hospital-wide admissions. A Radiology Information System (RIS) manages departmental orders, scheduling, and billing for imaging exams.

The Integrating the Healthcare Enterprise (IHE) Radiology Technical Framework outlines how these systems interact in its Scheduled Workflow profile. Section 2.4 illustrates typical functional groupings:

  • The HIS often serves as the Admission, Discharge, and Transfer (ADT) system and Order Placer.
  • The RIS acts as the Department System Scheduler and Order Filler.
  • The modality queries the RIS for patient worklists before scanning.

As explained in our guide to DICOM Modality Worklist (MWL), the RIS sends order details to the scanner. Technicians do not need to retype patient names manually. The RIS does not store pixel data or transmit diagnostic images to your software. After image acquisition, the modality sends pixels to an Image Archive through the IHE RAD-8 transaction, which relies on standard C-STORE transfers.

What is a DICOM router, and where does it sit?

A DICOM router is an intermediary software node that receives DICOM studies and forwards them to designated local or external destinations. You may also hear these tools called DICOM gateways or routing appliances. The DICOM standard does not define a router as a distinct service class, but vendors offer them to orchestrate traffic between disparate networks.

A router sits between image sources and downstream systems. For example, it can sit between scanners and a PACS, or between an enterprise archive and an offsite research platform. It acts as a traffic controller on the local network.

Hospital security policies often forbid individual modalities or core archives from initiating direct outbound internet connections. In these networks, administrators configure a single internal DICOM router to handle outbound traffic. The router collects completed studies from clinical systems, applies site forwarding rules, and routes the files to external vendors.

Which system will actually send studies to your product?

In most hospital integrations, the PACS, a VNA, or a centralized DICOM router will send studies directly to your receiving endpoint. Scanners can theoretically transmit images directly to an external destination, but hospital administrators rarely allow this. Pointing 20 separate scanners at an external IP requires 20 separate configuration projects, whereas sending from a PACS or router requires only one.

Under DICOM PS3.4 Annex B, the Storage Service Class supports routine transfers between archives, workstations, and external endpoints. From the hospital perspective, your receiving service functions as just another DICOM destination in their routing table.

Standard hospital integrations rely on outbound push rather than inbound pull. As detailed in push vs pull in medical imaging workflows, hospitals block inbound connections from the internet to protect clinical equipment. The hospital system initiates the TLS handshake and pushes images out to your cloud service.

How a transfer starts depends on local hospital workflow:

  • An automatic routing rule forwards studies that match specific criteria, such as a designated modality or reading code.
  • A radiologist or technician manually selects a study in their viewer and clicks a “Send to” destination button.
  • A batch script runs overnight to forward research cohorts.

To identify your sending system, ask the hospital team which box holds your target studies and has approval to transmit outbound network packets. That system is your integration partner.

Who owns each system, and who do you talk to?

Hospital imaging systems belong to different administrative groups, so you must identify the specific team that controls external routing rules. System ownership varies between healthcare facilities, but responsibilities usually follow common operational boundaries.

PACS administrators and imaging IT specialists run departmental PACS and routing appliances. They configure AE titles, maintain forwarding rules, and monitor daily transmission logs. Enterprise IT and infrastructure teams manage the hospital data center, core network firewalls, and enterprise VNAs. Radiology managers and clinical IT support the departmental RIS.

When you start an integration, request the DICOM Conformance Statement for the sending system. DICOM PS3.2 Chapter 7 requires every conformant network implementation to publish this document. It specifies:

  • Which Storage SOP classes the system can transmit.
  • Which transfer syntaxes and compression codecs it supports.
  • Any character set limitations or custom metadata behaviors.

Our guide on understanding DICOM conformance statements explains how to verify that the hospital sender matches your receiver capabilities. Once you confirm protocol compatibility, consult our pre-flight checklist for hospital onboarding to exchange network parameters with the local PACS administrator.

Why is the sender list never finished?

Hospital network configurations and imaging software change regularly over years of clinical operations. Healthcare organizations frequently acquire new clinics, replace aging modalities, and upgrade departmental archives.

A hospital group may operate three different PACS products across its regional campuses. Each vendor software features different routing interfaces, custom timeout settings, and distinct error reporting behavior. When a transmission fails, the failure notification displays on the hospital administrator management console rather than in your application logs.

Upgrades introduce subtle configuration shifts. When a hospital migrates to a modern VNA, staff might update the sender Application Entity (AE) title or change source IP addresses without advance notice. If your infrastructure expects rigid static credentials, transfers halt until administrators coordinate manual updates.

Connecting each new hospital sender requires coordinating firewall rules, client certificates, and protocol handshakes. Managing these listeners and TLS certificates across dozens of hospitals demands continuous maintenance from engineering teams. A managed DICOM gateway such as Dicomly handles this connectivity layer through an API. It provisions endpoints and client certificates, then converts inbound C-STORE traffic into standard HTTPS webhooks. Your team does not need to maintain raw DICOM listeners. The trade-off is clear: you pay a monthly service fee and rely on an external provider for ingestion, rather than maintaining custom socket servers in-house.

What can you do today?

You can map your target hospital imaging architecture on one page before scheduling an initial integration call. Creating a visual diagram clarifies which internal team controls your data feed.

Take these three practical steps:

  1. Draw the basic data chain: Modality → PACS → VNA or Router → Your Product.
  2. Ask your clinical sponsor which system holds the studies you need and who manages its outbound DICOM destinations.
  3. Obtain the vendor DICOM conformance statement for that sending system and compare its supported SOP classes against your ingestion requirements.

Once you know which system sends the data, you can agree on network parameters and begin testing your receiver.

Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →

Sources

  1. DICOM PS3.4 Annex B — Storage Service Class (dicom.nema.org)
  2. IHE Radiology Technical Framework Volume 1 — Scheduled Workflow (www.ihe.net)
  3. HIMSS-SIIM Enterprise Imaging White Paper Reflections (pmc.ncbi.nlm.nih.gov)
  4. DICOM PS3.2 Chapter 7 — Conformance Statement Requirements (dicom.nema.org)

Start receiving DICOM today.

Early access. No credit card. First endpoint free.