eRAD PACS is a web-based radiology imaging workflow system described by the vendor for distributed reading settings, with support for worklists, image access, reporting, and related workflow tools. The available material spans product pages and release notes, so current capabilities and versioned changes should be read separately from broader marketing language. [1][2][7][8]

Documented workflow and reading functions

The product page describes eRAD PACS as a scalable, web-based enterprise system for radiology imaging workflow, with global worklist access for distributed environments. The vendor says the system can move images to the radiologist rather than the radiologist to the images, and it describes event-driven workflow rules that can assign studies, trigger notifications, pre-fetch priors, pre-cache studies, auto-print, and auto-fax. [1]

Embedded reporting is presented as part of the workflow. The vendor states that users can scroll and dictate, self-edit, attach key images, and use speech recognition from the PACS through a web-based report editor. The same material also refers to role-specific worklists, embedded dictation, and advanced imaging tools such as MPR, image fusion, mask subtraction, and key images. [1]

The workflow-solutions page describes use in multi-location imaging centers and remote reading arrangements. It says eRAD can pull relevant priors from any system, coerce data into a format that is usable but not edited at the source, and let a remote subspecialist access studies through one eRAD interface. These statements are vendor descriptions of intended workflow behavior rather than independent performance claims. [5]

Integration and data access

eRAD’s PACS API page states that third-party applications can use a collection of HTTP commands to access and modify PACS data. Documented commands include searching study, order, and report details; editing study demographics, order information, and clinical reports; launching the viewer; and retrieving report contents such as text, addenda, and key images. [2]

The same page says the API can expose logging and statistical information for third-party dashboards and management reporting, and it frames the API as a way to place images and reports into the context of the patient record in an EMR. The page also discusses image-enabling the EMR as a general integration pattern, not as a guarantee of any specific deployment. [2]

Release notes for RIS 4.2026.016 document an updated integration path between RIS and the DeepHealth PACS Viewer. That note says RIS now supports configuration for the DeepHealth viewer as well as V8/V9 PACS, uses a PACS Web Service Login method, and stores bookmarks on the PACS server so reopening a study from RIS restores the view session. [3]

Practical implementation examples and boundary conditions

The sources do not describe a step-by-step deployment procedure for combining a browser-based worklist, the PACS API, and a DICOM gateway in one environment. They identify separate functions: worklist access and embedded reporting on the product page, HTTP commands for report and study access, and Send Server rules for secure image transmission. Whether those functions operate together in a given deployment depends on the environment, interfaces, and routing rules configured there.

The strongest documented implementation boundary is that capabilities differ by module and version. Some items are current product-page descriptions, while others appear only in release notes for specific RIS or viewer builds. The sources also do not establish universal interoperability across every EMR, every site layout, or every legacy archive; they describe supported functions and named integration points only. [1][2][3][4]

Image transmission, storage, and viewer behavior

The DICOM gateway material describes Send Server appliances for secure image acquisition and sending from remote or disparate sites. It says the gateway encrypts and compresses data, keeps transmitting until data packets are confirmed and logged, and can reduce resend scope when a transmission fails. [6]

That same document says rules can control which studies are sent based on modality, body part, referring physician, or other criteria. It also says a Send Server can run on a laptop for mobile radiology use, and that document scanning, CD burning, and patient data can be accessed immediately with the DICOM solution. [6]

Viewer release notes describe versioned changes in the desktop viewer. Examples include use of original allocated bits for image storage in one build, adaptive window-level handling, support for segmentation editing and overlays in another build, and support for AI result storage, MG CAD objects, and Veye SR changes in later builds. [4]

Version-specific PACS behavior and release-note boundaries

RIS release notes for 4.2024.123 describe PACS V9 server-side image preparation. In that release, images are prepared on the server, loaded directly from there, and readiness is shown on the Pending Dictation worklist through Study Cache Progress and Priors Cache Progress indicators. The same release note says PACS V9 does not cache to the workstation in the same manner as PACS V7 and PACS V8. [7][8]

Those release notes also define implementation limits. One note warns that a caching optimization feature can cause excessive queries and degraded performance, and recommends not enabling that feature in production until resolution. Another note introduces a unique viewer window caption and updated lookup-table property names for viewer distinctions, which are versioned configuration changes rather than general product-wide guarantees. [7][8]