MajwareMAJWARE
File Meta

(0002,0016)

Source Application Entity Title

Keyword: SourceApplicationEntityTitle

The AE Title of the application entity that wrote this file, or last updated its content.

Tag Attributes

Tag ID
(0002,0016)
Compact
00020016
Keyword
SourceApplicationEntityTitle
VR
AE — Application Entity
VM
1
Required
Type 3 — optional
PS3.15
Not listed in PS3.15 Table E.1-1
Retired
No

Defined in

File Meta Information

What Source Application Entity Title contains

Useful for tracing the originating modality AE Title in multi-system environments.

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: AE (Application Entity), VM 1

(0002,0016) SourceApplicationEntityTitle has Value Representation AE (Application Entity) and Value Multiplicity 1, which means exactly one value.

AE — Application Entity

A name that identifies a DICOM application (an AE Title). Leading and trailing spaces are not significant, and a value made only of spaces is not allowed.

Length
16 bytes maximum
Characters
Default character repertoire, without the backslash and without control characters.

Example value

CT_SCANNER_01

Format mistakes to avoid

  • A value longer than 16 characters is invalid.
  • AE Titles are compared as exact strings, so a difference in upper or lower case makes a different AE Title.

Where SourceApplicationEntityTitle appears

Defined inTypeMeaning
File Meta InformationPS3.10 Table 7.1-13Optional.

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)

Source Application Entity Title 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: If files arrive from an unexpected source, compare this value with the AE Titles configured on the sending devices. It is optional, so its absence proves nothing.

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.

Source Application Entity Title: frequently asked questions

What is DICOM tag (0002,0016) Source Application Entity Title?

The AE Title of the application entity that wrote this file, or last updated its content.

What VR and VM does Source Application Entity Title (0002,0016) have?

(0002,0016) SourceApplicationEntityTitle has Value Representation AE (Application Entity) and Value Multiplicity 1, which means exactly one value. A name that identifies a DICOM application (an AE Title). Leading and trailing spaces are not significant, and a value made only of spaces is not allowed. Maximum length: 16 bytes maximum.

Is Source Application Entity Title (0002,0016) required?

In the File Meta Information (PS3.10 Table 7.1-1) it is Type 3: optional.

How is Source Application Entity Title handled when de-identifying DICOM files?

Source Application Entity Title 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 Source Application Entity Title (0002,0016)?

If files arrive from an unexpected source, compare this value with the AE Titles configured on the sending devices. It is optional, so its absence proves nothing.

Check SourceApplicationEntityTitle 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