{"Scope of Project":"The Louisiana Department of Health (LDH) issued a non-binding RFI to gather information on technology platforms for eligibility and case management across human services programs, seeking input on capabilities, implementation, and pricing from all interested vendors","Purpose":"LDH is committed to modernizing eligibility and case management systems to prioritize accuracy, operational efficiency, rapid adaptability, and the resident experience. We welcome vendors who can contribute to these goals, whether through full system solutions or component technologies. \nIf your company is focused on agility, speed to market, innovation, low-code configurability, and user-centered design, we want to hear from you. This is your opportunity to help shape the future of health and human services in Louisiana.","Executive Summary":"The responder should provide administrative information, including, at a minimum, the responder’s contact name and phone number, email address, and any other pertinent contact information. This section should also include a summary of the responder’s qualifications, ability, and willingness to comply with the State’s requirements.","Experience":"The responder should provide a brief description of the company, including its history, corporate structure, organizational details, and years in business. Responders should also describe their experience with projects of this type with other states or corporate/governmental entities of comparable size and diversity, including development and maintenance.","User Base":"Medicaid:\nAround 1,682 internal users (includes auditors, appeals staff, field staff, and managers).\n38 roles defined in the eligibility system.\n\nEconomic Stability:\nAround 2,800 internal users.\n41 roles defined in the eligibility system.\n\nRole Design:\nRoles are inclusive and multi-functional, combining specific duties.\nAvoids creating many similar roles with only minor permission differences.","Time Line":"24 Months","Cost Estimate":"Provide a general overview of your pricing model (e.g., subscription-based, per user, per transaction). While this is an RFI, a high-level understanding of potential costs is beneficial. Please include any information regarding typical implementation and maintenance costs, as well as factors influencing them, with a focus on the cost-effectiveness of modifications and maintenance.","RFP Document Folder Link":"https://docs.google.com/spreadsheets/d/110H93A850TLIaq2i6gcG5Je_QsIDO3au7g7SqxfkwE8/edit?usp=drive_link"}
Assumptions
- Cardinality Solution will be hosted on AWS Gov Cloud for the production instance.
- AWS Hosting includes one production and four non-production instances - Development, Integration Testing, UAT and Staging
- Cardinality SaaS license includes - Yearly 2 upgrades, monthly hot fixes and level 3 support
- All resources would be based out of the US
- The Cardinality Saas license cost is provided for up to upto 4800 internal users
- Cardinality will leverage the Adobe or DocuSign licenses of the Agency for e-signature
- The Operations & Maintenance Support phase is assumed to start after DDI phase of 24 months
- Cardinality will provide a mobile responsive application. Development of a mobile app is not part of scope of work
- Cardinality will provide Level-1, Level-2 and Level-3 support during the M&O Phase
- The Agency will provide HelpDesk infrastructure during M&O Phase