(0010,0030)
Patient's Birth Date
Keyword: PatientBirthDate
Birth date of the patient. Format YYYYMMDD.
Tag Attributes
- Tag ID
- (0010,0030)
- Compact
- 00100030
- Keyword
- PatientBirthDate
- VR
- DA — Date
- VM
- 1
- Required
- Type 2 — required, may be empty
- PS3.15
- Basic Profile action Z
- Retired
- No
Defined in
What Patient's Birth Date contains
Patient's Birth Date is the patient's date of birth, as eight digits YYYYMMDD. It is Type 2 in the Patient Module, so it is always present but may be empty when unknown.
It is an Optional Key in C-FIND and Modality Worklist queries, so not every archive supports searching on it. Its main uses are confirming identity together with Patient ID and name, and computing the age.
The PS3.15 Basic Profile replaces it with an empty or dummy value (action Z). Research data sets that need ages keep Patient's Age (0010,1010) under the Retain Patient Characteristics Option rather than the birth date.
A secondary identifier used with Patient ID and name when reconciling patients, and the basis for age calculations in viewers. Type 2: it may be empty when unknown.
Group 0010 holds information about the patient.
Value format: DA (Date), VM 1
(0010,0030) PatientBirthDate has Value Representation DA (Date) and Value Multiplicity 1, which means exactly one value.
DA — Date
A calendar date in the format YYYYMMDD, for example 20240315 for 15 March 2024.
- Length
- 8 bytes fixed
- Characters
- The digits 0–9. In a query (C-FIND) a range such as 20240101-20240131 is also allowed.
Example value
19800214
Format mistakes to avoid
- Separators are not allowed: 2024-03-15, 2024.03.15 and 15/03/2024 are all invalid.
- Placeholder dates such as 19000101 are valid dates, so validators do not flag them; check them against the source system.
Where PatientBirthDate 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 O: an Optional Key: an SCP may or may not support matching on it, so check its conformance statement.
In the Patient Root model it is a PATIENT-level key of type O: an Optional Key: an SCP may or may not support matching on it, so check its conformance statement.
In a Modality Worklist query it is a matching key of type O (matching on it is optional for the worklist SCP) and a return key of type 2 (the SCP must return it, possibly empty).
De-identification (PS3.15)
PS3.15 Table E.1-1 gives Patient's Birth Date the Basic Profile action Z: replace it with an empty value, or with a dummy value consistent with the VR.
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
Troubleshooting: An empty birth date is allowed and usually means the order carried none. A placeholder such as 19000101 is a valid date and will be treated as real by age calculations, so look for it explicitly when checking data quality.
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's Birth Date: frequently asked questions
What is DICOM tag (0010,0030) Patient's Birth Date?
Birth date of the patient. Format YYYYMMDD. Patient's Birth Date is the patient's date of birth, as eight digits YYYYMMDD. It is Type 2 in the Patient Module, so it is always present but may be empty when unknown.
What VR and VM does Patient's Birth Date (0010,0030) have?
(0010,0030) PatientBirthDate has Value Representation DA (Date) and Value Multiplicity 1, which means exactly one value. A calendar date in the format YYYYMMDD, for example 20240315 for 15 March 2024. Maximum length: 8 bytes fixed.
Is Patient's Birth Date (0010,0030) 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's Birth Date?
In a C-FIND query using the Study Root Query/Retrieve Information Model, it is a STUDY-level key of type O: an Optional Key: an SCP may or may not support matching on it, so check its conformance statement. In the Patient Root model it is a PATIENT-level key of type O: an Optional Key: an SCP may or may not support matching on it, so check its conformance statement. In a Modality Worklist query it is a matching key of type O (matching on it is optional for the worklist SCP) and a return key of type 2 (the SCP must return it, possibly empty).
How is Patient's Birth Date handled when de-identifying DICOM files?
PS3.15 Table E.1-1 gives Patient's Birth Date the Basic Profile action Z: replace it with an empty value, or with a dummy value consistent with the VR.
How do I troubleshoot Patient's Birth Date (0010,0030)?
An empty birth date is allowed and usually means the order carried none. A placeholder such as 19000101 is a valid date and will be treated as real by age calculations, so look for it explicitly when checking data quality.
Check PatientBirthDate 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: