Quality Assurance with Plan Veto

Quality Assurance with Plan Veto (QAPV) QA check prior to treatment delivery for significant errors.

Summary

This supplement adds the Quality Assurance with Plan Veto (QAPV) profile to the IHE-RO Domain. The QAPV Profile describes the interaction between a Quality Check Requester and a Quality Check Performer that will force evaluation of radiation treatment data to detect and avoid severe treatment errors.

Benefits

• Provides check on treatment delivery parameters just prior to actual treatment
• Designed to verify on a parameter-by-parameter basis or by quick recalculation of treatment duration
• Evaluates treatment delivery data looking for significant errors

Details

Pre-conditions: The profile assumes some Critical Values have been defined on the Quality Check Performer. If the Critical Values have not been defined, the Quality Check Performer should accept the request to create a Unified Procedure Step to do a Quality Check, and will be required to cancel it after an initial subscription has been received. The profile also allows for the Quality Check Performer to indicate other required steps before the interactions described here can be supported. Because of the varied Critical Checks and requirements of different Quality Check Performer products, it would be prudent for Quality Check Requesters to allow for configuration of, and submission to multiple Quality Check Performers for each treatment. It is anticipated that Quality Check Performers will implement models of performing checks which may not be appropriate for all patients at a given site.

Main Flow: The Quality Assurance with Plan Veto profile describes behavior and interactions to augment safety checks during a patient’s treatment in radiation therapy:

• The QAPV Check Performer accepts a UPS Workitem for a verification action from a Check Requester
• The Check Requester subscribes to updates on the workitem.
• The Check Performer actor requests the data specified in the UPS Workitem as required to perform the evaluation. If the data is not available, or deemed insufficient, the evaluation is not performed.
• The Check Performer performs the check and prepares the resulting structured report for retrieval by the Check Requester.
• The Check Performer updates subscribers on the work that was done, including final state.
• The Check Requester gets the Output Information Sequence from the UPS maintained by the Check Performer.
• The Check Requester requests retrieval of a structured report from the Check Performer using the SOP Instance and AE Title specified in the Output Information Sequence.
• The Check Requester unsubscribes to the workitem.

Post-conditions: The Check Requester allows or prevents the treatment to proceed based on the information found in the structured report. Specific requirements on the treatment approval and override behavior can be found in the supplement.

Systems Affected

• Radiation Oncology Treatment Planning Systems
• Radiation Oncology Treatment Delivery Devices
• Radiation Oncology Treatment Management Systems
• Radiation Oncology Second Check Systems

Actors & Transactions:

Specification

Profile Status: Public Comment

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>

IHE Radiology Technical Framework:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• DICOM
• HL7
• ...

See Also

<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>

Related Profiles

<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>

• Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
• Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
• Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
• Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
• Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.

Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >

This page is based on the Profile Overview Template

<Delete this Category Templates line since your Profile page is no longer a template.>