PYCAD SSR Engine · OHIF integration
The PYCAD SSR Engine plugs into the OHIF viewer you already run. Large CT and tomosynthesis series stay on the server; the browser receives only the images on screen. Your PACS, your workflow and your OHIF stay the same.
The problem
Photon-counting CT, thin-slice protocols and breast tomosynthesis produce series of several gigabytes. A browser-based viewer has to download and decode all of it before MPR or 3D can start.
On a good connection that means minutes of waiting. On a home connection, MPR may never finish, the browser can use more than 10 GB of memory, and readers on laptops feel it first.
Our approach
The engine reads the series from your PACS once, renders slices, MPR planes and 3D on a server with a GPU, and streams just the pixels each viewport needs.
Window/level, zoom, pan and measurements still run in the browser on the images it receives, so they feel instant, and pixel values match stock OHIF, HU and ROI statistics included.
How it fits into OHIF
A connector script is loaded through OHIF’s documented extension mechanism in app-config.js. No fork of OHIF and no rebuild.
The study list, metadata, reports and segmentations keep coming from your PACS over DICOMweb. The engine only renders, and it never writes to the PACS.
Before downloading anything, the connector checks a series’ size. From 200 MB (configurable) it goes through the engine; smaller series stay on stock OHIF. MPR and 3D always use the engine.
While scrolling, the viewer receives fast previews sized to the pane; when you stop, the full-resolution slice arrives about 150 ms later.
Results
Each test opens the same study in the same viewer, once with the engine and once without. Times are until the view is on screen; shorter bars are better.
OHIF 3 · MPR and 3D
On a home connection (50 Mbit/s), stock OHIF 3 did not show MPR within 5 minutes on the 2.5 GB and 5 GB CTs; with the engine it took 2.1 s and 3.0 s.
OHIF 2 · scrolling and MPR
Across all large series, the engine sent 10 to 60 times less data to the browser: 6 to 60 MB instead of 73 MB to 5.1 GB.
Feature parity
We tested the engine against OHIF’s own features, on clinical-style public datasets: CT, MR, dental CBCT, PET/CT and breast tomosynthesis.
Crosshairs that move and rotate to any oblique plane, with the exact full-resolution plane at rest.
MIP, MinIP and average slabs, matching classic OHIF on the PET/CT MIP view.
OHIF’s 25 volume presets render on the server and look the same as vtk.js from the same camera.
Length, angle, ROIs with HU statistics and probe, with values identical to stock OHIF. In OHIF 2 the engine adds measurements in MPR, which stock OHIF 2 lacks.
Labelmap editing, brushes and DICOM SEG loading, with the same voxel counts as stock OHIF. RTSTRUCT and PET/CT fusion work too.
Structured reports are saved to your PACS and reopen as usual; the engine itself stays read-only.
Server capacity
One engine process serves every reader, sharing loaded studies between sessions. We simulated radiologists scrolling, reformatting and rotating 3D without pauses, a heavier load than real reading.
Smooth means 95% of scroll frames under 60 ms. As a rule of thumb, plan about 0.4 vCPU per actively scrolling reader. Memory grows with the number of different large studies open at the same time.
Being precise
Before production we are adding an automatic fallback to stock OHIF if the engine can’t be reached. Ultrasound, microscopy and 4D studies have not been tested yet.
How we tested
| Viewers | Stock OHIF 3.13 and the last OHIF 2 release (4.12.51), each with and without the engine connector |
|---|---|
| Server | One cloud server with 8 vCPU, 52 GB RAM and an NVIDIA T4 GPU (16 vCPU for one capacity run), with a test PACS on the same machine |
| Client | A Windows laptop running Chrome over the real internet, plus simulated home (50 Mbit/s) and mobile (15 Mbit/s) connections |
| Studies | A public kidney CT (320 MB), simulated photon-counting CTs of 2.5 GB and 5 GB built from it, and a public breast tomosynthesis study |
| Runs | 142 automated browser runs and a capacity test from 5 to 100 simulated users, November 2026. Results on the direct connection are medians of 3 runs. |
Tell us your OHIF version, your PACS and the size of your largest series. We’ll tell you what the engine can change for your readers.
The PYCAD SSR Engine is not cleared as a medical device. Results were measured with public or synthetic data and depend on the network, the server and the studies. OHIF is an open-source project; PYCAD is not affiliated with it.