Once the Contract has been awarded and the period of performance has begun, the first step is to determine what kind of work the contractor will be performing to meet the deliverables. The type of work that the contractor is doing will determine if there is a need for QualityNet IT Services. To start this process, the CMS COR and New Contractor must complete an initial form to request the start of the contract engagement. Based on the information provided, the ISG Contract Engagement team will determine if there is a need for QualityNet IT Services. If it is found that the New Contractor will need these services, an interview will be scheduled. Using the information provided, the ISG Contract Engagement team will prepare for the interview, ensuring the attendance of all necessary parties. The gathered information will also be used for entitlements and permissions for key roles in HARP.
| Button Hyperlink |
|---|
| title | Click to download the Contract Engagement Intake Form |
|---|
| type | primary |
|---|
| url | https://qnetconfluence.cms.gov/download/attachments/134989964/Contract%20Engagement%20Intake%20Form.xlsx?api=v2 |
|---|
| target | true |
|---|
|
The following information will need to be provided: - Contract Number (Required)
- Task Order Number (if applicable)
- DUA Number (required for SAS VIYA)
- Period of Performance start and end dates (Required)
- Contract Short Name (Required)
- Contract Full Legal Name (Required)
- Prime Contractor Company Name (Required)
- Contract Category (ADO, NQIIC, BFCC, ESRD, Support, Analytics) (Required)
- Contracting Officer Representative (COR) (Required)
- COR HARP EUA ID (Required)
- Contractual Duties (Mandatory)
- Contractor POC Name and Corporate Email (Required)
- Security Point of Contact (SPOC) - First Name, Last Name, Corporate Email, and Phone Number (Required)
- Security Point of Contact HARP EUA ID (Required)
- Security Official (SO) Information - First Name, Last Name, Corporate Email, and Phone Number (Required)
- Security Official HARP EUA ID (Required)
| 
ISG Playbook
APIs