DA10--RFI - Polypharmacy (VA-25-00104075)

Questions & Answers / Clarifications

This document provides additional Question and Answers for Request for Information (RFI) 36C10B25Q0550, concerning "Reducing Inappropriate Polypharmacy at the Department of Veterans Affairs".

This RFI is a modification to a previous notice and includes updated Q&A.

The due date for submissions remains September 15, 2025, at 3:00 PM Eastern Time. The specific questions and answers are detailed in the attached document: RFI 36C10B25Q0550 - QnA_9.12.25.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding Request for Information (RFI) 36C10B25Q0550, "Reducing Inappropriate Polypharmacy at the Department of Veterans Affairs." The answers clarify the nature of the RFI, potential acquisition strategies, technical requirements, and submission guidelines.

• RFI vs. Pre-solicitation: The VA is seeking formal RFI responses, which may also include comments on the RFI itself.
• SDVOSB Set-Aside: The inclusion of a total set-aside for Service-Disabled Veteran-Owned Small Businesses (SDVOSB) is dependent on the final acquisition strategy, which will be informed by market research, including this RFI. If a set-aside occurs, subcontracting thresholds will apply.
• VA Interface Requirements: Information on VA interface requirements can be found via the VA Technical Reference Model (TRM), VA Directive 6551 (Enterprise Cybersecurity), VA Office of Information and Technology (OIT) Standards, VA API Developer Portal, VA Digital Service Toolkit, and FedRAMP resources.
• Solution Type: The VA is primarily seeking a software-based solution, but the extent of contractor involvement in clinical or pharmaceutical aspects may vary based on their expertise. Responses can include brief descriptions of complementary services.
• Extensions: No formal extension is required as the requirement is in the market research phase. Submissions will be accepted after the deadline for consideration, but early submission is encouraged for inclusion in acquisition strategy development.
• Proprietary Information: Vendors should mark proprietary, confidential, and sensitive information as they deem appropriate.

This Q&A document clarifies aspects of the RFI, influencing how vendors should structure their responses and understand potential future acquisition strategies, including set-aside considerations and technical integration requirements.

Questions & Answers / Clarifications

This document provides Question and Answers (QnA) for Request for Information (RFI) 36C10B25Q0550, concerning "Reducing Inappropriate Polypharmacy at the Department of Veterans Affairs".

This RFI is a modification to a previous notice and serves to provide responses to vendor questions. The specific questions and answers are detailed within the attached document.

The due date for submissions remains September 15, 2025, at 3:00 PM Eastern Time. No other impacts to requirements or submission rules are mentioned in this modification notice.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding Request for Information (RFI) Number 36C10B25Q0550, focused on "Reducing Inappropriate Polypharmacy at the Department of Veterans Affairs."

• RFI vs. Pre-Solicitation: The VA is seeking formal RFI responses, which may also include comments on the RFI itself.
• SDVOSB Set-Aside: The inclusion of VAAR 852.219-73 (Total Set-Aside for SDVOSB) and related subcontracting limitations will depend on the final acquisition strategy, determined through market research including this RFI. If multiple capable SDVOSBs/VOSBs or small businesses exist, a set-aside may occur.
• VA Interface Requirements: Information on VA interface requirements can be found via the VA Technical Reference Model (TRM), VA Directive 6551 (Enterprise Cybersecurity), VA Office of Information and Technology (OIT) Standards, VA API Developer Portal, VA Digital Service Toolkit, and FedRAMP resources.
• Solution Scope: The VA is primarily seeking a software-based solution. The extent of contractor involvement for clinical and pharmaceutical input may vary. Responses can briefly describe complementary services (max 500 words) not explicitly detailed in the RFI.

This Q&A clarifies the nature of the RFI response sought and provides critical information regarding potential set-aside strategies and resources for understanding VA technical requirements. Bidders should consider this information when formulating their responses and assessing their capabilities against potential set-aside requirements.

Request for Information (RFI)

The Department of Veterans Affairs (VA) is seeking information on software solutions designed to reduce inappropriate polypharmacy among Veterans. The goal is to identify technologies that can detect cumulative multi-drug interactions, optimize medication regimens, and assist in managing Veteran medication plans.

• Sophisticated technology supported by clinical evidence.
• Demonstrated efficient implementation.
• Proven real-world return on investment based on actual platform deployments.

N/A (This is an RFI, not a solicitation for contract award).

• Interested parties should provide information regarding their software solutions.
• Response Date: September 15, 2025, 3:00 PM Eastern Time.

N/A (This is an RFI).

• NAICS Code: 541512 (Computer Systems Design and Related Services).
• Product Service Code: DA10 (Information Technology Professional Services).
• Contracting Office: Department of Veterans Affairs, Technology Acquisition Center, Eatontown, NJ.
• Contact: Juan Quinones, Contract Specialist, Juan.Quinones@va.gov, 848-377-5173.

Request for Information (RFI)

This RFI seeks information on software solutions to reduce inappropriate polypharmacy and potentially inappropriate medication (PIM) use among Veterans. The VA is looking for tools that can identify cumulative multi-drug interactions, optimize medication regimens, and assist in managing Veteran medication regimens. This RFI is for planning purposes only and is not a solicitation for quotes or proposals. No funds have been authorized for this effort.

Polypharmacy, the concurrent use of multiple medications, increases the risk of adverse drug events, medication non-adherence, drug-drug interactions, and healthcare costs. The VA is particularly interested in solutions that address polypharmacy in Veterans with Post Traumatic Stress Disorder (PTSD) and other mental health conditions, who are often prescribed multiple medications.

The VA requires an easy-to-use tool to facilitate optimal treatment for each Veteran, supporting shared decision-making.

• Automated presentation of active and inactive medications (VA and community).

• Automated evidence-based risk score for inappropriate polypharmacy, identifying high-risk patients.

• Identification of specific risk factors for negative outcomes (e.g., hospice, cognitive disorders, age, frailty, number of ED visits/hospitalizations).

• Automated generation of suggested evidence-based risk scores for individual medications.

• Facilitation of informed shared clinical decision-making by providing drug information, indications, interactions, side effects, and educational materials.

• Recording of adverse events and interface with VA communication tools for reconciliation and reminders.

• Support for collaboration and shared treatment planning across clinical teams.

• Minimization of time for clinical decision-making regarding treatment changes.

• Recommendations to healthcare providers that offer options rather than directives.

• Compliance with VA IT requirements (e.g., FedRAMP, ATO).

• Secure handling of Patient Health Information (PHI) and Personally Identifiable Information (PII).

• Interoperability with VA systems, including bidirectional data exchange and secure APIs.

• Ability to facilitate review of individual patient and population clinical outcomes.

• Respondents must indicate how their solution meets the clinical and critical requirements.

• For unmet requirements, provide plans, estimated costs, and timelines.

• Provide data showing software effectiveness, validated algorithms, and IT compliance.

• Identify specific scientific sophistication, deployment numbers, processing speed, and clinical efficiency.

• Explain software structure, implementation, and costs.

• Indicate operational readiness by November 15, 2025.

• Responses are due by September 15, 2025, via email.

• This is an RFI only; no contract will be awarded based on responses.

• Information submitted is voluntary and becomes government property.

• Set-aside decisions may be made based on responses.

• The requirement may be delayed, canceled, or revised.