J.1.A__ZPICUSOWAppendices-A-K.doc
DOC document 1 MB Posted
- Attached to
- Zone Program Integrity Contractor (ZPIC)
- Solicitation number
- RFP-CMS-2007-0027
About this file
J.1.A ZPIC USOW Appendices A-K
View the file
Other files
Show 40 more
Latest 50 of 55 listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Zone Program Integrity Contractor
Appendices
List of Appendices
A. DELIVERABLES
B. TRANSFER OF BENEFIT INTEGRITY MANAGER INFORMATION FROM AFFILIATED CONTRACTOR AND THE MEDICARE ADMINISTRATIVE CONTRACTOR
C. DATA RELEASE POLICIES AND PROCEDURES
D. RECORDS RETENTION
E. IRISFI OPERATING INSTRUCTIONS (AUGUST 1995)
F. MEMORANDUM OF UNDERSTANDING WITH LAW ENFORCEMENT
G. UNIFORM DESK REVIEW
H. FREEDOM OF INFORMATION GROUP POLICY AND PROCEDURAL GUIDE
I. ZPIC EDIT DIFFERENTIATION CHART
J. GLOSSARY AND ACRONYMS
K. CMS ARTS COST REPORTING DEFINITIONS
L. MEDI-MEDI POLICIES AND PROCEDURES MANUAL
M. PART C AND PART D INTEGRITY MANUAL
N. PRESCRIPTION DRUG EVENT DATA
O. DATA RELEASE POLICIES AND PROCEDURES UNDER THE PRIVACY ACT OF 1974
P. INSTRUCTIONS FOR COMPLETING THE MEDICARE PRESCRIPTION DRUG PLAN BID FORM FOR CONTRACT YEAR 2006
Q. PDP BID PRICING TOOL
R. MARx USER INFORMATION
S. WEEKLY WORKLOAD AND COMPLAINT ACTIVITY REPORT
T. EARNED VALUE MANAGEMENT INDUSTRY STANDARD EIA-748 MONTHLY EVMS PERFORMANCE REPORTS
The following Appendices are available on the Internet and are hereby incorporated with the same force and effect as if they were provided in full text herein.
U. BUSINESS PARTNERS SYSTEM SECURITY MANUAL
http://www.cms.hhs.gov/manuals/downloads/117_systems_security.pdf
V. PROGRAM INTEGRITY MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS019033
W. LOCAL COVERAGE DETERMINATIONS
http://www.cms.hhs.gov/mcd/search.asp
X. MEDICARE NATIONAL COVERAGE DERTERMINATIONS MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS014961&intNumPerPage=10
Y.
DATA USE AGREEMENT (DUA)
http://www.cms.hhs.gov/CMSForms/CMSForms/itemdetail.asp?filterType=keyword&filterValue=DUA&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS045932
Z. SUPPLEMENT TO DUA
http://www.cms.hhs.gov/cmsforms/downloads/cms-r-0235a.pdf
AA. CMS ANNUAL FREEDOM OF INFORMATION ACT (FOIA) REPORT
http://www.cms.hhs.gov/FOIA/05_annualreports.asp#TopOfPage.cms.hhs.gov/FOIA/
BB. FREEDOM OF INFORMATION ACT (FOIA) REQUEST FORM (CMS FORM 632)
http://www.cms.hhs.gov/FOIA/04_reqfrm.asp#TopOfPage
CC. INSTRUCTIONS FOR MA BIDS
http://www.cms.hhs.gov/healthplans/
DD. MA-PD BID PRICING TOOLS
http://www.cms.hhs.gov/pdps/
EE. BESS USER’S GUIDE
http://www.cms.hhs.gov/NonIdentifiableDataFiles/03_PartBExtractSummarySystem.asp FF. Access to CMS Computer Systems Form http://www.cms.hhs.gov/AccesstoDataApplication/Downloads/Access.pdf
GG. NOTICE OF PROPOSED RULEMAKING - E-PRESCRIBING
http://a257.g.akamaitech.net/7/257/2422/01jan20051800/edocket.access.gpo.gov/2005/pdf/05-1773.pdf
HH. CMS CERTIFICATION AND ACCREDITATION METHOLOGY
http://www.cms.hhs.gov/InformationSecurity/ List of Exhibits
E-1. FEDERAL REGISTER NOTICES
www.gpo.gov
E-2. CMS RULINGS
www.cms.hhs.gov/rulings/
E-3. SELF-ASSESSMENT
(see Government Team Leader for current self-assessment)
E-4 MEDICARE GENERAL INFORMATION, ELIGIBILITY AND ENTITLEMENT MANUAL
E-5 MEDICARE BENEFIT POLICY MANUAL
E-6 MEDICARE CLAIMS PROCESSING MANUAL
E-7 MEDICARE SECONDARY PAYER MANUAL
E-8 MEDICARE FINANCIAL MANAGEMENT MANUAL
E-9 MEDICARE CONTRACTOR BENEFICIARY AND PROVIDER COMMUNICATIONS MANUAL
E-10 STATE BUY-IN MANUAL
E-11 DEMONSTRATIONS
E-12. QUALITY IMPROVEMENT ORGANIZATION MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS019035&intNumPerPage=10
E-13. MEDICARE ESRD ORGANIZATION MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS019209&intNumPerPage=10
E-14. STATE OPERATIONS MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=dual, keyword&filterValue=medicaid&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS050483&intNumPerPage=10
E-15. MEDICARE MANAGED CARE MANUAL
http://www.cms.hhs.gov/Manuals/IOM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS019326&intNumPerPage=10
E-16. HOME HEALTH AGENCY MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS021914&intNumPerPage=10
E-17. HOSPICE MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS021923&intNumPerPage=10
E-18. HOSPITAL MANUAL
http://www.cms.hhs.gov/manuals/pbm/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021912&intNumPerPage=10
E-19. CARRIER MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS021921&intNumPerPage=10
E-20. INTERMEDIARY MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=-99&sortByDID=1&sortOrder=ascending&itemID=CMS021918&intNumPerPage=10
E-21. PEER REVIEW ORGANIZATION MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021922&intNumPerPage=10
E-22. PROVIDER REIMBURSEMENT MANUAL P. I
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021929&intNumPerPage=10
E-23. PROVIDER REIMBURSEMENT MANUAL P. II
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021935&intNumPerPage=10
E-24. MEDICARE RENAL DIALYSIS FACILITY MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021926&intNumPerPage=10
E-25. MEDICARE RURAL HEALTH CLINIC MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021925&intNumPerPage=10
E-26. SKILLED NURSING FACILITY MANUAL
http://www.cms.hhs.gov/Manuals/PBM/itemdetail.asp?filterType=none&filterByDID=0&sortByDID=1&sortOrder=ascending&itemID=CMS021915&intNumPerPage=10
E-27. HEALTH CARE PROVIDER COST REPORT INFORMATION SYSTEM (HCRIS)
http://www.cms.hhs.gov/CostReports/
E-28. CARRIER STANDARD SYSTEM USER GUIDE
http://www.cms.hhs.gov/ElectronicBillingEDITrans/08_HealthCareClaims.asp
E-29. INTERMEDIARY STANDARD SYSTEM USER GUIDE
www.cms.hhs.gov/providers/psc/userguid.asp
E-30. DURABLE MEDICAL EQUIPMENT REGIONAL CARRIER (DMERC) STANDARD SYSTEM USER GUIDE www.cms.hhs.gov/providers/psc/userguid.asp
E-31. COVERAGE DECISION MEMOS
http://www.cms.hhs.gov/DeterminationProcess/
E-32, SECURITY CLAUSE
http://cmsnet.cms.hhs.gov/hpages/oagm/PolicyNotices.htm
A. DELIVERABLES
ITEMS TO BE FURNISHED AND DELIVERABLE SCHEDULE
The Contractor shall submit all required reports and deliverables in accordance with the following schedule. Reports and/or deliverables submitted under this contract shall be in accordance with the Statement of Work entitled Zone Program Integrity Contractor Statement of Work.
DBIMO = Division of Benefit Integrity Management Operations
DMRE = Division of Medical Review & Education
IAW= In Accordance With
NCW = Medi-Medi National Coordinator Website
NLT = No Later Than
OPISI = One Program Integrity Systems Integrator
POC = Point of Contact
Notes:
1. All deliverables shall be entered into the CMS ARTS. All CMS ARTS deliverables shall be delivered electronically via email and/or secure email to the recipients noted, or as otherwise indicated in the schedule.
2. ALL DELIVERABLES, REGARDLESS OF CONTENT or METHOD OF SHIPMENT, SHALL BE “TRACKED” IN THE CMS ARTS. Additionally, all deliverable “content” shall be submitted into the CMS ARTS with the exception of deliverables that contains confidential and/or sensitive information and/or as otherwise noted (hard copy, etc.). Deliverable content that contains confidential or sensitive information shall be submitted via a secure method of shipment, e.g. secure email (preferable) or hard copy.
3. Deliverable dates that fall on a weekend or holiday shall be due on the first subsequent business day after the weekend or holiday.
Deliverables Schedule
| Item |
| Description |
| Recipient |
| Delivery Due Date |
| Media |
| 1. |
| Draft Project Management Plan IAW Statement of Work (SOW) Chap. 1, §§1.2.1.1.2, 1.2.1.2, and 1.2.3.2.1 |
| Primary Government Task Leader (GTL), Associate GTL |
| Draft plan is due 15 calendar days after Task Order award and subsequently 10 calendar days after a major change |
| Email notification, CMS ARTS |
| 2. |
| Final Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.2, 1.2.1.2, and 1.2.3.2.1 |
| Primary GTL, Associate GTL |
| Final plan is due 15 calendar days after the Task Order Kickoff Meeting and subsequently 10 calendar days after GTL comments when modified/updated as a result of major changes |
| Email notification, CMS ARTS |
| 3. |
| Draft Transition Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.1, 1.2.1.2, and 1.2.3.2.1.1 |
| Primary Government Task Leader (GTL), Associate GTL |
| Draft plan is due 15 calendar days after Task Order award and subsequently 10 calendar days after a major change |
| Email notification, CMS ARTS |
| 4. |
| Final Transition Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.1, 1.2.1.2, and 1.2.3.2.1.1 |
| Primary Government Task Leader (GTL), Associate GTL |
| Draft plan is due 15 calendar days after Task Order award and subsequently 10 calendar days after a major change |
| Email notification, CMS ARTS |
| 5. |
| Draft Implementation Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.2, 1.2.1.2, and 1.2.3.2.1.2 |
| Primary Government Task Leader (GTL), Associate GTL |
| Draft plan is due 15 calendar days after the Final Transition Project Management Plan |
| Email notification, CMS ARTS |
| 6. |
| Final Implementation Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.2, 1.2.1.2, and 1.2.3.2.1.2 |
| Primary Government Task Leader (GTL), Associate GTL |
| Final Plan is due 20 calendar days after the Draft Implementation Project Management Plan |
| Email notification, CMS ARTS |
| 7. |
| Draft Fully Operational Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.3, 1.2.1.2, and 1.2.3.2.1.3 |
| Primary Government Task Leader (GTL), Associate GTL |
| Draft Plan is due 15 calendar days after the Final Implementation Project Plan |
| Email notification, CMS ARTS |
| 8. |
| Final Fully Operational Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.3, 1.2.1.2, and 1.2.3.2.1.3 |
| Primary Government Task Leader (GTL), Associate GTL |
| Final Plan is due 20 calendar days after the Draft Implementation Project Plan |
| Email notification, CMS ARTS |
| 9. |
| Transition Deliverables List |
IAW SOW Chap. 1, §1.2.1.3 and §1.2.3.2.3 Primary GTL, Associate GTL, AC(s)
| No less than every 2 weeks during the transition period |
| Email to outgoing contractor(s), CMS ARTS |
| 10. |
| Implementation Deliverables List IAW SOW Chap. 1, §1.2.3.2.3 |
| Primary Government Task Leader (GTL), Associate GTL |
| No less than every 2 weeks during the implementation phase |
| Email to outgoing contractor(s), CMS ARTS |
| 11. |
| Fully Operational Deliverables List IAW SOW Chap. 1, §1.2.3.2.4 |
| Primary GTL, Associate GTL, |
Outgoing Contractor(s)
| No less than every 2 weeks during the fully operational phase |
| Email to outgoing contractor(s), CMS ARTS |
| 12. |
| Transition Meeting Minutes |
IAW SOW Chap. 1, §1.2.1.3
| Primary GTL, Associate GTL, Outgoing Contractor(s) |
| Within 3 business days of the meeting(s). |
| Email to outgoing contractor(s), CMS ARTS |
| 13. |
| Workload Release Dates and Transfer Procedures IAW SOW Chap. 1, §1.2.1.3 |
| Primary GTL, Associate GTL, Outgoing Contractor(s) |
| 10 business days after the first transition meeting |
| CMS ARTS (for GTLs) and E-mail (for outgoing contractor(s)) |
| 14. |
| Workload Review Listing IAW SOW Chap. 1, §1.2.1.3 |
| Primary GTL, Associate GTL, Outgoing Contractor(s) |
| 10 business days after the 1st transition meeting |
| CMS ARTS (for GTLs) and E-mail (for outgoing contractor(s)) |
| 15. |
| Draft Joint Operating Agreement |
IAW SOW Chap. 1, §1.2.3.2.5
| Primary GTL, Associate GTL, AC(s) or MAC(s) |
| 45 calendar days before transition or MAC alignment date |
| Email to AC or MAC, CMS ARTS |
| 16. |
| Final Joint Operating Agreement for signature |
IAW SOW Chap. 1, §1.2.3.2.5
| Primary GTL, Associate GTL, AC(s) or MAC(s) |
| 15 calendar days before the fully operational period or MAC alignment date |
| Email Notification to all, Email or Hard Copy to AC or MAC, CMS ARTS |
| 17. |
| Signed Final JOA |
IAW SOW Chap. 1, §1.2.3.2.5
| Primary GTL, Associate GTL, AC(s) or MAC(s) (original), and Contracting Officer (CO) |
| First day of fully operational period or MAC alignment date |
| Hard Copy w/CD-ROM, CMS ARTS, E-mail or hard copy to AC or MAC |
| 18. |
| Ongoing JOA Updates |
IAW SOW Chap. 2, §2.4.4.1
| Primary GTL (copy), Associate GTL (copy), AC(s) or MAC(s) (original), and Contracting Officer (CO) (copy) |
| Updated quarterly for the 1st year, by15 days following the end of each calendar quarter -1/15, 4/15, 7/15, and 10/15 |
After the 1st year, semi-annually on 1/15 and 7/15.
Hard Copy to AC or MAC, CD-ROM to CO, CMS ARTS
| 19. |
| JOA Non-Compliance Report IAW SOW Chap. 2, §2.4.4.1 |
| CO, PO, Primary GTL, Associate GTL |
| The report is submitted when an issue cannot be resolved between the parties within 30 calendar days. Due 3 business days after the 30 day period. |
| Hard Copy to AC or MAC, CD-ROM to CO, CMS ARTS |
| 20. |
| Draft Public Relations Plan |
IAW SOW Chap. 1, §1.2.3.2.6
| Primary GTL, Associate GTL |
| 45 calendar days after task order award |
| CMS ARTS |
| 21. |
| Final Public Relations Plan |
IAW SOW Chap. 1, §1.2.3.2.6
| Primary GTL, Associate GTL |
| 60 calendar days after task order award |
| CMS ARTS |
| 22. |
| Law Enforcement Request Report IAW SOW Chap.1, §1.2.3.2.13 |
| Primary GTL, Associate GTL |
| 15th Calendar Day after the end of each calendar quarter - 1/15, 4/15, 7/15, and 10/15 |
| CMS ARTS |
| 23. |
| Transition Lessons Learned Report |
IAW SOW Chap. 1, §1.2.3.2.7
| Primary GTL, Associate GTL |
| 30 calendar days after transition date |
| CMS ARTS |
| 24. |
| Implementation Lessons Learned Report |
IAW SOW Chap. 1, §1.2.3.2.7
| Primary GTL, Associate GTL |
| 30 calendar days after the end of the first full year of Task Order contract. |
| CMS ARTS |
| 25. |
| Cost Report |
IAW SOW Chap. 1, §1.2.3.2.8 and Chap. 4, §4.9.2
| Primary GTL, Associate GTL, CO |
| 20th of every month |
CMS ARTS
| 26. |
| Self-Assessment Report |
IAW SOW Chap. 1, §§1.2.3.2.9 and 1.2.3.2.9.1
| Primary GTL, Associate GTL , CO |
| 5.5 months prior to completion of the Task Order period of performance |
| CMS ARTS, Email notification |
| 27. |
| Award Fee Plan Evaluation |
IAW SOW Chap. 1, §1.2.3.2.9.2
| Primary GTL, Associate GTL, CO |
| 15 calendar days after the end of the Award Fee Evaluation Period as identified in each task order |
| CMS ARTS, Email notification |
| 28. |
| CMS Information System Security (CISS) tool as amended by CMS IAW SOW Chap. 1, §1.5.7.2 |
| DBIMO Systems Security Officer, |
| Annually on |
April 1 CD-ROM, Timestamp in CMS ARTS, Email notification
| 29. |
| E-Authorization Risk Assessment IAW SOW Chap. 1, §1.5.7.2.5 |
| DBIMO Systems Security Officer |
| 15 calendar days after final Information Technology System Plan submission – Initial Submission. Annual update 365 calendar days from the last submission, and 30 calendar days after a major system change. |
| E-mail notification, CD-ROM, CMS ARTS |
| 30. |
| Security Risk Assessment (RA) |
Chap. 1, §1.5.7.2.5
| DBIMO Systems Security Officer, |
| 15 calendar days after final Information Technology System Plan submission – Initial Submission. Annual update 365 calendar days from the last submission and 30 calendar days after a major system change |
| CD-ROM, CMS ARTS, Email notification |
| 31. |
| System Security Plan |
IAW SOW Chap. 1, §1.5.7.2.5
| DBIMO Systems Security Officer |
| 15 calendar days after final Information Technology System Plan submission - Initial Submission. Thereafter, 365 calendar days from the last date submitted and 30 calendar days after a major system change. |
| Hard Copy w/CD-ROM, CMS ARTS, Email notification |
| 32. |
| Security Corrective Action Plans (CAPS) |
IAW SOW Chap. 1, §1.5.7.2.3 and IOM Pub. 100-06
| DBIMO Systems Security Officer, |
| 30 calendar days after official notification of a security audit finding |
| CD-ROM, CMS ARTS, Email notification |
| 33. |
| Plan of Action and Milestones (POA&M) IAW SOW Chap. 1, §1.5.7.2.3 |
| DBIMO Security Systems Officer |
| 30 calendar days after submission of a CAP for a deficiency – Initial Submission and monthly on the 4th of the month until CAP for the deficiency is completed |
| E-mail notification, CD-ROM, CMS ARTS |
| 34. |
| Business Continuity Plan (BCP) |
IAW SOW Chap. 1, §1.5.7.2.5. Also, referred to as the Security IT Systems Contingency Plan.
| DBIMO Systems Security Officer, |
| 15 calendar days after final Information Technology System Plan submission – Initial Submission. |
Thereafter, 365 calendar days from the last date submitted or updated and 30 calendar days after a major system change.
DBIMO SSO Approvals to GTL & Associate GTL within 10 working days.
CD-ROM, CMS ARTS, Email notification
| 35. |
| Test of Business Continuity Plan IAW SOW Chap. 1, §1.5.7.2.5 |
| DBIMO Systems Security Officer |
| March 1, 2009 – Initial Submission. Thereafter, 365 calendar days from the last date of test. |
| E-mail notification, CD-ROM, CMS ARTS |
| 36. |
| Privacy Impact Analysis IAW SOW Chap. 1, §1.5.7.2 |
| DBIMO Systems Security Officer |
| May 1, 2009 – Initial Submission. Thereafter, 365 calendar days from the date of last test submission. |
| E-mail notification, CD-ROM, CMS ARTS |
| 37. |
| Corrective Action Attestation IAW SOW Chap. 1, §1.5.7.2.3 and §1.5.7.2.4 |
| DBIMO Systems Security Officer |
| September 4, 2008 – Initial Submission. Thereafter, September 4th of each year. |
| E-mail notification, Original Signature hard copy, CMS ARTS |
| 38. |
| Draft Information Technology (IT) Systems Plan |
IAW SOW Chap. 1, §1.2.3.2.10 and §1.5.3 and Chap. 4, §4.9.5
| DBIMO Systems Security Officer, Participating State, as applicable |
| 30 calendar days after contract award and thereafter, within 10 calendar days of identification of a change. |
| CMS ARTS, E-mail notification, NCW |
| 39. |
| Final Information Technology (IT) Systems Plan IAW SOW Chap. 1, §1.2.3.2.10 and §1.5.3 and Chap. 4, §4.9.5 |
| DBIMO Systems Security Officer, Participating State, as applicable |
| Final no later than 60 calendar days after contract award. |
Subsequent changes within 40 calendar days of identification of a change.
CMS ARTS, E-mail notification, NCW
| 40. |
| Ad Hoc Reports |
IAW SOW Chap. 1, §1.4.4 and §2.4.2
| Primary GTL, Associate GTL |
| As requested (to be confirmed via email from GTL) |
| As requested |
| 41. |
| Annual Deceased Beneficiary Improper Payment Report |
IAW SOW Chap. 2, §2.4.1 and Appendix M, §13
| dbim@cms.hhs.gov (email w/ attachment), Primary GTL, Associate GTL |
| December 5th of each year. |
| E-mail, Timestamp in CMS ARTS |
| 42. |
| Fraud Investigation Database (system) |
IAW SOW Chap. 2, §2.4.1
| CMS |
| IAW PIM |
| FID |
| 43. |
| Telecommunications Form |
IAW SOW Chap. 1, §1.5.4.1 and §1.5.4.2
| Primary GTL (original), Associate GTL (copy) |
| At least 90 calendar days before the expected operational delivery date for telecommunication services |
| E-mail, Hard Copy |
| 44. |
| Data Use Agreement (DUA) |
IAW SOW Chap.1, §1.5.1.1 & Appendix Y
| Primary GTL (original), Associate GTL (copy) |
| No later than 30 calendar days prior to the fully operational phase. |
| Hard Copy |
| 45. |
| Continuous Improvement Reports IAW SOW Chap. 1, §1.6.1.2 |
| Primary GTL, Associate GTL |
| As determined in each Task Order |
| CMS ARTS |
| 46. |
| Shared Systems (Fiscal Intermediary Shared System (FISS), Medicare Carrier System (MCS), VIPS Medicare System (VMS), Common Working File) Change Requests |
IAW SOW Chap. 1, §1.5.2.1
| Primary GTL, Associate GTL |
| Ongoing |
| E-mail Notification, CMS ARTS |
| 47. |
| Individual Subcontracting Report (ISR) (formerly Standard Form 294) |
IAW contract section H
| CO (original), SBA (copy) |
| April 30 and October 31 |
| eSRS |
| 48. |
| Summary Subcontracting Report (SSR) (formerly Standard Form 295) |
IAW contract section H
| CO (original), SBA (copy) |
| Annually on October 31 |
| eSRS |
| 49. |
| Organizational Conflict of Interest Certificate |
IAW contract section H
| CO (original + 2 cys) |
| Annually on October 31 |
| Hard Copy, Timestamp in CMS ARTS |
| 50. |
| FOIA Contractor Summary Sheet |
IAW SOW Chapter 1, §1.2.3.2.12 & Appendix H
| RO FOIA Coordinator (copy), Primary GTL (original), Associate GTL (copy) |
| Fifth business day of the month for all requests received the previous month. |
| Hard Copy, Timestamp in CMS ARTS |
| 51. |
| Freedom of Information Log |
IAW SOW Chapter 1, §1.2.3.2.12 & Appendix H
| RO FOIA Coordinator (copy), Primary GTL (original), Associate GTL (copy) |
| Fifth business day of the month for all requests received the previous month. |
| E-mail or Hard Copy, Timestamp in CMS ARTS |
| 52. |
| CMS Form 632 (Freedom of Information Act (FOIA) Request Form) |
IAW SOW Chap. 1, §1.2.3.2.12 and Appendix BB
| RO FOIA Coordinator (copy), Primary GTL (original), Associate GTL (copy) |
| As required |
| Hard Copy, Timestamp in CMS ARTS |
| 53. |
| Annual FOIA Report |
IAW SOW Chap. 1, §1.2.3.2.12 and Appendix AA
| RO FOIA Coordinator (copy), Primary GTL (original), Associate GTL (copy) |
| Annually per CMS request |
| As requested |
54.
Strategy Analysis Report (SAR)
IAW SOW Chap. 1, §1.7.1
| Primary GTL, Associate GTL, CMS DMRE, MRSTRATEGIES@cms.hhs.gov |
| Submit by 7 ½ months after contract award or 7 ½ months after option is exercised. (Submit until the MR function not in support of |
BI is fully transitioned to a MAC.)
E-mail Notification, CMS ARTS
| 55. |
| MR Strategy |
IAW SOW Chap. 1, §1.7.1
| Primary GTL, Associate GTL, CMS DMRE, MRSTRATEGIES@cms.hhs.gov |
| Initial within 30 calendar days after contract award; thereafter, 30 calendar days prior to option year award. (Submit until the MR function not in support of |
BI is fully transitioned to a MAC.)
E-mail Notification, CMS ARTS
| 56. |
| CD ROM of all deliverables |
IAW SOW Chap. 1, §1.2.3.1
| CO (original), Primary GTL (copy), Associate GTL (copy) |
| Annually 30 calendar days after the last day of task order period of performance. |
| CD-ROM, Timestamp in CMS ARTS |
| 57. |
| Vulnerability Reports IAW SOW Chap. 2, §2.4.1 |
| N/A |
| Per PIM, Chap. 4, §4.31 |
| Per PIM, Chap. 4, §4.31 |
| 58. |
| Log of Actual Referrals to Law Enforcement IAW SOW Appendix M, §5.2 |
| Primary GTL, Associate GTL |
| 1st business day of every month for previous month’s status |
| CMS Secure E-mail |
| 59. |
| Law Enforcement Kick-Off Meeting Notes and Deliverables IAW SOW Chap. 3, §3.2.1.1 and §3.2.2.1 |
| Primary GTL, Associate GTL |
| Within 3 business days of the meeting |
| Secure E-mail |
| 60. |
| Executive Summaries of Law Enforcement Referrals IAW SOW Chap. 3, §3.2.2.7 |
| Primary GTL, Associate GTL |
| Within 2 business days of referral to law enforcement |
| Secure E-mail |
| 61. |
| Target Audit Report IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL, Part D Compliance Officer, Part D Account Manager |
| As specified in individual task order |
| Secure E-mail |
| 62. |
| Fraud, Waste, and Abuse Compliance Audit Report IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL, Part D Compliance Officer, Part D Account Manager |
| 30 calendar days after completion of the audit |
| Secure E-mail |
| 63. |
| BI Audit Reports IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL, Part D Compliance Officer, Part D Account Manager |
| 30 calendar days after completion of the audit |
| Secure E-mail |
| 64. |
| P & T Committee Audit Report IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL, Part D Compliance Officer, Part D Account Manager |
| 30 calendar days after completion of the audit |
| Secure E-mail |
| 65. |
| Other BI Audit Reports IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL, Part D Compliance Officer, Part D Account Manager |
| 30 calendar days after completion of the audit |
| Secure E-mail |
| 66. |
| MA Audit Report IAW SOW Appendix M, §8.1.1 |
| Primary GTL, Associate GTL |
| As specified in individual task order |
| Secure E-mail |
| 67. |
| Employer Audit Report (RDS) IAW SOW Appendix M, §8.2 |
| Primary GTL, Associate GTL |
| As specified in individual task order |
| Secure E-mail |
| 68. |
| Actuarial Equivalence Attestation Audit Report IAW SOW Appendix M, §8.3.1 |
| Primary GTL, Associate GTL |
| As specified in individual task order |
| Secure E-mail |
| 69. |
| RDS Payment Audit Report IAW SOW Appendix M, §8.3.2 |
| Primary GTL, Associate GTL |
| As specified in individual task order |
| Secure E-mail |
| 70. |
| Creditable Coverage Disclosures Audit Report IAW SOW Appendix M, §8.3.3 |
| Primary GTL, Associate GTL |
| As specified in individual task order |
| Secure E-mail |
| 71. |
| List of Entities for Further Review IAW Appendix M, §11 |
| Primary GTL, Associate GTL |
| As directed by the Primary GTL and Associate GTL |
| Secure E-mail |
| 72. |
| Log of Education Referrals to CMS IAW Appendix M, §14 |
| Primary GTL, Associate GTL |
| 1st business day of every quarter |
| Secure E-mail |
| 73. |
| Improper Payments Report IAW SOW Chap. 3, §3.2.2.8 and Appendix M, §12 |
| Primary GTL, Associate GTL, Director of Program Integrity Analysis and Evaluation |
| November 1st of each calendar year |
| Secure E-mail |
| 74. |
| Subcontractor or Provider Education Referral IAW SOW Appendix M, §14 |
| Primary GTL, Associate GTL, Appropriate Account Manager |
| Within 3 business days of decision not to refer to LE |
| Secure E-mail |
| 75. |
| Education Referral IAW SOW Appendix M, §14 |
| Primary GTL, Associate GTL, Appropriate Account Manager |
| Within 3 business days of decision not to refer to LE |
| Secure E-mail |
| 76. |
| Draft National Medicare Fraud Alert Package IAW SOW Appendix M, §15.1 |
| Primary GTL, Associate GTL |
| As soon as potential fraud is detected |
| Password-Protected Secure E-mail |
| 77. |
| Draft Restricted Medicare Fraud Alert Package IAW SOW Appendix M, §15.1 |
| Primary GTL, Associate GTL |
| As soon as potential fraud is detected |
| Password-Protected Secure E-mail |
| 78. |
| Draft Restricted CMS Central Office Fraud Alert Package IAW SOW Appendix M, §15.1 |
| Primary GTL, Associate GTL |
| As soon as potential fraud is detected |
| Secure E-mail |
| 79. |
| Final Fraud Alert Packages (NMFA, RMFA, RCCOFA, and ZPIC FA) IAW SOW Appendix M, §15.1 |
| Intended Audience with copies to the Primary GTL, and Associate GTL |
| When final Fraud Alert is distributed |
| Secure E-mail |
| 80. |
| Draft Notice of Suspension of Payment, Enrollment or Marketing or Draft CMP Notice and Summary of Evidence for Action IAW SOW Appendix M, §16.2.1.3 and §1.6.2.2.2 |
| Primary GTL, Associate GTL |
| As soon as ZPIC proposes to take action against a Medicare contractor |
| Secure E-mail |
| 81. |
| Notice of Incentive Reward Payment IAW SOW Appendix M, §17.7 |
| Primary GTL, Associate GTL |
| As soon as complainant has returned complete reward claim form |
| Secure E-mail |
| 82. |
| Notice of Payments to Excluded Providers IAW SOW Appendix M, §18 |
| Primary GTL, Associate GTL |
| As soon as ZPIC identified improper payments to an excluded provider |
| Secure E-mail |
| 83. |
| CMP Recommendation IAW Appendix M, §1.6.2.3.2 |
| Primary GTL, Associate GTL |
| As soon as the need for a CMP is identified |
| Secure E-mail |
| 84. |
| Draft Medi-Medi Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.2, 1.2.1.2, and 1.2.3.2.1 and Chap. 4, §4.4.2.2 |
| Medi-Medi GTL(s); Hard copies for attendees of Project Initiation Meeting |
| Draft plan is due at the Project Initiation Meeting, which occurs NLT 30 calendar days after a state task is awarded and subsequently 10 calendar days after a major change |
| E-mail notification, CMS ARTS, NCW, and hard copy at the Project Initiation Meeting |
| 85. |
| Final Medi-Medi Project Management Plan IAW SOW Chap. 1, §§1.2.1.1.2, 1.2.1.2, 1.2.3.2.1 and Chap. 4, §4.4.2.2 |
| Medi-Medi GTL(s), attendees of Project Initiation Meeting |
| Final Plan is due NLT 60 calendar days after a state task is awarded and subsequently 10 calendar days after a major change |
| E-mail notification, CMS ARTS, and NCW |
| 86. |
| Medi-Medi Transition Deliverable List IAW SOW Chap. 1, §1.2.1.3 and §1.2.3.2.2 |
| Medi-Medi GTL(s), Outgoing Contractor, Participating State |
| List is due 10 business days after Project Initiation Meeting and updated as necessary |
| E-mail notification, CMS ARTS, NCW |
| 87. |
| Medi-Medi Transition Meeting Minutes IAW SOW Chap. 1, §1.2.1.3 |
| Medi-Medi GTL(s), Outgoing Contractor, Participating State |
| Within 3 calendar days of the meeting(s) |
| E-mail notification, CMS ARTS, NCW |
| 88. |
| Draft Medi-Medi Joint Operating Agreement IAW SOW Chap. 1, §1.2.3.2.5 and Chap. 4, §§4.4.2.3.1, 4.4.3.1.1, and 4.9.4 |
| Medi-Medi GTL(s), Participating State, OPISI (when applicable) |
| Draft plan is due at the Project Initiation Meeting, which occurs NLT 30 calendar days after a state task is awarded |
| E-mail notification, CMS ARTS, NCW, and hard copy at the Project Initiation Meeting |
| 89. |
| Final Medi-Medi Joint Operating Agreement IAW SOW Chap. 1, §1.2.3.2.5 and Chap. 4, §§4.4.2.3.1, 4.4.3.1.1, and 4.9.4 |
| Medi-Medi GTL(s), Participating State, OPISI (when applicable) |
| 90 calendar days after state task award |
| E-mail notification, CMS ARTS, NCW, hard copy to signatories |
| 90. |
| Medi-Medi Ongoing JOA Updates IAW SOW Chap. 1, §1.2.3.2.5 and Chap. 4, §§4.4.2.3.1, 4.4.3.1.1, and 4.9.4 |
| Medi-Medi GTL(s), Participating State, OPISI (when applicable) |
| Updated annually on 7/15 |
| E-mail notification, CMS ARTS, NCW, hard copy to signatories |
| 91. |
| Medi-Medi Monthly Status Report (one per state) IAW SOW Chap. 4, §4.9.1 |
| Medi-Medi GTL(s), applicable participating state |
| 20th of every month |
| CMS ARTS, NCW |
| 92. |
| Draft Medi-Medi Data Analysis Plan IAW SOW Chap. 4, §4.9.6 (one per state) |
| Medi-Medi GTL(s), applicable participating state |
| Annually 60 calendar days before the end of the contract year |
| E-mail notification, NCW, CMS ARTS |
| 93. |
| Final Medi-Medi Data Analysis Plan IAW SOW Chap. 4, §4.9.6 (one per state) |
| Medi-Medi GTL(s), applicable participating state |
| Annually 15 calendar days before the end of the contract year |
| E-mail notification, NCW, CMS ARTS |
| 94. |
| Medi-Medi Data Matching Protocol IAW SOW Chap. 4, §4.9.7 (one per state) |
| Medi-Medi GTL(s), applicable participating state |
| 180 calendar days after state task award |
Subsequent changes within 15 calendar days of identification of a change.
E-mail notification, NCW, CMS ARTS
| 95. |
| Medi-Medi Cross Claims Analysis Catalog Entries IAW SOW Chap. 4, §4.9.8 |
| Medi-Medi GTL(s), applicable participating state |
| 20th calendar day after the end of each calendar quarter – 1/20, 4/20, 7/20, and 10/20 |
| E-mail notification, NCW, CMS ARTS |
| 96. |
| Draft Medi-Medi Steering Committee Charter IAW SOW Chap. 4. §4.9.9 |
| Medi-Medi GTL(s), applicable participating state, and other steering committee members |
| Draft charter is due at the first steering committee meeting |
| E-mail notification, NCW, CMS ARTS, hard copy for meeting attendees |
| 97. |
| Final Medi-Medi Steering Committee Charter IAW SOW Chap. 4, §4.9.9 |
| Medi-Medi GTL(s), applicable participating state, and other steering committee members |
| Final charter is due 7 calendar days after ratification at the second steering committee meeting |
Subsequent changes within 15 calendar days of identification of a change.
E-mail notification, NCW, CMS ARTS
| 98. |
| Medi-Medi Steering Committee Minutes IAW SOW Chap. 4, §4.9.10 |
| Medi-Medi GTL(s), applicable participating state, and other steering committee attendees |
| Within 7 calendar days of the steering committee meeting |
| E-mail notification (fax or secure e-mail for PHI), NCW, CMS ARTS |
Recipient Addresses:
Theresa Schultz
Contracting Officer (CO)
Centers for Medicare & Medicaid Services
Office of Acquisition and Grants Management
Medicare Contracts Group
Division of Medicare Support Contracts
7500 Security Blvd, Mail Stop: C2-21-15
Baltimore, Maryland 21244
Email:
Theresa.Schultz@CMS.HHS.Gov Phone:
410-786-8496
Location:
C2-24-16 Project Officer (PO)
Centers for Medicare & Medicaid Services
Office of Financial Management
7500 Security Blvd, Mail Stop: C3-02-16
Baltimore, Maryland 21244
Government Task Leader (GTL)
As defined in task order Statement of Work
Associate Government Task Leader (Associate GTL)
As defined in the task order Statement of Work
CMS Division of Benefit Integrity Management Operations (DBIMO)
Centers for Medicare & Medicaid Services
Office of Financial Management
7500 Security Blvd, Mail Stop: C3-02-16
Baltimore, Maryland 21244
CMS Division of Benefit Integrity Management Operations (DBIMO) Systems Security Officer
Centers for Medicare & Medicaid Services
OFM/PIG/DBIMO
7500 Security Blvd., Mail Stop: C3-02-16
Baltimore, Maryland 21244
CMS Division of Benefit Integrity Management Operations (DBIMO) Medi-Medi Program Lead
Centers for Medicare & Medicaid Services
OFM/PIG/DBIMO
7500 Security Blvd., Mail Stop C3-02-16
Baltimore, Maryland 21244
CMS Division of Medical Review & Education (DMRE) Centers for Medicare & Medicaid Services
OFM/PIG/DMRE
7500 Security Blvd, Mail Stop: C3-02-16
Baltimore, Maryland 21244
Division of MMA Integrity
Centers for Medicare & Medicaid Services
Office of Financial Management/Program Integrity Group/Division of MMA Integrity
7500 Security Blvd., Mail Stop: C3-02-16
Baltimore, Maryland 21244
Regional Office FOIA Coordinator
TBD
Until the RO FOIA Coordinator is identified, please submit to:
Sam Seidman, Freedom of Information Specialist
Centers for Medicare & Medicaid Services
Freedom of Information Group
7500 Security Blvd, Mail Stop: N2-20-16
Baltimore, Maryland 21244
Fax: 410.786.0474
Phone: 410.786.3327
Small Business Administration (SBA)
CMS Small Business Specialist
Attn: Alice Roache
Centers for Medicare & Medicaid Services
Office of Acquisition and Grants Management
Acquisition Support & Policy
7500 Security Blvd, Mail Stop: C2-21-15
Baltimore, Maryland 21244 and
Linda Purnell
Dept. of Health and Human Services
Office of the Secretary
200 Independence Ave., SW, Room 517-D
Washington, DC 20201
B. TRANSFER OF BENEFIT INTEGRITY MANAGER INFORMATION FROM AFFILIATED CONTRACTOR AND THE MEDICARE ADMINISTRATIVE CONTRACTOR
The Zone Program Integrity Contractor (ZPIC) shall have access to the Affiliated Contractors’ (ACs’)and Medicare Administrative Contractors’ (MACs’) pricing files in order to make least-costly alternative decisions and other payment determinations that require clinical expertise.
The AC and the MAC will furnish the following information to the ZPIC:
· Local coverage determinations and internal medical review guidelines.
· Program safeguard edit parameters in hard copy format.
· Carrier Advisory Committee minutes for the past 3 years.
· Provider newsletters sent during the prior 3 years.
· A report highlighting program safeguard activities from the previous 12 months.
· Complex reviews and other post-pay reviews in process.
· All Benefit Integrity (BI) files (e.g., case referrals to Office of the Inspector General (OIG), fraud alerts, etc.).
· Medical documentation and other claims attachments for any claims currently under review and not yet paid.
· History of all contacts with specific providers for the last 3 years.
· Flagged providers/category III edits.
C. DATA RELEASE POLICIES AND PROCEDURES
1 - General
This section specifies the procedures that the Zone Program Integrity Contractor (ZPIC) shall follow under each of the Privacy Act (PA) data release provisions. The Centers for Medicare & Medicaid Services (CMS) is in the process of updating these procedures to incorporate privacy regulations of the Health Insurance Portability and Accountability Act of 1996 (HIPAA) and this appendix is subject to change upon their completion.
2 - Release of Data with Individual’s Consent
An individual may have access to any record maintained on him/her in a system of records. The ZPIC shall provide such access upon receipt of a request in writing and verification of the individual’s identity. The individual may request that data being maintained be sent to another party. ZPIC staff will send the data upon receipt of a completed Consent Statement. No fee will be charged for searching for an individual’s personal record or for a photocopy when a copy must be made in order to provide access to the record.
3 - Release of Identifiable Data Within CMS and Within Health and Human Services
3.1 - General
Identifiable data may be released within an agency from one employee to another employee on a need-to-know basis. That is, the requesting employee must need the data in identifiable form in order to perform his/her duties. The Department of Health and Human Services (HHS) is considered to be a single agency.
3.2 - Release Within CMS
Within CMS, both non-identifiable and identifiable data may be obtained from the Office of Information Services (OIS) by completing a Request for Information form. If identifiable data are requested, OIS will generally accept the CMS component’s determination that the data are needed in identifiable form unless it is obvious that more data are being requested than necessary or the data requested are unrelated to the purpose of the request. If the component intends to re-release the data to a contractor/grantee or other non-government entity, the CMS component and the non-government source must sign an Agreement for Release of Data with Individual Identifiers, binding the user to protect the confidentiality of the data. The agreement must be signed and must accompany the Request for Information form before data are released.
3.3 - Release Within HHS
Requestors outside of CMS, but within the Department of Health and Human Services, can also receive individually identifiable data on a need-to-know basis. CMS requires HHS agencies to meet the same criteria as are specified under the subsection Basic Routine Uses, below, and also to follow the same process. An exception to this is the approval of a research project by the component’s review panel, which will be accepted as establishing that the project is important and soundly designed. If the component plans to complete the research project in-house, the component will be required to sign a Federal Agreement for Release of Data with Individual Identifiers. There may be a charge for providing data.
4 - Release of Identifiable Data Outside of the Department for Purposes Compatible With Program Objectives (Routine Uses)
4.1 - General
Identifiable data may be released outside HHS without the beneficiary’s consent for “routine uses” that have been published in the Federal Register as part of the notice of the system of records containing the requested data. Routine uses must be compatible with purposes for which the data in the system were initially collected. Most of CMS’ routine uses are necessary in order to operate the Medicare/Medicaid programs: release to state welfare agencies, Quality Improvement Organizations, providers and suppliers, and state audit agencies, and to the Justice Department for litigation. A number of CMS components have routine uses for release of data for health research, for analysis of Medicare payment policies, for data processing by contractors, for determination of the quality and effectiveness of hospital care, for state agency cost containment, for Medicare hospital mortality analysis, and for other uses compatible with CMS’ mission. An outline of common routine uses follows. It should be noted that there is a charge, in most cases, for data released under a routine use.
4.2 - Basic Routine Uses
4.2.1 - Research Routine Use
Identifiable data may be released to an individual or organization for a health-related research evaluation or epidemiologic project when certain criteria (below) are met and a specific process is followed. (This provision for release of data is contained in System of Records notices for a number of CMS’ major data systems.)
4.2.1.1 - Criteria
· Purpose requires individually identifiable records.
· Project is of sufficient importance to warrant effect, or risk, on beneficiary privacy.
· There is reasonable probability that use of data will accomplish purpose, i.e., project is soundly designed and properly financed.
· Data will be protected and identifiers removed as soon as possible.
· Requester signs agreement to abide by CMS’ data release policies and procedures.
4.2.1.2 - Procedures to Obtain Data for Research Purposes
· Request is sent to the appropriate CMS component explaining purpose of the project, data needed, and how data would be used. The following documentation should accompany the request:
· Copy of research or evaluation protocol or detailed project plan that will be reviewed by research experts to determine if criteria are met.
· Copy of report of review by panel of scientists (if applicable).
· Copy of form (face sheet of grant/contract/cooperative agreement) showing that the project is funded.
· Documentation will be reviewed:
· To determine that data requested are available.
· By an appropriate CMS component to determine that the criteria are met. (This process takes approximately 6 weeks.) Approval by review panel of experts outside of CMS may be accepted as proof that the criteria are met.
· If all criteria are met, a data release agreement will be sent to the requester(s) for signature(s).
· This routine use may be used to release data under a CMS contract/grant/cooperative agreement. The component must obtain a copy of the data release agreement (or use a similar agreement that protects data confidentiality). The component and the contractor sign the agreement. A copy of the agreement must be sent to OIS where a master database of all CMS agreements is maintained.
· When the names and/or addresses of beneficiaries are requested to solicit them for participation in a research project not funded by CMS, a letter over the Administrator’s signature must be sent to each beneficiary.
4.2.2 - Data Processing Contractor Routine Use
This routine use permits release of identifiable data to CMS contractors for the purpose of data processing: collating, analyzing, aggregating, or otherwise processing data. Data would also be disclosed incidental to consultation, programming, operation or user assistance. ZPIC employees are required to sign statements agreeing to protect the data. (This provision is included in System of Records notices for all of CMS’ major data systems.)
4.2.3 - Quality and Effectiveness of Care MEDPAR (QC/MEDPAR) Routine Use - OIS Only
OIS will release the QC/MEDPAR to entities for research on, and evaluation of, the quality and effectiveness of care provided in hospitals. The focus must be on measures of determining, validating, evaluating, and monitoring quality and effectiveness in such areas as access and outcomes. A major difference between the characteristics of this file and the EXMM file is that the ZIP code of the beneficiary’s residence is provided, and an encrypted beneficiary health insurance account number is included, making it possible to follow the beneficiary from month to month and year to year.
4.2.3.1 - Criteria
· The research and/or evaluation purpose requires data in detailed form as provided in the file.
· The purpose is likely to be accomplished in light of requesting entity’s capabilities and other factors.
· The purpose is of sufficient importance to warrant effect on and risk to beneficiary privacy.
4.2.3.2 - Procedures to Obtain Data
Entity must submit to OIS, and CMS must approve the following:
· A research and/or an evaluation plan specifying the objectives of the research and/or evaluation, how data will be used, financial support, and completion date.
· A copy of report by panel of experts on review of plan (where such a review was performed).
Upon receipt of the above:
· The appropriate CMS component will review the plan and the documentation, determine if criteria are met, and provide a recommendation to OIS on release.
· Requester will be required to sign QC/MEDPAR data release agreement.
· Requester will be required to send a certified check/money order for the cost of the QC/MEDPAR file.
4.2.4 - State Agency Cost Containment and Quality and Effectiveness of Care Routine Use
CMS may release data with individual identifiers to a qualified state agency for purposes of determining, evaluating and/or assessing cost, effectiveness, and/or quality of health care services provided in the state. Release of the data is governed by the routine use published in the Federal Register on Thursday, December 29, 1988, page 52792. The agency must meet the criteria listed below and also follow the procedures specified below:
4.2.4.1 - Criteria
· Requesting organization must be an agency of a state government or established by state law.
· The data must be requested and used for the purpose of determining, evaluating and/or assessing cost, effectiveness and/or the quality of health care services provided in the state.
· Use or disclosure of the data must not violate legal limitations under which the data were provided, collected, or obtained.
· Once received by agency, data must be exempt from disclosure under any state/local Freedom of Information Act.
· Data with individual identifiers must be required to accomplish agency purposes.
· Agency purpose must be of sufficient importance to warrant effect and/or risk on beneficiary’s privacy.
· It must be reasonable to expect that the agency will be able to accomplish its purposes in using the data.
4.2.4.2 - Procedures to Obtain Data that State Agency Must Submit
State agency must submit:
· Documentation that it is a part of the state government or established by state law, e.g., submit a copy of enabling legislation.
· A copy of its operating plan that provides detail about goals, strategy, and activities that are being carried out and/or planned to accomplish goals, including periodic reports. It must be clear how CMS data would be used.
· Evidence that data would be exempt from any state or local Freedom of Information Act (FOIA).
· Signed data release agreement stipulating that state agency:
· Will not use data for other purposes.
· Will not publish data in a form permitting deduction of individual identities.
· Will submit a copy of aggregated data or proposed table shells to CMS prior to publication.
· Will make no further disclosure except for emergencies, to another CMS-approved project, or for official audits.
· Will establish reasonable safeguards to protect data.
4.2.4.3
- Expenses
As with other data released outside of CMS, there is a charge for data released to states.
4.2.5 - Congressional Office Routine Use
Data with individual identifiers may be released to a Congressional office in response to an inquiry made by the individual to the member of Congress. A separate provision of the Privacy Act authorizes release to the Congress itself or to a committee of the Congress. This provision is included in System of Records notice for all of CMS’ major data systems. (See Release of Identifiable Data to the Congress, below.)
4.2.6 - Bureau of the Census Routine Use
Data may be released to the Census Bureau to enable the Bureau to process research and statistical data for Social Security projects. A separate provision of the Privacy Act authorizes release of data for census purposes. This provision is included in System of Records notices for all of CMS’ major data systems. (See Release of Identifiable Data to the Bureau of the Census, below.)
4.2.7 - Justice Department (or Court or other Tribunal) Routine Use
This routine use authorizes release of identifiable data to the Department of Justice (or a court) in litigation where the Department of Justice has agreed to represent an employee of HHS in his/her official or private capacity. (This provision is included in System of Records notices for all of CMS’ major data systems.)
4.2.8 - Other Routine Uses
Various CMS systems have other routine uses in addition to those already mentioned in this subsection. For example, a new routine use was recently developed for OIS’s Medicare Bill File (Statistics). The new routine use permits the release of Medicare inpatient hospital data to allow an individual hospital to conduct mortality studies of its facility. As with all routine uses, there are specific procedures that hospitals must follow to obtain the data.
Due to the number of routine uses that evolve over time, and the specialized nature of each routine use, it is impractical to cover all of them in this guide. All routine uses are published in the Federal Register. A copy of the criteria for a particular routine use may be obtained by contacting the Privacy Act coordinator in the component that is designated the system manager.
5 - Release of Identifiable Data to the Bureau of the Census
Data may be released to the Census Bureau for census-taking purposes, including making population estimates between census taking and as a cross-check of persons missing in census counts of aged persons. Release for census purposes is specifically authorized by a special disclosure provision in the Privacy Act. Release of data to the Census Bureau for research with which the Census undertakes to assist other federal agencies must be authorized under the provisions of the routine use described in the preceding section, Release of Identifiable Data Outside of the Department for Purposes Compatible with Program Objectives (Routine Uses). CMS does require Census to sign a Federal Agreement for Release of Individual Identifiable Data. CMS may also recover its processing costs.
6 - Release of Statistical Data
Data that contain no individual identifiers or data elements that would permit the identity of a beneficiary to be deduced (e.g., date of birth, residence, ZIP code) may be released as statistical data. CMS releases many statistical tables containing aggregate data.
7 - Release for a Civil or Criminal Law Enforcement Activity
CMS releases identifiable information in response to requests from any governmental agency for law enforcement activities authorized by federal, state, or local law, upon the request of the head of the law enforcement agencies specifying the data needed and the law to be enforced. Data have been released to a state health department enforcing a law requiring family approval before removing a deceased individual’s organs for transplant purposes. Data were also released to the Department of Justice for enforcement activity involving restraint of trade. Attorneys in the Office of General Counsel may be queried formally or informally if there is doubt about the request.
8 - Release of Identifiable Data for the Health and Safety of the Individual
CMS may assist in the location of individuals where their health and safety is involved. For example, identifiable data were released to the Connecticut State Department of Health to locate individuals who had been exposed to benzene, a chemical that may cause bladder cancer. The employer was cooperating with the state in an effort to notify former employees of the possible danger and to offer an examination program. CMS has addresses for most individuals age 65 and over. Since few individuals under age 65 are Medicare beneficiaries, CMS coordinates with the Social Security Administration (SSA) to locate such individuals. SSA will forward a letter to the individuals at the individual’s last employer’s address.
9 - Release of Identifiable Data to the Congress
Data may be released to either House of Congress or for purposes falling under its jurisdiction to any committee, subcommittee, or joint committee. Data are furnished to the Congressional Budget Office and the Library of Congress for Congressional projects. The Prospective Payment Assessment Commission and the Physician Payment Review Commission have separate legislation authorizing release of data to them. Data are furnished as needed.
10 - Release of Identifiable Data to General Accounting Office
CMS cooperates fully with General Accounting Office.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .