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
Which measures assess institutional rebalancing and utilization measures?
The following measures assess institutional rebalancing and utilization:
- LTSS Admission to an Institution from the Community
- LTSS Minimizing Institutional Length of Stay
- LTSS Successful Transition after Long-Term Institutional Stay
Do I need to use value sets to calculate these institutional rebalancing and utilization measures? If so, where can I find the value sets?
Yes. Value sets are the complete set of procedure and codes used to identify a service or condition included in a measure. All three of the rebalancing measures—LTSS Admission to an Institution from the Community, LTSS Minimizing Institutional Length of Stay, and LTSS Successful Transition after Long-Term Institutional Stay—use the "Institutional Facility"value set (XLSX, 2.88 MB). See Table 2 in the "LTSS Value Sets to Codes" tab. Table 1 in the "LTSS Measures to Value Sets" tab shows each value set needed for each measure.
Should unpaid or denied claims be included in calculating the institutional utilization and rebalancing measures?
No, include paid claims only (days denied for any reason should not be included) for all three of the rebalancing measures—LTSS Admission to an Institution from the Community, LTSS Minimizing Institutional Length of Stay, and LTSS Successful Transition after Long-Term Institutional Stay.
Will there be any automatic updates coming through the Federal data services hub? Or will we always need to make a call to the Federal data services hub in order to get any information back? If a change is likely will the state need to send ongoing, frequent requests through the Federal data services hub?
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.
- This FAQ was released as part of a larger set. View the full set. (PDF, 104.38 KB)
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.