(0002,0013)
Implementation Version Name
Keyword: ImplementationVersionName
A short name for the implementation that wrote the file, usually including a version. Up to 16 characters.
Tag Attributes
- Tag ID
- (0002,0013)
- Compact
- 00020013
- Keyword
- ImplementationVersionName
- VR
- SH — Short String
- VM
- 1
- Required
- Type 3 — optional
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Implementation Version Name contains
Complement to Implementation Class UID. Use in audit trails and bug reports.
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: SH (Short String), VM 1
(0002,0013) ImplementationVersionName has Value Representation SH (Short String) and Value Multiplicity 1, which means exactly one value.
SH — Short String
A short character string. Leading and trailing spaces are not significant, and the backslash is not allowed.
- Length
- 16 characters maximum
- Characters
- The default character repertoire, or the one set by Specific Character Set (0008,0005).
Example value
EXAMPLE_TOOL_42
Format mistakes to avoid
- Values longer than 16 characters are invalid.
- A backslash inside the text splits it into two values.
Where ImplementationVersionName appears
| Defined in | Type | Meaning |
|---|---|---|
| File Meta InformationPS3.10 Table 7.1-1 | 3 | Optional. |
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 Version Name 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: Cross-reference with (0002,0012) for full implementation identification.
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 Version Name: frequently asked questions
What is DICOM tag (0002,0013) Implementation Version Name?
A short name for the implementation that wrote the file, usually including a version. Up to 16 characters.
What VR and VM does Implementation Version Name (0002,0013) have?
(0002,0013) ImplementationVersionName has Value Representation SH (Short String) and Value Multiplicity 1, which means exactly one value. A short character string. Leading and trailing spaces are not significant, and the backslash is not allowed. Maximum length: 16 characters maximum.
Is Implementation Version Name (0002,0013) required?
In the File Meta Information (PS3.10 Table 7.1-1) it is Type 3: optional.
How is Implementation Version Name handled when de-identifying DICOM files?
Implementation Version Name 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 Version Name (0002,0013)?
Cross-reference with (0002,0012) for full implementation identification.
Check ImplementationVersionName 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: