Werner Ceusters, MD Ontology Research Group

Slides:



Advertisements
Similar presentations
1 Skilling Up for Patient-Centered E-Health E. Vance Wilson University of Wisconsin-Milwaukee.
Advertisements

Definitions of EBP Popular in SW
ECO R European Centre for Ontological Research Realist Ontology for Electronic Health Records Dr. Werner Ceusters ECOR: European Centre for Ontological.
Lecture 5 Standardized Terminology and Language in Health Care (Chapter 15)
Proposed Meaningful Use Criteria for Stage 2 and 3 John D. Halamka.
Chapter 2 Health Care Information Systems: A Practical Approach for Health Care Management 2nd Edition Wager ~ Lee ~ Glaser.
Referent Tracking: Towards Semantic Interoperability and Knowledge Sharing Barry Smith Ontology Research Group Center of Excellence in Bioinformatics and.
New York State Center of Excellence in Bioinformatics & Life Sciences R T U Ontology and the future of Evidence-Based Medicine Dagstuhl May 23th, 2006.
Chapter 17 Nursing Diagnosis
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
E-Referral enabled collaborative health care Opportunities and considerations Presented by: Sasha Bojicic Emerging Technology Group Canada Health Infoway.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
NURS 4006 Nursing Informatics
 Definitions  Goals of automation in pharmacy  Advantages/disadvantages of automation  Application of automation to the medication use process  Clinical.
Performance Measurement and Analysis for Health Organizations
Ontology Development in the Sciences Some Fundamental Considerations Ontolytics LLC Topics:  Possible uses of ontologies  Ontologies vs. terminologies.
© 2003 East Collaborative e ast COLLABORATIVE ® eC SoftwareProducts TrackeCHealth.
INFORMATION SYSTEMS Overview
Standard of Electronic Health Record
New York State Center of Excellence in Bioinformatics & Life Sciences R T U New York State Center of Excellence in Bioinformatics & Life Sciences R T U.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
N222Y Health Information Technology Module: Improving Quality in Healthcare and Patient Centered Care Looking to the Future of Health IT.
LOGIC AND ONTOLOGY Both logic and ontology are important areas of philosophy covering large, diverse, and active research projects. These two areas overlap.
This material was developed by Oregon Health & Science University, funded by the Department of Health and Human Services, Office of the National Coordinator.
Trustworthy Semantic Webs Dr. Bhavani Thuraisingham The University of Texas at Dallas Lecture #4 Vision for Semantic Web.
Of 33 lecture 1: introduction. of 33 the semantic web vision today’s web (1) web content – for human consumption (no structural information) people search.
CRITICAL THINKING AND THE NURSING PROCESS Entry Into Professional Nursing NRS 101.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
Learning Outcomes Discuss current trends and issues in health care and nursing. Describe the essential elements of quality and safety in nursing and their.
New York State Center of Excellence in Bioinformatics & Life Sciences R T U New York State Center of Excellence in Bioinformatics & Life Sciences R T U.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
New York State Center of Excellence in Bioinformatics & Life Sciences R T U New York State Center of Excellence in Bioinformatics & Life Sciences R T U.
New York State Center of Excellence in Bioinformatics & Life Sciences R T U 1 MIE 2006 Workshop Semantic Challenge for Interoperable EHR Architectures.
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
Introduction to Health Informatics Leon Geffen MBChB MCFP(SA)
Engineering, 7th edition. Chapter 8 Slide 1 System models.
© 2016 Chapter 6 Data Management Health Information Management Technology: An Applied Approach.
Semantic Graph Mining for Biomedical Network Analysis: A Case Study in Traditional Chinese Medicine Tong Yu HCLS
TITIN ANDRI WIHASTUTI SCHOOL OF NURSING FACULTY OF MEDICINE
Functional EHR Systems
Efficient and secure transborder exchange of patient data
Department of Psychiatry, University at Buffalo, NY, USA
“Ontology Measurement and evaluation" mini-series Realism-based Change Management for Quality Assurance in Ontologies and Data Repositories NIST-Ontolog-NCOR,
NeurOn: Modeling Ontology for Neurosurgery
Europe’s Environment Assessment of Assessments EE-AoA 2011
Achieving Semantic Interoperability of Cancer Registries
THIS IS TO EVIDENCE YOUR WORK AND GET THE BEST GRADE POSSIBLE
IB Assessments CRITERION!!!.
MUHC Innovation Model.
Towards the Information Artifact Ontology 2
DSS & Warehousing Systems
Auditor Training Module 1 – Audit Concepts and Definitions
TechStambha PMP Certification Training
WP1: D 1.3 Standards Framework Status June 25, 2015
Abstract descriptions of systems whose requirements are being analysed
Component 11/Unit 7 Implementing Clinical Decision Support
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
Standard of Electronic Health Record
Electronic Health Information Systems
Electronic Health Records
Model-View-Controller Patterns and Frameworks
Functional EHR Systems
What is “Biomedical Informatics”?
2. An overview of SDMX (What is SDMX? Part I)
Medical Students Documenting in the EMR
AICT5 – eProject Project Planning for ICT
Werner CEUSTERS, Barry SMITH
Nursing informatics Lecture (11).
eHR Clinical data repository and pharmacovigilance
Presentation transcript:

Ontology and the future of Evidence-Based Medicine Dagstuhl May 23th, 2006 Werner Ceusters, MD Ontology Research Group Center of Excellence in Bioinformatics & Life Sciences SUNY at Buffalo, NY

Evidence Based Medicine the integration of best research evidence with clinical expertise and patient values. best research evidence: clinically relevant patient centered research into the accuracy and precision of diagnostic tests, the power of prognostic markers, and the efficacy and safety of care regimens. clinical expertise: the ability to use clinical skills and past experience to rapidly identify each patient's unique health state. patient values: the unique preferences, concerns and expectations each patient brings to a clinical encounter and which must be integrated into clinical decisions if they are to serve him.

Application of Evidence Based Medicine Now: Decisions based on (motivated/justified by) the outcomes of (reproducable) results of well-designed studies Guidelines and protocols Evidence is hard to get, takes time to accumulate. Future: Each discovered fact or expressed belief should instantly become available as contributing to ‘evidence’, wherever its description is generated.

Future scenarios Data entered about a successful treatment of a case in X generates a suggestion for a similar case in Y; Submission of a new paper to Pubmed on some ADR triggers an alert in EHR systems worldwide for those patients that might be at risk; …  From reactive care to proactive care

Some problem areas Pharmaceutical Industry: Consumer health: Optimise drug discovery Make “messy” databases more useful for everybody Consumer health: Opposing forces: Quality of information Make them consume Malpractice suits Public sector health: Cost containment Cost effectiviness of treatment, prevention Bio-informatics world: How to find out that a ‘discovery’ is a ‘new’ discovery ?

An action plan for a European eHealth Area. By the start of 2005: MS and EC should agree on an overall approach to benchmarking in order to assess the quantitative, including economic, and qualitative impacts of e-Health. By end 2006: in order to achieve a seamless exchange of health information across Europe through common structures and ontologies, MS, in collaboration with the EC, should identify and outline interoperability standards for health data messages and electronic health records, taking into account best practices and relevant standardisation efforts. By end 2008: the majority of all European health organisations and health regions (communities, counties, districts) should be able to provide online services such as teleconsultation (second medical opinion), e-prescription, e-referral, telemonitoring and telecare. Failed

One key issue: Semantic Interoperability Working definition: Two information systems are semantically interoperable if and only if each can carry out the tasks for which it was designed using data and information taken from the other as seemlessly as using its own data and information. system: Any organized assembly of resources and procedures united and regulated by interaction or interdependence to accomplish a set of specific functions. information system: a system, whether automated or manual, that comprises people, machines, and/or methods organized to collect, process, transmit, and disseminate data that represent user information.

Communication & Interpretation Essential components Communication & Interpretation People: physicians, nurses, patients, healthcare administrators, ... Machines: to make humans interact with the EHR, to transmit data from one EHR to another to enter data (lab analysers, EMR monitors, ...) to interprete data (alerts, quality assessment, protocol selection, ...) Data and information (data in context) Procedures

Understanding content (1) “John Doe has a pyogenic granuloma of the left thumb” John Doe has a pyogenic granuloma of the left thumb

Understanding content (2) <record> <patient>John Doe</patient> <diagnosis>pyogenic granuloma of the left thumb</diagnosis> </record> <record> <subject> John Doe </subject> <diagnosis> pyogenic granuloma of the left thumb </diagnosis> </record>

Understanding content (3) <129465004> <116154003>John Doe</116154003> < 8319008 > 17372009 <finding site> 76505004 <laterality>7771000</laterality> </finding site> </ 8319008 > </129465004>

Ontology based on Unqualified Realism Accepts the existence of a real world outside mind and language a structure in that world prior to mind and language (universals / particulars) Rejects nominalism, conceptualism, ontology as a matter of agreement on ‘conceptualizations’ Uses reality as a benchmark for testing the quality of ontologies as artifacts by building appropriate logics with referential semantics (rather than model-theoretic)

Relevance for EHR & Semantic Interoperability Ontology EHR The conceptualist approach

Relevance for EHR & Semantic Interoperability The realist approach R E A L I T Y L O G O L K A I S N S G Ontology EHR

Terminology A theory concerned with those aspects of the nature and the functions of language which permit the efficient representation and transmission of items of knowledge (J. Sager) Precise and appropriate terminologies provide important facilities for human communication (J. Gamper)

Ontology An ontology is a representation of some pre-existing domain of reality which (1) reflects the properties of the objects within its domain in such a way that there obtains a systematic correlation between reality and the representation itself, (2) is intelligible to a domain expert (3) is formalized in a way that allows it to support automatic information processing

A division of labour Terminology: Ontology: Communication amongst humans Communication between human and machine Ontology: Representation of “reality” inside a machine Communication amongst machines Interpretation by machines

Today’s biggest problem: a confusion between “terminology” and “ontology” The conditions to be agreed upon when to use a certain term to denote an entity, are often different than the conditions which make an entity what it is. Trees would still be different from rabbits if there were no humans to agree on how these things should be called. “ontos” means “being”. The link with reality tends to be forgotten: one concentrates on the models instead of on the reality.

What to do about it ? (1) Research: Revision of the appropriatness of concept-based terminology for our purposes Relationship between models and that part of reality that the models want to represent Adequacy of current tools and languages for representation Boundaries between terminology and ontology and the place of each in semantic interoperability in healthcare

Training and awareness What to do about it ? (2) Training and awareness Make people more critical wrt terminology and ontology promisses What is needed must be based on needs, not on the popularity of a new concept But in a system, it’s not just your own needs, it is each component’s needs ! Towards “an ontology of ontologies” First description Then quality criteria

Ultimate goal Ontology continuant disorder person CAG repeat EHR Juvenile HD #IUI-1 ‘affects’ #IUI-2 #IUI-3 ‘affects’ #IUI-2 #IUI-1 ‘causes’ #IUI-3 ... Referent Tracking Database

3 fundamentally different in levels the reality on the side of the patient; the cognitive representations of this reality embodied in observations and interpretations on the part of clinicians and others; the publicly accessible concretizations of such cognitive representations in representational artifacts of various sorts, of which ontologies and terminologies are examples.

Example: a person (in this room) ’s phenotypic gender Reality: Male Female Cognitive representation [male] [female] In the EHR: “male” “female” “unknown” Other types of phenotypic gender ?

4 fundamental reasons for making changes changes in the underlying reality does the appearance of an entry (in a new version of an ontology or in an EHR) relate to the appearance of an entity or a relationship among entities in reality ?; changes in our (scientific) understanding; reassessments of what is considered to be relevant for inclusion (notion of purpose), or: encoding mistakes introduced during data entry or ontology development.

Key requirement Any change in an ontology or data repository should be associated with the reason for that change !

Example: a person (in this room) ’s gender in the EHR In John Smith’s EHR: At t1: “male” at t2: “female” What are the possibilities ? Change in reality: transgender surgery Change in understanding: it was female from the very beginning but interpreted wrongly ( No change in relevance ) Correction of data entry mistake (was understood as male, but wrongly transcribed)

Possible combinations OE: objective existence; ORV: objective relevance; BE: belief in existence; BRV: belief in relevance; Int.: intended encoding; Ref.: manner in which the expression refers; G: typology which results when the factor of external reality is ignored. E: number of errors when measured against the benchmark of reality. P/A: presence/absence of term.

Possible evolutions

Towards an implementation A client-server application in which the server is composed of four layers: the Web Server Layer (WSL) provides the interface to clients via web services; the RT Core application programming interface (API) encapsulates the data services related to storage and retrieval. Its Security Module validates the access rights before any data service; the database layer stores all the RT data, and; the reasoner layer (RL) performs inferences upon specific requests, based on the information available in the database and, if available, the ontologies that have been used for the descriptions of the portions of reality. Shahid Manzoor

Schematic representation Internet Referent Tracking (RT) Server Web Server Referent Tracking Web services Referent Tracking Core System API Security Module ·         RT Data ·         Imported Ontologies rules   Reasoner Health Institution B registered WITH RT EHR Client Health Institution A hosting RT Session Manager

Simple Graph Representation Privacy issues

Complete structure

UML-diagram for the entities in the RDF-graph

Querying the RTDB using ontologies (SPARQL) Retrieve particulars that are related to the universal face 1 PREFIX rts: <http://ecor#> 2 PREFIX fma: <http://FMA#> 3 SELECT ?p ?u ?v 4 WHERE {?p rts:relation ?u . 5 ?u a rts:PtoU . 6 ?u rts:u ?t . 7 ?t a fma:Face . 8 }

Querying the RTDB using ontologies (SPARQL) 1 WHERE {?p rts:relation ?rf . 2 ?rf a rts:PtoP . 3 ?rf rts:p ?f . 4 ?f a fma:Head . 5 ?f rts:relation ?rd . 6 ?rd a rts:PtoP . 7 ?rd :p ?d . 8 ?d a dis:DISEASES AND INJURIES . } Retrieve patients with diseases in the head

Test interface