MajwareMAJWARE
Study

(0032,1060)

Requested Procedure Description

Keyword: RequestedProcedureDescription

Institution-generated description or classification of the Requested Procedure.

Tag Attributes

Tag ID
(0032,1060)
Compact
00321060
Keyword
RequestedProcedureDescription
VR
LO — Long String
VM
1
Required
Type 3 — optional
PS3.15
Basic Profile action X/Z
Retired
No

Defined in

Modality WorklistRequest Attributes Macro

What Requested Procedure Description contains

The order description that comes from the RIS through the Modality Worklist. A worklist SCP must return it or Requested Procedure Code Sequence (0032,1064). Modalities often copy it into Study Description (0008,1030).

Group 0032 holds study and request information.

Value format: LO (Long String), VM 1

(0032,1060) RequestedProcedureDescription 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

CT CHEST WITH CONTRAST

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 RequestedProcedureDescription appears

Defined inTypeMeaning
Request Attributes MacroPS3.3 Table 10-9, inside Request Attributes Sequence (0040,0275)3Optional.

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 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 1C (the SCP must return it with a value when its condition applies).

De-identification (PS3.15)

PS3.15 Table E.1-1 gives Requested Procedure Description the Basic Profile action X/Z: remove it; if the IOD requires the attribute to be present, keep it with an empty or dummy value instead.

With the Clean Descriptors Option, the action is C: clean it: replace values with similar values that carry no identifying information.

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

Study-level attributes are what people search on, so a migration should keep them identical. When the same study exists in two archives with different study-level values, users see two studies, or none, depending on which values they search for.

Common errors and how to fix them

Troubleshooting: If the description is missing on the modality, check the worklist response: when the RIS sends only the coded Requested Procedure Code Sequence, the text field can be empty.

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.

Requested Procedure Description: frequently asked questions

What is DICOM tag (0032,1060) Requested Procedure Description?

Institution-generated description or classification of the Requested Procedure.

What VR and VM does Requested Procedure Description (0032,1060) have?

(0032,1060) RequestedProcedureDescription 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 Requested Procedure Description (0032,1060) required?

In the Request Attributes Macro (PS3.3 Table 10-9, inside Request Attributes Sequence (0040,0275)) it is Type 3: optional.

How is Requested Procedure Description used in a Modality Worklist query?

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 1C (the SCP must return it with a value when its condition applies).

How is Requested Procedure Description handled when de-identifying DICOM files?

PS3.15 Table E.1-1 gives Requested Procedure Description the Basic Profile action X/Z: remove it; if the IOD requires the attribute to be present, keep it with an empty or dummy value instead. With the Clean Descriptors Option, the action is C: clean it: replace values with similar values that carry no identifying information.

How do I troubleshoot Requested Procedure Description (0032,1060)?

If the description is missing on the modality, check the worklist response: when the RIS sends only the coded Requested Procedure Code Sequence, the text field can be empty.

Check RequestedProcedureDescription 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:

More Study tags