DICOM Attribute

Imaging Service Request Comments (0040,2400)

Keyword
ImagingServiceRequestComments
VR
LT
VM
1

Attribute Metadata

Tag
(0040,2400)
Keyword
ImagingServiceRequestComments
Name
Imaging Service Request Comments
Value Representation (VR)
LT
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 LT with multiplicity 1.

This attribute uses the LT 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

  • NTE-3 Comment site-dependent
    ORM

    NTE segments concatenate into ImagingServiceRequestComments. Multiple NTEs join with newlines.

    Source: common convention

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

Append free-text NTE comments to ImagingServiceRequestComments — ORM messages with multiple NTE segments concatenate into ImagingServiceRequestCo

ORM messages with multiple NTE segments concatenate into ImagingServiceRequestComments — preserve order and source.

// (0040,2400) Imaging Service Request Comments — concatenate HL7 v2 NTE segments
var nteCount = msg['NTE'].length();
var comments = [];
for (var i = 0; i < nteCount; i++) {
  var c = String(msg['NTE'][i][3] || '').trim();
  if (c) comments.push(c);
}
if (comments.length > 0) {
  // DICOM LT max 10240 chars
  var combined = comments.join('\n').substring(0, 10240);
  channelMap.put('dicom_request_comments', combined);
}

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 ImagingServiceRequestComments or the broader (0040,2400) context: