Page 1 A Brief Review of CIMI and HSPC Stanley M Huff, MD Chief Medical Informatics Officer Intermountain Healthcare

Slides:



Advertisements
Similar presentations
National HIT Agenda and HIE John W. Loonsk, M.D. Director of Interoperability and Standards Office of the National Coordinator Department of Health.
Advertisements

FOUNDATION 1: CIMI REFERENCE MODEL. CIMI Reference Model - Core.
FEBRUARY 25, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Healthcare Services Platform: Goals and Vision.
Healthcare Healthy Community Information for a Integrating Healthcare Healthcare Overview of HSPC Awareness-Building, Marketing and Communications Activities.
HSPC Relationship to Other Initiatives
T echnology I nformatics G uiding E ducation R eform © 2011 The TIGER Initiative Foundation available for your use with citation.
Population Management & Reporting. Federally-designated Regional Extension Center for the State of Missouri  University of Missouri:  Department of.
JULY 31, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE The Healthcare Services Platform Consortium.
MAY 1, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Healthcare Services Platform: Goals and Vision.
FEBRUARY 5, 2015 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Meeting Introduction.
Open Source Clinical Decision Support Emory Fry, MD Cognitive Medical Systems January 14, 2014.
CONFUSED? DON’T BE. IT’S ACTUALLY REALLY STRAIGHTFORWARD. RICK FREEMAN FEBRUARY 4, 2015 The HSPC Tier 1 & Tier 2 Technical Specification Explained.
The HITCH project: Cooperation between EuroRec and IHE Pascal Coorevits EuroRec 2010 Annual Conference June 18 th 2010.
AUGUST 21, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Relationships to other Organizations and Activities.
FEBRUARY 4, 2015 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Modeling and Terminology.
AUGUST 21, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Meeting Introduction.
A Robust Health Data Infrastructure P. Jon White, MD Director, Health IT Agency for Healthcare Research and Quality
HSPC Meeting Washington DC, June 18, 2015
Community Information Technology Engagement (CITE): Program Overview
Riki Merrick, APHL Anna Orlova, PhD, PHDSC Lise Stevens, FDA Nikolay Lipskiy, MD, DrPH, MBA – CDC CSTE Conference June 5 th, 2012 The findings and conclusions.
JULY 29, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Update.
Logistics I need to leave by 9:30 am, I will be back tomorrow (Tuesday) Continental breakfast both days Buy lunch from the cafeteria Buy coffee or treats.
Initial slides for Layered Service Architecture
TECHNICAL. The iMDHT technical team Shared Technical Objective: Toolkit that lowers the bar and accelerates development of innovative applications Shared.
Governance & Organizational Structure Paula Autry President, Mount Carmel East Mount Carmel Health System.
AUGUST 22, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Healthcare Services Platform: Business Entity.
HL7 Webinar: Mobile Health Chuck Jaffe Austin Kreisler John Quinn 19 March 2012.
CIMI + FHIR Grahame Grieve 10-August 2015 Salt Lake City.
1 Dianne M. Reeves Report: HL7 25 th Annual Plenary and WGM September 11 – 16, 2011 San Diego, California.
Working Together to Advance Terminology Tooling Presentation to OHT Board, Birmingham Jennifer Zelmer & Karen Gibson.
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.
HIT Policy Committee NHIN Workgroup Introductory Remarks David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of Commerce,
© CDISC 2011 Joint Initiative Council 18 October 2011 Bron Kisler, VP, Strategic Initiatives, Current JIC Leader Rebecca D. Kush, PhD, President and CEO,
Lisa A. Lang, MPP Assistant Director for Health Services Research Information Head, National Information Center on Health Services Research and Health.
Data Gathering HITPC Workplan HITPC Request for Comments HITSC Committee Recommendations gathered by ONC HITSC Workgroup Chairs ONC Meaningful Use Stage.
Modeling Options HSPC Meeting June 17, 2015 Washington DC.
ONC FACA HIT Standards Committee Clinical Operations Workgroup Hearing on Barriers & Enablers for Medical Device Interoperability March 28, 2011 ~ Washington,
FEBRUARY 6, 2015 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Meeting Planning and Next Steps.
HIT Standards Committee Clinical Operations Workgroup Report Jamie Ferguson, Chair Kaiser Permanente John Halamka, Co-chair Harvard Medical School 20 August,
By Rick Freeman THE HEALTHCARE INNOVATION ECOSYSTEM HiMSS 2015 & Development Sandboxes Update President & Founder iSalus Consulting June 19, 2015.
MED INF HIT Integration, Interoperability & Standards ASTM E-31 January 14, 2010 By Imran Khan.
Briefing: HL7 Working Group Meeting Update for the VCDE Community Dianne M. Reeves Associate Director, Biomedical Data Standards NCI CBIIT VCDE Meeting.
OpenHIE Improving health for the underserved. The Open Health Information Exchange (OpenHIE) Community: A diverse community enabling interoperable health.
Public Health Data Standards Consortium
HIT Standards Committee NHIN Workgroup Introductory Remarks Farzad Mostashari Office of the National Coordinator for Health IT Douglas Fridsma Office of.
January 26, 2007 State Alliance for e-Health January 26, 2007 Robert M. Kolodner, MD Interim National Coordinator Office of the National Coordinator for.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
Public Health Data Standards Consortium
Adoption and Use of Electronic Medical Records (in Federally Qualified Health Centers) and Supporting an ASP Community Care Network of Virginia, Inc.
Arizona Health-e Connection November 17, 2015 Stanley M. Huff, MD THE HEALTHCARE INNOVATION ECOSYSTEM SHARING KNOWLEDGE AS EXECUTABLE.
Mariann Yeager, NHIN Policy and Governance Lead (Contractor) Office of the National Coordinator for Health IT David Riley, CONNECT Lead (Contractor) Federal.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
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.
Office of the National Coordinator for Health Information Technology ONC Update for HITSP Board U.S. Department of Health and Human Services John W. Loonsk,
Shaun Grannis, MD, MS, FAAFP FACMI Biomedical Informatics Scientist Regenstrief Institute / Indiana University The Impact of Interoperability / HIE to.
SNOMED CT Vendor Introduction 27 th October :30 (CET) Implementation Special Interest Group Tom Seabury IHTSDO.
EHealth Initiative Business and Clinical Motivator Work Group January 21, :00 p.m. EDT.
1 CDC Health Information Exchange (HIE) Accelerating State-wide Public Health Situational Awareness in New York Through Health Information Exchanges August.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
HSPC Terminology and Information Model Initiative Susan Matney, PhD, RNC-OB, FAAN (Initiative Lead) Stan Huff, MD, FACMI, FHL7 11/6/2016.
eHealth Standards and Profiles in Action for Europe and Beyond
Open Platforms for Innovation
Public Health Laboratory Data (PH-Lab) Exchange Project: Overview
VERMONT INFORMATION TECHNOLOGY LEADERS
Introduction to the HSPC Sandbox
HL7 FHIR Connectathon Care Planning & Management Track
ONC Update for HITSP Board
Presentation transcript:

Page 1 A Brief Review of CIMI and HSPC Stanley M Huff, MD Chief Medical Informatics Officer Intermountain Healthcare

Page 2 Introduction Stanley M. Huff, MD Professor (Clinical) Department of Biomedical Informatics Chief Informatics Officer, Intermountain Healthcare Chair of the Board of HL7 Member of the ONC HIT Standards Committee Co-chair of the LOINC Committee Chair of the Board of HSPC Leader of CIMI

Page 3 CIMI The Clinical Information Modeling Initiative (CIMI) is a community of interest that is producing detailed clinical information models to enable interoperability of health care information systems CIMI models are free for use for all purposes See for more detailshttp://

# 4 Graphic Presentation of a Detailed Clinical Model data 138 mmHg SystolicBP SystolicBPObs quals data Right Arm BodyLocation data Sitting PatientPosition

Page 5 Clinical Information Modeling Initiative Mission Improve the interoperability of healthcare systems through shared implementable clinical information models. (A single curated collection.)

Page 6 Clinical Information Modeling Initiative Goals Create a shared repository of detailed clinical information models Using an approved formalism – Archetype Definition Language (ADL) – Archetype Modeling Language (AML) Based on a common set of base data types With formal bindings of the models to standard coded terminologies Repository is open to everyone and models are licensed free for use at no cost

Page 7

# 8 Access to the models Browse and download models CIMI models – Intermountain models –

THE HEALTHCARE INNOVATION ECOSYSTEM An Opportunity to Foster Truly Interoperable Health Care Applications

OUR MISSION Improve health by creating a vibrant, open ecosystem of interoperable applications

OUR VISION Be a provider-led organization that accelerates the delivery of innovative healthcare applications that improve health and healthcare

FHIR Profiles from CIMI Models (uing standard terminology) Standards Based Services - HIMSS

Apps that address specific focused problems… Provider-facing services Focused decision support Visualization Disease management Specialty workflows National Shared Services Genomic testing & CDS Pharmacogenomic screening CDC Ebola screening? CDC immunization forecaster Prior Authorization / Appropriateness App 1 EHR App 2 App 3 Like Google Maps…

Apps that enable data sharing… Next-gen Interoperability Population Health integration HIE integration Data capture for research Clinical Trial recruiting Quality Repositories EHR 2 App 1 EHR 3 EHR 1 Like Facebook…

Apps that empower patients / consumers… Apps as Prescriptions Chronic disease management Pt-Provider Communication Remote monitoring Outcome capture & Clinical Effectiveness Monitoring SMART Phone App Pop Health EHR Like ???? …

HSPC Technology Assumptions (already decided) Services – FHIR Generate FHIR profiles from existing model content Data modeling CIMI models Terminology LOINC, SNOMED CT, RxNorm, HL7 tables EHR Integration – SMART 16

HSPC History HSPC was incorporated as a not-for-profit corporation on August 22, 2014 Meetings May 2013 Salt Lake City August 2013 in Phoenix January 2014 Salt Lake City May 2014 in Phoenix July 2014 Salt Lake (Technical modeling meeting) August , Washington DC, hosted by IBM February 4-6, New Orleans, Louisiana, hosted by LSU June 17-19, Washington DC August 10-13, Salt Lake City September 28-30, Phoenix (tentative) 17

Essential Functions of the Consortium Select the standards for interoperable services Standards for models, terminology, security, authorization, context sharing, transport protocols, etc. Modeling: SNOMED, LOINC, RxNorm – FHIR Profiles – do it together Publish the models, and development instructions openly, licensed free-for-use Provide testing, conformance evaluation, and certification of software Gold Standard Reference Architecture and its Implementation We will work with an established company to provide this service Fees that off set the cost of certification will be charged to those who certify their software Implementation of the standard services by vendors against their database and infrastructure Everyone does not have to do every service There must be a core set of services that enable a marketplace 18

Other Functions of the Consortium Participation in “other” functions is optional for a given member Enable development “sandboxes” Could be provided by companies or universities Could be open source or for-profit Set up a vendor and provider neutral “App Store” Many companies already have their own app stores Vendor certification that a given application can be safely used in their system Accommodate small companies or individuals that won’t have their own app store Create a business framework to support collaborative development Pre-agree on IP, ownership, co-investment, allocation of revenue Try to avoid unique contracts for each development project Provide a way for people to invest (Venture capital) in HSPC technologies 19

Opportunities Quality and disease specific repositories Sharing of data for patient care Sharing of clinical decision support and other applications Patient engagement

HSPC is about more than just data virtualization

SOA Services Layers 22

SOA Guiding Principles 23 Three tiered services model Maintain atomic services that are consistent in performance and behavior Can be administered once in a framework Can be orchestrated under a true SOA governance Can be consumed by anyone implementing the HSPC reference architecture Can be addressed by synchronous and asynchronous service requests Are implementable out of the box Are supportable and documented to a standard Provide HSPC supported services as open source

Principles Not-for-profit entity There could be an associated for-profit entity some day Provider led Simple majority of providers on the Board of Directors All organizations will have equal influence and opportunity Intermountain and Harris will not be “special” Start small, be effective, and then grow We want to allow everyone that is interested to participate Allow diverse strategies and participants Open source and for-profit One person business up to multi-national corporations Healthcare providers and healthcare software developers Students and professional software engineers 24

Principles (continued) Initially, focus on the minimum set of standards and technology Increase options as we gain experience and success HSPC is not producing software (mostly) HSPC members or groups of members produce software HSPC may need to provide a reference implementation for purposes of certification No “central planning” by HSPC of app development Participants decide what they want to build and invest their own resources We DO need to agree about the minimum set of services that will enable a marketplace 25

Sample of Participants HL7 FHIR – Grahame Grieve SMART – Josh Mandel Cerner – David McCallie, Marc Overhage Epic – Janet Campbell VA – Jonathan Nebeker, Paul Nichol openEHR – Thomas Beale Open Health Tools – David Carlson Harris – Vishal Agrawal Intermountain Healthcare Systems Made Simple – Viet Nguyen LSU – Frank Opelka, Wayne Wilbright, John Couk Center for Medical Interoperability – Todd Cooper RelayHealth – Arien Malec NLM – Clem McDonald Infocare Healthcare – Herb White Mayo Clinic – Cris Ross Clinical Architecture – Shaun Shakib Cognitive Medical Systems – Doug Burke IBM – Jeff Rogers, Dennis Leahy ASU – Aziz Boxwalla, Robert Greenes Regenstrief Institute – Douglas Martin 26

Key Organizational Relationships (not exhaustive)

Argonauts Don’t know for sure A call is planned to discuss the relationship Work together on HIMSS demonstrations? Work together to create industry wide consensus for profiles to be used for “true” interoperability?

HL7 HSPC will use HL7 FHIR for data services CIMI plans to become a part of HL7 HSPC will use HL7 as the forum for creating industry wide agreement about: Detailed profiles for true interoperability Consensus of professional and clinical bodies about data that needs to be collected and shared (workflow or process interoperability)

SMART HSPC will use SMART as a EHR integration strategy HSPC will work together with SMART on all activities of mutual interest We will create a written document (MOU?) to describe the relationship between the two organizations

Center for Medical Interoperability Work for support of CIMI and HSPC as part of C4MI technical programs Possible activities Host a vendor and provider neutral app store Create a reference implementation of HSPC services Host a development sandbox Logistic support Meetings, websites, publicity Host a model repository (and other knowledge artifacts) Support online terminology services Tool development Conformance testing and certification

HSPC Internet Sites Wiki: Healthcare+Services+Platform+Consortium Healthcare+Services+Platform+Consortium Website: 32

Q & A