1. The HealthMatch Project (Insert Conf. Name & Date)

2. Agenda  Discuss HealthMatch business cases  Explain HealthMatch system goals  Discuss potential changes to business processes  Provide project status update  Present HealthMatch timeline  Get a sneak peak at HealthMatch screens  Preview county implementation plans  Review the changes that clients may see

3. Why HealthMatch?  Present systems not originally designed to automate health care eligibility MinnesotaCare was never automated Manual interfaces result in gaps in coverage and uncompensated care costs  More than 100 health care eligibility types, complex policies and processes lead to: Administrative inefficiency Increased eligibility error rates

4. HealthMatch System Goals  Improve customer service: Automate eligibility determinations, allowing staff to focus more attention on clients’ needs Provide more options to consumers, allowing them to determine the best way to access services  Increase efficiency: Control administrative costs Standardize major processes Improve speed and accuracy via uniform determinations  Improve health care program integrity: Reduce eligibility error rates

5. HealthMatch Will Support Multiple Business Processes  Technology is just a tool  HealthMatch will provide flexibility to support unique needs across the state  County and partner staff have provided valuable input into system design and process improvements

6. Gaps and loss of coverage Processing delays Best benefit set at lowest cost Expedited enrollment TodayTomorrow HealthMatch One Program Minnesota Health Care Program (MHCP) Three Programs MA, MinnesotaCare, GAMC

7. HealthMatch Status  Workflow design is complete. Construction and testing are under way.  Notice design is complete. Construction has begun.  Client Partner Website design is complete. Construction has started.  Alerts design is nearly complete.

8. HealthMatch Status  Work on most complex designs continues Rules for eligibility engine  Nearly 15,000 rules identified Interfaces  External & internal interface designs are being worked on Conversion  80% data mapping of MMIS/MAXIS completed  Counties participating in data clean-up continues Continued

9. HealthMatch Project Review  Comprehensive project review in April and May lead to timeline adjustment Complexity of Minnesota’s health care programs Inclusion of elderly and disabled programs Added time for beta test and implementation support

10. HealthMatch Timeline

11. System Features  Goes beyond eligibility determination to include: Accounts receivable functionality Internal and external interfaces  System designed with workers’ needs to include: Screen navigation Point and click Drop down menus Online help Workflow

12. System Features  Public website provides access to information for clients, advocates, and business partners Apply and renew online View eligibility statuses, notices, obligations, etc. Pay premiums Continued

13. HealthMatch Eligibility Engine  Goals are to: Consistently apply policy statewide Rapidly calculate results based on data provided Determine information and verification needed Automate mailings of notices, forms, and verification requests to clients

19. Public Web Site Features  Information and referral  Questions-based application  Self-service web site Eligibility pre-screening tool Electronic payment of obligations Health plan selection Completion of renewals  English and Spanish languages

20. New client applying online

30. MHCP Member Viewing Information Online

31. Note: Each client’s main menu will only include options that apply to them.

34. Data Cleanup  Identify data elements that may impact the conversion of a case into HealthMatch  Develop strategies for resolving discrepant data  Report discrepant data for resolution  Provide effective support during data cleanup  Reduce discrepant data prior to HealthMatch conversion

35. Data Cleanup Update

36. Internal Interfaces  MMIS Recipient subsystem Managed Care TPL  MAXIS  PRISM  SMI  EDMS  IVR  DataWarehouse

37. External Interfaces  SVES  BENDEX  BEER  COLA  DEED  IRS

38. Interface Challenges and Goals  Reduce duplicate entry across systems while allowing each system to function efficiently and effectively on its own; and  Automate as much functionality as possible in the initial rollout and still meet development timelines and budgets

39. HealthMatch Implementation Training  Training will consists of two parts: Part I: Online course  An introductory course to the HealthMatch system Part II: Classroom course  A hands-on course offering practical case scenarios and system entries  Online User Guide will be available

40. Introduction to HealthMatch Online  Online course: Is designed for self-pace learning Contains eight modules Provides an introductory lesson to portlets, screen layout and system navigation Is a prerequisite to classroom training

41. HealthMatch Classroom Training  Provides two days of practical, hands-on learning experience  Scheduled at the regional lab sites  Offers separate training for workers and support staff  Offers specialized LTC training

42. HealthMatch User Guides  User Guide for workers Provides screen navigational tips Contains step-by-step system entry procedures for common situations Will be available to workers after completion of system training  User Guide for managers Contains reports, statistics, and daily administration procedures

43. HealthMatch Conversion  Conversion will occur at renewal  Reports will be run for cases exempt from six- month renewals  Manual data conversions will occur  Processes are being defined for conversion of pending, denied, closed, withdrawn, and reinstated cases  Clean cases ― clean conversion!

44.  Household-based, rather than person-based One notice per household Sent to one designated adult family member  Simple, easier to read and understand  Written at 7th grade reading level or lower Client Notices Continued

45.  Household Information Summary Family’s data, income, assets, insurance, etc.  Benefit Package Summary Each enrollee will have a benefit package type, A – P  A = covered services under the Medical Assistance Program Health care services covered, co-pays, limits, and access services information, if applicable Client Notices Continued

46.  Types of Notices Combined  Pending, approval, denial, suspensions, closures  FYI/informational Change  Change in benefits, spenddowns, or premiums Client Notices Continued

47.  Freeform Workers write the message  Pre-selection of text that is already written Translated Worker Memos

48. Renewals  Redesigned to be a pre-populated Renewal Form Enrollees must:  Review data on form  Update data and add new information  Sign, date and return form

49. For More Information  Julie Skoy, Health Care Eligibility & Access Supervisor 651.297.4344 julie.skoy@state.mn.us  Cristy Hong, HealthMatch Information Manager 612.772.6033 cristy.hong@state.mn.us