<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Building a Radiation Therapy Ontology</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mark Phillips</string-name>
          <xref ref-type="aff" rid="aff5">5</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Andre Dekker</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Charles Mayo</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Peter Gabriel</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jonathan P. Bona</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          ,
          <addr-line>Maastricht</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Maastricht University Medical Centre</institution>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of Arkansas</institution>
          ,
          <addr-line>Little Rock, AR</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Michigan</institution>
          ,
          <addr-line>Ann Arbor, MI</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>University of Pennsylvania</institution>
          ,
          <addr-line>Philadelphia, PA</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
        <aff id="aff5">
          <label>5</label>
          <institution>University of Washington</institution>
          ,
          <addr-line>Seattle, WA</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This poster reports on our ongoing work to develop a Radiation Therapy Ontology (RTO) designed according to OBO Foundry principles. This work aims to produce an ontology describing the domain of radiation therapy concerned primarily with the processes and equipment used to deliver therapeutic radiation in a clinical setting. Currently in radiation oncology, around 3% of patients are enrolled in clinical trials. Major hurdles to involving more patients include the work required to identify potential enrollees, collecting the data, and transforming data to meet protocol requirements. Axiomatically rich ontologies are uniquely positioned to serve as a bridge between the precision needed in clinical trials and the reality of electronic health records. This work is also motivated by the recent push for standardization in radiation oncology, and the realization that progress in clinical practice requires better access to clinical data. RTO aims to be useful in bridging institutional and clinical practice differences. The proliferation of standard terminologies can be at odds with each other and with existing data labels. Currently, nearly all patient data are in relational databases with no overall uniformity with respect to schemas, tables, column names and value sets. The structure of these databases is most often controlled by the vendors, and in those cases where institutions tailor the names and variables, there are no fixed standards. The upshot is that one must expect that for nearly every application, some transformation of the data will be needed.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In modeling this domain, RTO uses terms
from existing ontologies, including the Chemical
entities of Biological Interest; Ontology for
General Medical Science; Ontology for
Biomedical Investigations; and more.</p>
      <p>One aspect of the RTO is its inclusion of
classes describing medical imaging devices and
techniques. In radiation therapy, these are used to
assist in the planning, evaluation, and delivery of
RT. A solid description of these processes and
devices is very important for the RT domain.</p>
      <p>Another key area for RTO is defining,
connecting, and distinguishing between, plan
specifications for radiation therapy and processes
such as the delivery of radiation therapy. The
Information Artifact Ontology has been
indispensable for this.</p>
      <p>A challenge has been the lack of precise
consensus definitions for some critical concepts
in RT, caused by the rapid evolution of the field
over the last few decades and the widespread
medical propensity for multiple, overlapping
terms and practices. An example is
Intensitymodulated radiation therapy (IMRT), where
defining characteristics of the technique can vary,
from the type of algorithm used, the number of
beams, the motion of the radiation therapy device
and whether the RT is delivered during surgical
resection. Institutional classifications, historic
preferences and billing protocols can also result
in differences regarding which technique label is
used for a given radiation therapy. In defining the
IMRT class, we focused on necessary criteria,
including the use of at least one control point and
the use of a multi-leaf collimator, allowing for the
possibility that users of the ontology may develop
more detailed definitions as part of a site-specific
application ontology.</p>
      <p>We will submit RTO for consideration as an
OBOF candidate once a 1.0 release is complete.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>