19.04.2014 Views

(RFP) for Recovery Audit Contractor (RAC) - Texas Health and ...

(RFP) for Recovery Audit Contractor (RAC) - Texas Health and ...

(RFP) for Recovery Audit Contractor (RAC) - Texas Health and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

e. Establish a Governance process with HHSC <strong>and</strong> hold Governance meetings on a<br />

schedule as determined by HHSC; the governance meetings will serve as a means to<br />

establish processes <strong>for</strong> all audits <strong>and</strong> also serve as a means to monitor the project <strong>and</strong><br />

escalate issues.<br />

f. Coordinate with a State designee(s) <strong>for</strong> all audit activities <strong>and</strong> communication between<br />

the <strong>Texas</strong> Medicaid claims administrator, managed care organizations, <strong>and</strong> other <strong>Health</strong><br />

<strong>and</strong> Human Services Enterprise agencies including the Office of Inspector General<br />

(OIG), the Department of Aging <strong>and</strong> Disability Services (DADS), Department of<br />

Assistance <strong>and</strong> Rehabilitative Services (DARS), the Department of Family <strong>and</strong><br />

Protective Services (DFPS), <strong>and</strong> the Department of State <strong>Health</strong> Services (DSHS), as<br />

appropriate.<br />

g. Furnish all material, labor, computers, software, equipment <strong>and</strong> supplies necessary to<br />

per<strong>for</strong>m their services.<br />

h. Be responsible <strong>for</strong> all travel expenses.<br />

i. Not remove any original records from the State offices.<br />

j. Provide postage, long distance phone service, <strong>and</strong> email services <strong>for</strong> their staff; HHSC<br />

will not pay <strong>for</strong> incidental expenses related to the recovery audit(s) <strong>and</strong>/or fraud-related<br />

audit services.<br />

k. Follow all federal <strong>and</strong> state related laws, statutes, rules <strong>and</strong> contract terms in its<br />

recovery audit(s) <strong>and</strong> fraud-related audit activities.<br />

l. Retain all audit documentation <strong>for</strong> three years following the final payment under this<br />

contract or the date upon which all questions involving the improper payments <strong>and</strong><br />

fraudulent activities validity are resolved, whichever happens last.<br />

2.3.2. Identification of Specific Providers <strong>for</strong> <strong>Audit</strong> (Provider Based<br />

Approach)<br />

a. <strong>Audit</strong>s of Medicaid providers shall be based on such activities as improper payment risk<br />

assessments, regression, digital analysis, data mining, <strong>and</strong> other risk assessment or<br />

error detection techniques. Provider audits may also be indicated by HHSC based on<br />

other sources of in<strong>for</strong>mation, including complaints, investigations, other audits, etc.<br />

b. Provide timeline <strong>for</strong> each proposed provider audit, <strong>for</strong>mat to be determined by HHSC, <strong>for</strong><br />

approval by HHSC prior to the start of audit activities. The timeline should include all<br />

audit activities associated with the audit, including proposed major milestones such as<br />

engagement letter, entrance conference, exit conference, preliminary draft report, final<br />

draft report, final report.<br />

2.3.3. Identification of Specific Claims <strong>for</strong> <strong>Audit</strong> (Claims Based Approach)<br />

a. Provide a timeline <strong>for</strong> each audit type as determined by HHSC <strong>for</strong> approval by HHSC<br />

prior to the start of audit activities <strong>for</strong> each audit type. The timeline should include all<br />

audit activities associated with the audit type beginning with submittal of audit concepts<br />

17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!