Multi-Site Enterprise Imaging Diagram
Hospital groups rarely start with one PACS. This diagram shows a common way to join several sites without replacing everything: each hospital keeps its local PACS for reading, every site forwards to a central VNA, an EMPI reconciles patient identity across sites, and one enterprise viewer gives clinicians a single view of the patient’s imaging wherever it was acquired.
Free, no sign-up. The builder runs in your browser; nothing is uploaded.
What this diagram shows
Add more sites by duplicating the modality and PACS pair in the builder.
Components
Site modalities
Acquire images and store them to the local PACS, so acquisition never depends on the WAN.
Site PACS
Provide fast local reading and forward studies to the central archive.
Central VNA
Holds the enterprise copy of every study and is the source for cross-site access.
Enterprise viewer
A single viewer for all sites, reading from the VNA.
EMPI
Links each site’s MRN to an enterprise identifier using PIX-style cross-referencing.
Cloud archive
Off-site replica for disaster recovery.
How the data flows
Local acquisition
Modalities store to their own site PACS with C-STORE, so a WAN outage never stops scanning.
Forward
Each PACS forwards studies to the central VNA, typically when the study is complete.
Reconcile identity
The EMPI receives ADT from every site and cross-references identifiers (IHE PIX), so the VNA can present one patient across sites.
Access
The enterprise viewer retrieves from the VNA with WADO-RS, so clinicians see priors from any site.
Protect
The VNA replicates to the cloud archive.
Interfaces in this diagram
Every connection in the diagram, ready to copy into an interface register or test plan.
| # | From | To | Protocol | Detail |
|---|---|---|---|---|
| 1 | Modalities (Site A) | →PACS (Site A) | DICOM | C-STORE |
| 2 | Modalities (Site B) | →PACS (Site B) | DICOM | C-STORE |
| 3 | PACS (Site A) | →VNA (Central Archive) | DICOM | Forward |
| 4 | PACS (Site B) | →VNA (Central Archive) | DICOM | Forward |
| 5 | VNA (Central Archive) | →Enterprise Viewer (All sites) | WADO-RS | — |
| 6 | VNA (Central Archive) | →Cloud Archive (DR copy) | VPN | Replication |
| 7 | EMPI (Enterprise MRN) | →VNA (Central Archive) | HL7 | PIX · ADT |
Design considerations
- MRNs collide across sites. Use Issuer of Patient ID or a site prefix from day one.
- Size WAN links for forwarding peaks such as the start-of-day backlog, not for average load.
- Decide whether priors are fetched to the reading site on demand or prefetched overnight.
- Keep one Study Instance UID per study across sites; never regenerate UIDs when forwarding.
Related reference
Frequently asked questions
How do multiple hospitals share a PACS?
Either they move to one shared PACS or, more often, each keeps a local PACS and forwards to a shared VNA with an enterprise viewer. An EMPI links patient identifiers so images from all sites appear under one patient.
What is an EMPI in imaging?
An enterprise master patient index cross-references each site’s patient ID for the same person. Imaging systems use it — often through IHE PIX/PDQ — to show a complete imaging history across hospitals.
What happens if the WAN goes down?
In this design each site keeps scanning and reading locally; forwarding to the central archive queues up and catches up when the link returns. Only cross-site priors are temporarily unavailable.
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.