<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Controlled Natural Language for Clinical Practice Guidelines</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Richard</forename><forename type="middle">N</forename><surname>Shiffman</surname></persName>
							<email>richard.shiffman@yale.edu</email>
							<affiliation key="aff0">
								<orgName type="department">School of Medicine</orgName>
								<orgName type="institution">Yale University</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">George</forename><surname>Michel</surname></persName>
							<email>george.michel@yale.edu</email>
							<affiliation key="aff0">
								<orgName type="department">School of Medicine</orgName>
								<orgName type="institution">Yale University</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Michael</forename><surname>Krauthammer</surname></persName>
							<email>michael.krauthammer@yale.edu</email>
							<affiliation key="aff0">
								<orgName type="department">School of Medicine</orgName>
								<orgName type="institution">Yale University</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Norbert</forename><forename type="middle">E</forename><surname>Fuchs</surname></persName>
							<email>fuchs@ifi.uzh.ch</email>
							<affiliation key="aff1">
								<orgName type="department" key="dep1">Department of Informatics</orgName>
								<orgName type="department" key="dep2">Institute of Computational Linguistics</orgName>
								<orgName type="institution">University of Zurich</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Kaarel</forename><surname>Kaljurand</surname></persName>
							<affiliation key="aff1">
								<orgName type="department" key="dep1">Department of Informatics</orgName>
								<orgName type="department" key="dep2">Institute of Computational Linguistics</orgName>
								<orgName type="institution">University of Zurich</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Tobias</forename><surname>Kuhn</surname></persName>
							<email>tkuhn@ifi.uzh.ch</email>
							<affiliation key="aff1">
								<orgName type="department" key="dep1">Department of Informatics</orgName>
								<orgName type="department" key="dep2">Institute of Computational Linguistics</orgName>
								<orgName type="institution">University of Zurich</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Controlled Natural Language for Clinical Practice Guidelines</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">A7D365B19E179FD81CDC42E4314E335E</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T12:26+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Clinicians would benefit 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></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Clinical practice guidelines are defined as "systematically developed statements to assist practitioner and patient decisions about appropriate healthcare for specific clinical circumstances" <ref type="bibr" target="#b1">[2]</ref>. 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 scientific evidence. More than 4000 guidelines have been published by various organizations. The large number of guidelines impedes their practical application by clinicians who would profit 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 <ref type="bibr" target="#b3">[4]</ref>. Uncritical translation of such recommendations into computable statements risks distortion of the guideline authors' intent <ref type="bibr" target="#b7">[8,</ref><ref type="bibr" target="#b8">9]</ref>.</p><p>In order to address this problem, we investigate writing guidelines in Attempto Controlled English (ACE) <ref type="bibr" target="#b2">[3]</ref>. ACE is a controlled natural language, i.e. a precisely defined 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 simplified sentence and text structure. ACE has the additional benefit of being supported by a parsing engine that translates ACE texts into first-order logic, thereby providing a computable format and supporting automatic reasoning.</p><p>In the initial phases of the ERGO Project (Effective Representation of Guidelines with Ontologies) <ref type="foot" target="#foot_0">3</ref> 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 findings) against these rules to guide a health provider by offering patient-specific and situation-specific advice. A second goal is to demonstrate that ACE is a good candidate controlled natural language for writing recommendations. Figure <ref type="figure" target="#fig_0">1</ref> shows the general architecture of our approach.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table 1. A comparison of three of the eleven original natural language guidelines together with their ACE equivalents</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Original guideline Attempto Controlled English</head><p>The presence of UTI should be considered in infants and young children 2 months to 2 years of age with unexplained fever (strength of evidence: strong).</p><p>If the patient is a young child who has an unexplained fever then the clinician must consider UTI.</p><p>In infants and young children 2 months to 2 years of age with unexplained fever, the degree of toxicity, dehydration, and ability to retain oral intake must be carefully assessed (strength of evidence: strong).</p><p>If the patient is a young child who has an unexplained fever then the clinician must assess the degree of Toxicity and must assess the degree of Dehydration and must assess the Ability-to-retain-oral-intake.</p><p>If an infant or young child 2 months to 2 years of age with unexplained fever is assessed as being sufficiently ill to warrant immediate antimicrobial therapy, a urine specimen should be obtained by SPA or transurethral bladder catheterization; [...] (strength of evidence: good).</p><p>If the patient is a young child who has an unexplained fever and the patient is sufficiently-ill then the clinician should analyze a culture of a urine-specimen that is obtained-by SPA or that is obtained-by Transurethral-catheterization.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Expressing Clinical Practice Guidelines in ACE</head><p>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 amplified by supporting text. A first critical step is to establish whether clinical guidelines can be adequately expressed in ACE, and to identify potential barriers to the effective 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) <ref type="bibr" target="#b0">[1]</ref>. UTI was chosen because (1) it includes a sufficient 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 <ref type="table">1</ref> shows three of the original natural language guidelines together with their ACE equivalents. 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 identified 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,", "sufficiently ill" and "SPA" -require clear and consistent specifications 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 defined 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 benefits, risks, harms, and costs of the proposed actions.</p><p>The modals "can" and "must" originally offered by ACE are not sufficient 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 reflected 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-specific lexicon and a background ontology. Here is a sample of the UTI background ontology:</p><p>Every child is a person. SPA is a method. No analysis confirms X and excludes X. Every antimicrobial-therapy is a therapy. ...</p><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 <ref type="table">1</ref>) consists of preconditions that must be fulfilled to trigger the rule, and conclusions that are true after the rule fired, 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><p>The patient is a young child. The patient's age is 1.5 years.</p><p>The patient has an unexplained fever. ... The firing of a guideline rule can enable other rules, so that potentially every rule can be fired at some point.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Conclusions and Future Work</head><p>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 defined so far and the specific options available for extending or revising it, similiar to the existing ACE Editor<ref type="foot" target="#foot_1">4</ref> . This approach was described by Scott et al. <ref type="bibr" target="#b5">[6]</ref>, and has been used by Schwitter <ref type="bibr" target="#b6">[7]</ref> and by Kuhn <ref type="bibr" target="#b4">[5]</ref> 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></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. This diagram shows the general architecture of our approach. It shows the information and data flows between systems (in rectangular shapes) and users. The focus of the ERGO project lies on the guideline development part.</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">http://gem.med.yale.edu/ergo/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_1">http://attempto.ifi.uzh.ch/aceeditor</note>
		</body>
		<back>

			<div type="funding">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This work was supported by the US National Library of Medicine and the Agency for Healthcare Research and Quality (grant R01 LM007199).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Practice Parameter: The Diagnosis, Treatment, and Evaluation of the Initial Urinary Tract Infection in Febrile Infants and Young Children</title>
		<author>
			<persName><forename type="first">American</forename><surname>Academy</surname></persName>
		</author>
		<author>
			<persName><surname>Pediatrics</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Pediatrics</title>
		<imprint>
			<biblScope unit="volume">103</biblScope>
			<biblScope unit="page" from="843" to="852" />
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Guidelines for Clinical Practice: From Development to Use</title>
		<editor>M. J. Field, K. N. Lohr</editor>
		<imprint>
			<date type="published" when="1992">1992</date>
			<publisher>National Academy Press</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Attempto Controlled English for Knowledge Representation</title>
		<author>
			<persName><forename type="first">Norbert</forename><forename type="middle">E</forename><surname>Fuchs</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kaarel</forename><surname>Kaljurand</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Tobias</forename><surname>Kuhn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Reasoning Web, 4th International Summer School 2008, Tutorial Lectures</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Shortliffe Sharable Computer-Based Clinical Practice Guidelines: Rationale, Obstacles, Approaches, and Prospects</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">A</forename><surname>Greenes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Peleg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Boxwala</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Tu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Patel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">H</forename></persName>
		</author>
		<imprint>
			<date type="published" when="2001">2001</date>
			<publisher>Medinfo</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">AceWiki: Collaborative Ontology Management in Controlled Natural Language</title>
		<author>
			<persName><forename type="first">T</forename><surname>Kuhn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3rd Semantic Wiki Workshop</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
	<note>CEUR Workshop Proceedings</note>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">What You See Is What You Meant: Direct Knowledge Editing with Natural Language Feedback</title>
		<author>
			<persName><forename type="first">R</forename><surname>Power</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Scott</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Evans</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 13th European Conference on Artificial Intelligence (ECAI 98)</title>
				<meeting>13th European Conference on Artificial Intelligence (ECAI 98)</meeting>
		<imprint>
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">ECOLE: A Look-ahead Editor for a Controlled Language</title>
		<author>
			<persName><forename type="first">R</forename><surname>Schwitter</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ljungberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Hood</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc 8th European Association for Machine Translation and the 4th Controlled Language Applications Workshop (EAMT-CLAW 03)</title>
				<meeting>8th European Association for Machine Translation and the 4th Controlled Language Applications Workshop (EAMT-CLAW 03)</meeting>
		<imprint>
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Bridging the Guideline Implementation Gap: A Systematic, Document-centered Approach to Guideline Implementation</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">N</forename><surname>Shiffman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Michel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Essaihi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Thornquist</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">J Am Med Informatics Assoc</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="page" from="418" to="426" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">The Challenges of Implementing a Real-Time Clinical Practice Guideline</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Sun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">J</forename><surname>Van Wingerde</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">J</forename><surname>Homer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Clin Perform Quality Health Care</title>
		<imprint>
			<date type="published" when="1999">1999</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
