“TO-BE” OR NOT “TO-BE” MITA 3.0 SELF-ASSESSMENT

A N I N D U S T R Y PA N E L D I S C U S S I O N

“TO-BE” OR NOT “TO-BE” MITA 3.0 SELF-ASSESSMENT

AGENDA

•  Introduction of Panel •  MITA 3.0 Overview •  Panel Discussion

v  MITA 3.0 State Self-Assessment Approach v  Extending MITA across the Medicaid Enterprise v  Laying a Foundation for Interoperability

•  Questions & Answers

INTRODUCTION OF PANEL

•  Karen Walsh – CMS Moderator •  Jim Wang – State of Arizona •  Randy Canoy – State of Oregon •  Ed Dolly – State of West Virginia •  Brian Erdahl – Deloitte •  Patti Garofalo – CSG Government Solutions •  Marie Schwartz – Medicaid Learning Center (MLC) •  Robert Milk – SLI Global Solutions

MITA 3.0 OVERVIEW

•  Initial Release – March 2012 •  Eligibility and Enrollment – August 2012 •  Seven Standards & Conditions •  Business Architecture

v  10 Business Areas v  80 Business Processes

•  Information Architecture •  Technical Architecture •  MITA 3.0 State Self-Assessment MUST be completed

within 12 months of E&E release

PANELS

•  MITA 3.0 SS-A Approach v  Jim Wang – State of Arizona v  Brian Erdahl – Deloitte v  Ed Dolly – State of West Virginia v  Marie Schwartz – Medicaid Learning Center

•  Extending MITA across the Medicaid Enterprise v  Randy Canoy – State of Oregon v  Patti Garofalo – CSG Government Solutions

•  Laying a Foundation of Interoperability v  Randy Canoy – State of Oregon v  Patti Garofalo – CSG Government Solutions

MITA SS-A APPROACH

•  Placeholder for Panel Slides from AZ

WV MITA 3.0 SS-A APPROACH

Ed Dolly – State of West Virginia Marie Schwartz – MLC Multi-Phase Approach – discussion today •  Phase I: Prepare •  Phase II: Leverage/Recycle •  Phase II: Conduct


•  MITA 3.0 SS-A Companion Guide •  Prepare for SS-A Project •  Conduct Business Architecture SS-A •  Conduct Information Architecture SS-A •  Conduct Technical Architecture SS-A •  Conduct Seven Standards and Conditions SS-A


•  Prepare for the SS-A •  Set up MITA 3.0 Repository using the MITA

Management Portal (MMP) •  Leverage from MITA 2.0/2.1 effort •  Populate MMP with document templates •  Analyze BP templates from previous effort •  Transfer applicable information from MITA 2.0/2.1

effort into new MITA 3.0 templates •  Determine remaining work sessions/interviews to

populate MITA 3.0 templates (and scorecards)


•  Set up MITA 3.0 Repository using the MITA Management Portal (MMP) •  Design Repository •  Permissions Settings •  Stakeholder Analysis •  Ownership Assignment (BA, BC, and BP)


•  Leverage from MITA 2.0/2.1 effort •  Analyze BP templates from previous effort •  Transfer applicable information from MITA

2.0/2.1 effort into new MITA 3.0 templates


•  Determine remaining work sessions/interviews to populate MITA 3.0 templates (and scorecards) •  Information gathering interviews •  Information gathering work sessions

EXTENDING MITA ACROSS THE MEDICAID ENTERPRISE

•  No longer just MMIS v  Regulatory Mandates – ARRA, HITECH, ACA

•  Expanded data standards for Health Care and Health Insurance Industries v  ONC, NwHIN, NIEM

•  Expanded technological advancements v  Business Rules Engines, Cloud Computing Concepts, and

emerging standards

•  Expanded enterprise architecture principles to promote transformation

EXTENDING MITA ACROSS THE MEDICAID ENTERPRISE

•  MITA and SAMHSA Framework v  80 MITA Business Processes v  94 Combined Business Processes v  80% Shared Capabilities v  Business Process applicable to the Healthcare Enterprise

•  MITA and SAMHSA to Assess Healthcare v  Physical Health v  Mental Health v  Dental Health

LAYING A FOUNDATION FOR INTEROPERABILITY

•  Interoperability Condition v Ensure seamless coordination and integration with HIE, HIX,

public health agencies, human services programs, and community organizations

•  Makes it possible for two separate solutions to communicate •  Key Principles

v Shared business services v Standardized messaging and communication protocols v Exchange data across health and human services

enterprise v Maximize value and minimize cost


•  Recipients, Clients, Beneficiaries typically receive more than one service v  Health – Physical, Mental, Dental v  Nutritional – SNAP, WIC v  Public Assistance – TANF v  Employment Assistance – Work Programs, Unemployment, Training Programs v  Child Care v  Housing


•  Siloed Systems and Programs v  Narrow range of services v  Redundant data entry v  Duplicate Processing v  Inability to exchange information v  Susceptibility to duplicate and fraudulent payments v  Complicated and costly operations v  Directly impacting service and delivery to the client


•  Key Questions to Ask Your Team v What are you trying to accomplish? v How important is the ability to customize or extend business

processes to your ability to innovate?

•  Keys Questions to Ask Your Vendor v Does your vendor use an open standard development

platform? v How flexible is the technology? v Does the solution deliver integration and interoperability?

QUESTIONS & ANSWERS

??????

PANEL CONTACT INFO

•  David Hinson – CMS Moderator; [email protected]

•  Jim Wang – State of Arizona; [email protected]

•  Randy Canoy – State of Oregon [email protected]

•  Ed Dolly – State of West Virginia [email protected]

•  Brian Erdahl – Deloitte [email protected]

•  Patti Garofalo – CSG Government Solutions [email protected]

•  Marie Schwartz – Medicaid Learning Center; [email protected]

•  Robert Milk – SLI Global Solutions [email protected]

THANK YOU

“TO-BE” OR NOT “TO-BE” MITA 3.0 SELF-ASSESSMENT

Documents

Transcript of “TO-BE” OR NOT “TO-BE” MITA 3.0 SELF-ASSESSMENT