Introduction

The typical implementation scenario includes a central site, installed locally or on the Cloud, and peripheral sites that send studies to the central site.

VIEW is usually installed with the server component PACS that can act as a cache if another PACS is already present.
The technical architecture is described here.

Components can be installed as Docker images following these instructions:

• PACS and VIEW on a central site

• VEW on a central site (only with file system integration)

• FEED on peripheral sites.

Optional installation procedures for Kubernetes environments can be provided.

DICOM images can be stored via DICOM and DICOMweb or VIEW can read directly from the filesystem.
VIEW can query and retrieve from existing PACS nodes (also simultaneously from more nodes supporting federated Q&R).

VIEW can be easily integrated into existing EMR, EHR, HIS, RIS, and LIS via simple integrations for opening images inside an iFrame or on single or multi-monitors.
Advanced integrations (e.g. sending images and annotations to a RIS or sending a snapshot to a LIS) can be set up on the VIEW.