DICOM PS3.17 2020a - Explanatory Information

BBB.3.3.2 Transactions and Message Flow (Current)
Prev | BBB.3.3 Treatment-delivery With External Verification - Override Or Additional Info Required | Next

#### BBB.3.3.2 Transactions and Message Flow

This section describes in detail the interactions illustrated in Figure BBB.3.3.1-1.

1. 'Deliver Beam x' on TDS console (optional step)

   See use case BBB.3.2.

2. Create RT Conventional Machine Verification Instance

   See use case BBB.3.2.

3. Set 'Beam x' RT Conventional Machine Verification Instance

   See use case BBB.3.2.

4. Initiate Machine Verification

   See use case BBB.3.2.

5. Verify Machine Parameters

   The MPV then attempts to verify the treatment parameters for 'Beam x'. The MPV determines that one or more treatment parameters are out-of-tolerance, or that information such as a bar code is missing. It sends an N-EVENT-REPORT signal to the TDS with an Event Type of Done and an RT Machine Verification Status of NOT_VERIFIED. The MPV also shows the reason for the override/information request on its display (5a).

6. Supply Override Instruction or Bar Code

   The User observes on the MPV console that an override or missing information is required, and supplies the override approval or missing information to the MPV via its user interface, or equivalent proxy.

7. Initiate Machine Verification

   The TDS performs another N-ACTION on the RT Conventional Machine Verification SOP Instance to indicate that the TDS is once again ready for treatment verification. See use case BBB.3.2. This may be initiated by the user (as shown in this example), or may be initiated automatically by the TDS using a polling approach.

8. Re-verify Machine Parameters

   The MPV verifies the treatment parameters, and determines that all parameters are now within tolerance and all required information is supplied. It sends an N-EVENT-REPORT signal to the TDS with an Event Type of Done and an RT Machine Verification Status of VERIFIED_OVR.

   ### Note

   If another verification failure occurs, the override cycle can be repeated as many times as necessary.

9. Get RT Conventional Machine Verification (optional step)

   See use case BBB.3.2. If an N-GET is requested, the parameters that were overridden are available in Overridden Parameters Sequence (0074,104A).

   The TDS then delivers the therapeutic radiation.

10. Store 'Beam x' RT Beams Treatment Record to Archive

    See use case BBB.3.2. Overridden parameters are ultimately captured in the treatment record.

11. Delete RT Conventional Machine Verification Instance

    See use case BBB.3.2.

Prev | Up | Next
BBB.3.3 Treatment-delivery With External Verification - Override Or Additional Info Required | Home | BBB.3.4 Treatment-delivery With External Verification - Machine Adjustment Required

DICOM PS3.17 2020a - Explanatory Information