(0028,0102)
High Bit
Keyword: HighBit
The most significant bit of each pixel sample. The current standard requires it to be one less than Bits Stored.
Tag Attributes
- Tag ID
- (0028,0102)
- Compact
- 00280102
- Keyword
- HighBit
- VR
- US — Unsigned Short
- VM
- 1
- Required
- Type 1 — required, with a value
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What High Bit contains
Identifies the most significant bit position within the allocated bits. Must equal Bits Stored − 1. Incorrect value causes systematically wrong pixel value display.
Group 0028 describes the pixel matrix and how stored pixel values are turned into displayed values.
Value format: US (Unsigned Short), VM 1
(0028,0102) HighBit has Value Representation US (Unsigned Short) and Value Multiplicity 1, which means exactly one value.
US — Unsigned Short
A 16-bit unsigned binary integer, from 0 to 65535.
- Length
- 2 bytes fixed
- Characters
- Binary. Byte order follows the transfer syntax.
Example value
11
Common values
| Value | Meaning |
|---|---|
| 7 | For 8-bit stored |
| 11 | For 12-bit stored (CT standard) |
| 15 | For 16-bit stored |
Where HighBit appears
| Defined in | Type | Meaning |
|---|---|---|
| Image Pixel ModulePS3.3 C.7.6.3 | 1 | Required, and it must have a value. |
A module lists the attributes an object must or may carry. Many IODs (CT Image, MR Image, Secondary Capture and others) include the same module, and an IOD-specific module can make an attribute stricter than the general one.
De-identification (PS3.15)
High Bit is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
To see how de-identification changes your own files, try the free DICOM Anonymizer, which runs in the browser and uploads nothing.
In archives and migrations
Image pixel attributes must stay consistent with the Pixel Data. If images are recompressed during a move (for example to JPEG 2000), the transfer syntax changes and some of these values can change with it, so a lossless copy is the only way to keep them byte-for-byte identical.
Common errors and how to fix them
Troubleshooting: If High Bit ≠ Bits Stored − 1, immediately flag as encoding defect. This causes all pixel values to be bit-shifted, producing wrong Hounsfield units in CT.
Check a file in seconds with the free DICOM Validator: it reads the header in your browser, lists the tags with their values, and flags missing or malformed key attributes.
High Bit: frequently asked questions
What is DICOM tag (0028,0102) High Bit?
The most significant bit of each pixel sample. The current standard requires it to be one less than Bits Stored.
What VR and VM does High Bit (0028,0102) have?
(0028,0102) HighBit has Value Representation US (Unsigned Short) and Value Multiplicity 1, which means exactly one value. A 16-bit unsigned binary integer, from 0 to 65535. Maximum length: 2 bytes fixed.
Is High Bit (0028,0102) required?
In the Image Pixel Module (PS3.3 C.7.6.3) it is Type 1: required, and it must have a value.
How is High Bit handled when de-identifying DICOM files?
High Bit is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
How do I troubleshoot High Bit (0028,0102)?
If High Bit ≠ Bits Stored − 1, immediately flag as encoding defect. This causes all pixel values to be bit-shifted, producing wrong Hounsfield units in CT.
Check HighBit in your files
The free DICOM Validator lists every header tag and flags problems. Files stay in your browser.
Open DICOM Validator →Remove patient data before sharing
The free DICOM Anonymizer applies a de-identification profile in your browser, with no upload.
Open DICOM Anonymizer →Sources
Checked against the DICOM standard, release 2026d. Module Types, query keys and de-identification actions come from these tables: