DB Daemon Application Entity - AE Specifications

4.2 AE Specifications

4.2.3 DB Daemon Application Entity

4.2.3.1 SOP Classes

The DB Daemon Application Entity provides Standard Conformance to the following SOP Classes.

SOP Class Name SOP Class UID SCU

(Note 3) SCP

Computed Radiography Image

Storage 1.2.840.10008.5.1.4.1.1.1 Yes Yes

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Yes Yes

MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Yes Yes

Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 No Yes (Note 1)

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes Yes X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 No Yes

(Note 1) Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1 Yes Yes Positron Emission Tomography

Image Storage

1.2.840.10008.5.1.4.1.1.128 No Yes (Note 1)

RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1 Yes Yes

RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2 Yes Yes

RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3 Yes Yes RT Beams Treatment Record

Storage 1.2.840.10008.5.1.4.1.1.481.4 Yes Yes

LTArchive RT Treatment Record

Storage 1.2.246.352.70.1.10 Yes (Note 2) (Note 2) Yes

RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5 Yes Yes

RT Treatment Summary Record

Storage 1.2.840.10008.5.1.4.1.1.481.7 Yes No

RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8 Yes Yes RT Ion Beams Treatment Record

Storage

1.2.840.10008.5.1.4.1.1.481.9 Yes Yes Study Root Query/Retrieve

Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1 No Yes Study Root Query/Retrieve

Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2 No Yes

Table 4-37: SOP Classes for DB Daemon Application Entity

Note 1 Some SOP Instances will be converted to a different Modality when imported. For details see section 4.2.3.4.1.4.

Note 3 The SCU role is supported only to perform C-STORE sub-commands upon a C- MOVE request.

4.2.3.2 Association Policies

4.2.3.2.1 General

The DICOM standard application context name for DICOM 3.0 is always proposed.

Application Context Name 1.2.840.10008.3.1.1.1

Table 4-38: DICOM Application Context for DB Daemon Application Entity

4.2.3.2.2 Number of Associations

The DB Daemon Application Entity accepts all association requests that request one of the supported SOP Classes. It does not place any limitations on the number of concurrent associations or on who may connect to it, unless the ‘Permit Trusted Application Entities only’ option is enabled. If enabled, only Association request of the defined Application Entities will be accepted.

Maximum number of simultaneous Associations Unrestricted

Table 4-39: Number of Associations accepted for DB Daemon Application Entity

DB Daemon Application Entity does not initiate any Associations. 4.2.3.2.3 Asynchronous Nature

DB Daemon Application Entity does not support asynchronous communication. 4.2.3.2.4 Implementation Identifying Information

DB Daemon can be configured to work either in Vision Service mode or in Archive Service mode. The Archive Service mode is useful only in combination with Varian System Server LT Archive Client; therefore when in Archive Service mode it will accept only Association Open Requests from LT Archive Client.

The implementation information for this Application Entity is defined in the following table. Implementation Class UID (Vision Service mode) 1.2.246.352.70.2.1.42

Implementation Class UID (Archive Service mode) 1.2.246.352.70.2.1.32

Implementation Version Name (not used)

Table 4-40: DICOM Implementation Class and Version for DB Daemon Application Entity

4.2.3.3 Association Initiation Policy

4.2.3.4 Association Acceptance Policy

Unless the ‘Permit Trusted Application Entities only’ option is enabled, the DB Daemon Application Entity accepts all association requests that request one of the supported SOP Classes; otherwise it restricts access to the user-configured Application Entities.

4.2.3.4.1 Activity – Receive Storage Request

4.2.3.4.1.1 Description and Sequencing of Activities

All Instances received will be converted to the internal data model and stored to the DB. If conversion was not successful, the incoming DICOM stream will be stored as DICOM Media File on the local file system on a configurable location.

4.2.3.4.1.2 Accepted Presentation Contexts

DB Daemon Application Entity accepts Presentation Contexts shown in the following table.

Presentation Context Table

Abstract Syntax Transfer Syntax Role

Name UID Name UID

Ext. Neg. DICOM Implicit VR Little Endian 1.2.840.10008.1.2

All Storage SOP Classes in

SCP None Table 4-37 Table 4-37

DICOM Explicit VR Little Endian 1.2.840.10008.1.2.1

Table 4-41: Acceptable Presentation Contexts for DB Daemon Application Entity and Receive Storage Request

4.2.3.4.1.3 SOP Specific Conformance for all Storage SOP Classes

DB Daemon Application Entity conforms to storage service classes at level 0 (local) where not stated otherwise. Therefore it is guaranteed that at least all Type 1 Attributes are stored in the DB. Other Attributes are mainly supported but may be discarded in certain cases.

4.2.3.4.1.3.1 Presentation Context Acceptance Criterion

DB Daemon will always accept any Presentation Context for the supported SOP Classes with the supported Transfer Syntaxes. More than one proposed Presentation Context will be accepted for the same Abstract Syntax if the Transfer Syntax is supported, whether or not it is the same as another Presentation Context.

4.2.3.4.1.3.2 Transfer Syntax Selection Policies

If offered a choice of Transfer Syntaxes in a Presentation Context, DB Daemon will select the first Transfer Syntax that is listed in the Presentation Context.

DB Daemon will accept duplicate Presentation Contexts, that is, if it is offered multiple Presentation Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts, applying the same rule for selecting a Transfer Syntax for each as described above.

4.2.3.4.1.3.3 Response Status

DB Daemon will behave as described in the Table below when generating the C-STORE response command message.

Service Status

Further Meaning Error Code

Reason

Refused Out of Resources A7xx Never sent Data Set does not

match SOP Class A9xx Never sent Failure

Invalid C-STORE request

C000 Received invalid C-STORE request.

Conversion failed C101 Converting Instance from DICOM to internal data model failed.

Connection to

Database failed C102 Connecting Instance to internal data model failed. Save to Database

failed C103 Could not save Instance to DB. Reason is specified in Error Comment. Coercion of Data

Elements

B000 Never sent

Warning

Data Set does not

match SOP Class B007 Never sent Elements Discarded B006 Never sent

Success 0000 Instance successfully stored into DB

Table 4-42: Response Status of DB Daemon Storage SCP and Receive Storage Request

4.2.3.4.1.4 SOP Specific Conformance for RT Image Storage 4.2.3.4.1.4.1 Data Handling

Image Type

The following Defined Terms for Value 3 of Image Type (0008,0008) are supported: • DRR

• PORTAL • SIMULATOR

RT Image Position Parameters

As defined by the standard, it is assumed, that the Imager Position is defined by X-Ray Image Receptor Translation (3002,000D) and the image readout area by RT Image Position (3002,0012).

When RT Image Position (3002,0012) is not present, it is assumed that the image is centered around the IEC Image receptor system.

In the absence of RT Image Orientation (3002,0010), the interpretation goes along the definition in section C.8.8.2.7 of Part 3 of [1].

Portal Dose

RT Images of Image Type PORTAL are also used to represent portal doses, according to the DICOM Standard [1], PS 3, section A.17.3 (RT Image IOD Module Table), Note 2. The conversion between portal image pixel values and portal dose is defined by the Modality LUT Module through Rescale Intercept (0028,1052) and Rescale Slope (0028,1053). The unit depends on Rescale Slope (0028,1053).

The following 2 types of portal doses are supported, distinguished by their specific values for Image Type (0008,0008):

Image Type Meaning

DERIVED\SECONDARY\PORTAL\CALCULA

TED_DOSE Portal dose predicted by a treatment planning system, i.e. an estimate of the dose that will be perceived by the portal imaging device. ORIGINAL\PRIMARY\PORTAL\ACQUIRED_

DOSE Portal dose actually measured by the portal imaging device based on its calibration.

Table 4-43: Portal Dose Image Type Values and their Meaning Frame of Reference UID

RT Images that do not have a Frame of Reference UID (0020,0052) will be assigned a Frame of Reference UID. The following rules apply:

1. If other RT Images of the same Series are already on the DB, the Frame of Reference UID of an RT Image of this Series will be used.

2. If rule 1 does not apply, a new unrelated Frame of Reference UID will be generated and assigned.

4.2.3.4.1.4.2 Import Preconditions

If an RT Image references an RT Plan, this RT Plan must already be available on the DB, otherwise connection between RT Image and RT Plan will be lost.

4.2.3.4.1.5 SOP Specific Conformance for certain Image Storage SOP Classes

For SOP Classes listed in the following list DB Daemon Application Entity accepts the SOP Class, but may discard even Type 1 Attributes when storing those Instances to DB:

• Ultrasound Image Storage SOP Class

• X-Ray Angiographic Image Storage SOP Class

• Positron Emission Tomography Image Storage SOP Class

To preserve consistency of those image Instances they are converted to SC Modality, inserted into a Series of Modality OT and new Instance UIDs are issued for each Series and Image Instance.

4.2.3.4.1.6 SOP Specific Conformance for RT Structure Set Storage 4.2.3.4.1.6.1 Data Handling

An RT Structure Set serves as a starting point for 3D patient model creation. The internal representation of such a 3D patient model uses constant plane separation. If referenced images in an RT Structure Set are not scanned with constant plane separation, the constructed 3D patient model will use interpolated planes where necessary.

On import, the 3D patient model is constructed from images referenced in Contour Image Sequence (3006,0016) of the RT Structure Set Module. It is assumed, that this sequence contains all image references, which have been used to construct the 3D Volume, independent of the presence of any contours on those planes.

4.2.3.4.1.6.2 Import Preconditions

To be able to import an RT Structure Set to the DB, all images referenced in Contour Image Sequence (3006,0016) must already be available on the DB.

4.2.3.4.1.7 SOP Specific Conformance for RT Dose Storage Data Width

16 bit and 32 bit dose data is supported. This means that Bits Allocated (0028,0100) and Bits Stored (0028,0101) may contain value 16 or 32.

Dose Summation Type

The following values for Dose Summation Type (3004,000A) are supported: • PLAN

• FRACTION • BEAM

Values PLAN and FRACTION are handled identically, since only one Item in Fraction Group Sequence (300A,0070) is supported.

Dose Units

The following values for Dose Units (3004, 0002) are supported: • RELATIVE

• GY

Dose Plane Spacing

If Grid Frame Offset Vector (3004,000C) is present, it must contain offset values yielding equally spaced dose planes. Therefore, those values follow option a. in C.8.8.3.1 in Part 3 of [1]. RT Dose Instances having unequally spaced dose planes are not supported.

4.2.3.4.1.8 SOP Specific Conformance for RT Plan Storage 4.2.3.4.1.8.1 Data Handling

Beam Limiting Devices

Two collimators (symmetric or asymmetric, in any combination) or a collimator in one direction and an MLC in the direction perpendicular to it must be defined.

No more than one MLC is supported.

Wedges

Blocks

In contrary to DICOM the Varian System Server data model can handle multiple closed contours for the same block. Thus, if there are several blocks related to a single beam in imported DICOM data, they are merged into one block object if the following Attributes contain equal values among several DICOM blocks:

• Block Name (300A,00FE) • Block Divergence (300A,00FA) • Block Type (300A,00F8)

• Material ID (300A,00E1)

Control Point Parameter Changes

Changes in the following Attributes in Control Point Sequence (300A,0111) are supported: • Cumulative Meterset Weight (300A,0134)

• Wedge Position Sequence (300A,0116) • Wedge Position (300A,0118)

This change is supported only for MOTORIZED wedges in a static plan, having exactly 4 Control Points.

• Beam Limiting Device Position Sequence (300A,011A) • Leaf/Jaw Positions (300A,011C)

• Gantry Angle (300A,011E)

• Beam Limiting Device Angle (300A,0120)

Fraction Groups

Only one Fraction Group is supported, therefore only the first item of Fraction Group Sequence (300A,0070) is imported, additional ones are discarded.

Fluences

Optimal and Total Actual Fluences are exported in Compensator Sequence (300A,00E3) in RT Beams Module. Compensator Type (3004,00EE) contains either privately Defined Term OPTIMAL (for Optimal Fluence) or TOTAL_ACTUAL (for Total Actual Fluence).

4.2.3.4.1.8.2 Import Preconditions

If an RT Plan references a Bolus, the corresponding RT Structure Set must already be available on the DB.

If an RT Plan references an RT Structure Set, this RT Structure Set must already be available on the DB, otherwise connection between RT Plan and RT Structure Set will be lost.

4.2.3.4.1.8.3 Approval Status Requirements

RT Plans with Approval Status (300E,0002) APPROVED get internal status ‘Planning Approved’ when imported. For a good interoperability it is recommended that third-party applications sending RT Plans apply a validation that is at least as tight as RadOnc Client’s / Daemon’s before setting Approval Status to APPROVED.

In RadOnc Client / Daemon the following requirements (among others) have to be fulfilled to be able to change the plan status to ‘Planning Approved’:

• Jaw positions shall be defined for all existing collimators.

• If a wedge is used collimator jaw openings shall be smaller than the wedge’s dimension. • Gantry Angle (300A,011E) shall be defined.

• Patient Support Angle (300A,0122) shall be defined.

• Patient Position (0018,5100) shall be present for non-verification plans. • A block outline shall not intersect with itself.

• A block in a non-electron beam shall have a tray assigned (Block Tray ID (300A,00F5)) and defined Material ID (300A,00E1).

• Static electron fields shall have an applicator.

• If a treatment device (Treatment Machine Name (300A,00B2)) is assigned to a beam, then all beam parameters shall be within the machine’s operating limits.

• All accessories in a beam shall be enabled for the selected Nominal Beam Energy (300A,0114) and treatment technique.

• The difference between start and stop angle for an Arc treatment beam shall be greater than or equal to 1 and less than or equal to 360 degrees.

• Dose Rate Set (300A,0115) shall be the same across all control points. This is an implementation restriction of Varian treatment machines.

• Nominal Beam Energy (300A,0114) shall be the same across all control points. This is an implementation restriction of Varian treatment machines.

4.2.3.4.1.9 SOP Specific Conformance for RT Beams Treatment Record Storage and RT Ion Beams Treatment Record Storage

For RT Beams Treatment Record Storage and RT Ion Beams Treatment Record Storage this Application Entity conforms to storage service classes at level 2 (full). Therefore it is guaranteed that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition associated with the SOP Class, as well as any Standard Extended attributes (including Private Attributes) included in the SOP Instance, will be stored.

4.2.3.4.2 Activity – Handling Query and Retrieval Requests

4.2.3.4.2.1 Description and Sequencing of Activities

Figure 4-5: Sequencing of Activities – DB Daemon Handling Query Requests

A typical sequence of interactions between DB Daemon Query/Retrieve SCP and a remote Query/Retrieve SCU querying Instances is illustrated in Figure 4-5:

1. Remote AE opens Association to DB Daemon.

2. Remote AE sends one or more C-FIND Requests.

3. For every C-FIND Request DB Daemon generates a C-FIND Response containing matching results.

Figure 4-6: Sequencing of Activities – DB Daemon Handling Retrieval Requests

A typical sequence of interactions between DB Daemon Query/Retrieve SCP and a remote Query/Retrieve SCU retrieving Instances is illustrated in Figure 4-6:

1. Remote AE opens Association to DB Daemon Q/R SCP.

2. Remote AE sends a C-MOVE Request to retrieve one or more Instances.

3. DB Daemon Q/R SCP evaluates retrieve command, collects objects to send and hands them over to its Storage SCU for sending them to the desired C-MOVE destination.

4. DB Daemon Storage SCU sends one Instance to Remote Storage SCP and notifies DB Daemon Q/R SCP about success or failure of the operation.

5. DB Daemon Q/R SCP sends C-MOVE Response with Status PENDING to the Remote Q/R SCU to inform it about progress of transferring Instances.

6. DB Daemon Q/R SCP sends final C-MOVE Response.

7. Remote Q/R SCU releases Association to DB Daemon Q/R SCP

8. DB Daemon Storage SCU releases Association to Remote Storage SCP, if Association has not already been released by Remote Storage SCP.

4.2.3.4.2.2 Accepted Presentation Contexts

DB Daemon Application Entity accepts Presentation Contexts shown in the following table.

Presentation Context Table

Abstract Syntax Transfer Syntax Role

Name UID Name UID

Ext. Neg. DICOM Implicit VR Little Endian 1.2.840.10008.1.2

Study Root Query/Retrieve Information Model – FIND

1.2.840.10008.5.1.4.1.2.2.1 SCP None DICOM Explicit VR Little Endian 1.2.840.10008.1.2.1

DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Study Root

Query/Retrieve Information Model – MOVE

1.2.840.10008.5.1.4.1.2.2.2 SCP None DICOM Explicit VR Little Endian 1.2.840.10008.1.2.1

Table 4-44: Acceptable Presentation Contexts for DB Daemon Application Entity and Query/Retrieve

4.2.3.4.2.3 SOP Specific Conformance for all Query/Retrieve SOP Classes 4.2.3.4.2.3.1 Presentation Context Acceptance Criterion

4.2.3.4.2.3.2 Transfer Syntax Selection Policies

If offered a choice of Transfer Syntaxes in a Presentation Context, DB Daemon will select the first Transfer Syntax that is listed in the Presentation Context.

4.2.3.4.2.4 SOP Specific Conformance for Study Root Query SOP Classes 4.2.3.4.2.4.1 Matching Behavior

DB Daemon Query/Retrieve SCP supports the following Additional Query Levels not defined in DICOM Standard [1]. They are not required for successfully querying Instances of any supported Modality and are listed only for completeness:

• PLAN • DOSE

• TREATMENTRECORD

• TREATMENTSUMREC (which is equal to TREATMENTSUMMARYRECORD)

The following table lists the supported types of Matching for a C-FIND request on any Query Level specified by Study Root Query/Retrieve.

Name Tag VR Type Types of Matching

Study Level (Query Level STUDY)

Study Date (0008,0020) DA R S, U Study Time (0008,0030) TM R S, U Accession Number (0008,0050) SH R S, U, W Patient's Name (0010,0010) PN R S, U, W Patient ID (0010,0020) LO R S, U, W Study ID (0020,0010) SH R S, U, W

Study Instance UID (0020,000D) UI U S, U

Series Level (Query Level SERIES)

Modality (0008,0060) CS R S, U, W

Series Number (0020,0011) IS R S, U

Series Instance UID (0020,000E) UI U S, U

Composite Object Level (general)

Instance Number (0020,0013) IS R S, U

SOP Instance UID (0008,0018) UI U S, U

SOP Class UID (0008,0016) UI O S, U

Composite Object Level (Query Level IMAGE)

Image Type (0008,0008) CS O S, U

Content Date (0008,0023) DA O S, U

Content Time (0008,0033) TM O S, U

Referenced SOP Class UID (0008,1150) UI O S, U

Referenced SOP Instance UID (0008,1155) UI O S, U

Referenced Beam Number (300C,0006) IS O S, U

Reference Image Type (3257,1010) CS O S, U (see

Name Tag VR Type Types of Matching

Composite Object Level (Query Level PLAN)

Plan Label (300A,0002) SH O S, U, W

Plan Date (300A,0006) DA O S, U

Plan Time (300A,0007) TM O NONE

Number of Beams (300A,0080) IS O NONE

Referenced RT Plan Sequence (300C,0002) SQ O NONE

>Referenced SOP Class UID (0008,1150) UI O NONE

>Referenced SOP Instance UID (0008,1155) UI O NONE

>RT Plan Relationship (300A,0055) CS O NONE

Composite Object Level (Query Level DOSE)

Referenced SOP Class UID (0008,1150) UI O NONE

Referenced SOP Instance UID (0008,1155) UI O S, U

Referenced Beam Number (300C,0006) IS O S, U

Number of Frames (0028,0008) IS O NONE

Composite Object Level (Query Level TREATMENTRECORD)

Referenced SOP Class UID (0008,1150) UI O NONE

Referenced SOP Instance UID (0008,1155) UI O S, U

Treatment Date (3008,0250) DA O S, U

Treatment Time (3008,0251) TM O S, U

Referenced Fraction Group Number (300C,0022) IS O S, U Treatment Session Beam Sequence (3008,0020) SQ O NONE

In document Varian System Server. DICOM Conformance Statement (Page 49-66)