Frequently Asked Questions

The reuse webpage on Medicaid.gov features an introductory video and more information about reuse. The webpage also has policy guidance documents.

The Medicaid Enterprise Systems Reuse Repository has instructions on how to use its features. These include how to add artifacts, search for artifacts, use the discussion forum features, and more.

FAQ ID:93646

States can share reusable artifacts with others in several ways. States can participate in workgroups such as the Medicaid Management Information System Cohort, State Technical Advisory Group, and any other relevant state groups to facilitate knowledge sharing, partnerships, and collaboration. States with access to the Reuse Repository also may add their reusable artifacts directly to the repository.

View complete instructions for accessing the Medicaid Enterprise Systems (MES) Reuse Repository. Contact MES at MES@cms.hhs.gov for additional assistance in accessing the repository or participating in workgroups.

FAQ ID:93651

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

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

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

OMB Circular A-87requires costs associated with building shared state-based Information Technology (IT) systems that support multiple health and human service programs be allocated across all benefitting programs in proportion to their use of the system. The OMB A-87 Exception revised this approach by allowing human service programs (e.g. SNAP, TANF, LIHEAP, etc.) and others to utilize a wide range of IT components, needed by Medicaid but also of use to these other programs, at no additional cost except for interfaces or other uniquely required services specific to those programs. The A-87 Exception applies only to design, development, and implementation. Maintenance and operations work should continue to be allocated in accordance with the A-87 Circular. OMB Circular A-87  – Cost Principles for State, Local, and Indian Tribal Governments, has been Relocated to 2 CFR, Part 225 .

FAQ ID:93611

On July 20, 2015, the U.S. Department of Health and Human Services and the U.S. Department of Agriculture announced a three-year extension of the Exception to the OMB A-87 cost allocation requirements from December 31, 2015 to December 31, 2018. We are currently making plans for the OMB A-87 exception to end.

FAQ ID:93616

States will need to incur costs for goods and services furnished no later than December 31, 2018 to make use of this Exception. Therefore, if work is completed by December 31, 2018, it can be funded under the OMB A-87 Exception and states should follow typical invoicing and claiming processes. However, if an amount has been obligated by December 31, 2018, but the good or service is not furnished by that date, then such expenditure must be cost allocated by program in proportion to their use of the system in accordance with OMB A-87.

FAQ ID:93621

For FFY2019 annual APDs and budget tables, including the Medicaid Detailed Budget Table (MDBT), must be completed as follows:

• For Q1 FFY2019, states can allocate costs in accordance with the OMB A-87 Exception
• For Q2-Q$ FFY2019, and all APDs going forward, states should allocate costs as required under the OMB A-87 Circular

If a state has already submitted their annual APDs without providing separate budgets they will need to complete an APDU with a revised MDBT and cost allocation plan. The update should address how cost allocation will be done prior to, and after, December 31, 2018. Budget tables should be completed as described above.

The Data and Systems Group (DSG) that approves APDs does not approve cost allocation methodology. States working to develop their new methodologies should send operational cost allocation plans to Cost Allocation Services  and the regional office fiscal staff for all benefiting programs.

FAQ ID:93626

FAQ ID:92871