New Desiderata for Biomedical Terminologies Discussant: James J. Cimino Columbia University.

Slides:



Advertisements
Similar presentations
Ontology Assessment – Proposed Framework and Methodology.
Advertisements

Panel 3: What level of data granularity, common standards, lexicon elements, and definitions need to be developed by the health system community to meet.
Architecture Tutorial 1 Overview of Today’s Talks Provenance Data Structures Recording and Querying Provenance –Break (30 minutes) Distribution and Scalability.
Using the Semantic Web to Construct an Ontology- Based Repository for Software Patterns Scott Henninger Computer Science and Engineering University of.
Recheck Examinations and Results Of course it’s hard. That’s what makes it difficult.
The Librarian Infobutton Tailoring Environment (LITE) James J. Cimino National Institutes of Health and Columbia University.
The Future of NDC: The HL7 Perspective James J. Cimino, M.D. Co-chair, HL7 Vocabulary Technical Committee Departments of Medicine and Medical Informatics.
Introduction to Hypothesis Testing
The Role of Standard Terminologies in Facilitating Integration James J. Cimino, M.D. Departments of Biomedical Informatics and Medicine Columbia University.
Desiderata for Controlled Medical Vocabularies James J. Cimino.
Clinical computing and the repository George Hripcsak Jim Cimino Pete Stetson.
The Biomedical Translational Research Information System (BTRIS) James J. Cimino Chief, Laboratory for Informatics Development National Institutes of Health.
Adaptation of Practice Guidelines for Clinical Decision Support: A Case Study of Diabetic Foot Care Mor Peleg 1, Dongwen Wang 2, Adriana Fodor 3, Sagi.
Supporting Medical Decision Making with Electronic Medical Records James J. Cimino Departments of Medicine and Medical Informatics Columbia University.
The Promise of Pathology Informatics James J. Cimino, M.D. Department of Medical Informatics Columbia University.
Secondary Uses of Clinical Data James J. Cimino Departments of Medicine and Biomedical Informatics Columbia University.
Clinical Vocabularies James J. Cimino, M.D. Columbia University.
Desirable Clinical Terminology Characteristics and Present Adherence James J. Cimino.
The Medical Entities Dictionary Columbia University Department of Biomedical Informatics.
Harnessing World Wide Web Technology and Standardized Terminology to Improve Decision Making for Patients and Providers James J. Cimino Departments of.
Introduction to the programme A.Hasman. Medical Informatics The study concerned with the understanding, communication and management of information in.
The Medical Entities Dictionary - © James J. Cimino The Columbia University/ NewYork Presbyterian Hospital Medical Entities Dictionary (The MED)
HL7 RIM Exegesis and Critique Regenstrief Institute, November 8, 2005 Barry Smith Director National Center for Ontological Research.
Use, Usability, Usefulness and Impact of an Infobutton Manager James J. Cimino, M.D. Department of Biomedical Informatics Columbia University College of.
FHIR/RfH.....What is it? And what’s next? Furore Ewout Kramer.
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
The design process z Software engineering and the design process for interactive systems z Standards and guidelines as design rules z Usability engineering.
Provenance Metadata for Shared Product Model Databases Etiel Petrinja, Vlado Stankovski & Žiga Turk University of Ljubljana Faculty of Civil and Geodetic.
10th Intl. Protégé Conference - July 15-18, Budapest, Hungary Do ontologies work? Barriers and Possibilities to Implement Ontologies in (Health)
Artificial, Composite and Secondary UIDs
Architecture Tutorial 1 Overview of Today’s Talks Provenance Data Structures Recording and Querying Provenance –Break (30 minutes) Distribution and Scalability.
Integrating Clinical Systems by Integrating Controlled Vocabularies James J. Cimino, MD Center for Medical Informatics Columbia University New York, New.
1 HL7 RIM Barry Smith
WHO – IHTSDO: SNOMED CT – ICD-11 coordination: Conditions vs. Situations Stefan Schulz IHTSDO conference Copenhagen, Apr 24, 2012.
How can ontologies help with electronic health records? Kent Spackman, MD PhD.
BAA - Big Mechanism using SIRA Technology Chuck Rehberg CTO at Trigent Software and Chief Scientist at Semantic Insights™
Intranet Technology in Hospital Information Systems James J. Cimino, M.D. Department of Medical Informatics Columbia University.
Review of Infoway’s COPD* Use Case for Care Plan Business Requirements Sasha Bojicic, Canada Health Infoway Ron Parker, Canada Health Infoway
Usability and Human Factors Cognition and Human Performance Lecture b This material (Comp15_Unit3b) was developed by Columbia University, funded by the.
Psychology 394U: Cognitive Concepts in Clinical and Social Psychology First Day’s lecture Gordon Bower.
Selected Responses How deep does the question dig?????
Information Dynamics & Interoperability Presented at: NIT 2001 Global Digital Library Development in the New Millennium Beijing, China, May 2001, and DELOS.
AF1.1 L1-2 Using models for and in explanations Compare features or parts of objects, living things or events.
Nursing Informatics NI.
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Vision: Impact of Information on the Health Field in the Future James J. Cimino Department of Medical Informatics Columbia University.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
Infobuttons: Context-specific Links from Clinical Systems to On-Line Knowledge Resources to Anticipate and Address Clinician Information Needs at the Point.
(1) ICS 313: Programming Language Theory Chapter 11: Abstract Data Types (Data Abstraction)
Approach to building ontologies A high-level view Chris Wroe.
Bloom’s Taxonomy Dr. Middlebrooks. Bloom’s Taxonomy.
Temporal Data Modeling
Of 24 lecture 11: ontology – mediation, merging & aligning.
1 The Relational Data Model David J. Stucki. Relational Model Concepts 2 Fundamental concept: the relation  The Relational Model represents an entire.
SPECIAL PURPOSE DATABASES 13/09/ Temporal Database Concepts  Time is considered ordered sequence of points in some granularity Use the term choronon.
1 Entity Relationship Approach u Top-down approach to data modeling u Uses diagrams u Normalization - confirms technical soundness u Entity Relationship.
Biostatistics Class 2 Probability 2/1/2000.
Electrolyte Review Use the slide show to test you knowledge of electrolyte balance. Launch the slide show and try to answer the questions.
The Needs for Coding and Classification Systems
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
Experience Management
Desiderata for Controlled Medical Vocabularies in the Twenty-First Century James J. Cimino.
Department of Medical Informatics
Knowledge Representation, Structuring and Ontology Development
Validity and Reliability II: The Basics
Ecoinformatics: supporting ecology as a data-intensive science
Presentation transcript:

New Desiderata for Biomedical Terminologies Discussant: James J. Cimino Columbia University

Dilemmas of Biomedical Terminologies

Dilemmata of Biomedical Terminologies Abstract concepts vs. real world entities Knowledge about concepts vs. knowledge about extensions in reality Terms with context-specific meanings Changes in knowledge vs. changes in meaning

Abstract Concepts vs. Real World Entities Concept PhilosophyTerminology Ontology GOFMARealismConceptualism

Desiderata for Controlled Medical Data I - Capture what is known about the patient II - No information loss III - No false implications IV - Support retrieval V - Support reuse VI - Support aggregation VII - Support inference

Desiderata for Controlled Medical Terminologies Provide identifiers for meanings we want to apply to the patient Make sure the semantics are universally understood, separate from linguistics Make sure that, as our understanding changes, original meaning is not forgotten Provide a bridge between what we record and how we reason

Patient Data as Extensions of Concepts Everything we record is an abstraction Context tells us how the abstractions are interpreted Example: contexts of diagnoses in medical records Example: events Example: evolution of patient problems

Everything We Record is an Abstraction We don’t say that concepts cause concepts or terms cause terms Nor do we say that we are storing bits of pneumonia in the EMR Pneumococcal pneumonia is something we “know” about that we associate with the patient through interpretation of what we “know” about the patient So is the infiltrate seen on the chest x-ray So is the chest x-ray

Context in the EMR: What We See Lab results: Sodium 130 Problem list: Hyponatremia Medication list: Hypertonic Saline Medication administration: Hypertonic Saline

Context in the EMR: What We Record At lab reports with id and value for –At 10AM EST May 1, 2005 lab reports Stat Serum Sodium with id # and value 130 for Mr. Jones At interprets as indicating for –At 10:01AM EST May 1, 2005, Dr. Brown interprets # as indicating Hyponatremia for Mr. Jones

Context in the EMR: What We Record At orders pharmacy item with order id for –At 10:02AM EST, May 1, 2005 Dr. Brown orders pharmacy time with order id #3233 for Mr. Jones At pharmacy delivers with inventory id for order id for –At 10:03AM EST, May 1, 2005 pharmacy delivers Lilly Product 5505 with inventory id # for Mr. Jones

Context in the EMR: What We Record At decision support system suggests for –At 10:04AM EST, May 1, 2005 decision support system suggests Factitious Hyponatremia for Mr. Jones

Concepts or Entities? Concepts included in EMR: –Stat Serum Sodium –Hyponatremia –Hypertonic Saline –Lilly Product 5505 –Factitious Hyponatremia Entities in Real World –Mr. Jones –Mr. Jones’s Blood –Serum Specimen #55555 –Lab –Test ID # –Analyzer #114 –130 (reading on analyzer) –Dr. Brown –Pharmacy –Lilly Product 5505 # –Decision Support System

What Do Knowledge Do We Need? Stat Serum Sodium measures Sodium Hyponatremia is defined as Sodium below normal range Normal Range of Sodium is Lilly Product 5505 is a Hypertonic Saline # is an available instance of Lilly Product 5505 Analyzer #114 uses Flame Photometry Method Factitious Hyponatremia occurs when Sodium is low, method is flame photometry, and triglycerides are high

How Do We Cope with Changes in Our Knowledge About the Patient? Barrrows RC, Johnson SB: A data model that captures clinical reasoning about patient problems. SCAMC 1995: Chest pain  R/O CAD  Costochondritis  Resolved (S/P Costochondritis) Thread of assessments at points in time What do you think the patient has vs. (please tell the court) What did you think the patient had?

How Do We Cope with Changes in Our General Knowledge? Change in: –what tests measure –formulary –normal ranges –definition of disease The test: if we change update the knowledge, do we change the old data?

Referent Tracking We do this now (or we should) Implicit vs. explicit interpretation Each referent still has to correspond to some meaning Solution must be practical, usable, and maintainable

The Desiderata Revisited Concept orientation - what is the alternative? Concept permanence and graceful evolution - version control Formal definitions - add to knowledge vs. recognize change Reject NEC - store what the patient has and classify later Multiple granularities - patient level vs. reuse Representing context - the implicit meaning in the EMR design

General Philosophy of Concepts and Data Concept plus Context Meaning plus Stamp RecapitulatesPhilatelyOntology