Frequently Asked Questions

No. MLTSS plans are not required to share the full care plan with the PCP or other documented medical care practitioner. MLTSS plans may choose which parts of the care plan are most relevant to the practitioner.

FAQ ID:89221

No, the LTSS Shared Care Plan with Primary Care Practitioner (PCP) measure only looks to see that a care plan was sent to a primary care practitioner (PCP) by the MLTSS plan. No signature from the PCP is necessary to count towards the numerator of this measure.

FAQ ID:89226

There is no need for a release of information. If a member gives the plan the contact information for their PCP, the plan can share information with that PCP. Plans or other providers of LTSS should try to coordinate LTSS services with medical services, even if they are not the primary payer for medical services for the member. Plans that do not know the member’s PCP can/should ask the member to identify their PCP and request their contact information. The measure is intended to determine whether plans tried to connect with the medical care provider. There is an exclusion in this measure for members who refuse to have their care plan shared with the PCP, so if the member refuses, this should be documented, and such members are excluded from the measure rate.

FAQ ID:89231

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

FAQ ID:93631

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

FAQ ID:93636

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.

FAQ ID:93641

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