<!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>Why do it the hard way? The Case for an Expressive Description Logic for SNOMED</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Alan Rector</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sebastian Brandt</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Computer Science, University of Manchester</institution>
          ,
          <addr-line>Manchester M13 9PL, (rector</addr-line>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Since SNOMED-RT/CT was originally formulated
in the early to mid 1990s, there have been major
developments in logic-based formalisms, ontology
design and associated tools. Combined with the
increase in computing power in the past two
decades, these developments mean that many of the
restrictions that limited SNOMED’s original
formulation and schemas no longer need apply. We
contend that future development of SNOMED
would be made easier if a more expressive
formalism and more modern tools were adopted.
The difficulties in the existing structure of
SNOMED have been well documented. For
example, Bodenreider (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) examined the specialization
hierarchy of SNOMED classes. Schulz discussed
‘relationship groups’ (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) and a broad range of other
ontological problems along with potential remedies
(
        <xref ref-type="bibr" rid="ref3">3</xref>
        ). Schulz suggested a modest extension of
SNOMED’s formalism to one with more clearly
defined semantics (EL+) but which still lacks true
negation and disjunction. We argue here that
judicious use of a more expressive language, OWL
1.11, is now practical and would bring great
benefits including:
•
      </p>
      <p>A uniform, clear and understandable schema
for all concepts used in clinical records,
including context and negation.</p>
      <p>Elimination of the need for special
mechanisms to deal with context, partonomy, and
role groups.</p>
      <p>More effective leveraging of the underlying
logical representation to organise and quality
assure the SNOMED hierarchies.</p>
      <p>Improved ability to recognise semantic
equivalence between post-coordinated and
precoordinated expressions and between
“observables” with “values” and the corresponding
“findings.”
Improved ability to modularise and segment
SNOMED for specific purposes
Access to the tools and techniques being
developed by the wider Semantic Web and OWL
communities.
•
•
•
•
•
In outline, the proposals are:
•</p>
      <p>To represent all concepts used in clinical
records (findings, observables, and procedures)
1 http://www.webont.org/owl/1.1/
•
•
•
uniformly as fully defined “situations” that
include any context required and that deal with
negation explicitly and formally.</p>
      <p>To represent all sites explicitly as to whether
they refer to the site in its entirety or to the
disjunction of the site and its parts.</p>
      <p>
        To define observables and related findings in
such a way that the classifier can be used to
recognise the equivalence between a situation
involving an observable with a given value and
the corresponding finding of the observable
with that value – e.g., between an observable
of “blood pressure” qualified by “elevated”
and a finding of “elevated blood pressure”.
To organise the stated form as a set of modules
that can be separated for specific applications.
Details of the proposed mechanisms are described
in the extended version of this paper and in (
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ).
Although the effort to migrate any large software
object should not be underestimated, most of the
proposed changes would cause few changes to the
schemas except for “Situations with specific
context,” which are known to be problematic.
(However, the proposed analysis would identify many
errors to be corrected.) The effort would be more
than repaid by providing a more regular and
consistent system that would improve usability and
simplify software development and query formulation.
We argue that a feasibility study using a modest
subset of around 25K concepts should be an urgent
priority for the SNOMED community.
      </p>
      <p>References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bodenreider</surname>
            <given-names>O</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Smith</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burgun</surname>
            <given-names>A</given-names>
          </string-name>
          .
          <article-title>Investigating subsumption in SNOMED CT: An exploration into large description logic-based biomedical terminologies</article-title>
          .
          <source>AI in Medicine</source>
          .
          <year>2007</year>
          ;
          <volume>39</volume>
          :
          <fpage>183</fpage>
          -
          <lpage>195</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hanser</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hahn</surname>
            <given-names>U</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rogers</surname>
            <given-names>J.</given-names>
          </string-name>
          <article-title>The semantics of procedures and diseases in SNOMED CT</article-title>
          .
          <source>Meth Inf Med</source>
          .
          <year>2006</year>
          ;
          <volume>45</volume>
          :
          <fpage>354</fpage>
          -
          <lpage>358</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Schulz</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Suntisrivaraporn</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baader</surname>
            <given-names>F</given-names>
          </string-name>
          ;
          <article-title>SNOMED CT's Problem List: Ontologists' and logicians' therapy suggestions</article-title>
          .
          <source>; Medinfo</source>
          <year>2007</year>
          : IOS Press;
          <fpage>802</fpage>
          -
          <lpage>806</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Rector</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Qamar</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marley</surname>
            <given-names>T</given-names>
          </string-name>
          ;
          <article-title>Binding ontologies &amp; coding systems to electronic health records and messages</article-title>
          . 2006;
          <article-title>Formal Biomedical Knowledge Representation (KR-MED 2006</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Rector</surname>
            <given-names>AL</given-names>
          </string-name>
          ;
          <article-title>What's in a code: Towards a formal account of the relation of ontologies and coding systems</article-title>
          .
          <source>2007; Medinfo</source>
          <year>2007</year>
          : Brisbane, Australia: IOS Press;
          <fpage>730</fpage>
          -
          <lpage>734</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>