In the RT Machine Verification Model, the Service Class User (SCU) of the applicable Machine Verification Service Class is the radiation delivery system used to administer the treatment. The Machine Parameter Verifier (MPV) acts in the role of Service Class Provider (SCP).
The communication states between the SCU and SCP can be described in two levels shown in Figure DD. 2-1: A) the Plan Level and B) the Beam Level.
The first level (A in the diagram) is the Plan Level. The SCU initializes external verification of a new plan using the N-CREATE command. The MPV then retrieves the data necessary to perform verification through DICOM or other means. In general, there is a close relationship between an MPV and a Treatment Management System (TMS) or Archive. If DICOM is the protocol used to retrieve this data, this might be done using one or more C-MOVEs on the Archive.
The second level (B in the diagram) is the Beam Level. The SCU uses the N-SET command request to instruct the SCP on the specified attributes to be verified. The SCU then requests that the verification start using an N-ACTION command. The SCP compares the values of the specified attributes against the values of the attributes from the referenced plan, and signals the status of the verification using N-EVENT-REPORT command with the Treatment Verification Status (3008,002C) attribute indicating the verification result. The MPV’s use of tolerance values in the verification process shall be described in a Conformance Statement. The SCU may then optionally request the beam’s verification parameters using an N-GET.
Finally, when all beams have been delivered or abandoned, the SCU terminates the verification session at the Plan Level using an N-DELETE.
Figure DD.2-1 RT Verification Data Flow