GLARE: a Domain-Independent System for Acquiring, Representing and Executing Clinical Guidelines Paolo Terenziani, Stefania Montani, Alessio Bottrighi,

Slides:



Advertisements
Similar presentations
Clinical Guidelines Adaptation: Managing Authoring and Versioning Issues Paolo Terenziani 1, Stefania Montani 1, Alessio Bottrighi 1, Gianpaolo Molino.
Advertisements

Flexible and efficient retrieval of haemodialysis time series S. Montani, G. Leonardi, A. Bottrighi, L. Portinale, P. Terenziani DISIT, Sezione di Informatica,
Extending Temporal Databases to Deal with Telic/Atelic Medical Data Paolo Terenziani 1, Richard T. Snodgrass 2, Alessio Bottrighi 1, Mauro Torchio 3, Gianpaolo.
Exploiting decision theory for supporting therapy selection in computerized clinical guidelines Stefania Montani, Paolo Terenziani, Alessio Bottrighi DI,
Towards a Flexible Integration of Clinical Guideline Systems With Medical Ontologies and Medical Information Systems Gianluca Correndo 1, Paolo Terenziani.
Formal Semantics for an Abstract Agent Programming Language K.V. Hindriks, Ch. Mayer et al. Lecture Notes In Computer Science, Vol. 1365, 1997
A Case-based Approach to Business Process Monitoring S. Montani 1, G. Leonardi 1 1 Dipartimento di Informatica, University of Piemonte Orientale, Alessandria,
SOFTWARE TESTING. INTRODUCTION  Software Testing is the process of executing a program or system with the intent of finding errors.  It involves any.
GLARE (GuideLine Acquisition Representation and Execution) Paolo Terenziani Dipartimento di Informatica, Universita’ del Piemonte Orientale “Amedeo Avogadro”,
The design process IACT 403 IACT 931 CSCI 324 Human Computer Interface Lecturer:Gene Awyzio Room:3.117 Phone:
Architecture Tutorial 1 Overview of Today’s Talks Provenance Data Structures Recording and Querying Provenance –Break (30 minutes) Distribution and Scalability.
Clinical decision support system (CDSS). Knowledge-based systems Knowledge based systems are artificial intelligent tools working in a narrow domain to.
Intelligent systems Lecture 6 Rules, Semantic nets.
Identity Management Based on P3P Authors: Oliver Berthold and Marit Kohntopp P3P = Platform for Privacy Preferences Project.
Xyleme A Dynamic Warehouse for XML Data of the Web.
A Robust System Architecture For Mining Semi-structured Data By Aby M Mathew CSE
Visual Web Information Extraction With Lixto Robert Baumgartner Sergio Flesca Georg Gottlob.
Database management concepts Database Management Systems (DBMS) An example of a database (relational) Database schema (e.g. relational) Data independence.
How can Computer Science contribute to Research Publishing?
Guideline interaction scenarios  At the point of care Physicians apply marked-up guidelines, thus they Need to find an appropriate guideline in “ real.
Query Operations: Automatic Global Analysis. Motivation Methods of local analysis extract information from local set of documents retrieved to expand.
October 17-19, 2001ESA Workshop “On-Board Autonomy” Efficiency Issues in Model-Based Approaches to On-Board Diagnosis P.Torasso, C.Picardi and L. Console.
Chapter 1 Introduction to Databases
THE MODEL OF ASIS FOR PROCESS CONTROL APPLICATIONS P.Andreeva, T.Atanasova, J.Zaprianov Institute of Control and System Researches Topic Area: 12. Intelligent.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Overview of the Database Development Process
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Katanosh Morovat.   This concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control of the operation.
Deciding when to intervene: A Markov Decision Process approach Xiangjin Zou(Rho) Department of Computer Science Rice University [Paolo Magni, Silvana Quaglini,
An Approach to Task Modelling for User Interface Design Costin Pribeanu National Institute for Research and Development in Informatics, Bucureşti, Romania.
ITEC224 Database Programming
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Reviewing Recent ICSE Proceedings For:.  Defining and Continuous Checking of Structural Program Dependencies  Automatic Inference of Structural Changes.
RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah
Introduction to search Chapter 3. Why study search? §Search is a basis for all AI l search proposed as the basis of intelligence l all learning algorithms,
Conceptual Modelling – Behaviour
Keyword Searching and Browsing in Databases using BANKS Seoyoung Ahn Mar 3, 2005 The University of Texas at Arlington.
Clinical Guidelines Contextualization in GLARE Alessio Bottrighi*, Paolo Terenziani*, Stefania Montani*, Mauro Torchio #, Gianpaolo Molino # *DI, Univ.
Natallia Kokash (Accepted for PACO’2011) ACG, 31/05/ Input-output conformance testing for channel-based connectors 1.
Temporal Mediators: Integration of Temporal Reasoning and Temporal-Data Maintenance Yuval Shahar MD, PhD Temporal Reasoning and Planning in Medicine.
Object Oriented Multi-Database Systems An Overview of Chapters 4 and 5.
User Interfaces 4 BTECH: IT WIKI PAGE:
1 Chapter 1 Introduction to Databases Transparencies.
1 Welcome : To the third learning sequence “ DB ACTORS “ Present learning: We shall explore the following topics: - DB limitations. - DB actors. - DB Administrator.
Applying AI temporal reasoning techniques to Clinical Guidelines Luca Anselma%, Paolo Terenziani*, Stefania Montani*, Alessio Bottrighi* %DI, Università.
Fundamentals of Information Systems, Third Edition1 The Knowledge Base Stores all relevant information, data, rules, cases, and relationships used by the.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
ECOMPOSE: development of Executable COntent in Medicine using Proprietary and Open Standards Engineering Dipartimento di Informatica, Universita’ del Piemonte.
Clinical Decision Support Systems Dimitar Hristovski, Ph.D. Institute of Biomedical.
SOFTWARE TESTING. Introduction Software Testing is the process of executing a program or system with the intent of finding errors. It involves any activity.
Approach to building ontologies A high-level view Chris Wroe.
Modelling clinical goals A corpus of examples and a tentative ontology John Fox 1, Alyssa Alabassi 1,2, Elizabeth Black 1, Chris Hurt 1, Tony Rose 1 1.
The Object-Oriented Database System Manifesto Malcolm Atkinson, François Bancilhon, David deWitt, Klaus Dittrich, David Maier, Stanley Zdonik DOOD'89,
1 Chapter 2 Database Environment Pearson Education © 2009.
VIRTUAL CLINICAL DEPARTMENT by APPLIED LOGIC LABORATORY & INSTITUTE for HEALTH PROTECTION Ministry of Defence.
Rule Engine for executing and deploying the SAGE-based Guidelines Jeong Ah Kim', Sun Tae Kim 2 ' Computer Education Department, Kwandong University, KOREA.
Optimization of Association Rules Extraction Through Exploitation of Context Dependent Constraints Arianna Gallo, Roberto Esposito, Rosa Meo, Marco Botta.
Paolo Terenziani, Alessio Bottrighi, Stefania Montani
Architecture Components
Chapter 2: Database System Concepts and Architecture
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment.
Database management concepts
Database management concepts
Database System Concepts and Architecture
Extending computer guideline system with advanced AI and DB facilities
Chapter 12 Analyzing Semistructured Decision Support Systems
Chapter 2 Database Environment Pearson Education © 2009.
Presentation transcript:

GLARE: a Domain-Independent System for Acquiring, Representing and Executing Clinical Guidelines Paolo Terenziani, Stefania Montani, Alessio Bottrighi, DI, Universita’ del Piemonte Orientale “Amedeo Avogadro”, Alessandria, Italy Gianpaolo Molino, Mauro Torchio Laboratorio di Informatica Clinica, Azienda Ospedaliera S. Giovanni Battista, Torino, Italy - The GLARE system - Advances: support to decision making - Advances: management of temporal constraints (see AMIA06 poster T020) - Advances: contextualization facilities (see AMIA06 poster M010) - Advances: model-checking facilities (see AMIA06 presentation in session S52)

Introduction Many different computer systems managing clinical guidelines (e.g., Asgaard, GEM, Gliff, Guide, PROforma,…) Different roles: -support -critique -evaluation -education -…... Clinical guidelines are a means for specifying the “best” clinical procedures and for standardizing them Adopting (computer-based) clinical guidelines is advantageous

GLARE (GuideLine Acquisition Representation and Execution) -Joint project: Dept. Comp. Sci., Univ. Alessandria (It): P. Terenziani, S.Montani, A.Bottrighi Dept. Comp. Sci., Univ. Torino (It): L.Anselma,G.Correndo Az. Osp. S. Giovanni Battista, Torino (It): G.Molino, M.Torchio -Domain independent (e.g., bladder cancer, reflux esophagitis, heart failure) -Phisician-oriented & User-friendly Some recent pubblications: Terenziani et al., AIIMJ 01,07a,07b, AMIA 00,02,03, Medinfo 04, CGP’04a,04b, AI*IA 03,05, GIN 04,05, AIME 05a,05b,05c AMIA’06 posters T020 and M010 AMIA’06 paper in session S52

Representation Formalism Tree of graphs Atomic actions Composite actions (plans) Control relations between actions: -sequence -“controlled” -alternative -repetition (e.g. “3 times each 2 days for a month”) A B C B1B1 B2B2 B 1.1 B 1.2 B 2.1 B 2.2 B 2.3 CG B B1B1 B2B2 D

Representation Formalism Hierarchy of Action Types Action Plan Query Work action ConclusionDecision Clinical action Pharmacol. prescription Diagnostic decision Therapeutic decision

Representation Formalism description of a work action

Therapeutic decisions Fixed set of parameters (effectiveness, cost, side-effects, compliance, duration) Treatment choice for symptomless gallbladder stones Treatment choice Surgical treatment Expectant management Litholitic therapy

Local information associated with treatment choice (in the symptomless gallbladder stones guideline)

Diagnostic Decisions *Decision parameters *Decision criteria score-based mechanism For each alternative For each parameter  score  (additive) threshold range

Diagnostic Decisions (Gastro Esophageal Reflux Disease) PARAMETERS: heartburn absent (“no-hb”), heartburn lasted not more than 3 months (“hb= 3m”); dysphagia absent (“no-dys”); dysphagia present (“dys”); occurrence of weight loss (“wl”) or non-occurrence (“no-wl”); hemathemesis absence (“no- hem”); hemathemesis presence (“hem”); postural reflux absent (“no-ref”), postural reflux lasted not more than 3 months (“ref= 3m”). THRESHOLD: >9. (One should conclude “no GERD” only if heartburn, dysphagia, weight loss, hematemesis and postural reflux are all absent.)

Architecture of the system Clinical DB Pharmac. DB Resource DB ICD DB Expert Physician Acquisition Interface Guidelines DB Knowledge Manager User Physician Execution Interface Guidelines Instantiation DB Patient DB Execution Module

Acquisition Strict interaction with DB’s Clinical DB  hierarchically organized vocabulary  Standardization  Data sharing  Support for semantic checks (e.g., legal attribute values) NOTE: the organization (schema) of Patients DB is equal to the one of the Clinical DB  During acquisition, GLARE gets the information used at execution-time to retrieve automatically the patient’s data (via automatically generated dynamic-SQL queries)

Acquisition “Intelligent” helps (syntactic & semantic checks) - “legal” names & “legal” values for attributes - “logical” design criteria (no unstructured cycles, well-formed alternatives & decisions) - “semantic” checks: consistency of temporal constraints

Acquisition Graphical Interface

Agenda-based execution In the agenda -next actions to be executed -execution time (earliest and latest e.t.)  “On-line” execution: wait until the next e.t. (support physician in clinical activity)  “Simulated” execution: jump to the next e.t. (education, critique, evaluation)

Executing atomic actions Work actions: -evaluate pre-conditions -execute action within its range of time -delete from the agenda Query actions: -retrieve data from patient’s DB -wait for data not already in the DB, or for the update of “expired” data Conclusion actions: -insert conclusion into the patient’s DB Decision actions: (see alternatives)

Executing composite actions Sequence: -evaluate next action e.t. (given current time and delay) -execute it Concurrent actions: -execute actions according with the temporal constraints Decision + alternative actions (e.g., diagnostic decision): -evaluate parameter values for each alternative, using patient’s DB -determine the score for each alternative -compare the score with the threshold -show the alternatives to the user-physician (distinguishing between “suggested” and “not suggested” ones, and showing parameters and scores) -execute the alternative chosen by the physician (warning available)

Executing Clinical Guidelines: other issues  Exits  Failures return to previous decisions (chronological vs. guided backtracking)  Repeated actions and user-defined periodicities -expressive language for user-defined periodicities [IEEE TKDE, 97] -computing next execution time  A user-friendly graphical interface

Implementation & Testing Prototypical version (Java + Access) under revision TESTS (1) Using GLARE to build guidelines from scratch take advantage of grafical and “intelligent checks” facilities -bladder cancer algorithm (2) Converting guidelines on paper to GLARE inconsistencies/ambiguities detected! -reflux esophagitis, heart failure, ischemic stroke

Advanced features in GLARE: Supporting medical decision making “local information”: considering just the decision criteria associated with the specific decision at hand “global information”: information stemming from relevant alternative pathways in the guideline

Advanced features in GLARE: Supporting medical decision making: the “What if” facility Facility for gathering the chosen parameter (e.g, resources, costs, times) from the “relevant” alternative paths on the guideline It provides an idea of what could happen in the rest of the guideline if the physician selects a given alternative for the patient, and supports for comparisons of the alternatives Enhanced with an application of “Decision Theory” methodology, to provide an advanced tool to consider costs (money, time, resources) and utility of alternative sequences of actions (QALYs)

Syntomless gallbladder stones treatment choice: “global information” Treatment choice Surgical treatment Expectant management Litholitic therapy Litholitic treatment Choice of surgical appr. Laparoscopy Laparotomy Laparoscopy Laparotomy

Syntomless gallbladder stones treatment choice: “global information” Treatment choice Surgical treatment Expectant management Litholitic therapy Litholitic treatment Choice of surgical appr. Laparoscopy Laparotomy Laparoscopy Laparotomy Durationmin:2 daysMax:3 days

Syntomless gallbladder stones treatment choice: “global information” Treatment choice Surgical treatment Expectant management Litholitic therapy Litholitic treatment Choice of surgical appr. Laparoscopy Laparotomy Laparoscopy Laparotomy Durationmin:6 daysMax:8 days

Syntomless gallbladder stones treatment choice: “global information” Treatment choice Surgical treatment Expectant management Litholitic therapy Litholitic treatment Choice of surgical appr. Laparoscopy Laparotomy Laparoscopy Laparotomy Durationmin:1 dayMax: all life long

Syntomless gallbladder stones treatment choice: “global information” Treatment choice Surgical treatment Expectant management Litholitic therapy Litholitic treatment Choice of surgical appr. Laparoscopy Laparotomy Laparoscopy Laparotomy Durationmin:2 monthsMax:1 year

Local information associated with treatment choice (in the symptomless gallbladder stones guideline)

Digression 2 Why don’t we put “global info (about paths)” locally in the decision actions? Given “local info” in each node, collecting & storing might be automatic HOWEVER: -exponential space in each node -data duplication (consistency after updates?) -not user friendly (too many data!) -not all aternatives are “relevant” -data not always necessary >>global data only at execution time, on request

Advanced features in GLARE Management of temporal constraints >>>>> AMIA06 poster T020 Session S50 Terenziani et al., Proc. AMIA’03 Terenziani et al., Artificial Intelligence in Medicine Journal, to appear Contextualization facilities >>>>>> AMIA06 poster M010 Session S13 Terenziani et al., Proc. Medinfo’04, AIME’05 Model-checking facilities >>>>> AMIA06 paper, session S52 Terenziani et al., ECAI’06 Guidelines worshop