Frequently Asked Questions

No, a state is not required to reference or rely on the ASAM Criteria however, states should use guidelines/patient placement tools that are comparable to ASAM criteria. The State Medicaid Director Letter describing the SUD section 1115 demonstration opportunity references the ASAM Criteria as a recognized standard and an example of a patient placement assessment tool that states could use. Participating states are expected to ensure that providers use an SUD-specific, multi-dimensional assessment tool in determining the types of treatments and level of care a beneficiary with an SUD may need. The ASAM Criteria is referenced as a representative example of such an assessment tool. 

Some states proposed alternative needs assessment tools. CMS reviews each alternative proposal on an individual basis, and CMS has so far determined that those alternatives are comparable to the ASAM Criteria and meet the expectations for this demonstration initiative. In addition, participating states are expected to implement provider qualifications for residential treatment providers that reflect well-established standards for these treatment settings. Again, the ASAM Criteria is referenced as an example of a resource that states may use for determining those standards.

FAQ ID:93681

No; discharges for planned hospital admissions are excluded from the measure denominator. Identify planned discharges using the value sets (XLSX, 2.88 MB).

FAQ ID:89236

Yes, both the re-assessment and the care plan must include each of the nine specified core elements. The re-assessment and care plan must be done face-to-face unless there is documentation that the member refused a face-to-face encounter.

FAQ ID:89241

The denominator for the Reassessment/Care Plan Update after Inpatient Discharge measure is identified through administrative claims for inpatient discharges. Managed care plans that are not the primary payer for inpatient care, which is usually covered under a medical benefit, do not routinely have reliable access to administrative claims for inpatient stays to identify individuals who are eligible to be counted in the measure denominator. Therefore, the eligible population for this measure is restricted to individuals who receive both medical and LTSS benefits through the managed care plan providing MLTSS.

FAQ ID:89246

If MLTSS plans can obtain timely, complete, and accurate inpatient claims data for their members, then a state may choose to deviate from the measure specifications to require MLTSS plans not providing medical benefits report this measure. For example, because the timely transfer of information between hospitals and MLTSS plans is key to ensuring smooth transfers between settings of care, MLTSS plans may have access to hospital discharge data through state or regional health information exchanges. In some cases, MLTSS plans are working closely with hospitals to share timely information about admissions and discharges. In addition, some states have the data and capacity to construct this measure for MLTSS plans using Medicare claims data for Medicare- Medicaid dual eligible beneficiaries (see more information about state access to Medicare claims data).

FAQ ID:89251

A reassessment with the member after they have been discharged from an inpatient facility is required to determine whether a member has had a change (or no change) in their LTSS needs. Even if the reassessment conducted post-discharge finds no change in a member’s LTSS needs, the second rate for this measure (Reassessment and Care Plan Update after Inpatient Discharge), Managed Long Term Services and Supports (MLTSS) plan care managers should conduct a care plan update and document that they considered each of the nine core elements of the care plan, and determined that the plan of care for each element remains the same; documentation of “no changes” in the care plan as a whole does not meet the numerator criteria.

FAQ ID:89256

The Precertification Pilot was an experiment conducted from October 2017-March 2018 designed to streamline certification and attract new vendors. Unfortunately, the pilot was found to be unscalable across Medicaid. However, key learnings from the pilot will be incorporated into current processes and future experiments around vendor engagement, certification, scalability, and sustainability. The goals the Centers from Medicare & Medicaid Services (CMS) identified at the beginning of the Precertification Pilot process remain the same: reduce the level of effort of certification; shorten the certification timeline; promote modularity and interoperability; reduce risk of system failure; and attract new vendors to the Medicaid IT market. Contact CMS with your ideas for experiments to achieve those goals at MES@cms.hhs.gov.

FAQ ID:95151

As contained in the MECT standard RFP/contract language required by CMS, CMS does not cover activities that the state may require of the IV&V contractor during ongoing O&M. However, as Medicaid is moving away from monolithic single applications, it is expected that states will continuously update and replace modules in their enterprise. Therefore, IV&V should always have a role to ensure successful integration and testing.

FAQ ID:94881

If an organization is performing another role (such as systems integrator, PMO, quality assurance, etc.) on the MMIS or E&E project, it may not perform the IV&V function on the same project. A state may contract the same vendor to perform the IV&V role for both its E&E and MMIS projects.

FAQ ID:94886

To reduce potential conflict of interest, CMS is ensuring that states are arranging IV&V services through contracts that should be owned outside of the agency that owns the MMIS or E&E project. The oversight organization for the IV&V contractor should not be involved in oversight of the development effort, a stakeholder in the business implementation, or the DDI contractor. The IV&V contract monitor should be aware of system development problem solving, reporting, and contractor management. This contract oversight provides true independence between the IV&V contractor and system development teams. This requirement is consistent with other HHS agencies' practices and industry best practices.

FAQ ID:94891