2019
Technical Note: An open source solution for improving TG‐263 compliance
Abstract: Purpose Compliance with TG‐263 nomenclature standards can be challenging. We introduce an open source solution to this problem and evaluate its impact on compliance within our institution. Materials/methods The TG‐236 nomenclature standards were implemented in our clinic in two phases. In phase 1, we deployed TG‐263 compliant templates for each disease site. In phase 2, we developed and deployed a script for evaluating compliance which presented errors to the user. After each phase the compliance was recorded.…
Search citation statements
Paper Sections
Select...
10
5
4
1
Citation Types
0
18
0
0
Year Published
2020
2026
Publication Types
Select...
19
Relationship
2
17
Authors
Journals
Cited by 19 publications
(18 citation statements)
References 3 publications
0
18
0
0
“…The origin checker has also been released in order for clinics to have access to the full solution for preventing shift errors. These tools are part of a growing suite of open source software solutions used to improve safety and standardization in radiotherapy clinics developed at our institution …”
Section: Resultsmentioning
confidence: 99%
“…The origin checker has also been released in order for clinics to have access to the full solution for preventing shift errors. These tools are part of a growing suite of open source software solutions used to improve safety and standardization in radiotherapy clinics developed at our institution …”
Section: Resultsmentioning
confidence: 99%
“…A few publications have emerged with focus on technical approaches to either efficiently re-label retrospective data or improve TG-263 compliance going forward. 56,57 The current study details the significant variability in OAR nomenclature that was present prior to TG-263 implementation, with certain structures such as submandibular glands having over 35 name variants across institutions.…”
Section: Discussionmentioning
confidence: 99%
“…There are several open-source scripts and AI tools that can be utilized to identify errors and map structure templates to corresponding naming conventions in accordance with the TG 263 report's guidelines [ 25,26 ]. Large Language Models, for example, could be used to facilitate a quicker and easier renaming and mapping process of current structure templates, such that they abide by the guidelines [ 27 ].…”
Section: Discussionmentioning
confidence: 99%
