ArticleAdvances in radiation oncology
A Safe and Practical Cycle for Team-Based Development and Implementation of In-House Clinical Software.
Article in Advances in radiation oncology. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 11 papers.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
11 citing papers in PubMed, 8 citations in OpenAlex.
- Clinical implementation of automated IMRT/VMAT planning for lung cancer radiation therapy using the expedited constrained hierarchical optimization (ECHO) system.Radiotherapy and oncology : journal of the European Society for Therapeutic Radiology and Oncology · 2026Article
- AI-assisted software development for brachytherapy seed inventory management.Journal of applied clinical medical physics · 2026Article
- Software engineers develop better clinical applications than physicists with coding skills.Journal of applied clinical medical physics · 2026Article
- Sensitivity and concordance study of an open source EPID-based linear accelerator test suite.Journal of applied clinical medical physics · 2026Article
- Checklist and quality assurance tools for integration of two radiation oncology information systems (ROISs).Journal of applied clinical medical physics · 2026Article
- Responsible Artificial Intelligence governance in oncology.NPJ digital medicine · 2025Article
- Quality Management for Radiation Oncology In-House Software Products.Bioengineering (Basel, Switzerland) · 2025Article
- Survey in radiation oncology departments in Germany, Austria, and Switzerland: state of digitalization by 2023.Strahlentherapie und Onkologie : Organ der Deutschen Rontgengesellschaft ... [et al] · 2024Article
- Advancing the Production of Clinical Medical Devices Through ChatGPT.Annals of biomedical engineering · 2024Article
- Automated VMAT treatment planning using sequential convex programming: algorithm development and clinical implementation.Physics in medicine and biology · 2023Article
- RAdiotherapy Dose Accumulation Routine (RADAR)-A Novel Dose Accumulation Script With Built-In Uncertainty.Practical radiation oncologyArticle
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
12 authors at 1 institution in 1 country.
Funding
Abstract
purposeDue to a gap in published guidance, we describe our robust cycle of in-house clinical software development and implementation, which has been used for years to facilitate the safe treatment of all patients in our clinics. METHODS AND MATERIALS: Our software development and implementation cycle requires clarity in communication, clearly defined roles, thorough commissioning, and regular feedback. Cycle phases include design requirements and use cases, development, physics evaluation testing, clinical evaluation testing, and full clinical release. Software requirements, release notes, test suites, and a commissioning report are created and independently reviewed before clinical use. Software deemed to be high-risk, such as those that are writable to a database, incorporate the use of a formal, team-based hazard analysis. Incident learning is used to both guide initial development and improvements as well as to monitor the safe use of the software.
resultsOur standard process builds in transparency and establishes high expectations in the development and use of custom software to support patient care. Since moving to a commercial planning system platform in 2013, we have applied our team-based software release process to 16 programs related to scripting in the treatment planning system for the clinic.
conclusionsThe principles and methodology described here can be implemented in a range of practice settings regardless of whether or not dedicated resources are available for software development. In addition to teamwork with defined roles, documentation, and use of incident learning, we strongly recommend having a written policy on the process, using phased testing, and incorporating independent oversight and approval before use for patient care. This rigorous process ensures continuous monitoring for and mitigatation of any high risk hazards.
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.