Clinical Information Interoperability Council (CIIC) Providing a Shared Repository of Detailed Clinical Models for all of Health and Healthcare

Similar documents
Integrating RAPID Common Data Elements and Modeling with the Goals of HSPC. MDEpiNet RAPID Sept 14, 2016 Stanley M. Huff, MD

What is a Standards-based Healthcare Services Platform, and Why should it Matter to You?

The Future of Health Data Interoperability is on FHIR: the Argonaut Project

Digital Quality Summit. Charles Jaffe, MD, PhD CEO Health Level 7

CDA vs Archetypes: Use Cases March Tomaž Gornik, Co-founder and CEO

CIMI/IHTSDO DCM tooling ecosystem thoughts

Agenda. Background SNOMED International Collaborations developments Information models Extensions

Enhancing Laboratory Data Infrastructure to Access Real-World Evidence (RWE) for in vitro Diagnostics (IVDs): Three Models for RWE Use

STI ecr Learning Community: Webinar 2. April 27, 2017 Noon 1 p.m. EDT

HL 7 FHIR and the Future of Interoperability. January 25, pm 3pm ET

Achieving Clinical Transformation with an Interoperable Health IT Infrastructure

FHIR, Interoperability, and the World of Enablement

Clinical Quality and Policy

Reflections on Improving the Interoperability and Use of the Data Dividend

HL7 Newsletter Article for Sep 2018

Integrating the Healthcare Enterprise International Cardiology Domain Update. Webinar Series 2017

HEMIC Project: Design of a Clinical Information Modelling Tool Based on ISO13972 Technical Specification

Using HL7 FHIR to support interoperability: Lessons from Intermountain Healthcare

Dr. Karen DeSalvo Office of the National Coordinator for Health Information Technology U.S. Department of Health and Human Services

CDISC Controlled Terminology across the Clinical Trial Continuum. Bay Area Implementation Network 6 March 2008

HL7 Plenary EHR In Canada

openehr & clinical modelling

J P Systems, Inc

More Than You Think. HL7 is people, HL7 is ideas, HL7 is collaboration

GLOBAL HEALTH INFORMATICS STANDARDS FOR NATIONAL HEALTH INFORMATION

2016 Technical Update. August 2016

SOA at Intermountain Healthcare: New IDEAs and Progress Towards a New Platform SOA in Healthcare July 13, 2011 Stanley M. Huff, MD

Think Locally, Connect Nationally

HL7 Overview. Byoung-Kee Yi, PhD. Samsung Medical Center Digital Health Dept, SAIHST, SKKU. HL7 Korea ISO/TC215 Health informatics

Section D. HIT Standardization Phases and Entities (Continued)

Extending the EHR Platform with Open Apps and Services

A FHIR Enabled Ecosystem for Health Information Sharing

By Shahid N. Shah, CEO

Technical White Paper. Metadata management. Ontologies, measures, registries, and patient attribution

PCORI Methodology Standards: Academic Curriculum Patient-Centered Outcomes Research Institute. All Rights Reserved.

Data Quality in the Real World: Ensuring Integrity across the Medical Device Lifecycle

THE IMPACT OF THE AFFORDABLE CARE ACT (ACA) ON CANCER RESEARCH, CARE, AND PREVENTION

Integrating Standards to Achieve Semantic Interoperability. Dr Ken Lunn Director of Data Standards

Evolve from Master Patient Indexing to Identity Interoperability

National Program of Cancer Registries Advancing E-cancer Reporting and Registry Operations (NPCR-AERRO)

ELECTRONIC MEDICAL RECORDS. Selec g and zing an Electronic Medical Records. A WHITE PAPER by CureMD. CureMD Healthcare

The Transformation of Clinical Research. Health Information Technology Summit. Integration of Policy and Process with Information Technology

HL7 EHR Immunization Functional Profile Project. Gary L. Dickinson Mark Janczewski, MD 8 August 2016

RSNA Image Share Validation Testing

Industry Perspective Inside DXC s Digital Health Platform

Disease Specific Data Standards: Case Studies in TB and Cardiology

FHIR Sparking Innovation In Health Information Sharing

What s New in HL7. W. Ed Hammond, PhD Director, Duke Center for Health Informatics FACMI, FAIMBE, FHL7, FIMIA Secretary, HL7; Chair-Emeritus, HL7

DENOMINATOR: All final reports for patients, regardless of age, undergoing a CT procedure

CDISC Global Update. President and CEO, CDISC

HL7 C-CDA Consolidated Clinical Document Architecture

RHAPSODY VISION & ROADMAP FIORA AU, TIM WHITTINGTON OCT 2017

GLEE A Model-Driven Execution System for Computer-Based Implementation of Clinical Practice Guidelines

25 Skills a Healthcare Solutions Developer Should Have

Registry Assessment of Peripheral Interventional Devices (RAPID) Used to treat infrainguinal arterial occlusive disease

CDISC and Clinical Research Standards in the LHS

CDISC/TransCelerate Collaboration and TransCelerate work streams. -Clinical Data Standards -Common Protocol Template -esource

StartUp America Challenge. Improvements to Information Structure Data Standards, Quality & Interoperability. Part 3 FINAL PROJECT PLAN

Insights into the BMBF Medical Informatics Initiative SMITH Consortium


Organization Meeting & Overview

Enabling Knowledge-driven Care at Scale through CDS Hooks and the FHIR Clinical Reasoning Module Panel S64

Interoperability for clinical research Observational Health Data Sciences and Informatics (OHDSI)

Whole Interoperability

Health Data Management

Thoughts from the. Data Quality Core. Phenotypes, Data Standards & Rachel Richesson, PhD, MPH Duke University School of Nursing

Interoperability Robin Breslin

Immunization Information System Interoperability

Registry Assessment of Peripheral Interventional Devices (RAPID)

FHIR Interoperability: Point of Care Healthcare Apps in the Real World

PCORnet Front Door/ GPC Research Opportunity Assessment Process. Thursday 1:00 2:30 PM

Big Data & Clinical Informatics

SNOMED CT in the Age of Precision Medicine

Duane Steward, DVM, MSIE, PhD Nemours, Chief Computer Scientist for Clinical Informatics University Central Florida, Assistant Professor

Inside IHE: Patient Care Device Webinar Series 2018

Janus Clinical Trials Repository: Modernizing the Review Process through Innovation

HIT Policy Update. A Complimentary Webinar From healthsystemcio.com Sponsored by OnBase by Hyland

SALUS: Scalable, Standard based Interoperability Framework for Sustainable Proactive Post Market Safety Studies

Proposed Algorithm with Standard Terminologies (SNOMED and CPT) for Automated Generation of Medical Bills for Laboratory Tests

Report from the EHR Clinical Research Tiger Team

medicines, improving the health of people around the world.

CDISC Journal. Organizing and Accelerating the Clinical Research Process from the Beginning: The CDISC Protocol Representation Model and Toolkit

FHIR. FHIR : Fast Healthcare Interoperability Resources (Pronounced Fire ) The hottest thing interoperability this year

Federal Health Architecture: Government Collaboration in Action. John Forrester, Program Manager Neil Efrom, Enterprise Architect

Extreme Makeover - ICD-10 Code Edition: Demystifying the Conversion Toolkit

Project Scope Statement for: EHR- S FM + PHR- S FM + RM- ES FP on FHIR

Clinical Data Architecture for Business Intelligence and Quality Reporting

The Impact of Interoperability / HIE to a Health System s Strategic Roadmap: Lessons from the OpenHIE Project

CDISC Journal. Current status and future scope of CDISC standards. By Rebecca D. Kush, President and CEO, CDISC. 1. Introduction

The Payer/Provider Perspective on Interoperability Da Vinci

Organizational Track Definitions, Assumptions and Issues

Leveraging of CDISC Standards to Support Dissemination, Integration and Analysis of Raw Clinical Trials Data to Advance Open Science

Has no real or apparent conflicts of interest to report.

Working with Health IT Systems is available under a Creative Commons Attribution-NonCommercial- ShareAlike 3.0 Unported license.

Using Real-World Evidence (RWE) for Regulatory Decision Making and Pracatice. Danica Marinac-Dabic, MD, PhD Director, Division of Epidemiology

Cypress: New Features, Clinical Quality Language Support, and Burden Reduction

Pre- Decisional Working- Document; Not for Official Use EHR-S FM Release-3 Summer Prototype Plan 7/13. R2 Ballot Reconciled

Incorporating Evidence from Clinical Experience into Regulatory Decision- Making: A Pragmatic Approach to Randomization in the Clinical Setting

Is Your Healthcare Analytics System Missing the Gold in Your EHRs? A Special Report for Healthcare Executives

Governing Interinstitutional

Transcription:

Clinical Information Interoperability Council (CIIC) Providing a Shared Repository of Detailed Clinical Models for all of Health and Healthcare NIH HCS Collaboratory and PCORnet December 1, 2017 Stanley M. Huff, MD W. Ed Hammond, PhD 1

Agenda Why? What we want to do How? Questions, comments, and discussion

Why?

Why? To help people live the healthiest lives possible.

Patient 5

Core Assumptions The complexity of modern medicine exceeds the inherent limitations of the unaided human mind. ~ David M. Eddy, MD, Ph.D.... man is not perfectible. There are limits to man s capabilities as an information processor that assure the occurrence of random errors in his activities. ~ Clement J. McDonald, MD 6

Eileen

Why? We need to Provide better care By sharing executable clinical decision support modules Decrease cost By providing better care By eliminating point-to-point mapping of data elements Make clinicians and patients happier Provide accurate computable data as the foundation of a learning health system (LHS)

What we want to do

What We want to create ubiquitous sharing of standardized data across the breadth of medicine for: Direct patient care Patient entered data and outcomes Research and learning Public health Clinical trials Data from devices Post market surveillance Quality and disease specific registries Billing and health administration Any where that we share health related data and information..

Make a shared repository of Detailed Clinical Models (aka a logical models) SystolicBPObs SystolicBP data quals 138 mmhg LOINC or SNOMED Observable BodyLocation BodyLocation data Right Arm PatientPosition PatientPosition SNOMED CT data Sitting 11

What The models are used during software development, which makes the process much faster and more efficient, and it insures that the references to data in the software adhere to the agreed standards.

Logical Model Development Lifecycle Standards Infusion Core Reference Model SystolicBPObs data 138 mmhg quals SNOMED CT LOINC RxNorm SystolicBP LOINC or SNOMED Observable HL7 FHIR CDISC CEMs BodyLocation BodyLocation HL7 CDA DCMs datamodel Right Review Arm Translators X12 CDA Templates openehr Archetypes PatientPosition Repository of Shared Models datain an Sitting approved Formalism PatientPosition SNOMED CT NCPDP HL7 V2 ISO EN 13606 Archetypes FHIM Models FHIR Resources Initial Loading of Repository Model Dissemination

The Interoperable App Development Process Domain Analysis Create Logical Models (CIMI) Approve Models Model Repository Project Needs Pediatric Growth Chart Neonatal Bilirubin Comm Acq Pneumonia OPA Data Collection MQIP ACC registries Conformance Testing Terminology Server (SOLOR) Create Software (Apps, Services, CDS) Create Physical Artifacts (FHIR Profiles) Artifact Repository (FHIR Profiles)

The ultimate value of detailed information models Software is developed much faster Clinical knowledge is contained in the models Much easier for software engineers The data used in the applications is completely conformant to standards, leading to semantic interoperability If you follow the SMART on FHIR development strategy, your software can be shared with any system that supports the approved standards

Three related but very different questions What data should be collected? (part of domain analysis) It will be different for different situations How should the data be modelled? Two fields or one (the degree of pre and post coordination) What does the data mean? How do we make computable definitions for diabetes mellitus, myocardial infarction, heart failure, chronic renal failure, etc.

How?

How All stakeholders agree to work together Have practicing front-line clinicians direct the work Capitalize on the work in existing projects Agree to use a common format for representing the models Use and share common tools to create the models Share the models through an open internet accessible repository Approve one preferred model for a given kind of data in a given situation Use existing models whenever possible

CIIC 2017 Meeting Overview July 13, 2017

Summary of the July 13 th meeting in Bethesda Keynote speaker Don Rucker, MD (National Coordinator for HIT) About 120 attendees Representing AAN, AAO, ACOG, ACS, ACC, ACP, APTA, ANA, FDA, CDC, NCI, AHRQ, NIAID, DoD, VA, PCPI, AMIA, SPM, HIMSS and many other organizations Meeting outcomes CIIC should continue Create mission, vision, a plan for initial governance Develop a mailing list and a discussion forum Projects ACOG OPA FPAR, Cancer DTR, MDEpiNet RAPID, Vital Signs, Skin and Wound Assessment, PCPI Registries on FHIR, Upcoming meetings December 5-7 in New Orleans with HL7 Partners in Interoperability January 10-12 at LDS Hospital in Salt Lake City

The END (or maybe the beginning?) Contact Information: Stan.Huff@imail.org 21