DICOM File Meta Information

The first 132 bytes of a DICOM file are strictly structured for identification:

• File Preamble (128 bytes): A fixed-length field available for application-specific use, often zero-filled. It can be used to ensure compatibility with non-DICOM file viewers.
• DICOM Prefix (4 bytes): The literal ASCII characters 'D', 'I', 'C', 'M' (hex 44 49 43 4D). This magic number definitively identifies the file as a DICOM Part 10 format file.

If these 132 bytes are missing or corrupted, a parser must reject the file as non-conformant.

The Transfer Syntax UID (0002,0010) is the single most critical element in the File Meta Information. It defines the encoding rules for the entire subsequent data set:

• Byte Ordering: Little Endian vs. Big Endian.
• Compression: Explicit VR vs. Encapsulated formats like JPEG-LS Lossless (1.2.840.10008.1.2.4.80) or JPEG 2000 Lossless (1.2.840.10008.1.2.4.90).
• Implicit VR: The legacy Implicit VR Little Endian syntax (1.2.840.10008.1.2) must be parsed without VR fields.

A parser must read this UID before it can correctly unpack the pixel data and attributes that follow.

The Media Storage SOP Class UID (0002,0002) identifies the type of object stored in the file. This UID maps to a specific Information Object Definition (IOD):

• CT Image Storage: 1.2.840.10008.5.1.4.1.1.2
• MR Image Storage: 1.2.840.10008.5.1.4.1.1.4
• Secondary Capture Image Storage: 1.2.840.10008.5.1.4.1.1.7
• Encapsulated PDF Storage: 1.2.840.10008.5.1.4.1.1.104.1

This UID tells the receiving system which IOD template to use for validating the presence of mandatory modules like Patient and Study.

The SOP Instance UID (0008,0018) is a globally unique identifier for this specific image or data object. While technically part of the data set, it is often logged alongside the File Meta Information for indexing:

• Uniqueness: Must be globally unique across all systems and time, typically generated using a root UID assigned by an ISO-recognized registration authority.
• Format: A series of numeric components separated by periods (e.g., 1.2.840.113619.2.55.3.604688.943.12345).
• Conflict Resolution: If a PACS receives a file with a duplicate SOP Instance UID, it must reject the duplicate based on its storage commitment policy.

All elements in the File Meta Information belong to Group 0002 and follow strict encoding rules that differ from the main data set:

• Explicit VR Only: Group 0002 elements must always use Explicit Value Representation, even if the main data set uses Implicit VR.
• Little Endian Only: The byte ordering for Group 0002 is always Little Endian, regardless of the Transfer Syntax specified for the pixel data.
• Meta Element Length: The final element, (0002,0000) Group Length, signals the end of the meta header and the start of the raw data set.

This fixed encoding ensures that a parser can always read the critical identification parameters without needing prior knowledge of the file's internal encoding.

The Implementation Class UID (0002,0012) uniquely identifies the software implementation that wrote the file. This is crucial for debugging interoperability issues:

• Vendor Identification: Each vendor registers a unique UID to identify their specific software version.
• Implementation Version Name (0002,0013): An optional companion tag providing a human-readable label for the software version.
• Troubleshooting: If a file fails to parse correctly, the Implementation Class UID allows engineers to trace the bug back to a specific software release from a specific vendor.

This metadata is essential for maintaining a robust audit trail in a heterogeneous imaging environment.