Imaging viewers
Real patient studies from a public research archive, read in the browser. Pick the modality; they share one engine, so the controls behave the same way in each.
- CT Slices in Hounsfield units, with the windows a workstation has 76 serieschest, kidney, liver, prostate
- MRI T1, T2, FLAIR and diffusion, picked one sequence at a time 101 seriesbrain, breast, liver, prostate
- X-ray One or two projections, so brightness and zoom do all the work 28 serieschest
- Ultrasound Sector images and cine loops, scrolled frame by frame 16 seriesliver
- All modalities The whole index in one page, mammography and PET included 245 series20 collections
Questions
A demonstration of browser rendering, not a reporting workstation. Nothing here is for diagnostic use.
Why one viewer per modality?
Because the controls do not mean the same thing in each. A CT window is a statement about Hounsfield units, so Lung and Bone are real presets with fixed numbers. MR pixel values have no absolute scale, so the same buttons can only widen or narrow whatever the file came with. A radiograph is one image, so scrolling has nothing to move through, and a cine loop scrolls through time rather than through space.
One engine renders all of them. What changes per page is the window presets, the fields in the corner readout and the wording of the instructions beside the image. The combined viewer is the same thing with the modality picker left in.
Where do the studies come from?
The NCI Imaging Data Commons, which hosts collections from The Cancer Imaging Archive. The images are de-identified and public, and the endpoint is a viewing-only proxy, so the pages render pixels and never offer a download. The index is built once by a script that walks the archive, keeps the series that are worth opening and records what each one is.
The finding in the picker names the entry criterion of the collection a case came from, not a report read off these pixels. Every patient in a glioblastoma collection has glioblastoma, so the label is true of the case.
Is anything uploaded or stored?
No. Your browser asks the archive for the frames over DICOMweb and decodes them in a web worker on your own machine. No server of mine sits in the middle, nothing is written back to the archive, and the local-file source reads files you drag in without sending them anywhere.
What is it built on?
Cornerstone3D, the MIT-licensed rendering engine that also sits underneath the OHIF Viewer. OHIF itself is AGPL-3.0, so none of its code is used here. Each viewer page carries its own questions about the engine, the archive and DICOMweb.