DD.3 Machine Verification SOP Class Definitions
Prev | DD RT Machine Verification Service Classes (Normative) | Next

## DD.3 Machine Verification SOP Class Definitions

### DD.3.1 IOD Description

The Machine Verification IODs are abstractions of the information needed to verify the correct setup of a treatment delivery system prior to radiation treatment.

### DD.3.2 DIMSE Service Group

Table DD.3.2-1 shows DIMSE Services applicable to the IODs.

Table DD.3.2-1. DIMSE Service Group

DIMSE Service Element | Usage SCU/SCP
--- | ---
N-CREATE | M/M
N-SET | M/M
N-GET | M/M
N-ACTION | M/M
N-DELETE | M/M
N-EVENT-REPORT | M/M

The meaning of the Usage SCU/SCP is described in Section H.2.4.

This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE services is specified in PS3.7.

#### DD.3.2.1 N-CREATE and N-SET

The N-CREATE is used to create an instance of the applicable Machine Verification SOP Class.

The N-SET is used to communicate parameters for verification to an MPV by setting Attributes on an instance of the applicable Machine Verification SOP Class.

All Attributes in the table relating to the number of a certain item (e.g., Number of Wedges, Number of Control Points) specify the number in the N-SET command. The numbering in the Beams Verification Request is not necessarily the same as the numbering in the referenced RT Plan.

##### DD.3.2.1.1 Attributes

The Attribute list of the N-CREATE and N-SET for the RT Conventional Machine Verification SOP Class is shown in Table DD.3.2.1-1. See Section 5.4 for usage notation.

Table DD.3.2.1-1. N-CREATE and N-SET Attribute List - RT Conventional Machine Verification SOP Class

Attribute Name | Tag | N-CREATE Usage SCU/SCP | N-SET Usage SCU/SCP
--- | --- | --- | ---
RT General Machine Verification Module
Referenced RT Plan Sequence | (300C,0002) | 1/1 (only a single Item shall be permitted) | Not allowed
>Referenced SOP Class UID | (0008,1150) | 1/1 | Not allowed
>Referenced SOP Instance UID | (0008,1155) | 1/1 | Not allowed
Referenced Fraction Group Number | (300C,0022) | 1C/1 (required if plan has more than one fraction group) | Not allowed
Patient ID | (0010,0020) | 1/1 | Not allowed
Include Table CC.2.5-2e “Issuer of Patient ID Macro”
Treatment Verification Status | (3008,002C) | Not allowed | Not allowed
Failed Parameters Sequence | (0074,1048) | Not allowed | Not allowed
Overridden Parameters Sequence | (0074,104A) | Not allowed | Not allowed
General Machine Verification Sequence | (0074,1042) | 2/2 (sequence shall contain zero items) | 1/1 (only a single Item shall be permitted)
>Specified Primary Meterset | (3008,0032) | -/- | 3/3
>Specified Secondary Meterset | (3008,0033) | -/- | 3/3
>Specified Treatment Time | (3008,003A) | -/- | 3/3
>Beam Limiting Device Leaf Pairs Sequence | (3008,00A0) | -/- | 3/3
>>RT Beam Limiting Device Type | (300A,00B8) | -/- | 1/1
>>Number of Leaf/Jaw Pairs | (300A,00BC) | -/- | 1/1
>Recorded Wedge Sequence | (3008,00B0) | -/- | 2C/2C (required if MPV is capable of verifying wedges). See Section DD.3.2.1.1.1.
>>Wedge Number | (300A,00D2) | -/- | 1/1
>>Wedge ID | (300A,00D4) | -/- | 3/3
>>Wedge Angle | (300A,00D5) | -/- | 3/3
>>Wedge Orientation | (300A,00D8) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>Recorded Compensator Sequence | (3008,00C0) | -/- | 2C/2C (required if MPV is capable of verifying compensators). See Section DD.3.2.1.1.1.
>>Compensator ID | (300A,00E5) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Referenced Compensator Number | (300C,00D0) | -/- | 1/1
>Recorded Block Sequence | (3008,00D0) | -/- | 2C/2C (required if MPV is capable of verifying blocks). See Section DD.3.2.1.1.1.
>>Block Tray ID | (300A,00F5) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Referenced Block Number | (300C,00E0) | -/- | 1/1
>Treatment Machine Name | (300A,00B2) | -/- | 1/1
>Beam Name | (300A,00C2) | -/- | 3/3
>Radiation Type | (300A,00C6) | -/- | 1/1
>Number of Wedges | (300A,00D0) | -/- | 1/1
>Number of Compensators | (300A,00E0) | -/- | 1/1
>Number of Boli | (300A,00ED) | -/- | 1/1
>Number of Blocks | (300A,00F0) | -/- | 1/1
>Applicator Sequence | (300A,0107) | -/- | 2C/2C (required if MPV is capable of verifying applicators). See Section DD.3.2.1.1.1.
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Applicator ID | (300A,0108) | -/- | 3/3
>>Applicator Type | (300A,0109) | -/- | 1/1
>Number of Control Points | (300A,0110) | -/- | 1/1 (value shall be 1)
>Patient Setup Sequence | (300A,0180) | -/- | 3/3 (one or more Items may be included)
>>Patient Setup Number | (300A,0182) | -/- | 1/1
>>Fixation Device Sequence | (300A,0190) | -/- | 2C/2C (required if MPV is capable of verifying fixation devices). See Section DD.3.2.1.1.1.
>>>Accessory Code | (300A,00F9) | -/- | 3/3
>>>Fixation Device Type | (300A,0192) | -/- | 1/1
>Referenced Beam Number | (300C,0006) | -/- | 1/1
>Referenced Bolus Sequence | (300C,00B0) | -/- | 2C/2C (required if MPV is capable of verifying bolus). See Section DD.3.2.1.1.1.
>>Referenced ROI Number | (3006,0084) | -/- | 1/1
>>Accessory Code | (300A,00F9) | -/- | 3/3
All other Attributes in RT General Machine Verification Module | - | -/- | 3/3
RT Conventional Machine Verification Module
Conventional Machine Verification Sequence | (0074,1044) | 2/2 (sequence shall contain zero items) | 1/1 (only a single Item shall be permitted)
>Conventional Control Point Verification Sequence | (0074,104C) | -/- | 1/1 (only a single Item shall be permitted)
>>Nominal Beam Energy | (300A,0114) | -/- | 3/3
>>Dose Rate Set | (300A,0115) | -/- | 3/3
>>Wedge Position Sequence | (300A,0116) | -/- | 1C/1C (required if Number of Wedges (300A,00D0) is non-zero,one or more Items may be included)
>>>Wedge Position | (300A,0118) | -/- | 1/1
>>>Referenced Wedge Number | (300C,00C0) | -/- | 1/1
>>Beam Limiting Device Position Sequence | (300A,011A) | -/- | 1C/1C (required if Beam Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items may be included)
>>>RT Beam Limiting Device Type | (300A,00B8) | -/- | 1/1
>>>Leaf/Jaw Positions | (300A,011C) | -/- | 1/1
>>Gantry Angle | (300A,011E) | -/- | 3/3
>>Gantry Rotation Direction | (300A,011F) | -/- | 2/2
>>Beam Limiting Device Angle | (300A,0120) | -/- | 3/3
>>Beam Limiting Device Rotation Direction | (300A,0121) | -/- | 3/3
>>Patient Support Angle | (300A,0122) | -/- | 3/3
>>Patient Support Rotation Direction | (300A,0123) | -/- | 3/3
>>Table Top Eccentric Axis Distance | (300A,0124) | -/- | 3/3
>>Table Top Eccentric Angle | (300A,0125) | -/- | 3/3
>>Table Top Eccentric Rotation Direction | (300A,0126) | -/- | 3/3
>>Table Top Vertical Position | (300A,0128) | -/- | 3/3
>>Table Top Longitudinal Position | (300A,0129) | -/- | 3/3
>>Table Top Lateral Position | (300A,012A) | -/- | 3/3
>>Table Top Pitch Angle | (300A,0140) | -/- | 3/3
>>Table Top Pitch Rotation Direction | (300A,0142) | -/- | 3/3
>>Table Top Roll Angle | (300A,0144) | -/- | 3/3
>>Table Top Roll Rotation Direction | (300A,0146) | -/- | 3/3
>>Referenced Control Point Index | (300C,00F0) | -/- | 1/1
All other Attributes in RT Conventional Machine Verification Module | - | -/- | 3/3

The Attribute list of the N-CREATE and N-SET for the RT Ion Machine Verification SOP Class is shown in Table DD.3.2.1-2.

Table DD.3.2.1-2. N-CREATE and N-SET Attribute List - RT Ion Machine Verification SOP Class

Attribute Name | Tag | N-CREATE Usage SCU/SCP | N-SET Usage SCU/SCP
--- | --- | --- | ---
RT General Machine Verification Module
Referenced RT Plan Sequence | (300C,0002) | 1/1 (only a single Item shall be permitted) | Not allowed
>Referenced SOP Class UID | (0008,1150) | 1/1 | Not allowed
>Referenced SOP Instance UID | (0008,1155) | 1/1 | Not allowed
Referenced Fraction Group Number | (300C,0022) | 1C/1 (required if plan has more than one fraction group) | Not allowed
Patient ID | (0010,0020) | 1/1 | Not allowed
Include Table CC.2.5-2e “Issuer of Patient ID Macro”
Treatment Verification Status | (3008,002C) | Not allowed | Not allowed
Failed Parameters Sequence | (0074,1048) | Not allowed | Not allowed
Overridden Parameters Sequence | (0074,104A) | Not allowed | Not allowed
General Machine Verification Sequence | (0074,1042) | 2/2 (sequence shall contain zero items) | 1/1 (only a single Item shall be permitted)
>Specified Primary Meterset | (3008,0032) | -/- | 3/3
>Specified Secondary Meterset | (3008,0033) | -/- | 3/3
>Specified Treatment Time | (3008,003A) | -/- | 3/3
>Beam Limiting Device Leaf Pairs Sequence | (3008,00A0) | -/- | 3/3 See Section DD.3.2.1.1.1.
>>RT Beam Limiting Device Type | (300A,00B8) | -/- | 1/1
>>Number of Leaf/Jaw Pairs | (300A,00BC) | -/- | 1/1
>Recorded Wedge Sequence | (3008,00B0) | -/- | 2C/2C (required if MPV is capable of verifying wedges). See Section DD.3.2.1.1.1.
>>Wedge Number | (300A,00D2) | -/- | 1/1
>>Wedge ID | (300A,00D4) | -/- | 3/3
>>Wedge Angle | (300A,00D5) | -/- | 3/3
>>Wedge Orientation | (300A,00D8) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>Recorded Compensator Sequence | (3008,00C0) | -/- | 2C/2C (required if MPV is capable of verifying compensators). See Section DD.3.2.1.1.1.
>>Compensator ID | (300A,00E5) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Referenced Compensator Number | (300C,00D0) | -/- | 1/1
>Recorded Block Sequence | (3008,00D0) | -/- | 2C/2C (required if MPV is capable of verifying blocks). See Section DD.3.2.1.1.1.
>>Block Tray ID | (300A,00F5) | -/- | 3/3
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Referenced Block Number | (300C,00E0) | -/- | 1/1
>Treatment Machine Name | (300A,00B2) | -/- | 1/1
>Beam Name | (300A,00C2) | -/- | 3/3
>Radiation Type | (300A,00C6) | -/- | 1/1
>Number of Wedges | (300A,00D0) | -/- | 1/1
>Number of Compensators | (300A,00E0) | -/- | 1/1
>Number of Boli | (300A,00ED) | -/- | 1/1
>Number of Blocks | (300A,00F0) | -/- | 1/1
>Applicator Sequence | (300A,0107) | -/- | 2C/2C (required if MPV is capable of verifying applicators). See Section DD.3.2.1.1.1.
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Applicator ID | (300A,0108) | -/- | 3/3
>>Applicator Type | (300A,0109) | -/- | 1/1
>Number of Control Points | (300A,0110) | -/- | 1/1 (value shall be 1)
>Patient Setup Sequence | (300A,0180) | -/- | 3/3 See Section DD.3.2.1.1.1.
>>Patient Setup Number | (300A,0182) | -/- | 1/1
>>Fixation Device Sequence | (300A,0190) | -/- | 2C/2C (required if MPV is capable of verifying fixation devices). See Section DD.3.2.1.1.1.
>>>Accessory Code | (300A,00F9) | -/- | 3/3
>>>Fixation Device Type | (300A,0192) | -/- | 1/1
>Referenced Beam Number | (300C,0006) | -/- | 1/1
>Referenced Bolus Sequence | (300C,00B0) | -/- | 2C/2C (required if MPV is capable of verifying bolus). See Section DD.3.2.1.1.1.
>>Referenced ROI Number | (3006,0084) | -/- | 1/1
>>Accessory Code | (300A,00F9) | -/- | 3/3
All other Attributes in RT General Machine Verification Module | - | -/- | 3/3
RT Ion Machine Verification Module
Ion Machine Verification Sequence | (0074,1046) | 2/2 (sequence shall contain zero items) | 1/1 (only a single Item shall be permitted)
>Ion Control Point Verification Sequence | (0074,104E) | -/- | 1/1 (only a single Item shall be permitted)
>>Meterset Rate Set | (3008,0045) | -/- | 3/3
>>Nominal Beam Energy | (300A,0114) | -/- | 3/3
>>Beam Limiting Device Position Sequence | (300A,011A) | -/- | 1C/1C (required if Beam Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items may be included)
>>>RT Beam Limiting Device Type | (300A,00B8) | -/- | 1/1
>>>Leaf/Jaw Positions | (300A,011C) | -/- | 1/1
>>Gantry Angle | (300A,011E) | -/- | 3/3
>>Gantry Rotation Direction | (300A,011F) | -/- | 2/2
>>Beam Limiting Device Angle | (300A,0120) | -/- | 3/3
>>Beam Limiting Device Rotation Direction | (300A,0121) | -/- | 3/3
>>Patient Support Angle | (300A,0122) | -/- | 3/3
>>Patient Support Rotation Direction | (300A,0123) | -/- | 3/3
>>Table Top Vertical Position | (300A,0128) | -/- | 3/3
>>Table Top Longitudinal Position | (300A,0129) | -/- | 3/3
>>Table Top Lateral Position | (300A,012A) | -/- | 3/3
>>Table Top Pitch Angle | (300A,0140) | -/- | 3/3
>>Table Top Pitch Rotation Direction | (300A,0142) | -/- | 3/3
>>Table Top Roll Angle | (300A,0144) | -/- | 3/3
>>Table Top Roll Rotation Direction | (300A,0146) | -/- | 3/3
>>Head Fixation Angle | (300A,0148) | -/- | 3/3
>>Gantry Pitch Angle | (300A,014A) | -/- | 3/3
>>Gantry Pitch Rotation Direction | (300A,014C) | -/- | 3/3
>>Snout Position | (300A,030D) | -/- | 3/3
>>Range Shifter Settings Sequence | (300A,0360) | -/- | 1C/1C (required if Number of Range Shifters (300A,0312) is non-zero,one or more Items may be included)
>>>Range Shifter Setting | (300A,0362) | -/- | 1/1
>>>Referenced Range Shifter Number | (300C,0100) | -/- | 1/1
>>Lateral Spreading Device Settings Sequence | (300A,0370) | -/- | 1C/1C (required if Number of Lateral Spreading Devices (300A,0330) is non-zero,one or more Items may be included)
>>>Lateral Spreading Device Setting | (300A,0372) | -/- | 1/1
>>>Referenced Lateral Spreading Device Number | (300C,0102) | -/- | 1/1
>>Range Modulator Settings Sequence | (300A,0380) | -/- | 1C/1C (required if Number of Range Modulators (300A,0340) is non-zero,one or more Items may be included)
>>>Range Modulator Gating Start Value | (300A,0382) | -/- | 1/1
>>>Range Modulator Gating Stop Value | (300A,0384) | -/- | 1/1
>>>Referenced Range Modulator Number | (300C,0104) | -/- | 1/1
>>Ion Wedge Position Sequence | (300A,03AC) | -/- | 1C/1C (required if Number of Wedges (300A,00D0) is non-zero,one or more Items may be included)
>>>Wedge Thin Edge Position | (300A,00DB) | -/- | 1C/1C (required if Wedge Type (300A,00D3) of the wedge referenced by Referenced Wedge Number (300C,00C0) is PARTIAL_STANDARD or PARTIAL_MOTORIZ)
>>>Wedge Position | (300A,0118) | -/- | 1/1
>>Referenced Control Point Index | (300C,00F0) | -/- | 1/1
>Recorded Snout Sequence | (3008,00F0) | -/- | 1C/1C (required if Snout Sequence is included in the RT Ion Plan referenced within the Referenced RT Plan Sequence (300C,0002); only a single Item is permitted in this sequence)
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Snout ID | (300A,030F) | -/- | 3/3
>Recorded Range Shifter Sequence | (3008,00F2) | -/- | 2C/2C (required if MPV is capable of verifying range shifters). See Section DD.3.2.1.1.1.
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Range Shifter ID | (300A,0318) | -/- | 3/3
>>Referenced Range Shifter Number | (300C,0100) | -/- | 1/1
>Recorded Lateral Spreading Device Sequence | (3008,00F4) | -/- | 2C/2C (required if MPV is capable of verifying lateral spreading devices). See Section DD.3.2.1.1.1.
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Lateral Spreading Device ID | (300A,0336) | -/- | 3/3
>>Referenced Lateral Spreading Device Number | (300C,0102) | -/- | 1/1
>Recorded Range Modulator Sequence | (3008,00F6) | -/- | 2C/2C (required if MPV is capable of verifying range modulators). See Section DD.3.2.1.1.1.
>>Accessory Code | (300A,00F9) | -/- | 3/3
>>Range Modulator ID | (300A,0346) | -/- | 3/3
>>Range Modulator Type | (300A,0348) | -/- | 1/1
>>Beam Current Modulation ID | (300A,034C) | -/- | 1C/1C (required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS)
>>Referenced Range Modulator Number | (300C,0104) | -/- | 1/1
>Radiation Mass Number | (300A,0302) | -/- | 1C/1C (required if Radiation Type (300A,00C6) is ION)
>Radiation Atomic Number | (300A,0304) | -/- | 1C/1C (required if Radiation Type (300A,00C6) is ION)
>Radiation Charge State | (300A,0306) | -/- | 1C/1C (required if Radiation Type (300A,00C6) is ION)
>Scan Mode | (300A,0308) | -/- | 1/1
>Number of Range Shifters | (300A,0312) | -/- | 1/1
>Number of Lateral Spreading Devices | (300A,0330) | -/- | 1/1
>Number of Range Modulators | (300A,0340) | -/- | 1/1
>Patient Support Type | (300A,0350) | -/- | 3/3
>Patient Support ID | (300A,0352) | -/- | 3/3
>Patient Support Accessory Code | (300A,0354) | -/- | 3/3
>Fixation Light Azimuthal Angle | (300A,0356) | -/- | 3/3
>Fixation Light Polar Angle | (300A,0358) | -/- | 3/3
All other Attributes in RT Ion Machine Verification Module | - | -/- | 3/3

###### DD.3.2.1.1.1 Beam Modifiers

If the MPV is not capable of performing the type of verification required by the Attribute, then the Attribute shall not be present. If the MPV is capable of performing the type of verification required by the Attribute, then the Attribute will be zero length if there are no such modifiers, and valued with one or more items if there are one or more such modifiers.

##### DD.3.2.1.2 Status

The status values for N-CREATE that are specific for these SOP Classes are defined as follows:

Table DD.3.2.1.2-1. RT Ion Machine Verification SOP Class N-CREATE Status Values

Status | Meaning | Code
--- | --- | ---
Success | Machine Verification successfully created | 0000
Failure | No such object instance - Referenced RT Plan not found | C227
The Referenced Fraction Group Number does not exist in the referenced plan | C221
No beams exist within the referenced fraction group | C222
SCU already verifying and cannot currently process this request. | C223

The status values for N-SET that are specific for these SOP Classes are defined as follows:

Table DD.3.2.1.2-2. RT Ion Machine Verification SOP Class N-SET Status Values

Status | Meaning | Code
--- | --- | ---
Success | Machine Verification successfully updated | 0000
Failure | Referenced Beam Number not found within the referenced Fraction Group | C224
Referenced device or accessory not supported | C225
Referenced device or accessory not found within the referenced beam | C226

##### DD.3.2.1.3 Behavior

###### DD.3.2.1.3.1 N-CREATE

The SCU uses N-CREATE to request the SCP to create an applicable Machine Verification SOP Instance. The SCP shall create the SOP Instance and shall initialize Attributes of the SOP Class.

The General Machine Verification Sequence, Conventional Machine Verification Sequence, and Ion Machine Verification Sequence are created with an empty value, and specification of the contained Attributes is deferred until the N-SET operation.

The SCP shall return the status code of the requested SOP Instance creation. The meaning of success, warning and failure status codes is defined in Section DD.3.2.1.2.

###### DD.3.2.1.3.2 N-SET

The SCU uses the N-SET to request the SCP to update an applicable Machine Verification instance. The SCU shall specify the SOP Instance to be updated and shall specify the list of Attributes for which the Attribute Values are to be set. The Attributes in the Conventional/Ion Control Point Verification Sequence represent the Treatment Delivery System's actual geometric values at the time the N-SET request is issued and therefore, the Conventional/Ion Control Point Verification Sequence shall always contain one sequence item. The Referenced Control Point Index shall be zero for NORMAL treatments, and may be greater than zero for CONTINUATION treatments.

Within an Attribute sequence such as the General Machine Verification Sequence, Conventional Machine Verification Sequence, and Ion Machine Verification Sequence, values for all required Attributes must be supplied with each N-SET, or else the missing Attributes will have any previously set values removed from the SOP Instance. Existing parameters may be cleared by sending an empty sequence or Attribute. The MPV's Conformance Statement shall specify the set of Attributes that it requires for verification.

The SCU shall set the new values for the specified Attributes of the specified SOP Instance. The SCP shall then compare the values of Attributes of the specified SOP Instance to the values of the same Attributes found in the RT Plan referenced in N-CREATE. Values shall be compared using the tolerance values also found in the referenced RT Plan. The result of this comparison shall be available for use when the SCU requests the Treatment Verification Status using an N-GET.

#### DD.3.2.2 N-GET

The N-GET is used to get the verification status and results of the applicable Machine Verification SOP Class.

##### DD.3.2.2.1Verification Parameters Selector Attribute Macro

Table DD.3.2.2.1-1 describes N-GET support requirements for the Selector Attribute Macro. See Section 5.4 for requirements type code meaning.

Table DD.3.2.2.1-1. Verification Parameters Selector Attribute Macro

Attribute Name | Tag | Req. Type N-GET (SCU/SCP)
--- | --- | ---
Selector Attribute | (0072,0026) | -/1
Selector Value Number | (0072,0028) | -/1
Selector Sequence Pointer | (0072,0052) | -/1
Selector Sequence Pointer Private Creator | (0072,0054) | -/1
Selector Sequence Pointer Items | (0074,1057) | -/1
Selector Attribute Private Creator | (0072,0056) | -/1

##### DD.3.2.2.2 Attributes

The Attribute list of the N-GET for the RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class is shown in Table DD.3.2.2.2-1. See Section 5.4 for usage notation.

Table DD.3.2.2.2-1. N-GET Attribute List- RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class

Attribute Name | Tag | Usage SCU/SCP
--- | --- | ---
Referenced RT Plan Sequence | (300C,0002) | -/1
>Referenced SOP Class UID | (0008,1150) | -/1
>Referenced SOP Instance UID | (0008,1155) | -/1
Referenced Fraction Group Number | (300C,0022) | -/1
Patient ID | (0010,0020) | -/1
Include Table CC.2.5-2e “Issuer of Patient ID Macro”
Treatment Verification Status | (3008,002C) | -/1
Failed Parameters Sequence | (0074,1048) | -/2 (zero or more items shall be included in this Sequence)
>Include Table DD.3.2.2.1-1 “Verification Parameters Selector Attribute Macro”
Overridden Parameters Sequence | (0074,104A) | -/2 (zero or more items shall be included in this Sequence)
>Include Table DD.3.2.2.1-1 “Verification Parameters Selector Attribute Macro”
>Operators' Name | (0008,1070) | -/2
>Override Reason | (3008,0066) | -/2
All other Attributes | - | 3/2

##### DD.3.2.2.3 Status

The status values that are specific for these SOP Classes are defined as follows:

Table DD.3.2.2.3-1. RT Conventional Machine and RT Ion Machine Verification SOP Class N-GET Status Values

Status | Meaning | Code
--- | --- | ---
Success | Treatment Verification Status of the applicable Machine Verification instance successfully returned. | 0000
Failure | No such object instance - applicable Machine Verification instance not found | C112

##### DD.3.2.2.4 Behavior

The SCU uses N-GET to retrieve from the SCP the verification status and results of the applicable Machine Verification SOP Instance.

The SCP shall return the Treatment Verification Status (3008,002C) Attribute as well as the status code of the requested SOP Instance update. Treatment Verification Status shall have one of the following values:

VERIFIED = treatment verified

VERIFIED_OVR = treatment verified with at least one out-of-range value overridden

NOT_VERIFIED = verification of treatment was not successful

The VERIFIED state indicates that all required parameters have been checked and no out-of-range values have been detected. The VERIFIED_OVR state indicates that the treatment failed to verify due to one or more out-of-range values that were then overridden. NOT_VERIFIED indicates that one of more of the out-of-range values has not yet been overridden and the treatment cannot go ahead. This could be because at least one out-of-range value was detected, or one or more values required for verification were not supplied. The site- and vendor-specific configuration of the MPV determines the Attributes and ranges required for successful verification.

If the Treatment Verification Status is VERIFIED_OVR, one or more parameter occurrences shall be returned in Overridden Parameters Sequence (0074,104A), otherwise the sequence shall be empty.

If the Treatment Verification Status is NOT_VERIFIED, one or more parameter occurrences shall be returned in Failed Parameters Sequence (0074,1048), otherwise the sequence shall be empty.

See Section C.31.1.1 “Failed Parameters and Overridden Parameters” in PS3.3 for specification of how the Attribute tags and position within a sequence are encoded.

The SCP shall return the status code of the requested action. The meanings of success, warning and failure status codes are defined in Section DD.3.2.2.3.

#### DD.3.2.3 N-ACTION

The N-ACTION is used to initiate parameter verification of an instance of the applicable Machine Verification SOP Class.

##### DD.3.2.3.1 Attributes

The action types of the N-ACTION are defined as shown in Table DD.3.2.3-1.

Table DD.3.2.3-1. Action Event Information

Action Type Name | Action Type ID | Attribute | Tag | Usage SCU/SCP
--- | --- | --- | --- | ---
Request Beam Verification | 1 | None | - | -

##### DD.3.2.3.2 Status

The status values that are specific for these SOP Classes are defined in Table DD.3.2.3-2.

Table DD.3.2.3-2. RT Conventional Machine and RT Ion Machine Verification SOP Class N-ACTION Status Values

Status | Meaning | Code
--- | --- | ---
Success | Machine Parameter Verification of the applicable Machine Verification instance successfully initiated. | 0000
Failure | No such object instance - Machine Verification requested instance not found. | C112

##### DD.3.2.3.3 Behavior

The SCU uses N-ACTION to instruct the SCP to initiate machine parameter verification of the applicable Machine Verification SOP Instance.

#### DD.3.2.4 N-DELETE

The N-DELETE is used to delete an instance of the applicable Machine Verification SOP Class.

##### DD.3.2.4.1 Attributes

There are no specific Attributes.

##### DD.3.2.4.2 Status

There are no specific status codes.

##### DD.3.2.4.3 Behavior

The SCU uses the N-DELETE to request the SCP to delete an applicable Machine Verification SOP Instance. The SCU shall specify in the N-DELETE request primitive the SOP Instance UID of the applicable Machine Verification instance.

The SCP shall delete the specified SOP Instance, such that subsequent operations of the same SOP Instance will fail.

The SCP shall return the status code of the requested SOP Instance deletion. The meanings of success, warning, and failure status classes are defined in Annex C “Status Type Encoding (Normative)”.

If an N-DELETE is not issued, the SOP Class instance may be deleted on the SCP by a manual or automatic operation. This behavior is beyond the scope of the standard.

#### DD.3.2.5 N-EVENT-REPORT

The N-EVENT-REPORT is used by the MPV to notify the TDS of the status of the verification task (successful or otherwise), or to notify the TDS that a verification is pending (in progress). The encoding of Notification Event Information is defined in PS3.7.

##### DD.3.2.5.1 Attributes

The arguments of the N-EVENT-REPORT are defined as shown in Table DD.3.2.5-1.

Table DD.3.2.5-1. Notification Event Information

Event Type Name | Event Type ID | Attribute | Tag | Usage SCU/SCP
--- | --- | --- | --- | ---
Pending | 1 | None | - | -
Done | 2 | Treatment Verification Status | (3008,002C) | -/1

##### DD.3.2.5.2 Status

There are no specific status codes.

##### DD.3.2.5.3 Behavior

The SCP uses the N-EVENT-REPORT to inform the SCU of the verification status. See Section BBB.3 “Use Cases” in PS3.17 .

If the Event Type ID = 1 then the verification is still in progress, and the SCU must wait until another event is received. See Section BBB.3.2.2 “Transactions and Message Flow” in PS3.17 .

If the Event Type ID = 2 then the verification process has been completed. The SCU may use the returned value of the Treatment Verification Status (3008,002C) to determine whether or not the beam is ready to be delivered, or if a machine adjustment or override needs to be made. See Section BBB.3.2.2 “Transactions and Message Flow” in PS3.17 .

Prev | Up | Next
DD.2 RT Machine Verification Model | Home | EE Display System Management Service Class (Normative)