Enhancing interoperation: an i2b2 ETL schema for Epic EHRs

Slides:



Advertisements
Similar presentations
© Copyright 2005 dbMotion Ltd. By dbMotion RIM Based Semantic Interoperability Assaf Halevy, Co – Founder & VP Strategic Accounts
Advertisements

TRANSITIONING FROM PP EXTRACT TO A VENDOR NEUTRAL DATA EXTRACTION APPROACH RUTH JENKINS, PHD AUGUST 22, 2014 ©PPRNET 2014.
1 Department of Computer Science 2 Department of Emergeny Medicine
Big Data Research for Transforming USA Healthcare – LOINC Possible Road Map Susan A. Matney, MSN, RN, FAAN1 Bonnie L. Westra, PhD, RN, FAAN, FACMI2 13M.
VSAC Users’ Forum Thursday, January 15 2:00 – 3:00 PM, EST.
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Archetypes in HL7 2.x Snomed-CT “Computable Medical Records” Andrew McIntyre Medical-Objects NEHTA Snomed-CT Workshop.
Minnesota Recommendation to Use of a Standard Nursing Terminology in All Health Care Settings Bonnie L. Associate Professor & Director Center for Nursing.
The Role of Standard Terminologies in Facilitating Integration James J. Cimino, M.D. Departments of Biomedical Informatics and Medicine Columbia University.
© 2013 The McGraw-Hill Companies, Inc. All rights reserved. Chapter 9 Tests, Procedures, and Codes.
Azara Proprietary & Confidential Overview June 2014 Improving Patient Outcomes through Data.
0 Hosted Monthly on the 3 rd Tuesday 3 :00PM EST Registration is Free.
Meaningful Use Measures. Reporting Time Periods Reporting Period for 1 st year of MU (Stage 1) 90 consecutive days within the calendar year Reporting.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
Terminology in Health Care and Public Health Settings
NWH TRANSITION OF CARE DOCUMENT FOR MU STAGE 2 JUNE 6, 2014.
Our Joint Playing Field: A Few Constants Change Change Our missions (if defined properly) Our missions (if defined properly) Importance of Community Engagement.
PCORI/GPC Standard Data Model Jim Campbell, Dan Connolly, GPC Data standardization team.
Overview of Interoperability Standards Advisory Steve Posnack Director of Office of Standards and Technology, ONC 1.
Referral request - data classification Patient information – Patient demographics, covered by MU2 and CCDA requirements – Patient identifier (Med Rec Number)
Survey of Medical Informatics CS 493 – Fall 2004 September 27, 2004.
Query Health Concept-to-Codes (C2C) SWG Meeting #12 March 6,
PCORI/GPC Standard Data Model Jim Campbell, Dan Connolly, GPC Data standardization team.
PCORI/GPC Standard Data Model Jim Campbell, Dan Connolly, GPC Data standardization team.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
HIT Policy Committee Adoption/Certification Workgroup Comments on NPRM, IFR Paul Egerman, Co-Chair Retired Marc Probst, Co-Chair Intermountain Healthcare.
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
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.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Component 11/Unit 2a Meaningful Use of the Electronic Health Record (EHR)
Research Network Query Interoperation James R. Campbell University of Nebraska.
PCORI/GPC Standard Data Model Jim Campbell, Dan Connolly, GPC Data standardization team.
HIT Standards Committee Clinical Operations Workgroup Jamie Ferguson Kaiser Permanente John Halamka Harvard University February 24, 2010.
Terminology in Healthcare and Public Health Settings Standards to Promote Health Information Exchange This material Comp3_Unit 16 was developed by The.
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
Pharmacy Health Information Technology Collaborative Date: April 28, 2016 Presenter:Shelly Spiro, RPh, FASCP Pharmacy HIT Collaborative Executive Director.
3M Health Information Systems 1© 3M All Rights Reserved. 3M Health Information Systems Data Standardization Interoperability.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Clinical terminology for personalized medicine: Deploying a common concept model for SNOMED CT and LOINC Observables in service of genomic medicine James.
Deploying ONC terminology standards in SNOW SHRINE i2b2 data warehouse
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
Deploying ONC terminology standards in SNOW SHRINE i2b2 data warehouse
Table core Part file Answer file Group file
OMOP on FHIR Version 1 is in use. Version 2 is under development
Use of translationCode and Combination Code Proposal
Genomic Definition by Reference Mapping
Care planning model and content
LOINC – SNOMED CT Cooperation on Content
Shawn Murphy, MD PhD Diane Keogh, i2b2 Foundation
Networking and Health Information Exchange
Electronic Health Records (EHR)
Terminology Service Bureau Vision
Achieving Semantic Interoperability of Cancer Registries
DROC Request from Cancer CRG Preliminary feasibility query 06/13/2017
SNOMED CT, Synoptic Observables and Clinical Genomics
WorldVistA EHR (VOE) CCHIT Certified EHR.
Interoperable Social Determinants of Health: LOINCing the PCAM
What is Useful? Publishing Support for Precision Medicine
Research on FHIR Fast Healthcare Interoperability Resources
LOCAL EXPERIENCES Innovation practices and experiences related to FIC development and implementation Ariadna Rius Clinical Dictionary for iSalut.
Miscellaneous FHIR Slides
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.3.3 Manage Clinical Documents and Notes aka DC in EHR-S FM.
Relevant and Pertinent Short Survey Results
Special Topics in Vendor-Specific Systems
, facilitator January 21, 2011 DRAFT-A
Relevant and Pertinent Short Survey Results
Electronic Health Record Access Control 7
Patient Care WG Allergy and Intolerances Project
Interoperability with SNOW SHRINE
Presentation transcript:

Enhancing interoperation: an i2b2 ETL schema for Epic EHRs James R. Campbell MD James McClay MD Departments of Internal Medicine & Emergency Medicine University of Nebraska Medical Center

Outline Organizing i2b2 for interoperation I2b2 Extract, Transfer and Load architecture for Epic EHRs Data warehouse extracts vs CCDA vs FHIR interface for transportability of code

Operational Expectations of i2b2 load Query / aggregate data across collaborators with little or no mapping (Move towards US standard data model) Store facts so that query by value is supported: Numeric, Code lists, structured text Narrative reflects content of many EHRs but is not interoperable and should be structured when extracted

ONC Top Level Model for Semantic Interoperability Information model: Social and medical history: Problem list/encounter diagnoses: Lab results Radiology and other test results: Physical findings: Medication orders: Laboratory Orders: Immunizations: Procedures: Documents: Demographics: LOINC, HL7/OMB code set Social and medical history: SNOMED CT Problem list/encounter diagnoses: SNOMED CT / ICD-10-CM Lab results (observables): Lab LOINC Physical findings: LOINC, SNOMED CT observables Medication orders: RxNORM, SNOMED CT Laboratory Orders: LOINC Immunizations: CVX, MVX Procedures: CPT, HCPCS Documents: LOINC (Clinical) Observables Findings and Situations Findings, Events and Situations (Laboratory) Observables (Clinical) Observables (Laboratory) Observables

ONC Terminology Model for Semantic Interoperability Demographics: LOINC, HL7/OMB code set Social and medical history: SNOMED CT Problem list/encounter diagnoses: SNOMED CT / ICD-10-CM Lab results (observables): Lab LOINC Physical findings: LOINC, SNOMED CT observables Medication orders: RxNORM, SNOMED CT Laboratory Orders: LOINC Immunizations: CVX, MVX Procedures: CPT, HCPCS Documents: LOINC (Clinical) Observables Findings and Situations Findings, Events and Situations (Laboratory) Observables (Clinical) Observables (Laboratory) Observables

I2b2 Star schema: One fact per record (= One question + answer) i2b2 Observation fact Encounter Patient Observation Fact Instance_num Concept_CD Modifier_CD Provider Start_date End_date VALTYPE_CD UNITS_CD TVAL_CHAR NVAL_NUM OBSERVATION_BLOB

Desiderata for interoperability of OBSERVATION_FACTs (OFs) When possible for observables, CONCEPT_CD should align with interoperability reference standards When coded ontologies are the answer, use…MODIFIER_CD for imposing information model context Complex data records (allergy list, medication orders) should be organized into set of facts that are organized by content with MODIFIER_CD linked by INSTANCE_NUM Precoordinate results into CONCEPT_CD only if valueset is small and there is no reference observable code Choice of TVAL_CHAR, NVAL_NUM or BLOB for results should reflect datatypes; use published valuesets always for interoperability

What is the patient hemoglobin? “13.2 mg/dl” i2b2 Observation fact Encounter Patient Modifier_CD Concept_CD LOINC:2951-2 Observation Fact Provider 11/1/2016 7:30AM End_date 13.2 Mg/dl

Epic Laboratory in i2b2 LRRCLARITY_COMPONENT Laboratory results LABS_TRANSFORM.sql LRRCLARITY_COMPONENT 1534435|“Hemoglobin”|”HGB”|LOINC:718-7| Maps ORD ORDER_RESULTS Record Data

What is the patient problem? “Breast cancer” i2b2 Observation fact Encounter Patient Concept_CD SNOMEDCT:254837009 (Malignant tumor of breast) Observation Fact Modifier_CD DX|PROB\ACTIVE Provider Start_date End_date

I2b2 Metadata I2b2 client employs reference ontologies such as ONC terminologies in the user interface: displays the hierarchical structure of the terminology which may be useful for concept navigation supports queries of sets of concepts (hierarchical sub-trees) supported by boolean logic

“Severe allergic rx to aspirin with anaphylaxis” i2b2 Observation fact Encounter Patient Concept_CD SNOMEDCT:39579001 (Anaphylaxis) Observation Fact Instance:10030 Modifier_CD DX|ALGRX Provider Start_date End_date

Nebraska Medicine i2b2 Data Architecture I2b2 Information Class Standard Metadata Ontology ADT history Epic Facility Cancer registry ICD-O Clinical measurements Social history LOINC; SNOMED CT Demographics Diagnoses (Encounter dx; Problems; Past Med History) (ICD-9-CM); ICD-10-CM; SNOMED CT Encounters Epic Facility; Encounter classes Laboratory results LOINC Medications (Orders and Rx; Dispense records) RXNORM; NDC Procedures (Professional services; Hospital procedures; Procedure history ) CPT; (ICD-9-CM); ICD-10-PCS; HCPCS;

Loading an i2b2 warehouse from Epic with ONC terminology Install and maintain terminology maps in Epic and i2b2 Refresh research Clarity (Epic includes mapping data) Run ETLs and load (identified) staging tables Obfuscate dates, anonymize patients and encounters and populate (identified and de-identified) OBSERVATION_FACT tables Install and maintain i2b2 standards metadata & metadataxml for browsing and query Extract CDMV3 tables (SAS) from OBSERVATION_FACT

I2b2 Load Documentation on the Epic UserWeb https://datahandbook. epic UNMC i2b2 ETL Procedures 20160803.docx Identified (idwk) dataset procedures: Heronloader data extracts and table builds(ETLs) Blueheronmetadata metadata build De-identified (deid) dataset procedures: Heronloader extracts and table builds Blueheronmetadata CDMV3 extracts from deid Python scripts: Fact counter code

FHIR datatypes supported by Epic *Adverse reaction *Allergy/Intolerance *Conditions Devices Document Reference *Family History Goals Immunizations Lab results *Medications *Prescription *Patient *Practitioner Procedures *Substance *Social history; smoking status *Vital signs *2015 release

Questions? Comments?