MajwareMAJWARE
File Meta

(0002,0012)

Implementation Class UID

Keyword: ImplementationClassUID

Uniquely identifies the implementation (the software) that wrote the file. Each implementation uses a UID under its own organisation root.

Tag Attributes

Tag ID
(0002,0012)
Compact
00020012
Keyword
ImplementationClassUID
VR
UI — Unique Identifier (UID)
VM
1
Required
Type 1 — required, with a value
PS3.15
Not listed in PS3.15 Table E.1-1
Retired
No

Defined in

File Meta Information

What Implementation Class UID contains

Useful for debugging — identifies which software version or vendor created the file. Log this when investigating encoding bugs.

Group 0002 is the File Meta Information defined in PS3.10. It sits at the start of every DICOM file, is always encoded in Explicit VR Little Endian, and is not part of the data set that is sent over the network.

Value format: UI (Unique Identifier (UID)), VM 1

(0002,0012) ImplementationClassUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value.

UI — Unique Identifier (UID)

A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte.

Length
64 bytes maximum
Characters
The digits 0–9 and the period.

Example value

2.25.98327190538312767519483301623452168001

Format mistakes to avoid

  • A component may not start with a zero unless it is the single digit 0, so 1.2.03 is invalid.
  • Letters, spaces and values longer than 64 bytes are invalid.

Where ImplementationClassUID appears

Defined inTypeMeaning
File Meta InformationPS3.10 Table 7.1-11Required, and it must have a value.

A module lists the attributes an object must or may carry. Many IODs (CT Image, MR Image, Secondary Capture and others) include the same module, and an IOD-specific module can make an attribute stricter than the general one.

De-identification (PS3.15)

Implementation Class UID is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.

To see how de-identification changes your own files, try the free DICOM Anonymizer, which runs in the browser and uploads nothing.

In archives and migrations

Group 0002 belongs to the file, not to the data set. A C-STORE sends only the data set, and the receiving system writes its own File Meta header when it saves the object. After a transfer, the File Meta values describe the system that wrote the copy you are looking at, which is not necessarily the system that created the image.

Common errors and how to fix them

Troubleshooting: Use this tag to identify the originating system when reporting encoding defects to vendors.

Check a file in seconds with the free DICOM Validator: it reads the header in your browser, lists the tags with their values, and flags missing or malformed key attributes.

Implementation Class UID: frequently asked questions

What is DICOM tag (0002,0012) Implementation Class UID?

Uniquely identifies the implementation (the software) that wrote the file. Each implementation uses a UID under its own organisation root.

What VR and VM does Implementation Class UID (0002,0012) have?

(0002,0012) ImplementationClassUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value. A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte. Maximum length: 64 bytes maximum.

Is Implementation Class UID (0002,0012) required?

In the File Meta Information (PS3.10 Table 7.1-1) it is Type 1: required, and it must have a value.

How is Implementation Class UID handled when de-identifying DICOM files?

Implementation Class UID is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.

How do I troubleshoot Implementation Class UID (0002,0012)?

Use this tag to identify the originating system when reporting encoding defects to vendors.

Check ImplementationClassUID in your files

The free DICOM Validator lists every header tag and flags problems. Files stay in your browser.

Open DICOM Validator →

Remove patient data before sharing

The free DICOM Anonymizer applies a de-identification profile in your browser, with no upload.

Open DICOM Anonymizer →

Sources

Checked against the DICOM standard, release 2026d. Module Types, query keys and de-identification actions come from these tables:

More File Meta tags