DICOM PS3.17 2017a - Explanatory Information

BBB.3.2 Treatment Delivery Normal Flow - External Verification
Prev | BBB.3 Use Cases | Next

### BBB.3.2 Treatment Delivery Normal Flow - External Verification

#### BBB.3.2.1 Message Sequencing

Figure BBB.3.2.1-1 illustrates a message sequence example in the case where a treatment procedure delivery is requested and performed by a conventional delivery device requiring an external verification capability.

In the case where external verification is requested (i.e., where the UPS Requested Procedure Code Sequence item has a value of "RT Treatment With External Verification"), the information contained in the UPS and potentially other required delivery data must be communicated to the Machine Parameter Verifier (MPV). In many real-world situations the Oncology Information System fulfills both the role of the TMS and the MPV, hence this communication is internal to the device and not standardized. If separate physical devices perform the two roles, the communication may also be non-standard, since these two devices must be very closely coupled.

Elements in bold indicate the additional messages required when the Machine Parameter Verifier is charged with validating the beam parameters for each beam, prior to radiation being administered. These checks can be initiated by the User on a beam-by-beam basis ('manual sequencing', shown with the optional 'Deliver Beam x' messages), or can be performed by the Machine Parameter Verifier without intervention ('automatic sequencing'). The TDS would typically store an RT Treatment Record SOP Instance after each beam.

This example illustrates the case where photon or electron beams are being delivered. If ion beams are to be delivered, instances of the RT Conventional Machine Verification IOD will be replaced with instances of the RT Ion Machine Verification IOD.

Delivery of individual beams can be explicitly requested by the User (as shown in this example), or sequenced automatically by the TDS.

Prev | Up | Next
BBB.3 Use Cases | Home | BBB.3.2.2 Transactions and Message Flow

DICOM PS3.17 2017a - Explanatory Information