Extending computer guideline system with advanced AI and DB facilities

Slides:



Advertisements
Similar presentations
Jeremy S. Bradbury, James R. Cordy, Juergen Dingel, Michel Wermelinger
Advertisements

Clinical Decision Support TC Order Set Proposal September 14, 2005.
Clinical Guidelines Adaptation: Managing Authoring and Versioning Issues Paolo Terenziani 1, Stefania Montani 1, Alessio Bottrighi 1, Gianpaolo Molino.
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,
Identifying, Modifying, Creating, and Removing Monitor Rules for SOC Ricardo Contreras Andrea Zisman
BCDM Temporal Domains - Time is linear and totally ordered - Chronons are the basic time unit - Time domains are isomorphic to subsets of the domain of.
Mapping Studies – Why and How Andy Burn. Resources The idea of employing evidence-based practices in software engineering was proposed in (Kitchenham.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
CMPT 354, Simon Fraser University, Fall 2008, Martin Ester 52 Database Systems I Relational Algebra.
HYGIA Design and Application of new Artificial Intelligence techniques to the acquisition and use of medical knowledge represented as care pathways.
Chapter 2 Access Control Fundamentals. Chapter Overview Protection Systems Mandatory Protection Systems Reference Monitors Definition of a Secure Operating.
Metareasoning: Thinking about thinking Chicago July 2008 Stefania Costantini Pierangelo Dell’Acqua Luis M. Pereira A Multi-layer Framework for Evolving.
Chapter 9 Database Design
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
Lecture Nine Database Planning, Design, and Administration
Theresa Tsosie-Robledo MS RN-BC February 15, 2012
Team Dosen UMN Physical DB Design Connolly Book Chapter 18.
Medical Informatics Basics
Query Processing Presented by Aung S. Win.
● Problem statement ● Proposed solution ● Proposed product ● Product Features ● Web Service ● Delegation ● Revocation ● Report Generation ● XACML 3.0.
Overview of the Database Development Process
Context Tailoring the DBMS –To support particular applications Beyond alphanumerical data Beyond retrieve + process –To support particular hardware New.
ITEC224 Database Programming
Software School of Hunan University Database Systems Design Part III Section 5 Design Methodology.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Medical Informatics Basics Lection 1 Associated professor Andriy Semenets Department of Medical Informatics.
1 On Provenance of Non-Answers for Queries over Extracted Data Jiansheng Huang Ting Chen AnHai Doan Jeffrey F. Naughton.
Lecture 7 Integrity & Veracity UFCE8K-15-M: Data Management.
DANIEL J. ABADI, ADAM MARCUS, SAMUEL R. MADDEN, AND KATE HOLLENBACH THE VLDB JOURNAL. SW-Store: a vertically partitioned DBMS for Semantic Web data.
Recent research : Temporal databases N. L. Sarda
TM 1 Dr. Chen, Business Database Systems Data Modeling Professor Chen School of Business Administration Gonzaga University Spokane, WA
E.Bertino, L.Matino Object-Oriented Database Systems 1 Chapter.1 Introduction Seoul National University Department. of Computer Engineering OOPSLA Lab.
HYGIA: Design and Application of New Techniques of Artificial Intelligence for the Acquisition and Use of Represented Medical Knowledge as Care Pathways.
Verification and Validation in the Context of Domain-Specific Modelling Janne Merilinna.
©2001 Sowerby Centre for Health Informatics at Newcastle Progress on Virtual Medical Record HL7 Salt Lake City.
Lecture 7: Requirements Engineering
Clinical Guidelines Contextualization in GLARE Alessio Bottrighi*, Paolo Terenziani*, Stefania Montani*, Mauro Torchio #, Gianpaolo Molino # *DI, Univ.
Temporal Mediators: Integration of Temporal Reasoning and Temporal-Data Maintenance Yuval Shahar MD, PhD Temporal Reasoning and Planning in Medicine.
Part4 Methodology of Database Design Chapter 07- Overview of Conceptual Database Design Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Chapter 2 Database System Concepts and Architecture Dr. Bernard Chen Ph.D. University of Central Arkansas.
Methodology – Physical Database Design for Relational Databases.
Clinical Decision Support 1 Historical Perspectives.
ECOMPOSE: development of Executable COntent in Medicine using Proprietary and Open Standards Engineering Dipartimento di Informatica, Universita’ del Piemonte.
Informatics in healthcare professions Lec130/08/2015.
Ontology-Based Interoperability Service for HL7 Interfaces Implementation Carolina González, Bernd Blobel and Diego López eHealth Competence Center, Regensurg.
Artificial Intelligence: Research and Collaborative Possibilities a presentation by: Dr. Ernest L. McDuffie, Assistant Professor Department of Computer.
Temporal Data Modeling
1 The T4SQL Temporal Query Language Presented by 黃泰豐 2007/12/26.
Rule Engine for executing and deploying the SAGE-based Guidelines Jeong Ah Kim', Sun Tae Kim 2 ' Computer Education Department, Kwandong University, KOREA.
Chapter (12) – Old Version
USING NATIONAL GUIDELINES FOR SCREENING, TREATMENT, AND FOLLOW-UP
Paolo Terenziani, Alessio Bottrighi, Stefania Montani
Component 11: Configuring EHRs
Methodology – Physical Database Design for Relational Databases
Enterprise Content Management Owners Representative Contract Approval
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment.
Data, Databases, and DBMSs
國立臺北科技大學 課程:資料庫系統 fall Chapter 18
Database management concepts
Updating GML datasets S-100 WG TSM September 2017
Metadata The metadata contains
Database System Concepts and Architecture
Dept. of Computation, UMIST
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment Pearson Education © 2009.
CS240A: Databases and Knowledge Bases A Taxonomy of Temporal DBs
Practical Database Design and Tuning Objectives
INTRODUCTION A Database system is basically a computer based record keeping system. The collection of data, usually referred to as the database, contains.
Presentation transcript:

Extending computer guideline system with advanced AI and DB facilities Alessio Bottrighi

Alessio Bottrighi 's Ph.d. Dissertation A clinical guidelines is sistematically developments statemnts to assist pratictioners and patient decision about appropriate health care for specific clinical circumstance Alessio Bottrighi 's Ph.d. Dissertation

Alessio Bottrighi 's Ph.d. Dissertation Our work Decision theory support Model checking in clinical guidelines Cooperative update Alessio Bottrighi 's Ph.d. Dissertation

Decision System Support decision making is a central issue in clinical practice. it is frequent that it is not possible define if an alternative is really “better” than other, for a clinical point of view Alessio Bottrighi 's Ph.d. Dissertation

Decision System Support: our work We made a systematic analysis of main clinical guidelines representation primitives We made the mapping of representation primitives into Markov Decision Process. We studied how algorithms for evaluating utility and for evaluating the optimal policy can be exploited in clinical guidelines context As case of study, we have applied our general approach to the GLARE system Alessio Bottrighi 's Ph.d. Dissertation

Decision System Support: publication S. Montani, P. Terenziani, A. Bottrighi, Exploiting decision theory for supporting therapy selection in computerized clinical guidelines, Proc. European Conference on Artificial Intelligence in Medicine (AIME) 2005, July 2005 P. Terenziani, S. Montani, A. Bottrighi, M. Torchio, G. Molino, G. Correndo, Managing clinical guidelines contextualization in the GLARE system, Proc. Congresso Nazionale dell'Associazione Italiana per l'Intelligenza Artificiale (AI*IA) 2005, September 2005 Alessio Bottrighi 's Ph.d. Dissertation

Model checking in clinical guidelines improving the quality of clinical guideline the capabilities verification available in the guideline systems is usually rather limited defining a general mechanism to evaluate the quality of clinical guideline Alessio Bottrighi 's Ph.d. Dissertation

Model checking in clinical guidelines: our work We had mapped the behaviour of a clinical guideline into a formalism accepted by the model checker (the SPIN model checker) We have defined a comprehensive framework in which a computer-based approach to clinical guidelines is developed using an agent-based technology We have identified the types of properties that are useful to verify about a clinical guideline As case of study, we have applied our general approach to the GLARE system Alessio Bottrighi 's Ph.d. Dissertation

Model checking in clinical guidelines: publication P. Terenziani, L. Giordano, A. Bottrighi, S. Montani, L.Donzella, Spin Model Ckecking for the verification of Clinical Guidelines, Workshop on AI techniques in healthcare: evidence-based guidelines and protocols, ECAI 2006, August 2006 L. Giordano, P. Terenziani, A. Bottrighi, S. Montani, L. Donzella, Model checking for clinical guidelines: an agent-based approach, American Medical Informatics Association (AMIA), November 2006 Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: introduction (1) Important, e.g. software development Multiple alternative proposals Selection Software engineering tools Analogous problems using Database to model complex domains Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: introduction (2) The case of clinical guidelines: General guideline proposed by a standardization committee Proposals of update Local contextualization New therapies Evaluation of proposals Guideline to be stored in a DB Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: introduction (3) Augmenting DB approaches to support cooperative work, i.e.: distinction between two phases: proposals and acceptance/rejection history of the evolution of the proposals alternative proposals Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: introduction (4) Both validity time and transaction time should be supported “Consensus” approach (TSQL2) with a high-level semantics (BCDM) BCDM supports several Temporal Database implementations (not only TSQL2) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: goal Extending BCDM to support cooperative updates Propose vs accept/reject Alternative proposals of updates Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: criteria (1) Under-constrained policy: Super user vs user Super user operations: standard + accept/reject proposals User operations: delete (not proposals) insert update (chains allowed) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: criteria (2) “Minimal” extension of BCDM: Upward compatibility (manipulation operations) Reducibility (algebra) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: our work Data model Manipulation operations Algebra Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (1) Two data levels needed: Super users (accepted) data User proposals Observe that proposals need to be maintained and affect super-user data only if/when accepted Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (2) Authoring: author as a data attribute Basically a “standard” data attribute (however, author cannot be modified) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (3) Super user data: Standard BCDM semantics User proposals data: For each super-user relation r: insert(r) delete(r) update(r) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (4) insert(r) is a set of standard BCDM tuples delete(r) is a set of standard transaction-time tuples Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (5) Update involves: An origin tuple to be updated (time not needed) A new temporal tuple (standard BCDM tuple) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (6) Semantic interpretation: disjunctive set of alternative proposals (each one is a BCDM tuple) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (7) Definition: proposal tuple pt = <o, Alt{alt1,alt2,..,altk}> an origin o a non empty set Alt{alt1,alt2,..,altk} of (bi)temporal tuples Observe that Alt{alt1,alt2,..,altk} is a disjunctive set of mutually exclusive tuples referring to the origin o, representing the different proposals of update concerning o. Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: data model (8) proposal(r) is a set of Proposal-tuples Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (1) User: propose_update propose_insert propose_delete Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (2) Super-user: accept_update, accept_insert, accept_delete reject_update, reject_insert, reject_delete confirm Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (3) E.g.: propose_update(r,origin,old,new,VT) Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (4) E.g.: propose_update(r,origin,old,new,VT) IF admissible IF  ptproposal(r) with origin(pt)=origin THEN add <origin, <new,user,UCVT>> in proposal(r) insert a new propoasal tuple IF  ptproposal (r) with origin(pt)=origin  ( a1  alternatives(pt)\ a1 value equivalent to ‘new’ OR  a1  alternatives(pt)\ a1 value equivalent to ‘new’  user(a) user) THEN add ‘new’ to alternatives(pt) insert a new proposal into an existing proposal-tuple user(a) = user THEN add (UCVT) to the bitemporal of a1 update previous proposal Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (5) Admissibility of propose_uptade operation origin: in r or in insert(r)  current old: old (old=origin OR old origin)  current new: ( tuple t r  current  t value equivalent to ‘new’  t value equivalent to origin)   proposal value equivalent to t with same VT Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: manipulation operation (6) Condition on ‘new’: example r: {<a,u,Ta>,<b,u,Tb>,…..} (r is a super-user relation) Admissible update: a,u  <a,u’,T’> NOT admissible: b,u  <a,u,T’>

Cooperative Update: manipulation operation (7) E.g.: accept update proposal IF admissible IF  tr \ t value equivalent to origin  current(t) THEN DELETE(t); INSERT(new); close UC to all alternative proposals concerning origin IF  tr \ t value equivalent to origin  current(t)   tinsert(r) \ t value equivalent to origin  current(t) THEN INSERT(new); close UC to all alternative proposals concerning origin admissible:  ptproposal(r) with origin(pt)=origin  newalternatives(pt)  current(new)  [( tr \ t value equivalent to new  current(t))  t value equivalent to origin] Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: algebra(1) Standard BCDM algebraic operations for super-user and for insert(r), delete(r) New algebraic operations on Proposal-relations Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: algebra(2) E.g.: natural join: r⋈A s = { z=<origin(z),alternatives(z)> \ IF $pt1Îr , $pt2Îs \ origin(pt1)[A]= origin(pt2) [A] $a1Îalternatives(pt1), $a2Îalternatives(pt2) \ a1[A]=a2[A] Ù a1[T]a2[T]  THEN origin(z)[A]=origin(pt1)[A] Ù z[B]=origin(pt1)[B] Ù z[C]=origin(pt2)[C] Ù altÎalternatives(z), where alt[A]=a1[A]=a2[A] Ù alt[B]=a1[B] Ù alt[C]=a2[C] Ù alt[T]=a1[T]a2[T] } Alessio Bottrighi 's Ph.d. Dissertation

Cooperative Update: algebra(3) Definition: convert convert(proposal(r))={(a1,..,a1,u, a’1,…,a’n,u',T)\ ptproposal(r) \(a1,…,an,u)=origin(pt) (a’1,…,a’n,u’)=alternatives(pt) } Alessio Bottrighi 's Ph.d. Dissertation

Alessio Bottrighi 's Ph.d. Dissertation End Thanks!! Alessio Bottrighi 's Ph.d. Dissertation