Does the whole DICOM file have only one hyphenation syntax?
Sorry if this is pretty simple, I am new to DICOM. I know that the DICOM file has several parts like Patient, Study, Series and Instance (Image).
Now, in order to communicate with a device, it needs a transfer syntax that communicates the communication method, such as Little-Endian, Big-Endian, JPEG-Lossless, lossy, etc.
So, does each of the parts of the DICOM file (Patient, Study, Series, and Instance (Image)) have a different hyphenation syntax? How the patient can communicate like Little-Endian, the study can use JPEG-Lossless or MPEG-4 (if it's a video), etc.
OR the entire DICOM file uses only one hyphenation syntax.
source to share
Single transfer syntax is used throughout the complete DICOM file (except for the first group with ID = 0002, which is written with low or trailing core transfer syntax)
When sending DICOM messages over the network, you can have a different transfer syntax for each message: there you can define different Context Contexts during association negotiation, and each Content Context can have a different Transfer Syntax.
Once the association has been negotiated, you can transmit messages with different transfer syntaxes by choosing an appropriate context / presentation transfer ID in the message header
source to share
It is not clear in your question how DICOM is organized.
DICOM is composed of various SOP classes. The SOP class is a service pair object. Examples of services are the storage service class (a service for storing messages over the network (usually modal images) or the Media Service Class (for writing files to media or simply saving them to disk).
The SOP object part is defined in the IOD (Information Object Definition). IODs are defined by multiple modules. Modules, in turn, are composed of DICOM tags. Each module usually groups tags together and is usually associated with an "Entity" in the DICOM model. The module can be linked to patient level, batch or DICOM image model. The IOD consists of all the tags defined in the various modules. When encoding IODs, the context of the module in which the tags are defined is irrelevant.
The DICOM service defines how tags in IOD are encoded. Both the DICOM message for network services (in its 0x0000 group members) and the media DICOM file (in its 0x0002 groups) contain metadata that describes the encoding and dataset that contains the IOD tags. Group 0x0000 elements in a DICOM message are always encoded in Implicit VR Little Endian, and group 0x0002 elements in a DICOM file are always encoded in Explicit VR Little Endian transfer syntax. Data sets are always encoded in the same transfer syntax.
Hope this helps a little.
source to share