<!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>Controlled Natural Language for Clinical Practice Guidelines?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Richard N. Shi man</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>George Michel</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Krauthammer</string-name>
          <email>michael.krauthammerg@yale.edu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Norbert E. Fuchs</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kaarel Kaljurand</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tobias Kuhn</string-name>
          <email>tkuhng@ifi.uzh.ch</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Informatics and Institute of Computational Linguistics, University of Zurich</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>School of Medicine, Yale University</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Clinicians would bene t from decision support systems incorporating the knowledge of clinical practice guidelines. However, the unstructured form of the guidelines makes them unsuitable for formal representation. To remedy this shortcoming we translated a set of pediatric guidelines into Attempto Controlled English (ACE). An experienced pediatrician and a knowledge engineer assessed that ACE can accurately represent the clinical concepts and the proposed actions of the guidelines. Currently, we are developing a systematic and replicable approach to authoring guideline recommendations in ACE.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Clinical practice guidelines are de ned as \systematically developed statements
to assist practitioner and patient decisions about appropriate healthcare for
speci c clinical circumstances" [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Guidelines are developed by teams of clinical
experts who systematically review and appraise the relevant biomedical literature
and apply rigorous methods to link recommendations about appropriate care to
the supporting scienti c evidence. More than 4000 guidelines have been
published by various organizations. The large number of guidelines impedes their
practical application by clinicians who would pro t from computerized decision
support.
      </p>
      <p>
        However, there is a mismatch between the unstructured narrative form of the
published guidelines and the formality that is necessary for the operationalization
of guideline knowledge [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Uncritical translation of such recommendations into
computable statements risks distortion of the guideline authors' intent [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ].
      </p>
      <p>
        In order to address this problem, we investigate writing guidelines in
Attempto Controlled English (ACE) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. ACE is a controlled natural language, i.e.
guideline development
      </p>
      <p>guideline application
domain experts committee</p>
      <p>clinician
expertise
authoring tool
decisions &amp;
feedback
recommendations
formal
guidelines
decision
support
system
patient
data</p>
      <p>electronic
health record
system
a precisely de ned subset of English with restrictions on vocabulary and
grammar. These restrictions result in increased terminological consistency, reduced
ambiguity, consistent vocabulary, potentially templated phrases, and a generally
simpli ed sentence and text structure. ACE has the additional bene t of being
supported by a parsing engine that translates ACE texts into rst-order logic,
thereby providing a computable format and supporting automatic reasoning.</p>
      <p>In the initial phases of the ERGO Project (E ective Representation of
Guidelines with Ontologies)3 we will demonstrate the feasibility of translating guideline
knowledge into rules. We propose to use ACE as an intermediary representation
between the implicit knowledge contained in the minds of the domain experts and
the representation of that knowledge in an explicit computable form. Our goal
is to develop an authoring tool that helps guideline authors to reduce ambiguity,
vagueness, incompleteness, and inconsistency, and facilitates the translation of
guideline recommendations into logic statements that can be implemented in
decision support systems. These systems generally depend on production rules
derived from guideline recommendations to create a knowledge base. The
decision support system compares an individual patient's characteristics
(demographic descriptors and clinical ndings) against these rules to guide a health
provider by o ering patient-speci c and situation-speci c advice. A second goal
is to demonstrate that ACE is a good candidate controlled natural language
for writing recommendations. Figure 1 shows the general architecture of our
approach.</p>
    </sec>
    <sec id="sec-2">
      <title>3 http://gem.med.yale.edu/ergo/</title>
      <p>If an infant or young child 2 months to 2 If
years of age with unexplained fever is assessed the patient is a young child who has an unexplained fever and
as being su ciently ill to warrant immedi- the patient is su ciently-ill
ate antimicrobial therapy, a urine specimen then
should be obtained by SPA or transurethral the clinician should analyze a culture of a urine-specimen
bladder catheterization; [...] (strength of evi- that is obtained-by SPA or
dence: good). that is obtained-by Transurethral-catheterization.
2</p>
      <p>
        Expressing Clinical Practice Guidelines in ACE
We plan to use ACE to encode the summary recommendation statements that
form the backbone of guideline documents. Often published in boldface, these
recommendation statements embody the critical knowledge about appropriate
practice that is ampli ed by supporting text. A rst critical step is to establish
whether clinical guidelines can be adequately expressed in ACE, and to identify
potential barriers to the e ective translation. To answer this question we decided
to manually \ACE'ify" the set of recommendations contained in the guideline
\Diagnosis, Treatment, and Evaluation of the Initial Urinary Tract Infection
in Febrile Infants and Young Children" (UTI) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. UTI was chosen because (1)
it includes a su cient number of recommendations to exercise the translation
process, (2) its recommendations involve a variety of action types and levels
of obligation, (3) some recommendations incorporate a temporal sequence, (4)
while others contain sentences related by anaphoric references. This guideline
demonstrates many challenges in translating recommendations in spite of its
small size. All eleven UTI guidelines could be successfully translated into ACE.
Table 1 shows three of the original natural language guidelines together with
their ACE equivalents.
      </p>
      <p>The recommendations were translated by 3 members of the ACE team at
the University of Zurich. Once translated into ACE, the recommendations were
reviewed by a pediatrician with expertise in clinical guidelines and by a
knowledge engineer. Judgements were made regarding the accuracy of translation,
the naturalness of the ACE statements, and potential solutions to encountered
impediments of the translation. Altogether, the reviewers concluded that ACE
is capable of accurately stating the clinical concepts and the actions described
in the guideline's recommendations. Nevertheless, the reviewers identi ed some
problem areas.</p>
      <p>The example guidelines use specialized medical terms that are not part of
the basic lexicon of the ACE parser. Though many of these terms can be found
in lexicons like UMLS and SNOMED, the problem remains that terms | such
as \ability to retain oral intake,", \su ciently ill" and \SPA" | require clear
and consistent speci cations by guideline authors. We plan to solve this problem
by providing an authoring tool that accepts only terms that are known to the
system and that have a clearly de ned meaning.</p>
      <p>Considerable uncertainty accompanies most medical decision making.
Evidence validity as well as the accuracy of clinical observations and measurements
contribute to this uncertainty. Guideline authors express the uncertainty by
using deontic modals and by including coded representations of evidence quality
and recommendation strength with their recommendations. Strength of
recommendation is a judgment based on the anticipated bene ts, risks, harms, and
costs of the proposed actions.</p>
      <p>The modals \can" and \must" originally o ered by ACE are not su cient
to capture the levels of obligation imposed by recommendations. In guideline
recommendations \should" is the most frequently used modal with a level of
obligation between \can" and \must". To adequately represent the required
levels, ACE was extended by the modal \should". This is already re ected in
the examples of table 1.</p>
      <p>While \ACE'ifying" UTI, we noticed that a systematic approach is needed
to consistently author clinical guidelines, and to adequately support clinicians in
the use of guidelines. All knowledge should be made explicit, all terms should be
used consistently, and guidelines should be rendered operational to be executed
under the control of the responsible clinician | who ultimately must decide
whether, or not, to follow the recommendations of a guideline.</p>
      <p>To make all knowledge explicit and to enforce a consistent use of this
knowledge we introduce a domain-speci c lexicon and a background ontology. Here is
a sample of the UTI background ontology:</p>
      <sec id="sec-2-1">
        <title>Every child is a person.</title>
      </sec>
      <sec id="sec-2-2">
        <title>SPA is a method.</title>
      </sec>
      <sec id="sec-2-3">
        <title>No analysis con rms X and excludes X.</title>
      </sec>
      <sec id="sec-2-4">
        <title>Every antimicrobial-therapy is a therapy. ...</title>
        <p>To make the guidelines operational we express them as linked rules that are
executed under the control of the clinician. Every rule (see Table 1) consists
of preconditions that must be ful lled to trigger the rule, and conclusions that
are true after the rule red, and that can be used as preconditions for other
rules. To get the rule machinery running, a number of initial facts are asserted
that originate from the patient's electronic health record or that are manually
asserted by the clinician, for instance:</p>
      </sec>
      <sec id="sec-2-5">
        <title>The patient is a young child.</title>
      </sec>
      <sec id="sec-2-6">
        <title>The patient's age is 1.5 years.</title>
      </sec>
      <sec id="sec-2-7">
        <title>The patient has an unexplained fever. ...</title>
        <p>The ring of a guideline rule can enable other rules, so that potentially every
rule can be red at some point.
3</p>
        <p>Conclusions and Future Work
We showed that ACE can be used to adequately express clinical practice
guidelines. Furthermore, we prototypically developed a systematic approach to author
and to transparently use clinical practice guidelines stated in ACE.</p>
        <p>
          Our immediate plan is to build a \look-ahead" editor for clinical practice
guidelines expressed in ACE that dynamically displays the knowledge de ned so
far and the speci c options available for extending or revising it, similiar to the
existing ACE Editor4. This approach was described by Scott et al. [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], and has
been used by Schwitter [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] and by Kuhn [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ] working with controlled language
grammars. Furthermore, in the future, we plan to embed rules created with the
ACE editor in a decision support system that advises clinicians. That system will
combine the rules with clinical observations derived from an electronic health
record system to provide guidance about best practices for care.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>4 http://attempto.ifi.uzh.ch/aceeditor</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>American</surname>
          </string-name>
          <article-title>Academy of Pediatrics. Practice Parameter: The Diagnosis, Treatment, and Evaluation of the Initial Urinary Tract Infection in Febrile Infants and Young Children</article-title>
          . In Pediatrics,
          <year>1999</year>
          ;
          <volume>103</volume>
          :
          <fpage>843</fpage>
          -
          <lpage>52</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>M. J. Field</surname>
            ,
            <given-names>K. N.</given-names>
          </string-name>
          <string-name>
            <surname>Lohr</surname>
          </string-name>
          (eds.).
          <source>Guidelines for Clinical Practice: From Development to Use</source>
          , National Academy Press,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Norbert</surname>
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Fuchs</surname>
            , Kaarel Kaljurand, and
            <given-names>Tobias</given-names>
          </string-name>
          <string-name>
            <surname>Kuhn</surname>
          </string-name>
          .
          <article-title>Attempto Controlled English for Knowledge Representation</article-title>
          .
          <source>In Reasoning Web, 4th International Summer School</source>
          <year>2008</year>
          , Tutorial Lectures,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>R. A.</given-names>
            <surname>Greenes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Peleg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Boxwala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Tu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Patel</surname>
          </string-name>
          ,
          <string-name>
            <surname>E. H.</surname>
          </string-name>
          <article-title>Shortli e Sharable Computer-Based Clinical Practice Guidelines: Rationale, Obstacles, Approaches, and Prospects</article-title>
          . In Medinfo,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>T.</given-names>
            <surname>Kuhn</surname>
          </string-name>
          .
          <article-title>AceWiki: Collaborative Ontology Management in Controlled Natural Language</article-title>
          .
          <source>In 3rd Semantic Wiki Workshop, CEUR Workshop Proceedings</source>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>R.</given-names>
            <surname>Power</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Scott</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Evans</surname>
          </string-name>
          .
          <article-title>What You See Is What You Meant: Direct Knowledge Editing with Natural Language Feedback</article-title>
          .
          <source>In Proc. 13th European Conference on Arti cial Intelligence (ECAI 98)</source>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>R.</given-names>
            <surname>Schwitter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ljungberg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hood</surname>
          </string-name>
          .
          <article-title>ECOLE: A Look-ahead Editor for a Controlled Language</article-title>
          .
          <source>In Proc 8th European Association for Machine Translation and the 4th Controlled Language Applications Workshop (EAMT-CLAW 03)</source>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>R. N.</surname>
          </string-name>
          <article-title>Shi man</article-title>
          , G. Michel,
          <string-name>
            <given-names>A.</given-names>
            <surname>Essaihi</surname>
          </string-name>
          ,
          <string-name>
            <surname>E. Thornquist.</surname>
          </string-name>
          <article-title>Bridging the Guideline Implementation Gap: A Systematic, Document-centered Approach to Guideline Implementation</article-title>
          .
          <source>J Am Med Informatics Assoc</source>
          ,
          <year>2004</year>
          ;
          <volume>5</volume>
          :
          <fpage>418</fpage>
          -
          <lpage>26</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Y.</given-names>
            <surname>Sun</surname>
          </string-name>
          ,
          <string-name>
            <surname>F. J. van Wingerde</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. J.</given-names>
            <surname>Homer</surname>
          </string-name>
          .
          <article-title>The Challenges of Implementing a Real-Time Clinical Practice Guideline</article-title>
          .
          <source>Clin Perform Quality Health Care</source>
          ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>