DICOM Attribute

Requested Procedure ID (0040,1001)

Keyword
RequestedProcedureID
VR
SH
VM
1

Attribute Metadata

Tag
(0040,1001)
Keyword
RequestedProcedureID
Name
Requested Procedure ID
Value Representation (VR)
SH
Value Multiplicity (VM)
1
Status
Active
Source
NEMA PS3.6 (table_6-1)

This attribute is part of the current DICOM Standard. Its value representation is SH with multiplicity 1.

This attribute uses the SH Value Representation. Multiplicity 1 governs how many values may be encoded.

Integration Notes

Real-world integration guidance for engineers implementing this attribute in Mirth Connect, FHIR gateways, HL7 v2 bridges, and cloud DICOM services. Authoritative source data where available; reference examples and operational notes where they add value.

FHIR Mapping

No direct FHIR ImagingStudy mapping published for this attribute. Some tags map indirectly via the Patient, Endpoint, or ImagingSelection resources — Phase 2b will expand coverage to those.

HL7 v2 Equivalent

  • IPC-1 or OBR-19 Accession Identifier (IHE RAD) or Placer Field 2
    ORMORU

    RequestedProcedureID is the IHE workflow's primary identifier of a requested procedure. IHE RAD-TF SWF profile uses IPC-1. Older interfaces overload OBR-19.

    Source: IHE RAD-TF Vol 2 §4.7

Verify against IHE Radiology TF Vol 2 and your facility's interface specification before production use.

Cloud DICOM Support

AWS HealthImaging, Azure DICOM, and GCP Healthcare DICOM coverage rolls out by attribute. The QIDO-RS matching keys + Patient/Study/Series core (~50 attributes) are documented; lower-traffic attributes will be added as Saga teams encounter them in production.

Real-World Sample Values

No representative sample value available — this attribute isn't present in the de-identified pydicom fixture set. Add a fixture covering this attribute to expand coverage.

Mirth Connect Example

Echo IHE RAD RequestedProcedureID through to Performed Procedure Step — IHE Scheduled Workflow expects the RequestedProcedureID (0040,1001) from the ord

IHE Scheduled Workflow expects the RequestedProcedureID (0040,1001) from the order to be echoed in the MPPS (0040,0253) when the procedure is performed.

// (0040,1001) Requested Procedure ID — echo through to outbound MPPS
var reqProcId = String(msg.dataset.attr.(@tag == '00401001').value).trim();
if (reqProcId) {
  channelMap.put('mpps_requested_procedure_id', reqProcId);
  // Also stash for OBR-19 mapping in HL7 v2 ORU
  tmp['OBR'][19] = reqProcId;
}

Reference only — validate before production. Snippets are starting points, not turnkey solutions. Always test against your channel's specific message structure and your facility's interface specification. See Mirth Connect User Guide + NEMA PS3.6 + your vendor conformance statement for authoritative specification.

Common Operational Errors

Operational error patterns for the most-queried tags will be added as coverage expands.

DICOM Integration Services

Saga IT builds production DICOM integrations across Mirth Connect, FHIR gateways, and cloud imaging platforms. If you're working with RequestedProcedureID or the broader (0040,1001) context: