(0018,5100)
Patient Position
Keyword: PatientPosition
How the patient lay relative to the imaging equipment: which end entered first (head or feet) and whether the patient was supine, prone or on the side.
Tag Attributes
- Tag ID
- (0018,5100)
- Compact
- 00185100
- Keyword
- PatientPosition
- VR
- CS — Code String
- VM
- 1
- Required
- Type 2C — required when a condition applies, may be empty
- PS3.15
- Not listed in PS3.15 Table E.1-1
- Retired
- No
Defined in
What Patient Position contains
Patient Position describes how the patient lies relative to the equipment: which end enters the gantry or magnet first and the posture (supine, prone, decubitus right or left). It is a code string such as HFS for head first, supine.
It is Type 2C in the General Series Module: required for CT and MR images unless Patient Orientation Code Sequence (0054,0410) is sent instead. The operator selects it at the console, and the scanner uses it to place the images in the patient coordinate system.
Orientation labels and 3D geometry come from Image Orientation (Patient) and Image Position (Patient), not from this attribute. Patient Position records what the operator selected, which is why a wrong selection produces consistently wrong geometry rather than just a wrong label.
It is entered by the operator, and the scanner uses it to compute Image Orientation (Patient) and Image Position (Patient). Viewers take orientation labels from those two attributes, not from Patient Position.
Group 0018 holds acquisition information: how the data were acquired and with which settings.
Value format: CS (Code String), VM 1
(0018,5100) PatientPosition 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
HFS
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 |
|---|---|
| HFS | Head First-Supine |
| HFP | Head First-Prone |
| FFS | Feet First-Supine |
| FFP | Feet First-Prone |
| HFDR | Head First-Decubitus Right |
| HFDL | Head First-Decubitus Left |
| FFDR | Feet First-Decubitus Right |
| FFDL | Feet First-Decubitus Left |
Where PatientPosition appears
| Defined in | Type | Meaning |
|---|---|---|
| General Series ModulePS3.3 C.7.3.1 | 2C | Required, possibly empty, when its condition applies.Required for CT and MR images (including Enhanced CT, Enhanced MR, Enhanced Color MR and MR Spectroscopy) when Patient Orientation Code Sequence (0054,0410) is not present. |
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)
Patient Position 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
Acquisition parameters describe what happened at the scanner and should never change after the fact. A migration copies them as they are; a difference between the source and the copy points to a fault in the transfer, not to a correction.
Common errors and how to fix them
Troubleshooting: When left and right or head and feet are swapped on CT or MR images, the usual cause is a wrong position selected at the console before the scan: the scanner computed the patient coordinates from it. Correcting Patient Position afterwards does not fix the geometry.
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.
Patient Position: frequently asked questions
What is DICOM tag (0018,5100) Patient Position?
How the patient lay relative to the imaging equipment: which end entered first (head or feet) and whether the patient was supine, prone or on the side. Patient Position describes how the patient lies relative to the equipment: which end enters the gantry or magnet first and the posture (supine, prone, decubitus right or left). It is a code string such as HFS for head first, supine.
What VR and VM does Patient Position (0018,5100) have?
(0018,5100) PatientPosition 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 Patient Position (0018,5100) required?
In the General Series Module (PS3.3 C.7.3.1) it is Type 2C: required, possibly empty, when its condition applies. Required for CT and MR images (including Enhanced CT, Enhanced MR, Enhanced Color MR and MR Spectroscopy) when Patient Orientation Code Sequence (0054,0410) is not present.
How is Patient Position handled when de-identifying DICOM files?
Patient Position 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 Patient Position (0018,5100)?
When left and right or head and feet are swapped on CT or MR images, the usual cause is a wrong position selected at the console before the scan: the scanner computed the patient coordinates from it. Correcting Patient Position afterwards does not fix the geometry.
Check PatientPosition 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: