The Role of Ontologies for Sustainable, Semantically Interoperable and Trustworthy EHR Solutions Stefan SCHULZ University Medical Center Freiburg, Germany.

Slides:



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

Biomedical Informatics Reference Ontologies in Biomedicine Christopher G. Chute, MD DrPH Professor and Chair, Biomedical Informatics Mayo Clinic College.
The KOS spectra: a tentative typology of Knowledge Organization Systems Renato Rocha Souza Douglas Tudhope Maurício Barcellos Almeida 11 th ISKO International.
Depicting EHRs Immunization capability HL7 WGM – September 11, 2006 Immunization Storyboard project update.
HL7 Version 3 Laboratory Result-based Adverse Event Assessment Message Specifications RCRIM Technical Meeting September 18, 2007 Jennifer Neat Project.
HL7 Templates A means to Manage Complexity. Objectives What is an HL7 Template? What types of constraints can HL7 Templates define? What types of HL7.
Catalogue, synthesise Templates, forms, data sets used in real, diverse health settings Formal representation of clinical business object REQUIREMENTS.
Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
ECO R European Centre for Ontological Research Realist Ontology for Electronic Health Records Dr. Werner Ceusters ECOR: European Centre for Ontological.
Dogac, Kabak, YukselOASIS SET TC Working Document The Use of CCTS in HL7 CDA Asuman Dogac, Yildiray Kabak, Mustafa Yuksel METU, Ankara, Turkey.
Archetypes in HL7 2.x Archetypes/Structure in HL7 Version 2.x Andrew McIntyre Medical-Objects 10 th HL7 Australia Conference,
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4e Basic Health Data Standards Component 9/Unit.
Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.
A Model of eHealth Interoperability Craig Kuziemsky, Telfer School of Mgmt, University of Ottawa. James Williams, Community Care Information Management.
QIDAM Issues and proposals for a logical model For discussion during HL7 WG Meeting in Jan 2014 Thursday Q3.
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
Catherine Hoang Ioana Singureanu Greg Staudenmaier Detailed Clinical Models for Medical Device Domain Analysis Model 1.
Catalina Martínez-Costa, Stefan Schulz: Ontology-based reinterpretation of the SNOMED CT context model Ontology-based reinterpretation of the SNOMED CT.
SNOMED CT’s Ontological Commitment Stefan Schulz University Medical Center, Freiburg, Germany Ronald Cornet Academic Medical Center, Amsterdam, The Netherlands.
Records and situations. Integrating contextual aspects in clinical ontologies Stefan Schulz a,b Daniel Karlsson b a Institute for Medical Informatics,
OASIS Reference Model for Service Oriented Architecture 1.0
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
New ISO projects Joint meeting HL7, IHE and ISO Pharmacy groups Leonora Grandia, Z-Index.
Introduction to the HL7 Terminfo Project IHTSDO Implementation SIG Webinar 5 June, 2012 Robert Hausam, MD.
3/18/19990© 1999, Health Level Seven, Inc. Introduction: Vocabulary domains Marital Status –single (never married) –married –divorced –separated “Vocabulary”
Implementation and Use of ICPS in Health Information Systems (HIS) Stefan Schulz Freiburg University Medical Center, Germany.
Developing an OWL-DL Ontology for Research and Care of Intracranial Aneurysms – Challenges and Limitations Holger Stenzhorn, Martin Boeker, Stefan Schulz,
The EHR-S FIM project plans to harmonize the EHR-S FM R2
1 Federal Health IT Ontology Project (HITOP) Group The Vision Toward Testing Ontology Tools in High Priority Health IT Applications October 5, 2005.
Of 39 lecture 2: ontology - basics. of 39 ontology a branch of metaphysics relating to the nature and relations of being a particular theory about the.
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.
Presentation copyright - The Clinical Information Consultancy ( SNOMED Clinical Terms is a copyright work of the College of American.
SNOMED CT – Distributed Content Management Stefan Schulz Content Committee April 2, 2009.
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
Terminology and HL7 Dr Colin Price HL7 UK 11 th December 2003.
Tommie Curtis SAIC January 17, 2000 Open Forum on Metadata Registries Santa Fe, NM SDC JE-2023.
Clinical Document Architecture. Outline History Introduction Levels Level One Structures.
1 HL7 RIM Barry Smith
Briefing: HL7 Working Group Meeting Update for the VCDE Community Dianne M. Reeves Associate Director, Biomedical Data Standards NCI CBIIT VCDE Meeting.
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 Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
A School of Information Science, Federal University of Minas Gerais, Brazil b Medical University of Graz, Austria, c University Medical Center Freiburg,
The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany.
The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany.
Common Terminology Services 2 CTS 2 Submission Team Status Update HL7 Vocabulary Working Group May 17, 2011.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Commentary: The HL7 Reference Information Model as the Basis for Interoperability George W. Beeler, Jr. Ph.D. Co-Chair, HL7 Modeling & Methodology.
SNOMED Core Structures NAHLN January 2005 Las Vegas, NV.
Ballot Reconciliation Meeting Notes 1.Ballot Tally & Reconciliation a.CTLaboratory Release 3 / HL7 Version 3 Standard: Periodic Reporting of Clinical Trial.
ABRA Week 3 research design, methods… SS. Research Design and Method.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4a Basic Health Data Standards Component 9/Unit.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Knowledge Representation Part I Ontology Jan Pettersen Nytun Knowledge Representation Part I, JPN, UiA1.
Assessing SNOMED CT for Large Scale eHealth Deployments in the EU Workpackage 2- Building new Evidence Daniel Karlsson, Linköping University Stefan Schulz,
UNIFIED MEDICAL LANGUAGE SYSTEMS (UMLS)
The “Common Ontology” between ICD 11 and SNOMED CT
W. Scott Campbell, MBA, PhD James R. Campbell, MD
Stefan Schulz Medical Informatics Research Group
Achieving Semantic Interoperability of Cancer Registries
Care plan content February 2015 presented by Zac Whitewood-Moores.
Federal Health IT Ontology Project (HITOP) Group
Secondary Uses Primary Use EHR and other Auhortities Clinical Trial
Networking and Health Information Exchange
Harmonizing SNOMED CT with BioTopLite
Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany
Presentation transcript:

The Role of Ontologies for Sustainable, Semantically Interoperable and Trustworthy EHR Solutions Stefan SCHULZ University Medical Center Freiburg, Germany Edward CHEETHAM NHS Connecting for Health, United Kingdom TermInfo Draft Standard for Trial Use (DSTU): Managing overlap between SNOMED CT and HL7-RIM

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

Two Health Information Standards Standards Typology Overlap TermInfo Outlook

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

From metaphysics… theory of realitytheory of meaning of (human language) designations theory of knowledge OntologySemantics Epistemology bla bla bla Standards Typology Overlap TermInfo Outlook

…to an ideal world of representation artifacts theories that attempt to give precise mathematical formulations of the properties and relations of certain entities. (Stanford Encyclopedia of Philosophy) Set of terms representing the system of concepts of a particular subject field. (ISO 1087) artefacts in which information is recorded A. Rector, SemanticHealth D6.1 OntologiesTerminologies Data models / Information models Standards Typology Overlap TermInfo Outlook

Examples Formal descriptions MRSA subtype-of SA SA subtype-of Staphylococcus SA implies bearer-of some MR quality Textual descriptions “MRSA is defined as SA for which methicillin has no toxic effect” Concept 1 – Synonyms: -SA -Staphylococcus aureus -Staph. aur. -Concept 2 – Synonyms: -MRSA -Methicillin-resistant SA -Methicillin-resistant Staphylococcus Aureus Methicillin resistance OntologiesTerminologies Data models / Information models  Clinically confirmed  Confirmed by antibiogram  Suspected  None  Unknown Standards Typology Overlap TermInfo Outlook

but in the real, chaotic world… Standards Typology Overlap TermInfo Outlook

we have to deal with “living” representational artifacts far from being ideal TerminologyOntology Information models Standards Typology Overlap TermInfo Outlook

that combine teminology, ontology and information model elements TerminologyOntology Information models MeSH SNOMED CT HL7 RIM ICD 10 Standards Typology Overlap TermInfo Outlook

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

Problem: Semantic Overlap Terminologies / Ontologies stray the terrain of information models Information models stray the terrain of Terminologies / Ontologies Historically: solution developers tended to work with a single representation standard Multiple approaches to encode the same information Risk of arbitrary design decisions when used together Lack of clarity with regard to satisfying unmet representational need Standards Typology Overlap TermInfo Outlook

Examples of “epistemic intrusion” SNOMED CT: “Suspected autism” SNOMED CT: “Biopsy planned” SNOMED CT: “Take at regular intervals” ICD 10: “Tuberculosis of lung, confirmed histologically” ICD-O: “Basal cell tumor, uncertain whether benign or” malignant ICD-9-CM: “Replacement of unspecified heart valve” NCI Thesaurus: “Unknown If Ever Smoked” NCI Thesaurus: “Absent Adverse Event” Bodenreider et al. The Ontology-Epistemology Divide: A Case Study in Medical Terminology. Proceedings of FOIS 2004 Standards Typology Overlap TermInfo Outlook

Solutions Establish a clear boundary between information models and ontologies: desirable but unfeasible for legacy systems Develop rules for managing ambiguities –HL7 TermInfo * Standards Typology Overlap TermInfo Outlook

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

TermInfo Draft Standard for Trial Use (DSTU): History 2004 onwards, Growing interest in use of SNOMED Clinical Terms (SNOMED CT) in the HL7 community HL7 Vocabulary Technical Committee (supported by SNOMED International and NASA) launched the 'TermInfo Project’ with the following missions: –General: investigate interfacing between HL7 information models and terminologies or code systems. –Specific: A guide on use of SNOMED CT within the HL7 V3 Outcome September 2007: –Guide to Use of SNOMED CT in HL7 Version 3‘ accepted as a Draft Standard for Trial Use (DSTU) Standards Typology Overlap TermInfo Outlook

Using SNOMED CT in HL7 v3 DSTU Standards Typology Overlap TermInfo Outlook

Structure of SNOMED CT in HL7 v3 DSTU 1.Introduction and Scope 2.Guidance on Overlaps between RIM and SNOMED CT Semantics 3.Common Patterns 4.Normal Forms 5.SNOMED CT vocabulary domain constraints 6.Glossary Appendix A General Options for Dealing with Potential Overlaps Appendix B References Appendix C Revision changes Appendix D SNOMED CT Open Issues Appendix E Detailed aspects of issues with a vocabulary specification formalism Standards Typology Overlap TermInfo Outlook

Section 2: Guidance on overlaps between RIM and SNOMED CT Semantics Detailed walk-through of RIM attributes vs. SNOMED CT properties: –Act.classCode –Act.code and Observation.value –Act.moodCode –Act.statusCode –Procedure.targetSiteCode and Observation.targetSiteCode –Procedure.approachSiteCode and SubstanceAdministration.approachSiteCode –Procedure.methodCode and Observation.methodCode –Act.priorityCode –Act.negationInd –Act.uncertaintyCode –Representation of Units –Dates and Times Standards Typology Overlap TermInfo Outlook

HL7 moodCode  SNOMED CT finding and procedure context HL7 methodCode  SNOMED CT finding and procedure methods And so on... Standards Typology Overlap TermInfo Outlook

1.Potential overlap 2.Rules and guidance 3.Rationale Using SNOMED CT in HL7 v3 DSTU Guidance on overlaps between RIM and SNOMED CT Semantics Each subsection in HL7 v3 DSTU Section 2: divided into: Two examples Standards Typology Overlap TermInfo Outlook

Potential Overlap: –Complete overlap HL-7 targetSiteCodes are defined as “the anatomical site or system that is the focus of the procedure / observation.” SNOMED CT finding and procedure concepts have a defining attribute that specifies the site: e.g. Appendicitis – Finding Site – Appendix structure Rules and Guidance –omit targetSiteCode attribute from: any Act class clone in which SNOMED CT is the only permitted code system for the Act.code attribute. any Observation class clone in which SNOMED CT is the only permitted code system for the Observation.value attribute...’ Rationale –Argues case for SNOMED CT attribute preference –Precision of available attributes; relationship grouping –The site of an action or event is clearly of ontological nature Example 1: Procedure.targetSiteCode and Observation.targetSiteCode Standards Typology Overlap TermInfo Outlook

Potential overlap –The values in ActMood vocabulary partially overlap with SNOMED CT representations of Finding context and Procedure context Finding context relevant to instances of HL7 Observation classes expressed in "event", "goal", "expectation" and "risk" moods. Procedure context relevant to (i) instances of various HL7 Act classes including Procedure, SubstanceAdministration and Supply, (ii) instances of the HL7 Observation class except in "intent" moods (including "request" and other subtype of "intent"). Rules and guidance –The moodCode SHALL be present in all Act class instances –Rules for valied moodCode / SNOMED CT associations: ‘...IF moodCode <>INT (or subtype), THEN code attribute of Observation class MAY be populated by the following SNOMED CT expression patterns...’ –Defaults described by default correspondence tables –Allowable patterns described by constraint tables –‘If both are present then they must be kept in step Example 2: Act.MoodCode Standards Typology Overlap TermInfo Outlook

Mood Code = SNOMED CT context default and constraint tables moodCodeMood NameSNOMED CT Finding context EVNEvent[ | known present ] GOLGoal[ | goal ] RSKRisk[ | at risk ] EXPECExpectation[ | expectation ] moodCodeMood nameSNOMED CT Finding context EVNEvent [(<< | known |) OR (<< | unknown |)] GOLGoal [ << | goal ] RSKRisk [ << | at risk ] EXPECExpectation [ << | expectation ] Finding default Finding constraints Example 2: Act.MoodCode Standards Typology Overlap TermInfo Outlook

Outline Health information standards Typology of representation artifacts Semantic overlap between representation artifacts TermInfo Draft Standard for Trial Use Outlook Standards Typology Overlap TermInfo Outlook

Next Steps - DSTU Encourage use and testing –Marketing effort Encourage and support submission and timely resolution of issues encountered in use –HL7 DSTU issue reporting mechanism (pending re-publication) –HL7 Project Homebase mechanism Encourage list membership and submission of issues –Conference call debate and resolution –Establish close ties with e.g. IHTSDO expertise for timely resolution/interim suggestions –Advancement through IHTSDO standards approval processes Standards Typology Overlap TermInfo Outlook

Conclusion The ontology / epistemology boundary is crossed by both standards SNOMED CT and HL7v3. Consequence: overlap ! DSTU produced to assist in the co-implementation of SNOMED CT and HL7v3 Provides guidance on: Provides mechanism for issues resolution and gap management where both standards used Does not claim perfection and does need systematic testing Recommendation: decrease of SNOMED CT / HL7v3 overlaps by collaborative development of both standards, assigning representational responsibility based on reproducible boundary rules –informed by ontological/epistemological considerations, balanced with consideration of real-world practical considerations. Standards Typology Overlap TermInfo Outlook –Representation overlap management –Sensible integration of the standards