DICOM · Tool

DICOM Tag Editor — Edit Metadata Without Uploading

Inline editable DICOM tag table with VR-aware validation. Fix PatientName, PatientID, AccessionNumber, or any editable tag and download the corrected file — all in your browser.

Drop a .dcm file ↓ Browse the standard

Or use the Tag Editor as a side-panel inside the DICOM Viewer — same engine, alongside imaging.

Edit DICOM metadata

Drop a .dcm file below. Each file lands in the shelf — click Edit to open the editor as a popup over this page; files stay on the shelf so you can edit more after saving. Parsing, editing, and serialization all happen in your browser. Powered by Saga's dicom-tag-editor-core engine.

Drop a .dcm file here or click to browse — files stay in your browser

What you can edit

Patient demographics — PatientName, PatientID, BirthDate, Sex (see the Patient module).
Study context — StudyDate, AccessionNumber, ReferringPhysicianName, StudyDescription.
UIDs — StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID (with optional consistent-remap for an entire study).
Modality + body part — Modality, BodyPartExamined, ViewPosition for rotated scans.
Imaging parameters — slice thickness, pixel spacing (don't change unless you know why).

Pixel data is read-only. Private tags and sequence elements editable with caution.

VR-aware validation

Every tag has a Value Representation (VR) that constrains its allowed values. The editor enforces the rules inline:

DA Date fields → date picker writing YYYYMMDD.
CS Code String fields → enum dropdown from PS3.3.
PN Person Name → caret-separated component entry.
IS, DS, US numeric → numeric input with range checks.
UI UID → format validation + optional remap-all-occurrences.

Common edit workflows

Fix a mis-matched MRN on an imported study before archive.
Reassign an Accession Number for billing or worklist reconciliation.
Remap UIDs when transferring a study across institutions.
Correct modality or body part after a mis-configured scan.
Patch free-text fields that contain PII before sharing externally.

Need these edits in a production pipeline rather than one file at a time? Saga's medical imaging integration team builds Mirth Connect + Orthanc flows that apply these corrections at ingest — so the human-in-the-loop tag editor is only the occasional fallback, not the routine path.

FAQ

Can I edit any DICOM tag?

Most editable tags yes — PatientName, PatientID, AccessionNumber, study/series UIDs, demographics, and other text/numeric fields. VR-restricted fields (DA date picker, CS enum, SQ sequence) get inline validation. Pixel data (7FE0,0010) is read-only to prevent accidental image corruption.

What's a "VR" and why does it matter?

Value Representation — DICOM's type system. A DA (Date) field only accepts YYYYMMDD; a CS (Code String) field has a defined enum per PS3.3; a PN (Person Name) field uses caret-separated components. The editor enforces VR rules so you don't accidentally write malformed values that break downstream PACS/viewer parsing.

Why would I edit DICOM tags?

Common reasons: patching a wrong MRN on an imported study, reassigning an accession number for billing, fixing a typo in patient name before archive, remapping UIDs for cross-institution research transfer, or correcting modality after a mis-configured scan.

Does it upload the file?

No — entirely client-side. Edits happen in the browser via dcmjs. Download button produces the edited .dcm (or ZIP for multi-file studies). Verify via DevTools Network tab: no outbound request carrying the file bytes.

How does this compare to Innolitics File Editor?

Innolitics' File Editor is a standalone tag browser/editor. The Saga editor sits inside a full DICOM viewer — you can inspect the image AND edit tags in one session, then save. For engineers who need "view the image to understand what needs editing," the integrated workflow is faster.