A Case Study of ICD-11 Anatomy Value Set Extraction from SNOMED CT Guoqian Jiang, PhD ©2011 MFMER | slide-1 Division of Biomedical Statistics & Informatics,

Slides:



Advertisements
Similar presentations
Semantic Interoperability in Health Informatics: Lessons Learned 10 January 2008Semantic Interoperability in Health Informatics: Lessons Learned 1 Medical.
Advertisements

Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.
Biomedical Informatics Reference Ontologies in Biomedicine Christopher G. Chute, MD DrPH Professor and Chair, Biomedical Informatics Mayo Clinic College.
Using Several Ontologies for Describing Audio-Visual Documents: A Case Study in the Medical Domain Sunday 29 th of May, 2005 Antoine Isaac 1 & Raphaël.
Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.
Data Normalization Milestones. Data Normalization  Goals –To conduct the science for realizing semantic interoperability and integration of diverse data.
CTS2 Terminology Services
Catalina Martínez-Costa, Stefan Schulz: Ontology-based reinterpretation of the SNOMED CT context model Ontology-based reinterpretation of the SNOMED CT.
Open Health Tools Distributed Terminology System Presentation Jack Bowie SVP Sales and Marketing Apelon, Inc. 1.
© Copyright 2008, Mayo Clinic College of Medicine Mayo Clinic Open Health Tools Application for Membership OHT Board Meeting, Birmingham, UK July 1, 2008.
A general-purpose text annotation tool called Knowtator is presented. Knowtator facilitates the manual creation of annotated corpora that can be used for.
LexWiki Framework & Use Cases SMW for Distributed Terminology Development Guoqian Jiang, PhD, Robert Freimuth, PhD, Haorld Solbrig Mayo Clinic NCI caBIG.
©2013 MFMER | slide-1 Building A Knowledge Base of Severe Adverse Drug Events Based On AERS Reporting Data Using Semantic Web Technologies Guoqian Jiang,
Guoqian Jiang, MD, PhD Mayo Clinic
Introduction to openEHR
Biomedical Informatics Some Observations on Clinical Data Representation in EHRs Christopher G. Chute, MD DrPH, Mayo Clinic Chair, ICD11 Revision, World.
Implementing a Clinical Terminology David Crook Subset Development Project Manager SNOMED in Structured electronic Records Programme NHS Connecting for.
Mayo LexWiki: A Prototype of Collaborative Platform for Terminology/Ontology Content Development Guoqian Jiang, Ph.D. Division of Biomedical Informatics,
Harmonization of SHARPn Clinical Element Models with CDISC SHARE Clinical Study Data Standards Guoqian Jiang, MD, PhD Mayo Clinic On behalf of CDISC CEMs.
1 Betsy L. Humphreys, MLS Betsy L. Humphreys, MLS National Library of Medicine National Library of Medicine National Institutes of Health National Institutes.
Ontology-based Convergence of Medical Terminologies: SNOMED CT and ICD-11 Institute for Medical Informatics, Statistics and Documentation, Medical University.
LexEVS 6.0 Overview Scott Bauer Mayo Clinic Rochester, Minnesota February 2011.
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
SNOMED CT – Distributed Content Management Stefan Schulz Content Committee April 2, 2009.
Knowledge Representation and Indexing Using the Unified Medical Language System Kenneth Baclawski* Joseph “Jay” Cigna* Mieczyslaw M. Kokar* Peter Major.
1 st June 2006 St. George’s University of LondonSlide 1 Using UMLS to map from a Library to a Clinical Classification: Improving the Functionality of a.
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.
LexRDF: A Semantic-Web Compatible Extension of LexGrid Cui Tao Jyotishman Pathak Harold R. Solbrig Wei-Qi Wei Christopher G. Chute Division of Biomedical.
Value Set Resolution: Build generalizable data normalization pipeline using LexEVS infrastructure resources Explore UIMA framework for implementing semantic.
WHO – IHTSDO: SNOMED CT – ICD-11 coordination: Conditions vs. Situations Stefan Schulz IHTSDO conference Copenhagen, Apr 24, 2012.
Coastal Atlas Interoperability - Ontologies (Advanced topics that we did not get to in detail) Luis Bermudez Stephanie Watson Marine Metadata Interoperability.
Terminology Services in the OpenHIE. Agenda Terminology Services Overview Terminology Services in Rwanda Distributed Terminology System (DTS) Next Steps.
Using Several Ontologies for Describing Audio-Visual Documents: A Case Study in the Medical Domain Sunday 29 th of May, 2005 Antoine Isaac 1 & Raphaël.
Sharing Ontologies in the Biomedical Domain Alexa T. McCray National Library of Medicine National Institutes of Health Department of Health & Human Services.
SKOS. Ontologies Metadata –Resources marked-up with descriptions of their content. No good unless everyone speaks the same language; Terminologies –Provide.
A Semantic-Web Representation of Clinical Element Models
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
LexGrid Philosophy, Model and Interfaces Harold R Solbrig Division of Biomedical Statistics and Informatics Mayo Clinic.
A LexWiki-based Representation and Harmonization Framework for caDSR Common Data Elements Guoqian Jiang, Ph.D. Robert Freimuth, Ph.D. Harold Solbrig Mayo.
-KHUSHBOO BAGHADIYA.  Introduction  System Description  iCAT in use  Evolution of the system  Evolution of modeling  Evolution of features  Evolution.
© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Lexically Suggest, Logically Define: QA of Qualifiers &
1 Open Ontology Repository initiative - Planning Meeting - Thu Co-conveners: PeterYim, LeoObrst & MikeDean ref.:
Approach to building ontologies A high-level view Chris Wroe.
Oncologic Pathology in Biomedical Terminologies Challenges for Data Integration Olivier Bodenreider National Library of Medicine Bethesda, Maryland -
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Semantic Media Wiki Open Terminology Development - Initial Steps - Frank Hartel, Ph.D. Associate Director, Enterprise Vocabulary Services National Cancer.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4a Basic Health Data Standards Component 9/Unit.
LexWiki Framework & Use Cases SMW for Distributed Terminology Development Guoqian Jiang, PhD, Harold Solbrig Mayo Clinic Meeting with Dr. Jakob (WHO) May.
ITI Infrastructure - Wednesday November 7th, IHE IT infrastructure “Terminology Sharing” Christel Daniel (AP-HP, INSERM, Paris), Ana Esterlich (GIP-DMP),
Oncology in SNOMED CT NCI Workshop The Role of Ontology in Big Cancer Data Session 3: Cancer big data and the Ontology of Disease Bethesda, Maryland May.
© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.
Canadian SNOMED CT® Extensions Challenges & Lessons learned Presentation to Implementation SIG October 2012 Presented by Linda Parisien and Beverly Knight.
SNOMED CT and Surgical Pathology
The “Common Ontology” between ICD 11 and SNOMED CT
SNOMED CT® in Surgical Pathology and Cancer Registry Work
SNOMED CT E-Learning Status & Planning September Update (for ELRG)
SNOMED CT and Surgical Pathology
Can SNOMED CT be harmonized with an upper-level ontology?
Development of the Amphibian Anatomical Ontology
Kin Wah Fung, MD, MS, MA National Library of Medicine, NIH
LexRDF: An Approach for Representing Biomedical Ontologies in RDF
Presented by Joe Nichols MD Principal – Health Data Consulting
Alan Rector, Luigi Iannone, Robert Stevens
Architecture for ICD 11 and SNOMED CT Harmonization
Terminology and HL7 Dr Colin Price
Guoqian Jiang, Harold R. Solbrig, Christopher G. Chute
Harmonizing SNOMED CT with BioTopLite
Summary Report Project Name: IHTSDO Workbench
Presentation transcript:

A Case Study of ICD-11 Anatomy Value Set Extraction from SNOMED CT Guoqian Jiang, PhD ©2011 MFMER | slide-1 Division of Biomedical Statistics & Informatics, Mayo Clinic College of Medicine ICBO 2011, Buffalo, NY July 29, 2011

Acknowledgements Harold R. Solbrig Mayo Clinic Robert J.G. Chalmers University of Manchester, Manchester, U.K Kent Spackman International Health Terminology Standards Development Organisation, Copenhagen, Denmark Alan L. Rector University of Manchester, Manchester, U.K Christopher G. Chute, MD, Dr.PH Mayo Clinic ©2011 MFMER | slide-2

©2011 MFMER | slide-3 Motivation The 11 th revision of the International Classification of Diseases (ICD) was officially launched by the World Health Organization (WHO) in March The WHO has sought to reuse existing ontologies such as SNOMED CT for value set definition. One of the core value sets being developed is for anatomical site, defined by WHO as “the most specific level of the topographical location or the anatomical structure where the health-related problem can be found relevant to the condition”.

Value Sets A value set is a uniquely identifiable set of valid values that can be resolved at a given point in time to an exact collection of codes. Typically, value sets can be drawn from pre- existing coding schemes such as SNOMED CT by constraining the value selection based on a logical expression (e.g. all sub-codes of the code “breast cancer”). ©2011 MFMER | slide-4

Clinically meaningful value sets Generating clinically meaningful value sets in a (semi-) automatic way from a terminology/ontology service has been challenging for the community. A number of research and standardization efforts HL7 Common Terminology Services II (CTS2) specification, Mayo’s LexEVS 6.0 implementation on a value set definition service, and Manchester’s new OWL API 3 which contains a set of modularization tools. ©2011 MFMER | slide-5

Objectives of the study We perform a case study of ICD-11 anatomy value set extraction from SNOMED CT. We propose four semi-automatic value set extraction strategies based on different clinical context patterns. We evaluate the strategies and discuss their implications in terms of domain coverage, granularity and clinical usefulness from both technical and clinical perspectives ©2011 MFMER | slide-6

ICD-11 Content Model To present the knowledge that underlies the definitions of an ICD entity. For example, we may choose a SNOMED CT concept “ Myocardium structure (body structure)” as the value of the parameter “Body Structure” for the ICD category “Acute myocardial infarction”. ©2011 MFMER | slide-7

SNOMED CT Structure-Entire-Parts (SEP) SEP triples are a means to avoid the use of transitive properties and to make clear which disorders and procedures apply to an entire structure and which to the structure and/or its parts. ©2011 MFMER | slide-8

SNOMED CT Clinical Finding Concept Model ©2011 MFMER | slide-9

Materials The topographical term mappings from SNOMED CT to ICD-O Topography provided by the International Release of SNOMED CT; A subset of SNOMED CT anatomy “base terms” extracted by IHTSDO (to provide familiar names to end users); A subset of all “Clinical Finding” concepts extracted from SNOMED CT stated form in Web Ontology Language (OWL); The entries from a download of the UMLS CORE Problem List Subset of SNOMED CT. ©2011 MFMER | slide-10

Methods We took advantage of a Manchester SNOMED module extraction API and developed an extension as a Protégé 4.1 plugin. In this way, we were able to load the SNOMED CT stated form as an OWL ontology into the Protégé 4.1 platform for module extraction. ©2011 MFMER | slide-11

SNOMED CT Module Extraction Tool as a Protégé 4.1 Plug-in ©2011 MFMER | slide-12

Module Extraction Input (Anatomy/CF) Control BaseTerm ClinicalFinding ProblemList Output (Anatomy) Control BaseTerm ClinicalFinding ProblemList ©2011 MFMER | slide-13 * Control - The topographical term mappings from SNOMED CT to ICD-O

Evaluation Measures (I) Domain coverage 287 ICD-O topographical categories as domain anchors The ratio of the number of categories containing mappings over total number of categories (i.e. the 287 categories). ©2011 MFMER | slide-14

Evaluation Measures (II) Module granularity General granularity simply by the ratio of the number of concept IDs in the module over the number of concept IDs in a control module (i.e. the module of the first pattern). Adjusted granularity by the average ratio of the number of concept IDs in each of 287 categories in a module over that of the control module. ©2011 MFMER | slide-15

Evaluation Measures (III) Clinical usefulness of the module We chose two categories out of the 287 ICD-O categories “C44.3 skin of face” and “C44.5 Skin of trunk” in the dermatology domain. One of the authors (RC, a dermatology physician) reviewed the SNOMED CT mapping concepts to the two categories and marked those that should be considered as part of ICD-11 anatomy concepts. We measured the clinical usefulness by the ratio of the number of concepts checked (by RC’s ratings) over the number of total concepts in the two categories. ©2011 MFMER | slide-16

Results ©2011 MFMER | slide-17 Number of concept IDs in each module and their distribution

Evaluation results of domain coverage and granularity for four modules ©2011 MFMER | slide-18

Evaluation results of clinical usefulness ©2011 MFMER | slide-19 C44.5 Skin of trunk C44.3 Skin of face

Discussion The strategy used for the module ClinicalFinding would be a good starting point for the ICD-11 anatomy use case. The module has good domain coverage while keeping a relatively small size and better outcome on clinical usefulness. ©2011 MFMER | slide-20

Discussion The upper level of the SNOMED CT anatomy may create some confusion because it has three main branches: 1) Anatomical structure, i.e. the normal anatomy, 2) Acquired body structure - mostly the results of surgery plus “scar (morphologic abnormality)”, and 3) Body structure altered from its original anatomic structure (morphologic abnormality) – the results of disease or repair. Given these different types of body structure, the question really is what is needed for ICD-11 development. ©2011 MFMER | slide-21

Discussion The Protégé based OWL module extraction tool we developed in this study has been demonstrated very useful for achieving our goal. While we mainly use an external signature file for module extraction in this study, we have extended the tool and integrated it with the Protégé DL Query plugin, by which a signature can be defined through a semantic query which invokes a DL (description logic)-based reasoner. We consider that this provides a powerful and ease to use feature to define and extract a domain specific value set. ©2011 MFMER | slide-22

In summary We performed a case study for ICD-11 anatomy value set extraction from SNOMED CT. We proposed four different clinical context patterns for the purpose of generating clinically meaningful value sets for ICD-11 anatomy. We evaluated the value sets in terms of domain coverage, granularity and clinical usefulness by defining quantitative measures, which provide effective metrics for helping us to select an approach for satisfying the ICD-11 anatomy use case. ©2011 MFMER | slide-23

©2011 MFMER | slide-24 Questions