DICOM Attribute

Rows (0028,0010)

Keyword
Rows
VR
US
VM
1

Definition

Number of rows in the image.

From NEMA PS3.3 §C.7.6.24.

Attribute Metadata

Tag
(0028,0010)
Keyword
Rows
Name
Rows
Value Representation (VR)
US
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 US with multiplicity 1.

Used in 9 Modules

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

No standard HL7 v2 equivalent published for this attribute. Imaging-only attributes (Image Pixel data, technical acquisition parameters, modality-specific values) typically have no HL7 v2 carrier.

Cloud DICOM Support

  • AWS HealthImaging Preserved
  • Azure DICOM Preserved
  • Google Cloud Healthcare Preserved

Rows — required for valid pixel data interpretation; preserved by all three. AWS HealthImaging exposes it as ImageFrame metadata.

Per-vendor source URLs and verification date in src/content/dicom/cloud-support.json#_meta. Status taxonomy: required (mandated on Store), queryable (QIDO-RS matching key), preserved (stored as-is), promoted (AWS top-level metadata), unsupported (stripped/rejected).

Real-World Sample Values

  • 128 CT_small.dcm
  • 64 MR_small.dcm
  • 60 ExplVR_BigEnd.dcm

Extracted from pydicom test fixtures (MIT, de-identified).

Mirth Connect Example

Skip thumbnail-only DICOM with degenerate Rows — Some PACS / VNA vendors push tiny preview images alongside full-resolution data

Some PACS / VNA vendors push tiny preview images alongside full-resolution data. Filter these from full ingest pipeline.

// (0028,0010) Rows — drop suspiciously small images on the perimeter channel
var rows = parseInt(String(msg.dataset.attr.(@tag == '00280010').value), 10);
if (rows < 64) {
  logger.info('Dropping low-resolution image (Rows=' + rows + ')');
  destinationSet.removeAll();
  return;
}

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

  • high Image dimensions don't match Pixel Data length

    Diagnosis: (0028,0010) Rows × (0028,0011) Columns × bytes-per-pixel ≠ length of (7FE0,0010) Pixel Data. File is corrupt or partially uploaded.

    Fix: Validate at perimeter: compute expected pixel data length from Rows/Columns/BitsAllocated/SamplesPerPixel and compare to actual length. On mismatch: route to quarantine, do not forward to PACS.

Reference only — validate before applying a fix. Scenarios are drawn from common DICOM/HL7 v2 integration patterns; reproduce against your environment before acting on any diagnosis. See NEMA PS3.6 + your vendor conformance statement for authoritative specification. Severity levels: high (data-loss / patient-safety), medium (workflow disruption), low (cosmetic).

DICOM Integration Services

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