Quality Management for Radiation Oncology In-House Software Products

Sua Yoo, P. Antoine, Chunhao Wang, Sheng Yang, Jackie Wu, Joseph T. Kowalski, Qiuwen Wu, F Yin, William GilesBioengineering 2025 · DOI

TL;DR

This paper introduces a standardized In-House Software Quality Management (ISQM) program designed to ensure the safety, accuracy, and reliability of custom software used in radiation oncology. By integrating rigorous quality assurance (QA) processes with comprehensive documentation, the ISQM program aims to provide continuous oversight and support for these critical clinical tools.

What Problem Does This Paper Address?

Radiation oncology increasingly relies on sophisticated software, including custom-developed "in-house" solutions, to enhance treatment planning, delivery, and overall patient care. While commercial software often comes with established quality control measures, in-house software, developed by institutions themselves, can lack a standardized framework for ensuring quality. This can lead to potential risks in patient safety, data integrity, and long-term maintainability, especially as software evolves and developers change. The paper addresses the need for a systematic approach to manage the quality of these in-house software products, bridging the gap between development and safe clinical deployment.

Methods

The core of the ISQM program is built upon two key pillars: Quality Assurance (QA) and comprehensive documentation.

The QA component involves a multi-stage process:

  • Code Review: An independent reviewer, with technical expertise, scrutinizes the software's algorithm and source code for defects, organizational issues, and documentation quality. This ensures long-term viability and supports future updates.
  • Acceptance Testing: This phase verifies that the software functions correctly and meets its specifications in a clinical environment, acting as a preliminary check before more rigorous testing.
  • Commissioning: This is a crucial step to ensure the software meets clinical requirements for safe and effective operation. It involves comprehensive testing of typical and edge-case clinical scenarios, dose calculation accuracy, reproducibility, and end-to-end workflow integration.
  • Routine QA: A streamlined version of commissioning, performed periodically or after software updates, to ensure consistent performance and accuracy.

The documentation component mandates the creation of several key documents:

  • Product Report: A primary document detailing the software's scope, aims, technology specifications, personnel involved, and required resources.
  • Product Manual: A user-friendly guide with step-by-step instructions for operating the software.
  • QA Documents: Records of QA procedures, test results, and checklists.
  • Release Notes: Summaries of new features and bug fixes for each software version.
  • Version Control: A system for managing file names and storage locations of software versions.
  • Log: A centralized record of all software-related activities.

Datasets

Not discussed in the paper. The paper focuses on the framework for managing software quality rather than the datasets used to train or evaluate specific AI models.

Key Insights and Ideas

  • Proactive vs. Reactive Maintenance: The paper emphasizes that in radiation oncology, software maintenance must be proactive, not just reactive to issues. This means building quality into the development process from the start.
  • Standardization is Key: The ISQM program provides a much-needed standardized framework, moving away from ad-hoc QA practices to ensure consistency across all in-house software.
  • Documentation as a Pillar: Comprehensive documentation is not an afterthought but an integral part of the quality management process, crucial for user training, troubleshooting, and long-term support.
  • Collaboration is Essential: The success of the ISQM program relies on close collaboration between developers, QA personnel, IT staff, and end-users.
  • Adaptability of the Framework: While initially developed for Eclipse scripting tools, the ISQM program is designed to be adaptable to a wide range of in-house software, including AI-driven applications.

Key Results

The ISQM program was successfully developed and piloted on an in-house software product named "AutoSetupFields" (version 1.0). This pilot implementation demonstrated the program's ability to integrate QA and documentation requirements. The process involved code review, acceptance testing combined with commissioning, and the creation of all required documentation. A limitation was identified where the software failed if a setup field already existed in a plan; instead of immediate modification, this was documented in the manual for future release, showcasing a pragmatic approach to managing issues. The program has since been applied to other existing in-house software products, and compliance is now mandatory for all new software releases.

Limitations and Future Work

  • Expertise Requirement: The paper acknowledges that the ISQM program requires adequate expertise within the institution to staff roles like code reviewers and developers. Loss of this expertise could disrupt patient care if critical software cannot be maintained.
  • Disruption Scenarios: The authors anticipate challenging scenarios such as software incompatibility with updated clinical environments, departure of original developers, or the need to train new staff. The ISQM program is designed to mitigate these risks, but ongoing vigilance and adaptation will be necessary.
  • Future Work: While not explicitly detailed as future work, the paper implies that the ISQM program will continue to evolve and be applied to an increasing number of in-house software products, including AI tools, ensuring their safe and effective integration into clinical workflows. The focus on AI tools suggests a future where the ISQM framework will be crucial for managing the quality of these advanced applications.

Summary updated

Abstract

(1) Objective: To develop and implement an in-house software quality management (ISQM) program to ensure the continuous, consistent quality of in-house software products. (2) Methods: The ISQM program consists of two key components: quality assurance (QA) and comprehensive documentation. The QA component involves code review, acceptance testing, commissioning, and routine quality checks. Documentation requirements encompass a product report, user manual, QA procedures and reports, release notes, version control, and logs. For each software product, the QA process must be completed, and all required documentation must be finalized before clinical deployment. (3) Results: The ISQM program was successfully developed and retrospectively implemented for existing software products. Future software products will adhere to the ISQM framework, ensuring compliance before clinical release. (4) Conclusions: This study demonstrates the successful development and implementation of the ISQM program-a standardized framework for managing the quality of in-house software products. The ISQM program ensures continuous and consistent oversight, playing a critical role in guaranteeing safe and high-quality patient care in the field of radiation oncology.
BibTeX
@inproceedings{yoo2025quality,
  author = {Sua Yoo and P. Antoine and Chunhao Wang and Sheng Yang and Jackie Wu and Joseph T. Kowalski and Qiuwen Wu and F Yin and William Giles},
  title = {{Quality Management for Radiation Oncology In-House Software Products}},
  booktitle = {Bioengineering},
  year = {2025},
  doi = {10.3390/bioengineering12040352},
}

Loading related content...

Figure