MajwareMAJWARE
Free templateEditable7 systems7 interfaces

PACS Architecture Diagram

A Picture Archiving and Communication System (PACS) sits at the centre of every imaging department. This reference diagram shows the components most hospitals run and how they talk to each other: modalities acquire images, the RIS supplies the worklist, the PACS image manager stores and distributes studies, radiologists read on diagnostic viewers, clinicians use a web viewer, and a vendor neutral archive keeps the long-term copy.

Open & edit in Diagram Builder →Download SVG

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

PACS Architecture Diagram: RIS, EHR / EMR, Modalities, PACS, Diagnostic Viewer, Web Viewer, VNA
PACS Architecture Diagram — 7 systems and 7 labelled interfaces. Free to use in your own documentation.

What this diagram shows

Every connection is labelled with its protocol and the DICOM service or HL7 message it carries, so the diagram works as a starting point for design reviews, interface specifications, go-live runbooks and security assessments. Open it in the builder to rename systems to match your site and export it.

Components

Modalities

CT, MR, ultrasound and DX equipment. They query the worklist as a DICOM MWL SCU and send images to PACS as a Storage SCU.

RIS

Receives orders from the EHR, schedules exams, publishes the modality worklist and returns final reports.

PACS image manager

Storage SCP and Query/Retrieve SCP. Indexes studies in its database, applies routing and prefetch rules, and serves the viewers.

Diagnostic viewer

The radiologist’s workstation, with calibrated displays, hanging protocols and comparison with priors.

Web viewer

Zero-footprint browser viewer for referring clinicians, usually launched from the EHR and backed by DICOMweb (WADO-RS).

VNA

Vendor neutral archive holding the long-term, standards-based copy of every study, independent of the PACS vendor.

EHR / EMR

Source of orders (CPOE) and destination for final reports and image links.

How the data flows

  1. Order placed

    The clinician orders an exam in the EHR. An HL7 ORM^O01 (or OMI^O23 in v2.5 and later) creates the order in the RIS.

  2. Worklist query

    The technologist selects the patient on the modality, which sends a DICOM C-FIND to the Modality Worklist. Patient ID, accession number and Study Instance UID arrive pre-filled, so nothing is retyped.

  3. Image storage

    After acquisition the modality sends the images to PACS with DICOM C-STORE. PACS matches them to the order by accession number.

  4. Order context to PACS

    The RIS forwards orders and ADT updates to PACS over HL7, so studies carry correct demographics and prefetch rules can pull relevant priors.

  5. Reading

    The diagnostic viewer retrieves current and prior studies with C-MOVE or C-GET; web viewers use WADO-RS.

  6. Archive

    PACS forwards a copy of each study to the VNA with C-STORE for long-term retention and enterprise access.

  7. Results

    The signed report flows from the RIS to the EHR as HL7 ORU^R01.

Interfaces in this diagram

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

#FromToProtocolDetail
1EHR / EMR (Orders & Results)↔RIS (Orders / Reports)HL7ORM · ORU
2RIS (Orders / Reports)→Modalities (CT · MR · US · DX)DICOM MWLC-FIND
3Modalities (CT · MR · US · DX)→PACS (Image Manager)DICOMC-STORE
4RIS (Orders / Reports)→PACS (Image Manager)HL7ORM · ADT
5PACS (Image Manager)→Diagnostic Viewer (Radiologist)DICOM Q/RC-MOVE
6PACS (Image Manager)→Web Viewer (Clinicians)WADO-RS—
7PACS (Image Manager)→VNA (Long-term Archive)DICOMC-STORE

Design considerations

  • Record the AE title, IP address and port of every DICOM node. Most go-live failures are an AE title or port mismatch.
  • Keep modalities on a dedicated medical-device VLAN and allow only the DICOM ports PACS needs (commonly 104 or 11112) through the firewall.
  • Decide early whether the PACS or the VNA is the system of record for deletions and corrections, and use IHE IOCM so changes propagate.
  • Size storage for growth: studies per day × average study size × retention years, plus replication and backup overhead.
  • Plan for downtime: modalities should be able to hold studies locally or send to a secondary archive if PACS is unavailable.

Related reference

Frequently asked questions

What are the main components of a PACS?

A PACS consists of acquisition modalities, a PACS server (image manager and database), image storage (a short-term cache plus a long-term archive or VNA), diagnostic workstations for radiologists, web viewers for clinicians, and integration with the RIS and EHR over HL7 and DICOM.

Which DICOM services does a typical PACS use?

Storage (C-STORE) to receive images; Query/Retrieve (C-FIND, C-MOVE, C-GET) to serve viewers and other archives; Modality Worklist (C-FIND) and MPPS on the RIS side; Storage Commitment to confirm safe receipt; and increasingly DICOMweb (QIDO-RS, WADO-RS, STOW-RS) for web access.

What is the difference between PACS and VNA?

A PACS is optimised for the radiology workflow: fast access to recent studies, hanging protocols and reading tools. A VNA is a standards-based long-term archive that stores images from many departments and vendors, so the PACS can be replaced without migrating the archive again.

Can I edit this PACS diagram?

Yes. Choose “Open & edit in Diagram Builder” to load it into the free browser-based builder. You can rename systems, add nodes, change protocols, export PNG, SVG or PDF, or share a link. Nothing is uploaded — the diagram stays in your browser.

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 →
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

Vendor Neutral Archive (VNA) Architecture Diagram — preview
Imaging

VNA Architecture

Departmental PACS and non-DICOM sources consolidated into one VNA with an enterprise viewer and EHR links.

7 systems · 7 interfaces