PYCAD SSR Engine
A server-side rendering engine for medical imaging. It renders multi-gigabyte CT, MR and tomosynthesis studies on a server and streams only what each screen shows, so the web viewer you already use opens them in seconds, on any laptop and any connection.
What it enables
Photon-counting CT, thin-slice protocols and breast tomosynthesis open as quickly as a small study, because the browser never downloads the whole series.
A home connection or an ordinary laptop is enough: the viewer receives megabytes of images instead of gigabytes of raw data.
One engine process serves every user and shares loaded studies between sessions, so capacity grows with CPU cores, not with copies of the data.
The complete volume stays on your server. Each browser only receives the images it displays.
The engine plugs into an existing web viewer through a connector and reads from your PACS or storage. Your interface, tools and workflow don’t change.
Volume rendering runs on the server’s GPU and streams to the browser, so 3D works on devices that couldn’t render it themselves.
How it works
The engine pulls a series from your PACS over DICOMweb, or from your storage, into a bounded cache. It decodes compressed and multi-frame formats such as JPEG 2000 and HTJ2K itself, and never writes back.
Slices, MPR and oblique planes, thick slabs and 3D volume rendering, on all CPU cores and a GPU. Only the newest request per view is rendered, so fast scrolling never queues stale frames.
Light previews while the user scrolls or rotates, then the full-resolution image when they stop. Pixel values are preserved, so measurements and HU statistics stay exact.
Each viewer gets a connector that routes the heavy views to the engine and leaves everything else as it was, including the viewer’s own tools and reports.
Works with your viewer
The engine doesn’t come with its own viewer. It sits behind the one your users already know.
Available now
Connectors for stock OHIF 3.13 and the last OHIF 2 release, added through OHIF’s own extension mechanism, with no fork and no rebuild. Tested for MPR, 3D, measurements, segmentation and reports.
Through a connector
The engine has a documented interface, and the OHIF connectors follow a template meant for new viewers. For an in-house or commercial web viewer, we write the connector and keep your interface and tools as they are.
Proof
In the OHIF viewer · public data
Stock OHIF 3 and OHIF 2, same study with and without the engine, over the real internet. All OHIF results
Capabilities
| 2D | Large stacks with smooth scrolling, MPR and oblique planes, thick slabs (MIP, MinIP, average), window/level kept in the browser |
|---|---|
| 3D | GPU volume rendering with OHIF’s 25 presets, MIP, MinIP and average blending, rotation streamed at interactive rates |
| Data | DICOM over DICOMweb from your PACS, multi-frame and enhanced CT/MR, breast tomosynthesis, JPEG 2000 and HTJ2K decoded on the server |
| Overlays | Segmentations (DICOM SEG and labelmaps) on the engine’s planes, with the same voxel counts as the viewer’s own path |
| Fidelity | Original pixel values preserved: HU, ROI statistics and measurements match the viewer without the engine |
Deployment and scaling
Packaged as a container with GPU access. Capacity figures come from simulated readers working without pauses, a heavier load than real reading; your numbers depend on your studies and how many different ones are open at once.
Tell us which viewer you run, where your images live and how large your biggest series are. We’ll tell you what the engine can change.
The PYCAD SSR Engine is not cleared as a medical device. Results come from tests with public or synthetic data and depend on the network, the server and the studies.