(0020,1041)
Slice Location
Keyword: SliceLocation
Relative position of the image plane, in mm. The standard leaves the reference point to the implementation, so values from different series or devices cannot be compared.
Tag Attributes
- Tag ID
- (0020,1041)
- Compact
- 00201041
- Keyword
- SliceLocation
- VR
- DS — Decimal String
- VM
- 1
- Required
- Type 3 — optional
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Slice Location contains
A convenient scalar for display and simple sorting within a series. For any geometric work, use Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037).
Group 0020 holds the identifiers and numbers that tie instances into series and studies, and the geometry of the patient coordinate system.
Value format: DS (Decimal String), VM 1
(0020,1041) SliceLocation has Value Representation DS (Decimal String) and Value Multiplicity 1, which means exactly one value.
DS — Decimal String
A fixed-point or floating-point number written as text, for example 0.5, -1024 or 1.2E-3. Leading and trailing spaces are allowed.
- Length
- 16 bytes maximum
- Characters
- The digits 0–9, +, -, E, e, the period and the space.
Example value
-312.250
Format mistakes to avoid
- Writing a number at full floating-point precision can exceed 16 characters, which is invalid.
- A comma as decimal separator (0,5) is invalid; DICOM always uses the period.
Where SliceLocation appears
| Defined in | Type | Meaning |
|---|---|---|
| Image Plane ModulePS3.3 C.7.6.2 | 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)
Slice Location 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 geometry attributes are copied unchanged in a migration. Viewers rebuild 3D volumes, MPR and measurements from them, so a changed value changes the clinical picture.
Common errors and how to fix them
Troubleshooting: Do not use Slice Location to compute slice spacing or to register series: its origin is undefined. Use Image Position (Patient) instead.
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.
Slice Location: frequently asked questions
What is DICOM tag (0020,1041) Slice Location?
Relative position of the image plane, in mm. The standard leaves the reference point to the implementation, so values from different series or devices cannot be compared.
What VR and VM does Slice Location (0020,1041) have?
(0020,1041) SliceLocation has Value Representation DS (Decimal String) and Value Multiplicity 1, which means exactly one value. A fixed-point or floating-point number written as text, for example 0.5, -1024 or 1.2E-3. Leading and trailing spaces are allowed. Maximum length: 16 bytes maximum.
Is Slice Location (0020,1041) required?
In the Image Plane Module (PS3.3 C.7.6.2) it is Type 3: optional.
How is Slice Location handled when de-identifying DICOM files?
Slice Location 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 Slice Location (0020,1041)?
Do not use Slice Location to compute slice spacing or to register series: its origin is undefined. Use Image Position (Patient) instead.
Check SliceLocation 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: