Ontology Content Patterns - A Quick Overview

Similar documents
Improving EHR Semantic Interoperability Future Vision and Challenges

How Ontologies Can Improve Semantic Interoperability in Health Care

MDHT Capabilities & Success Story

What s next for openehr. Sam Heard Thomas Beale

EHR Systems: an Introduction

EHR Standards Landscape

A Repository of Semantic Open EHR Archetypes

HL7 CDA, Clinical Modelling and openehr

The ASTM/HL7 Continuity of Care Document. HIMSS 2008 Liora Alschuler

EHR Archetypes in practice: getting feedback from clinicians and the role of EuroRec

Standardised and Flexible Health Data Management with an Archetype Driven EHR System (EHRflex)

What do clinical data standards mean for clinicians? Dr Nick Booth GP and Informatician, Warden, Northumberland, UK

Templates and Archetypes: how do we know what we are talking about?

Advanced Aspects of Hospital Information Systems

Electronic Health Record (EHR) Standards Survey

The next generation EHR

Tackling the Semantic Interoperability challenge

Electronic Health Records: An introduction to openehr and archetypes

Meaningful use. Meaningful data. Meaningful care. The 3M Healthcare Data Dictionary: Enabling effective health information exchange

ISO EN TECHNICAL REVISION

SaaS based Interoperability Service for Semantic Mappings among Health-care Standards

The HL7 Clinical Document Architecture. HIMSS 2008 Liora Alschuler

Il lavoro di armonizzazione. e HL7

Design of Modern Mobile Devices based on Medical Information Interchange Standards Med e Tel, 2015 Luxembourg

Proceedings of the Second Symposium on Healthcare Systems Interoperability

Advanced and secure architectural EHR approaches

How To Understand The Difference Between Terminology And Ontology

Clinical Decision Support Strategies

The Role of Ontologies for Sustainable, Semantically Interoperable and Trustworthy EHR Solutions

DICOM Correction Proposal

Meaningful Use Stage 2 Update: Deploying SNOMED CT to provide decision support in the EHR

A Sematic Web-Based Framework for Quality Assurance of Electronic Medical Records Data for Secondary Use

CHAPTER 3 PROPOSED SCHEME

Comparing Different Approaches to Two-Level Modelling of Electronic Health Records

Semantic interoperability of dual-model EHR clinical standards

PUBLIC HEALTH MU OBJECTIVES

TEST INSTRUCTIONS FOR CROSS VENDOR EXCHANGE TABLE OF CONTENTS

SMART C CDA Collaborative Perspective & Debriefing

Quality, Research and Public Health (QRPH) Technical Framework Supplement. Physician Reporting to a Public Health Repository Cancer Registry (PRPH-Ca)

Archetype-Based Knowledge Management for Semantic Interoperability of Electronic Health Records

Using Archetypes with HL7 Messages and Clinical Documents. Heath Frankel HL7 Working Group Meeting 14 January 2011

Binding Ontologies & Coding systems to Electronic Health Records and Messages

REQUIREMENTS REGARDING QUALITY CERTIFICATION OF ELECTRONIC HEALTH RECORDS

Development of an EHR System for Sharing A Semantic Perspective

Health Care Information System Standards

Binding Ontologies & Coding systems to Electronic Health Records and Messages

Clinical Knowledge Manager. Product Description 2012 MAKING HEALTH COMPUTE

Clinical Quality Improvement

HL7 and Meaningful Use

Secondary Use of EMR Data View from SHARPn AMIA Health Policy, 12 Dec 2012

Ontology-based Archetype Interoperability and Management

Models of Meaning and Models of Use: Binding Terminology to the EHR An Approach using OWL

Practical Implementation of a Bridge between Legacy EHR System and a Clinical Research Environment

Shelly Spiro, Executive Director, Pharmacy HIT Collaborative reports no relevant financial relationships.

Linköping University Post Print. Archetype-based conversion of EHR content models: pilot experience with a regional EHR system

The Electronic Healthcare Record for Clinical Research (EHR4CR) information model and terminology

Electronic Health Record. Standards, Coding Systems, Frameworks, and Infrastructures

Management and maintenance policies for EHR interoperability resources

Integration Information Model

The HL7 CIMI Workgroup: Creating Detailed Clinical Models to Support FHIR Interoperability. HIMSS March 2, 2016 Las Vegas Stanley M.

IHE Australia Workshops July Prepared by: Heather Grain Chair: Standards Australia IT14 Health Informatics and Ehealth Education

HL7 and SOA Based Distributed Electronic Patient Record Architecture Using Open EMR

HIE Ready 2.0 SPECIFICATIONS MATRIX. Product Name: Version Number: Preferred Message and Trigger

An overview of Health Informatics Standards

Deliverable 26.2 Report on EHCR

Strategies and experiences in Sweden

ProRec QREC Workshop 2011 Nicosia, 24 March 2011

CDX Conformance Profile EMR System Conformance CDA Level 1

Translational & Interoperable Health Infostructure - The Servant of Three Masters. Abridged Presentation

An Introduction to Health Level 7

Clinical Interoperability to Improve Quality and the Point-of-Care of EHR

Health IT Interoperability: HITSP Overview, Update and Discussion

Informatics and Technology, Hall in Tirol, Austria. Austria

Semantic validation of standard based electronic health record documents with W3C XML Schema

Clinical Decision Support Product Area Rong Chen MD PhD Chief Medical Informatics Officer

The Template Object Model (TOM)

Integrating Patient Care & Research Information Systems «ORBIS Research»

Interoperabilidad entre los Sistemas de Laboratório Clinico

Health Information Exchange Language - Bostaik

Certification of Electronic Health Record systems (EHR s)

Techniques for ensuring interoperability in an Electronic health Record

EHR systems - Future developments

Evaluation of a Persistent Store for openehr

Achieving Clinical Statement Interoperability using R-MIM and Archetype-based Semantic Transformations

Standards for E-Health Interoperability

The Big Picture: IDNT in Electronic Records Glossary

Towards Semantic Interoperability in Healthcare: Ontology Mapping from SNOMED-CT to HL7 version 3

Trends in Healthcare Information Standardization

Goals. Accelerating adoption & exchange of EHRs project. Evaluation Indicators EMR adoption (Hospitals) 20% (100 hospitals)

3M Health Information Systems

The use of ehealth standards in Norway

The Development of the Clinical Trial Ontology to standardize dissemination of clinical trial data. Ravi Shankar

Semantic Issues in Integrating Data from Different Models to Achieve Data Interoperability

EHR Data Reuse through openehr Archetypes

ONTARIO EHR INTEROPERABILITY STANDARDS WHY STANDARDS MATTER

Meaningful use. Meaningful data. Meaningful care. The 3M Healthcare Data Dictionary: Standardizing lab data to LOINC for meaningful use

Combining Smart Spaces and HL7 Medical standard in telemedicine scenarios

ERS. Boundaries between structuring applications and messaging. Trondheim. Tuesday 21 September Electronic Record Services B.V.

SNOMED CT Introduction. Dr Linda Bird, IHTSDO Implementation Specialist

Health Information Technology OIT Architecture Strategy

Transcription:

Ontology Content Patterns as Bridge for the Semantic Representation of Clinical Information Catalina Martínez Costa 1, Stefan Schulz 1,2 1 Institute for Medical Informatics, Statistics and Documentation, Medical University of Graz, Austria 2 Institute of Medical Biometry and Medical Informatics, University Medical Center, Freiburg, Germany

Three Kinds of Artefacts Focus on clinical information representation BOUNDARY PROBLEM EHR Information Models ISO 13606, openehr, HL7 RIM, DCM, etc. OVERLAPPING AREA Medical Terminologies / Ontologies SNOMED CT, ICD, LOINC, etc. Clinical Models ISO 13606 / openehr archetypes, DCMs, HL7 CDA, Intermountain CEM, etc. Clinical Model Clinical Model Clinical Model Clinical Model ISO-SEMANTIC MODELS 2

Methods ONTOLOGICAL FRAMEWORK SEMANTIC INFRASTRUCTURE SEMANTIC PATTERNS 3

Ontological Framework BioTopLite 2.0 epistemic entities FORMALISED IN OWL 2 DL (description logics) 4

Ontological Framework (II) Medical Application Systems HOMOGENEOUS DATA ACCESS POINT SEMANTIC INFRASTRUCTURE Hospital STRUCTURED HETEROGENEOUS DATA Primary Care EHR - OpenEHR Patient: Franz Müller DoB: 17/01/1965 Encounter: 23/08/98 Tobacco Use Summary - Cigarette smoker, 14 /d EHR - HL7 CDA Patient: Franz Müller DoB: 17/01/1965 Encounter: 23/08/2001 Social history - Heavy cigarette tobacco smoker 5

Ontological Framework (III) EHR Patient: Franz Müller DoB: 17/01/1965 Encounter: 23/08/98 Tobacco Use Summary - Cigarette smoker, 14 /d OWL DL Hospital --Smoking status and isaboutsituation only sct:tobaccosmokingsituation and isoutcomeof some sct:historytaking -- Form and isaboutsituation only sct:cigarettetobaccosmoking and isoutcomeof some sct:historytaking -- Amount ObservationResult and isaboutquality some (MassIntake and inheresin some sct:cigarettetobaccosmokingsituation and projectsonto some (ValueRegion and isrepresentedby only (hasvalue value 14 and hasinformationattribute some sct:perday))) openehr archetype EVALUATION[at0000] matches { -- Tobacco Use Summary data matches { ITEM_TREE[at0001] matches { -- Tree items cardinality matches {0..*; unordered} matches { ELEMENT[at0002] occurrences matches {0..1} matches { -- Smoking Status value matches { DV_CODED_TEXT matches { defining_code matches { [local:: at0003, -- Current Smoker at0027, -- Never Smoked at0005] -- Ex-smoker }}}} CLUSTER[at0029] occurrences matches {0..*} matches { -- Smoking Details items cardinality matches {1..*; unordered} matches { ELEMENT[at0028] occurrences matches {0..1} matches { -- Form value matches { DV_TEXT matches {*}}} ELEMENT[at0030] occurrences matches {0..1} matches { -- Typical smoked amount value matches { C_DV_QUANTITY < property = <[openehr::382]> list = < ["1"] = < units = <"/d"> magnitude = < >=0.0 > precision = < 0 > >>}}}} }}}}} 6

Ontological Framework (IV) Primary Care EHR Patient: Franz Müller DoB: 17/01/1965 Encounter: 23/08/2001 Social history - Heavy cigarette tobacco smoker OWL DL --Current Heavy tobacco smoker and isaboutsituation only sct:heavycigarettesmokingsituation and isoutcomeof some sct:evaluation HL7 CDA model compliant with Meaningful Use <section> <!-- Social History Section templateid --> <templateid root="2.16.840.1.113883.10.20.22.2.17"/> <code code="29762-2" codesystem="2.16.840.1.113883.6.1" displayname="social history"/> <title>social History</title> <text>began smoking daily on 4/10/2011.</text> <entry> <observation classcode="obs" moodcode="evn"> <templateid root="2.16.840.1.113883.10.20.22.4.78"/> <code code="assertion" codesystem="2.16.840.1.113883.5.4"/> <statuscode code="completed"/> <effectivetime> <!-- Date the person began smoking --> <low value="20110410"/> </effectivetime> <value xsi:type="cd" code="428071000124103" codesystem="2.16.840.1.113883.6.96" displayname="current Heavy tobacco smoker" /> </observation> </entry> </section> Meaningful Use : > = 10 cigarettes / day 7

Semantic Patterns User-friendly abstractions that provide a more intuitive and closer to natural language representation Prevent modelers from a in-depth ontology and description logics modeling knowledge and skills Represent recurring content modelling tasks by following a standardized structure E.g. who does what, when and where?, which objects take part in a certain event?, etc. Defined wrt. a reference ontology (particular view on it) They can be specialised and composed 8

Semantic Patterns (II) Represented as a set of constrained Subject-Predicate-Object (SPO) triples. Cardinality and Value Constraints 9

Semantic Patterns OWL DL Representation Use of DL reasoning for: Detection of iso-semantic information across models Advanced query of clinical information OWL 2 DL transformation: SUB and OBJ into OWL DL classes Predicates into OWL DL expressions Predicate OWL DL expression 'describes situation' SUBJ subclassof shn:isaboutsituation only OBJ 'results from process' SUBJ subclassof btl:isoutcomeof some OBJ 'has attribute' SUBJ subclassof btl:hasinformationattribute some OBJ 'has observed value' SUBJ subclassof btl:quality and btl:projectsonto some OBJ 'has units' SUBJ subclassof btl:isrepresentedby only (shn:hasinformationattribure some OBJ) shn: describes situation shn:clinicalsituation shn: and shn:isaboutsituation only shn:clinicalsituation

Advanced Query of Clinical Information Hospital Patient: Franz Müller Primary Care Patient: Franz Müller DoB: 17/01/1965 DoB: 17/01/1965 Encounter: 23/08/98 Encounter: 23/08/2001 Tobacco Use Summary - Cigarette smoker, 14 /d Social History - Heavy cigarette tobacco smoker OWL DL Representation --Smoking status and isaboutsituation only sct:tobaccosmokingsituation and isoutcomeof some sct:historytaking --Current Heavy tobacco smoker and isaboutsituation only sct:heavycigarettesmokingsituation and isoutcomeof some sct:evaluation -- Form and isaboutsituation only sct:cigarettetobaccosmoking and isoutcomeof some sct:historytaking -- Amount ObservationResult and isaboutquality some (MassIntake and inheresin some sct:cigarettetobaccosmokingsituation and projectsonto some (ValueRegion and isrepresentedby only (hasvalue value 14 and hasinformationattribute some sct:perday))) 11

Advanced Query of Clinical Information (II) #Q1 shn: and btl:isoutcomeof some sct:historytaking and shn:isaboutsituation only sct:tobaccosmokingsituation #Q2 shn: and btl:isoutcomeof some shn:evaluation and shn:isaboutsituation only sct:heavytobaccosmokingsituation #Q3 shn: and btl:isoutcomeof some shn:evaluation --Smoking status and shn:isaboutsituation only sct:heavytobaccosmokingsituation and shn:isaboutsituation only sct:cigarettetobaccosmokingsituation and isaboutsituation only sct:tobaccosmokingsituation and isoutcomeof some sct:historytaking #Q4 shn:observationresult and shn:isaboutquality only (shn:massintake --Current Heavy tobacco smoker and isaboutsituation only sct:heavycigarettesmokingsituation and isoutcomeof some sct:evaluation and btl:inheresin some sct:cigarettetobaccosmokingsituation and btl:projectsonto some DL reasoning (btl:valueregion and btl:isrepresentedby only (shn:hasinformationattribute SNOMED CT ontology some sct:perday shn:hasvalue some int[>15]))) 12

Advanced Query of Clinical Information (III) #Q1 shn: and btl:isoutcomeof some sct:historytaking and shn:isaboutsituation only sct:tobaccosmokingsituation #Q2 shn: and btl:isoutcomeof some shn:evaluation and shn:isaboutsituation only sct:heavytobaccosmokingsituation #Q3 shn: and btl:isoutcomeof some shn:evaluation and shn:isaboutsituation only sct:heavytobaccosmokingsituation and shn:isaboutsituation only sct:cigarettetobaccosmokingsituation #Q4 shn:observationresult and shn:isaboutquality only (shn:massintake and btl:inheresin some sct:cigarettetobaccosmokingsituation -- Amount ObservationResult and isaboutquality some (MassIntake and inheresin some sct:cigarettetobaccosmokingsituation and projectsonto some (ValueRegion and isrepresentedby only (hasvalue value 14 and hasinformationattribute some sct:perday))) and btl:projectsonto some (btl:valueregion and btl:isrepresentedby only (shn:hasinformationattribute --Current Heavy tobacco smoker some sct:perday shn:hasvalue some int[>15]))) and isaboutsituation only sct:heavycigarettesmokingsituation and isoutcomeof some sct:evaluation Local system rules. Vary across institutions DL reasoning SNOMED CT ontology 13

#Q1 shn: and btl:isoutcomeof some sct:historytaking and shn:isaboutsituation only sct:tobaccosmokingsituation Advanced #Q2 shn: Query of Clinical Information (IV) and btl:isoutcomeof some shn:evaluation and shn:isaboutsituation only sct:heavytobaccosmokingsituation #Q3 shn: and btl:isoutcomeof some shn:evaluation and shn:isaboutsituation only sct:heavytobaccosmokingsituation and shn:isaboutsituation only sct:cigarettetobaccosmokingsituation #Q4 shn:observationresult and shn:isaboutquality only (shn:massintake and btl:inheresin some sct:cigarettetobaccosmokingsituation and btl:projectsonto some (btl:valueregion and btl:isrepresentedby only (shn:hasinformationattribute some sct:perday shn:hasvalue some int[>15]))) -- Amount ObservationResult and isaboutquality some (MassIntake and inheresin some sct:cigarettetobaccosmokingsituation and projectsonto some (ValueRegion and isrepresentedby only (hasvalue value 14 and hasinformationattribute some sct:perday))) --Current Heavy tobacco smoker and isaboutsituation only sct:heavycigarettesmokingsituation and isoutcomeof some sct:evaluation The query does not retrieve any record Local system rules. Vary across institutions 14

Conclusions The use of EHR standards and terminologies does not guarantee semantic interoperability SemanticHealthNet proposes an intermediate semantic layer able to deal with the present clinical information heterogeneity We hypothesize that clinical models information can be represented by the specialisation and composition of a set of limited top-level semantic patterns The proposed infrastructure faces two main kinds of challenges (human & computational) Compromises between performance and functionality might be required 15

Danke! ONTOLOGICAL FRAMEWORK SEMANTIC INFRASTRUCTURE SEMANTIC PATTERNS 16