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
Must the Managed Long Term Services and Supports (MLTSS) LTSS Comprehensive Assessment and Update measure assessment take place in the home?
Yes, the assessment for the LTSS Comprehensive Assessment and Update measure is required to take place in the member’s home as a face-to-face discussion unless certain exceptions are met. These exceptions include circumstances in which:
- The member was offered an in-home assessment and refused the in-home assessment (either refused to allow the care manager into the home or requested a telephone assessment instead of an in-home assessment).
- The member is residing in an acute or post-acute care facility (hospital, skilled nursing facility, other post-acute care facility) during the assessment time period.
- The state policy, regulation, or other state guidance excludes the member from a requirement for in-home assessment.
What if a Managed Long Term Services and Supports (MLTSS) member refuses an LTSS Comprehensive Assessment and Update measure assessment?
There must be documentation of the refusal, which would result in exclusion from the measure. The rate of exclusion due to a member refusing to participate should also be reported along with the measure performance rate.
What if a Managed Long Term Services and Supports (MLTSS) member could not be reached for an LTSS Comprehensive Assessment and Update measure assessment?
There must be documentation that at least three attempts were made to reach the member, and that the member could not be reached, which would result in exclusion from the measure. The rate of exclusion due to inability to reach a member should also be reported along with the measure performance rate.
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.