

The DICOM Application Entity (AE) Title of the AE that wrote this file's content (or last updated it). It follows the same policies as defined by PS3.7 (association negotiation). Identifies a version for an Implementation Class UID (0002,0012) using up to 16 characters of the repertoire identified in Section 8.5. It provides an unambiguous identification of the type of implementation that last wrote the file in the event of interchange problems. Uniquely identifies the implementation that wrote this file and its content. JPIP Referenced Pixel Data Transfer Syntaxes are not used (see PS3.5). It is recommended to use one of the DICOM Transfer Syntaxes supporting explicit Value Representation encoding to facilitate interpretation of File Meta Element Values. Implementations reading Files with Meta Information where this attribute has bit 0 (lsb) of the second byte set to 1 may interpret the File Meta Information as specified in this version of PS3.10. In version 1 the first byte value is 00H and the second value byte value is 01H. This is a two byte field where each bit identifies a version of this File Meta Information header. Number of bytes following this File Meta Element (end of the Value field) up to and including the last File Meta Element of the Group 2 File Meta Information

This Prefix is intended to be used to recognize that this File is or not a DICOM File. If not used by an Application Profile or a specific implementation all bytes shall be set to 00H.įile-set Readers or Updaters shall not rely on the content of this Preamble to determine that this File is or is not a DICOM File.įour bytes containing the character string "DICM".

A fixed 128 byte field available for Application Profile or implementation specified use.
