Application of multiple health standards and resulting issues Daniella Meeker.

Slides:



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

Ontology Assessment – Proposed Framework and Methodology.
Data collection, integration and normalization presented to DIMACS Gil Delgado October 17, 2002.
Chapter 6 Database Design
Application architectures
AHCCCS/ASU Clinical Data Project March 17 th, 2009 Arizona Health Care Cost Containment Health System Medicaid Transformation Grant Program.
Documentation for Acute Care
July 3, 2015 New HIE Capabilities Enable Breakthroughs In Connected And Coordinated Care Delivery. January 8, 2015 Charissa Fotinos.
Selection of Data Sources for Observational Comparative Effectiveness Research Prepared for: Agency for Healthcare Research and Quality (AHRQ)
Clinical Quality Language (CQL)
Supported by the Patient-Centered Outcomes Research Institute (PCORI) Contract CDRN PopMedNet in the pSCANNER Network PMN User Meeting.
IDR Snapshot: Quantitative Assessment Methodology Evaluating Size and Comprehensiveness of an Integrated Data Repository Vojtech Huser, MD, PhD a James.
Initial slides for Layered Service Architecture
Interoperability to Support a Learning Health System HL7 Learning Health Systems Workgroup.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Ihr Logo Chapter 5 Business Intelligence: Data Warehousing, Data Acquisition, Data Mining, Business Analytics, and Visualization Turban, Aronson, and Liang.
1 Yolanda Gil Information Sciences InstituteJanuary 10, 2010 Requirements for caBIG Infrastructure to Support Semantic Workflows Yolanda.
Concept demo System dashboard. Overview Dashboard use case General implementation ideas Use of MULE integration platform Collection Aggregation/Factorization.
December 15, 2011 Use of Semantic Adapter in caCIS Architecture.
Our Joint Playing Field: A Few Constants Change Change Our missions (if defined properly) Our missions (if defined properly) Importance of Community Engagement.
CIMI + FHIR Grahame Grieve 10-August 2015 Salt Lake City.
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
Exploring the Applicability of Scientific Data Management Tools and Techniques on the Records Management Requirements for the National Archives and Records.
Query Health Operations Workgroup HQMF & QRDA Query Format - Results Format February 9, :00am – 12:00am ET.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
National Efforts for Clinical Decision Support (CDS) Erik Pupo Deloitte Consulting.
Clinical Quality Framework (CQF) Update cqframework.info Kensaku Kawamoto, MD, PhD, MHS Co-Initiative Coordinator, CQF Public Health Tiger Team August.
L SERVICE DELIVERY Pharmacy Public Health Provider Interoperability Services Data Interchange Legacy System Adapters Simulator Health Service Bus Infrastructure.
Treatment Summary University of California San Francisco Center of Excellence for Breast Cancer Care PI: Laura J Esserman MD MBA; Edward Mahoney; Elly.
Clinical Quality Language (CQL) Bryn Rhodes Chris Moesel Mark Kramer.
Ihr Logo Chapter 5 Business Intelligence: Data Warehousing, Data Acquisition, Data Mining, Business Analytics, and Visualization Turban, Aronson, and Liang.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
Building Data and Document-Driven Decision Support Systems How do managers access and use large databases of historical and external facts?
1 Incorporating Data Mining Applications into Clinical Guidelines Reza Sherafat Dr. Kamran Sartipi Department of Computing and Software McMaster University,
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 3b National and International Standards Developing.
The Practical Challenges of Implementing a Terminology on a National Scale Professor Martin Severs.
Clinical Collaboration Platform Overview ST Electronics (Training & Simulation Systems) 8 September 2009 Research Enablers  Consulting  Open Standards.
1/22/08 RTR Project Presentation to TPTF RTR Project Michael Daskalantonakis & Brian Cook.
PHS / Department of General Practice Royal College of Surgeons in Ireland Coláiste Ríoga na Máinleá in Éirinn Knowledge representation in TRANSFoRm AMIA.
Promoting excellence in social security Building on sector wide commonalities to enhance the benefits of Information.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Architecture Roadmap HSPC Specification.
Data Access Framework (DAF) Relationship to Other ONC Initiatives 1.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Open Source & Interoperability Profit Proprietary Closed Free Collaborative Open.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
Behavioral Framework Background & Terminology. Behavioral Framework: Introduction  Background..  What was the goal..
Subject Registrations Adverse Events Subject Registrations Biospecimens Lab Results IN: 1. Lab Results OUT: 1. Subject Registrations 2. Clinical Notes.
Helping the Cause of Medical Device Interoperability Through Standards- based Test Tools DoC/NIST John J. Garguilo January 25,
SAGE Nick Beard Vice President, IDX Systems Corp..
© University of Manchester Creative Commons Attribution-NonCommercial 3.0 unported 3.0 license Quality Assurance, Ontology Engineering, and Semantic Interoperability.
Rule Engine for executing and deploying the SAGE-based Guidelines Jeong Ah Kim', Sun Tae Kim 2 ' Computer Education Department, Kwandong University, KOREA.
CDA Overview HL7 CDA IHE Meeting, February 5, 2002 Slides from Liora Alschuler, alschuler.spinosa Co-chair HL7.
May 2007 CTMS / Imaging Interoperability Scenarios March 2009.
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Definition and Use of Clinical Pathways and Case Definition Templates
Semantic Web - caBIG Abstract: 21st century biomedical research is driven by massive amounts of data: automated technologies generate hundreds of.
Summary Report Project Name: Model-Driven Health Tools (MDHT)
Overall Architecture and Distributed Analysis Tools
Definition and Use of Clinical Pathways and Case Definition Templates
Unit 5 Systems Integration and Interoperability
Chapter 6 Database Design
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List aka DC
Sandy Jones, Public Health Advisor
Tomaž Špeh, Rudi Seljak Statistical Office of the Republic of Slovenia
Electronic Health Record Access Control 7
Regulatory Perspective of the Use of EHRs in RCTs
Presentation transcript:

Application of multiple health standards and resulting issues Daniella Meeker

From Platform Independent Rules to Implementation $50,000

Some Historical References on SOA approaches to Health-Research Standards CaBIG HL7 Generations (from RIM to FHIR)

Learning Health “System” Interoperability between Research and Delivery Conceptually, the data we collect in research, personally generated data, and care can be optimally collected and applied. – Predictive model for best treatment – Measuring the quality of clinical care There are no financial incentives to researchers, patients, payers, or providers to participate in such a system, so standards that would support are generally not adopted or captured in metadata Not a closed system

Learning Health System

Data Generated in Health (transactional data not originally intended for analysis) Claims and Billing Data – Streaming, Transactional – Established terminology standards for billed services, associated diagnostics, drugs Electronic Medical Record Data – Transactional, intended largely to enhance billing with electronic documents – Only data that is related to payment is reliably standardized – No API standard (yet) Personnally Generated Data – mHealth – Surveys

Challenges History of Knowledge Management Noisy Instruments Data Processing is 90% of the work Lost information Aims for the future: data useful and actionable in Real Time Metadata for Interoperability Standard for identifying triggering event for computation (workflow/time series) Standard for input data specification (data description standards) Standard for expressing data operations/computations (rules & operations standards) Standard for output data specification Standard for output data presentation trigger (operation) Metadata for Privacy & Regulatory Conformance

Logical representation of one Clinical Quality Indicator Derived From Transactional Data

What is the right level of abstraction and expressiveness for PI Rules? Reference information models and terminologies (is the right reference point the active ingredients in a drug, or do I also need manufacturer/batch information?) What is the best format for time representation? Expressiveness of rule/operations syntax (e.g. ageAtEvent vs. Event.DateTime-person.datetime(DOB)) First Order Logic Allen Interval Operations

PMML Transformations PMML defines various kinds of simple data transformations: Normalization: map values to numbers, the input can be continuous or discrete. Discretization: map continuous values to discrete values. Value mapping: map discrete values to discrete values. Text Indexing: derive a frequency-based value for a given term. Functions: derive a value by applying a function to one or more parameters Aggregation: summarize or collect groups of values, e.g., compute average

HQMF Operations Interval Logic & Event/Time Series Data – (e.g. “starts before start of”) Health-Specific Operators – (e.g. drug exposure) Health Terminology Specific Value Sets – Value Set Authority Center – Hierarchical Standards Reusable Logical Clauses

Incentives and Interfaces Cortese & Rouse, 2011 If these domains were technically and conceptually interoperable, would we improve meaningful outcomes? Research Language EHR Language (MU)Payer Terminology ??jk??jk ? Formulary Pay for Performance Prior Authorization Guidelines Patient Preferences PROs = Not funded research 90% in US PCOR CBPR mHealth Observational Studies Randomized Clinical Trials

Challenges History of Knowledge Management Capture data in structured, custom formats Analyze data in accordance with statistical standards Obfuscate useful information by publishing in plain text journals Conduct systematic reviews to create human-readable guidelines Noisy Instruments Each EHR vendor has its own implementation Each EHR user has its own adherence to use Data Processing is 90% of the work Forensics (what context, what provenance, what capture format?) Processing Data Quality Characterization & Adjudication Missing Data Imputation using internal and external data Harmonization & Standardization Top Down (Enterprise Investment) Use-case driven* Get it and forget it Incremental standardization (no incentive) Change control What is lost? Cross-organism information Molecular similarity Geographic and Socioeconomics context Methodology Aims for the future: data useful and actionable Purposeful capture of data in customizable instruments Transactional data capture Metadata for Interoperability Standard for identifying triggering event for computation (workflow/time series) Standard for input data specification (data description standards) Standard for expressing data operations/computations (rules & operations standards) Standard for output data specification Standard for output data presentation trigger (operation) Metadata for Privacy Risks Measurement of privacy loss with each access Measurement of privacy with each transformation Regulatory standards What is the right level of abstraction and expressiveness? Reference information models and terminologies (is the right reference point the active ingredients in a drug, or do I also need manufacturer/batch information?) What is the best format for time representation? Expressiveness of rule/operations syntax (e.g. ageAtEvent vs. Event.DateTime- person.datetime(DOB)) Incentives? Clinicians: Payment & Value Based Care Researchers: None Journals? Funding agency audit Consumers Mobile Devices

Local Code & Specification Repository (1)PRESENTATION (2)TRANSLATION (3)AGGREGATION (4)STORED SPECIFICATIONS Aggregation Logic Tier This layer coordinates across results produced by multiple sites. (1)Aggregate for Display (2)Aggregate for Iteration Translation Logic Tier (DAN) TBD whether this happens locally or as a service (OR BOTH). This layer reads metadata from each site and translates platform independent specifications into platform-specific executables ASSEMBLE PROGRAM S STANDARDIZE OUTPUT Authorization Tier Local authorities verify (may be automated, pre-authorized, or manual) (1)Validity of Localization (2)Access Permission (3)Verity of Results Authorize Verify Authorize Verify Authorize Verify Authorize Verify Authorize Verify Authorize Verify GLOBAL LOCAL

Some tools we’ve used ANTLR (Grammar Translation) SQL Alchemy (PIM to Queries) PMML Plug-Ins to stats packages Apache Spark Machine Learning Library Frequent Pattern Mining Methods for reverse engineering metadata

Thank You