Architecture

The ChRIS user interface, ChRIS_ui, is what a typical user sees in their web browser. It works by making HTTP requests to the backend API, which we call CUBE (an appreviation of its repository name, the ChRIS ultron backEnd).

At its core, CUBE is responsible for maintaining a database of users, files, and computational jobs. It runs jobs by sending job requests to one or more pfcon services. A pfcon provides CUBE access to a specific compute resource. pfcon speaks to pman, which is a shim that translates a job request from CUBE to a call to the compute resource cluster.

Other parts of ChRIS include pfdcm, oxidicom, and serie. These components integrate ChRIS with specialized features in the hospital environment, e.g. reception of DICOM from PACS and automatic execution of pipelines for clinical analysis.