DICOM Conformance Statement

Updated August 16, 2019 for ProKnow DS v1.12.0

1.  Conformance Statement Overview

ProKnow DS is a cloud-based RT-PACS (Radiation Therapy Picture/Patient Archiving and Communication System). It enables radiotherapy professionals to archive, inspect, analyze, and interact with radiation therapy patient data for retrospective studies, prospective analysis, and clinical decision support. Although most patient data will be generated and imported from external systems, ProKnow DS also allows users to interact with patient data by performing common tasks such as structure renaming, Boolean operators, and contouring.

ProKnow DS does not support any of the DICOM networking services (transfer, query/retrieve, workflow management, print management). Instead, a user interface is provided to upload and download DICOM files. In addition, ProKnow DS contains a private REST API to receive uploaded files from the client-side application and ProKnow DICOM DS local data services. Table 1-1 identifies the standard SOP classes supported by ProKnow DS.

Table 1-1. Supported Standard SOP Classes

SOP Class Name SOP Class UID PS 3.3 Reference
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 A.3
MR Image Storage 1.2.840.10008.5.1.4.1.1.4 A.4
RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2 A.18
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3 A.19
RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5 A.20
RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8 A.49
Spatial Registration 1.2.840.10008.5.1.4.1.1.66.1 C.20

2.  Table of Contents

2.1. List of Tables

Table Number Table Name
1-1 Supported Standard SOP Classes
3-1 Revision History
3-2 Terms and Definitions
3-3 Abbreviations
3-4 References
9-1 IOD of Edited or Created RT Structure Set SOP Instances
9-2 RT Series Module Attributes Saved with RT Structure Set SOP Instances
9-3 Structure Set Module Attributes Saved with RT Structure Set SOP Instances
9-4 ROI Contour Module Attributes Saved with RT Structure Set SOP Instances
9-5 RT ROI Observations Module Attributes Saved with RT Structure Set SOP Instances
9-6 IOD of Edited or Created Registration Object SOP Instances
9-7 Spatial Registration Series Module Attributes Saved with Registration Object SOP Instances
9-8 Spatial Registration Module Attributes Saved with Registration Object SOP Instances
9-9 Patient Module Attributes Saved with All SOP Instances
9-10 General Study Module Attributes Saved with All SOP Instances
9-11 General Series Module Attributes Saved with All SOP Instances
9-12 Frame of Reference Module Attributes Saved with All SOP Instances
9-13 General Equipment Module Attributes Saved with All SOP Instances
9-14 SOP Common Module Attributes Saved with All SOP Instances
9-15 Common Instance Reference Module Attributes Saved with All SOP Instances
9-16 SOP CT Image IOD Modules Used
9-17 CT Image Module Attributes Used from CT Image SOP Instances
9-18 MR Image IOD Modules Used
9-19 RT Structure Set IOD Modules Used
9-20 Structure Set Module Attributes Used from RT Structure Set SOP Instances
9-21 ROI Contour Module Attributes Used from RT Structure Set SOP Instances
9-22 RT ROI Observations Module Attributes Used from RT Structure Set SOP Instances
9-23 RT Plan/RT Ion Plan IOD Modules Used
9-24 RT General Plan Module Attributes Used from RT Plan, RT Ion Plan SOP Instances
9-25 RT Patient Setup Module Attributes Used from RT Plan, RT Ion Plan SOP Instances
9-26 RT Fraction Scheme Module Attributes Used from RT Plan, RT Ion Plan SOP Instances
9-27 RT Beams, RT Ion Beams Module Attributes Used from RT Plan, RT Ion Plan SOP Instances
9-28 RT Brachy Application Setups Module Attributes Used from RT Plan SOP Instances
9-29 RT Dose IOD Modules Used
9-30 RT Dose Module Attributes Used from RT Dose SOP Instances
9-31 Spatial Registration IOD Modules Used
9-32 Spatial Registration Series Module Attributes saved with Registration Object SOP Instances
9-33 Spatial Registration Module Attributes saved with Registration Object SOP Instances
9-34 Patient Module Attributes Used from All SOP Instances
9-35 General Study Module Attributes Used from All SOP Instances
9-36 General Series, RT Series Module Attributes Used from All SOP Instances
9-37 Frame of Reference Module Attributes Used from All SOP Instances
9-38 General Equipment Module Attributes Used from All SOP Instances
9-39 Image Plane Module Attributes Used from CT Image, MR Image, and RT Dose SOP Instances
9-40 Image Pixel Module Attributes Used from CT Image, MR Image, and RT Dose SOP Instances
9-41 SOP Common Module Attributes Used from All SOP Instances
9-42 Common Instance Reference Module Attributes Used from All SOP Instances

3.  Introduction

3.1. Revision History

Table 3-1. Revision History

Document Revision Date of Issue Description of Change
A September 28, 2018 Initial release
B August 16, 2019 Addition of Spatial Registration support

3.2. Audience

This document is written for the people that need to understand how ProKnow DS will integrate into their healthcare facility. This includes both those responsible for overall imaging network policy and architecture, as well as integrators who need to have a detailed understanding of the DICOM features of the product. This document contains some basic DICOM definitions so that any reader may understand how this product implements DICOM features. However, integrators are expected to fully understand all the DICOM terminology, how the tables in this document relate to the product's functionality, and how that functionality integrates with other devices that support compatible DICOM features.

3.3. Remarks

The scope of this DICOM conformance statement is to facilitate integration between ProKnow DS and other DICOM products. The conformance statement should be read and understood in conjunction with the DICOM standard. DICOM by itself does not guarantee interoperability. The conformance statement does, however, facilitate a first-level comparison for interoperability between different applications supporting compatible DICOM functionality. This conformance statement is not supposed to replace validation with other DICOM equipment to ensure proper exchange of intended information. In fact, the user should be aware of the following important issues:

  • The comparison of different conformance statements is just the first step towards assessing interconnectivity and interoperability between the product and other DICOM conformant equipment.
  • Test procedures should be defined and executed to validate the required level of interoperability with specific compatible DICOM equipment, as established by the healthcare facility.

3.4. Terms and Definitions

Informal definitions are provided for the following terms used in this conformance statement. The DICOM standard is the authoritative source for formal definitions of these terms.

Table 3-2. Terms and Definitions

Term Definition
Attribute A unit of information in an object definition; a data element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower level data elements. Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032).
Information Entity (IE) That portion of information defined by a Composite IOD which is related to one specific class of Real-World Object. There is a one-to-one correspondence between Information Entities and entities in the DICOM Application Model.
Information Object Definition (IOD) The specified set of Attributes that comprise a type of data object, does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. The Attributes may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C). Examples: MR Image IOD, CT Image IOD, Print Job IOD.
Module A set of Attributes within an Information Object Definition that are logically related to each other. Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex
Service/Object Pair (SOP) Class The specification of the network or media transfer (service) of a particular type of data (object); the fundamental unit of DICOM interoperability specification. Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management.
Service/Object Pair (SOP) Instance An information object; a specific occurrence of information exchanged in a SOP Class. Example: a specific x-ray image.
Tag A 32-bit identifier for a data element, represented as a pair of four digit hexadecimal numbers, the “group” and the “element”. If the “group” number is odd, the tag is for a private (manufacturer-specific) data element. Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element]
Transfer Syntax The encoding used for exchange of DICOM information objects and messages. Examples: JPEG compressed (images), little endian explicit value representation.
Unique Identifier (UID) A globally unique “dotted decimal” string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study Instance UID, SOP Class UID, SOP Instance UID.
Value Representation (VR) The format type of an individual DICOM data element, such as text, an integer, a person’s name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element.

3.5. Basics of DICOM Communication

This section describes terminology used in this conformance statement for the non-specialist. The key terms used in the conformance statement are highlighted in italics below. This section is not a substitute for training about DICOM, and it makes many simplifications about the meanings of DICOM terms.

Since ProKnow DS does not support any DICOM networking services, these services need to be provided by other applications. ProKnow DS does provide a user interface and private REST API to upload and download files created and used by these other applications.

DICOM specifies a variety of methods for encoding data, denoted transfer syntaxes. The transfer syntax specifies endianness and whether the value representation for each attribute is explicitly provided or whether it must be determined based on the tag using a DICOM dictionary. Each unit of data is formatted in accordance with the appropriate information object definition, using the transfer syntax.

3.6. Abbreviations

Table 3-3. Abbreviations

C Conditional (Module Usage)
DICOM Digital Imaging and Communications in Medicine
IE Information Entity
IOD Information Object Definition
ISO International Organization for Standards
M Mandatory (Module Usage)
NEMA National Electrical Manufacturers Association
OSI Open Systems Interconnection
PS 3.3 DICOM Standard Part 3: Information Object Definitions
PS 3.15 DICOM Standard Part 15: Security and System Management Profiles
QA Quality Assurance
RT Radiotherapy
SOP Service-Object Pair
SRO Spatial Registration Object
U User Option (Module Usage)
UID Unique Identifier
VR Value Representation

3.7. References

Table 3-4. References

NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free at Digital Imaging and Communications in Medicine (DICOM) Standard, available free at https://www.dicomstandard.org

4.  Networking

ProKnow DS does not provide any DICOM networking services or support any networking roles.

5.  Media Interchange

ProKnow DS does not provide any media interchange services.

6.  Transformation of DICOM to CDA

ProKnow DS does not support any Structured Reporting (SR) objects.

7.  Support Character Sets

ProKnow DS does not support extended character sets.

8.  Security

ProKnow DS does not claim conformance to any of the Security and System Management Profiles defined in the DICOM Standard. That being said, data security is one of the most important aspects of the ProKnow DS design. All data transmission both to and from the Internet (including calls to the REST API to upload DICOM files) is encrypted using secure HTTP access (HTTPS) and all communication between servers is encrypted using HTTPS or SSL.

8.1. Security Profiles

No Security Profiles are supported.

8.2. Association Level Security

ProKnow DS does not support Association Level Security.

8.3. Application Level Security

Any users logging into ProKnow DS must identify themselves with, at a minimum, an email and password. It is also possible to utilize multi-factor authentication (enabled at a per-user or organization-wide level) to further enhance security.

9.  Annexes

9.1. IOD Contents

9.1.1. Created SOP Instances

ProKnow DS creates RT Structure Set and Spatial Registration SOP instances as either new or edited instances. The attribute values saved are the same as the values in the referenced Image instances for new or edited SOP instances, except where noted, to facilitate interoperability with external systems.

The following tables use a number of abbreviations. The abbreviations used in the “Presence of Value” column are:

VNAP – Value Not Always Present (attribute saved with zero length if no value is present)
ANAP – Attribute Not Always Present
ALWAYS – Always Present
EMPTY – Attribute is sent without a value
N/A – Attribute does not have a value, e.g., a sequence (SQ)

The abbreviations used in the “Source” column are:

USER – the attribute value source is from User input
AUTO – the attribute value is generated automatically

9.1.1.1. RT Structure Set Information Object Implementation

Table 9-1. IOD of Edited or Created RT Structure Set SOP Instances

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-9
Study General Study C.7.2.1 See Table 9-10
Series RT Series C.8.8.1 See Table 9-2
Equipment General Equipment C.7.5.1 See Table 9-13
Frame of Reference Frame of Reference C.7.4.1 See Table 9-12
Structure Set Structure Set C.8.8.5 See Table 9-3
ROI Contour C.8.8.6 See Table 9-4
RT ROI Observations C.8.8.8 See Table 9-5
SOP Common C.12.1 See Table 9-14

Table 9-2. RT Series Module Attributes Saved with RT Structure Set SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Modality (0008,0060) CS "RTSTRUCT" ALWAYS  
Series Instance UID (0020,000E) UI Copied ALWAYS Input SOP instance(s)
Series Number (0020,0011) IS Copied VNAP Input SOP instance(s)
Series Date (0008,0021) DA Copied ANAP Input SOP instance(s)
Series Time (0008,0031) TM Copied ANAP Input SOP instance(s)
Operators’ Name (0008,1070) PN Copied ANAP Input SOP instance(s)

Table 9-3. Structure Set Module Attributes Saved with RT Structure Set SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Structure Set Label (3006,0002) SH Copied ALWAYS Input SOP instance(s) or USER
Structure Set Date (3006,0008) DA   EMPTY  
Structure Set Time (3006,0009) TM   EMPTY  
Referenced Frame of Reference Sequence (3006,0010) SQ   N/A  
>Frame of Reference UID (0020,0052) UI Copied ALWAYS Referenced CT image set
>RT Referenced Study Sequence (3006,0012) SQ   N/A  
>>Referenced SOP Class UID (0008,1150) UI Copied ALWAYS Referenced CT image set
>>Referenced SOP Instance UID (0008,1155) UI Copied ALWAYS Referenced CT image set
>>RT Referenced Series Sequence (3006,0014) SQ   N/A  
>>>Series Instance UID (0020,000E) UI Copied ALWAYS Referenced CT image set
>>>Contour Image Sequence (3006,0016) SQ   N/A  
>>>>Referenced SOP Class UID (0008,1150) UI Copied ALWAYS Referenced CT image set
>>>>Referenced SOP Instance UID (0008,1155) UI Copied ALWAYS Referenced CT image set
Structure Set ROI Sequence (3006,0020) SQ   N/A  
>ROI Number (3006,0022) IS Copied or uniquely generated ALWAYS Input SOP instance
>Referenced Frame of Reference UID (3006,0024) UI Copied ALWAYS Referenced CT image set
>ROI Name (3006,0026) LO Copied ALWAYS Input SOP instance or USER
>ROI Generation Algorithm (3006,0036) CS “MANUAL” ALWAYS  

Table 9-4. ROI Contour Module Attributes Saved with RT Structure Set SOP Instances

Attribute Name Tag VR Value Presence of Value Source
ROI Contour Sequence (3006,0039) SQ      
>Referenced ROI Number (3006,0084) IS Copied or the number of the new ROI ALWAYS Input SOP instance or AUTO
>ROI Display Color (3006,002A) IS Copied or the assigned color ALWAYS Input SOP instance or USER
>Contour Sequence (3006,0040) SQ      
>>Contour Image Sequence (3006,0016) SQ NOTE: Removed for existing POINT ROIs    
>>>Referenced SOP Class UID (0008,1150) UI Copied or SOP class UID of image on which contour was drawn ALWAYS Referenced CT image set
>>>Referenced SOP Instance UID (0008,1155) UI Copied or SOP instance UID of image on which contour was drawn ALWAYS Referenced CT image set
>>Contour Geometric Type (3006,0042) CS Copied or "CLOSED_PLANAR" for new contours ALWAYS Input SOP instance or AUTO
>>Number of Contour Points (3006,0046) IS Copied or the number of contour points drawn ALWAYS Input SOP instance or AUTO
>>Contour Data (3006,0050) DS Copied or the contour points drawn ALWAYS Input SOP instance or AUTO

Table 9-5. RT ROI Observations Module Attributes Saved with RT Structure Set SOP Instances

Attribute Name Tag VR Value Presence of Value Source
RT ROI Observations Sequence (3006,0080) SQ      
>Observation Number (3006,0082) IS Copied or the number of the new observation ALWAYS Input SOP instance or AUTO
>Referenced ROI Number (3006,0084) IS Copied or the number of the new ROI ALWAYS Input SOP instance or AUTO
>RT ROI Interpreted Type (3006,00A4) CS Copied or the user assigned value VNAP Input SOP instance or USER
>ROI Interpreter (3006,00A6) PN   EMPTY  

9.1.1.2. Registration Object Information Object Implementation

Table 9-6. IOD of Edited or Created Registration Object SOP Instances

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-9
Study General Study C.7.2.1 See Table 9-10
Series General Series C.8.8.1 See Table 9-11
Spatial Registration Series C.20.1 See Table 9-7
Frame of Reference Frame of Reference C.7.4.1 See Table 9-12
Equipment General Equipment C.7.5.1 See Table 9-13
Spatial Registration Spatial Registration C.20.2 See Table 9-10
Common Instance Reference C.12.2 See Table 9-15
SOP Common C.12.1 See Table 9-14

Table 9-7. Spatial Registration Series Module Attributes Saved with Registration Object SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Modality (0008,0060) CS "REG" ALWAYS AUTO

Table 9-8. Spatial Registration Module Attributes Saved with Registration Object SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Content Date (0008,0023) DA Date SRO was last updated ALWAYS AUTO
Content Time (0008,0033) TM Time SRO was last updated ALWAYS AUTO
Instance Number (0020,0013) IS 0 ALWAYS AUTO
Content Label (0070,0080) CS "REGISTRATION" ALWAYS AUTO
Content Description (0070,0081) LO SRO Name ALWAYS USER
Content Creator's Name (0070,0084) PN   EMPTY  
Registration Sequence (0070,0308) SQ      
>Frame of Reference UID (0020,0052) UI Frame of reference of source or target coordinate system ALWAYS AUTO
>Referenced Image Sequence (0008,1140) SQ      
>>Referenced SOP Class UID Sequence (0008,1150) UI Class UID of referenced image set ALWAYS AUTO
>>Referenced SOP Instance UID (0008,1155) UI SOP Instance UID of referenced image set ALWAYS AUTO
>Matrix Registration Sequence (0070,0309) SQ      
>>Registration Type Code Sequence (0070,030D) SQ      
>>>Code Value (0008,0100) SH "125025" ALWAYS AUTO
>>>Coding Scheme Designator (0008,0102) SH "DCM" ALWAYS AUTO
>>>Coding Scheme Version (0008,0103) SH "20040115" ALWAYS AUTO
>>>Code Meaning (0008,0104) LO "Visual Alignment" ALWAYS AUTO
>>Matrix Sequence (0070,030A) SQ      
>>>Frame Of Reference Transformation Matrix (0070,030A) DS SRO 4x4 affine transformation matrix ALWAYS USER
>>>Frame Of Reference Transformation Matrix Type (0070,030C) CS "RIGID" ALWAYS AUTO

9.1.1.3. Common Module Implementations

Table 9-9. Patient Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Patient's Name (0010,0010) PN Copied VNAP Input SOP instance(s)
Patient's ID (0010,0020) LO Copied VNAP Input SOP instance(s)
Patient's Birth Date (0010,0030) DA Copied VNAP Input SOP instance(s)
Patient's Birth Time (0010,0032) TM Copied ANAP Input SOP instance(s)
Patient's Sex (0010,0040) CS Copied VNAP Input SOP instance(s)

Table 9-10. General Study Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Study Instance UID (0020,000D) UI Copied ALWAYS Input SOP instance(s)
Study Date (0008,0020) DA Copied VNAP Input SOP instance(s)
Study Time (0008,0030) TM Copied VNAP Input SOP instance(s)
Referring Physician’s Name (0008,0090) PN   EMPTY  
Study ID (0020,0010) SH Copied VNAP Input SOP instance(s)
Accession Number (0008,0050) SH   EMPTY  
Study Description (0008,1030) LO Copied ANAP Input SOP instance(s)

Table 9-11. General Series Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Modality (0008,0060) CS Modality based on SOP Instance ALWAYS  
Series Instance UID (0020,000E) UI Copied ALWAYS Input SOP instance(s)
Series Number (0020,0011) IS Copied VNAP Input SOP instance(s)
Series Date (0008,0021) DA Copied ANAP Input SOP instance(s)
Series Time (0008,0031) TM Copied ANAP Input SOP instance(s)
Series Description (0008,103E) LO Copied ANAP Input SOP instance(s)

Table 9-12. Frame of Reference Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Frame of Reference UID (0020,0052) UI Frame of reference from referenced instances ALWAYS AUTO
Position Reference Indicator (0020,1040) LO   EMPTY  

Table 9-13. General Equipment Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Manufacturer (0008,0070) LO "ProKnow" ALWAYS AUTO
Manufacturer’s Model Name (0008,1090) LO "ProKnow DS" ALWAYS AUTO

Table 9-14. SOP Common Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
SOP Class UID (0008,0016) UI Specific class UID for instance ALWAYS AUTO
SOP Instance UID (0008,0018) UI SOP Instance UID ALWAYS AUTO

Table 9-15. Common Instance Reference Module Attributes Saved with All SOP Instances

Attribute Name Tag VR Value Presence of Value Source
Referenced Series Sequence (0008,1115) SQ   ANAP  
>Series Instance UID (0020,000E) UI Referenced Series Instance UID ALWAYS AUTO
>Referenced Instance Sequence (0008,114A) SQ   ALWAYS  
>>Referenced SOP Class UID (0008,1150) UI SOP Class UID of Referenced Instance ALWAYS AUTO
>>Referenced SOP Instance UID (0008,1155) UI SOP Instance UID of Referenced Instance ALWAYS AUTO
Studies Containing Other Referenced Instances Sequence (0008,1200) SQ   ANAP  
>Study Instance UID (0020,000E) UI Referenced Study Instance UID ALWAYS AUTO
>Referenced Series Sequence (0008,1115) SQ   ANAP  
>>Series Instance UID (0020,000E) UI Referenced Series Instance UID ALWAYS AUTO
>>Referenced Instance Sequence (0008,114A) SQ   ALWAYS  
>>>Referenced SOP Class UID (0008,1150) UI SOP Class UID of Referenced Instance ALWAYS AUTO
>>>Referenced SOP Instance UID (0008,1155) UI SOP Instance UID of Referenced Instance ALWAYS AUTO

9.1.2. Usage of Attributes from Received IODs

The following sections list the attributes used in the ProKnow DS implementation of each information object, along with any additional attribute requirements not already specified in the DICOM Standard.

9.1.2.1. CT Image Information Object Implementation

Table 9-16. SOP CT Image IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Series General Series C.7.3.1 See Table 9-36
Frame of Reference Frame of Reference C.7.4.1 See Table 9-37
Image Image Plane C.7.6.2 See Table 9-39
Image Pixel C.7.6.3 See Table 9-40
CT Image C.8.2.1 See Table 9-17
SOP Common C.12.1 See Table 9-41

Table 9-17. CT Image Module Attributes Used from CT Image SOP Instances

Attribute Name Tag Type Notes
Rescale Intercept (0028,1052) 1 Rescale Intercept
Rescale Slope (0028,1053) 1 Rescale Slope

9.1.2.2. MR Image Information Object Implementation

Table 9-18. MR Image IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Series General Series C.7.3.1 See Table 9-36
Frame of Reference Frame of Reference C.7.4.1 See Table 9-37
Image Image Plane C.7.6.2 See Table 9-39
Image Pixel C.7.6.3 See Table 9-40
SOP Common C.12.1 See Table 9-41

9.1.2.3. RT Structure Set Information Implementation

Table 9-19. RT Structure Set IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Series RT Series C.8.8.1 See Table 9-36
Structure Set Structure Set C.8.8.5 See Table 9-20
ROI Contour C.8.8.6 See Table 9-21
RT ROI Observations C.8.8.8 See Table 9-22
  SOP Common C.12.1 See Table 9-41

Table 9-20. Structure Set Module Attributes Used from RT Structure Set SOP Instances

Attribute Name Tag Type Notes
Structure Set Label (3006,0002) 1  
Structure Set Date (3006,0008) 2  
Structure Set Time (3006,0009) 2  
Referenced Frame of Reference Sequence (3006,0010) 3  
>Frame of Reference UID (0020,0052) 1  
>RT Referenced Study Sequence (3006,0012) 3  
>>Referenced SOP Class UID (0008,1150) 1  
>>Referenced SOP Instance UID (0008,1155) 1  
>>RT Referenced Series Sequence (3006,0014) 1  
>>>Series Instance UID (0020,000E) 1  
Structure Set ROI Sequence (3006,0020) 1  
>ROI Number (3006,0022) 1  
>Referenced Frame of Reference UID (3006,0024) 1  
>ROI Name (3006,0026) 2  
>ROI Generation Algorithm (3006,0036) 2  

Table 9-21. ROI Contour Module Attributes Used from RT Structure Set SOP Instances

Attribute Name Tag Type Notes
ROI Contour Sequence (3006,0039) 1  
>Referenced ROI Number (3006,0084) 1  
>ROI Display Color (3006,002A) 3  
>Contour Sequence (3006,0040) 3  
>>Contour Geometric Type (3006,0042) 1  
>>Contour Data (3006,0050) 1  

Table 9-22. RT ROI Observations Module Attributes Used from RT Structure Set SOP Instances

Attribute Name Tag Type Notes
RT ROI Observations Sequence (3006,0080) 1  
>Referenced ROI Number (3006,0084) 1  
>RT ROI Interpreted Type (3006,00A4) 2  

9.1.2.4. RT Plan, RT Ion Plan Information Object Implementation

Table 9-23. RT Plan/RT Ion Plan IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Frame of Reference Frame of Reference C.7.4.1 See Table 9-37
Equipment General Equipment C.7.5.1 See Table 9-38
Plan RT General Plan C.8.8.9 See Table 9-24
RT Patient Setup C.8.8.12 See Table 9-25
RT Fraction Scheme C.8.8.13 See Table 9-26
RT Beams, RT Ion Beams C.8.8.14, C8.8.25 See Table 9-27
RT Brachy Application Setups C.8.8.15 See Table 9-28
SOP Common C.12.1 See Table 9-41

Table 9-24. RT General Plan Module Attributes Used from RT Plan, RT Ion Plan SOP Instances

Attribute Name Tag Type Notes
RT Plan Label (300A,0002) 1  
RT Plan Name (300A,0003) 3  
RT Plan Description (300A,0004) 3  
Instance Number (0020,0013) 3  
RT Plan Date (300A,0006) 2  
RT Plan Time (300A,0007) 2  
Plan Intent (300A,000A) 3  
RT Plan Geometry (300A,000C) 1  
Referenced Structure Set Sequence (300C,0060) 1C  
>Referenced SOP Class UID (0008,1150) 1  
>Referenced SOP Instance UID (0008,1155) 1  
Referenced Dose Sequence (300C,0080) 3  
>Referenced SOP Class UID (0008,1150) 1  
>Referenced SOP Instance UID (0008,1155) 1  
Referenced RT Plan Sequence (300C,0002) 3  
>Referenced SOP Class UID (0008,1150) 1  
>Referenced SOP Instance UID (0008,1155) 1  

Table 9-25. RT Patient Setup Module Attributes Used from RT Plan, RT Ion Plan SOP Instances

Attribute Name Tag Type Notes
Patient Setup Sequence (300A,0180) 1  
>Patient Setup Number (300A,0182) 1  
>Patient Setup Label (300A,0183) 3  
>Patient Position (0018,5100) 1C  

Table 9-26. RT Fraction Scheme Module Attributes Used from RT Plan, RT Ion Plan SOP Instances

Attribute Name Tag Type Notes
Fraction Group Sequence (300A,0070) 1  
>Fraction Group Number (300A,0071) 1  
>Fraction Group Description (300A,0072) 3  
>Number of Fractions Planned (300A,0078) 2  
>Referenced Beam Sequence (300C,0004) 1C  
>>Referenced Beam Number (300C,0006) 1  
>>Beam Dose Specification Point (300A,0082) 3  
>>Beam Dose (300A,0084) 3  
>>Beam Meterset (300A,0086) 3  
>Referenced Brachy Application Setup Sequence (300C,000A) 1C  
>>Referenced Brachy Application Setup Number (300C,000C) 1  
>>Brachy Application Setup Dose Specification Point (300A,00A2) 3  
>>Brachy Application Setup Dose (300A,00A4) 3  

Table 9-27. RT Beams, RT Ion Beams Module Attributes Used from RT Plan, RT Ion Plan SOP Instances

Attribute Name Tag Type Notes
Beam Sequence, Ion Beam Sequence (300A,00B0), (300A,03A2) 1 RT Plan, RT Ion Plan
>Beam Number (300A,00C0) 1  
>Beam Name (300A,00C2) 3  
>Beam Description (300A,00C3) 3  
>Beam Type (300A,00C4) 1  
>Radiation Type (300A,00C6) 2  
>Primary Fluence Mode Sequence (3002,0050) 3 RT Beams only
>>Fluence Mode (3002,0051) 1 RT Beams only
>>Fluence Mode ID (3002,0052) 1C RT Beams only
>High-Dose Technique Type (300A,00C7) 1C RT Beams only
>Scan Mode (300A,0308) 1 RT Ion Beams only
>Treatment Machine Name (300A,00B2) 2  
>Manufacturer (0008,0070) 3  
>Institution Name (0008,0080) 3  
>Institution Address (0008,0081) 3  
>Institutional Department Name (0008,1040) 3  
>Manufacturer’s Model Name (0008,1090) 3  
>Device Serial Number (0018,1000) 3  
>Primary Dosimeter Unit (300A,00B3) 1  
>Virtual Source Axis Distance (300A,030A) 1 RT Ion Beams only
>Beam Limiting Device Sequence, Ion Beam Limiting Device Sequence (300A,00B6), (300A,03A4) 1, 3 RT Beams, RT Ion Beams
>>RT Beam Limiting Device Type (300A,00B8) 1  
>>Source to Beam Limiting Device Distance (300A,00BA) 3 RT Beams only
>>Isocenter to Beam Limiting Device Distance (300A,00BB) 2 RT Ion Beams only
>>Number of Leaf/Jaw Pairs (300A,00BC) 1  
>>Leaf Position Boundaries (300A,00BE) 2C  
>Referenced Patient Setup Number (300C,006A) 3  
>Treatment Delivery Type (300A,00CE) 3  
>Wedge Sequence, Ion Wedge Sequence (300A,00D1), (300A,03AA) 1C RT Beams, RT Ion Beams
>>Wedge Number (300A,00D2) 1  
>>Wedge Type (300A,00D3) 2  
>Compensator Sequence, Ion Range Compensator Sequence (300A,00E3), (300A,02EA) 1C RT Beams, RT Ion Beams
>>Compensator Number (300A,00E4) 1  
>>Material ID (300A,00E1) 2  
>>Compensator ID (300A,00E5) 3  
>Referenced Bolus Sequence (300C,00B0) 1C  
>>Referenced ROI Number (3006,0084) 1  
>Block Sequence, Ion Block Sequence (300A,00F4), (300A,03A6) 1C RT Beams, RT Ion Beams
>>Block Type (300A,00F8) 1  
>>Block Divergence (300A,00FA) 1  
>>Block Mounting Position (300A,00FB) 1  
>>Block Number (300A,00FE) 1  
>>Material ID (300A,00E1) 2  
>>Block Thickness (300A,0100) 1  
>Snout Sequence (300A,030C) 3 RT Ion Beams only
>>Snout ID (300A,030F) 1 RT Ion Beams only
>Applicator Sequence (300A,0107) 3  
>>Applicator ID (300A,0108) 1  
>>Applicator Type (300A,0109) 1  
>General Accessory Sequence (300A,0420) 3  
>>General Accessory Number (300A,0424) 1  
>>General Accessory ID (300A,0421) 1  
>>General Accessory Type (300A,0423) 3  
>Lateral Spreading Device Sequence (300A,0332) 1C RT Ion Beams only
>>Lateral Spreading Device Number (300A,0334) 1 RT Ion Beams only
>>Lateral Spreading Device ID (300A,0336) 1 RT Ion Beams only
>>Lateral Spreading Device Type (300A,0338) 1 RT Ion Beams only
>Range Shifter Sequence (300A,0314) 1C RT Ion Beams only
>>Range Shifter Number (300A,0316) 1 RT Ion Beams only
>>Range Shifter ID (300A,0318) 1 RT Ion Beams only
>>Range Shifter Type (300A,0320) 1 RT Ion Beams only
>Range Modulator Sequence (300A,0342) 1C RT Ion Beams only
>>Range Modulator Number (300A,0344) 1 RT Ion Beams only
>>Range Modulator ID (300A,0346) 1 RT Ion Beams only
>>Range Modulator Type (300A,0348) 1 RT Ion Beams only
>Final Cumulative Meterset Weight (300A,010E) 1C  
>Control Point Sequence, Ion Control Point Sequence (300A,0111), (300A,03A8) 1 RT Beams, RT Ion Beams
>>Cumulative Meterset Weight (300A,0134) 2  
>>Nominal Beam Energy (300A,0114) 3, 1C RT Beams, RT Ion Beams
>>Dose Rate Set (300A,0115) 3 RT Beams only
>>Meterset Rate (300A,035A) 3 RT Ion Beams only
>>Beam Limiting Device Position Sequence (300A,011A) 1C  
>>>RT Beam Limiting Device Type (300A,00B8) 1  
>>>Leaf/Jaw Positions (300A,011C) 1  
>>Gantry Angle (300A,011E) 1C  
>>Gantry Rotation Direction (300A,011F) 1C  
>>Gantry Pitch Angle (300A,014A) 3  
>>Gantry Pitch Rotation Direction (300A,014C) 3  
>>Beam Limiting Device Angle (300A,0120) 1C  
>>Beam Limiting Device Rotation Direction (300A,0121) 1C  
>>Patient Support Angle (300A,0122) 1C  
>>Patient Support Rotation Direction (300A,0123) 1C  
>>Table Top Pitch Angle (300A,0140) 1C  
>>Table Top Pitch Rotation Direction (300A,0142) 1C  
>>Table Top Roll Angle (300A,0144) 1C  
>>Table Top Roll Rotation Direction (300A,0146) 1C  
>>Isocenter Position (300A,012C) 2C  

Table 9-28. RT Brachy Application Setups Module Attributes Used from RT Plan SOP Instances

Attribute Name Tag Type Notes
Brachy Treatment Technique (300A,0200) 1  
Brachy Treatment Type (300A,0202) 1  
Treatment Machine Sequence (300A,0206) 1  
>Treatment Machine Name (300A,00B2) 2  
>Manufacturer (0008,0070) 3  
>Institution Name (0008,0080) 3  
>Institution Address (0008,0081) 3  
>Institutional Department Name (0008,1040) 3  
>Manufacturer’s Model Name (0008,1090) 3  
>Device Serial Number (0018,1000) 3  
Source Sequence (300A,0210) 1  
>Source Number (300A,0212) 1  
>Source Type (300A,0214) 1  
>Source Manufacturer (300A,0216) 3  
>Active Source Diameter (300A,0218) 3  
>Active Source Length (300A,021A) 3  
>Source Isotope Name (300A,0226) 1  
>Source Isotope Half Life (300A,0228) 1  
>Source Strength Units (300A,0229) 1C  
>Reference Air Kerma Rate (300A,022A) 1  
>Source Strength (300A,022B) 1C  
>Source Strength Reference Date (300A,022C) 1  
>Source Strength Reference Time (300A,022E) 1  
Application Setup Sequence (300A,0230) 1  
>Application Setup Type (300A,0232) 1  
>Application Setup Number (300A,0234) 1  
>Application Setup Name (300A,0236) 3  
>Application Setup Manufacturer (300A,0238) 3  
>Total Reference Air Kerma (300A,0250) 1  
>Channel Sequence (300A,0280) 1  
>>Channel Number (300A,0282) 1  
>>Channel Length (300A,0284) 2  
>>Channel Total Time (300A,0286) 1  
>>Source Movement Type (300A,0288) 1  
>>Source Applicator Number (300A,0290) 3  
>>Source Applicator ID (300A,0291) 2C  
>>Source Applicator Type (300A,0292) 1C  
>>Source Applicator Name (300A,0294) 3  
>>Source Applicator Length (300A,0296) 1C  
>>Source Applicator Step Size (300A,02A0) 1C  
>>Referenced ROI Number (3006,0084) 2C  
>>Transfer Tube Number (300A,02A2) 2  
>>Reference Source Number (300C,000E) 1  
>>Final Cumulative Time Weight (300A,02C8) 1C  
>>Brachy Control Point Sequence (300A,02D0) 1  
>>>Cumulative Time Weight (300A,02D6) 2  
>>>Control Point Relative Position (300A,02D2) 1  
>>>Control Point 3D Position (300A,02D4) 3  

9.1.2.5. RT Dose Information Object Implementation

Table 9-29. RT Dose IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Series General Series C.7.3.1 See Table 9-36
Frame of Reference Frame of Reference C.7.4.1 See Table 9-37
  Image Plane C.7.6.2 See Table 9-39
Image Pixel C.7.6.3 See Table 9-40
RT Dose C.8.8.3 See Table 9-30
SOP Common C.12.1 See Table 9-41

Table 9-30. RT Dose Module Attributes Used from RT Dose SOP Instances

Attribute Name Tag Type Notes
Dose Type (3004,0004) 1  
Dose Summation Type (3004,000A) 1  
Referenced RT Plan Sequence (300C,0002) 1C  
>Referenced SOP Class UID (0008,1150) 1  
>Referenced SOP Instance UID (0008,1155) 1  
>Referenced Fraction Group Sequence (300C,0020) 1C  
>>Referenced Fraction Group Number (300C,0022) 1  
>>Referenced Beam Sequence (300C,0004) 1C  
>>>Referenced Beam Number (300C,0006) 1  
Grid Frame Offset Vector (3004,000C) 1C Dose planes must be uniformly spaced.
Dose Grid Scaling (3004,000E) 1C  

9.1.2.6. Spatial Registration Information Object Implementation

Table 9-31. Spatial Registration IOD Modules Used

IE Module PS 3.3 Reference Notes
Patient Patient C.7.1.1 See Table 9-34
Study General Study C.7.2.1 See Table 9-35
Series General Series C.8.8.1 See Table 9-36
Spatial Registration Series C.20.1 See Table 9-32
Frame of Reference Frame of Reference C.7.4.1 See Table 9-37
Equipment General Equipment C.7.5.1 See Table 9-38
Spatial Registration Spatial Registration C.20.2 See Table 9-33
Common Instance Reference C.12.2 See Table 9-42
SOP Common C.12.1 See Table 9-41

Table 9-32. Spatial Registration Series Module Attributes Saved with Registration Object SOP Instances

Attribute Name Tag Type Notes
Modality (0008,0060) 1 Must be "REG"

Table 9-33. Spatial Registration Module Attributes Saved with Registration Object SOP Instances

Attribute Name Tag Type Notes
Content Date (0008,0023) 1 Used to name SRO if Content Description is not present
Content Time (0008,0033) 1 Used to name SRO if Content Description is not present
Content Description (0070,0081) 2 If present, used to name SRO; otherwise, the Content Date and Time are used
Registration Sequence (0070,0308) 1 Exactly one or two items shall be included in this Sequence
>Frame of Reference UID (0020,0052) 1C Required
>Referenced Image Sequence (0008,1140) 1C Required
>>Referenced SOP Class UID Sequence (0008,1150) 1  
>>Referenced SOP Instance UID (0008,1155) 1  
>Matrix Registration Sequence (0070,0309) 1 Only a single item shall be included in this Sequence
>>Matrix Sequence (0070,030A) 1 Only a single item shall be included in this Sequence
>>>Frame Of Reference Transformation Matrix (0070,030A) 1  
>>>Frame Of Reference Transformation Matrix Type (0070,030C) 1 Must be "RIGID"

9.1.2.7. Common Module Implementations

Table 9-34. Patient Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Patient's Name (0010,0010) 2  
Patient ID (0010,0020) 2  
Patient’s Birth Date (0010,0030) 2  
Patient’s Birth Time (0010,0032) 3  
Patient’s Sex (0010,0040) 2  

Table 9-35. General Study Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Study Instance UID (0020,000D) 1  
Study Date (0008,0020) 2  
Study Time (0008,0030) 2  
Study ID (0020,0010) 2  
Study Description (0008,1030) 3  

Table 9-36. General Series, RT Series Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Modality (0008,0060) 1  
Series Instance UID (0020,000E) 1  
Series Number (0020,0011) 2  
Series Date (0008,0021) 3  
Series Time (0008,0031) 3  
Series Description (0008,103E) 3  

Table 9-37. Frame of Reference Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Frame of Reference UID (0020,0052) 1  

Table 9-38. General Equipment Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Manufacturer (0008,0070) 2  
Institution Name (0008,0080) 3  
Institution Address (0008,0081) 3  
Station Name (0008,1010) 3  
Institutional Department Name (0008,1040) 3  
Manufacturer’s Model Name (0008,1090) 3  
Device Serial Number (0018,1000) 3  
Software Versions (0018,1020) 3  

Table 9-39. Image Plane Module Attributes Used from CT Image, MR Image, and RT Dose SOP Instances

Attribute Name Tag Type Notes
Pixel Spacing (0028,0030 1 Must contain two values
Image Orientation (Patient) (0020,0037) 1 RT Dose SOP Instances must specify direction cosines as (+/-1, 0, 0, 0, +/-1, 0) or (0, +/-1, 0, +/-1, 0, 0) with an angle tolerance of 0.01 radians, i.e., the dose grid must be orthogonal to the patient coordinate system. CT Image and MR Image SOP Instances may specify any arbitrary (i.e., oblique) direction cosines.
Image Position (Patient) (0020,0032) 1  

Table 9-40. Image Pixel Module Attributes Used from CT Image, MR Image, and RT Dose SOP Instances

Attribute Name Tag Type Notes
Samples per Pixel (0028,0002) 1  
Photometric Interpretation (0028,0004) 1 RT Dose only
Rows (0028,0010) 1  
Columns (0028,0011) 1  
Bits Allocated (0028,0100) 1 Must be 16 or 32
Bits Stored (0028,0101) 1 Must be between 8 and Bits Allocated, inclusive
High Bit (0028,0102) 1  
Pixel Representation (0028,0103) 1  
Pixel Data (7FE0,0010) 1C  

Table 9-41. SOP Common Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
SOP Class UID (0008,0016) 1 Must be correct value for SOP Instance
SOP Instance UID (0008,0018) 1  

Table 9-42. Common Instance Reference Module Attributes Used from All SOP Instances

Attribute Name Tag Type Notes
Referenced Series Sequence (0008,1115) SQ 1C
>Series Instance UID (0020,000E) 1  
>Referenced Instance Sequence (0008,114A) 1  
>>Referenced SOP Class UID (0008,1150) 1 SOP Class UID of Referenced Instance
>>Referenced SOP Instance UID (0008,1155) 1  
Studies Containing Other Referenced Instances Sequence (0008,1200) SQ 1C
>Study Instance UID (0020,000E) UI 1
>Referenced Series Sequence (0008,1115) SQ 1
>>Series Instance UID (0020,000E) UI 1
>>Referenced Instance Sequence (0008,114A) SQ 11
>>>Referenced SOP Class UID (0008,1150) UI 1
>>>Referenced SOP Instance UID (0008,1155) UI 1

9.1.3. Attribute Mapping

ProKnow DS does not perform any attribute mapping.

9.1.4. Coerced/Modified Fields

ProKnow DS does not coerce nor modify any of the input fields.

9.2. Data Dictionary of Private Attributes

ProKnow DS does not use any private attributes.

9.3. Coded Terminology Templates

ProKnow DS does used not support coded terminology or templates.

9.4. Greyscale Image Consistency

ProKnow DS does not provide support for the DICOM Grayscale Standard Display Function.

9.5. Standard Extended/Specialized/Private SOP Classes

ProKnow DS supports extensions of the standard SOP classes specified in section 1, ignoring any private attributes. It does not support any specialized or private SOP classes.

9.6. Private Transfer Syntaxes

ProKnow DS does not support any private transfer syntaxes.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.