SHARP F2F Meeting Mayo Clinic June 21, 2010 Stanley M Huff, MD

Slides:



Advertisements
Similar presentations
Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.
Advertisements

# 1 Practical modeling issues: Representing coded and structured patient data in EHR systems AMIA Fall Conference Novermber 13, 2010 Stanley M Huff, MD.
Clinical Model and Terminology Issues in Guideline Execution Craig Parker, Harold Solbrig, Stan Huff & Roberto Rocha as part of the SAGE project The SAGE.
HL7-Individual Case Safety Reporting (ICSR)
© 2011 TIBCO Software Inc. All Rights Reserved. Confidential and Proprietary. Towards a Model-Based Characterization of Data and Services Integration Paul.
Consistent and standardized common model to support large-scale vocabulary use and adoption Robust, scalable, and common API to reduce variation in clinical.
Data Normalization Milestones. Data Normalization  Goals –To conduct the science for realizing semantic interoperability and integration of diverse data.
CTS2 Terminology Services
Data Normalization Dr. Stan Huff. # 2 Acknowledgements Tom Oniki Joey Coyle Craig Parker Yan Heras Cessily Johnson Roberto Rocha Lee Min Lau Alan James.
VSAC Users’ Forum Thursday, January 15 2:00 – 3:00 PM, EST.
CIMI Modelling Taskforce Progress Report
Kaiser Permanente Standards Summit September 7-8, 2011 Stanley M. Huff, MD Huff # 1 A Brief Review of CIMI Plans and Goals London CIMI Meetings November.
Archetypes in HL7 2.x Snomed-CT “Computable Medical Records” Andrew McIntyre Medical-Objects NEHTA Snomed-CT Workshop.
Implementing a Clinical Terminology David Crook Subset Development Project Manager SNOMED in Structured electronic Records Programme NHS Connecting for.
The Role of Standard Terminologies in Facilitating Integration James J. Cimino, M.D. Departments of Biomedical Informatics and Medicine Columbia University.
“DOK 322 DBMS” Y.T. Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems.
FEBRUARY 4, 2015 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Modeling and Terminology.
Clinical Vocabularies James J. Cimino, M.D. Columbia University.
Lab Data Modeling Options Lab LOINC Meeting June, 2015 Indianapolis, Indiana.
C o n f i d e n t i a l Developed By Nitendra NextHome Subject Name: Data Structure Using C Title: Overview of Data Structure.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
Terminology in Health Care and Public Health Settings
1 Betsy L. Humphreys, MLS Betsy L. Humphreys, MLS National Library of Medicine National Library of Medicine National Institutes of Health National Institutes.
Our Joint Playing Field: A Few Constants Change Change Our missions (if defined properly) Our missions (if defined properly) Importance of Community Engagement.
# 1 Practical modeling issues: Representing coded and structured patient data in EHR systems AMIA Fall Conference Novermber 14, 2009 Stanley M Huff, MD.
Terminology Standards 2/3 BDK06-6 Clinical Data Standards Related to Big Data William Hersh, MD Department of Medical Informatics & Clinical Epidemiology.
10/3/2015DRAFT1 Public Health & Clinical LOINC - Jan 28 th 2011 CDC Vocabulary Team Office of Surveillance, Epidemiology and Laboratory Services (OSELS)
# 1 Practical modeling issues: Representing coded and structured patient data in EHR systems SHARP August 23, 2010 Stanley M Huff, MD Chief Medical Informatics.
Kaiser Permanente Standards Summit September 7-8, 2011 Stanley M. Huff, MD Huff # 1 We Are on the Right Path! SHARPn Face-to-Face June 11, 2012 Stanley.
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Modeling Options HSPC Meeting June 17, 2015 Washington DC.
# 1 Clinical Data Normalization / Practical Modeling Issues Representing Coded & Structured Patient Data SHARPn Face to Face Meeting June 11, 2012 Stanley.
Value Set Resolution: Build generalizable data normalization pipeline using LexEVS infrastructure resources Explore UIMA framework for implementing semantic.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Andrew S. Kanter, MD MPH a,b a Millennium Villages Project, Earth Institute, Columbia University, New York, USA b Department of Biomedical Informatics,
Component 3-Terminology in Healthcare and Public Health Settings Unit 17-Clinical Vocabularies This material was developed by The University of Alabama.
Query Health Concept-to-Codes (C2C) SWG Meeting #11 February 28,
# 1 Clinical Element Models (CEMs) SHARP F2F Meeting Mayo Clinic June 21, 2010 Stanley M Huff, MD.
Copyright © 2006 Pilothouse Consulting Inc. All rights reserved. Search Overview Search Features: WSS and Office Search Architecture Content Sources and.
LexGrid Philosophy, Model and Interfaces Harold R Solbrig Division of Biomedical Statistics and Informatics Mayo Clinic.
Health Level 7- Templates SIG By Peter Elkin, Mayo Clinic Martin Kernberg, UCSF Angelo Rossi-Mori, Italy.
SNOMED Bound to (Information) Model Putting terminology to work… Koray Atalag MD, PhD, FACHI Senior Research Fellow (NIHI & ABI)
Part I: Introduction to SHARPn Normalization Hongfang Liu, PhD, Mayo Clinic Tom Oniki, PhD, Intermountain Healthcare.
CIMI_Phoenix_Huff_ Page 1 A Brief Review of CIMI Progress, Plans, and Goals CIMI Meeting Orlando HL7 WGM, January 2016 Stanley M Huff, MD Chief.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4a Basic Health Data Standards Component 9/Unit.
All Recurring Key Themes The below list includes themes across many of the different presentations to date. The next 2 slides address how these may be.
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
C-CDA Encoding Issues and Solutions
Use of translationCode and Combination Code Proposal
11th HL7 Australia Conference, 13th December 2006
Combination Codes Discussion.
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
Achieving Semantic Interoperability of Cancer Registries
CIMI Semantics Roundup
WP1: D 1.3 Standards Framework Status June 25, 2015
Detailed Clinical Models WC3, March 29, 2007
Data Normalization Architecture
A bit more about Read Codes and SNOMED CT
Health Information Exchange Interoperability
Database Systems Instructor Name: Lecture-3.
Model ID: Model to represent entire statement including context
Data Element Definitions Pediatric SIG
Database Design Hacettepe University
Clinical Element Models
ICT Database Lesson 2 Designing a Database.
Interoperability with SNOW SHRINE
Extending OMOP CDM to Support Observational Cancer Research
Presentation transcript:

SHARP F2F Meeting Mayo Clinic June 21, 2010 Stanley M Huff, MD Clinical Element Models (CEMs) SHARP F2F Meeting Mayo Clinic June 21, 2010 Stanley M Huff, MD

What if there is no model? Site #1 70 70 kg Dry Weight: Site #2 70 70 kg Dry Weight: Wet Ideal

Relational database implications Patient Identifier Date and Time Observation Type Observation Value Units 123456789 7/4/2005 Dry Weight 70 kg 7/19/2005 Current Weight 73 Patient Identifier Date and Time Observation Type Weight type Observation Value Units 123456789 7/4/2005 Weight Dry 70 kg 7/19/2005 Current 73 How would you calculate the desired weight loss during the hospital stay?

Model Centered Data Representation SNOMED ICD-10 RxNorm FDB LOINC CPT SNOMED ICD-10 RxNorm FDB LOINC CPT LexGrid Terminology Server Context Specific Mapping Tables Models and Concepts Internal Terminology (ECIDS) IH Thesaurus ECIS Thesaurus Mayo Thesaurus Models

We assume that the model is used in association with a terminology server.

Model and Terminology If the medicationOrder.drug is_a “antibiotic” Instance data MedicationOrder ::= SET { drug Drug, dose Decimal, route DrugRoute, frequency DrugFrequency, startTime DateTime, endTime DateTime, orderedBy Clinician, orderNumber OrderNumber} MedicationOrder { drug PenVK, dose 250, route Oral, frequency Q6H, startTime 09/01/95 10:01, endTime 09/11/95 23:59, orderedBy Don Jones, M.D., orderNumber A234567 } If the medicationOrder.drug is_a “antibiotic” then notify the infection control officer.

Concept Semantic Network Drugs Antibiotics Analgesics Cardiovascular Penicillins Cephalosporins Aminoglycosides Pen VK Amoxicillin Nafcillin

Basic elements of the core model Type - The name of a particular model Key - Links the model to a concept in an external coded terminology. Value Choice - Possible ways to convey the model’s value. Do not want to store LOINC, SNOMED code directly by design. We link to external coded terminology. 1. Impossible to correct errors made in standard terminology, I.e. SNOMED, unless change database. If use mapping, then can just change the mapping to correct the error. 2. Standard terminology makes mistakes.

A Panel containing 2 Observations

Mods and Quals of the Value Choice Mods - Component CE’s which change the meaning of the Value Choice. Quals - Component CE’s which give more information about the Value Choice.

The use of Qualifiers

The use of Modifiers

XML Model with Term Binding The name of this model Binding to a single “observable” concept <cetype name="BloodPressurePanel" kind="panel">   <key code="BloodPressurePanel_KEY_ECID" />  <item name="systolicBloodPressureMeas" type="SystolicBloodPressureMeas" card="0-1" />   <item name="diastolicBloodPressureMeas" type="DiastolicBloodPressureMeas" card="0-1" />   <item name="meanArterialPressureMeas" type="MeanArterialPressureMeas" card="0-1" />   <qual name="methodDevice" type="MethodDevice" card="0-1" />   <qual name="bodyLocationPrecoord" type="BodyLocationPrecoord" card="0-1" />   <qual name="bodyPosition" type="BodyPosition" card="0-1" />   <qual name="relativeTemporalContext" type="RelativeTemporalContext" card="0-M" />   <qual name="patientPrecondition" type="PatientPrecondition" card="0-M" />   <mod name="subject" type="Subject" card="0-1" />   <att name="observed" type="Observed" card="0-1" />   <att name="reportedReceived" type="ReportedReceived" card="0-1" />   <att name="verified" type="Verified" card="0-1" />   … </cetype>

Binding to a “domain” (value set)   <constraint path="qual.methodDevice.data.cwe.domain" value="BloodPressureMeasurementDevice_DOMAIN_ECID" /> <constraint path="qual.bodyLocationPrecoord.data.cwe.domain" value="BloodPressureBodyLocationPrecoord_DOMAIN_ECID" /> Path to the coded element The name of the terminology “domain” that the element is “bound” to

Decomposition Mapping Precoordinated Model (User Interface Model) SystolicBPRightArmSittingObs SystolicBPRightArmSitting data 138 mmHg Post coordinated Model (Storage Model) SystolicBPObs SystolicBP data 138 mmHg quals BodyLocation BodyLocation data Right Arm PatientPosition PatientPosition data Sitting