DICOM Attribute

RT Plan Relationship (300A,0055)

Keyword
RTPlanRelationship
VR
CS
VM
1

Definition

Relationship of referenced plan with respect to current plan. Defined Terms: PRIOR plan delivered prior to current treatment ALTERNATIVE alternative plan prepared for current treatment PREDECESSOR plan used in derivation of current plan VERIFIED_PLAN plan that is verified using the current plan. This Value shall only be used if Plan Intent (300A,000A) is present and has a Value of VERIFICATION CONCURRENT plan that forms part of a set of two or more RT Plan Instances representing a single conceptual 'plan', applied in parallel in one treatment phase

From NEMA PS3.3 §C.8.8.9.

Attribute Metadata

Tag
(300A,0055)
Keyword
RTPlanRelationship
Name
RT Plan Relationship
Value Representation (VR)
CS
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 CS with multiplicity 1.

Used in 1 Module

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

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

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

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 RTPlanRelationship or the broader (300A,0055) context: