Medicaid State Program Integrity (SPIA) CMS-10244

Forms and Documents

Forms and supporting documents for this ICR

Document	Type	Status	Availability
Form CMS-10244 Medicaid State Program Integrity Assessment (SPIA) CMS-10244	Form and Instruction	Modified	Available
SPIA Supporting Statement 11-24-2010.doc	Supporting Statement A	Uploaded 2010-12-03	Available

IC Document Collections

Information collection document groups

IC ID	Collection	Type	Status	Form
182825	Medicaid State Program Integrity Assessment (SPIA) CMS-10244	Form and Instruction	Modified

ICR Details

OMB Control No: 0938-1033	ICR Reference No: 201012-0938-014
Status: Historical Active	Previous ICR Reference No: 200711-0938-013
Agency/Subagency: HHS/CMS	Agency Tracking No:
Title: Medicaid State Program Integrity (SPIA) CMS-10244
Type of Information Collection: Extension without change of a currently approved collection	Common Form ICR:  No
Type of Review Request: Regular
OIRA Conclusion Action: Approved without change	Conclusion Date: 02/27/2011
	Date Received in OIRA: 12/17/2010
Terms of Clearance:

table that charts list comparision

	Inventory as of this Action	Requested	Previously Approved
Expiration Date	02/28/2014	36 Months From Approved	02/28/2011
Responses	56	0	56
Time Burden (Hours)	1,400	0	1,400
Cost Burden (Dollars)	0	0	0

---

Abstract: Under the provisions of the Deficit Reduction Act (DRA) of 2005, Congress directed the Centers for Medicare & Medicaid Services (CMS) to establish the Medicaid Integrity Program (MIP), CMS' first national strategy to combat Medicaid fraud, waste, and abuse. CMS has two broad responsibilities under the MIP: 1) Reviewing the actions of individuals or entities providing services or furnishing items under Medicaid; conducting audits of claims submitted for payment; identifying overpayments; and educating providers and others on payment integrity and quality of care; and 2) Providing effective support and assistance to States to combat Medicaid fraud, waste, and abuse. In order to fulfill the second of these requirements, CMS developed the Medicaid State Program Integrity Assessment (SPIA). CMS uses SPIA to collect data on State Medicaid program integrity activities, develop reports for each State based on these data, determine areas to provide States with technical support and assistance, andevelop measures to assess States' performance. CMS is seeking an extension of the approval from the Office of Management and Budget (OMB) to annually collection information from the States through SPIA.

---

Authorizing Statute(s): Statute at Large: 42 Stat. 455 Name of Statute: null
   PL: Pub.L. 109 - 171 6034 Name of Law: Medicaid Integrity Program
   Statute at Large: 19 Stat. 1936 Name of Statute: null
  

Citations for New Statutory Requirements: None

---

Associated Rulemaking Information
RIN:	Stage of Rulemaking:	Federal Register Citation:	Date:
	Not associated with rulemaking

---

Federal Register Notices & Comments
60-day Notice:	Federal Register Citation:	Citation Date:
	75 FR 55330	09/10/2010
30-day Notice:	Federal Register Citation:	Citation Date:
	75 FR 70926	11/19/2010
Did the Agency receive public comments on this ICR? No

---

Number of Information Collection (IC) in this ICR: 1

table that charts list of burden

IC Title	Form No.	Form Name
Medicaid State Program Integrity Assessment (SPIA) CMS-10244	CMS-10244	Medicaid State Program Integrity Assessment (SPIA)

---

ICR Summary of Burden

table that charts list of burden

	Total Approved	Previously Approved	Change Due to New Statute	Change Due to Agency Discretion	Change Due to Adjustment in Estimate	Change Due to Potential Violation of the PRA
Annual Number of Responses	56	56	0	0	0	0
Annual Time Burden (Hours)	1,400	1,400	0	0	0	0
Annual Cost Burden (Dollars)	0	0	0	0	0	0

Burden increases because of Program Change due to Agency Discretion: No

Burden Increase Due to:

Burden decreases because of Program Change due to Agency Discretion: No

Burden Reduction Due to:

Short Statement:

---

Annual Cost to Federal Government: $0

Does this IC contain surveys, censuses, or employ statistical methods? No

Is the Supporting Statement intended to be a Privacy Impact Assessment required by the E-Government Act of 2002? No

Is this ICR related to the Affordable Care Act [Pub. L. 111-148 & 111-152]? No

Is this ICR related to the Dodd-Frank Wall Street Reform and Consumer Protection Act, [Pub. L. 111-203]? No

Is this ICR related to the American Recovery and Reinvestment Act of 2009 (ARRA)? No

Is this ICR related to the Pandemic Response? Uncollected

---

Common Form ICR:  No

---

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).

The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:

(a) It is necessary for the proper performance of agency functions;

(b) It avoids unnecessary duplication;

(c) It reduces burden on small entities;

(d) It uses plain, coherent, and unambiguous language that is understandable to respondents;

(e) Its implementation will be consistent and compatible with current reporting and recordkeeping practices;

(f) It indicates the retention periods for recordkeeping requirements;

(g) It informs respondents of the information called for under 5 CFR 1320.8 (b)(3) about:

(i) Why the information is being collected;

(ii) Use of information;

(iii) Burden estimate;

(iv) Nature of response (voluntary, required for a benefit, or mandatory);

(v) Nature and extent of confidentiality; and

(vi) Need to display currently valid OMB control number;

(h) It was developed by an office that has planned and allocated resources for the efficient and effective management and use of the information to be collected.

(i) It uses effective and efficient statistical survey methodology (if applicable); and

(j) It makes appropriate use of information technology.

If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.

Certification Date: 12/17/2010

---