(0010,0020)
Patient ID
Keyword: PatientID
The primary identifier of the patient, typically the medical record number used by the hospital that ordered the study.
Tag Attributes
- Tag ID
- (0010,0020)
- Compact
- 00100020
- Keyword
- PatientID
- VR
- LO — Long String
- VM
- 1
- Required
- Type 2 — required, may be empty
- PS3.15
- Basic Profile action Z/D
- Retired
- No
Defined in
What Patient ID contains
Patient ID is the patient's identifier in the organisation that ordered or produced the study, usually the hospital's medical record number. It is a Long String of up to 64 characters and Type 2 in the Patient Module: always present, but allowed to be empty.
In the Patient Root query model it is the Unique Key at patient level; in the Study Root model it is a Required Key at study level. Matching is exact and case-sensitive, so MRN00123 and 00123 are two different patients to a PACS.
A Patient ID is only unique within the organisation that issued it. When studies from several hospitals meet in one archive, Issuer of Patient ID (0010,0021), or a master patient index, is what keeps two different patients with the same number apart.
All patient matching between PACS, RIS and the EMR depends on it. Matching on LO values is case-sensitive and exact, so leading zeros, prefixes and case differences make two IDs for the same patient. The ID is only unique within the organisation that issued it, which Issuer of Patient ID (0010,0021) names.
Group 0010 holds information about the patient.
Value format: LO (Long String), VM 1
(0010,0020) PatientID has Value Representation LO (Long String) and Value Multiplicity 1, which means exactly one value.
LO — Long String
A character string that may be padded with leading or trailing spaces. The backslash is not allowed, because it separates values.
- Length
- 64 characters maximum
- Characters
- The default character repertoire, or the one set by Specific Character Set (0008,0005).
Example value
MRN00123456
Format mistakes to avoid
- A backslash inside the text splits it into two values.
- Accented or non-Latin characters need a matching Specific Character Set (0008,0005), or receivers decode them wrongly.
Where PatientID appears
| Defined in | Type | Meaning |
|---|---|---|
| Patient ModulePS3.3 C.7.1.1 | 2 | Required, but it may be empty (zero length) when the value is unknown. |
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.
In a C-FIND query using the Study Root Query/Retrieve Information Model, it is a STUDY-level key of type R: a Required Key: every Query/Retrieve SCP must support matching on it.
In the Patient Root model it is a PATIENT-level key of type U: a Unique Key: one value identifies a single entity at that level.
In a Modality Worklist query it is a matching key of type R (the worklist SCP must support matching on it) and a return key of type 1 (the SCP must return it with a value).
De-identification (PS3.15)
PS3.15 Table E.1-1 gives Patient ID the Basic Profile action Z/D: replace it with an empty value; if the IOD requires it to have a value, use a dummy value instead.
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
Patient attributes are the values most often changed after acquisition: corrections from the RIS or a master patient index, merges, and attribute coercion on receipt, which an archive lists in its DICOM conformance statement. Before a migration, decide which archive holds the correct demographics, because the same study with different patient values in two places looks like two patients.
Common errors and how to fix them
Duplicate patient records in the archive
The same person arrived with different IDs: leading zeros, prefixes, or a temporary ID from an emergency registration. Normalise IDs at the interfaces and merge records in the archive under a controlled procedure.
Two different patients share one ID
IDs from two issuers collide. Record Issuer of Patient ID (0010,0021) and include it in patient matching.
Empty Patient ID
Allowed by the standard (Type 2), but useless for matching. Use the Modality Worklist so the ID comes from the order instead of being typed at the device.
Troubleshooting: Duplicate patients in a PACS almost always trace back to Patient ID inconsistencies between feeding systems. Standardise the format at the interfaces, and record the issuer when one archive serves several organisations.
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 ID: frequently asked questions
What is DICOM tag (0010,0020) Patient ID?
The primary identifier of the patient, typically the medical record number used by the hospital that ordered the study. Patient ID is the patient's identifier in the organisation that ordered or produced the study, usually the hospital's medical record number. It is a Long String of up to 64 characters and Type 2 in the Patient Module: always present, but allowed to be empty.
What VR and VM does Patient ID (0010,0020) have?
(0010,0020) PatientID has Value Representation LO (Long String) and Value Multiplicity 1, which means exactly one value. A character string that may be padded with leading or trailing spaces. The backslash is not allowed, because it separates values. Maximum length: 64 characters maximum.
Is Patient ID (0010,0020) required?
In the Patient Module (PS3.3 C.7.1.1) it is Type 2: required, but it may be empty (zero length) when the value is unknown.
Can you query a PACS by Patient ID?
In a C-FIND query using the Study Root Query/Retrieve Information Model, it is a STUDY-level key of type R: a Required Key: every Query/Retrieve SCP must support matching on it. In the Patient Root model it is a PATIENT-level key of type U: a Unique Key: one value identifies a single entity at that level. In a Modality Worklist query it is a matching key of type R (the worklist SCP must support matching on it) and a return key of type 1 (the SCP must return it with a value).
How is Patient ID handled when de-identifying DICOM files?
PS3.15 Table E.1-1 gives Patient ID the Basic Profile action Z/D: replace it with an empty value; if the IOD requires it to have a value, use a dummy value instead.
How do I troubleshoot Patient ID (0010,0020)?
Duplicate patients in a PACS almost always trace back to Patient ID inconsistencies between feeding systems. Standardise the format at the interfaces, and record the issuer when one archive serves several organisations.
Is Patient ID unique in DICOM?
Only within the organisation that issued it. It is the Unique Key at patient level in the Patient Root query model, but two hospitals can use the same number for different people, which is why Issuer of Patient ID (0010,0021) exists.
Check PatientID 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: