(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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
2.6 Location of Services<br />
The <strong>RAC</strong> will be responsible <strong>for</strong> providing its own equipment <strong>and</strong> office resources <strong>for</strong> business<br />
related to this project <strong>and</strong> contract. HHSC will provide meeting space <strong>for</strong> all joint meetings <strong>and</strong><br />
work-sessions, if needed. HHSC may provide office space <strong>and</strong> equipment <strong>for</strong> the selected<br />
vendor <strong>for</strong> key day-to-day personnel.<br />
2.7 Contract Turnover Requirements<br />
This section presents the Turnover Requirements to which the selected vendor must agree.<br />
Turnover is defined as those activities that are required <strong>for</strong> the selected vendor to per<strong>for</strong>m in<br />
order to transition contract operations to a subsequent <strong>RAC</strong> <strong>and</strong>/or HHSC, or its designee.<br />
2.8 Turnover Services<br />
Six months prior to the end of the base contract period or any extension thereof, the selected<br />
vendor must develop, submit, <strong>and</strong> implement an HHSC approved Turnover Plan covering the<br />
possible turnover of contract requirements to HHSC, its designee, or a successor vendor. The<br />
Turnover Plan must be a comprehensive document detailing the proposed schedule, activities,<br />
<strong>and</strong> resource requirements associated with the turnover tasks outlined in this section below.<br />
HHSC reserves the right to have the <strong>RAC</strong> submit an additional updated Turnover Plan one<br />
month prior to the end of the base contract or any extension thereof.<br />
The plan will describe the <strong>RAC</strong>’s approach <strong>and</strong> schedule <strong>for</strong> transfer of activities <strong>and</strong><br />
operational support in<strong>for</strong>mation. The in<strong>for</strong>mation must be supplied on media specified by <strong>and</strong><br />
according to the schedule approved by HHSC.<br />
The time frames <strong>and</strong> turnover task requirements are provided herein. The timing <strong>and</strong> data<br />
requirements are illustrative only <strong>and</strong> do not limit or restrict HHSC’s ability to require additional<br />
in<strong>for</strong>mation from the selected vendor or modify the turnover schedule as necessary. Proprietary<br />
software programs will not be required to be delivered to HHSC pursuant to these Turnover<br />
Requirements.<br />
As part of the Turnover Plan, the <strong>RAC</strong> must provide HHSC with copies of all relevant nonproprietary<br />
data, all documentation, including but not limited to the following:<br />
a. Copies of working papers, including procedures, programs, <strong>and</strong> schedules;<br />
b. Status of current projects<br />
c. Copies of correspondence (internal <strong>and</strong> external);<br />
d. Listings of third-party software used by the contractor(s), including availability of the<br />
software <strong>for</strong> transfer or purchase by HHSC or successor vendor(s);<br />
e. Description of functional business process flows;<br />
f. Operational <strong>and</strong> system in<strong>for</strong>mation concerning subcontractors;<br />
g. Documentation of ongoing outst<strong>and</strong>ing issues;<br />
h. Other documentation necessary to support contract operations; <strong>and</strong><br />
i. Other pertinent in<strong>for</strong>mation necessary to take over <strong>and</strong> operate the project or to assume<br />
the operational activities successfully.<br />
The <strong>RAC</strong> will provide HHSC or its agent all updated non-proprietary computer programs, data<br />
<strong>and</strong> reference tables, scripts, <strong>and</strong> other documentation/records within 15 business days of the<br />
request.<br />
25