Frequently Asked Questions

In accordance with Medicare cost reporting, the state must use 12 months of cost data reported by each facility. With regard to payment data, the state should use actual amounts, to the extent available, then calculate a claims completion factor based on historic utilization. The state’s UPL submission must include an explanation of its methodology to estimate payments. The use of a claims completion factor provides a reasonable estimate of the amount that Medicare would pay for these services, consistent with the UPL as defined at 42 CFR 447.272.

FAQ ID:92446

Yes. Mapping data, through V-Look-ups, for example, is a much easier and consistent process for current and future UPL submissions. However, a state may choose to type information and data into unlocked fields in the UPL templates. When a state chooses to input data directly (not through a V-Look-up) into the template, it still must provide the supporting documentation with the source data. Additionally, the state should explain how it mapped data from the supporting documentation into the template. The Centers for Medicare & Medicaid Services utilizes the supporting information to confirm that the information in the templates is correct.

FAQ ID:92451

The cost of the tax should be reported in Variable 401 - MCD Provider Tax Cost. A state may separately report the Medicaid portion of the cost of a provider assessment/tax only when it is using a cost based methodology to calculate the UPL. A state may not include this cost when calculating a DRG or Payment based UPL demonstration.

FAQ ID:92366

IV&V contractor activities must still be performed such as checklist evaluation, artifact review and preparation of IV&V Progress Reports. The state should provide a plan and timeline for how these activities will be supported and performed until the proper IV&V contract can be either procured or aligned with updated CMS guidance on IV&V.

FAQ ID:94866

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