DRAFT_Product_Description_MedKnowledge_18Nov2026.pdf

PDF 364 KB Posted

Attached to
DA10--MedKnowledge Decision Support Tools (First Data Bank)
Solicitation number
36C10B27Q0126
Issued by

About this file

This is a Product Description document for a federal contract opportunity issued by the Department of Veterans Affairs, Veterans Health Administration (VHA), Pharmacy Service for the renewal of FDB MedKnowledge Information Architecture and Clinical Decision Support Modules (Contract Number VA-27-00009129).

The VA requires an enterprise license for the FDB MedKnowledge framework and associated clinical modules to support medication order checks within the VistA Electronic Health Record system and MOCHA pharmacy applications. The MedKnowledge database provides critical clinical decision support for drug-drug interactions, therapeutic duplication, maximum dosage, and pharmacogenomic medication order checks, with planned additions of hepatic and renal order checks in 2027. The system is tightly coupled with VistA APIs developed according to the vendor's database schema and algorithms, and the clinical content is required for validation and support of the VA's National Drug File (NDF) and National Clinical Infusion Library (NCIL). The contractor must provide daily updates of changes to the architecture and framework, drug database updates, and FDB customer service support to VA personnel and contractors.

The contract period consists of a Base Period from January 31, 2027 to January 30, 2028, with four optional 12-month renewal periods through January 30, 2032. The Base Period deliverables include the MedKnowledge Framework enterprise license, Patient Education Module (Spanish), Drug-Drug Interaction for Consumers Module, Hepatic and Renal Dosing Content Bundle with API implementation and 12 months of customization support, Pharmacogenomics Content & API Bundle, Custom Monthly Reports, Infusion Knowledge Solution (fewer than 10 users), and Federal Custom Clinical Utility Development Maintenance and Support. Additionally, five Optional Tasks may be exercised individually or concurrently during the Base Period and Option Periods, including the MedGuide Module, Opioid Risk Module, and CDS Module Bundles in Sandbox/Development, Pilot Phase (up to 10 sites), and Enterprise Roll-out configurations. The contractor must comply with Section 508 accessibility standards, VA Technical Reference Model requirements, Zero Trust VA Critical Security Controls (effective July 1, 2025), SSN reduction and usage restrictions, IPv6-Only support, TIC 3.0 requirements, and software licensing provisions. AI-related requirements apply only if AI is incorporated into the contractor's solution; compliance with Trustworthy AI Framework, Unbiased AI Principles (Truth-Seeking and Ideological Neutrality), and comprehensive AI documentation and monitoring requirements are mandatory. The contractor must provide quarterly Price and Utilization Reports using the OMB M-26-10 Template. Contact information is provided for the VA Program Manager (Ms. Amy Norris), Contracting Officer's Representative (Ms. Zita Schmitt), Contracting Officer (Mr. John Fields), and Contract Specialist (Mr. James Cummiskey).

View the file

Other files

File Type Posted
36C10B27Q0126_Request for Information.pdf PDF
36C10B27Q0126.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

B.5 PRODUCT DESCRIPTION

PRODUCT DESCRIPTION

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA)

Pharmacy Service

MedKnowledge Information Architecture and Clinical Decision Support Modules

VA-27-00009129

PD Version Number: 1.0

1.0 PRODUCT REQUIREMENTS

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Pharmacy Service has a requirement to renew the license for the FDB MedKnowledge Information Architecture and associated clinical knowledge content modules. The VA’s VistA Electronic Health Record (EHR), Medication Order Check Healthcare Application (MOCHA) suite of pharmacy software applications, utilizes commercially sourced clinical content to provide foundational clinical decision support (CDS) in the form of medication order checks that VA providers and pharmacists rely upon within CPRS and pharmacy applications. MOCHA encompasses drug-drug interaction, therapeutic duplication, maximum dosage, and pharmacogenomic medication order check alerts. Development is underway for the addition of hepatic and renal order checks alerts in 2027. These order checks are vital to the VA mission, ensuring patient safety and high-quality healthcare. Additionally, the FDB clinical content is required for internal validation and support of data within the VA’s National Drug File (NDF) and National

Clinical Infusion Library (NCIL).

FDB MedKnowledge Information Architecture is tightly coupled with VistA Application Program

Interfaces (APIs) which were strictly developed according to the vendor’s database schema, API calls and algorithms. The FDB standard Reference Tables, via APIs, sustain the MOCHA suite of pharmacy applications including MOCHA, Pharmacy Product System National (PPSN)/ National Drug File

(NDF), Pharmacy Enterprise Customization System (PECS), Data Update (DATUP), and MOCHA

Server.

The period of performance (PoP) for this proposed contract will consist of a Base Period of 12 months and four 12-month Option Periods. There are also five Optional Tasks for the Base Period and Option

Periods that can be exercised at any point during those periods for a maximum of twelve months.

1.1 MEDKNOWLEDGE LICENSE REQUIREMENTS:

The Contractor shall provide MedKnowledge Information Architecture, associated clinical modules and support for duration of 12 months from contract award. The Contractor shall provide MedKnowledge database and tools given the following assumptions:

1. The Contractor shall provide VA with an enterprise license for 12 months for the MedKnowledge framework, architecture and modules identified in the table below.

2. The MedKnowledge database and tools shall be available to all VA personnel. The MedKnowledge database and tools shall also be available to VA Contractors working for VA.

3. Non-Proprietary information shall also be shared with users outside VA, for example, Department of

Defense and other VA vendors.

4. A VA developed, open source code interface shall be utilized to access the MedKnowledge database and associated modules for the purpose of sending medication order check data and then receiving applicable FDB medication order check alert data.

5. The Contractor shall ensure the information is available for use for the following purposes:

a. The information will be accessed by the VA Veterans Health Information Systems and Technology

Architecture (VistA) system for use in Pharmacy, Physician order entry, Electronic Medical Records, E-prescribing, Bar Code Administration

b. VA Reports

c. Web sites

d. Validation of internal data

6. VA reserves the right to use the information in other ways not listed.

7. VA reserves the right to use consumer drug monographs (i.e. Patient Medication Information PMI), images, and drug names on VA website, including the use of NDCs and other identifying information to direct users to the correct information. Any other information contained on the web will be placed either on the VA intranet or be password protected.

8. The Contractor shall provide updates of any changes to the architecture, framework and any modules daily, or on another recurring schedule determined by VA, not to exceed daily.

9. The Contractor shall provide drug database updates to the packages listed.

10. The Contractor shall provide FDB customer service support for VA personnel and VA Contractors.

1.2 REPORTING REQUIREMENTS

The Contractor shall provide a Price and Utilization Report using the M-26-10 Template, completing the appropriate tabs, which collects information related to Software, Artificial Intelligence, Cloud, and

Hardware acquisitions in accordance with OMB M-26-10. This information shall be submitted on a quarterly basis throughout the period of performance, including any exercised options or contract extensions. OMB M-26-10 is a requirement of this contract and requires IT vendors to disclose utilization and pricing information to the Government, without limiting the extent to which that information may be shared across agencies. The Contractor shall access the M-26-10 Template, located here, prior to reporting each quarter to ensure latest template is used.

Deliverable:

A. Price and Utilization Report

1.3 FEDERAL CUSTOM CLINICAL UTILITY

Federal Custom Clinical Utility will allow integration with the most recent MedKnowledge Framework clinical data within the VA developed Pharmacy Enterprise Customization System (PECS). The Custom

Utility is an existing, Contractor-managed product that enables replication of the Framework within

PECS.

1.3.1 FEDERAL CUSTOM CLINICAL UTILITY DEVELOPMENT MAINTENANCE AND

SUPPORT

https://www.voa.va.gov/DocumentView.aspx?DocumentID=5122

The contractor shall allow continued integration with the most recent MedKnowledge Framework clinical data within VA developed PECS. The Contractor shall maintain and support the Custom Utility to ensure continued integration and compatibility with PECS, including compatibility of the hepatic and renal content with VA PECS functionality.

Table 1.0

Base Period - 01.31.2027 - 01.30.2028

Description Quantity

MedKnowledge Information Architecture (Formerly

National Drug Database File (NDDF)) including:

MEDKNOWLEDGE FRAMEWORK

1 x 12 month enterprise license

Patient Education Module (Spanish) 1 x 12 month enterprise license

Drug-Drug Interaction for Consumers Module 1 x 12 month enterprise license

Hepatic and Renal Dosing Content Bundle (API

Implementation)

1 x 12 month enterprise license

Hepatic and Renal Dosing Content Customization

Support

12 months

Pharmacogenomics Content & API Bundle (Enterprise) 1 x 12 month enterprise license

Custom Monthly Reports 1 x 12 month enterprise license

Infusion Knowledge Solution (Less than 10 users) 1 x 12 month enterprise license

Federal Custom Clinical Utility Development

Maintenance and Support IAW PD 1.3.1

12 months

Option Periods 1 through 4 (If exercised)

Option Period 1 - 01.31.2028 - 01.30.2029

Option Period 2 - 01.31.2029 - 01.30.2030

Option Period 3 - 01.31.2030 - 01.30.2031

Option Period 4 - 01.31.2031 - 01.30.2032

Description Quantity

MedKnowledge Information Architecture (Formerly

National Drug Database File (NDDF)) including:

MEDKNOWLEDGE FRAMEWORK

1 x 12 month enterprise license

Patient Education Module (Spanish) 1 x 12 month enterprise license

Drug-Drug Interaction for Consumers Module 1 x 12 month enterprise license

Hepatic and Renal Dosing Content Bundle (API

Implementation)

1 x 12 month enterprise license

Pharmacogenomics Content & API Bundle (Enterprise) 1 x 12 month enterprise license

Custom Monthly Reports 1 x 12 month enterprise license

Infusion Knowledge Solution (Less than 10 users) 1 x 12 month enterprise license

Federal Custom Clinical Utility Development

Maintenance and Support IAW PD 1.3.1

12-months

Base Period Optional Tasks (If exercised)

01.31.2027 - 01.30.2028

Each line item below may be exercised individually, or in concert with other Optional Tasks.

The PoP for the Optional Tasks shall be up to 12 months from date of Option Exercise, to run concurrent with the current Period of Performance.

Description Quantity

Optional Task 1

MedGuide Module – (Enterprise License)

Optional Task 2

Opioid Risk Module (Enterprise)

Optional Task 3

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, MK Enh, FWK Enh)

-Sandbox/Development

Up to 12-months

Optional Task 4

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, -Pilot Phase - up to 10 sites

Optional Task 5

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, -Enterprise Roll-out

Optional Tasks (If exercised)

Each below line item may be exercised individually, or in concert with other Optional Tasks.

The PoP for the Optional Tasks shall be up to 12 months from date of Option Exercise, to run concurrent with the current Period of Performance.

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section

255 of the Communications Act. The final rule went into effect on January 18, 2018. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all

VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

Option Period 1 Optional Tasks - 01.31.2028 to 01.30.2029

Option Period 2 Optional Tasks - 01.31.2029 to 01.30.2030

Option Period 3 Optional Tasks - 01.31.2030 to 01.30.2031

Option Period 4 Optional Tasks - 01.31.2031 to 01.30.2032

Description

Quantity

Optional Task 1

MedGuide Module – (Enterprise License)

Optional Task 2

Opioid Risk Module (Enterprise)

Optional Task 3

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, -Sandbox / Development

Optional Task 4

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, -Pilot Phase - up to 10 sites

Optional Task 5

CDS Module Bundle (MCP, TMW, Navigo, Verify Assist, -Enterprise Roll-out

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA

Guidelines)

E204 Functional Performance Criteria

E206 Hardware Requirements

E207 Software Requirements

E208 Support Documentation and Services Requirements

2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

2.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section

508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

3.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS

Not Applicable. This acquisition does not involve the procurement of information technology hardware or equipment subject to Energy Star, FEMP Low Standby Power, or RFO 52.223-23 sustainable product requirements.

4.0 SHIPMENT OF HARDWARE OR EQUIPMENT

Not Applicable.

5.0 GENERAL REQUIREMENTS

5.1 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.

5.2 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.

5.3 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.

5.4 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 https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119 https://doi.org/10.6028/NIST.SP.800-119 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.

5.5 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.

5.6 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.)

5.7 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS

(Note to Offerors: Section 5.7, including 5.7.1 through 5.7.3, applies only if AI is part of the proposed system/solution or is used in contract performance. Offerors shall indicate applicability through the AI self-certification as part of their quote if a solicitation is issued. If the Offeror certifies that no AI will be used, Section 5.7 will be removed or marked “Not Applicable” in the resulting award. The “Artificial

Intelligence in VA Contracts” clause applies to any resulting contract regardless.)

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.

https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdepartment.va.gov%2Fai%2Fguidance-for-generative-ai-use-at-va%2F&data=05%7C02%7C%7Cb4d631443f87422faac408deee52467d%7Ce95f1b23abaf45ee821db7ab251ab3bf%7C0%7C0%7C639210234603950587%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1GPSJAilRKNtxAY0%2BiTU19C764Fn9giq9oTOp1Xqj1c%3D&reserved=0

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.

A. Statement of Attestation

5.7.1 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:

https://department.va.gov/ai/trustworthy/

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

2. 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

3. 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

4. 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.

5. Pre-Training and Post-Training Activities of the AI System/LLM

The Contractor shall provide documentation of Pre-Training and Post Training Activity that provides details on:

a. Actions taken that impact the factuality and grounding of AI System/LLM outputs

b. System-level prompts that provide natural language instructions to the model specifying guidelines on responding to user-generated queries, to include how a model responds when reliable information is incomplete, contradictory, or subject to individual interpretation

c. The type of outputs restricted via content moderation and safety filters

d. The use of red teaming as a means of continuously assessing the model to protect against incidents of bias in generated output.

e. Training or development, if any, that occurred outside the United States, to include the type of activity and the country in which it occurred.

f. Any modifications or configurations undertaken to comply with any regulation from a government other than the U.S. Federal Government.

6. Model Evaluation Results and Methodologies

The Contractor shall provide documentation describing the Evaluation Results of bias evaluations conducted by the Vendor to include the methodology for performing such tests (e.g., testing prompt pairs for politically oriented topics).

The documentation shall also include Benchmark scoring results measuring the model’s bias, helpfulness, honesty, or accuracy when provided with ambiguous versus straightforward questions. (Including any benchmarks comparing performance across multiple languages, where applicable).

7. Description of Enterprise-Level Controls

The Contractor shall provide documentation describing the Enterprise Governance tools and controls, such as:

a. Customizable system instructions that are additive to a base model’s system prompts or content generation filters.

b. Product features that require a model to cite sources of its outputs or otherwise provide visibility into the provenance of the model’s outputs.

c. AI System/LLM model evaluation tools that enable comparisons either between a model’s outputs, or across various models.

8. Third Party Modification Disclosure

The Contractor shall disclose of any additional controls to modify an AI Model’s/LLM’s output applied by the Contractor if the Contractor is not a direct developer of the LLM (e.g., classifiers, system prompts, fine-tuning, content moderation and filters, etc.)

A. AI System/LLM Development and Operation Documentation Package

5.7.2 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.

A. Compliance Monitoring and Reporting Plan

B. Corrective Action Plan

5.7.3 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.

A. AI Model/LLM Change Disclosure

6.0 SECURITY AND PRIVACY REQUIREMENTS

Not Applicable. Position risk designation and contractor personnel security requirements are not required for this acquisition. The C&A requirements do not apply, and a Security Accreditation

Package is not required.

POINTS OF CONTACT

VA Program Manager:

Name: Ms. Amy Norris

Voice: 561-543-8876

Email: amy.colon@va.gov

Contracting Officer’s Representative:

Name: Ms. Zita Schmitt

Voice: Use E-mail

Email: zita.schmitt@va.gov

Contracting Officer:

Name: Mr. John Fields

Voice: 843-377-5259

Email: john.fields3@va.gov

Contract Specialist:

Name: Mr. James Cummiskey

Voice: 848-377-5117

Email: james.cummiskey@va.gov

B.5 PRODUCT DESCRIPTION
1.0 PRODUCT REQUIREMENTS
2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508)
2.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS
2.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY
2.3 ACCEPTANCE AND ACCEPTANCE TESTING
3.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS
4.0 SHIPMENT OF HARDWARE OR EQUIPMENT
5.0 GENERAL REQUIREMENTS
5.1 VA TECHNICAL REFERENCE MODEL
5.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS
5.3 ENTERPRISE SOCIAL SECURITY NUMBER (ESSN) REDUCTION
5.4 INTERNET PROTOCOL VERSION 6 (IPV6)
5.5 SOFTWARE AND LICENSING REQUIREMENTS
5.6 TRUSTED INTERNET CONNECTION (TIC)
5.7 GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS
6.0 security and privacy requirements
Not Applicable. Position risk designation and contractor personnel security requirements are not required for this acquisition. The C&A requirements do not apply, and a Security Accreditation Package is not required.

File details come from the government source that posted it. Updated .