Specifications include, but are not limited to: A. High-level solution requirements have been identified and grouped into 12 categories. 1. The purpose of the General requirements is to ensure the system supports the regulatory requirements laid out in the Cures Act, sec. 12006(a)(2)(A) requiring in-home visits for personal care services and home health services to be electronically verified. 2. The purpose of the Architecture and Data requirements is to ensure the system supports the process of Kansas’ State Agencies, Provider groups, and Medicaid members. In addition, these requirements support the adherence to Federal requirements and Medicaid Best Practices (MBPs) for EVV, as outlined by the Centers for Medicare and Medicaid Services (CMS) in their guidance for EVV. To satisfy both Federal and State requirements, data elements and architectural design must accommodate key goals of the project, which include fraud prevention, process automation, ease of use, appropriately paid claims, and secure data. 3. The purpose of the User Interface requirements is to ensure all users can easily interact with the system using preferred devices, establishing personal preferences, including compliance to Accessibility Guidelines, and allowing Provider agencies and State personnel role-based access to data. 4. The purpose of the Device requirements is to define the types and ways in which users will interact with the system as users perform their day-to-day responsibilities and tasks. 5. The purpose of the Security requirements is to provide on-demand capability to manage user accounts and passwords while complying with enterprise security standards and the corresponding privacy laws. Part of the on-demand capability is to equip the State and Provider Agencies with the necessary tools to support external users. The system needs to use configurable roles and role-based security. 6. The purpose of the Legal and Outcome Based Certification (OBC) requirements is to communicate the rules and regulations the system shall be in compliance with and the CMS certification the system shall achieve.
