Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
DICOM Default Transfer Syntax (DICOM Standard PS3.5-2011, 10.1)
64 views
Skip to first unread message
Shinichi Boman
Apr 30, 2012, 1:28:06 PM4/30/12
to
According to Section 10.1 of PS3.5-2011 Standard on page 63, it
explains that “DICOM default Transfer Syntax requirements, a) and b),
are waived when the Application Entity sending the pixel data has only
access to the pixel data in Lossy compressed form and a Transfer
Syntax that uses a pixel data reference is not offered”. It also
explains that “Every sending AE is required to be able to convert any
dataset it is going to transmit into the default Transfer Syntax,
regardless of the form in which it originally received or stored the
data set, except in the single case of when it received it in a Lossy
compression form. In that exceptional case, the sending AE is
permitted to propose only the Lossy compressed Transfer Syntax
appropriate to the Lossy form that was received” (this statement is
the last NOTE at the bottom of page 63).
Does this means that AE (in this case the modality) is not required to
offer DICOM Implicit VR Little Endian but can just offer JPEG Lossy
(1.2.840.10008.1.2.4.50) if the AE (modality) creates an image using
DICOM Lossy? If this is true then shouldn’t all PACS be able to
support JPEG Lossy (1.2.840.10008.1.2.4.50) in addition to the default
Implicit VR Little Endian?
Thank you in advance for your feedback.
explains that “DICOM default Transfer Syntax requirements, a) and b),
are waived when the Application Entity sending the pixel data has only
access to the pixel data in Lossy compressed form and a Transfer
Syntax that uses a pixel data reference is not offered”. It also
explains that “Every sending AE is required to be able to convert any
dataset it is going to transmit into the default Transfer Syntax,
regardless of the form in which it originally received or stored the
data set, except in the single case of when it received it in a Lossy
compression form. In that exceptional case, the sending AE is
permitted to propose only the Lossy compressed Transfer Syntax
appropriate to the Lossy form that was received” (this statement is
the last NOTE at the bottom of page 63).
Does this means that AE (in this case the modality) is not required to
offer DICOM Implicit VR Little Endian but can just offer JPEG Lossy
(1.2.840.10008.1.2.4.50) if the AE (modality) creates an image using
DICOM Lossy? If this is true then shouldn’t all PACS be able to
support JPEG Lossy (1.2.840.10008.1.2.4.50) in addition to the default
Implicit VR Little Endian?
Thank you in advance for your feedback.
David Clunie
Apr 30, 2012, 6:30:53 PM4/30/12
to
On 4/30/12 1:28 PM, Shinichi Boman wrote:
> Does this means that AE (in this case the modality) is not required to
> offer DICOM Implicit VR Little Endian but can just offer JPEG Lossy
> (1.2.840.10008.1.2.4.50) if the AE (modality) creates an image using
> DICOM Lossy?
Yes, that's exactly what it means.
> Does this means that AE (in this case the modality) is not required to
> offer DICOM Implicit VR Little Endian but can just offer JPEG Lossy
> (1.2.840.10008.1.2.4.50) if the AE (modality) creates an image using
> DICOM Lossy?
> If this is true then shouldn’t all PACS be able to
> support JPEG Lossy (1.2.840.10008.1.2.4.50) in addition to the default
> Implicit VR Little Endian?
of input.
That said, it is nice it it does, especially for modalities that use
lossy compression a lot, like US and VL modality images.
Also, this is not limited to just JPEG ... a modality might created
irreversible JPEG 2000 images, for example, and the same rule would
apply, yet not all PACS support JPEG 2000 (though again, it is nice
if they do).
David
0 new messages