SOURCES SOUGHT CVO.docx

SOURCES SOUGHT: Credentialing Verification Organization

This Sources Sought (SS) is issued solely for planning purposes. It does not constitute a solicitation or a promise to issue a solicitation in the future. Responses to this SS are strictly for market research purposes and will be used by the U.S. Government to make appropriate acquisition decisions. This SS does not commit the U.S. Government to contract for any supply or service whatsoever. Further, the U.S. Government is not at this time seeking a solicitation response and will not accept unsolicited responses in the form of a quote, proposal, or bid.

Interested parties are advised that the U.S. Government will not pay for any costs incurred in response to this SS. All costs associated with responding to this SS will be solely at the interested party’s expense. Submittals will not be returned. Not responding to this SS does not preclude participation in any future solicitation, if any is issued. All questions and responses to this SS shall be e-mailed to the individuals identified in the announcement. No phone calls will be accepted.

Be brief and confine your responses to the questions asked.

Business Details:

Name of the business, point of contact, phone number, email address, UEI number, and business type/size.

Provide a brief statement of core business competencies and why your organization suitable to meet the requirements outlined in the DRAFT Performance Work Statement.

What NAICS or PSC code would you recommend if different than the announcement and why?

Describe your experience in successfully performing requirements of a similar size, scope, and complexity relative to the DRAFT Performance Work Statement.

Do you have a General Services Administration Federal Supply Schedule that falls within the scope of the DRAFT Performance Work Statement or any other ordering vehicle the VA could use?

Provide any relevant information to help determine if the requirement is commercially available, including any existing pricing information, basis for the pricing information (e.g., market pricing, catalog pricing, historical pricing, etc.), delivery schedules, customary terms and conditions, warranties, etc.

System & Technical Capability

1. Can your database provide real time dashboards and queue views showing credentialing status by provider/facility?

2. Can your system support bulk upload (e.g., ingesting multiple applications from Excel)? Can your system bulk export providers by risk category with sortable fields intact?

3. What audit ready reporting features exist (e.g., MEC-approved dates, thread capture, NPDB CQ documentation, committee minutes)?

4. How do you ensure national coverage with no IP based access failures across states/territories?

5. Can your system allow VA users to request provider deactivation or application edits directly inside the platform?

6. Is it technically feasible within your system’s user provisioning capabilities to restrict or customize user access so that only designated users may request or initiate provider data changes or updates?

7. Does your system have the capability to ingest and process bulk provider data? If so, what formats are acceptable?

8. How do you document CMO or delegated reviews of off cycle NPDB or monitoring events?

9. Is your solution capable of providing a real‑time status dashboard with a queue view that displays each provider/facility’s current credentialing stage and a consolidated timeline of all credentialing actions and communication attempts—without requiring staff to open and review each NPI individually?

10. Please describe the key data fields your system collects and maintains for credentialing applications.

11. How long, in calendar days, do you estimate it will take for you to be fully implemented and operational once the contract is awarded?

Credentialing & Verification Process

1. What are your standard PSV timeframes, and what is your average turnaround?

2. How do you handle provider non‑response beyond the required five attempts?

3. How is your communication matrix structured, and what enhancements do you recommend for VA?

4. Can you monitor CMS star ratings for community nursing homes and incorporate them into risk scoring?

5. How do you ensure the 10‑year lookback is accurate, complete, and uniformly applied?

6. What is your approach to handling providers outside NCQA/URAC standards (e.g., home health, unskilled labor)?

Review Board & Appeals

1. What are your qualifications and standards for peer‑level review board members?

2. How do you ensure consistency of enhanced review recommendations across specialties?

3. Can you support VA participation in your credentialing committees (as observers or voting members)?

4. What is your workflow for appeal processing and timelines?

Monitoring (NPDB‑CQ and Beyond)

1. How do you prevent NPDB‑CQ renewal lapses, and how is tracking automated?

2. Can you integrate other monitoring (LEIE, SAM, Medicare opt-out, state actions) into a single workflow?

3. How do you notify VA and document monitoring hits in a standardized, exportable format?

Pricing & CLIN Structure

1. What contract type do you believe is best suited for this requirement?

2. What pricing model do you recommend for separating:

a. Initial credentialing

b. Recredentialing

c. NPDB-CQ enrollment

d. NPDB-CQ annual renewals

e. Ongoing monitoring?

3. What is your Rough Order of Magnitude (ROM) estimate for the requirement?

4. What is included in your cost for monitoring beyond NPDB‑CQ?

Do you have any input regarding the DRAFT Performance Work Statement? Please provide any comments using the Microsoft Word Comment tool with your response.

Identify whether your business is interested in competing for this requirement as a prime contractor or not. Identify existing subcontracting, joint ventures, or teaming arrangement that would be included.