Frequently Asked Questions are used to provide additional information and/or statutory guidance not found in State Medicaid Director Letters, State Health Official Letters, or CMCS Informational Bulletins. The different sets of FAQs as originally released can be accessed below.
Frequently Asked Questions
If a state is reusing a system or module already certified in another state, do they still need to go through certification review and decision?
Certification is required for any new implementation, whether it is a custom- developed module that is transferred from another state, or a commercial off-the-shelf module that is being configured and integrated. The certification process looks at the state’s implementation of the solution to ensure the state has met all federal requirements.
States may reuse system documentation and other supporting evidence from a previous state certification if it is available and applicable to their systems and has been reconfirmed by independent verification and validation.
FAQ ID:93656
SHARE URLWhat aspects of reuse do states need to be aware of when developing advance planning documents (APDs)?
APDs must demonstrate a reuse-friendly design that includes the sharing of systems, modules, code, and any other developed artifacts. States could include language describing their efforts to find and learn from or reuse components from similar systems, or efforts the state is making to ensure that other states more easily can reuse the proposed system once it is developed.
FAQ ID:93661
SHARE URLWhat is the Centers for Medicare & Medicaid Services (CMS) policy regarding ownership rights?
From an intellectual property standpoint, reuse is supported by the general grant conditions for Federal Financial Participation (FFP) under 45 CFR 95.617, which require states to "include a clause in all procurement instruments that provides that the State or local government will have all ownership rights in software or modifications thereof and associated documentation designed, developed, or installed with FFP under this subpart."
Further, according to 42 CFR 433.112(6), CMS has "a royalty free, non-exclusive, and irrevocable license to reproduce, publish, or otherwise use and authorize others to use, for Federal Government purposes, software, modifications to software, and documentation that is designed, developed, installed or enhanced with 90 percent FFP."
In practice, this means that vendors retain ownership rights to software and other products they have developed under their own initiative and funding, while states and CMS have ownership rights to and may share any software, customizations, configurations, or add-ons funded with FFP.
FAQ ID:93666
SHARE URLAre states required to submit their Upper Payment Limit (UPL) demonstrations directly to the mailbox or should they continue to submit them to the CMS Regional Office?
States are requested to submit their UPL demonstrations to the UPL mailbox at MedicaidUPL@cms.hhs.gov, but should also send a copy of each demonstration to their CMS Regional Office, including the National Institutional Reimbursement Team (NIRT) and Non-Institutional Payment Team (NIPT) staff as appropriate, and addressed to the Associate Regional Administrator. UPL demonstrations should be submitted to meet the annual reporting requirement described in SMDL 13-003, as well as when proposing changes in payment through SPAs.
FAQ ID:92251
SHARE URLBased on CMS guidance, states may take up to 18 months to bring an IV&V contractor on board to perform certification tasks or align current IV&V contract to comply with CMS guidance pertaining to scope of services and financial independence. What must the state do if the IV&V contractor's start up is delayed?
IV&V contractor activities must still be performed such as checklist evaluation, artifact review and preparation of IV&V Progress Reports. The state should provide a plan and timeline for how these activities will be supported and performed until the proper IV&V contract can be either procured or aligned with updated CMS guidance on IV&V.
FAQ ID:94866
SHARE URLIs IV&V required during operations and maintenance (O&M) for MMIS?
As contained in the MECT standard RFP/contract language required by CMS, CMS does not cover activities that the state may require of the IV&V contractor during ongoing O&M. However, as Medicaid is moving away from monolithic single applications, it is expected that states will continuously update and replace modules in their enterprise. Therefore, IV&V should always have a role to ensure successful integration and testing.
FAQ ID:94881
SHARE URLWhat would preclude a company from being eligible to bid on the MMIS or E&E IV&V contract(s)?
If an organization is performing another role (such as systems integrator, PMO, quality assurance, etc.) on the MMIS or E&E project, it may not perform the IV&V function on the same project. A state may contract the same vendor to perform the IV&V role for both its E&E and MMIS projects.
FAQ ID:94886
SHARE URLWhy does the IV&V contractor need to sit outside the Medicaid agency?
To reduce potential conflict of interest, CMS is ensuring that states are arranging IV&V services through contracts that should be owned outside of the agency that owns the MMIS or E&E project. The oversight organization for the IV&V contractor should not be involved in oversight of the development effort, a stakeholder in the business implementation, or the DDI contractor. The IV&V contract monitor should be aware of system development problem solving, reporting, and contractor management. This contract oversight provides true independence between the IV&V contractor and system development teams. This requirement is consistent with other HHS agencies' practices and industry best practices.
FAQ ID:94891
SHARE URL
Results per page