- Solicitation number
- 36C10B27Q0117
About this file
This is a Draft Performance Work Statement (PWS) for a Utilization Management Software licensing and support contract (VA-27-00009483) issued by the Department of Veterans Affairs Veterans Health Administration. The VA seeks an enterprise-wide software licensing agreement for a Utilization Management tool supporting over 1,000 users across all five Veterans Integrated Service Networks, 18 Health Service Areas, and 153 medical facilities. The contractor must provide unlimited use licensing, software updates, patches, upgrades, and clinical and technical helpdesk support for evidence-based criteria and associated tools that integrate seamlessly with the National Utilization Management Integration (NUMI) application and Federal EHR systems compatible with both VHA VistA and Cerner platforms.
The required deliverables include: Level of Care Criteria for acute adult, long-term acute care, inpatient rehabilitation, skilled nursing, home care, hospice, palliative care, outpatient rehabilitation, and chiropractic services; Care Planning Criteria for DME, imaging, invasive and surgical procedures, specialist referrals, and retrospective quality review; Behavioral Health Level of Care Criteria for substance use disorders and residential/community-based care; static clinical decision support tools; an automated suite for creating evidence-based clinical assessment questions with subaccount access and performance reporting; mobile web applications with current clinical criteria; and anonymous cloud applications providing real-time criteria review with outcome indicators. The contract period consists of one 12-month base period with up to four optional 12-month periods, not to exceed 60 months total. System availability must meet a 98.5% threshold with a 99.5% objective, and Mean Time to Repair or Restore (MTTR) performance standards apply. The contractor must also provide initial and ongoing instructor-led and web-based refresher training, training registration, and trainer certification maintenance throughout VHA. Performance shall be completed at contractor facilities, and all travel costs for training delivery must be included in firm-fixed-price line items without direct government reimbursement.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B27Q0117.docx | DOCX document |
On GovTribe
Work with this file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Utilization Management
VA-27-00009483
DRAFT PERFORMANCE WORK STATEMENT (PWS)
DEPARTMENT OF VETERANS AFFAIRS
Veterans Health Administration (VHA) Office of Patient Safety Utilization Management Program Office
Utilization Management Review Criteria
Date: November 10, 2026
VA-27-00009483
PWS Version Number: 1.1
Contents
| 1.0 | BACKGROUND | 4 |
| 2.0 | APPLICABLE DOCUMENTS | 4 |
| 3.0 | SCOPE OF WORK | 7 |
| 4.0 | PERFORMANCE DETAILS | 8 |
| 4.1 | PERFORMANCE PERIOD | 8 |
| 4.2 | PLACE OF PERFORMANCE | 8 |
| 4.3 | TRAVEL | 8 |
| 5.0 | SPECIFIC TASKS AND DELIVERABLES | 8 |
| 5.1 | PROJECT MANAGEMENT | 8 |
| 5.1.1 | CONTRACTOR PROJECT MANAGEMENT PLAN | 8 |
| 5.1.2 | REPORTING REQUIREMENTS | 9 |
| 5.2 | VHA ENTERPRISE-WIDE LICENSING AGREEMENT | 9 |
| 5.3 | SYSTEM AVAILABILITY AND PERFORMANCE | 10 |
| 5.4 | CUSTOMER AND SERVICE DESK SUPPORT | 11 |
| 5.4.1 | CUSTOMER SUPPORT SURVEY | 11 |
| 5.5 | NUMI AND EHR COMPATIBILITY | 12 |
| 5.6 | ANNUAL EVIDENCE-BASED CRITERIA UPDATES | 12 |
| 5.7 | TRAINING | 12 |
| 5.7.1 | INITIAL TRAINING AND CERTIFICATION | 13 |
| 5.7.2 | INSTRUCTOR-LED, WEB-BASED REFRESHER TRAINING | 13 |
| 5.7.3 | TRAINING REGISTRATION | 13 |
| 5.7.4 | TRAINING SURVEY | 13 |
| 5.8 | OPTIONAL TASK- MIGRATION TO THE PUBLIC CLOUD | 14 |
| 6.0 | GENERAL REQUIREMENTS | 15 |
| 6.1 | ENTERPRISE AND IT FRAMEWORK | 15 |
| 6.1.1 | VA TECHNICAL REFERENCE MODEL | 15 |
| 6.1.2 | FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM) | 15 |
| 6.1.3 | INTERNET PROTOCOL VERSION 6 (IPV6) | 17 |
| 6.1.4 | TRUSTED INTERNET CONNECTION (TIC) | 17 |
| 6.1.5 | STANDARD COMPUTER CONFIGURATION | 18 |
| 6.1.6 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM) | 18 |
| 6.1.7 | PROCESS ASSET LIBRARY (PAL) | 19 |
| 6.1.8 | AUTHORITATIVE DATA SOURCES | 19 |
| 6.1.9 | SOCIAL SECURITY NUMBER (SSN) REDUCTION | 20 |
| 6.2 | SECURITY AND PRIVACY REQUIREMENTS | 20 |
| 6.2.1 | POSITION/TASK RISK DESIGNATION LEVEL(S) | 20 |
| 6.2.2 | CONTRACTOR PERSONNEL SECURITY REQUIREMENTS | 21 |
| 6.3 | METHOD AND DISTRIBUTION OF DELIVERABLES | 23 |
| 6.4 | PERFORMANCE METRICS | 23 |
| 6.5 | GOVERNMENT FURNISHED PROPERTY | 26 |
| ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED | 27 | |
| ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE | 32 |
BACKGROUND
Veterans Health Administration (VHA) is committed to a healthcare system that treats its patient population effectively, efficiently, and appropriately. The VHA’s Utilization Management (UM) Program focuses on using resources efficiently and ensuring that every Veteran receives consistent reliable, high-quality care in the optimal setting and at appropriate care delivery intervals. The objective of the UM program is to provide the correct care, for the right patient, at the best time and for the proper reasons using evidence-based practice and continuous measurement and improvement.
VHA mandates the use of the National Utilization Management Integration (NUMI) application via VHA Directive 1117, Utilization Management Program. The government-owned, NUMI application and Federal Electronic Health Record (EHR) system standardizes clinical appropriateness review of patient care at over 150 VHA facilities by integrating evidence-based clinical criteria into the application to assist clinicians and managers in care management decisions.
VHA users are from all five Veterans Integrated Service Networks (VISNs), 18 Health Service Areas (HSAs), 153 medical facilities; and program offices that include the Utilization Management program office, the Chief Business Office, Purchased Care and the Consolidated Patient Account Centers (CPAC).
APPLICABLE DOCUMENTS
In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:
1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”
2. “Federal Information Security Modernization Act of 2014”
3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules”
4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004
5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006
6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013
7. 10 U.S.C. § 2224, "Defense Information Assurance Program"
8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”
9. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters
10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”
11. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm
12. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm
13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019
14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017
15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016
16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”
17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008
18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017
19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004
20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021
21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021
22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019
23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle,” March 22, 2010
24. VA Handbook 6500.6, “Contract Security,” March 12, 2010
25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6, 2011
26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018
27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017
28. OIT Process Asset Library (PAL), https://www.va.gov/process/ . Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp
29. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)
30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014
31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015
32. VA Handbook 6510, “VA Identity and Access Management,” January 15, 2016
33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017
34. VA Directive 6300, “Records and Information Management,” September 21, 2018
35. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010
36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018
37. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)
38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015
39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014
40. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005
41. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019
42. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008
43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)
44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018
45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020
46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014
47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices (Draft),” October 2012
48. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014
49. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
50. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
51. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896
52. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents
53. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019
54. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008
55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007
56. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005
57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018
58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001
59. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013
60. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013
61. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
62. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103
63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371
64. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946
66. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020
67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020
68. Social Security Number (SSN) Fraud Prevention Act of 2017
69. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018
70. VA Enterprise Cloud Technical Reference Guide, Version 1.3 July 2018
71. VA Enterprise Cloud Technical Reference Guide, Version 1.3 July 2018
SCOPE OF WORK
The Contractor shall provide enterprise-wide software licensing for a Utilization Management Software tool that includes unlimited use, updates, clinical and technical support for evidence-based criteria and the associated tools identified in this PWS that interface into the NUMI application and the Federal EHR System. In addition, the Contractor shall provide training to certify and maintain certification for trainers throughout the VHA and helpdesk support.
PERFORMANCE DETAILS
PERFORMANCE PERIOD
The period of performance (PoP) shall be a 12-month Base period, with up to four (4) 12-month option periods and optional tasks to be exercised by the Government at its sole discretion.
The total PoP shall not exceed 60 months.
PLACE OF PERFORMANCE
Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.
TRAVEL
If contractor travel is necessary to perform the training tasks associated with the effort, include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.
SPECIFIC TASKS AND DELIVERABLES
PROJECT MANAGEMENT
CONTRACTOR PROJECT MANAGEMENT PLAN
The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP shall take the form of both a narrative and graphic format that displays the schedule, milestones, and risks, including the risk management approach. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.
Deliverable:
Contractor Project Management Plan
REPORTING REQUIREMENTS
The Contractor shall provide the COR with Quarterly Progress Reports in electronic form in Microsoft Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Month.
The quarterly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor availability and performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.
Deliverable:
A. Quarterly Progress Report
VHA ENTERPRISE-WIDE LICENSING
The Contractor shall provide an enterprise-wide (currently over 1000 users), unlimited use, Licensing Agreement for all VHA users to access and use evidence-based clinical appropriateness criteria and associated tools.
The Contractor shall include unlimited Government use of the criteria in electronic format. The Contractor shall provide all product support such as application/software updates, patches and upgrades, report generation, and clinical and technical help desk response and resolution. Updates to the electronic version of the criteria or associated applications including clinical revisions, technical enhancements, system patches, and version upgrades shall be included in the software license.
The Contractor shall provide access, view, use, and download of the following criteria and associated applications and tools as part of the licensing agreement:
a) Level of Care Criteria: evidence-based review criteria to determine and evaluate appropriateness, medical necessity and the efficiency of health care services in Acute adult, Long term acute care, inpatient rehab, subacute and skilled nursing care, initiation and continuation of home care to include hospice and palliative care, outpatient rehab and chiropractic services. Review criteria must include the ability to review observation, admission and continue stay based on evidence-based medicine and determine appropriate level of care for admission, continued stay, and recommendations for community follow up care. Must be compatible with both VHA VistA and Cerner EHR.
b) Care Planning Criteria: evidence-based review criteria to help identify if requested services are medically necessary and based on evidence- based practice. Criteria should evaluate care related to requests for DME, Imaging, Invasive and surgical procedures which are costly and often performed, referrals to specialists, criteria to review retrospectively care provided to evaluate quality and identify opportunities for improvement. Must be compatible with both VHA VistA and Cerner EHR.
c) Level of Care Criteria for Behavioral Health: evidence-based review criteria to determine and evaluate appropriateness, medical necessity and the efficiency of health care services. Behavioral health criteria review to include patient presentation of symptoms, behavior, social risks and support and functions. Behavioral health of adult and geriatric patients to include substance use disorders, residential and community-based care. Review criteria must include the ability to review observation, admission and continue stay based on evidence-based medicine and determine appropriate level of care for admission, continued stay, and recommendations for community follow up care. Must be compatible with both VHA VistA and Cerner EHR.
d) Static Reference for clinical decision making that is automated and accessible through browser providing evidence-based medicine clinical decision support for level of care determination.
e) Automated suite used for creating evidence based clinical application questions to assess end user’s learning. This suite provides stakeholder the ability to create exams from vendor provided questions based on the clinical criteria application and the review process. The suite allows subaccount spaces for multiple account access administrators to view and monitor reviewer competency and build reports for performance assessment and opportunities.
f) Mobile web application for cell phones is available organization wide for all users with the most up to date clinical evidence-based evaluation criteria. Tool is the exact content of the computer software version of review criteria available.
g) Anonymous Cloud application providing real time criteria for review of all services noted above with an outcome indicator.
SYSTEM AVAILABILITY AND PERFORMANCE
The contractor shall meet the following availability and performance metrics:
| Metric |
| Metric Description |
| Expected Value |
| Availability (Asubo) |
| Percent of time and duration the VA platform and tools were up and operational based on available data from OEHRM and VA OIT |
| Threshold: 98.5% |
Objective: 99.5%
| Maintainability – Mean Time To Repair or Restore (MTTR) |
| Mean Time to Repair or Restore (MTTR) for software, service components of the tool for a given reporting period |
| Threshold: <= 8 hours per incident |
Objective: <= 4 hours per incident
| Reliability – Mean Time Between Failure (MTBF) |
| Mean Time Between Failure (MTBF) for hardware/platform, software, service components of the VA platform and the tool for a given reporting period |
| Threshold: 10 days |
Objective: 30 days
| Cybersecurity Incident Response |
| Time elapsed to address cybersecurity incident based on severity of impact and criticality of system components |
| Threshold: 48 to 120 hours |
Objective: 24, 48, 72 hours (respectively to severity of impact level)
| Data Breach Reporting |
| Time elapsed to report a data breach event |
| Threshold and Objective: 1 hour |
DHA Privacy Office: 24 hours DoD Privacy & Civil Liberty Division: 48 hours
CUSTOMER AND SERVICE DESK SUPPORT
The contractor shall provide clinical and technical help desk response and resolution. All VHA user support calls are initially sent to the VA Enterprise Service Desk (ESD), which is responsible for Tier 1 support. The VA ESD currently uses the Service Now (Snow) tool to track all support calls. The VA ESD will address any issues such as computer hardware, user access, network access, and printing. Any issues that are specifically related to the licensed products described in paragraph 5.2 shall be forwarded to the contractor’s service desk. The Contractor shall provide customer support for the VHA medical centers and program offices during operating hours of 7:00 am to 9:00 pm EST/EDT. The Contractor shall provide both clinical (e.g., the explanation and interpretation of criteria, use of applications, and guidance with complex cases) and technical (e.g., access, account and password help, download, and use of the applications) support. The Contractor shall maintain a 96% customer satisfaction rate based on timely response and resolution. The Contractor shall respond to all requests for support within 24 hours of the request. The Contractor shall resolve issues within 15 calendar days of request for support. The Contractor shall provide both an email contact and a phone number for support.
CUSTOMER SUPPORT SURVEY
The Contractor shall survey VHA customers and provide the results (and/or access to the results) to the COR on a quarterly basis. The Contractor shall coordinate the surveys for COR approval prior to conducting the survey; and shall deliver the survey results in accordance with the CPMP (e.g., no later than 10 calendar days after the end of each quarter).
Deliverable:
A: Customer Survey Results
NUMI AND EHR COMPATIBILITY
The Contractor shall ensure all electronic criteria application changes are compatible with the existing/current version of NUMI and EHR are coordinated at least 60 business days in advance of implementation with the COR through submission of a change log.
Deliverable:
A. Change Log
ANNUAL EVIDENCE-BASED CRITERIA UPDATES
The Contractor shall assess the criteria and provide an annual complete updated criteria release that reflects current healthcare best practices. The Contractor shall ensure that all criteria are compliant with the applicable regulations and laws. The Contractor shall notify the COR at least 60 calendar days prior to implementing changes though submission of a change log. The Contractor shall ensure that all changes to the Criteria and associated applications are compatible with the current version of NUMI and EHR.
Deliverable:
A. Change Log
TRAINING
The Contractor shall provide educational resources and training to support the VHA in maintaining certifications for a core group of certified clinical trainers, who are experts in the interpretation, application and content delivery of UM criteria. This VHA core group will then train VHA UM end-users on the use of the criteria products.
The Contractor shall ensure that the training meets certification and accreditation requirements. The Contractor shall provide the training materials to all enrolled learners no later than 10 business days prior to the scheduled training session. The Contractor shall offer instructor-led, web-based training, or face-to-face training.
Deliverable:
A: Training Materials
INITIAL TRAINING AND CERTIFICATION
The Contractor shall provide Virtual instructor led initial training sessions for up to 10 VHA staff members each who are identified as candidates for instructor certification in all licensed criteria products. The Contractor shall develop a comprehensive curriculum and agenda for the training, provide faculty, educational material, and continuing education credits approved by the American Nursing Association. The Contractor shall ensure that the training is relative to the development, interpretation, application, and content delivery of the licensed criteria.
OPTIONAL TASK ONE: ADDITIONAL INITIAL TRAINING AND CERTIFICATION
The Contractor shall provide up to two additional sessions per year of Initial Training and Certification as outlined in section 5.7.1.
INSTRUCTOR-LED, WEB-BASED REFRESHER TRAINING
Contractor shall provide instructor-led, web-based training annually for VHA staff trainers for recertification in all licensed criteria products. The Contractor shall develop a comprehensive curriculum and agenda for the training, provide faculty, educational materials, evaluation of participants and continuing education credits approved by the American Nursing Association. The Contractor shall ensure that the training is relative to the interpretation, application, and content delivery of the annual update of licensed criteria products. The Contractor will ensure competency of all participants at the conclusion of training.
OPTIONAL TASK TWO: ADDITIONAL INSTRUCTOR-LED, WEB-BASED REFRESHER TRAINING
The Contractor shall provide up to 6 additional sessions per year of Instructor-Led, Web-Based Refresher Training as outlined in section 5.7.3.
TRAINING REGISTRATION
The Contractor shall establish and coordinate the registration of VHA staff for all training sessions. The Contractor shall accept registrations directly from VHA staff members. The Contractor shall provide information regarding the training to each enrollee to include availability and delivery of training materials, contact information, dates and times of sessions, and other administrative information. The Contractor shall complete the registration for each training session within 30 calendar days prior to conducting the training; and shall provide the COR a list of all VA employees registered to attend the training session no later than 20 calendar days prior to the training start date. The Contractor shall provide the COR a list of the actual attendees for each training session within 10 calendar days of the conclusion of each session.
Deliverable:
A: List of Attendees
TRAINING SURVEY
The Contractor shall prepare a student survey/questionnaire for COR approval for all training provided no later than 30 calendar days prior to conducting training sessions. The Contractor shall provide the completed surveys and results directly to the COR within 10 calendar days of the conclusion of each training session. The Contractor shall maintain a 96% learner satisfaction rate.
Deliverable:
A: Training Surveys
GENERAL REQUIREMENTS
ENTERPRISE AND IT FRAMEWORK
VA TECHNICAL REFERENCE MODEL
The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM). Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.
ZERO TRUST – VA CRITICAL SECURITY CONTROLS
VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.
FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)
The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23-01, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.
The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-4, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.
The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.
The Contractor shall ensure all Contractor delivered applications and systems support:
1. Automated provisioning and are able to use enterprise provisioning service.
2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.
3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).
4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.
5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.
6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.
7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.
8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-4 guidelines.
9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.
10. Role Based Access Control.
11. Auditing and reporting capabilities.
12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.
The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.
INTERNET PROTOCOL VERSION 6 (IPv6)
The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.
TRUSTED INTERNET CONNECTION (TIC)
The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents).
STANDARD COMPUTER CONFIGURATION
The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, Windows 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 11 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.
VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM)
The Contractor shall support VA efforts IAW the Veteran-Focused Integration Process (VIP) Guide and Product Line Management (PLM) Playbook. The major focus of VIP is on Enterprise Oversight, Governance, reporting, and establishing practices that focus on outcomes and continuously delivering sustainable IT capabilities to benefit the Veteran. PLM is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Transformation Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Transformation Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.
The VIP Guide provides guidance for transitioning from project-centric to product-centric delivery. The VIP guide applies to all OIT Office of Management and Budget (OMB) reportable products that are required to collect and report costs, schedules, risks, and other valuable information in VA PARS (whether products are procured or developed by VA) and any VA Information Technology project effort in Software Product Management (SPM) and Infrastructure Operations (IO), or their successors, that touch the VA network regardless of IT organizational alignment (whether it spends government funding from VA's Congressional IT Appropriation or any other appropriation).
The PLM Transformation Playbook details how OIT leadership expects Product Lines (PLs) to implement PLM, DevOps, and Lean-Agile principles, methods, practices, and techniques through levels of maturity. The PLM Transformation Playbook applies to all Information Technology (IT) products aligned to PLs in the Software Product Management, Infrastructure Operations and Product Engineering organizations within the OIT organization.
Others outside the referenced groups or organizations may use the VIP Guide and PLM Transformation Playbook for situational awareness as needed.
PROCESS ASSET LIBRARY (PAL)
The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL includes a spectrum of OIT functions and activities, such as project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. OIT utilizes PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at process_CONB_ext.docx (live.com). The main PAL can be accessed at www.va.gov/process.
AUTHORITATIVE DATA SOURCES
The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:
1. Interfacing with VA’s Master Person Index (MPI) (formerly the Master Veteran Index (MVI)) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.
2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.
3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.
4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data.
5. Interfacing with VA Profile to access personal contact information, if the solution relies on VA Veteran personal contact information data. VA Profile is the authoritative source for VA Veteran Personal Contact Data.
6. Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for qualifying active duty military service in VA.
7. Interfacing with VA Systems Inventory (VASI) to access VA systems information, if the solution relies on VA system information. VASI is the authoritative source for VA Information Technology systems.
8. Interfacing with Enterprise Mission Assurance Support Service (eMASS) to access the historical Authority to Operate (ATO) status of all VA Information Systems prior to migrating to ServiceNow Continuous Authorization and Monitoring (SNowCAM) until it is determined the migration is completed and eMASS is sunset. eMASS contains the historical Authority to Operate (ATO) status of all VA Information Systems prior to September 30, 2025, with all status provided through SNowCAM once migration is completed.
ENTERPRISE SOCIAL SECURITY NUMBER (ESSN) REDUCTION
The Contractor solution shall comply with the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 (P.L. 115-59 (Sept. 15, 2017)) which prohibits the inclusion of Social Security Numbers (SSNs) on any document sent by mail, except for limited exemptions codified in 38 C.F.R. § 1.575 (2022). The Contractor solution shall only include a SSN on a mailed document with an approved Exemption from VA Enterprise Social Security Number Reduction (ESSNR) Leadership. The Contractor solution shall also comply with the Continuing Appropriations, Agriculture, Legislative Branch, Military Construction and Veterans Affairs, and Extensions Act (CAA), 2026 (P.L. 119-37, Div. D, Title II, Sect. 237 (Nov. 12, 2025)) that prohibits VA from using SSN for VA system authentication and restricts VA’s use of a SSN to identify an individual in a VA information system. The Contractor solution shall only use a SSN to identify an individual in a VA information system if its use complies with CAA’s Acceptable Use and the information system has received approval from ESSNR Leadership.
SOFTWARE AND LICENSING REQUIREMENTS
The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.
GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS
If Artificial Intelligence (AI) is part of the Contractor system/solution, the Contractor shall be in compliance with E.O. 13960 and 14319, OMB Memorandums M-25-21, M-25-22, and M-26-04, and VA Directive and Handbook 6500 to support VA in trustworthy, secure, responsible, accountable, Truth Seeking, and Ideologically Neutral AI innovation.
The Contractor shall protect VA Sensitive data from unauthorized disclosure or use, and from being used to train or improve the functionality of the vendor's commercial offerings without express permission from VA. Current guidance and approved AI tools are available here: https://department.va.gov/ai/guidance-for-generative-ai-use-at-va/. The entire definition of VA Sensitive Data can be found at 38 U.S.C. § 5727 (23).
The Contractor shall deliver the services, technical data, configurations, models, weights, documentation or other information, including source code, developed during contract performance. The Contractor, in collaboration with VA, must evaluate the output of any AI tool for accuracy prior to using the output in VA efforts. All data, including models, weights, algorithms, and outputs generated using either Government-furnished data or data first developed under this contract shall be the property of the Government with unlimited rights as defined by FAR 52.227-14. The Contractor shall also deliver any custom-developed code developed with AI methodologies in accordance with the SHARE IT Act, if applicable. VA shall also retain unlimited rights to any improvements to that data, including the continued design, development, testing, and operation of AI systems and/or systems utilizing AI.
The Contractor shall ensure that all AI Systems, including Large Language Models (LLM), whether standalone LLMs or integrated into broader software platforms, procured under this effort and/or used in performance of this contract complies with the Unbiased AI Principles as defined in Executive Order 14319 and OMB Memorandum M-26-04, e.g. Truth Seeking and Ideologically Neutral, as applicable to the intended use of the system.
The Contractor shall ensure that AI System/LLM generated outputs are truthful in responding to user prompts seeking factual information or analysis, prioritize historical accuracy, scientific inquiry, and objectivity, as well as acknowledge uncertainty where reliable information is incomplete or contradictory and do not fabricate, hallucinate, or present unverifiable information as fact.
The Contractor shall ensure that LLMs and AI outputs are neutral, nonpartisan tools that do not manipulate responses in favor of ideological dogmas such as Diversity, Equity, and Inclusion (DEI). The Contractor shall ensure that the LLMs, including the AI System, are not intentionally encoded with partisan or ideological judgments within an AI System’s/LLM’s outputs unless those judgments are prompted by or otherwise readily accessible to the end user.
Compliance with the AI requirements of this contract, including adherence to the Unbiased AI Principles, Truth-Seeking and Ideological Neutrality requirements, disclosure obligations, monitoring and reporting requirements, and corrective action responsibilities, is a material condition of eligibility for payment and continued performance. In accordance with OMB Memorandum M-26-04, failure to comply with these requirements, or refusal to take timely and appropriate corrective action to remedy identified noncompliance, may constitute a material breach of contract and may result in remedies consistent with the terms of the contract and applicable law including but not limited to withholding of payment, termination for cause/default, or other appropriate contractual remedies, as determined by the Contracting Officer.
All AI for delivery and/or use in performance of the contract shall adhere to the VA Trustworthy AI Framework, available at https://department.va.gov/ai/trustworthy/. Once the Contractor has obtained CO authorization to use specific AI in contract performance, the Contractor shall provide the COR a signed Statement of Attestation prior to AI implementation as identified in the Artificial Intelligence in VA Contracts clause, to include its associated list of AI being used in contract performance.
Deliverable:
A. Statement of Attestation
AI SYSTEM/LLM DEVELOPMENT AND OPERATION DOCUMENTATION REQUIREMENTS
To enable Government continued assessment of compliance with Trustworthy AI requirements and both Unbiased AI Principles, Truth-seeking and Ideological Neutrality, in accordance with OMB M-26-04, the Contractor shall provide AI System/LLM Development and Operation Documentation Package to include, at a minimum:
1. Acceptable Use Policy The Contractor shall provide an Acceptable Use Policy document governing its AI operation that characterizes and differentiates appropriate and inappropriate use of their product offering
1. Model Cards, System Cards and/or Data Cards The Contractor shall provide documentation describing essential information about the model, system, and or data as it relates to the AI/LLM product offering. The documentation shall address summaries of training process, identified risks and mitigations, and model evaluation scores on LLM benchmarks at a minimum, where appropriate
1. End User Resources The Contractor shall provide documentation to include product tutorials, developer guides, and/or other tools to assist VA in ensuring proper use of the AI/LLM to maximize utility
1. Mechanism for End User Feedback The Contractor shall provide documentation describing the mechanism employed to provide feedback to the Offeror on outputs identified that violate the Unbiased AI Principles. This may be satisfied by a general inbox, specific Point of Contact, or similar feedback mechanism.
Deliverable:
1. AI System/LLM Development and Operation Documentation Package
MONITORING, REPORTING, AND CORRECTIVE ACTION
The Contractor shall develop and implement a Compliance Monitoring and Reporting Plan supporting ongoing monitoring processes to evaluate AI outputs for compliance with Trustworthy AI and Unbiased AI principles. This plan shall include the mechanism for authorized users to provide end user feedback to report suspected violations of Truth-Seeking or Ideological Neutrality requirements.
The Contractor shall notify the COR within 10 business days of identifying any material deviation from these principles and shall submit a written Corrective Action Plan describing mitigation steps, responsible parties, and timelines. Any material deviation, corrective action taken, and results shall be detailed in the Monthly Progress Reports.
Deliverable:
1. Compliance Monitoring and Reporting Plan
1. Corrective Action Plan
AI MODEL UPDATES AND CHANGE DISCLOSURES
The Contractor, in an AI Model/LLM Change Disclosure, shall notify the Government throughout the PoP in advance of any material changes to AI models, including new AI enhancements, features and/or components, controls, retraining, classifiers, system prompts, fine-tuning, content moderation, filters, version replacement, or architectural changes, that could reasonably affect compliance with Trustworthy AI or Unbiased AI principles. Updated documentation shall be provided to VA for VA approval prior to implementation of such changes.
Deliverable:
1. AI Model/LLM Change Disclosure
SECURITY AND PRIVACY REQUIREMENTS
POSITION/TASK RISK…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .