MajwareMAJWARE
Free templateEditable7 systems6 interfaces

PACS Data Migration Architecture Diagram

Replacing a PACS means moving years of images — often hundreds of terabytes — without losing a study or breaking its link to the report. This diagram shows the parts of a controlled migration: a migration engine reads from the legacy PACS by DICOM Query/Retrieve (or directly from its storage), corrects headers against the RIS, writes to the new archive and records every object in an audit database.

Open & edit in Diagram Builder →Download SVG

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

PACS Data Migration Architecture Diagram: RIS, Legacy PACS, Migration Engine, Target VNA, New PACS, Legacy Storage, Audit Database
PACS Data Migration Architecture Diagram — 7 systems and 6 labelled interfaces. Free to use in your own documentation.

What this diagram shows

The same pattern applies whether the target is a new PACS, a VNA or a cloud archive.

Components

Legacy PACS

The source archive, queried with C-FIND and asked to send studies with C-MOVE.

Legacy storage

Direct read of DICOM files from the old storage, used when Q/R throughput is too slow or the legacy database is unreliable.

Migration engine

Schedules the work, retrieves studies, applies tag morphing and validation, and writes to the target.

RIS

Reference for reconciliation — correct patient IDs, accession numbers and procedure codes.

Target VNA

The new long-term archive receiving migrated studies.

New PACS

Receives a prefetched subset (recent studies and relevant priors) for go-live.

Audit database

Records every study and instance moved, with counts and status — your evidence that nothing was lost.

How the data flows

  1. Inventory

    The engine queries the legacy PACS with C-FIND to build a complete list of studies, series and instance counts.

  2. Reconcile

    Each study is checked against RIS orders and ADT data; mismatched IDs and missing accession numbers are corrected by rule or queued for review.

  3. Retrieve

    Studies are pulled with C-MOVE, or read from storage when faster, newest first or in an agreed priority order.

  4. Transform and store

    Tag morphing fixes identifiers and descriptions, then the engine sends to the target with C-STORE and confirms receipt with Storage Commitment.

  5. Verify and log

    Instance counts are compared between source and target, and every result is written to the audit database.

  6. Prefetch for go-live

    Relevant priors are pushed from the new archive to the new PACS so radiologists have history on day one.

Interfaces in this diagram

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

#FromToProtocolDetail
1Legacy PACS (Source archive)→Migration Engine (Q/R · Tag morphing)DICOM Q/RC-MOVE
2Legacy Storage (Direct file read)→Migration Engine (Q/R · Tag morphing)TCP/IPFile read
3Migration Engine (Q/R · Tag morphing)→Target VNA (New archive)DICOMC-STORE
4RIS (Order history)→Migration Engine (Q/R · Tag morphing)HL7ADT · ORM
5Migration Engine (Q/R · Tag morphing)→Audit Database (Reconciliation log)TCP/IPAudit log
6Target VNA (New archive)→New PACS (Go-live)DICOMPrefetch

Design considerations

  • Measure real retrieval throughput in the first week; the legacy PACS is usually the bottleneck, not the network.
  • Migrate recent years first so the new system is useful immediately, then work backwards.
  • Decide what to do with deleted, hidden and unverified studies before you start.
  • Run a dual-delivery period: new studies go to both old and new systems until cutover.
  • Keep the audit database after the project — auditors and clinicians will ask where a study went.

Majware software

DICOM Migration Engine

Majware’s desktop tool for the sending and checking steps: it sends studies exported to disk to the new PACS over C-STORE, with resume, retries and a CSV log for every study, then audits the new PACS against the legacy PACS with read-only C-FIND and repairs missing studies with a C-MOVE you approve. It does not change tags.

See DICOM Migration Engine →

Related reference

Frequently asked questions

How long does a PACS migration take?

It depends on volume and on how fast the legacy system can deliver images, which is usually the limiting factor. Large archives can take months. Measure throughput in a pilot and consider reading directly from storage to speed it up.

What is tag morphing in a PACS migration?

Tag morphing is rule-based correction of DICOM header values during migration — for example fixing patient IDs to match the RIS, adding an Issuer of Patient ID, or standardising study descriptions — so migrated data matches the new system.

How do you validate a PACS migration?

Compare study, series and instance counts between source and target for every study, confirm receipt with DICOM Storage Commitment, review a sample of studies visually, and keep an audit log of every object moved and every exception.

C-MOVE or direct file migration?

C-MOVE uses the legacy PACS as intended and returns its corrected view of the data, but it is often slow. Reading files from storage is much faster but bypasses the legacy database, so corrections made in the PACS may not be in the files. Many projects use both.

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