The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany.

Slides:



Advertisements
Similar presentations
WHO Agenda: Classifications – Terminologies - Standards
Advertisements

The Role of Ontologies for Sustainable, Semantically Interoperable and Trustworthy EHR Solutions Stefan SCHULZ University Medical Center Freiburg, Germany.
Knowledge Representation
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,
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
What is an Ontology? AmphibiaTree 2006 Workshop Saturday 8:45–9:15 A. Maglia.
The Enhanced Entity- Relationship (EER) Model
HL7 RIM Exegesis and Critique Regenstrief Institute, November 8, 2005 Barry Smith Director National Center for Ontological Research.
DAML+OIL Ontology Tutorial Chris Wroe, Robert Stevens (Sean Bechhofer, Carole Goble, Alan Rector, Ian Horrocks….) University of Manchester.
Semantic Web Technologies Lecture # 2 Faculty of Computer Science, IBA.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1 EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling concepts.
Implementation and Use of ICPS in Health Information Systems (HIS) Stefan Schulz Freiburg University Medical Center, Germany.
Ontology-based Convergence of Medical Terminologies: SNOMED CT and ICD-11 Institute for Medical Informatics, Statistics and Documentation, Medical University.
Ontology Development Kenneth Baclawski Northeastern University Harvard Medical School.
Developing an OWL-DL Ontology for Research and Care of Intracranial Aneurysms – Challenges and Limitations Holger Stenzhorn, Martin Boeker, Stefan Schulz,
GEM/IRDR Social Vulnerability and Resilience Information System and Metadata Portal IRDR Scientific Board Meeting Chengdu 03/11/2012.
The Foundational Model of Anatomy and its Ontological Commitment(s) Stefan Schulz University Medical Center, Freiburg, Germany FMA in OWL meeting November.
Protege OWL Plugin Short Tutorial. OWL Usage The world wide web is a natural application area of ontologies, because ontologies could be used to describe.
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.
INF 384 C, Spring 2009 Ontologies Knowledge representation to support computer reasoning.
The ICPS process: Typology of a novel terminological system Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany Daniel KARLSSON Department.
Nancy Lawler U.S. Department of Defense ISO/IEC Part 2: Classification Schemes Metadata Registries — Part 2: Classification Schemes The revision.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
ISURF -An Interoperability Service Utility for Collaborative Supply Chain Planning across Multiple Domains Prof. Dr. Asuman Dogac METU-SRDC Turkey METU.
Metadata. Generally speaking, metadata are data and information that describe and model data and information For example, a database schema is the metadata.
The International Classification for Patient Safety: an overview In collaboration with WHO Classifications, Standards and Terminology March 2011.
Definition of a taxonomy “System for naming and organizing things into groups that share similar characteristics” Taxonomy Architectures Applications.
Ontology Summit2007 Survey Response Analysis Ken Baclawski Northeastern University.
LOGIC AND ONTOLOGY Both logic and ontology are important areas of philosophy covering large, diverse, and active research projects. These two areas overlap.
Terminology and documentation*  Object of the study of terminology:  analysis and description of the units representing specialized knowledge in specialized.
WHO – IHTSDO: SNOMED CT – ICD-11 coordination: Conditions vs. Situations Stefan Schulz IHTSDO conference Copenhagen, Apr 24, 2012.
Taken from Schulze-Kremer Steffen Ontologies - What, why and how? Cartic Ramakrishnan LSDIS lab University of Georgia.
Logics for Data and Knowledge Representation Applications of ClassL: Lightweight Ontologies.
Database Systems: Enhanced Entity-Relationship Modeling Dr. Taysir Hassan Abdel Hamid.
The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany.
Logics for Data and Knowledge Representation
Proposed NWI KIF/CG --> Common Logic Standard A working group was recently formed from the KIF working group. John Sowa is the only CG representative so.
Sharing Ontologies in the Biomedical Domain Alexa T. McCray National Library of Medicine National Institutes of Health Department of Health & Human Services.
Metadata Common Vocabulary a journey from a glossary to an ontology of statistical metadata, and back Sérgio Bacelar
The RDF meta model Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations of XML compared.
A modular metadata-driven statistical production system The case of price index production system at Statistics Finland Pekka Mäkelä, Mika Sirviö.
Knowledge Representation. Keywordsquick way for agents to locate potentially useful information Thesaurimore structured approach than keywords, arranging.
An Ontology-based Approach to Context Modeling and Reasoning in Pervasive Computing Dejene Ejigu, Marian Scuturici, Lionel Brunie Laboratoire INSA de Lyon,
Building a Hospital Incident Reporting Ontology (HIRO) in the Web Ontology Language (OWL) using the JCAHO Patient Safety Event Taxonomy (PSET) presented.
Enable Semantic Interoperability for Decision Support and Risk Management Presented by Dr. David Li Key Contributors: Dr. Ruixin Yang and Dr. John Qu.
Using OWL 2 For Product Modeling David Leal Caesar Systems April 2009 Henson Graves Lockheed Martin Aeronautics.
Semantic Interoperability in GIS N. L. Sarda Suman Somavarapu.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Ontology in Model-Based Systems Engineering Henson Graves 29 January 2011.
Of 24 lecture 11: ontology – mediation, merging & aligning.
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 Enhanced Entity- Relationship (EER) Model
The “Common Ontology” between ICD 11 and SNOMED CT
Conceptual Design & ERD Modelling
Stefan Schulz Medical Informatics Research Group
NeurOn: Modeling Ontology for Neurosurgery
Semantic Web Foundations
Using OWL for the RESO Data Dictionary
ece 627 intelligent web: ontology and beyond
Ontology From Wikipedia, the free encyclopedia
Architecture for ICD 11 and SNOMED CT Harmonization
Harmonizing SNOMED CT with BioTopLite
Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany
Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany
IDEAS Core Model Concept
When the Swiss cheese aligns - Making a clinical error
Presentation transcript:

The ICPS: A taxonomy, a classification, an ontology or an information model? Stefan SCHULZ IMBI, University Medical Center, Freiburg, Germany

Representation Artifacts theory of reality theory of knowledge Ontology Ontologies Epistemology Information Models Standards Typology Overlap TermInfo Outlook artifacts in which information is recorded A. Rector, SemanticHealth D6.1 theories that attempt to give precise mathematical formulations of the properties and relations of certain entities. (Stanford Encyclopedia of Philosophy)

Representation Artifacts Ontologies Information Models Standards Typology Overlap TermInfo Outlook artifacts in which information is recorded A. Rector, SemanticHealth D6.1 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”  Clinically confirmed  Confirmed by antibiogram  Suspected  None  Unknown Methicillin resistance theories that attempt to give precise mathematical formulations of the properties and relations of certain entities. (Stanford Encyclopedia of Philosophy)

Representation Artifacts Ontologies Information Models Standards Typology Overlap TermInfo Outlook artifacts in which information is recorded A. Rector, SemanticHealth D6.1 Formal descriptions MRSA subclass-of SA SA subclass-of Staphylococcus SA implies bearer-of some MR quality Textual descriptions “MRSA is defined as SA for which methicillin has no toxic effect”  Clinically confirmed  Confirmed by antibiogram  Suspected  None  Unknown Methicillin resistance Taxonomies Backbone of Ontologies SubClass or is-a relation: a class B is a subclass of a class A if and only if all members of B are also members of A (ENV 12264:2005, Horrocks 2003)

Taxonomy building principles Individuals (particulars, instances) Standards Typology Overlap TermInfo Outlook

Taxonomy building principles Individuals (particulars, instances) Class Standards Typology Overlap TermInfo Outlook

Taxonomy building principles Individuals (particulars, instances) Class Subclasses Standards Typology Overlap TermInfo Outlook

Taxonomy building principles Individuals (particulars, instances) Class Subclasses is-a or subclass relation (relating classes with classes): corresponds to subset relation instance-of relation (relating individuals with classes) corresponds to set membership relation Standards Typology Overlap TermInfo Outlook

Representation Artifacts Ontologies Information Models Standards Typology Overlap TermInfo Outlook artifacts in which information is recorded A. Rector, SemanticHealth D6.1 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”  Clinically confirmed  Confirmed by antibiogram  Suspected  None  Unknown Methicillin resistance Taxonomies Backbone of Ontologies SubClass or is-a relation: a class B is a subclass of a class A if and only if all members of B are also members of A (ENV 12264:2005, Horrocks 2003) Classifications Taxonomies with additional building principles: - exhaustiveness - disjointness

Classifications: Disjointness principle Classifications, e.g. ICDOther Terminologies, e.g. SNOMED CT

Representation Artifacts Ontologies Information Models Standards Typology Overlap TermInfo Outlook Taxonomies Classifications ICPS ?

Three components of ICPS 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” ICPS "taxonomy" ICPS Architecture Critique Typology Outlook

Three components of ICPS 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” ICPS Architecture Critique Typology Outlook ICPS "taxonomy"

ICPS Components 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” Incident Characteristics ICPS Architecture Critique Typology Outlook ICPS "taxonomy"

ICPS Conceptual Framework 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” ICPS Architecture Critique Typology Outlook ICPS "taxonomy"

Analyzing ICPS ICPS Architecture Critique Typology Outlook target of analysis: the ICPS tree… –graph structure: resemblance with WHO-FIC classifications (4 – 5 levels, single parents) –artifact meant to be used by coders key concepts and conceptual framework: meta information from user’s point of view 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient.

ICPS is in a strict sense not… … a taxonomy (ENV 12264:2005, Cornet 2006) Semantic nature of hierarchic links are not specified Subclass or is-a relation: a class B is a subclass of a class A if and only if all members of B are also members of A (ENV 12264:2005, Horrocks 2003) ICPS Architecture Critique Typology Outlook A member of the class Person Reporting is not a member of the class Discovery of Incident: No taxonomic link! But For every member of the class Discovery of Incident” there is some member of the class Person Reporting as a participant: non-taxonomic, ontological relation A member of the class Country is not a member of the class Where and no member of Discovery of Incident. No taxonomic link! But: for every member of the class Discovery of Incident” there is some member of the class Country as a location: non-taxonomic, ontological relation

ICPS is not yet… … a classification (ISO 17115:2007, Ingenerf MIM 1998, Madden [WHO-FIC] 2007) Criterion of mutually disjoint, exhaustive classes not fulfilled more than hundred ICPS concepts occur more than once in different hierarchies –Healthcare Professional occurs both as a child of People Involved and Person Reporting ICPS Architecture Critique Typology Outlook

ICPS: What it is now 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” ICPS Architecture Critique Typology Outlook ICPS "taxonomy"

ICPS: What it is now 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Concepts by Class” “Conceptual Framework” “Key Concepts” This is a rudimentary, informal ontology describes terms by their generic properties close to upper-level ontologies (e.g. BioTop): “state”, “substance”, “event”, “agent”, “object”, “action”, “quality”. ICPS Architecture Critique Typology Outlook

ICPS: What it is now 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” ICPS Architecture Critique Typology Outlook ICPS "taxonomy" This is a complex patient safety model Similarity with - workflows - business models -Ontologically: - complex event type

ICPS: What it is now 9.Hazard: a circumstance, agent or action with the potential to cause harm. 10.Circumstance: a situation or factor that may influence an event, agent or person(s). 11.Event: something that happens to or involves a patient. 12.Agent: a substance, object or system which acts to produce change. 13.Patient Safety: the reduction of risk of unnecessary harm associated with healthcare to an acceptable minimum. 14.Healthcare-associated harm: harm arising from or associated with plans or actions taken during the provision of healthcare, rather than an underlying disease or injury. 15.Patient safety incident: an event or circumstance which could have resulted, or did result, in unnecessary harm to a patient. “Conceptual Framework” “Key Concepts” This is a structured data acquisition template consisting of (mostly) binary fields Can be described as information model Hierarchical parents provide context information for fields (but are not superclasses) It is not meant to arrange classes of entities by their inherent properties (ontology), but gives a framework for acquiring what a reporting person knows (information model) ICPS Architecture Critique Typology Outlook ICPS "taxonomy"

Representation Artifacts Ontologies Information Models Standards Typology Overlap TermInfo Outlook artifacts in which information is recorded A. Rector, SemanticHealth D6.1 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”  Clinically confirmed  Confirmed by antibiogram  Suspected  None  Unknown Methicillin resistance theories that attempt to give precise mathematical formulations of the properties and relations of certain entities. (Stanford Encyclopedia of Philosophy)

Structure of the Talk ICPS: How does it look like? ICPS: What it isn’t ICPS: What it is now ICPS: What it may be in the future

What ICPS may be in the future After finishing, ICPS has the potential to be universally accepted as a reporting standard The ICPS “key concepts” may become a fully-fledged formal ontology rooted in existing upper-level ontologies and using Semantic Web standards (OWL) and being linked to ontological / terminological standards like SNOMED CT The ICPS “conceptual framework” can be enhanced by formal descriptions The ICPS reporting template ("taxonomy") may then be fully described in terms of ICPS’s ontological core but… ICPS Architecture Critique Typology Outlook

Open issues The needs for semantically interoperable patient-safety relevant event reporting is essentially different from the reporting of diseases For the latter, the format of a statistical classification is adequate (ICD-10) Is the format of a reporting template adequate for the purpose ICPS is devised for? Is it necessary to transform the ICPS tree into a real taxonomy or classification structure? Terms like “taxonomy”, “classification” should be used thoughtfully ICPS Architecture Critique Typology Outlook

Acknowledgements Is the “International Classification for Patient Safety” (ICPS) a Classification? Stefan SCHULZ, Daniel KARLSSON, Christel DANIEL, Hans COOLS, Christian LOVIS Thanks for discussions: Pierre Lewalle (WHO) Jean-Marie Rodrigues Cédric Bousquet (Université de St.Etienne)

Classification Principles Particular Objects in the world to be classified

Classification Principles Particular Objects in the world to be classified Classes

Classification Principles Particular Objects in the world to be classified Classes Superclasses

Classification Principles Particular Objects in the world to be classified Classes Superclasses and so on…

Classification Principles Particular Objects in the world to be classified Classes Superclasses and so on…

Classification Principles Particular Objects in the world to be classified Classes Superclasses and so on…

Classification Principles

No overlapping classes: Each individual is member of exactly one terminal class

single parenthood / multiple parenthood Classifications, e.g. ICDOther Terminologies, e.g. SNOMED CT

Classification Principles

Structure of the Talk ICPS: How does it look like? ICPS: What it isn’t ICPS: What it is now ICPS: What it may be in the future ICPS Architecture Critique Typology Outlook

ICPS: Architecture ICPS Architecture Critique Typology Outlook