(0028,0301)
Burned In Annotation
Keyword: BurnedInAnnotation
Indicates whether or not image contains sufficient burned in annotation to identify the patient and date.
Tag Attributes
- Tag ID
- (0028,0301)
- Compact
- 00280301
- Keyword
- BurnedInAnnotation
- VR
- CS — Code String
- VM
- 1
- Required
- Type 3 — optional
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Burned In Annotation contains
Burned In Annotation states whether the image pixels contain enough burned-in text to identify the patient and the date the image was acquired: YES or NO. Burned-in text is part of the picture itself, as on many ultrasound images, screen captures and scanned documents.
It is optional (Type 3) in the General Image Module, so its absence does not mean the image is clean. For de-identification, the safe reading is: YES means the pixels must be cleaned or the image left out; absent means unknown.
If YES, the image pixel data contains patient-identifying information burned into the pixel matrix — it cannot be removed by tag-stripping alone. Critical for de-identification workflows.
Group 0028 describes the pixel matrix and how stored pixel values are turned into displayed values.
Value format: CS (Code String), VM 1
(0028,0301) BurnedInAnnotation has Value Representation CS (Code String) and Value Multiplicity 1, which means exactly one value.
CS — Code String
A short code. Leading and trailing spaces are not significant. Codes are usually Defined Terms or Enumerated Values listed by the standard.
- Length
- 16 bytes maximum
- Characters
- Uppercase letters A–Z, digits 0–9, the space and the underscore.
Example value
NO
Format mistakes to avoid
- Lowercase letters, hyphens and other punctuation are not allowed, so ct or Head-Neck are invalid code strings.
- Values longer than 16 characters are invalid.
Common values
| Value | Meaning |
|---|---|
| YES | Patient information is burned into the pixel data |
| NO | No patient information in pixel data |
Where BurnedInAnnotation appears
| Defined in | Type | Meaning |
|---|---|---|
| General Image ModulePS3.3 C.7.6.1 | 3 | Optional. |
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)
Burned In Annotation is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it.
Table E.1-1 covers attributes, not pixels. When Burned In Annotation is YES, the pixel data itself contains identifying text, so the Clean Pixel Data Option of PS3.15 (or leaving the image out) is needed; removing attributes alone does not de-identify the image.
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: De-identification that only edits attributes does not remove text burned into the pixels. Treat YES, and also a missing value on ultrasound, screen captures and scanned documents, as a reason to inspect the pixels.
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.
Burned In Annotation: frequently asked questions
What is DICOM tag (0028,0301) Burned In Annotation?
Indicates whether or not image contains sufficient burned in annotation to identify the patient and date. Burned In Annotation states whether the image pixels contain enough burned-in text to identify the patient and the date the image was acquired: YES or NO. Burned-in text is part of the picture itself, as on many ultrasound images, screen captures and scanned documents.
What VR and VM does Burned In Annotation (0028,0301) have?
(0028,0301) BurnedInAnnotation has Value Representation CS (Code String) and Value Multiplicity 1, which means exactly one value. A short code. Leading and trailing spaces are not significant. Codes are usually Defined Terms or Enumerated Values listed by the standard. Maximum length: 16 bytes maximum.
Is Burned In Annotation (0028,0301) required?
In the General Image Module (PS3.3 C.7.6.1) it is Type 3: optional.
How is Burned In Annotation handled when de-identifying DICOM files?
Burned In Annotation is not listed in PS3.15 Table E.1-1, so the Basic Application Level Confidentiality Profile gives no specific action for it. Table E.1-1 covers attributes, not pixels. When Burned In Annotation is YES, the pixel data itself contains identifying text, so the Clean Pixel Data Option of PS3.15 (or leaving the image out) is needed; removing attributes alone does not de-identify the image.
How do I troubleshoot Burned In Annotation (0028,0301)?
De-identification that only edits attributes does not remove text burned into the pixels. Treat YES, and also a missing value on ultrasound, screen captures and scanned documents, as a reason to inspect the pixels.
Check BurnedInAnnotation 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: