DICOM private tags: what they are and how to handle them
- DICOM private tags live in odd-numbered groups and store proprietary vendor acquisition and calibration metadata.
- A private creator string reserves a 256-element block within an odd group to prevent vendor tag collisions.
- Software should look up private elements by pairing the group number with the creator string, not hardcoded tags.
- Explicit VR preserves private tag data types, while Implicit VR can default unknown tags to Unknown (UN).
- The basic de-identification profile strips private tags by default because vendors may embed PHI in them.
DICOM private tags are non-standard data elements stored in odd-numbered groups that scanner vendors use to record proprietary acquisition, calibration, and processing metadata. Standard tags have entries in the public data dictionary. Private tags require a private creator reservation in the group header to claim an element block and prevent naming collisions between different manufacturers.
Imaging software often depends on these proprietary fields. If you build computer vision models, cloud archives, or specialized viewing platforms, you will encounter private tags across CT, MRI, and ultrasound exams. Knowing how DICOM reserves private elements keeps your parsers stable across scanner updates. It also prevents accidental leaks of patient data during export.
What are DICOM private tags?
A DICOM private tag is any data element whose group number is an odd hexadecimal integer, such as group 0019, 0029, or 7001. The DICOM standard (PS3.5 Section 7.1) splits all data element tags into two distinct categories based on their group number:
- Standard data elements: Have even group numbers, such as
(0010,0010)for Patient Name or(0020,000D)for Study Instance UID. Their definitions, data types, and names are globally standardized in Part 6 of the standard. Even groups0000,0002,0004, and0006are reserved for network commands and file headers. - Private data elements: Have odd group numbers greater than
0008. The standard reserves odd groups0001,0003,0005,0007, andFFFF, but leaves all other odd groups open for equipment manufacturers.
Equipment makers introduce private tags when their hardware generates clinical parameters that do not exist in the public DICOM dictionary. Standardizing a new public tag through the DICOM Standards Committee takes months or years. Private tags give manufacturers an immediate place to store proprietary calibration data, custom filter settings, and raw sensor readings.
How does private creator reservation work?
Private creator reservation assigns a 256-element block within an odd group to a specific vendor by recording an identifier string in elements (gggg,0010) through (gggg,00FF). This mechanism prevents tag collisions when two different vendors write private elements into the same odd group.
Section 7.8 of DICOM PS3.5 defines the reservation rules:
- The creator element: To claim a block, the sender writes an identification code into an unassigned element between
0010and00FF. The Value Representation (VR) of this creator element must beLO(Long String), and its Value Multiplicity must be 1. Typical creator strings include values like"SIEMENS CT VA0 COI","GEMS_ACQU_01", or"ELSCINT1". - The reserved block: Writing a creator string into slot
(gggg,00xx)reserves the entire element range(gggg,xx00)through(gggg,xxFF). - Capacity: A single odd group can hold up to 240 independent creator blocks, running from slot
0x10through0xFF.
For example, if GE places the creator string "GEMS_ACQU_01" in tag (0019,0010), GE owns elements (0019,1000) through (0019,10FF). If a hospital PACS later appends its own metadata to the same group using slot (0019,0011), the PACS owns elements (0019,1100) through (0019,11FF). Neither system overwrites the other.
Why do imaging products need private tags?
Clinical imaging products often rely on private tags because advanced scanner parameters appear in vendor tags years before standard committees adopt them. If you build clinical viewing software or machine learning models, public attributes alone may not give you the full acquisition context.
Three common clinical use cases depend directly on private attributes:
- Diffusion MRI parameters: Modern diffusion tensor imaging requires diffusion b-values and gradient direction vectors. In classic single-frame MR images, Siemens stores diffusion b-values in tag
(0019,100C)under creator"SIEMENS MR HEADER". GE stores them in tag(0043,1039)under"GEMS_PARM_01". Without these values, neural networks cannot calculate apparent diffusion coefficient maps. - CT scanner geometry: Advanced 3D volume reconstruction often requires gantry tilt angles, dual-energy ratios, and proprietary convolution kernels stored solely in private groups.
- Radiotherapy planning: Proprietary multileaf collimator positions and treatment machine calibration offsets often travel inside vendor-specific private sequences.
When your application processes DICOM pixel metadata for machine learning, you may need these private attributes to normalize image matrices accurately across scanner fleets.
How should your code look up private elements safely?
Software should always look up private elements by pairing the group number with the private creator string, rather than hardcoding static tag numbers. Hardcoding raw tags like (0019,1010) is one of the most common bugs in DICOM integration pipelines.
When a scanner writes a private element, it can place its creator string in any free slot between 0010 and 00FF. On a Siemens scanner, "SIEMENS CT VA0 COI" might claim slot 0010, placing your target slice angle at (0019,1010). But if an intermediary archive or router injects its own private creator into slot 0010 first, Siemens shifts to slot 0011. Your target attribute now sits at (0019,1110). If your code reads (0019,1010), it reads the wrong vendor’s data or crashes with a missing key.
Modern DICOM libraries provide creator-aware lookups:
- In Python’s
pydicom, calldataset.get_private_item(0x0019, 0x10, "SIEMENS CT VA0 COI"). - In C++ with DCMTK, call
DcmItem::findAndGet...with the creator identifier string. - In Java with dcm4che, query attributes using the group, element offset, and creator ID.
Encoding rules also affect private element stability. With Explicit VR vs Implicit VR encoding, Explicit VR keeps the sender’s data type without a local dictionary. Implicit VR defaults unknown tags to UN (Unknown), forcing you to parse raw byte buffers manually.
When you ingest studies from hospital senders, your connectivity layer must deliver raw DICOM objects without dropping or mutating private attributes. Hosting an internet-facing DICOM listener yourself means maintaining DIMSE associations, scanner transfer syntaxes, and hospital TLS certificates. A managed gateway such as Dicomly terminates the mTLS C-STORE connection at the edge. It streams the complete DICOM payload to your application over HTTPS POST (using DICOMweb STOW-RS). Your webhook receives the full dataset with all private tags preserved, and no patient data stays at rest. You pay a monthly fee and trade raw socket control for zero listener operations.
Why do private tags create privacy risks during de-identification?
Private tags pose a serious data privacy risk because equipment vendors frequently place unprotected patient identifiers and operator notes inside proprietary attributes. When you export imaging data for clinical trials or AI training datasets, uncleaned private tags can leak protected health information (PHI).
Technicians often enter internal medical record numbers or patient names into free-text scanner fields. Scanners frequently replicate those strings into private acquisition comments or custom protocol headers.
DICOM PS3.15 Annex E defines the standard de-identification profile for medical imaging. The standard rule for private attributes is simple:
- Strip by default: The basic confidentiality profile assigns action code
X(remove) to all private data elements. Unless you audit a tag, you must delete all odd groups before sharing data outside your security perimeter. - Selective retention: If your machine learning model requires specific acquisition parameters, such as diffusion b-values, you must configure a private tag allowlist.
- Creator validation: Never allowlist by tag number alone. Only retain an element when both the tag offset and the private creator string match your audited specification.
- Data type auditing: Inspect the Value Representation. Retain numbers and short enumerated codes (
IS,DS,CS). Reject free-text strings (LT,UT,ST,LO) unless you run an automated redaction pass.
For practical workflows on generating and cleaning test data without leaking sensitive patient attributes, read our guide on de-identification under PS3.15.
How to inspect private tags in your test lab
You can inspect private creator reservations and data elements directly using command-line tools like DCMTK’s dcmdump. Running a dump command reveals the reservation slots and the data elements assigned to each vendor.
To view private creator tags in group 0019, run:
dcmdump +P 0019,0010 +P 0019,1010 image.dcm
The output displays the creator tag, the LO Value Representation, and the creator string in brackets:
(0019,0010) LO [SIEMENS CT VA0 COI] # 20, 1 PrivateCreator
(0019,1010) CS [HEAD] # 4, 1 PrivateTag
Take a sample DICOM file from your target modality and run dcmdump on its odd groups. Note the exact creator strings and data types your downstream model needs. Building an explicit creator allowlist today protects your processing pipeline from parsing bugs and keeps your patient data secure.
Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →