DICOM · Tools & References

DICOM Tools & References

Free browser-based DICOM tools — viewer, tag editor, validator, anonymizer, and samples — plus the NEMA PS3 standard browser and Learn DICOM explainers. Built and used by Saga's medical imaging team; files never leave your browser.

Launch the viewer → Browse all tools

  • Files never leave your browser
  • Built on OHIF v3 (open-source)
  • No account required
  • HIPAA-conscious design

Pick a tool

Tools marked ✓ In viewer also run as a side-panel inside the OHIF viewer at /dicom/viewer/app. The standalone pages are optimized for one-shot tasks; the viewer panels keep the same engine alongside imaging when you need study context.

  • DICOM Viewer

    ✓ In viewer

    Drag a .dcm file in and render it locally. Window/level, pan/zoom, multi-frame, tag browser. Built on OHIF v3.

    This is the viewer

  • Tag Editor

    ✓ In viewer

    Inspect every tag in a DICOM file, edit values with VR-aware validation, save the modified file.

    Side-panel in viewer

    Or open in the viewer →

  • Validator

    ✓ In viewer

    Check PS3.3 + PS3.5 + PS3.6 conformance. Issue list with spec citations + JSON / Markdown report.

    Side-panel in viewer

    Or open in the viewer →

  • Anonymizer

    ◷ Soon

    Redact PHI per PS3.15 Basic Confidentiality Profile. Researcher-friendly defaults; no PHI will leave your browser.

    In active development — not shipped yet

  • Sample DICOM files

    ✓ In viewer

    Curated CT, MR, US, mammography studies for testing. One-click deep-link into the viewer.

    Featured in viewer launcher

    Or open in the viewer →

  • Spec Browser

    § Reference

    Every DICOM attribute, CIOD, module, SOP class, VR, and transfer syntax — cross-linked with HL7 v2, FHIR ImagingStudy, and cloud conformance notes.

    6,200 pages from NEMA PS3, normalized + cross-linked

Same engine, two surfaces

Each tool has a focused standalone page (drop a file, do the thing, save) AND runs as a side-panel inside the OHIF viewer when you need imaging context. Both surfaces share the same engine — Saga's DICOM core packages — so your edits behave identically wherever you make them. Pick the workflow that matches the job at hand.

Files never leave your browser

Every tool runs in your browser via JavaScript. Parsing, editing, validation, and anonymization execute locally — there's no upload, no telemetry on file content, no server-side processing. Verified by inspecting network requests during a full edit + save cycle (zero outbound DICOM bytes). The privacy posture is the same whether you use the standalone page or the side-panel inside the viewer.

Built on OHIF v3

The viewer is the OHIF v3 SPA — the de-facto clinical-grade open-source DICOM viewer — with a Saga shell. The tag editor, validator, and download engines are Saga's own DICOM core packages, proprietary but free to use through these tools and inside the viewer. Same engine runs on the standalone pages and as side-panels in the viewer, so behaviour is identical across both surfaces.

The standard, cross-linked

The Spec Browser is the entire NEMA PS3 standard — every CIOD, module, attribute, SOP class, VR, and transfer syntax — snapshotted from the canonical source, normalized, and cross-linked. 6,200 pages, fully static, no signups.

Each attribute page surfaces what integration engineers actually need beyond the spec text: HL7 v2 segment mappings (IHE Radiology Technical Framework), FHIR ImagingStudy mappings (HL7 CC0), cloud conformance notes (AWS HealthImaging, Azure HDS, GCP Healthcare API), and Mirth Connect transformer examples.

What runs where

Tool Standalone page In the viewer
DICOM Viewer This is the viewer · Launch →
Tag Editor Open standalone Side-panel · select DICOM Tag Editor in the viewer's panel chooser
Validator Open standalone Side-panel · select DICOM Validator in the viewer's panel chooser
Anonymizer Coming soon Coming with standalone
Sample DICOM files Browse the catalog Featured in the viewer's launcher dashboard
Spec Browser Open the browser Reference only — not a viewer panel

Further reading

The tools above are runnable. These are the explainers + long-form reference behind them.

Frequently asked questions

Are these DICOM tools really free?

Yes — all five tools are free to use with no account, no upload, and no usage limits. They run entirely in your browser; we don't see your files. The viewer is built on the open-source OHIF v3 platform. The tag editor, validator, and anonymizer engines are Saga-built — proprietary, free to use through these pages and inside the viewer.

What's the difference between the standalone tools and the viewer's side-panels?

Same engine, different workflow. The standalone pages (e.g. /dicom/tag-editor) are optimized for a single one-shot task — drop a file, do the thing, save. The viewer's side-panels run the same logic alongside imaging, so you can edit tags or validate while reviewing the actual study. Use the standalone when you don't need imaging context; use the viewer when you do.

Do my DICOM files leave my computer?

No. Every tool runs entirely in your browser via JavaScript. Parsing, editing, validation, anonymization, and rendering all happen locally — there's no upload, no analytics on file content, and no telemetry that includes PHI. Verified by inspecting network requests during the workflow.

Which tools work in the OHIF viewer?

The DICOM Viewer is the OHIF SPA itself. The Tag Editor and Validator are wired in as right-side panels you can switch to from the panel chooser while a study is open. The Anonymizer is in development. Sample DICOM files are featured in the viewer's launcher dashboard for one-click loading.

Which platforms do these tools support?

Any modern browser — Chrome, Edge, Firefox, Safari — on Windows, macOS, ChromeOS, or Linux. There's no install, no extension, no driver. You just open the page and use the tool.

Are these HIPAA-compliant?

HIPAA compliance is a property of how YOU use a tool, not the tool itself. These tools are HIPAA-conscious by design (files stay local, no telemetry on file content), which removes the upload-leak risk that is a common blocker. If you need a fully audited de-identification path for production research data, contact our team about managed pipelines.

Sources & Licensing

Every fact on these pages comes from an authoritative upstream: NEMA, HL7, IHE, cloud vendor docs, or OSS reference libraries. Full source + license attribution: Data Sources & Licensing.

Why Saga Built This

We spend our days integrating DICOM across PACS, VNA, cloud imaging platforms (AWS HealthImaging, Azure HDS, Google Cloud Healthcare), and AI/ML pipelines. The DICOM standard is dense and the reference tooling hasn't kept up with modern workflows.

Our DICOM browser starts with the NEMA standard and layers on what integration engineers actually need: HL7 v2 mappings (pulled from IHE Radiology Technical Framework), FHIR ImagingStudy mappings (CC0, HL7), cloud conformance data (AWS/Azure/GCP), and Mirth Connect transformer examples.

If you need help with a production DICOM integration, talk to us.