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 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
What is reuse?
The Centers for Medicare & Medicaid Services expects states receiving Federal Financial Participation to share with other states project artifacts, documents and other related materials, and systems components and code for leverage and reuse.
Read the state Medicaid director letter (SMD #18-005) on reuse (PDF, 70.77 KB). Reuse can be accomplished through sharing or acquiring:
- An entire set of business services or systems, including shared hosting of a system or shared acquisition and management of a turnkey service
- A complete business service or a stand-alone system module
- Subcomponents such as code segments, rule bases, configurations, customizations, and other parts of a system or module that are designed for reuse
How do states get started with reuse?
To get started with reuse, a state can:
- Review the state Medicaid director letter (SMD #18-005) on reuse (PDF, 70.77 KB)
- View the introductory video to get familiar with the concept and framework of reuse
- Contact the Medicaid Enterprise Systems (MES) at MES@cms.hhs.gov to request access to the MES Reuse Repository
What is the Reuse Repository, and how can states access it?
The Centers for Medicare & Medicaid Services (CMS) established the Medicaid Enterprise Systems (MES) Reuse Repository to support states’ ability to share and reuse project life cycle artifacts. The repository is available on the CMS zONE (Opportunity to Network and Engage). States must have a CMS Enterprise Identity Management login to access the Reuse Repository.
View complete instructions for accessing the Reuse Repository.
Contact MES at MES@cms.hhs.gov for additional assistance in accessing the repository.
Is training available for reuse concepts and tools?
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.
How do states share?
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.
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.
What 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.
What 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.
What are the expectations for states in implementing telephonic applications as required by the statute at section 1413(b)(1)(A) and regulations at 42 CFR 435.907?
The statute and regulations require that states provide individuals several channels through which they can apply for Medicaid and CHIP coverage - by mail, in person, on line and over the telephone. Following are some guiding principles for administering telephonic applications based on successful strategies many states have in place today.
- Accepting a Telephonic Application - States may develop their own processes for accepting and adjudicating telephonic applications. The process for accepting applications by phone must be designed to gather data into a sufficient format that will be accessible for account transfer to the appropriate insurance affordability program. For example, a customer service representative could verbally communicate application questions to the applicant, while electronically filling out the online version of the single streamlined application.
- Voice Signatures - All applications must be signed (under penalty of perjury) in order to complete an eligibility determination. In the case of telephonic applications, states must have a process in place to assist individuals in applying by phone and be able to accept telephonically recorded signatures at the time of application submission. If applicable, states can maintain their current practices of audio recording and accepting voice signatures as required for identity proofing.
- Records and Storage - Upon request, states must be able to provide individuals with a record of their completed application, including all information used to make the eligibility determination. As such, CMS recommends that states record all telephonic applications. This may be accomplished by taping the complete application transaction as an audio file, or by producing a written transcript of the application transaction, among other options. The length of storage of these records should comply with current regulations on application storage.
- Confirmations and Receipts - States should provide a confirmation receipt documenting the telephonic application to the applicant. Such confirmation should be provided upon submission of the application or at any time the applicant wishes to end the customer representative interaction. Confirmation receipts can be delivered via electronic or paper mail (based on the applicant's preference). Confirmation receipts must include key information for applicants, including but not limited to the application summary, the eligibility determination summary page, a copy of the attestations/rights and responsibilities and the submission date of the signed application.
- This FAQ was released as part of a larger set. View the full set. (PDF, 295.71 KB)