1 / 13

Possible partecipants (AIM group): - Paolo Terenziani (Full Professor)

ECOMPOSE: development of Executable COntent in Medicine using Proprietary and Open Standards Engineering Dipartimento di Informatica , Universita’ del Piemonte Orientale “Amedeo Avogadro” , Alessandria, Italy. Possible partecipants (AIM group): - Paolo Terenziani (Full Professor)

neville-morton
Download Presentation

Possible partecipants (AIM group): - Paolo Terenziani (Full Professor)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECOMPOSE: development of Executable COntent in Medicine using Proprietary and Open Standards EngineeringDipartimento di Informatica,Universita’ del Piemonte Orientale “Amedeo Avogadro”, Alessandria, Italy • Possible partecipants (AIM group): - Paolo Terenziani (Full Professor) - Laura Giordano (Professor) - Stefania Montani (Researcher) - Luca Anselma (Univ. Torino, Researcher) - Alessio Bottrighi (Dr., PhD) - …. ??

  2. Previous & current work of the group Starting from 1997, GLARE project, with Az. Ospedaliera S. Giovanni Battista in Turin GLARE (Guideline Acquisition, Representation, Execution) • domain-independent (e.g. bladder cancer, ischemic stroke) • “physician-oriented” formalism • Advanced AI techiques (only prototypes)

  3. Previous & current work of the group • TEMPORAL CONSTRAINTS (IN CLINICAL GUIDELINES) • Representation formalisms • Constraint propagation algorithms (e.g., to check consistency) • Computational complexity vs expressiveness trade-off • Methodology: a domain-independent module coping with time, to be loosely coupled with different systems GL System_n GL System_1 Temporal Module

  4. Previous & current work of the group (2) VERIFICATION OF CLINICAL GUIDELINES THROUGH MODEL-CHECKING • Goal: a general-purpose approach to verify (any!?) property about any guideline in GLARE • Which properties? (consistency, reachability of actions,…) • Methodology: pairing GLARE with a model-checker (SPIN) GL1 GL1 GLARE SPIN …. Translator …. GLn GLn …. P1 Pk

  5. Previous & current work of the group (3) RESOURCE-BASED CONTEXTUALIZATION OF CLINICAL GUIDELINES • Each GL action must specify required resources (instruments) • Each specific hospital has a set of available resources • Pruning away (paths of) actions which are not locally executable (due to lack of resources)

  6. Previous & current work of the group (3) RESOURCE-BASED CONTEXTUALIZATION OF CLINICAL GUIDELINES • Each GL action must specify required resources (instruments) • Each specific hospital has a set of available resources • Pruning away (paths of) actions which are not locally executable (due to lack of resources)

  7. Previous & current work of the group (3) RESOURCE-BASED CONTEXTUALIZATION OF CLINICAL GUIDELINES • Each GL action must specify required resources (instruments) • Each specific hospital has a set of available resources • Pruning away (paths of) actions which are not locally executable (due to lack of resources)

  8. Previous & current work of the group (3) RESOURCE-BASED CONTEXTUALIZATION OF CLINICAL GUIDELINES • Each GL action must specify required resources (instruments) • Each specific hospital has a set of available resources • Pruning away (paths of) actions which are not locally executable (due to lack of resources)

  9. Previous & current work of the group(not directly related to Medical Informatics) • Temporal extensions to (the semantics of) Relational Databases • (Semantics of) cooperative updates to Relational Temporal Databases • Ontology: modeling time and causation

  10. LINKS to Workpackages WP1, reviews (a) Languages. We may contribute to the survey about languages representing guidelines (with specific attention to the treatment of temporal aspects)

  11. LINKS to Workpackages WP2, Standard developments (b) Languages for clinical guidelines (with specific reference to temporal constraints). (c) An “upper-level” for the ontology of clinical actions(IF ANY!?) (d) Modelling the semantics of clinical guidelines (mapping into model-checkers’ languages; also temporal logics). • Semantics of Relational Temporal Databases (IF USED!?)

  12. LINKS to Workpackages WP3, Life-cycles, and life-cycle support • Semantics of cooperative updates on Temporal Relational Databases (IF USED!?) • Resource-based contextualization

  13. LINKS to Workpackages WP4, Software tools (h) task-specific prototypical tool to represent and propagate temporal constraints in clinical guidelines • Prototypical tool for validation based on model-checking techniques (IF VALIDATION INCLUDED !?) (j) Prototypical tool to contextualise guidelines on the basis of locally available resources.

More Related