Detailed Clinical Models for Sharable, Executable Guidelines



Similar documents
What s next for openehr. Sam Heard Thomas Beale

A Virtual Medical Record for Guideline-Based Decision Support

How To Improve Data Collection

Sharable Appropriateness Criteria in GLIF3 Using Standards and the Knowledge-Data Ontology Mapper

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

Information Model Requirements of Post-Coordinated SNOMED CT Expressions for Structured Pathology Reports

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

Translation Protégé Knowledge for Executing Clinical Guidelines. Jeong Ah Kim, BinGu Shim, SunTae Kim, JaeHoon Lee, InSook Cho, Yoon Kim

Ahmed AlBarrak PhD Medical Informatics Associate Professor, Family & Community Med. Chairman, Medical Informatics Department College of Medicine King

Interconnected Health 2012 April 3, Daryl Chertcoff, Project Manager, HLN Consulting, LLC Angel Aponte, Computer Specialist

Advanced Aspects of Hospital Information Systems

Arriclides: An Architecture Integrating Clinical Decision Support Models

OpenCDS: an Open-Source, Standards-Based, Service-Oriented Framework for Scalable CDS

Binding Ontologies & Coding systems to Electronic Health Records and Messages

- Panel - RDF as a Universal Healthcare Exchange Language

medexter clinical decision support

Global Health Informatics Standards for Patient Safety

ICOM 6005 Database Management Systems Design. Dr. Manuel Rodríguez Martínez Electrical and Computer Engineering Department Lecture 2 August 23, 2001

HL7 & HL7 CDA: The Implementation of Thailand s Healthcare Messaging Exchange Standards Nawanan Theera-Ampornpunt, M.D., Ph.D.

OpenCDS: an Open-Source, Standards-Based, Service-Oriented Framework for Scalable CDS

Binding Ontologies & Coding systems to Electronic Health Records and Messages

Medical Clinical Trials and Natural Language Processing (NPAT)

HL7 Common Terminology Services 2 Service Functional Model (SFM)

SNOMED CT in the EHR Present and Future. with the patient at the heart

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

Mapping Computerized Clinical Guidelines to Electronic Medical. Records: Knowledge-Data Ontological Mapper (KDOM)

Ontology Content Patterns - A Quick Overview

Agile Software Development

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

OpenCDS: Overview, Demonstration, and Potential Implications for HeD Use Case 2

Bringing Business Objects into ETL Technology

Cancer Communication & Care Plan - We Learned How We Work

Natural Language Processing in the EHR Lifecycle

Secure Exchange of Clinical Information for Clinical Research. Using open source technology

Defining the content of shared electronic medical records (emr)

New Graduate Degree Program. Required Signatures Name Signature Date Teaching Unit Chair or Director

Improving EHR Semantic Interoperability Future Vision and Challenges

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

HL7 NCPDP e-prescribing harmonization: using the v3 HDF for as a basis for semantic interoperability

Standardized Representation for Electronic Health Record-Driven Phenotypes

Strategic Health IT Advanced Research Projects (SHARP) Area 4: Secondary Use of EHR Data. SHARPfest Washington June 2-3, 2010

The next generation EHR

HL7 FHIR The Argonaut Project C-CDA

Gai Elhanan, M.D., M.A. Chief Medical Information Officer. Jane A. Burke BSMT (ASCP) Clinical Data Specialist

Model-Driven Health Tools (MDHT) CDA Tools Overview.

The Healthcare Services Platform Consortium

NIST GCR Templated CDA: Key Concept for Interoperability

Ontology Mapping and Data Discovery for the Translational Investigator

A National Clinical Decision Support Infrastructure to Enable Genetically-Guided Population Health Management at Scale

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

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

A Guideline Engine For Knowledge Management in Clinical Decision Support Systems (CDSSs)

DEMONSTRATING CLOUD-BASED CLINICAL DECISION SUPPORT AT SCALE: THE CLINICAL DECISION SUPPORT CONSORTIUM

Electronic Submission of Medical Documentation (esmd) CDA Digital Signatures. January 8, 2013

Abstract. 2. Participant and specimen tracking in clinical trials. 1. Introduction. 2.1 Protocol concepts relevant to managing clinical trials

Cross-Tool Communication: From Protocol Authoring to Eligibility Determination

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

ARGOS Policy Brief on Semantic Interoperability

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

How To Use An Electronic Medical Record

Health IT Enabled Quality Measurement and Improvement: The HL7 Clinical Quality Information Workgroup

Electronic Medical Records Getting It Right and Going to Scale

DermLex, Patient Registries, DermBase and More: What s New in

Clinical Decision Support Consortium

Heading off the traffic jam

Promoting perinatal safety through discrete data interoperability across multiple EHRs Vish Anantraman, MD, MS Michael I.

Telling the Data Story: Use of Informatics, Harmonized Semantics and Metadata in the National Children s Study

Quality Reporting Under Meaningful Use Stage 2. Crystal Kallem, Director of Business Analysis & Policy Lantana Consulting Group

XML for Manufacturing Systems Integration

The Healthcare Services Platform Consortium

Health IT Certificate Series Introduction. Health IT Certificate Series - Professional Tracks

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

Object-Oriented Design

SNOMED-CT

There has to be more: iconnect Blends XDS and Image Exchange. A Merge White Paper

Electronic Submission of Regulatory Information, and Creating an Electronic Platform for Enhanced Information Management

Chapter 6: Programming Languages

Helping the Cause of Medical Device Interoperability Through Standardsbased

Component 6 - Health Management Information Systems. Objectives. Purpose of a Patient (medical) Record. Unit 3-1 Electronic Health Records

TAP into NAU. TAP is a single tool. How it works. Transfer Academic Plan nau.edu/tap

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

The Evolution of Clinical Decision Support. David McCallie Jr. MD Cerner Corp.

HISPANIS HEALTH INTEGRATED CARE SOLUTION HH - ICS

For the enterprise application environment utilizing the SOA Paradigm

Integration Information Model

Clinical Decision Support Based on Topic Maps and Virtual Medical Record

VistA Evolution Presentation to World Vista

Clinical Decision Support Strategies

IBM Watson and Medical Records Text Analytics HIMSS Presentation

Introducing Reference Models in ERP Development

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville

Genomic Medicine Centers Meeting VII. Summary of Themes Discussed in Keynote and Panel Discussions October 3, 2014

Clinical Decision Support Systems An Open Source Perspective

Data Standards and the National Cardiovascular Research Infrastructure (NCRI)

Future Tense. How everything is going to be different and why you should care. David A Stumpf, MD, PhD

Best Practices with IBM Cognos Framework Manager & the SAP Business Warehouse Agnes Chau Cognos SAP Solution Specialist

A Semantic Foundation for Achieving HIE Interoperability

10/13/2010. Objectives. Overview. Introduction. Intermountain Healthcare. Nutrition Informatics

A Qualitative Study of the Electronic Medical Record

Qint Software - Technical White Paper

Transcription:

Detailed Clinical Models for Sharable, Executable Guidelines Craig G. Parker MD Roberto A. Rocha MD PhD James R. Campbell MD Samson W. Tu MS Stanley M. Huff MD

Roadmap What is SAGE? Sharing guideline information Challenges Solutions

What Is SAGE? Standards-based, Active Guideline Environment NIST ATP Grant Apelon, IDX, IHC, Mayo Clinic, Stanford, UNMC

What Is SAGE? Standards-based Leverage existing standards Help create new standards Goal: shareable guidelines Active Guideline Environment

What Is SAGE? Standards-based Active Executable Guideline Environment

SAGE Overview

Multiple EMRs, Multiple Mappings EMR 1 EMR 2 EMR 3

Mappings Grow Exponentially EMR 1 EMR 2 EMR 3 EMR 4

Standard, Shared Representation EMR 1 EMR 2 EMR 3 EMR 4

For Guidelines EMR 1 EMR 2 SAGE EMR 3 EMR 4

What Needs to Be Sharable? Logic E.g. Arden Syntax (procedural) SAGE guideline format (declarative) Data (focus of this presentation) Curly braces in Arden Syntax VMR + Detailed Clinical Models in SAGE

For Data in Guidelines EMR 1 EMR 2 VMR + DCM EMR 3 EMR 4

What Is the VMR? Virtual Medical Record A small set of classes corresponding to the broad types of clinical data needed for guideline execution Classes defined on an as-needed basis Based on other existing standards (HL7 RIM) where possible

Virtual Medical Record

VMR in Protege 13 Classes (currently) Relatively flat inheritance hierarchy (currently) Designed to meet specific needs of specific guidelines

VMR Observation Class

Do We Need More Than a VMR? It describes broad areas of guideline related information It enables representations of clinical information It does not constrain or validate except at the coarsest level

Too Many Ways to Say the Same Thing A single name/code and value Left patellar deep tendon reflex intensity is 2+ Combination of two names/codes and values Patellar deep tendon reflex intensity is 2+ Laterality is left Combination of three names/codes and values Deep tendon reflex intensity is 2+ Body part is patella Laterality is left

Too Many Ways to Say the Same Thing A single name/code and value Left patellar deep tendon reflex intensity is 2+ Combination of two names/codes and values All of these examples Patellar deep tendon reflex intensity is 2+ can be represented by Laterality is left a single VMR Combination of three names/codes and values Deep tendon reflex intensity is 2+ Body part is patella Laterality is left

Detailed Clinical Models Specializations of VMR classes Define boundary between terminology and information models Similar to (if not the same as): Archetypes Templates Clinical Statements

Pseudocode DCM Example Reflex constrains vmr.observation { code.equals( reflex finding ) value.isa(reflex_finding_value_set) hasqualifier { code.equals( body part ) value.isa(body_part_value_set) } hasqualifier { code.equals( laterality ) value.isa(laterality_value_set) } }

What Do We Gain? Preserve modeling decisions across guidelines Can be used as a catalog of the data used in a guideline A shareable definition of a clinical entity

Priorities Internally consistent Pragmatic - The ideal separation of information and terminology models was not always supported by: Our chosen terminologies Our information model The real underlying EMRs If every EMR stores the concept no family history of breast cancer what do we gain practically form using a post-coordination? Elegant

Status of DCMs in SAGE Currently: Defines boundary between terminology & information models Specify appropriate value sets In the future: Aggregation Qualification

Conclusion We have implemented a method for sharing data needed for representing clinical guidelines by: Designing an abstraction of specific EMRs (the VMR) Defining specializations of this abstraction (Detailed Clinical Models)

Thank You http://www.sageproject.net