Controlled Medical Nomenclature for NAHLN NAHLN January 2005 Las Vegas, NV.

Slides:



Advertisements
Similar presentations
Term list(s) vs. SNOMED -CT ® subset. 2 nd AAHA Software Vendors Summit – April 21, 2009.
Advertisements

SNOMED Core Structures 2 nd AAHA Software Vendors Summit – April 21, 2009.
C6 Databases.
Copyright © 2001 College of American Pathologists Pseudophakic corneal edema Sample Hierarchy for Corneal Edema Idiopathic corneal edema Phakic corneal.
Copyright © 2001 College of American Pathologists Sample Hierarchy for AIDS with Pneumonia AIDS with bacterial pneumonia AIDS with viral Pneumonia About.
Medical Record Abstract Workshop Nov 16, Why are we here? VMDB success requires “harmony” Sophisticated veterinary medical records need a capable.
Overview of SNOMED CT International Release, U. S
Introduction to Database Management  Department of Computer Science Northern Illinois University January 2001.
The Role of the UMLS in Vocabulary Control CENDI Conference “Controlled Vocabulary and the Internet” Stuart J. Nelson, MD.
Lecture 5 Standardized Terminology and Language in Health Care (Chapter 15)
Managing data Resources: An information system provides users with timely, accurate, and relevant information. The information is stored in computer files.
The Future of NDC: The HL7 Perspective James J. Cimino, M.D. Co-chair, HL7 Vocabulary Technical Committee Departments of Medicine and Medical Informatics.
Desiderata for Controlled Medical Vocabularies James J. Cimino.
Introduction to Databases Transparencies
Clinical Vocabularies James J. Cimino, M.D. Columbia University.
Desirable Clinical Terminology Characteristics and Present Adherence James J. Cimino.
New Desiderata for Biomedical Terminologies Discussant: James J. Cimino Columbia University.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Copyright © 2001 College of American Pathologists Sample Hierarchy for Acute MI Acute MI of lateral wall Acute MI of apical-lateral wall Acute Myocardial.
Copyright © 2001 College of American Pathologists Sample Hierarchy for Hepatitis Chronic viral hepatitis Chronic viral hepatitis C About SNOMED Relationships.
Veterinary Informatics Standards Development and Harmonization AVMA Stakeholders Meeting July, 2002 Nashville, TN.
THEORIES, MODELS, AND FRAMEWORKS
The chapter will address the following questions:
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
Managing SNOMED in your system. 2 nd AAHA Software Vendors Summit – April 21, 2009.
Overview of the Database Development Process
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Veterinary Terminology Services Lab Va-Md Regional College of Veterinary Medicine The Animal Names Terminology Subset of SNOMED CT ® Suzanne L. Santamaria,
Karen Gibson.  Significant investment in eHealth is underway  Clinical records: ◦ Not only a record for the author ◦ Essential to inform the next person.
SNOMED for Clinical Records: Tools to facilitate implementation. Jeff R. Wilcke, DVM, MS, DACVCP AVMA Liaison to the SNOMED Editorial Board.
Invitation to Computer Science 5th Edition
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
10th Intl. Protégé Conference - July 15-18, Budapest, Hungary Do ontologies work? Barriers and Possibilities to Implement Ontologies in (Health)
Chapter 7: Database Systems Succeeding with Technology: Second Edition.
6 Chapter Databases and Information Management. File Organization Terms and Concepts Bit: Smallest unit of data; binary digit (0,1) Byte: Group of bits.
More and Better Data for Research: U.S. Health Data Content Standards Betsy L. Humphreys Assistant Director for Health Services Research Information National.
Overview, Benefits and how to approach Implementing - Robyn Richards (NEHTA)
Copyright © 2001 College of American Pathologists Sample Hierarchy for Tularemia Disorder Zoonotic bacterial disease Enteric tularemia Glandular tularemia.
Storing Organizational Information - Databases
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4c Basic Health Data Standards Component 9/Unit.
Module 2: Information Technology Infrastructure Chapter 5: Databases and Information Management.
Chapter 5 Uma Gupta Introduction to Information Systems  2000 by Prentice Hall. 5-1 Database Design and Management.
Generic Tasks by Ihab M. Amer Graduate Student Computer Science Dept. AUC, Cairo, Egypt.
Lab and Messaging CoP 11/29/2012. Agenda Agenda review Introduction to the Specimen Cross-Mapping Table (Specimen CMT) – Background – Expected uses –
2/20: Ch. 6 Data Management What is data? How is it stored? –Traditional management storage techniques; problems –DBMS.
SNOMED Core Structures NAHLN January 2005 Las Vegas, NV.
Veterinary Adaptation of SNOMED-CT ® We don’t have to eat the whole elephant!
SNOMED and Veterinary Clinical Systems “Do we have to eat the whole elephant?” Dr. Jeff Wilcke, June 2008.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
FROM ONE NOMENCLATURES TO ANOTHER… Drs. Sven Van Laere.
FIND IT! USING LIBRARY CATALOGING CONCEPTS TO ORGANIZE AND MAKE RECORDS FINDABLE DIONNE L. MACK, INTERIM DIRECTOR OF QUALITY OF LIFE DEPARTMENTS.
Essential SNOMED. Simplifying S-CT. Supporting integration with health
© 2017 by McGraw-Hill Education. This proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
What is Database Administration ?
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
Database Management.
Data Quality Webinar for General Practice
The Needs for Coding and Classification Systems
Database Database is a large collection of related data that can be stored, generally describes activities of an organization. An organised collection.
Networking and Health Information Exchange
Controlled Medical Nomenclature for NAHLN
Chapter 2 Database Environment.
Data Base System Lecture : Database Environment
MANAGING DATA RESOURCES
Managing data Resources:
Undergraduate Courses
Desiderata for Controlled Medical Vocabularies in the Twenty-First Century James J. Cimino.
Module 2 Topics Information technology governance: Organization and planning for IS.
Presentation transcript:

Controlled Medical Nomenclature for NAHLN NAHLN January 2005 Las Vegas, NV

Qualifications There’s “retentive” – if that’s not enough: There’s “anal retentive” – if that’s not enough: There’s “retentive enough to create and maintain a nomenclature”

Lists of words… Nomenclature The system or set of names for things, etc., commonly employed by a person or community (Petchamp, SNVDO, SNOMED) The system or set of names for things, etc., commonly employed by a person or community (Petchamp, SNVDO, SNOMED)Vocabulary A collection or list of words with explanations of their meanings (SNOMED) A collection or list of words with explanations of their meanings (SNOMED)Classification The result of classifying; a systematic distribution, allocation, or arrangement, in a class or classes; esp. of things which form the subject-matter of a science or of a methodic inquiry. (SNOMED) The result of classifying; a systematic distribution, allocation, or arrangement, in a class or classes; esp. of things which form the subject-matter of a science or of a methodic inquiry. (SNOMED)

What do we need? Nomenclature ONLY Provides a simple list for data entry Provides a simple list for data entry Vocabulary / Classification We can be CERTAIN that the “term” (description in SNOMED) means what we think it means. We can be CERTAIN that the “term” (description in SNOMED) means what we think it means. We can develop rules that allow us to combine concepts to express ideas more complicated than those contained in the nomenclature. We can develop rules that allow us to combine concepts to express ideas more complicated than those contained in the nomenclature. We can use the knowledge base supported by the vocabulary/classification to search, retrieve and analyze our data. We can use the knowledge base supported by the vocabulary/classification to search, retrieve and analyze our data.

NAHLN Nomenclature needs Is controlled nomenclature (1 or more) essential – YES Is LOINC essential – Yes (or something close) Is SNOMED essential – NO, but you need standard microorganisms, breed/species, etc. Can SNOMED provide what’s needed outside of laboratory tests - YES

Why a controlled nomenclature? Aggregation of text-based content from multiple sources Multiple individuals Multiple individuals Multiple institutions Multiple institutions Any time you rely on a computer to manipulate language and “meaning” is critical. Procedures list (for billing) Procedures list (for billing)

Why a controlled vocabulary / nomenclature? Bovine respiratory disease complex = Shipping fever = BRDC How does one automate recognition of the synonymy?

Why did “we” pick SNOMED? A shared nomenclature must be maintained. SNOMED is the ONLY actively maintained nomenclature that has veterinary content. AVMA had a long-term investment Veterinary medicine CANNOT afford: To build it’s own competent nomenclature To build it’s own competent nomenclature To continue to live without a competent nomenclature To continue to live without a competent nomenclature

Characteristics of a controlled vocabulary / nomenclature. Cimino, JJ. Desiderata for Controlled Medical Vocabularies in the Twenty- First Century Methods of Information in Medicine Nov, 37(4-5): THE Review of ideal characteristics of a controlled medical vocabulary / nomenclature. Perhaps the best READING review of medical vocabulary / nomenclature available.

Content, content, content First criticism of ANY nomenclature (by users) is lack of content

Content, content, content Approaches Enumerate all possible concepts (simple and complex) Enumerate all possible concepts (simple and complex)Pneumonia Pneumonia of left lung Pneumonia of left caudal lung This nomenclature will grow quickly. It will get VERY large VERY fast.

Content, content, content Approaches Enumerate all possible concepts (simple and complex) Enumerate all possible concepts (simple and complex) Provide all necessary “atoms,” create effective syntax, “teach” the syntax to users (or systems). Provide all necessary “atoms,” create effective syntax, “teach” the syntax to users (or systems).Pneumonia Left lung Left Caudal lung Pneumonia Pneumonia, body part (left lung) Pneumonia, body part (left caudal lung) Probably the theoretical ideal. I have not the first idea how!

Content, content, content Approaches Enumerate all possible concepts (simple and complex) Enumerate all possible concepts (simple and complex) Provide all necessary “atoms,” create effective syntax, “teach” the syntax to users (or systems). Provide all necessary “atoms,” create effective syntax, “teach” the syntax to users (or systems). Drastically limit the scope of the nomenclature. Drastically limit the scope of the nomenclature. May actually improve usability of the nomenclature for a limited purpose, however: 1. The next project and the next interaction require development of a new nomenclature 2. Connections between projects require “mapping”. 3. Users will not be happy. Might be easier to build and use a large single nomenclature.

Concept Orientation Concept – an embodiment of a particular meaning Concepts must correspond to at least one meaning (non-vagueness) Concepts must correspond to at least one meaning (non-vagueness) Concepts must correspond to no more than one meaning (non-ambiguity) Concepts must correspond to no more than one meaning (non-ambiguity) Meanings correspond to no more than one concept (non-redundancy) Meanings correspond to no more than one concept (non-redundancy)

Concept permanence Once created, the meaning of a concept is inviolable. Concept identifiers can NEVER be reused. Contributes to stability of legacy information. Contributes to stability of legacy information.

Non-semantic identifier Unique name Using the name inhibits (prohibits?) improvements in concept “name” Using the name inhibits (prohibits?) improvements in concept “name” Harder to cope with synonymy. Harder to cope with synonymy. Hierarchical designators (codes with meaning) inhibit classification Monohierarchies provide inadequate classification capability for retrieval purposes. Monohierarchies provide inadequate classification capability for retrieval purposes. Polyhierarchies cannot be supported. Polyhierarchies cannot be supported. (A concept can’t be in its multiple logical locations).

Polyhierarchies Medical concepts often classified in multiple ways Acute bacterial pneumonia It is a bacterial (infectious) disease It is a bacterial (infectious) disease It is a pulmonary disease It is a pulmonary disease It is an inflammatory condition It is an inflammatory condition It is an acute condition It is an acute condition

Formal definitions Collection of relationships to other concepts in the vocabulary Acute Bacterial pneumonia Causative agent = bacteria Causative agent = bacteria Has location = lung Has location = lung Has morphology = inflammation Has morphology = inflammation Has course = acute Has course = acute

Reject “not elsewhere classified” The fundamental problem is “meaning drift” Example Year one nomenclature has Year one nomenclature hasPneumoniaBronchitis Respiratory disease NEC

Reject “not elsewhere classified” The fundamental problem is “meaning drift” Example Year TWO the nomenclature has Year TWO the nomenclature hasPneumoniaBronchitisTracheobronchitis Respiratory disease NEC Last year tracheobronchitis was “respiratory disease, NEC”

Reject “not elsewhere classified” (NEC) NEC ≠ NOS (Not Otherwise Specified) NOS = “I’ve said all I’m going to say”. NOS = “I’ve said all I’m going to say”. NOS is not considered to be inappropriate. NOS is not considered to be inappropriate. Current preference is to exclude NOS. The concept means what it means, no more no less. Current preference is to exclude NOS. The concept means what it means, no more no less.

Multiple granularities A large standardizing nomenclature (like SNOMED) must provide concepts at an appropriate level of detail for every user class. Not an issue with a purpose-built nomenclature.

Recognize Context Must provide an ability to distinguish between uses of the concept… Patient has acute bacterial pneumonia Patient has acute bacterial pneumonia Patient has history of acute bacterial pneumonia Patient has history of acute bacterial pneumonia Patients littermate died of acute bacterial pneumonia Patients littermate died of acute bacterial pneumonia System design and perhaps the message system should cope with acquiring context Nomenclature may be required to cope with context in messages, or may provide context concepts for the message.

Evolve Gracefully A nomenclature must have a strategy for coping with new content. The bane of home grown nomenclatures The bane of home grown nomenclatures (Who’s looking after your list of concepts?) Nomenclature maintenance is not everyone’s cup of tea. Nomenclature maintenance is not everyone’s cup of tea. A controlled nomenclature serves as an arbiter of sorts. A controlled nomenclature serves as an arbiter of sorts. A nomenclature used by more than one organization (d-lab) must have update and sharing mechanisms in place.

Recognize redundancy Redundancy must be avoided in the concept list Redundancy must be provided for using a synonym mechanism. Egos and dispersed training insure that there exist multiple ways to say almost anything. They’re still talkin’ about the same thing. They’re still talkin’ about the same thing.

SNOMED history / future Reduce storage size Reduce Storage size No longer relevant Categorize information Multiple code-based hierarchies Poly-hierarchical categorization Pathology content “All Medicine” Veterinary content separate, then integrated Integrated content “Computability” for retrieval. Natural language, artificial intelligence, decision support SNOP SNOMED SNOVET SNOMED III SNOMED RTSNOMED CT

Development history SNOP Morphologies MorphologiesSNOMED Morphologies, Etiologies, Locations Morphologies, Etiologies, LocationsSNOVET Same structure as SNOMED Same structure as SNOMED Mix of existing SNOMED, additional veterinary content Mix of existing SNOMED, additional veterinary content SNOMED III Disorders, Morphology, Living organisms, social context Disorders, Morphology, Living organisms, social context Veterinary content re-integrated Veterinary content re-integrated SNOMED RT Logic based approach to SNOMED. Axes became hierarchies. Most significantly, the poly-hierarchic approach to classification. Logic based approach to SNOMED. Axes became hierarchies. Most significantly, the poly-hierarchic approach to classification. SNOMED CT SNOMED RT on steroids. Post merger with CTv3. SNOMED RT on steroids. Post merger with CTv3.

SNOMED III (3.5) A – Physical agents C – Chemicals D – Disease F – Biological function G – General qualifiers J - Jobs L – Living organisms M – Morphology P – Procedures S – Social context T – Topography X – Pharmaceutical companies Axes

SNOMED CT Disease Finding / observation / clinical history Procedure Body structure normal and abnormal Organism Physical Force SubstanceSpecimen Social Context Attributes Context dependent categories Physical object Events Environments and geographical location Observable entity Qualifier value Staging and Scales

Complaints about SNOMED It’s too… Big Big Complicated Complicated Expensive Expensive Yes but… We can make it smaller (sort of), and use small pieces (for most purposes). We can make it smaller (sort of), and use small pieces (for most purposes). Use it in simple and straightforward ways Use it in simple and straightforward ways But nothin, it’s a bit expensive. But nothin, it’s a bit expensive. Not the license fees, the cost of making it work.

Is the expense worth it? IF the long-range goal is useful… The selected standards adhere to design specifications that have developed through hard experience in the medical profession. The selected standards adhere to design specifications that have developed through hard experience in the medical profession. Essential / desirable features have been documented. The selected standards represent extraordinary functionality, produced and maintained at great cost to the medical profession. The selected standards represent extraordinary functionality, produced and maintained at great cost to the medical profession. We can leverage these standards for 10¢ / $1.00

Bovine reportable disease system. Bovine breeds Bovine “occupation” and husbandry concepts Brief list of reportable diseases Lab tests that support disease list Place to put the concepts in the message structures Lab to network Lab to network

Bovine medical record Bovine Breeds Bovine lab tests, all not just reportable All applicable disorders, findings, procedures Message structures lab to clinic lab to clinic clinic to lab clinic to lab clinic to clinic clinic to clinic

SNOMED-CT, HL-7, LOINC Mixed practice Subsets of standards Bovine practice Bovine disorders Bovine Reportable

WNV Rabies FMD SNOMED 1 LOINC 1 HL7 2 Disease reporting system 1 = three independent subsets 2 = one subset of necessary messages