U.S. flag

An official website of the United States government

Frequently Asked Questions

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.

Showing 1 to 10 of 26 results

When will the Basic Health Program be operational?

Given the scope of the coverage changes that states and the federal government will be implementing on January 1, 2014, and the value of building on the experience that will be gained from those changes, HHS expects to issue proposed rules regarding the Basic Health Program for comment in 2013 and final guidance in 2014, so that the program will be operational beginning in 2015 for states interested in pursuing this option.

Supplemental Links:

FAQ ID:92141

SHARE URL

What approaches are available to states that are interested in the Basic Health Program in the interim?

HHS is working with states that are interested in the concepts included in the Basic Health Program option to identify similar flexibilities to design coverage systems for 2014, such as continuity of coverage as individuals' income changes. Specifically, we have outlined options to states related to using Medicaid funds to purchase coverage through a Qualified Health Plan (QHP) on the Marketplace for Medicaid beneficiaries (PDF, 242.79 KB). Additionally, some states with current Medicaid adult coverage expansions are considering offering additional types of assistance with premiums to individuals who will be enrolled in QHPs through the Marketplace. HHS will review all such ideas.

Supplemental Links:

FAQ ID:92146

SHARE URL

How is the demonstration year defined? For example, if a state has a fiscal year starting on July 1, 2016 and ending on June 30, 2017, is the Upper Payment Limit (UPL) demonstration entered with the SFY 2016/17 State Plan Amendment considered to be a "2016 demonstration" or a "2017 demonstration"?

The UPL demonstration year is defined according to the last year encompassed by the demonstration. For example, a UPL covering the period 07/01/2016 to 06/30/2017 is defined as the 2017 UPL.

FAQ ID:92231

SHARE URL

Based on CMS guidance, states may take up to 18 months to bring an IV&V contractor on board to perform certification tasks or align current IV&V contract to comply with CMS guidance pertaining to scope of services and financial independence. What must the state do if the IV&V contractor's start up is delayed?

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

SHARE URL

Is IV&V required during operations and maintenance (O&M) for MMIS?

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

SHARE URL

What would preclude a company from being eligible to bid on the MMIS or E&E IV&V contract(s)?

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

SHARE URL

Why does the IV&V contractor need to sit outside the Medicaid agency?

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

SHARE URL

This table indicates what reports are available to CMS Users. These can be found under the "Reports" tab.

Report Name

Description

Available For

Clock Status Report

View the regulatory clock statuses

CPOC, CMS Disapproval Coordinator, SRT Admin CMS Report Admin,

State Agency Profile Report

Overview of a State's Medicaid Plan including the prior 12 months' submission package history

CPOC, CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, CSA, SRT

Submission Detail Report

View details on packages by date

CPOC, CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, SME, PA, PD,SRRVW, SRT

Submission Statistics Detail Report

View all Submission Packages currently in review

CPOC, CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, SME, PA, PD, SRRVW, SRT

Submission Statistics Summary Report

View summary of Submission Packages in a specific review status within a specified date range.

CPOC, CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, SME, PA, PD,SRRVW, SRT

Submission Summary Report

Overview of submitted packages by date

CPOC, CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, SME, PA, PD,SRRVW, SRT

Staff Workload Report

View the number of Submission Packages assigned to each CPOC and SRT member, as of the report run date.

CMS Disapproval Coordinator, SRT Admin, CMS Report Admin, CSA

FAQ ID:92871

SHARE URL

What is the Review Tool Report?

The Review Tool Report is a feature CPOCs, SRTs, Senior Reviewers, Package Approvers, Package Disapprovers, and CMS Report Admins can utilize to see Package Reviewable Units, Reviewers, Reviewable Unit Assessment Values, and Notes.

Log in as CMS Point of Contact or Submission Review Team member. Under the "Records" tab, select "Submission Packages". Then select the link to the submission package. In the left panel, select "Review Tool Report". You may sort the reviews of all Review Team members by Package Reviewable Unit, Reviewer, Reviewable Unit Assessment Value, or Note/Assessments by utilizing the drop-down boxes. You also have the ability to export this report to Excel by selecting "Export to Excel."

FAQ ID:92876

SHARE URL

What is the purpose of each Analyst Note Type?

Analyst Notes are a form of brief internal communication for the CMS Review Team. These notes are a part of the official record; however, State users are not able to see these notes. Analyst Notes are part of the Review Tool for each Reviewable Unit and the SRT or CPOC may view the notes from other Review Team members (depending on the type of note) within the Review Tool, and add his/her own notes.


The CMS Point of Contact or Submission Review Team members may add Analysts Notes through the Review Tool. The types of notes available are referenced in a table below. You will start by logging in as the CMS Point of Contact or Submission Review Team member, then going to the "Records" tab. Under the "Records" tab select "Submission Packages" and then select the link to the package. In the left panel select "Analyst Notes". You will then have the ability to search notes entered by Review Team Members.

Analyst Note Type Description Visible By
Note to self Private note for self only Self
For POC (Formal Review) Indicates information that should be included in disposition CPOC
For Review Team For other Review Team members CPOC and SRT
For RAI Indicates something that requires RAI CPOC and SRT
For Correspondence Log Indicates information that should be communicated to the SPOC CPOC and SRT
Non SRT-User Note on behalf of a CMS participant outside of the Review Team CPOC and SRT
General Note A note that doesn't fall into another category All
Justification Provides bases for a recommended disposition POC Admin, CPOC and SRT
Post-Recommendation Included by other CMS users during the package disposition review POC Admin, CPOC and SRT

FAQ ID:92881

SHARE URL
Results per page