DICOM Attribute

Transfer Syntax UID (0002,0010)

Keyword
TransferSyntaxUID
VR
UI
VM
1

Attribute Metadata

Tag
(0002,0010)
Keyword
TransferSyntaxUID
Name
Transfer Syntax UID
Value Representation (VR)
UI
Value Multiplicity (VM)
1
Status
Active
Source
NEMA PS3.6 (table_7-1)

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

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

  • 1.2.840.10008.1.2.1 CT_small.dcm
  • 1.2.840.10008.1.2.5 MR_small_RLE.dcm
  • 1.2.840.10008.1.2.2 MR_small_bigendian.dcm

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

Mirth Connect Example

JavaScript transformer snippets for the most-queried tags will be added as coverage expands.

Common Operational Errors

  • high TransferSyntaxUID declared but not honored

    Diagnosis: File's FMI header declares Transfer Syntax UID 1.2.840.10008.1.2.4.90 (JPEG 2000 Lossless) but the pixel data is actually uncompressed little-endian. Happens when modality's DICOM library header-writing and pixel-writing paths aren't synchronized. Viewers attempting JPEG 2000 decode fail; viewers guessing encoding may succeed.

    Fix: On ingress, verify the declared transfer syntax matches the actual pixel data encoding. For JPEG-family, confirm the JPEG magic bytes at the start of each frame. If mismatch: reject and alert the sender. Do NOT attempt to auto-detect and rewrite — that's a compliance violation.

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 TransferSyntaxUID or the broader (0002,0010) context: