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.

6. Detailed findings organized by type of improper payment or fraudulent activity,<br />

including amount of improper payment or fraudulent activity, complete description<br />

of the cause of the improper payment or fraudulent activity, <strong>and</strong> a<br />

recommendation to remedy the cause.<br />

c. <strong>RAC</strong> must recommend a web-based application that allows providers to customize<br />

addresses, send inquiries related to the audit, etc., <strong>and</strong> allows HHSC <strong>and</strong> providers to<br />

check the status of medical records requests <strong>and</strong> case review (i.e.: outst<strong>and</strong>ing,<br />

received, review underway, review complete, case closed); HHSC is requesting a<br />

respondent to recommend a web-based application to satisfy the requirement. HHSC<br />

will review the recommendation <strong>and</strong> then, if approved by HHSC, the successful<br />

respondent will be required to implement, maintain <strong>and</strong> operate the web-based<br />

application. If HHSC does not approve of the recommended web-based application<br />

proposed by a respondent, HHSC may request a respondent to provide additional<br />

alternatives to the original web-based application until an acceptable application is<br />

approved. The successful respondent will be required to implement, maintain <strong>and</strong><br />

operate an HHSC approved web-based application.<br />

d. Recommend system changes to prevent future improper payments.<br />

e. Recommend solutions/concepts to improve the <strong>Texas</strong> Medicaid program based on<br />

findings from audits related to fraud investigations.<br />

2.3.6. Data Sharing <strong>and</strong> Security<br />

a. After consultation with HHSC, identify <strong>and</strong> provide a complete list/description of required<br />

data fields necessary from HHSC <strong>for</strong> review of claims associated with the audit.<br />

b. Propose a solution that will have minimal impact on the current operations of the MMIS;<br />

include a high-level diagram of expected data flow.<br />

c. Provide secure transmission of data exchange, <strong>and</strong> provide a description to the HHSC of<br />

the process that will be used <strong>for</strong> secure data exchange.<br />

d. Follow all federal <strong>and</strong> state rules <strong>and</strong> regulations as they apply to the disclosure of<br />

protected health in<strong>for</strong>mation (PHI) obtained from HHSC that is necessary <strong>for</strong> the<br />

per<strong>for</strong>mance of the recovery audit <strong>and</strong> fraud-related audit services. This applies to a<br />

person acting under this contract, <strong>and</strong> each employee or agent of the person.<br />

2.3.7. Recoupment <strong>and</strong> Appeals Process<br />

a. Identify claims with improper payments <strong>and</strong> provide the details to HHSC <strong>for</strong> recoupment<br />

of overpayments or repayment of underpayments.<br />

b. Invoice <strong>and</strong> receive payment <strong>for</strong> only those funds recovered by HHSC <strong>for</strong> overpayments,<br />

or <strong>for</strong> underpayments actually paid to providers by the state, during the life of the<br />

contract; any funds recovered by HHSC <strong>for</strong> overpayments or underpayments actually<br />

paid to providers by the state after each agreed upon audit completion date will be<br />

excluded from the contingency <strong>and</strong>/or fixed fee calculation <strong>and</strong> payment. Each audit<br />

20

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

Saved successfully!

Ooh no, something went wrong!