Is it always ok to use OW as the VR PixelData for every transfer syntax?
Reading DICOM PS3.5 2020d - Data Structures and Encoding:
A.1 DICOM Implicit VR Little Endian Transfer Syntax
A.2 DICOM Little Endian Transfer Syntax (Explicit VR)
A.4 Transfer Syntaxes For Encapsulation of Encoded Pixel Data
To me it seems so, but for encapsulated TS, where:
"Pixel Data (7FE0,0010) may be encapsulated or native. (...) If encapsulated, it has the Value Representation OB".
But with various tools, when I compress an image using an encapsulated TS (e.g. JPEG Lossless), I see that the PixelData VR is OW.
What am I missing?
It is required to be OB. There was a bug in GDCM (and possibly derivatives) but it has been fixed in latest versions. Which tool(s)/version(s) were you using ?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 185 |
Nodes: | 16 (1 / 15) |
Uptime: | 135:36:55 |
Calls: | 3,758 |
Calls today: | 2 |
Files: | 11,180 |
Messages: | 3,469,426 |