<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rdf:RDF[
	<!ENTITY rdf 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
	<!ENTITY rdfs 'http://www.w3.org/2000/01/rdf-schema#'>
	<!ENTITY owl 'http://www.w3.org/2002/07/owl#'>
	<!ENTITY swivt 'http://semantic-mediawiki.org/swivt/1.0#'>
	<!ENTITY wiki 'http://tw.rpi.edu/wiki/Special:URIResolver/'>
	<!ENTITY property 'http://tw.rpi.edu/wiki/Special:URIResolver/Property-3A'>
	<!ENTITY wikiurl 'http://tw.rpi.edu/wiki/'>
]>

<rdf:RDF
	xmlns:rdf="&rdf;"
	xmlns:rdfs="&rdfs;"
	xmlns:owl ="&owl;"
	xmlns:swivt="&swivt;"
	xmlns:wiki="&wiki;"
	xmlns:property="&property;">
	<!-- Ontology header -->
	<owl:Ontology rdf:about="">
		<swivt:creationDate rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2012-02-11T03:35:14-05:00</swivt:creationDate>
		<owl:imports rdf:resource="http://semantic-mediawiki.org/swivt/1.0" />
	</owl:Ontology>
	<!-- exported page data -->
	<swivt:Subject rdf:about="&wiki;A_Component-2DBased_Approach_to_Automation_of_Protocol-2DDirected_Therapy">
		<rdfs:label>A Component-Based Approach to Automation of Protocol-Directed Therapy</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;A_Component-Based_Approach_to_Automation_of_Protocol-Directed_Therapy"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/A_Component-Based_Approach_to_Automation_of_Protocol-Directed_Therapy"/>
		<rdf:type rdf:resource="&wiki;Category-3ATechnical_Report"/>
		<rdf:type rdf:resource="&wiki;Category-3APublication"/>
		<rdf:type rdf:resource="&wiki;Category-3AKSL_Technical_Report"/>
		<property:Abstract rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Objective:  Automating the task of planning protocol-directed therapy requires a computer program to take as input clinical data stored in an electronic patient-record system, and to generate as output recommendations for therapeutic interventions and laboratory testing that are defined by predefined protocols.  The output must be tailored for the current patient situation and stage of protocol execution.  Our goal has been to model the functional requirements of the therapy-planning task.Design:  We constructed a computational model that includes components that(1) interpret abstract protocol specifications to construct appropriate patient-specific treatment plans, (2) infer from time-stamped patient data higher-level, interval-based, abstract concepts, (3) perform time-oriented queries on a time-oriented patient database, and (4) allow for acquisition and maintenance of protocol knowledge in a manner that facilitates efficient processing both by humans and computers.  We have implemented these components in a computer system known as EON.Results:  The EON architecture brings together (1) a therapy planner based on a reusable problem-solving method known as episodic skeletal-plan refinement,(2) the RESUME temporal-abstraction system, which implements the knowledge-based temporal-abstraction problem-solving method, (3) the Chronus database system, which processes complex temporal queries referred to a clinical, time-oriented relational database, and (4) special-purpose knowledge-acquisition tools that are generated automatically from descriptions of the relevant clinical domains by the PROTEGE-II system.   We have evaluated the capabilities of the EON components by implementing T-Helper,  a computer-based patient record system that uses EON to offer advice regarding the management of patients who have AIDS and HIV infection.Conclusion:  Each of the modules that comprise the EON architecture has been developed as a self-contained, reusable component.  The integration of these elements, however, leads to an aggregate component that is itself reusable for automating the task of planning protocol-based therapy in a variety of clinical domains.  EON provides a comprehensive, yet flexible approach that facilitates development, maintenance, and execution of electronic knowledge bases that encode clinical protocols of substantial complexity.Objective:  Automating the task of planning protocol-directed therapy requires a computer program to take as input clinical data stored in an electronic patient-record system, and to generate as output recommendations for therapeutic interventions and laboratory testing that are defined by predefined protocols.  The output must be tailored for the current patient situation and stage of protocol execution.  Our goal has been to model the functional requirements of the therapy-planning task.Design:  We constructed a computational model that includes components that(1) interpret abstract protocol specifications to construct appropriate patient-specific treatment plans, (2) infer from time-stamped patient data higher-level, interval-based, abstract concepts, (3) perform time-oriented queries on a time-oriented patient database, and (4) allow for acquisition and maintenance of protocol knowledge in a manner that facilitates efficient processing both by humans and computers.  We have implemented these components in a computer system known as EON.Results:  The EON architecture brings together (1) a therapy planner based on a reusable problem-solving method known as episodic skeletal-plan refinement,(2) the RESUME temporal-abstraction system, which implements the knowledge-based temporal-abstraction problem-solving method, (3) the Chronus database system, which processes complex temporal queries referred to a clinical, time-oriented relational database, and (4) special-purpose knowledge-acquisition tools that are generated automatically from descriptions of the relevant clinical domains by the PROTEGE-II system.   We have evaluated the capabilities of the EON components by implementing T-Helper,  a computer-based patient record system that uses EON to offer advice regarding the management of patients who have AIDS and HIV infection.Conclusion:  Each of the modules that comprise the EON architecture has been developed as a self-contained, reusable component.  The integration of these elements, however, leads to an aggregate component that is itself reusable for automating the task of planning protocol-based therapy in a variety of clinical domains.  EON provides a comprehensive, yet flexible approach that facilitates development, maintenance, and execution of electronic knowledge bases that encode clinical protocols of substantial complexity.</property:Abstract>
		<property:Author rdf:resource="&wiki;Mark_A._Musen_and_Samson_W._Tu_and_Amar_K._Das_and_Yuval_Shahar"/>
		<property:Bibtype rdf:datatype="http://www.w3.org/2001/XMLSchema#string">techreport</property:Bibtype>
		<property:Has_author rdf:resource="&wiki;Mark_A._Musen_and_Samson_W._Tu_and_Amar_K._Das_and_Yuval_Shahar"/>
		<property:Has_identifier rdf:resource="&wiki;A_Component-2DBased_Approach_to_Automation_of_Protocol-2DDirected_Therapy"/>
		<property:Has_publishing_details rdf:datatype="http://www.w3.org/2001/XMLSchema#string">1996,1996</property:Has_publishing_details>
		<property:Has_title rdf:datatype="http://www.w3.org/2001/XMLSchema#string">A Component-Based Approach to Automation of Protocol-Directed Therapy</property:Has_title>
		<property:Has_where_published rdf:datatype="http://www.w3.org/2001/XMLSchema#string">KSL-96-06</property:Has_where_published>
		<property:Has_year rdf:datatype="http://www.w3.org/2001/XMLSchema#string">1996</property:Has_year>
		<property:Institution rdf:resource="&wiki;Knowledge_Systems-2C_AI_Laboratory"/>
		<property:Ksl_tr_id rdf:resource="&wiki;A_Component-2DBased_Approach_to_Automation_of_Protocol-2DDirected_Therapy"/>
		<property:Month rdf:resource="&wiki;1996"/>
		<property:Note rdf:datatype="http://www.w3.org/2001/XMLSchema#string">Medical Computer Science</property:Note>
		<property:Number rdf:resource="&wiki;A_Component-2DBased_Approach_to_Automation_of_Protocol-2DDirected_Therapy"/>
		<property:Process_note rdf:resource="&wiki;NO"/>
		<property:Title rdf:datatype="http://www.w3.org/2001/XMLSchema#string">A Component-Based Approach to Automation of Protocol-Directed Therapy</property:Title>
		<property:Year rdf:datatype="http://www.w3.org/2001/XMLSchema#string">1996</property:Year>
	</swivt:Subject>
	<!-- auxilliary definitions -->
	<owl:DatatypeProperty rdf:about="&property;Year">
		<rdfs:label>Year</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Year"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Year"/>
	</owl:DatatypeProperty>
	<owl:DatatypeProperty rdf:about="&property;Title">
		<rdfs:label>Title</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Title"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Title"/>
	</owl:DatatypeProperty>
	<swivt:Subject rdf:about="&wiki;NO">
		<rdfs:label>NO</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;NO"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/NO"/>
	</swivt:Subject>
	<owl:ObjectProperty rdf:about="&property;Process_note">
		<rdfs:label>Process note</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Process_note"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Process_note"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:about="&property;Number">
		<rdfs:label>Number</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Number"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Number"/>
	</owl:ObjectProperty>
	<owl:DatatypeProperty rdf:about="&property;Note">
		<rdfs:label>Note</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Note"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Note"/>
	</owl:DatatypeProperty>
	<swivt:Subject rdf:about="&wiki;1996">
		<rdfs:label>1996</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;1996"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/1996"/>
	</swivt:Subject>
	<owl:ObjectProperty rdf:about="&property;Month">
		<rdfs:label>Month</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Month"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Month"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:about="&property;Ksl_tr_id">
		<rdfs:label>Ksl tr id</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Ksl_tr_id"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Ksl_tr_id"/>
	</owl:ObjectProperty>
	<swivt:Subject rdf:about="&wiki;Knowledge_Systems-2C_AI_Laboratory">
		<rdfs:label>Knowledge Systems, AI Laboratory</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Knowledge_Systems%2C_AI_Laboratory"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Knowledge_Systems%2C_AI_Laboratory"/>
	</swivt:Subject>
	<owl:ObjectProperty rdf:about="&property;Institution">
		<rdfs:label>Institution</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Institution"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Institution"/>
	</owl:ObjectProperty>
	<owl:DatatypeProperty rdf:about="&property;Has_year">
		<rdfs:label>Has year</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_year"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_year"/>
	</owl:DatatypeProperty>
	<owl:DatatypeProperty rdf:about="&property;Has_where_published">
		<rdfs:label>Has where published</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_where_published"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_where_published"/>
	</owl:DatatypeProperty>
	<owl:DatatypeProperty rdf:about="&property;Has_title">
		<rdfs:label>Has title</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_title"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_title"/>
	</owl:DatatypeProperty>
	<owl:DatatypeProperty rdf:about="&property;Has_publishing_details">
		<rdfs:label>Has publishing details</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_publishing_details"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_publishing_details"/>
	</owl:DatatypeProperty>
	<owl:ObjectProperty rdf:about="&property;Has_identifier">
		<rdfs:label>Has identifier</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_identifier"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_identifier"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:about="&property;Has_author">
		<rdfs:label>Has author</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Has_author"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Has_author"/>
	</owl:ObjectProperty>
	<owl:DatatypeProperty rdf:about="&property;Bibtype">
		<rdfs:label>Bibtype</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Bibtype"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Bibtype"/>
	</owl:DatatypeProperty>
	<swivt:Subject rdf:about="&wiki;Mark_A._Musen_and_Samson_W._Tu_and_Amar_K._Das_and_Yuval_Shahar">
		<rdfs:label>Mark A. Musen and Samson W. Tu and Amar K. Das and Yuval Shahar</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Mark_A._Musen_and_Samson_W._Tu_and_Amar_K._Das_and_Yuval_Shahar"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Mark_A._Musen_and_Samson_W._Tu_and_Amar_K._Das_and_Yuval_Shahar"/>
	</swivt:Subject>
	<owl:ObjectProperty rdf:about="&property;Author">
		<rdfs:label>Author</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Author"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Author"/>
	</owl:ObjectProperty>
	<owl:DatatypeProperty rdf:about="&property;Abstract">
		<rdfs:label>Abstract</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Property:Abstract"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Property:Abstract"/>
	</owl:DatatypeProperty>
	<owl:Class rdf:about="&wiki;Category-3AKSL_Technical_Report">
		<rdfs:label>KSL Technical Report</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Category:KSL_Technical_Report"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Category:KSL_Technical_Report"/>
	</owl:Class>
	<owl:Class rdf:about="&wiki;Category-3APublication">
		<rdfs:label>Publication</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Category:Publication"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Category:Publication"/>
	</owl:Class>
	<owl:Class rdf:about="&wiki;Category-3ATechnical_Report">
		<rdfs:label>Technical Report</rdfs:label>
		<swivt:page rdf:resource="&wikiurl;Category:Technical_Report"/>
		<rdfs:isDefinedBy rdf:resource="&wikiurl;Special:ExportRDF/Category:Technical_Report"/>
	</owl:Class>
	<!-- References to the SWiVT Ontology, see http://semantic-mediawiki.org/swivt/ -->
	<owl:AnnotationProperty rdf:about="&swivt;page">
		<rdfs:isDefinedBy rdf:resource="http://semantic-mediawiki.org/swivt/1.0"/>
	</owl:AnnotationProperty>
	<owl:AnnotationProperty rdf:about="&swivt;creationDate">
		<rdfs:isDefinedBy rdf:resource="http://semantic-mediawiki.org/swivt/1.0"/>
	</owl:AnnotationProperty>
	<owl:Class rdf:about="&swivt;Subject">
		<rdfs:isDefinedBy rdf:resource="http://semantic-mediawiki.org/swivt/1.0"/>
	</owl:Class>
	<!-- Created by Semantic MediaWiki, http://semantic-mediawiki.org -->
</rdf:RDF>
