DICOM Tag Editor
DICOM tag editor for fixing studies in place
Edit DICOM tags on studies that have already been sent — correct a wrong Accession or MRN, fix a mangled study description, and re-push the corrected exam. Works on studies in cloud stores as well as on-prem PACS.
The basics
What is a DICOM tag editor?
A DICOM tag editor lets you change the metadata attributes inside a DICOM study — Patient Name, Patient ID, Accession Number, Study Description, Referring Physician, and the rest — without re-acquiring the images. It is the tool you reach for when a technologist keys in the wrong MRN, when a modality writes a study description no downstream system recognizes, or when an outside study arrives with metadata that does not match your conventions.
The problem is usually not the editing itself; it is where the study already lives. Once an exam has been archived to a cloud DICOM store, many tools can no longer touch it — you can view it, but not correct it. RadFuzion edits tags on studies wherever they are: in its own cache, on a traditional PACS, or in a Google Cloud Healthcare, Azure, DICOMweb, or S3 destination, then writes the corrected study back.
Why RadFuzion
A tag editor that reaches into the cloud
Most DICOM tag editors assume the study is sitting on local disk. RadFuzion is a router first, so it can fetch, correct, and re-send an exam that already left the building.
Edit studies already in the cloud
Query a Google Cloud Healthcare, Azure, DICOMweb, or S3 store, pull the study, correct its tags, and push it back — without a round trip through separate tooling.
Or fix it automatically, in flight
Routing rules can normalize and coerce tags as studies pass through, so recurring problems — a modality that always writes the wrong station name — get corrected once rather than exam by exam.
Merge and split studies
When an exam arrives under two Study UIDs, or two exams land under one, merge or split them so the study identity matches what the archive and the RIS expect.
Under the hood
Tag editing capabilities
- check_circleEdit Patient Name, Patient ID, Accession Number
- check_circleCorrect Study/Series Description
- check_circleFix Referring Physician and station values
- check_circleEdit studies held in cloud DICOM stores
- check_circleEdit studies on traditional PACS
- check_circleMerge studies sharing an identity
- check_circleSplit studies that arrived combined
- check_circleRule-based tag coercion in flight
- check_circleRe-push corrected studies to any destination
- check_circleStudy UID normalization and regeneration
- check_circleFull audit trail of who changed what
- check_circleAnonymization profiles for de-identification
When you need it
The common cases are mundane and constant: an exam booked under the wrong patient, an Accession that does not match the order, a modality writing "CHEST" where the RIS expects "XR CHEST 2V", or priors pulled from an outside facility whose descriptions match nothing in your exam-code table. Each one blocks something downstream — a study that will not reconcile, a worklist entry that never clears, an AI pipeline that skips the exam.
Fixing these by re-acquiring images is not an option, and asking the archive vendor to correct records is slow. A tag editor closes the loop in minutes. Where the same defect recurs, converting the manual fix into a routing rule — or into RadMatch for study-description normalization — stops it coming back.
FAQ
DICOM tag editor questions
Can I edit DICOM tags on a study already sent to the cloud?add
Yes. RadFuzion can query a Google Cloud Healthcare DICOM store, Azure, DICOMweb endpoint, or S3 bucket, retrieve the study, edit its tags, and write the corrected study back. Many tag editors only work on local files, which is the usual sticking point once an exam has been archived.
Which DICOM tags can be edited?add
Patient-level identifiers (Patient Name, Patient ID, birth date), study-level values (Accession Number, Study Description, Study Date, Referring Physician), and series and equipment attributes such as Series Description and station name. Study and Series Instance UIDs can also be normalized or regenerated when a study identity needs to change.
Can tags be corrected automatically instead of by hand?add
Yes. Routing rules apply tag modifications as studies pass through, so a recurring problem is fixed once in the rule rather than repeatedly in the editor. RadMatch additionally normalizes free-text study descriptions to your own exam codes using machine learning.
Does editing tags break the study for the PACS?add
Not when identity is handled correctly, which is why the editor exposes UID normalization, merge, and split alongside plain tag edits. Changing an Accession or MRN on its own is safe; changing the Study Instance UID creates a distinct study, so the tool makes that an explicit choice rather than a side effect.
Is there an audit trail of tag changes?add
Yes. RadFuzion keeps a user audit trail recording who accessed and modified which exam, alongside the routing logs for the study itself. That record is separate from imaging retention so it survives normal data cleanup.
Can it de-identify studies as well as edit them?add
Yes. Anonymization profiles strip or replace patient identifiers for research, teaching, or vendor sharing, applied either on demand or automatically by routing rule.
Fix a study in the live preview
Open the demo to see tag editing, merge/split, and query/retrieve running against sample studies — no PHI, no signup.