SNOMED CT – Distributed Content Management Stefan Schulz Content Committee April 2, 2009.

Slides:



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

TU/e technische universiteit eindhoven Hera: Development of Semantic Web Information Systems Geert-Jan Houben Peter Barna Flavius Frasincar Richard Vdovjak.
SNOMED Core Structures 2 nd AAHA Software Vendors Summit – April 21, 2009.
 Implementing terminology requires supporting tools  Tools required are highly dependant on the type of implementation  Covered in this presentation.
Catalina Martínez-Costa, Stefan Schulz: Ontology-based reinterpretation of the SNOMED CT context model Ontology-based reinterpretation of the SNOMED CT.
Copyright Irwin/McGraw-Hill Data Modeling Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley.
System Analysis - Data Modeling
Implementing a Clinical Terminology David Crook Subset Development Project Manager SNOMED in Structured electronic Records Programme NHS Connecting for.
Domain Modelling the upper levels of the eframework Yvonne Howard Hilary Dexter David Millard Learning Societies LabDistributed Learning, University of.
1 Definitions Value set: A list of specific values, which may – or may not – contain subsets of one or more standard vocabularies, that define or identify:
Development Principles PHIN advances the use of standard vocabularies by working with Standards Development Organizations to ensure that public health.
The IHTSDO Workbench A Terminology Management Tool John Gutai, IHTSDO May 2011 For OHT.
Veterinary Terminology Services Lab Va-Md Regional College of Veterinary Medicine The Animal Names Terminology Subset of SNOMED CT ® Suzanne L. Santamaria,
SC32 WG2 Metadata Standards Tutorial Metadata Registries and Big Data WG2 N1945 June 9, 2014 Beijing, China.
Karen Gibson.  Significant investment in eHealth is underway  Clinical records: ◦ Not only a record for the author ◦ Essential to inform the next person.
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
Working Together to Advance Terminology Tooling Presentation to OHT Board, Birmingham Jennifer Zelmer & Karen Gibson.
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,
Spoken dialog for e-learning supported by domain ontologies Dario Bianchi, Monica Mordonini and Agostino Poggi Dipartimento di Ingegneria dell’Informazione.
Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.
A School of Information Science, Federal University of Minas Gerais, Brazil b Medical University of Graz, Austria, c University Medical Center Freiburg,
WHO – IHTSDO: SNOMED CT – ICD-11 coordination: Conditions vs. Situations Stefan Schulz IHTSDO conference Copenhagen, Apr 24, 2012.
A Context Model based on Ontological Languages: a Proposal for Information Visualization School of Informatics Castilla-La Mancha University Ramón Hervás.
Ontological Analysis, Ontological Commitment, and Epistemic Contexts Stefan Schulz WHO – IHTSDO Joint Advisory Group First Face-to-Face Meeting Heathrow,
The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
SKOS. Ontologies Metadata –Resources marked-up with descriptions of their content. No good unless everyone speaks the same language; Terminologies –Provide.
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
Appraisal of Guidelines for Research & Evaluation Using the AGREE¹ Instrument CAN-IMPLEMENT Toolkit Version 1.0 April 2010 Modified from:
HIT Standards Committee Vocabulary Task Force Task Force Report and Recommendation Jamie Ferguson Kaiser Permanente Betsy Humphreys National Library of.
Ontology Evaluation, Metrics, and Metadata in NCBO BioPortal Natasha Noy Stanford University.
SNOMED Core Structures NAHLN January 2005 Las Vegas, NV.
Detection of underspecifications in SNOMED CT concept definitions using language processing 1 Federal Technical University of Paraná (UTFPR), Curitiba,
ISO TC 37/CLARIN DISCUSSION UTRECHT, DECEMBER 9/ Thinning Down a Bloated Cat SUE ELLEN WRIGHT DECEMBER 2013.
SNOMED CT A Technologist’s Perspective Gaur Sunder Principal Technical Officer & Incharge, National Release Center VC&BA, C-DAC, Pune.
Nursing Occupations Proposed by: Cynthia Lundberg, BSN Judith Warren, PhD, RN.
Post-coordination Implementation Challenges Project IHTSDO Conference October 2010 Jay Kola.
1 Developing an Ontology of Ontologies for OOR Ontology Summit 2008 April 28-29, 2008 Michael Gruninger and Pat Hayes.
Reinventing research and education Linköping University Mikael Nyström Department of Biomedical Engineering, Linköping University SNOMED CT Implementation.
Mapping International Classification for Nursing Practice (ICNP) and SNOMED CT Submitted by the ICNP Programme Team to IHTSDO Nursing Special Interest.
1 Alberta Health Services Capital Health Palliative Care Program Clinical Vocabulary Pilot Project Project Update Friday April 24, 2009 Dennis Lee & Francis.
Essential SNOMED. Simplifying S-CT. Supporting integration with health
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.
Canadian SNOMED CT® Extensions Challenges & Lessons learned Presentation to Implementation SIG October 2012 Presented by Linda Parisien and Beverly Knight.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Assessing SNOMED CT for Large Scale eHealth Deployments in the EU Workpackage 2- Building new Evidence Daniel Karlsson, Linköping University Stefan Schulz,
SNOMED Core Structures RF2
SNOMED CT and Surgical Pathology
Business System Development
Types and Characteristics of Requirements
The UMLS and the Semantic Web
Representation of Hypersensitivity, Allergy and adverse reactions in SNOMED CT Bruce Goldberg, MD, PhD.
The “Common Ontology” between ICD 11 and SNOMED CT
Using language technology for SNOMED CT localization
Stefan Schulz Medical Informatics Research Group
SNOMED CT Logic Profile Enhancement Yongsheng Gao, 2017/07/11
(existing FSN – hierarchy designator omitted) (proposed term)
SNOMED CT E-Learning Status & Planning September Update (for ELRG)
SNOMED CT and Surgical Pathology
The Role of Ontologies for Mapping the Domain of Landscape Architecture An introduction.
Can SNOMED CT be harmonized with an upper-level ontology?
February 17, 2017 Bruce Goldberg, MD, PhD
MedDRA and Ontology Discussion of Strategy
The Re3gistry software and the INSPIRE Registry
Architecture for ICD 11 and SNOMED CT Harmonization
Terminology and HL7 Dr Colin Price
A bit more about Read Codes and SNOMED CT
Lexical ambiguity in SNOMED CT
Model ID: Model to represent entire statement including context
Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany
Presentation transcript:

SNOMED CT – Distributed Content Management Stefan Schulz Content Committee April 2, 2009

Problem statement SNOMED CT’s size: barrier for effective content management and redesign Any action on SNOMED as a whole is a major undertaking Only a small fraction of this material has ever been used Concentration on quality-assured subset recommended Alan Rector (2008): Semantic Interoperability Deployment and Research Roadmap

SNOMED CT: Ontology + Vocabulary SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) SNOMED CT

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Natural primitives constituting the conceptual “atoms” of the domain. entire esophagussarcomaL-carnitineIntensive care unitStenosis

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Extended Core (EC) Natural primitives constituting the conceptual “atoms” of the domain. Clinically relevant frequent concepts that are (could be) expressed by full definitions esophagitisesophageal neoplasmentire left upper extremitySevere asthma

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Extended Core (EC) Authoritative Concepts (AC) Natural primitives constituting the conceptual “atoms” of the domain. Clinically relevant frequent concepts that are (could be) expressed by full definitions Primitive Concepts for which a SNOMED CT independent, authoritative source exists prednisolone 50 mg tabletL-Carnitine productnurse – RAFGeorgia stateLeishmania donovani

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Extended Core (EC) Authoritative Concepts (AC) Precoordinated Concepts (PC) Natural primitives constituting the conceptual “atoms” of the domain. Clinically relevant frequent concepts that are (could be) expressed by full definitions Primitive Concepts for which a SNOMED CT independent, authoritative source exists Fully defined but idiosyncratic concepts Abrasion AND/OR friction burn of ear with infection,Injection of triamnicolone into nail bed,Deep third degree burn of forehead AND/OR cheek with loss of body part

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Extended Core (EC) Authoritative Concepts (AC) Precoordinated Concepts (PC) Contextual Concepts (CC) Natural primitives constituting the conceptual “atoms” of the domain. Clinically relevant frequent concepts that are (could be) expressed by full definitions Primitive Concepts for which a SNOMED CT independent, authoritative source exists Fully defined but idiosyncratic concepts Concepts, fully defined or not, that describe a clinical situation, belief state or database entry implementation of planned interventionsTake at regular intervals. Complete the prescribed course unless otherwise directedNo antenatal care: not known pregnantPrevious known suicide attempt

SNOMED CT Ontology SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) Basic Core (BC) Extended Core (EC) Authoritative Concepts (AC) Precoordinated Concepts (PC) Contextual Concepts (CC) Natural primitives constituting the conceptual “atoms” of the domain. Clinically relevant frequent concepts that are (could be) expressed by full definitions Primitive Concepts for which a SNOMED CT independent, authoritative source exists Fully defined but idiosyncratic concepts Concepts, fully defined or not, that describe a clinical situation, belief state or database entry   

SNOMED CT: Ontology + Vocabulary SNOMED – CT Ontology (concepts, relations) SNOMED – CT Vocabulary (descriptions) SNOMED CT

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) FSN Fully Specified Name ”malignant tumor of esophagus (disorder)”

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) FSN Fully Specified Name PT Preferred Term ”malignant tumor of esophagus”

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT FSN Real Synonym Fully Specified Name RS PT Preferred Term “esophageal carcinoma”

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT NS: term with a broader meaning, but in many contexts used as synonym to the related FSN FSN Real Synonym Fully Specified Name RS Near Synonym NS PT Preferred Term “foot” (body part vs. length unit),“fundus” for “uterine fundus”“appendectomy” for „open appendectomy“

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) FSN Real Synonym Fully Specified Name RS Text Definition Near Synonym NS TDPT Preferred Term FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT NS: term with a broader meaning, but in many contexts used as synonym to the related FSN TD: Glossary-like definition that refines the description given by the Fully Specified Name. “Intertrigo (disorder) - Superficial dermatitis on opposed skin surfaces”

SNOMED CT: Vocabulary SNOMED – CT Vocabulary (descriptions) FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT NS: term with a broader meaning, but in many contexts used as synonym to the related FSN TD: Glossary-like definition that refines the description given by the Fully Specified Name. FSN Real Synonym Fully Specified Name RS Near Synonym NS TDPT Preferred Term Text Definition

SNOMED CT: Vocabulary * Ontology SNOMED – CT Vocabulary (descriptions) FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT NS: term with a broader meaning, but in many contexts used as synonym to the related FSN TD: Glossary-like definition that refines the description given by the Fully Specified Name. BC: Natural primitives constituting the conceptual “atoms” of the domain. EC: Clinically relevant frequent concepts that are (could be) expressed by full definitions AC: Primitive Concepts for which a SNOMED CT independent, authoritative source exists PC: Fully defined but idiosyncratic concepts CC: Concepts, fully defined or not, that describe a clinical situation, belief state or database entry SNOMED Ontology (concepts, relations)

FSN: Unambiguous, largely self-explaining unique term (with hierarchy tag) PT: Unambiguous, largely self-explaining unique term (without hierarchy tag) RS: Carries the same meaning as the corresponding FSN or PT NS: term with a broader meaning, but in many contexts used as synonym to the related FSN TD: Glossary-like definition that refines the description given by the Fully Specified Name. BC: Natural primitives constituting the conceptual “atoms” of the domain. EC: Clinically relevant frequent concepts that are (could be) expressed by full definitions AC: Primitive Concepts for which a SNOMED CT independent, authoritative source exists PC: Fully defined but idiosyncratic concepts CC: Concepts, fully defined or not, that describe a clinical situation, belief state or database entry SNOMED CT: Language Dimension SNOMED – CT Vocabulary (descriptions) SNOMED Ontology (concepts, relations)

Stakeholders and Roles SNOMED CT Ontology Terms IHTSDO National Release Centers Affiliates User Groups Other SDOs maintain propose assure quality audit propose translate

Possible Distributed Management … propose maintain propose maintain propose maintain User groups provide names, meaning, and IDs External authoritative sources audit (others) translate (?) main- tain (others) main- tain (others) main- tain (other) propose maintain propose maintain translatequality assess- ment National Release Centers audit (english) fully main- tain fully main- tain (english) fully main- tain (english) fully main- tain (english) audit quality assess- ment audit quality assess- ment define sources, manage IDs fully main- tain IHTSDO NSTDRSPTFSNCCPCACECBC SNOMED CT descriptionsSNOMED CT Concepts Consequences: “outsourcing” of many pre-coordinated concepts and synonyms: under the responsibility of user groups. IHTSDO’s role: audit and quality assurance. IHTSDO mostly concentrates on BC and EC Use of IDs from external namespaces

Example 1 Now: –user proposes a new concept C –IHTSDO processes request –IHTSDO finds concept definition –IHTSDO includes C into new SNOMED release Future –user proposes a new concept C –user uploads to common repository –users discuss suitable definition –IHTSDO approves FSN and formal definition –IHTSDO decides whether to leave in repository or include in terminology

Example 2 Now: –National Release Center translates concept C Future –user proposes a translation to concept C –user uploads proposal to common repository –users discuss –National Release Center approves translation

Open issues tooling management of identifiers, namespaces etc. intellectual property issues workflows quality control referential integrity …