ehealth commission meeting
play

EHEALTH COMMISSION MEETING OCTOBER 12, 2016 AGENDA Call to Order - PowerPoint PPT Presentation

EHEALTH COMMISSION MEETING OCTOBER 12, 2016 AGENDA Call to Order 1:00 Roll Call and Introductions Approval of September Minutes October Agenda and Objectives Michelle Mills, Chair Announcements 1:05 OeHI Updates SIM HIT Updates Grant


  1. EHEALTH COMMISSION MEETING OCTOBER 12, 2016

  2. AGENDA Call to Order 1:00 Roll Call and Introductions Approval of September Minutes October Agenda and Objectives Michelle Mills, Chair Announcements 1:05 OeHI Updates SIM HIT Updates Grant Opportunities, Workgroup Updates, Announcements Chris Underwood, OeHI Interim Director Carrie Paykoc, State Health IT Coordinator Commission Members New Business 1:10 Colorado Health IT Roadmap Steering Committee Laura Kolkman and Bob Brown, Mosaica Partners Master Data Management Requirements Review 2:00 Jim Younkin, CedarBridge Group Patient-Centered Data Home and Admit, Discharge, and Transfer Message 2:20 Exchange Morgan Honea, CORHIO 2:40 Public Comment Period Closing Remarks 2:50 Open Discussion, November Agenda, Adjourn Michelle Mills 2

  3. MEETING OBJECTIVES WHAT ARE WE TRYING TO ACHIEVE TODAY?  As the Steering Committee for the Colorado Health IT Roadmap, provide direction & feedback on the proposed Roadmap Objectives  Understand the current requirements for Master Data Management in Colorado  Understand the work being performed within the Patient Centered Data Home Project as it relates to ADT Messaging 3

  4. ANNOUNCEMENTS ▪ OeHI Updates Chris Underwood, OeHI Interim Director ▪ SIM HIT Updates Carrie Paykoc, State HIT Coordinator ▪ Grant Opportunities, Workgroup Updates, Announcements Commission Members 4

  5. COLORADO HEALTH IT ROADMAP STEERING COMMITTEE LAURA KOLKMAN AND BOB BROWN, MOSAICA PARTNERS

  6. COLORADO HEALTH IT ROADMAP STEERING COMMITTEE MEETING OCTOBER 12, 2016

  7. STEERING COMMITTEE AGENDA  Workshops: Follow-Up and Feedback  Principles: Review  Objectives: Discussion (handout)  Survey: Distribution  Next Steps 7

  8. ENVISIONING WORKSHOPS

  9. ENVISIONING WORKSHOP ATTENDANCE 9

  10. FEEDBACK FROM WORKSHOPS

  11. VISION AND PRINCIPLES GUIDING THE DEVELOPMENT OF THE COLORADO HEALTH IT ROADMAP

  12. VISION STATEMENT “Our VISION is a future where health and well- being are as much a part of Colorado’s way of life as our mountains, clear skies, and pristine environment.” Source: “The State of Health” Colorado’s Commitment to Become the Healthiest State Office of the Governor, April 2013 12

  13. PRINCIPLES REVIEW ▪ Supports Colorado’s health care transformation efforts ▪ Use an open and transparent process ▪ Ensure broad stakeholder participation, support, and acceptance ▪ Broad geographic and demographic considerations ▪ Leverage existing capabilities, where possible ▪ Roadmap should be achievable, actionable, and practical ▪ Health information technology supports the patients, persons, and providers in their pursuit of the Triple Aim ▪ The value of health IT and health information exchange is real and recognized ▪ Technology promotes patient/provider interaction ▪ Includes social determinates of health ▪ Focus on the “person” not the “patient” ▪ Provides guidance for priority setting

  14. DISCUSSION OF PROPOSED OBJECTIVES

  15. PROCESS OF DEVELOPING THE OBJECTIVES ▪ Reviewed many relevant documents ▪ Conducted 25 key stakeholder interviews ▪ Met with other key stakeholders and organizations ▪ Facilitated 5 Envisioning Workshops ▪ Applied knowledge of national direction as well as what other states are doing ▪ Held Colorado Health IT Roadmap project team discussions 15

  16. PROPOSED OBJECTIVES Colorado Health IT Roadmap Objectives Discussion Handout 16

  17. SURVEY

  18. SURVEY ▪ Purpose ▪ Relative importance of objectives of Colorado’s Health IT Roadmap ▪ Distribution process ▪ Master Stakeholder List ▪ Steering Committee ▪ Colorado stakeholders – BROAD distribution ▪ Distribution channels ▪ Steering Committee input 18

  19. NEXT STEPS ▪ Finalize Objectives ▪ Develop and conduct survey ▪ Publish prioritized objectives 19

  20. PROJECT CALENDAR 20

  21. THANK YOU Laura Kolkman RN, MS, FHIMSS President Mosaica Partners LKolkman@MosaicaPartners.com www.MosaicaPartners.com 727-570-8100 21

  22. MASTER DATA MANAGEMENT REQUIREMENTS REVIEW JIM YOUNKIN, CEDARBRIDGE GROUP

  23. CEDARBRIDGE TEAM Carol Robinson – Project Oversight Kate Kiefert – Senior Consultant Jim Younkin – Subject Matter Expert Pam Russell – Subject Matter Expert 23

  24. OVERVIEW  Acknowledgements  Background  Business Requirements  Use Cases  Functional Requirements  Data Sources  Data Elements  Glossary 24

  25. ACKNOWLEDGEMENTS Governor’s Office of eHealth Innovation ( OeHI) Carrie Paykoc Department of Public Health & Environment Steve Holloway (CDPHE) Office of Information Technology (OIT) Bill Stevens Department of Health Care Policy and Chris Underwood, Joel Dalzell, Financing (HCPF) Micah Jones, Nathan Culkin Colorado Regional Health Information Morgan Honea, Kate Horle Organization (CORHIO) Quality Health Networks (QHN) Marc Lassaux Colorado Community Managed Care Network Jason Greer, Chloe Bailey (CCMCN) Dave Abernethy, Center for Improving Value in Health Care Jonathan Mathieu, (CIVHC) Tracey Campbell, Ana English 25

  26. BACKGROUND  Guiding Principles  Phasing  Objectives  References 26

  27. GENERAL OBJECTIVES Increase/Improve: • information availability and interoperability within the State • Information agility • Information security Decrease: • Costs and redundancy 27

  28. GUIDING PRINCIPLES Leverage existing Focus first systems, on Medicaid Use national Begin with where those & priority standards MPI/MPD are meeting SIM best populations practices 28

  29. PROJECT PHASING Phase 2 • Medicaid • External • DORA Partners • SIM • CDPHE Phase 1 Phase 3 29

  30. REFERENCES Provider Directory Brief for the Colorado eHealth Commission Colorado Implementation Advanced Planning Document (IAPD) Update Master Patient Index Brief for the Colorado eHealth Commission Comprehensive State Health Information Management Strategy Provider directory work products of the Clinician Data Consortium 30

  31. BUSINESS REQUIREMENTS SAMPLES Identify and Link provider Aggregate for Support care differentiate billing licensure analysis/reporting coordination provider from information servicing provider Phase 1 Reduce duplicate Improve patient Maintain source of Improve patient data capture attribution data matching rates Phase 2 Improve quality / Geo-mapping Phase 3 efficiency of data Link claims and Role-based access solution to identify for program clinical data workforce shortages evaluation Increase data Support consistent One stop source of Improve data quality reliability and eCQMs across comprehensive from sources integrity programs provider information 31

  32. USE CASE SAMPLES Emergency Connecting Medical Practice integration Quality measurement Preparedness: Disaster Homes and between behavioral where “metric follows assessment, response Neighborhoods health & primary care the client” and recovery Link providers to various Connect clients with Improve linkage Phase 1 Manage client networks (practices, non-health provider between CDPHE enrollment health systems, ACOs, community providers and MMIS data payers, etc.) Phase 2 Central source of truth Improve patient/client Providers to enter and Link 80+ data sources for provider updates Phase 3 attributions across maintain their connected (or in (i.e. Addresses, Panel systems information in one place process) to BIDM size, Office hours, Languages, etc.) Link public health Medicaid and Non- Provider data Evaluate utilization registries to MMIS to Medicaid Provider maintenance variances provide actionable communications health information 32

  33. FUNCTIONAL REQUIREMENT SAMPLES Data must be searchable, Highly accurate, Unique identification query-able, and integrate- configurable matching Entity Level and Individual information in the form of able with other data engine to ensure matching Level Provider Directory a “golden record” sources accuracy System must be secure, Ability to interface with Store individual encounter MPD must support scalable, reliable and existing and future information at the MPI one-to-many linkages sustainable systems level Record quality must be Systems should be agile Support an enterprise easy to review / verify Capability to audit activity and support a modular “common key” as well as against a generated across entire system architecture separate, multiple MRNs reliability score Ability to share MPI and Ability to accept data Ability to notify all Digital certificate / public store identifiers from from disparate data systems when new key discoverability other systems sources patients are added 33

Recommend


More recommend