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
Generally, information from the Federal data services hub will only be sent in direct response to a call from the requesting entity. However, in the case of verifications conducted by DHS, there can be up to three steps to a verification, the second and third of which will not be in real time. If the step 1 query fails, the Federal data services hub will automatically invoke step 2, and the response may take up to several days. If step 2 fails, the Federal data services hub will notify the requesting entity which will need to submit additional documentation from the applicant for step 3. The step 3 response can take weeks. During this time, the Federal data services hub will regularly poll DHS to see if the response has come back.
Supplemental Links:
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. 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
To get started with reuse, a state can:
- Review the state Medicaid director letter (SMD #18-005) on reuse
- 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
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.
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.
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.
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.