1 Introduction
This article presents the Kasimir system dedicated to decision knowledge management in oncology. The system is built on top of advanced Semantic Web technologies (Hitzler et al., Reference Hitzler, Krötsch and Rudolph2009), where knowledge representation formalisms are based on description logics—Web ontology language description logic (OWL DL) (Baader et al., Reference Baader, Calvanese, McGuinness, Nardi and Patel-Schneider2003; Antoniou & van Harmelen, Reference Antoniou and van Harmelen2004) and context Web ontology language (C-OWL; Bouquet et al., Reference Bouquet, Giunchiglia, van Harmelen, Serafini and Stuckenschmidt2004)—with associated reasoning formalisms such as subsumption and instantiation, and in addition case-based reasoning (CBR; Riesbeck & Schank, Reference Riesbeck and Schank1989; Kolodner, Reference Kolodner1993; Aamodt & Plaza, Reference Aamodt and Plaza1994). The Kasimir system can be viewed as an intelligent assistant for physicians in their everyday practice of decision making (d'Aquin et al., Reference d'Aquin, Lieber and Napoli2008). In Lorraine, that is, the region of North-East France where the Kasimir system is currently developed, the decisions on cancer treatment, surveillance, etc., are based on decision protocols. For example, the protocol for breast cancer treatment associates a specific treatment recommendation with the clinical status of a patient. The main example used throughout the paper is related to breast cancer treatment. The associated protocol is called hereafter either decision protocol or simply protocol.
A protocol contains the standard knowledge for decision support in oncology and is structured as a kind of decision tree. Roughly speaking, the protocol can be considered as a set of associations relating a class of patients suffering from cancer and a set of therapeutic decisions that can be applied to these patients. A patient suffering from cancer is called a ‘cancer patient’, a ‘tumor patient’ or simply a ‘patient’ when there is no ambiguity. For most medical cases—about 60–70%—the protocol is simply and straightforwardly applied. The remaining non-typical medical cases, called out-of-protocol cases, are examined by a committee of physicians called the breast therapeutic decision committee, for adapting the protocol and making a therapeutic decision. More precisely, given an out-of-protocol patient description, say P, the breast therapeutic decision committee generally selects a class of patients whose description is close to the patient description P and adapts the associated therapeutic decision to propose a treatment for the patient. This adaptation of the protocol can be modeled within a CBR process, where the problem to be solved corresponds to a patient description and the solution to a therapeutic decision to be applied to the patient.
Oncology has to be regarded as a complex domain where several specialties, for example, chemotherapy, surgery, and radiotherapy, are involved. For each specialty, different characteristics of the patient are analyzed and taken into account for setting on a specific treatment within the whole treatment process. Accordingly, during a meeting of the breast therapeutic decision committee, each expert provides a view specific to his/her specialty on the treatment, as a part of a collective recommendation. The oncology specialties determine interrelated viewpoints for a patient treatment, that is, units of information on a given patient in a local viewpoint can be shared and combined with other units of information in another local viewpoint to build a global treatment. Moreover, a decision taken in a local viewpoint, that is, for a particular oncology specialty, may have an influence on the decision to be taken in another local viewpoint. Hence, knowledge representation and reasoning within the Kasimir system have to consider—and to take advantage of—the multiple viewpoints involved in the decision.
Until now, two versions of the Kasimir system have been developed. The first version is based on an object-based representation formalism (d'Aquin et al., Reference d'Aquin, Brachais, Lieber and Napoli2004), and the second version is based on a semantic portal using DLs and knowledge formalisms dedicated to the Semantic Web (d'Aquin et al., Reference d'Aquin, Brachais, Bouthier, Lieber and Napoli2005a). Being a standard for knowledge representation and exchange for Semantic Web applications, the Web ontology language OWLFootnote 1, particularly the sub-language OWL DL, provide an adequate formalism for a reusable representation of knowledge contained in a decision protocol. Reasoning mechanisms associated with OWL DL, such as subsumption, classification, and instantiation, can be efficiently used for decision support in oncology. Finally, it should be noticed that there are still new developments in the Kasimir system (Meilender et al., Reference Meilender, Lieber, Palomares and Jay2012).
Applying Semantic Web technologies in such a challenging domain leads to interesting issues, emphasizing some of the distinctive strengths and limitations of available formalisms such as OWL. Actually, an originality of the present research work is that the Kasimir system implements various non-typical elements within a DL framework, namely:
• The representation of a decision protocol for associating a treatment recommendation with a patient description is based on a domain ontology implemented within the OWL DL, and used for knowledge representation and reasoning.
• The representation of adaptation knowledge for protocol adaptation and CBR within a DL framework uses similarity paths for comparing two problems and adaptation paths for adapting the solution of a source problem to a target problem considered as being close to the source problem.
• The representation of viewpoints within the Kasimir system—one viewpoint corresponding to one oncology specialty—is based on a distributed DL (DDL) formalism, namely C-OWL. The C-OWL formalism provides means for local representation and reasoning within a viewpoint, and global reasoning across several viewpoints, leading to decentralized CBR.
Accordingly, the main contributions of the paper are the following:
• We define and use CBR in a distributed environment based on DDLs and implemented in C-OWL. This leads to the original notion of ‘decentralized CBR’, which combines CBR and DDLs.
• We make precise and give details on a real-world application in the medical domain, thanks to the Kasimir system. This application illustrates and shows the capabilities of decentralized CBR.
To the best of the authors’ knowledge, decentralized CBR is an original approach, and one of the few implementing CBR within a DDL framework in a working system.
These non-typical items show that the Kasimir system has a particular situation in the family of systems for decision support in medicine based on Semantic Web technology. Some systems are close to the Kasimir system without necessarily having the same focus on knowledge representation and reasoning. In Patkar et al. (Reference Patkar, Hurt, Steele, Love, Purushotham, Williams, Thomson and Fox2006), the focus is mainly on the implementation of oncology guidelines in practice with an evaluation of ‘computerized decision support’ systems (a related distributed architecture is presented in Besana et al. (Reference Besana, Patkar, Glasspool and Robertson2008)). An analysis of the decision systems is given and the possible improvements of physician decisions when they use a computerized decision support system. An evaluation carried out on a version of the Kasimir system led to the same conclusions (see Section 5). In the same way, the representation, evolution, and management of clinical practice guidelines are discussed in Bouaud and Séroussi (Reference Bouaud and Séroussi2008), following a series of work on the subject. The focus here relates to the management of the different temporal versions of the clinical guideline rather than decision support and problem solving. A Semantic Web-based approach for synthesizing health knowledge through ontologies is presented in Hussain and Abidi (Reference Hussain and Abidi2009), which focuses on the integration of different knowledge sources. The most influential work for us probably remains (Bouquet et al., Reference Bouquet, Giunchiglia, van Harmelen, Serafini and Stuckenschmidt2004), mainly for introducing contextualized ontologies and C-OWL, as this is explained throughout the paper. An important research work is also carried out in biomedicine and Semantic Web by the team that is currently developing the Protégé editor and BioportalFootnote 2, an open repository of biomedical ontologies (Ghazvinian et al., Reference Ghazvinian, Noy, Jonquet, Shah and Musen2009; Noy et al., Reference Noy, Shah, Whetzel, Dai, Dorf, Griffith, Jonquet, Rubin, Storey, Chute and Musen2009). Finally, let us mention a recent ‘Workshop on Semantic Interoperability in Medical Informatics (SIMI 2012)’ including contributions about knowledge acquisition, ontology mapping of disperse biomedical resources, annotation and semantic search in the biomedical domain, and automated decision support services (http://grid.ece.ntua.gr/sites/simi2012/SIMI2012_proc.pdf).
The summary of the paper is as follows. First, the framework for protocol representation based on DLs is introduced. It is shown how a problem matching the protocol, that is, the description of a patient satisfying the protocol, is solved (Section 2). Then, CBR for protocol adaptation is motivated and described. The reformulation model underlies the CBR problem-solving process, involving both similarity and adaptation paths (Section 3). The representation of viewpoints in oncology and distributed reasoning within viewpoints are then detailed (Section 4). A discussion follows, focusing on the use of a DL framework for tasks such as: (i) managing real-world knowledge in oncology, (ii) designing the associated Kasimir system, and (iii) implementing viewpoints and a CBR process within the Kasimir system (Section 5). A paragraph explaining the implementation and the evaluation of the Kasimir system concludes the paper (Section 5).
2 The description logic framework for decision support guided by a protocol
A clinical decision support system is defined in van Bemmel and Musen (Reference van Bemmel and Musen1997) as a program for which the input is the description of a medical situation and the output corresponds to information units helping the practitioner in making decisions concerning this situation. In general, a clinical decision support system is a knowledge-based system, relying on a formalized medical knowledge base and on inference mechanisms. The Kasimir system is compliant with the above definition: the knowledge base corresponds to the representation of a medical protocol in OWL DL, while standard DL reasoning mechanisms control decision support for protocol application.
2.1 A brief introduction to description logics
In this section, we recall the basics of DLs that are useful and necessary for understanding the DL expressions given in the paper. This short presentation is based on the DL Handbook (Baader et al., Reference Baader, Calvanese, McGuinness, Nardi and Patel-Schneider2003) and on another more recent introduction to DLs (Krötzsch et al., Reference Krötzsch, Simancik and Horrocks2012).
DLs are a family of knowledge representation languages that are widely used for designing knowledge-based systems. In DLs, there are three kinds of entities: concepts, roles, and individual names. Concepts denote sets of individuals (classes in OWL), roles denote binary relations between the individuals (properties in OWL), and individual names denote simple individuals in the domain. Concepts correspond to unary predicates in first-order logic, roles to binary predicates and individuals to constants. Two levels of knowledge are taken into account: conceptual knowledge (‘Tbox’) including introductions of concepts and roles, and assertional knowledge (‘Abox’) including expressions involving individuals. DLs are equipped with a formal logic-based semantics, and DL systems provide their users with various inference capabilities mainly based on satisfiability, subsumption, and classification of concepts and of individuals.
Elementary descriptions are atomic concepts and atomic roles, while complex descriptions can be built using concept contructors. More precisely, let C be a set of concept names and R be a set of role names disjoint from C. For the so-called
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
description logic, the set of concepts over C and R is inductively defined as follows:
• Every concept name is an
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
concept description.• ⊤ (top) and ⊥ (bottom) are
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
concept descriptions.• If C and D are
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
concept descriptions and r is a role name, then the following are also
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
concept descriptions:
– C⊓D (conjunction)
– C
$$\[--><$>\sqcup<$><!--$$
D (disjunction)– ¬C (complete negation)
– ∃r.C (existential restriction)
– ∀r.C (universal restriction)
Other concept constructions can be defined such as: cardinality restrictions with (≥n r) (‘at least’ restriction) and (≤n r) (‘at most’ restriction), and set of individuals (nominals). Role constructions can be used for extending
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
, such as conjunctions of roles, inverse roles, role hierarchy, etc. Each
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
extension has a name: e.g.
$$\[--><$>{\cal A}{\cal L}{\cal C}{\cal N} <$><!--$$
for cardinality restrictions,
$$\[--><$>{\cal A}{\cal L}{\cal C}{\cal O} <$><!--$$
for nominals,
$$\[--><$>{\cal A}{\cal L}{\cal C}{\cal R} <$><!--$$
for conjunctions of roles,
$$\[--><$> {\cal A}{\cal L}{\cal C}{\cal I} <$><!--$$
for inverse roles, and finally
$$\[--><$> {\cal A}{\cal L}{\cal C}{\cal H} <$><!--$$
for role hierarchy. Below, the
$$\[--><$> {\cal S} <$><!--$$
notation is used where
$$\[--><$> {\cal S} <$><!--$$
stands for
$$\[--><$>{\cal A}{\cal L}{\cal C} <$><!--$$
and thus
$$\[--><$> {\cal S}{\cal H}{\cal O}{\cal I}{\cal N} <$><!--$$
stands for
$$\[--><$> {\cal A}{\cal L}{\cal C}{\cal H}{\cal O}{\cal I}{\cal N} <$><!--$$
. Moreover, in
$$\[--><$> {\cal S}{\cal H}{\cal O}{\cal I}{\cal N}\!\left( {\cal D} \right) <$><!--$$
,
$$\[--><$> {\cal D} <$><!--$$
indicates a concrete domain and this is explained in the Section 2.2.
An interpretation
$$\[--><$> {\cal I}\, = \,({{{\rm{\rDelta }}}^{\cal I}} {{,\,.}^{\cal I}} ) <$><!--$$
is based on an interpretation domain
$$\[--><$>{{\rDelta }^{\cal I}} <$><!--$$
and on an interpretation function
$$\[--><$>{{.}^{\cal I}} <$><!--$$
mapping a concept onto a subset of
$$\[--><$>{{\rDelta }^{\cal I}} <$><!--$$
, and a role onto a subset of the product
$$\[--><$>{{{\rm{\rDelta }}}^{\cal I}} \times {{{\rm{\rDelta }}}^{\cal I}} <$><!--$$
, with respect to the following equations (where card(X) returns the cardinality of set X).
$$\[--><$$l>\quad\qquad \matrix{ {{{ \top }^{\cal I}} \, = \,{{\rDelta }^{\cal I}} } \hfill \cr \\ {{{ \bot }^{\cal I}} \, = \,\emptyset} \hfill \cr \\ {{{{\left( {{\rm{\tf="courier" C}}\, \sqcap \,{\rm{\tf="courier" D}}} \right)}}^{\cal I}} \, = \,{{{\rm{\tf="courier" C}}}^{\cal I}} \, \cap \,{{{\rm{\tf="courier" D}}}^{\cal I}} } \hfill \cr \\ {{{{\left( {{\rm{\tf="courier" C}}\, \sqcup \,{\rm{\tf="courier" D}}} \right)}}^{\cal I}} \, = \,{{{\rm{\tf="courier" C}}}^{\cal I}} \, \cup \,{{{\rm{\tf="courier" D}}}^{\cal I}} } \hfill \cr \\ {{{{\left( {\neg {\rm{\tf="courier" C}}} \right)}}^{\cal I}} \, = \,{{\rDelta }^{\cal I}} \,\backslash \,{{{\rm{\tf="courier" C}}}^{\cal I}} } \hfill \cr \\ {{{{\left( {\forall {\rm{\tf="courier" r}}.{\rm{\tf="courier" C}}} \right)}}^{\cal I}} \, = \,\left\{ {x\, \in \,{{\rDelta }^{\cal I}} \,|\,\forall y:\left( {x,y} \right)\, \in {{{\rm{\tf="courier" r}}}^{\cal I}} \, \rightarrow \,y\, \in \,{{{\rm{\tf="courier" C}}}^{\cal I}} } \right\}} \hfill \cr \\ {{{{\left( {\exists {\rm{\tf="courier" r}}.{\rm{\tf="courier" C}}} \right)}}^{\cal I}} \, = \,\left\{ {x\, \in \,{{\rDelta }^{\cal I}} \,|\,\exists y:\left( {x,y} \right)\, \in \,{{{\rm{\tf="courier" r}}}^{\cal I}} \, \wedge \,y\, \in \,{{{\rm{\tf="courier" C}}}^{\cal I}} } \right\}} \hfill \cr \\ {{{{\left( {\geq \!{\rm{\tf="courier" m}}\,{\rm{\tf="courier" r}}} \right)}}^{\cal I}} \, = \,\left\{ {x\, \in \,{{\rDelta }^{\cal I}} \,|\,card\left( {\left\{ {y\, \in \,{{\rDelta }^{\cal I}} /\left( {x,y} \right)\, \in \,{{{\rm{\tf="courier" r}}}^{\cal I}} } \right\}} \right)\geq m} \right\}} \hfill \cr \\ {{{{\left( {\leq \!{\rm{\tf="courier" n}}\,{\rm{\tf="courier" r}}} \right)}}^{\cal I}} \, = \,\left\{ {x\, \in \,{{\rDelta }^{\cal I}} \,|\,card\left( {\left\{ {y\, \in \,{{\rDelta }^{\cal I}} /\left( {x,y} \right)\, \in \,{{{\rm{\tf="courier" r}}}^{\cal I}} } \right\}} \right)\leq n} \right\}} \hfill \cr \\ \\ \\ $$
Then, a concept C is satisfiable iff there exists an interpretation
$$\[--><$>{\cal I} = \left( {{{\rDelta }^{\cal I}}, {{.}^{\cal I}} } \right) <$><!--$$
such as
$$\[--><$>{{{\rm{C}}}^{\cal I}} \ne \emptyset\<$><!--$$
, otherwise C is not satisfiable. A concept C is subsumed by a concept D iff for all interpretation
$$\[--><$>{\cal I} <$><!--$$
,
$$\[--><$>{{{\rm{\tf="courier" C}}}^{\cal I}} \subseteq {{{\rm{\tf="courier" D}}}^{\cal I}} <$><!--$$
. Satisfiability and subsumption are the base of DL-based reasoning modes. Examples are proposed in Section 2.4.
Hereafter, the usual syntax and semantics of DLs, introduced in Baader et al. (Reference Baader, Calvanese, McGuinness, Nardi and Patel-Schneider2003) as well as the naming conventions and recommendations are respected: that is, a concept name such as MultifocalTumor has a capitalized first letter, an instance name such as PAT has every letters capitalized, and a role name such as hasRecommendation has capitalized first letters except for the first one.
2.2 Description logics and Web ontology language description logic
The knowledge associated with a protocol is represented within OWL DL 1.0, which can be seen as an expressive DL such as
$$\[--><$> {\cal S}{\cal H}{\cal O}{\cal I}{\cal N}\left( {\cal D} \right) <$><!--$$
, integrated within standard technologies of the Web such as XML and RDF(S) (Horrocks et al., Reference Horrocks, Patel-Schneider and van Harmelen2003). The notion of an ontology is considered here as an equivalent for a DL knowledge base.
In addition, the system described here makes use of concrete domain within the DL formalism (Lutz et al., Reference Lutz, Areces, Horrocks and Sattler2005; Lutz & Milicic, Reference Lutz and Milicic2007). Following the notations in Lutz (Reference Lutz2003), a concrete domain is a pair
$$\[--><$>\left( {{{\rDelta }^{\cal D}}, \,{{\rPhi }^{\cal D}} } \right) <$><!--$$
where
$$\[--><$>{{\rDelta }^{\cal D}} <$><!--$$
is a set and
$$\[--><$>{{\rPhi }^{\cal D}} <$><!--$$
is a set of predicate names on
$$\[--><$>{{\rDelta }^{\cal D}} <$><!--$$
. Here, the concrete domain
$$\[--><$>{\cal D} = \left( {{\Bbb R}{\rm{,}}\,{{\rPhi }^{\Bbb R}} } \right) <$><!--$$
is considered, where
$$\[--><$>{\Bbb R} <$><!--$$
denotes real numbers, and
$$\[--><$>{{\rPhi }^{\Bbb R}} <$><!--$$
is the set of predicate names for comparing real numbers:
$$\[--><$> {{\{ \lt }_a},{{\leq }_a}{{, = }_a},{{ \ne }_a},{{\geq }_a}{{, \gt }_a}\} <$><!--$$
, with
$$\[--><$>a \in {\Bbb R} <$><!--$$
. The predicate Pa where
$$\[--><$> P \in \{ \lt, \leq, =, \ne, \geq, \gt \} <$><!--$$
is interpreted as
$$\[--><$> P_{a}^{{\cal D}} = \{ y \in {{\rDelta }^{\cal D}} \,|\,y\,P\,a\} <$><!--$$
. For example,
$$\[--><$> \geq _{3}^{{\ \cal D}} = [3;\, + \,\infty [ <$><!--$$
. The DL constructors are extended for integrating concrete domains. It becomes then possible to define a concept
$$\[--><$>\exists \tf="courier" g.\varphi <$><!--$$
, where g is a concrete role and
$$\[--><$>\varphi \in {{\rPhi }^{\cal D}} <$><!--$$
. The concrete role g is interpreted as a partial function
$$\[--><$>{{\tf="courier" g}^{\cal I}} <$><!--$$
:
$$\[--><$>{{\rDelta }^{\cal I}} \mapsto {{\rDelta }^{\cal D}} <$><!--$$
where
$$\[--><$>{{\rDelta }^{\cal I}} \, \cap \,{{\rDelta }^{\cal D}} = \emptyset<$><!--$$
and
$$\[--><$>{{\left( {\exists {\tf="courier" g}.\varphi } \right)}^{\cal I}} = \left\{ {{\rm{\tf="courier" x}} \in {{\rDelta }^{\cal I}} |{{\tf="courier" g}^{\cal I}} \left( {\rm{\tf="courier" x}} \right) \in {{\varphi }^D} } \right\}. <$><!--$$
Accordingly, the concept of a ‘patient older than 70 having a tumor whose grade is different from 1’ can be represented as:
where TumorPatient is a concept representing patients suffering from a tumor.
2.3 Representation of a protocol using description logics
A protocol can be likened to a decision tree, where internal nodes are related to the patient characteristics and leaf nodes are recommendations of treatments (see Figure 1). An internal node corresponds to a binary or Yes/No question related to one or several patient characteristics or features. Examples of features are the age, the tumor size (size), the tumor grade (grade 1, 2, or 3), the status of the lymph nodes (N+ for involved and N− for non-involved lymph nodes), the status of the hormone receptors (HR+ for positive and HR− for negative hormone receptors). The protocol in Figure 1 shows that, for a patient without involved lymph nodes (N−), with positive hormone receptors (HR+), younger than 35 years, and with a tumor size >1 cm or having a grade g ≠ 1, a chemotherapy of level 1 is recommended.
Excerpts from the breast cancer treatment protocol used at the CAV Hospital in Nancy, France (www.oncolor.org)
A path in the tree corresponds to a conjunction of conditions satisfied by a patient. The set of patients for which all these conditions apply constitutes a class of patients. Such a path is represented by a concept in DL and is defined by characteristics checked at the nodes of the path. For example, the concept C1 represents the set of patients having no involved lymph nodes and positive hormone receptors:
$$\[--><$$l>no{ \qquad\quad{\rm{\tf="courier" C}}\tf="courier" 1 \equiv & {\rm{\tf="courier" TumorPatient}} \cr & \sqcap \exists {\rm{\tf="courier" hasLymphNodes}}{\rm{\tf="courier" .}}\left\{ {{\rm{\tf="courier" n - }}} \right\} \cr & \sqcap \exists {\rm{\tf="courier" hasHormoneReceptors}}{\rm{\tf="courier" .}}\left\{ {{\rm{\tf="courier" hr + }}} \right\} $$
The C1 concept reifies the path from the root of the tree to the node marked (1) in Figure 1. In particular, this concept includes the two nominals n− and hr+. Reasoning in presence of nominals is discussed in Section 4.1 and detailed for example in Lutz et al. (Reference Lutz, Areces, Horrocks and Sattler2005), Sirin et al. (Reference Sirin, Grau and Parsia2006), and Kazakov et al. (Reference Kazakov, Kroetzsch and Simancik2012). An instance PAT of the TumorPatient concept satisfying every condition on the path from the root of the tree to the node (1) is recognized as an instance of C1. The path leading to the edge marked by (2) in Figure 1 is represented by the concept C2:
$$\[--><$$l>no{ \qquad\quad{\rm{\tf="courier" C2}} \equiv {\rm{\tf="courier" C1}} \cr \ \qquad\sqcap \,\exists {\rm{\tf="courier" hasAge}}{\rm{\tf="courier" .}}{{{\rm{\tf="courier" \lt }}}_{{\rm{\tf="courier" 35}}}} \cr \qquad \ \sqcap \,\neg \left( {\exists {\rm{\tf="courier" hasTumor}}{\rm{\tf="courier" .}}\left( {\exists {\rm{\tf="courier" hasSize}}{\rm{\tf="courier" .}}{{{\rm{\tf="courier" \lt }}}_{\rm{\tf="courier" 1}}} \sqcap \exists {\rm{\tf="courier" hasGrade}}{\rm{\tf="courier" .}}\,{{{\rm{\tf="courier" = }}}_{\rm{\tf="courier" 1}}}} \right)} \right) $$
Following the physician way of doing, a cancer patient is considered as a person and as a medical case. A medical case is, in turn, considered as a problem case to be solved, or for which a solution has to be found, that is, a cancer patient has a tumor for which a treatment has to be recommended. This leads to the notion of medical case-treatment axiom (see [mct-ax]) in the Kasimir system (as made precise below, [mct-ax] is a kind of problem-solution axiom, see [ps-ax]). In the DL framework, the concepts to be considered are MedicalCase, TumorPatient, Tumor, and Treatment.
A recommendation corresponds to a treatment to be applied: a specific treatment is represented by a subconcept of Treatment. For example, the [ax3] axiom represents the link existing between the class of patients C2 and a recommendation for a treatment based on a chemotherapy of level 1.
On a general level, the application of the protocol to a particular patient can be seen as a problem-solving task, where the problem corresponds to the description of the state of a cancer patient, that is, a medical case, and the solution to the description of a treatment that can be recommended according to the characteristics of the patient. The following elements are involved in the problem-solving model:
• Problems are represented by the ProblemCase concept.
• Solutions are represented by the SolutionCase concept.
• Axioms relate specific problems to specific solutions.
In terms of DL representation, the concepts to be considered are:
$$\[--><$$l> no{\qquad\quad & {\rm{\tf="courier" ProblemCase}} \sqsubseteq \exists {\rm{\tf="courier" hasSolution}}{\rm{\tf="courier" .SolutionCase}} \cr & {\rm{\tf="courier" MedicalCase}} \sqsubseteq {\rm{\tf="courier" ProblemCase}} \cr & {\rm{\tf="courier" hasRecommendation}} \sqsubseteq {\rm{\tf="courier" hasSolution}} $$
The [ps-ax] axiom is called a problem-solution axiom and can be used to guide DL reasoning for solving domain-specific problems, for example, decision support in oncology. In addition, the MedicalCase concept is a subconcept of ProblemCase and the hasRecommendation role is a subrole of the hasSolution role. The introduction of problem-solution axioms is a generic technique for problem-solving, and can be reused in any other specific domain, for example, diagnosis, recognition, classification. In addition, problem-solution axioms provide a basis for integrating DLs and CBR as explained in Section 3.
2.4 Description logic reasoning for decision support
Given two concepts C and D in an ontology O, the subsumption test checks whether C is subsumed by D (or C is more specific than D): formally, C is subsumed by D, denoted by
$$\[--><$>{\rm{\tf="courier" C}} \sqsubseteq {\rm{\tf="courier" D}} <$><!--$$
if, for every model
$$\[--><$>{\cal I} <$><!--$$
of O,
$$\[--><$>{{{\rm{\tf="courier" C}}}^{\cal I}} \sqsubseteq {{{\rm{\tf="courier" D}}}^{\cal I}} <$><!--$$
. Based on the subsumption test, the classification process consists in searching, for a given concept C, the concepts subsuming C and the concepts subsumed by C. The classification process allows to organize the concepts of an ontology into a concept hierarchy. In the Kasimir system, the concept hierarchy is used as a structure for representing a protocol.
The instance checking test checks whether an individual a is an instance of a concept C in an ontology O, that is, if for every model
$$\[--><$>{\cal I} <$><!--$$
of O,
$$\[--><$>{{{\rm{\tf="courier" a}}}^{\cal I}} \in {{{\rm{\tf="courier" C}}}^{\cal I}} <$><!--$$
. This test is a basis for the instantiation reasoning service that, given an individual a, consists in searching for the concepts C for which a is an instance of C. Decision support for protocol application is based on instantiation as follows. Relying on the problem-solution axiom [ps-ax], an individual recognized as an instance of the ProblemCase concept is linked to an instance of the SolutionCase concept through the hasSolution role.
Accordingly, an instance representing a cancer patient is first recognized as an instance of the concept MedicalCase and is then associated with an instance of the Treatment concept through the role hasRecommendation. For example, let us consider that the instance PAT is a cancer patient verifying the following assertions:
$$\[--><$$l>\qquad\quad \matrix{{{\rm{\tf="courier" TumorPatient}}\left( {{\rm{\tf="courier" PAT}}} \right)} \hfill \cr {{\rm{\tf="courier" Tumor}}\left( {\rm{\tf="courier" T}} \right)} \hfill \cr {{\rm{\tf="courier" hasTumor}}\left( {{\rm{\tf="courier" PAT ,}}\,{\rm{\tf="courier" T}}} \right)} {} \hfill \cr \\ {{\rm{\tf="courier" hasLymphNodes}}\left( {{\rm{\tf="courier" PAT,}}\,{\rm{\tf="courier" n - }}} \right)} \,\qquad\qquad\qquad\qquad\qquad\qquad\qquad \ \ \quad {\; \; \; \; no\,involved\,lymph\,node} \hfill \cr \\ {{\rm{\tf="courier" hasHormoneReceptors}}\left( {{\rm{\tf="courier" PAT,}}\,{\rm{\tf="courier" hr + }}} \right)} \,\qquad\qquad\qquad\qquad\qquad{\; \; \; \; positive\,hormone\,receptors} \hfill \cr \\ {{\rm{\tf="courier" hasAge}}\left( {{\rm{\tf="courier" PAT,}}\,{\rm{\tf="courier" 27}}} \right)} \qquad\qquad\qquad\qquad\qquad\qquad\qquad \ \ \ \ \quad\quad\quad\quad\quad\quad\quad\quad\quad \ \ \quad {\; \; \; \; age\leq \it 35} \hfill \cr \\ {{\rm{\tf="courier" hasGrade}}\left( {{\rm{\tf="courier" T,}}\,{\rm{\tf="courier" 1}}} \right)} \quad\quad\quad\quad\quad\quad\quad\quad\quad\quad \, \quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad \ {\; \; \; \; tumor\,of\,grade\,\it1} \hfill \cr \\ {{\rm{\tf="courier" hasSize}}\left( {{\rm{\tf="courier" T,}}\,{\rm{\tf="courier" 1}}{\rm{\tf="courier" .2}}} \right)} \quad \ \, \quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad\quad \ \ {\; \; \; \; tumor\,size\geq \it1} \hfill \cr \\ \\ \\ $$
The instantiation reasoning mechanism recognizes PAT as being an instance of the concept C2 (see axiom [ax2]). The axiom [ax3] states that a chemotherapy of level 1 is recommended for patients whose tumor satisfies the characteristics of the C2 concept. Formally, it can be inferred from the instantiation of C2 by PAT that there exists
$$\[--><$> {\rm{\tf="courier" x}} \in {\rm{\tf="courier" Level1Chemotherap}}{{{\rm{\tf="courier" y}}}^{\cal I}} <$><!--$$
such that
$$\[--><$> {\rm{\tf="courier" (PAT,}}\,{\rm{\tf="courier" x)}} \in {\rm{\tf="courier" hasRecommendatio}}{{{\rm{\tf="courier" n}}}^{\cal I}} <$><!--$$
, that is, the instance PAT is associated with the object x in
$$\[--><$> {\rm{\tf="courier" Level1Chemotherap}}{{{\rm{\tf="courier" y}}}^{\cal I}} <$><!--$$
through the hasRecommendation role.
The concept satisfiability test checks whether a concept C can be instantiated, that is, if there exists a model
$$\[--><$>{\cal I} <$><!--$$
of the ontology for which
$$\[--><$>{{C}^{\cal I}} \ne \emptyset <$><!--$$
. In addition, an ontology O is said to be unsatisfiable or inconsistent if O does not have any model, for example, O includes an instance of an unsatisfiable concept. In the Kasimir system, the concept satisfiability test is used during the validation of the protocol representation, for example, for checking whether a decision rule can be triggered. Moreover, it is assumed that the description of a cancer patient is correctly defined with respect to the protocol, that is, the protocol and the description of the patient constitute a consistent knowledge base. The DL reasoner is then used during the design of the protocol and the elaboration of the patient description for detecting inconsistencies to be (manually) repaired.
3 Protocol adaptation: from description logic reasoning to case-based reasoning
Section 2 explains how traditional DL inferences are carried out in the Kasimir system for decision support associated with the application of medical protocols. These protocols take into account the most common medical situations, that is, about 60–70% of the medical cases. For the non-standard medical cases, or out-of-protocol patients, the protocol cannot be directly applied. A decision has to be taken by a committee of physicians (having multiple specialties). During a meeting of this committee, a recommendation is established by adapting the solutions provided by the protocol for similar cases. For example, the breast cancer treatment protocol is designed for a female patient and cannot be directly applied to a male patient suffering from a breast cancer. A treatment for such a male patient can be established by reusing the recommendation provided by the protocol for a ‘similar female patient’, that is, considering the male patient as a female patient and adapting this recommendation. Actually, a precise and formal definition of an out-of-protocol patient does not exist. When the protocol cannot be applied in a direct and satisfactory way, the fact that a patient is declared as being out-of-protocol is decided by physicians. In the context of the Kasimir system, the protocol cannot be directly applied to an out-of-protocol patient because some characteristics of the patient are missing or are unknown. Then, the protocol has to be adapted.
The retrieval of a similar patient and the adaptation of the protocol can be taken into account by CBR. This is the purpose of the next sections to introduce the principles of CBR and to show how CBR is integrated within a DL formalism for protocol adaptation and decision support.
3.1 Principles of case-based reasoning
CBR is used in many applications to solve problems in so-called ‘weak theory domains’. CBR solves new problems by retrieving and adapting solutions of previously solved cases stored in a case base (Riesbeck & Schank, Reference Riesbeck and Schank1989; Kolodner, Reference Kolodner1993; Aamodt & Plaza, Reference Aamodt and Plaza1994).
A typical CBR cycle is composed of four main steps: given a new problem, called a target problem, the retrieval step selects a source case from a case base; the adaptation step builds a solution to the target problem, relying on the differences between the source and target problems, and modifying accordingly the solution of the retrieved source case; the revision step improves the current target solution depending on actual and expected system results; finally the retention (memorization) step stores the newly solved case for further reuse. As shown in Figure 2, among these steps, retrieval and adaptation are closely related and have a central place.
The case-based inference. (1) A target problem is provided to the CBR system. (2) The system retrieves a source problem similar to the target problem. (3) The source problem is a problem associated with a solution. (4) The system adapts this solution in order to solve the target problem
In CBR, the basic knowledge unit is the case that represents a problem-solving episode. More precisely, a case (pb, Sol(pb)) is a pair composed of a problem pb and a solution Sol(pb) of pb. A case base is a structured set of source cases denoted by (srce, Sol(srce)). The CBR process aims at solving a target problem, denoted by tgt, with respect to a case base. During the retrieval step, a source problem srce, considered to be similar to the target problem tgt, is searched for in the case base. During the adaptation step, the solution Sol(srce) of srce is adapted for building a solution Sol(tgt) of tgt. Then, the solution Sol(tgt) may be tested and repaired. A learning step may complete the process where the new case (tgt, Sol(tgt)) can be memorized for future reuse.
In knowledge intensive CBR (KI-CBR) (Aamodt, Reference Aamodt1990, Reference Aamodt1991; Gómez-Albarrán et al., Reference Gómez-Albarrán, Gonzàles-Calero, Díaz-Agudo and Fernàndez-Conde1999; Aamodt, Reference Aamodt2004), the CBR process relies on a formalized model of domain knowledge, such as a domain ontology, for case organization and retrieval (Lieber & Napoli, Reference Lieber and Napoli1996). In Section 3.2, it is shown how a KI-CBR system takes advantage of domain knowledge for adapting a decision protocol, on the basis of the reformulation model.
3.2 Principles of case-based reasoning in the Kasimir system
The model of reformulations introduced in Melis et al. (Reference Melis, Lieber and Napoli1998) is a general framework for modeling and representing adaptation knowledge into simple and separated components. A reformulation is a pair
$$\[--><$>({\rm{\tf="courier" r}},{{{\cal A}}_{\rm{\tf="courier" r}}}) <$><!--$$
where r is a relation between problems and
$$\[--><$>{{{\cal A}}_{\rm{\tf="courier" r}}} <$><!--$$
is an adaptation function: when r relates srce to tgt, then any solution Sol(srce) of srce can be adapted into a solution Sol(tgt) of tgt, thanks to the adaptation function
$$\[--><$>{{{\cal A}}_{\rm{\tf="courier" r}}} <$><!--$$
relating Sol(srce) to Sol(tgt) w.r.t. srce and tgt. Actually,
$$\[--><$>{{{\cal A}}_{\rm{\tf="courier" r}}} <$><!--$$
is a function depending on three inputs, namely srce, Sol(srce), and tgt (this is made precise below).
The operations corresponding to problem relations r and adaptation functions
$$\[--><$>{{{\cal A}}_{\rm{\tf="courier" r}}} <$><!--$$
have to be designed for a particular application, and, as well, a relevant strategy should be provided for building reformulations. Most of the time, and this is also true for the Kasimir system, reformulations are based on operations such as specialization, generalization, and substitution.
In the reformulation model, retrieval consists in finding a similarity path relating srce to tgt. Accordingly, a sequence of adaptation functions following the similarity path is reified into a corresponding adaptation path (see Figure 3).
On the first line, a similarity path from srce to tgt. On the second line, the corresponding adaptation path from Sol(srce) to Sol(tgt)
3.2.1 Similarity paths and adaptation paths
A similarity path SP from a problem srce to a problem tgt is a set SP of triples
$$\[--><$>\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{{\rm{\tf="courier" i - 1}}}},\,{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" i}}},\,{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" i}}}} \right) <$><!--$$
, i ∈ {1, 2, …, q}, where pb0 = srce and pbq = tgt, ri relates the pbi−1 and pbi problems and is such that there exists a reformulation
$$\[--><$>({{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" i}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" i}}}}}) <$><!--$$
in the available adaptation knowledge (constituted by a finite set of reformulations). Given Sol(srce), a solution of srce, and a similarity path from srce to tgt, the solution of tgt can be built, thanks to a sequential application of the adaptation functions
$$\[--><$>{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}}}},\, \ldots, \,{\rm{ and}}\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" q}}}}}<$><!--$$
:
$$\[--><$$l>{ \qquad\quad {\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 1}}}} \right)\, & = \,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_1}}}\left( {{\rm{\tf="courier" srce,}}\,{\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" srce}}} \right),\,{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 1}}}} \right) = {{{\cal A}}_{{{{\rm{\tf="courier" r}}}_1}}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 0}}},\,{\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 0}}}} \right),\,{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 1}}}} \right) \cr {\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 2}}}} \right)\, & = \,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_2}}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 1}}},\,{\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 1}}}} \right),\,{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" 2}}}} \right) \cr & \hskip -3.7pc\ldots \cr {\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" tgt}}} \right)\, & = \,{\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" q}}}} \right) = {{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" q}}}}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{{\rm{\tf="courier" q - 1}}}},\,{\rm{\tf="courier" Sol}}\left( {{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{{\rm{\tf="courier" q - 1}}}}} \right),\,{\rm{\tf="courier" p}}{{{\rm{\tf="courier" b}}}_{\rm{\tf="courier" q}}}} \right) \cr}$$
A similarity path is built according to a collection of available reformulations. Then several similarity paths relating two problems srce and tgt may exist. The choice between two similarity paths can be made either by the system according to an evaluation function or to an ‘external’ domain expert (as this is the case here). In the current implementation (see Section 5 and d'Aquin et al., Reference d'Aquin, Lieber and Napoli2006c for details), the set of available applicable operations, for example, specialization, generalization, substitution, is recursively used to enumerate the possible (non-cyclic) similarity paths. All possible solutions based on the different existing similarity paths are provided to the expert in charge of the decision.
This search for similarity paths respects the adaptation-guided retrieval principle (Smyth, Reference Smyth1996), where only source cases for which a solution is adaptable are retrieved, meaning and implying that adaptation knowledge is available. According to this principle, a similarity path provides a ‘symbolic reification’ of similarity between problems, allowing a case-based reasoner to build an understandable explanation of the results.
3.2.2 An example of application of reformulations to breast cancer treatment
Figure 4 presents a simplified example of the reformulation model for adapting the breast cancer treatment protocol. In this example, the tgt problem corresponds to the description of a patient for which the protocol cannot be directly applied. There are two reasons for that: (i) the patient is a man, and the protocol for breast cancer treatment takes into account only female patients, (ii) the tumor localization of this patient cannot be determined with precision in the breast, linked to the fact that the patient is a man. The other characteristics used for making a decision are related to the age of the patient, the size of the tumor, and the fact that the tumor has only one focal point.
An example of CBR problem-solving using reformulations, with similarity path from srce to tgt on first line and corresponding adaptation path from Sol(srce) to Sol(tgt) on the second line. CBR = case-based reasoning
Given the target problem tgt and the source case (srce, Sol(srce)), two reformulations, namely
$$\[--><$>({{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}}}}) <$><!--$$
and
$$\[--><$>({{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}}}}) <$><!--$$
, are applied for solving tgt. Considering the similarity path, that is, reading the figure from right to left, from tgt to srce, relation r2 denotes a substitution of Male Patient with Female Patient, while relation r1 denotes a substitution of Unknown Localization with Internal Localization. Considering the adaptation path, the
$$\[--><$>({{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}}}}) <$><!--$$
reformulation indicates that, when the localization of the tumor is unknown, the patient has to be considered as if she/he had an internal tumor, because it is the worst case, and thus, the one for which the largest treatment should be envisioned. The adaptation function
$$\[--><$>{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}}}} <$><!--$$
simply corresponds to a copy of the solution Sol(srce). The
$$\[--><$>({{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}},\,{{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}}}}) <$><!--$$
reformulation expresses that, since an ovary ablation is not applicable for a man, it has to be replaced with an hormone therapy having similar effects, that is, cures of an anti-oestrogen drug called tamoxifen.
For implementing a CBR system following this framework in a particular application domain, adaptation knowledge is needed, taking the form of a set of reformulations
$$\[--><$>({\rm{\tf="courier" r}},\,{{{\cal A}}_{\rm{\tf="courier" r}}}) <$><!--$$
. This knowledge acquisition issue is addressed for the Kasimir system in two complementary ways: (1) the acquisition of adaptation knowledge from experts is examined in d'Aquin et al. (Reference d'Aquin, Lieber and Napoli2006b), that is, a kind of ‘manual’ knowledge acquisition process, whereas (2) a knowledge discovery approach is proposed in d'Aquin et al. (Reference d'Aquin, Badra, Lafrogne, Lieber, Napoli and Szathmary2007), that is, a kind of semi-automatic learning process based on frequent itemset search. The work presented here focuses on the reasoning mechanism making use of such adaptation knowledge and therefore assumes that it is available.
3.3 Description logic reasoning for supporting case-based reasoning inferences
The inference mechanisms available within DL formalisms, namely subsumption and instantiation, can be used for implementing a CBR system (Salotti & Ventos, Reference Salotti and Ventos1998; Gómez-Albarrán et al., Reference Gómez-Albarrán, Gonzàles-Calero, Díaz-Agudo and Fernàndez-Conde1999). The subsumption relation organizes the concepts of an ontology into a hierarchy, that can be used in CBR as an indexing structure for the case base, for facilitating the retrieval of relevant source cases (Lieber & Napoli, Reference Lieber and Napoli1996; Napoli et al., Reference Napoli, Lieber and Curien1996). In this hierarchy, an index idx(srce) is an abstraction of srce, encoding the relevant elements in the srce description leading to the Sol(srce) solution. The index idx(srce) is represented by the concept Idx_Srce and is linked to a solution represented by the Idx_Sol_Srce concept. A problem-solution axiom relates the index concept Idx_Srce to an index solution concept Idx_Sol_Srce as follows:
Moreover, the source and target problems, respectively, denoted as srce and tgt in the CBR notation, are represented by instances in DLs, respectively, denoted by SRCE and TGT, while their solutions are represented by the instances SOL_SRCE and SOL_TGT. The individual SRCE is an instance of the index concept Idx_Srce, while the solution SOL_SRCE can be reused for any instance of the index concept Idx_Srce, that is, as soon as a problem TGT is recognized as an instance of Idx_Srce, the solution SOL_SRCE of SRCE can be reused to solve TGT.
The retrieval operation of CBR relies on instantiation for finding the index of a source problem having an adaptable solution. The similarity path built during retrieval relates the problem TGT to a problem PB0 (i.e. the source problem), such that PB0 is an instance of Idx_Srce:
The
$$\[--><$>\hookrightarrow<$><!--$$
arrow stands for ‘is an instance of’. The source problem represented by an instance of the index concept Idx_srce is attached to a source solution through a problem-solution axiom similar to the axioms [mct-ax] and [ps-ax] introduced above. Thus, as soon as PB0 is recognized as an instance of Idx_srce, the solution Sol_PB0 is put in correspondence with the solution SOL_SRCE of SRCE. Therefore, the associated adaptation path is
As an application, let us consider the example introduced in Figure 4. The target problem (on the right) can be represented as
$$\[--><$$l>\qquad\quad \matrix{{{\rm{\tf="courier" TumorPatient(TGT)}}} \hfill \cr \\ {{\rm{\tf="courier" Male(S)}}} \hfill \cr \\ {{\rm{\tf="courier" hasGender(TGT,S)}}} \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \ \, \qquad {male\,gender}\hfill \cr \\ {{\rm{\tf="courier" hasAge(TGT,}}\,{\rm{\tf="courier" 55)}}} \qquad \qquad \qquad \qquad \qquad \qquad \qquad \,\qquad \qquad \quad \,\qquad{age\,between \ \it20 \ and \ \it 75}\hfill \cr \\ {{\rm{\tf="courier" hasTumor(TGT,}}\,{\rm{\tf="courier" T)}}} \hfill \cr \\ {\neg {\rm{\tf="courier" MultifocalTumor(T)}}} \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \quad \, \qquad unifocal \ tumor\hfill \cr \\ {{\rm{\tf="courier" UnknownLoc(L)}}} \hfill \cr \\ {{\rm{\tf="courier" hasLocalization(T,}}\,{\rm{\tf="courier" L)}}} \qquad \qquad \qquad \qquad \qquad \qquad \ \, \qquad {\; \; \; \; unknown\,tumor\,localization} \hfill \cr \\ {{\rm{\tf="courier" hasSize(T,}}\,{\rm{\tf="courier" 5}}{\rm{\tf="courier" .2)}}} \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \qquad \ \quad{\; \; tumor\,size\,between \ \it 4 \ and \ \it 7}\hfill $$
The index concept of the source problem in Figure 4 is represented by the concept Idx_Srce ([ax4]) with the problem-solution axiom introducing the concept Idx_Sol_Srce, that is, the recommended treatment ([ax45]):
$$\[--><$$l>no{ \qquad\quad {\rm{\tf="courier" Idx\_Srce}} \equiv & {\rm{\tf="courier" TumorPatient}} \cr & \sqcap \exists {\rm{\tf="courier" hasGender}}{\rm{\tf="courier" .Female}} \cr & \sqcap \exists {\rm{\tf="courier" hasAge}}{\rm{\tf="courier" .}}\,{{\geq }_{{\rm{\tf="courier" 20}}}} \cr & \sqcap \exists {\rm{\tf="courier" hasAge}}{\rm{\tf="courier" .}}\,{{\leq }_{{\rm{\tf="courier" 75}}}} \cr & \sqcap \exists {\rm{\tf="courier" hasTumor}}{\rm{\tf="courier" .}} \ {\rm{\tf="courier" (}}\neg {\rm{\tf="courier" MultifocalTumor}} \cr & \; \; \; \; \; \; \; \; \; \; \; \; \qquad \ \ \ \quad\sqcap \exists {\rm{\tf="courier" hasLocalization}}{\rm{\tf="courier" .Internal}} \cr \; \; \; \; \; \; \; \; \; \; \; \; & \qquad\qquad\qquad \ \quad\sqcap \exists {\rm{\tf="courier" hasSize}}{\rm{\tf="courier" .}}\,{{\geq }_{\rm{\tf="courier" 4}}} \cr \; \; \; \; \; \; \; \; \; \; \; \; & \qquad\qquad\qquad \ \quad\sqcap \exists {\rm{\tf="courier" hasSize}}{\rm{\tf="courier" .}}\,{{\leq }_{\rm{\tf="courier" 7}}})$$
The BreastAndOvaryAblation concept corresponds to Idx_Sol_Srce and represents treatments composed of a breast ablation and an ovary ablation. The similarity path built by the CBR retrieval operation corresponds to the similarity path shown in Figure 4:
TGT is an instance of TumorPatient with the properties corresponding to the characteristics of the patient to be treated. PB0 and PB1 are also instances of TumorPatient. According to r2, PB1 is introduced with the same set of assertions as TGT, except for the gender:
According to r1, PB0 (the source problem) is introduced with the same set of assertions as PB1, except for the localization of the tumor:
$$\[--><$$l>\qquad\quad \matrix{{\neg {\rm{\tf="courier" MultifocalTumor}}({{{\rm{\tf="courier" T}}}_0})} \hfill \cr \\ {{\rm{\tf="courier" hasTumor}}({\rm{\tf="courier" P}}{{{\rm{\tf="courier" B}}}_0},\,{{{\rm{\tf="courier" T}}}_{\rm{\tf="courier" 0}}})} \hfill \cr \\ {{\rm{\tf="courier" Internal}}({{{\rm{\tf="courier" L}}}_0})} \hfill \cr \\ {{\rm{\tf="courier" hasLocalization}}({{{\rm{\tf="courier" T}}}_0},\,{{{\rm{\tf="courier" L}}}_{\rm{\tf="courier" 0}}})} $$
Then, PB0 is recognized as an instance of the index concept Idx_Srce (see axiom [ax4]) and is linked to the solution SOL_PB0 of the Idx_Sol_Srce treatment concept, that is, a surgery consisting of a breast ablation and an ovary ablation (see axiom [ax5]). The adaptation of the solution is based on the adaptation path:
The instance SOL_PB1 is a copy of SOL_PB0 (application of
$$\[--><$> {{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 1}}}}} <$><!--$$
), and SOL_TGT is obtained by replacing the ovary ablation in SOL_PB1 by cures of tamoxifen (application of
$$\[--><$> {{{\cal A}}_{{{{\rm{\tf="courier" r}}}_{\rm{\tf="courier" 2}}}}} <$><!--$$
):
4 Using distributed description logics for reasoning with multiple viewpoints
Oncology, like many other medical domains, involves several medical specialties. Thus, decision knowledge embedded in the protocols combines aspects from different specialties within several viewpoints. Each of these viewpoints constitutes a suitable way within a specialty for representing, organizing, and using decision knowledge. Indeed, a cancer specialist will use different elements of knowledge, and different representations of the patient according to his/her interest, for example, for establishing a surgical treatment or a chemotherapy.
In this section, we introduce an original way of representing viewpoints in a distributed environment, namely DDLs. In addition, we show how CBR can be used for problem-solving in a particular application domain.
4.1 The modularization of oncology protocols
Multiple viewpoints are visible in the structure of protocols. For example, the protocol for breast cancer treatment is based on several ‘sub-protocols’, each of them focusing on a particular phase of the medical treatment, that is, preoperative chemotherapy, surgery, radiotherapy, and complementary treatment, involving one or more specialties of oncology, among chemotherapy, surgery, radiotherapy, and hormonotherapy. A sub-protocol relies on its own vocabulary and provides a particular recommendation, in a given phase of the treatment, using only specific characteristics for this task. In addition, the breast therapeutic decision committee whose role is to adapt the content of the protocol for out-of-protocol cases, includes experts from different oncology specialties. An expert brings his/her own contribution to the solution, according to the specialty he/she depends on, and collaborates with the experts from other specialties, in the construction of a global and satisfactory solution.
DDLs are extensions of DLs in which several local ontologies are considered to be related through semantic mappings (Borgida & Serafini, Reference Borgida and Serafini2002, Reference Borgida and Serafini2003). Hereafter, it is shown how knowledge representation and reasoning based on the DDL framework is used within the Kasimir system for taking into account the multiple viewpoints of the oncology specialties. Actually, the representation of the protocol presented in Section 2.3 is modularized, meaning that it is reified as a multi-viewpoint representation relying on the principles of DDLs. Nevertheless, the characteristics of the representation introduced in Section 2.3 remain valid and are used locally in each viewpoint.
Note on the distributed description logic implementation of viewpoints
In the following, the emphasis is put on the design principles for multi-viewpoint representation of medical protocols, actually on what is expected to be achieved with DDLs. Consequently, some of the examples introduced in this section, as well as their representation in DDL, relies on characteristics going beyond the possibilities offered by the current implementation of the DDL formalism (e.g. the Drago system; Serafini and Tamilin, Reference Serafini and Tamilin2005; Tamilin, Reference Tamilin2007). In addition to showing what is expected to be achieved with DDLs and the Drago system, these examples are intended to provide real-world use-cases to be used for guiding further developments in DDLs.
In particular, the DDL formalism did not allow the use of nominals in bridge rules and this is still the case in the current version of the Drago system. Luciano Serafini, one of the initiators of the DDL formalism, has proposed a formalism and a tableau algorithm for dealing with mappings and axioms involving nominals in DDLs (Serafini, Reference Serafini2007; Homola & Serafini, Reference Homola and Serafini2010; Serafini & Homola, Reference Serafini and Homola2012). Thus, the use of nominals in axioms hereafter is justified. However, in practice, the multi-viewpoint representation of the breast cancer treatment protocol implemented within the Kasimir system is a simplification of what is presented in the following. In particular, nominals are replaced with atomic concepts having only one instance, namely the nominal that has to be considered. When the system has to deal with multiple nominals in expressions such as sets of nominals, an atomic concept is introduced for every nominal, with the constraint that these atomic concepts are mutually disjoint. Replacing nominals with atomic concepts is a simplification leading to an inelegant way of implementing the system: it is not easy to get a generic construction and many atomic concepts have to be introduced. Fortunately, the proposition in Serafini (Reference Serafini2007) and Homola and Serafini (Reference Homola and Serafini2010) allows the implementers to adapt the coding of the system and to propose more generic and efficient constructions for DDLs.
4.2 Distributed description logics and C-OWL
DDLs have been introduced in Borgida and Serafini (Reference Borgida and Serafini2002) and are the basis of the C-OWL extension of OWL for representing contextualized ontologies (Bouquet et al., Reference Bouquet, Giunchiglia, van Harmelen, Serafini and Stuckenschmidt2004). Contextualized ontologies are local representations of a domain, called contexts, that are semantically related through mappings. In the present framework, DDLs are used for formalizing and implementing several complementary representations of the oncology domain called viewpoints.
4.2.1 Syntax and semantics
In a DDL, the knowledge about a domain is distributed over a set of contexts. A context Oi is an ontology, with a proper language and a proper interpretation. A mapping between contexts Oi and Oj is expressed through a set of bridge rules from Oi to Oj allowing to declare a correspondence between the interpretation domains of the two contexts. In this way, knowledge units in Oi can be interpreted and reused in (terms of) Oj.
Formally, a context space includes a set of contexts {Oi}i ∈I, where I is a set of indexes for contexts. The indexes in I are used to prefix the expressions, in associating an expression with the context in which it is defined. For example, i:C, i:∃R.C, i:a, i:C⊑D, and i:C(a), are expressions of the local language in Oi.
The semantics of a context space is given by a distributed interpretation
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
, including an interpretation
$$\[--><$>{{{\cal I}}_i} <$><!--$$
for each
$$\[--><$>i \in I <$><!--$$
.
$$\[--><$>{{{\cal I}}_i} <$><!--$$
is defined by a local interpretation domain
$$\[--><$>{{\rDelta }^{{\cal I}{{}_i}}} <$><!--$$
and a local interpretation function
$$\[--><$>.^{{{{{\cal I}}_i}}} <$><!--$$
. A context is interpreted with the corresponding local interpretation, that is, an axiom or an assertion of Oi is satisfied by
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
if it is satisfied by
$$\[--><$>{{{\cal I}}_i} <$><!--$$
.
A mapping
$$\[--><$>{{{\cal M}}_{ij}} <$><!--$$
is a set of bridge rules from Oi to Oj. There are different types of bridge rules between concepts, instances or roles, of two contexts. An into rule is a bridge rule of the form
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" C}}\,\mathop{\longrightarrow}\limits^{ \sqsubseteq }\,{\rm{\tf="courier" j}}{\rm{\tf="courier" :}}{\rm{\tf="courier" D}} <$><!--$$
, where i:C and j:D are concepts, respectively, from Oi and Oj. This rule means that the concept i:C of Oi is considered, from the viewpoint of Oj, as being more specific than the concept j:D. The onto rule
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" C}}\,\mathop {\longrightarrow}\limits ^{ \sqsupseteq }\,{\rm{\tf="courier" j:D}} <$><!--$$
means that the concept i:C is considered in Oj to be more general than j:D. Bridge rules are directional: a bridge rule from Oi to Oj is considered from the viewpoint of Oj, and thus,
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" C}}\mathop{\longrightarrow}\limits^{ \sqsubseteq }{\rm{\tf="courier" j}}{\rm{\tf="courier" :}}{\rm{\tf="courier" D}} <$><!--$$
is not equivalent to
$$\[--><$>{\rm{\tf="courier" j}}:{\rm{\tf="courier" D}}\mathop{\longrightarrow}\limits^{ \sqsupseteq }{\rm{\tf="courier" i}}{\rm{\tf="courier" :}}{\rm{\tf="courier" C}} <$><!--$$
.
Formally, the distributed interpretation
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
of a context space is associated with a set of domain relations. A domain relation
$$\[--><$>{{r}_{ij}} \subseteq {{\rDelta }^{{{{\cal I}}_i}}} \,\times \,{{\rDelta }^{{{{\cal I}}_j}}} <$><!--$$
states, for an arbitrary object of
$$\[--><$>{{\rDelta }^{{{{\cal I}}_i}}} <$><!--$$
, the object of
$$\[--><$>{{\rDelta }^{{{{\cal I}}_j}}} <$><!--$$
it corresponds to. The notation
$$\[--><$>{{r}_{ij}}\left( {{{{\rm{\tf="courier" C}}}^{{{{\cal I}}_i}}} } \right) <$><!--$$
denotes the interpretation of the concept i:C of Oi considered in the interpretation domain of Oj. The semantics of a bridge rule is given with respect to domain relations:
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" C}}\,\mathop{\longrightarrow}\limits^{ \sqsubseteq }{\rm{\tf="courier" j}}{\rm{\tf="courier" :}}{\rm{\tf="courier" D}} <$><!--$$
if
$$\[--><$>{{r}_{ij}}\left( {{{{\rm{\tf="courier" C}}}^{{{{\cal I}}_i}}} } \right) \subseteq {{{\rm{\tf="courier" D}}}^{{{{\cal I}}_j}}} <$><!--$$
and
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" i}}{\rm{\tf="courier" :}}{\rm{\tf="courier" C}}\mathop{\longrightarrow}\limits^{ \sqsupseteq}{\rm{\tf="courier" j}}\,:\,{\rm{\tf="courier" D}} <$><!--$$
if
$$\[--><$>{{r}_{ij}}\left( {{{{\rm{\tf="courier" C}}}^{{{{\cal I}}_i}}} } \right) \supseteq {{{\rm{\tf="courier" D}}}^{{{{\cal I}}_j}}} <$><!--$$
.
Another form of bridge rules can be used to specify a correspondence between instances.
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" a}}\,\mathop{\longrightarrow}\limits^{ \equiv }{\rm{\tf="courier" j:b}} <$><!--$$
means that the instance i : a in Oi corresponds to the instance j:b in Oj. Formally,
$$\[--><$>{\tf="Fraktur" J} <$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" a}}\mathop{\longrightarrow}\limits^{ \equiv }{\rm{\tf="courier" j}}{\rm{\tf="courier" :}}{\rm{\tf="courier" b}} <$><!--$$
if
$$\[--><$>{{r}_{ij}}\left( {{{{\rm{\tf="courier" a}}}^{{{{\cal I}}_i}}} } \right) = {{{\rm{\tf="courier" b}}}^{{{{\cal I}}_j}}} <$><!--$$
.
4.2.2 Global and local reasoning
Local reasoning services in DDL are the standard DL reasoning services, performed in a particular context, without taking into account the bridge rules. A global reasoning service takes advantage of bridge rules for inferring statements in a context in using knowledge from other contexts. In Serafini and Tamilin (Reference Serafini and Tamilin2004) and Tamilin (Reference Tamilin2007), an extension of the standard tableau algorithm for the computation of the global subsumption test in DDLs is presented. Global subsumption relies on the principle of ‘subsumption propagation’ that, in its simplest form, can be expressed as
if the mapping
$$\[--><$>{{{\cal M}}_{ij}}<$><!--$$
contains ‘
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" E}}\mathop {\longrightarrow}\limits ^{ \sqsupseteq }{\rm{\tf="courier" j}}:{\rm{\tf="courier" C}}<$><!--$$
’ and ‘
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" F}}\mathop {\longrightarrow}\limits ^{ \sqsubseteq }{\rm{\tf="courier" j}}:{\rm{\tf="courier" D}}<$><!--$$
’
then ‘
$$\[--><$>{\tf="Fraktur" J}<$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" i}}{\rm{\tf="courier" :}}{\rm{\tf="courier" E}}\, \sqsubseteq \,{\rm{\tf="courier" F}}<$><!--$$
’ implies that ‘
$$\[--><$>{\tf="Fraktur" J}<$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" j}}:{\rm{\tf="courier" C}} \sqsubseteq {\rm{\tf="courier" D}}<$><!--$$
’
Intuitively, this means that subsumption in a particular context can be inferred from subsumption in another context, thanks to bridge rules. Similarly, global instance checking is based on an instantiation propagation rule:
if
$$\[--><$> {{{\cal M}}_{ij}} <$><!--$$
includes ‘
$$\[--><$>{\rm{\tf="courier" i}}\,:\,{\rm{\tf="courier" C}}\,\mathop {\longrightarrow}\limits ^{ \sqsubseteq }\,{\rm{\tf="courier" j}}:{\rm{\tf="courier" D}}<$><!--$$
’ and ‘
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" a}}\mathop{\longrightarrow}\limits^{ \equiv }{\rm{\tf="courier" j:b}}<$><!--$$
’
then ‘
$$\[--><$>{\tf="Fraktur" J}<$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" i}}:{\rm{\tf="courier" C}}({\rm{\tf="courier" a}})<$><!--$$
’ implies that ‘
$$\[--><$>{\tf="Fraktur" J}<$><!--$$
satisfies
$$\[--><$>{\rm{\tf="courier" j}}:{\rm{\tf="courier" D}}({\rm{\tf="courier" b}})<$><!--$$
’
Instantiation is extended for global instance checking. Based on bridge rules, information known about an instance in a particular context can be completed using inferences made in other contexts. It can be noticed that bridge rules relating instances, as well as global instance checking, were introduced in the Drago system (Tamilin, Reference Tamilin2007), being in part motivated by the needs of the Kasimir system.
4.3 Representation of oncology viewpoints using distributed description logics
Modeling and formalizing a multiple viewpoint representation within a DDL is a decentralized task, that is, there is no need to set up a consensus, but there is a need to distinguish viewpoints. Three main steps can be considered (see Figure 5): (1) determine the relevant viewpoints in the domain, (2) build a local ontology for every viewpoint, and (3) establish mappings between local ontologies, reifying correspondences between viewpoints.
Three main steps can be considered for representing knowledge according to multiple viewpoints: determining viewpoints, building a local ontology, and mapping ontologies
4.3.1 Determining viewpoints
A large and complex domain is often organized according to various sub-domains, for example, services, tasks, working groups, communities. Such an organization provides a prior division of the domain into viewpoints, that can be reused by determining the viewpoints to be represented in an application. In the same way, the protocol for breast cancer treatment is considered to be composed of four main treatment phases, involving the following oncology specialties: presurgical chemotherapy (pc), surgery (s), radiotherapy (r), and complementary treatment (ct: hormonotherapy and/or chemotherapy). Although they exist for themselves, these four treatment phases are interrelated, that is, in some situations, the decision taken for a particular phase depends on decision units lying in another one. This division of oncology knowledge is daily used by physicians and is well suited for their work. Accordingly, in the Kasimir system, this division supports four viewpoints, namely Opc, Os, Or, and Oct, respectively, corresponding to the specialties pc, s, r, and ct. A fifth viewpoint could be considered as well: viewing the patient as a person, with, for example, administrative data, habits, geographical data. However, this supplementary viewpoint was not introduced for keeping the example as simple as possible.
4.3.2 Building a local ontology
Building a local ontology consists in formalizing a context in DDL corresponding to a viewpoint. A local ontology includes the knowledge units considered to be useful within the current viewpoint, independently from the other viewpoints, that is, a context in DDL formalizing a local ontology only implements knowledge units relevant to the viewpoint.
Decisions in the different specialties depend on different characteristics of the patient. Therefore, different concepts, representing a patient with different roles, are used for taking into account the protocol according to a given viewpoint. For example, in surgery, a patient with a directly operable and non-multifocal tumor has to be treated with a partial ablation of the breast. This is represented by the following axioms in Os:
$$\[--><$$l>no{ \qquad\quad {\rm{\tf="courier" s}}{\rm{\tf="courier" :}}{\rm{\tf="courier" C}} \equiv & {\rm{\tf="courier" TumorPatient}} \cr & \sqcap \exists {\rm{\tf="courier" hasTumor}}{\rm{\tf="courier" .}}\, {\rm{\tf="courier" (OperableTumor}} \cr & \qquad\qquad \, \quad\qquad\sqcap \exists {\rm{\tf="courier" hasFocus}}{\rm{\tf="courier" .SimpleFocus)}} $$
In radiotherapy, the considered characteristics are related to the recommended surgery, to the localization of the tumor in the breast, the size, and the presence of malignant cells in the lymph nodes:
$$\[--><$$l> no{\qquad\quad {\rm{\tf="courier" r}}:{\rm{\tf="courier" C}} \equiv & {\rm{\tf="courier" TumorPatient}} \cr & \sqcap \exists {\rm{\tf="courier" hasRecommendedSurgery}}{\rm{\tf="courier" .PreservingAblation}} \cr & \sqcap \exists {\rm{\tf="courier" hasLymphNodes}}{\rm{\tf="courier" .}}\left\{ {{\rm{\tf="courier" n - }}} \right\} \cr & \sqcap \exists {\rm{\tf="courier" hasTumor}}{\rm{\tf="courier" .}}\left( {\exists {\rm{\tf="courier" hasLocalization}}{\rm{\tf="courier" .InferoInternal}}} \right) $$
$$\[--><$$l> no{\qquad\quad {\rm{\tf="courier" r}}:{\rm{\tf="courier" RadiotherapyBreastAndEIMC}} \equiv & {\rm{\tf="courier" Irradiation}} \cr & \sqcap \exists {\rm{\tf="courier" hasZone}}{\rm{\tf="courier" .Breast}} \cr & \sqcap \exists {\rm{\tf="courier" hasZone}}{\rm{\tf="courier" .EIMC}} $$
These axioms state that a patient with a preserving surgery recommendation, non-involved lymph nodes, and a tumor located in the infero-internal part of the breast, has to be treated by a radiotherapy of the breast and a radiotherapy of the extended internal mammary chain (EIMC).
In the context Oct the choice of the complementary treatment is guided by characteristics such as the status of the hormone receptors, the number of involved lymph nodes, the age of the patient, the size of the tumor, and the grade (1, 2, or 3). For example, the protocol states that a patient whose age is <35, with no involved lymph nodes, positive hormone receptors, a tumor of grade ≥2, or of size ≥1 cm, has to be treated by a chemotherapy of level 1:
$$\[--><$$l>no{ \qquad\quad {\rm{\tf="courier" ct}}:{\rm{\tf="courier" C}} \equiv & {\rm{\tf="courier" TumorPatient}} \cr & \sqcap \exists {\rm{\tf="courier" hasAge}}{\rm{\tf="courier" .}}\,{{\leq }_{{\rm{\tf="courier" 35}}}} \cr & \sqcap \exists {\rm{\tf="courier" numberInvolvedLymphNodes}}{\rm{\tf="courier" .}}\left\{ {\rm{\tf="courier" 0}} \right\} \cr & \sqcap \exists {\rm{\tf="courier" hasHormoneReceptors}}{\rm{\tf="courier" .}}\left\{ {{\rm{\tf="courier" hr + }}} \right\} \cr & \sqcap \neg \exists {\rm{\tf="courier" hasTumor}}{\rm{\tf="courier" .}}\left( {\exists {\rm{\tf="courier" hasGrade}}{\rm{\tf="courier" .}}\,{{{\rm{\tf="courier" = }}}_{\rm{\tf="courier" 1}}} \sqcap \exists {\rm{\tf="courier" hasSize}}{\rm{\tf="courier" .}}{{{\rm{\tf="courier" \lt }}}_{\rm{\tf="courier" 1}}}} \right) $$
4.3.3 Mapping ontologies
The relations existing between viewpoints are materialized through mappings between local ontologies. An important question concerns the knowledge units that can be shared and reused from a given viewpoint in another viewpoint. Thus, it is important to make precise the correspondences between viewpoints, indicating how a given context may take advantage of knowledge units in another context.
In the current example, a local ontology represents the vision of one or two specialties of oncology, playing a role in a particular phase of the treatment. Surgery is the central phase of the treatment and takes place after presurgical chemotherapy: then, decisions in surgery follow decisions in presurgical chemotherapy accordingly. In the same way, radiotherapy and complementary treatment aim at complementing surgery (for eliminating remaining involved cells with radiotherapy, chemotherapy, or hormonotherapy). The decision in these two viewpoints depends on the knowledge units in the surgery viewpoint. Figure 6 summarizes the existing mappings between the viewpoints introduced above. An arrow from a context Oi to a context Oj indicates the existence of a non-empty mapping
$$\[--><$>{{{\cal M}}_{ij}} <$><!--$$
.
The mappings existing between viewpoints (contexts) in the multiple viewpoint representation of the protocol for breast cancer treatment
In this framework, bridge rules are used either for sharing knowledge on patients between the viewpoints or for representing the influence of a decision in a particular viewpoint on the decision in another viewpoint. For example, decisions in radiotherapy and in complementary treatment both rely on the status of the lymph nodes—either involved or not—even if this information unit is represented differently in Or and Oct. The sharing of this characteristic of the patient between Or and Oct can be represented by the bridge rules [br1] and [br2].
In sequence, a decision in radiotherapy depends on the recommended treatment in surgery, either preserving, that is, a partial ablation preserving the essential part of the breast, or not preserving. The influence of the treatment in surgery on the treatment in radiotherapy is reified in the following bridge rule, allowing to complete a decision for the patient in Or with the recommendation decided in Os (bridge rule [br3]):
4.4 Distributed description logic reasoning for decision support in oncology
In the Kasimir system, decision support based on multiple viewpoints is performed by global reasoning services provided by DDLs, mainly global instantiation (see Section 4.2.2). This reasoning service is extended to a decentralized CBR mechanism for case adaptation.
4.4.1 Global instantiation for protocol application
Solving a problem in a multi-viewpoint framework with CBR is a decentralized process: inferences occur locally, in each viewpoint represented by a context in DDL, taking advantage of bridge rules for reusing the knowledge and inferences from the other viewpoints. This problem-solving approach is similar to a reasoning process in decentralized artificial intelligence, defined in Demazeau and Müller (Reference Demazeau and Müller1989) as concerning the activity of autonomous intelligent agents that coexist and collaborate with other agents, each agent having proper goals and proper knowledge.
Hereafter, a specific example shows how global instantiation is used for applying the protocol in a decentralized reasoning approach. In the example, the considered patient is 33 years old, is suffering from breast cancer, with a tumor having the following characteristics: non-multifocal tumor of grade 2, with a size of 1.8 cm, directly operable, localized in the infero-internal part of the breast, with positive hormone receptors, and no involved lymph node. The physician having to establish a treatment for this patient may consider the above characteristics according to one or several viewpoints, among the four available viewpoints, that is, Opc, Os, Or, and Oct. However, according to domain knowledge, the viewpoint ‘presurgical chemotherapy’ cannot be considered in the present case. Thus, the physician is interested in the recommendations of the protocol for the three other viewpoints. The patient is represented by three local instances of the TumorPatient concept, namely: s:P (surgery), r:P (radiotherapy), and ct:P (complementary treatment) (see Figure 7).
The assertions describing the patient P to be treated in the three considered contexts
Equivalence bridge rules make precise the fact that the different instances introduced in the viewpoints denote a same patient:
$$\[--><$$l> no{ \qquad\quad & {\rm{\tf="courier" s}}:{\rm{\tf="courier" P}}\,\mathop{\longrightarrow}^{ \equiv }\,{\rm{\tf="courier" r}}\,{\rm{\tf="courier" :}}\,{\rm{\tf="courier" P}} \cr & {\rm{\tf="courier" r}}:{\rm{\tf="courier" P}}\,\mathop{\longrightarrow}^{ \equiv }\,{\rm{\tf="courier" ct}}\,{\rm{\tf="courier" :}}\,{\rm{\tf="courier" P}} \cr & {\rm{\tf="courier" ct:P}}\,\mathop{\longrightarrow}^{ \equiv }\,{\rm{\tf="courier" s}}\,{\rm{\tf="courier" :}}\,{\rm{\tf="courier" P}} \cr} $$
Based on the assertions introduced in Os and on the axioms associated with the protocol in Os, namely [axS1] and [axS2], it can be inferred that a partial ablation is recommended for the patient in surgery (knowing that a directly operable tumor is an operable tumor). Accordingly, the bridge rule [br3] is used to complete the information known on the patient in radiotherapy, r:P is recognized as an instance of
$$\[--><$>{\rm{\tf="courier" r}}:\exists {\rm{\tf="courier" hasRecommendedSurgery}}{\rm{\tf="courier" . \ PreservingAblation}} <$><!--$$
.
Relying on the axioms [axR1], [axR2], and [axR3], in Or, a radiotherapy of the breast and of the EIMC is recommended (RadiotherapyBreastAndEIMC). Now, the bridge rule [br1] allows to reuse information in Or concerning involved lymph nodes in Oct. Then, ct : P is considered as an instance of ct : ∃numberInvolvedLymphNodes.{0}. The axioms [axCT1] and [axCT2] in Oct allow to infer that a chemotherapy of level 1 is recommended for the patient ct:P. Finally, the global solution recommended by the protocol is composed of three instances of Treatment, that is, three complementary viewpoints on the solution:
$$\[--><$$l> { \qquad\quad &{\rm{\tf="courier" s}}:{\rm{\tf="courier" PartialAblation}} \cr & {\rm{\tf="courier" r:RadiotherapyBreastAndEIMC}} \cr & {\rm{\tf="courier" ct:Level1Chemotherapy}} \cr} $$
This decentralized problem-solving approach provides a decentralized solution composed of elements of solution for every viewpoint that has been considered during the problem-solving process. These three treatments do not represent alternatives, but different recommendations made by the system for the different phases of treatment, built from local knowledge in each viewpoint and taking into account the influence of viewpoints on one another.
4.4.2 Decentralized case-based reasoning for protocol application
Decentralized CBR (DzCBR) is the CBR mechanism defined in a framework based on multiple viewpoint representation, such as a multi-viewpoint protocol. DzCBR relies on DDL bridge rules. The target problem is divided into a set of local target problems
$$\[--><$>{{\left\{ {{\rm{\tf="courier" i}}:{\rm{\tf="courier" TGT}}} \right\}}_i} <$><!--$$
, one local target problem i:TGT for a particular viewpoint (context Oi). Equivalence bridge rules such as
$$\[--><$>\left\{ {{\rm{\tf="courier" i}}:{\rm{\tf="courier" TGT}}} \right\}\,\mathop{\longrightarrow}\limits^{ \equiv }\,{\rm{\tf="courier" j}}{\rm{\tf="courier" :}}{\rm{\tf="courier" TGT}} <$><!--$$
are declared between local target problems i:TGT and
$$\[--><$>{\rm{\tf="courier" j}}:{\rm{\tf="courier" TGT}}\left( {i \ne j} \right) <$><!--$$
, for making precise the fact that a local target problem is a view of the global target problem in a given viewpoint. The DzCBR mechanism relies on two main operations, materializing, respectively, the localized and the collaborative components of the reasoning process:
1. Local CBR works on local knowledge for building a local solution i:SOL_TGT of the local target problem i:TGT. Local CBR relies on the CBR problem-solving approach introduced in Section 3. Since local CBR is restricted to one particular viewpoint, it can be carried out in each context independently from the others.
2. Case completion is the collaborative step of DzCBR. It is based on bridge rules and global instantiation for completing the local target case, either the problem i:TGT or the solution i:SOL_TGT, thanks to knowledge sharing with the other viewpoints.
Local CBR and case completion are performed in each context Oi, until no more inferences can be drawn. The solution finally delivered corresponds to a set of local solutions, {i:SOL_TGT}i, provided by the local CBR processes and by the collaboration between viewpoints through bridge rules (as this is described in the preceding section on global instantiation for protocol application). Therefore, DzCBR is applied in the Kasimir system for protocol adaptation relying on a multiple viewpoint representation of the protocol (d'Aquin et al., Reference d'Aquin, Lieber and Napoli2005b).
5 Discussion
5.1 Representation and reasoning with medical knowledge
There is a long history of research in medical informatics concerning formalization, capitalization, and automated use of medical knowledge, from the first expert systems (Clancey & Shortliffe, Reference Clancey and Shortliffe1984; Marcus, Reference Marcus1988) to Semantic Web portals such as the Kasimir semantic portal. In relation with the topic of this paper, several languages have been developed for the representation of medical guidelines and protocols, allowing a partial automated use of the protocol content. As shown in the survey (Peleg et al., Reference Peleg, Tu, Bury, Ciccarese, Fox, Greenes, Hall, Johnson, Jones, Kumar, Miksch, Quaglini, Seyfang, Shortliffe and Stefanelli2003), these languages are generally focused on task-centric protocols, in the sense that the medical knowledge is represented in terms of sequences of actions. By contrast, the protocols represented within the Kasimir system are patient-centered and based on knowledge representation languages such as DLs and DDLs. The representation of sequences of decisions and actions was not taken into account in the present paper, but could be considered in the future, for example, reifying the sequence in which treatments have to be applied. Actually, there is an on-going research work on the analysis and representation of patient pathways in the team of the authors (Jay et al., Reference Jay, Napoli and Kohler2006, Reference Jay, Kohler and Napoli2008; Egho et al., Reference Egho, Jay, Raïssi and Napoli2011). The sequence of treatments are not so easy to integrate in a DL-based representation system, and requires the use of adapted temporal extensions, such as the one introduced in Schulz and Hahn (Reference Schulz and Hahn2004).
5.2 Using description logics for a real-world application in the domain of oncology
In this paper, a number of features of the Kasimir system are detailed. Although these features are implemented for specific and actual purpose needs, namely decision support in oncology, they are of general interest and may be reused in other domains where similar problems are raised. First, a protocol can be seen as a decision tree and can be represented as such within a description logic framework. In addition, the problem-solving process relies on the association of a medical case description (problem case) with a treatment description (solution case) through DL axioms. The DL used for implementing the Kasimir system is the representation language OWL DL, a semantically well-founded knowledge representation language. OWL DL allows interoperability with Web applications, such as the set of tools linked to a semantic portal for, for example, editing, retrieving, and visualizing knowledge units.
Meanwhile, the Kasimir system is aimed at working in a complex real-world domain, involving elements that are difficult to represent and to manipulate. A first remark concerns the non-easiness of manipulating concrete domains (datatypes) as integrated elements within DLs (see e.g. Pan & Horrocks, Reference Pan and Horrocks2005). In the Kasimir system, real numbers, intervals of numbers, and procedures for managing these datatypes, are needed. The actual implementation of the system shows that this is neither easy nor convenient to work with these datatypes, without being obliged to build ad hoc constructions for satisfying reasoning and computational services, for example, interval comparison (inclusion, equality), computation of attribute values such as the age given the date of birth, the body mass index depending on the height and the mass, etc.
5.3 Embedding case-based reasoning within a description logic framework
Another element of importance is the introduction of a CBR process within the Kasimir system. Here, CBR may be regarded as an extension of DL reasoning based on satisfiability, subsumption, and instantiation. The CBR process allows a flexible problem-solving process, not based on exact matching but on partial matching. For that purpose, similarity paths and adaptation paths have been defined for reusing already solved problems. The idea of similarity path may be imported in other contexts, where the similarity between two problems or two elements to be compared can be defined and reified in terms of a set of transformations in the problem space. The transformations have a counterpart in the solution space through an adaptation function that corresponds to each transformation function. Then, the sequence of applied adaptation functions yields to an adaptation path. The framework of similarity and adaptation paths is of general interest, and provides an efficient operational problem-solving approach, that can be embedded without major changes in the framework of a DL. Moreover, the reasoning procedures of the DL system, namely concept classification, concept satisfiability, and instance recognition, support the CBR process. In this way, classification-based reasoning and CBR are fully integrated, and provide a realistic reasoning framework for a real-world working system. For example, in the Kasimir system, they allow the full exploitation of the protocols and the guidance for the adaptation of source cases for solving medical out-of-protocol cases.
5.4 On the design of a distributed or viewpoint-based knowledge base
One of the first elements to be considered for evaluating the strength of the viewpoint representation is the easiness and convenience of expressiveness provided by a distributed representation language, such as DDLs and C-OWL. First of all, it can be noticed that, formally, the DDL formalism is not more expressive than a DL formalism, as shown in Borgida and Serafini (Reference Borgida and Serafini2002, Reference Borgida and Serafini2003): any knowledge base represented within a DDL can be transformed without loss of information into a knowledge base represented within a standard DL. A set of contexts in a context space implemented in C-OWL can be organized in a standard ontology implemented in OWL. However, the principle of non-propagation of the inconsistency, introduced in C-OWL (Bouquet et al., Reference Bouquet, Giunchiglia, van Harmelen, Serafini and Stuckenschmidt2004; Serafini & Tamilin, Reference Serafini and Tamilin2005), is not taken into account in the transformation described in Borgida and Serafini (Reference Borgida and Serafini2002). This principle has not yet been directly used in the Kasimir system.
A main interest of the representation of viewpoints in DDL can be understood in terms of knowledge engineering and knowledge management. The decentralized approach based on viewpoints or local ontologies represented by contexts, consists in building a set of local and modular ontologies. These ontologies are presenting an interest for a given group of persons and correspond to a part of the domain or to a given problem-solving task. Then, the ontologies are mapped to each other by the mean of bridge rules. A prior global consensus on domain knowledge is no more necessary. A viewpoint materializes an oriented and homogeneous representation of the knowledge considered to be useful according to a given interest. Moreover, the maintenance of a set of contexts is simpler than the maintenance of a unique ontology aggregating the whole domain knowledge. The knowledge units represented in a particular viewpoint may be locally updated, without making any reference to other representation units in other contexts (in certain cases, bridge rules have to be updated as well). Furthermore, the actors of the domain focus on the relevant and/or well-suited context, with a simplified and direct access to the adequate knowledge units. The collaboration and knowledge exchange between viewpoints are then carried out and controlled automatically, through mappings. Accordingly, in the Kasimir system, the viewpoint-based representation of the protocol allows a simpler and focused knowledge acquisition and representation, knowing that a viewpoint is composed of only a few hundreds of concepts, built and evolving independently from other viewpoint's concepts.
5.5 The implementation of the Kasimir system
The Kasimir system is embedded within a semantic portal, committed to knowledge management and decision support in oncology (d'Aquin et al., Reference d'Aquin, Brachais, Bouthier, Lieber and Napoli2005a). The architecture of the Kasimir semantic portal relies on a knowledge server, implemented as a set of Web services and embedding a DL reasoner. The Pellet OWL reasoner (Sirin et al., Reference Sirin, Parsia, Grau, Kalyanpur and Katz2007) and the jena api (McBride, Reference McBride2002) are currently used to manage the representation of the protocols in OWL and DL reasoning. Practically, several protocols are modeled and formalized (see next paragraph). For example, the representation of the breast cancer treatment protocol, according to the principles introduced in Section 2, includes about one thousand concepts and one hundred roles. The implementation was realized using the Protégé ontology editor, extended with features for visualization and maintenance specific to the Kasimir system. Furthermore, the DDL reasoner Drago, which is currently developed within Pellet at the Trento University (Serafini & Tamilin, Reference Serafini and Tamilin2005), was tested on a multi-viewpoint representation of the breast cancer treatment protocol (actually a simplification of the representation presented in Section 4.3).
Finally, as introduced in Section 3, a CBR prototype system was designed and implemented (d'Aquin et al., Reference d'Aquin, Lieber and Napoli2006c). It is based on two Web services for case retrieval and adaptation, and relies on an OWL representation of the knowledge units used by the CBR process; for example, cases and reformulations.
5.6 An evaluation of the Kasimir system
The use of the Kasimir system by physicians has been evaluated for the object-based representation version of the system (mentioned in the introduction and implemented within an object-based representation or OBR formalism). The OBR formalism includes the concept constructors ⊤, C⊓D, ∃r.C, and ∃g.ϕ (see Section 2.2, in this way, it can be compared with the DL
$$\[--><$>{\cal E}{\cal L}(D) <$><!--$$
). The OBR formalism was sufficient for representing the protocols and for standard reasoning (as explained in § 2.4). However, the use of the OBR formalism requires the introduction of much more atomic concepts than this is necessary for the OWL DL version. From this point of view, the use of the OWL DL formalism can be considered as a substantial improvement. Nevertheless, the results of the evaluation of the OBR version Kasimir of can be understood in the same way in the context of the OWL DL version of the Kasimir system (http://katexowl.loria.fr).
An evaluation of the OBR version of Kasimir is presented in Rios et al. (Reference Rios, Desandes, Bresson, Klein, Lesur, Boisson, Demange and Bey2003) and was carried out by physicians on breast and prostate cancer protocols. The protocols were presented under three formats: (i) the original documents describing the protocols called the ‘paper protocols’, (ii) an HTML version of these documents as available on the www.oncolor.org website called the ‘HTML protocols’, (iii) the protocols as implemented in the OBR version of the Kasimir system called the ‘Kasimir protocols’. The use of these three formats of the protocol was measured by the so-called compliance. For a given physician and a given format, the compliance on a test set of medical cases is the proportion of answers of the physician that are in agreement with the protocol. According to the principles of evidence-based medicine (Evidence-based medicine working-group, 1992), the compliance has to be maximized whenever the medical cases are not out-of-protocol (and this was the case for the test sets).
The results of this evaluation show that the mean compliance with the Kasimir format was better for breast and prostate cancer protocols than the two other formats (paper and HTML), though this ‘superiority’ was statistically significant only for the breast cancer protocol, certainly because not enough data were collected for the prostate cancer protocol. More precisely, the compliance values for the breast cancer protocol were 77.8%, 75.8%, and 87.1%, respectively, for the paper, HTML, and Kasimir formats. This shows that the development of the Kasimir system has to be continued.
The evaluation of the DL version of the Kasimir system has to be considered at a qualitative level. Actually, this DL version is viewed as a ‘proof of concept’ of the following statements:
• Medical decision protocols can be represented with DLs such as
$$\[--><$>{\cal S}{\cal H}{\cal O}{\cal I}{\cal N}\!\left( {\cal D} \right) <$><!--$$
and DDLs, with a concrete domain for numerical intervals.• A decision problem, say pb, consists of the description of a medical case, for example, the state of a patient, while the associated solution Sol(pb) consists of a medical decision, for example, a treatment. The inference relating pb to Sol(pb) relies on instance classification.
• Inferences are efficiently carried out with an inference engine such as Pellet.
Several decision protocols were implemented and their use, for example, by querying, is made possible through Pellet. These computerized medical decision protocols are related to the treatment of
• prostate cancer,
• melanoma cancer,
• rectum cancer,
• larynx cancer,
• non-metastatic breast cancer.
In addition, other existing protocols are related to
• Breast cancer surveillance: where the problem consists of the description of a patient who has been cured of her/his breast cancer, and the solution consists of the forthcoming exams to prevent the patient from having a relapse.
• Neutropenia with fever: where the problem consists of the description of a patient having fever and who is currently under chemotherapy treatment—which involves less defense of the organism—and the solution consists of actions to be carried out for taking in charge the patient.
• Eligibility of patients for some clinical trials where the problem consists of a description of a patient ill with cancer, and a solution consists of clinical trials she/he is eligible for.
All these ‘computerized protocols’ belong to the Oncolor network (www.oncolor.org) and are not directly available (though they can be consulted on proper site). Moreover, their validity is restricted in time as they compile the state of the art about a medical decision protocol at a given time and they have to be updated when new results about this decision problem are published.
6 Conclusion and future work
The Kasimir system is aimed at knowledge management and decision support in oncology. In this paper, topics such as representation, reasoning, and viewpoints, have been detailed. The Kasimir system implements medical decision protocols, in particular for breast cancer treatment, using a DL formalism, namely the OWL DL language. In addition, a way of associating the characteristics of patients with recommended treatments is shown. The direct application of standard patient–treatment associations in the protocol is not always satisfactory, leading to the need of adapting the protocol. A CBR process embedded within a DL framework is used for solving the adaptation problem.
Moreover, a viewpoint-based representation of the protocols has been set up, using a DDL, for taking into account the complexity and diversity of oncology. The representation is based on four main viewpoints: surgery, chemotherapy, radiotherapy, and complementary treatment. A decentralized reasoning mechanism, relying on classification and decentralized CBR, takes advantage of viewpoints and of bridge rules between viewpoints for solving adaptation problems.
The CBR mechanism presented in Section 3 is considered as a knowledge intensive process, relying on a DL-based representation of domain knowledge and on adaptation knowledge. Accordingly, the reformulation model is implemented within a DL framework for representing and making operational adaptation knowledge. In addition, efforts are currently carried out for designing methods, techniques, and tools for the acquisition of adaptation knowledge in the Kasimir system. In particular, a part of this research work is related to the reuse of the results of adaptation knowledge acquisition sessions gathering oncology experts, researchers in computer science and in psycho-ergonomy (Lieber et al., Reference Lieber, d'Aquin, Bey, Napoli, Rios and Sauvagnac2003). Another part involves knowledge discovery in databases techniques: the so-called CabamakA system is a tool for semi-automatic adaptation knowledge acquisition. The CabamakA system relies on a data mining technique for extracting adaptation knowledge from a case base, namely the search for frequent closed itemsets (d'Aquin et al., Reference d'Aquin, Badra, Lafrogne, Lieber, Napoli and Szathmary2007).
Finally, in the same way, the integration of semi-automatic adaptation knowledge extraction, and acquisition methods driven by experts is another topic of interest. Besides knowledge discovery, another ongoing work in the Kasimir system concerns the definition and the implementation of fuzzy predicates over numerical concrete domains, with an associate inference engine (for extending work introduced in d'Aquin et al., Reference d'Aquin, Lieber and Napoli2006a).