1. MITA -- A Vision of Evolving Medicaid Systems The View from CMS Rick Friedman Director, Division of State Systems Centers for Medicare & Medicaid Services April 18, 2006

2. Growth in Medicaid Beneficiaries Millions of Medicaid Beneficiaries 0 10 20 30 40 50 60 196519701975198019851990199520002004

3. MEDICAID: People and Money PeopleMoney U.S. Totals294 million$1.54 trillion Medicaid52 million (1 out of every 6 Americans) $305 billion (1 out of every 5 health care dollars) Medicare42 million$ 297 billion Medicaid and Medicare 87 million*$602 billion *About 7 million duals have been subtracted from the total to avoid double-counting Source: Kaiser Commission, 2005

4. Growth in Program Complexity ► Waivers ► HIPAA—Privacy, NPI, etc. ► Focus on Quality ► Rising Concerns re Privacy and Security ► Duals ► Medicare Part D

5. What Is MITA? ► MITA is a CMS IT initiative to transform the concept of today’s State-based claims processing systems into an enterprise-wide backbone architecture capable of addressing tomorrow’s Medicaid needs, as well as today’s. 1. IT Architecture Framework  Consolidation of principles, business and technical models and guidelines that form a template for states to use to develop their own enterprise architectures 2. Planning Guidelines  Assistance to States to define their own strategic MITA goals and objectives consistent with CMSO expectations and requirements 3. Processes  For States to use in adopting the MITA framework through shared leadership, partnering and reuse of solutions

6. What Are MITA’s Goals? ► Help Medicaid managers improve health care outcomes ► Align with Federal Health Architecture ► Ensure patient-centric views not constrained by organizational barriers ► Make use of common IT and data standards ► Foster Interoperability between and within State Medicaid organizations ► Provide web-based access and integration ► Support software reusability with commercial off-the-shelf (COTS) software ► Seamlessly integrate clinical and public health data

7. MITA’s Key Principles ► Business-driven service oriented architecture solution ► Firmly grounded in enterprise architecture principles ► Defines a business transformation over a five year and long-term (10 years and greater) timeframe ► Includes a technical architecture and a transition strategy to enable the business transformation

8. MITA’s Components ► Business Architecture  Operations Concept  MITA Maturity Model  Business Process Model  Business Capability Matrix  MITA Self-Assessment  MITA Business Services ► Technical Architecture  MITA Application Architecture  MITA Data Architecture  Technology Architecture  Technical Capability Matrix  MITA Standards

9. Why Business Processes? ► Views the business cross-functionally ► Organizes the actions of the business as a set of activities in response to business events ► Cuts through the existing silos enabling opportunities for real process improvement ► Discover Shared Business Capabilities ► Capabilities point to the Services needed by the architecture

14. Approach ► MITA framework contains models and tools to guide states in the transformation process -- it does NOT contain implementation solutions.  Implementation solutions will be developed by states and vendors  These solutions can be shared with others through a MITA repository. ► MITA team needs state support to refine business processes and develop business services. ► No vendor’s product is “MITA-certified”

15. Steps Along MITA Path 1. Adopt a business orientation -- identify program needs, objectives, goals. Later, decide what technology is required. 2.Map business processes to MITA business process model (see CMS white paper). 3.Do a self-assessment against the MITA business capability matrix (another CMS white paper). 4. Determine maturity level of each business process. 5.Decide which business processes are candidates for improvement by implementing higher level capabilities. 6.Begin to collaborate on the development of business services that can be shared through a MITA repository.

16. Follow Up Activities ► Publication/distribution of Release 2.0 ► Additional MITA white papers ► Emphasis on Outreach/Training/Communications ► More info on deployment and implementation ► Detailed Business Service specifications ► Creation of work groups, collaboration to develop Business Services and Solution Sets ► Work on one or more MITA repositories