36C26026Q0775 0001.pdf

5. PROJECT NUMBER (if applicable)

CODE 7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER 3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO. 1. CONTRACT ID CODE

FACILITY CODE CODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office. is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30 PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243

(Type or print) (Type or print)

(Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code)

(If other than Item 6)

(Specify type of modification and authority)

(such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

1 9

0001 07-09-2026

496-26-4-287-0034

36C260

Department of Veterans Affairs Network Contracting Office 20 (V4CONT) 1601 E. Fourth Plain Boulevard Building 17, Suite B428 Vancouver WA 98661

36C260

Department of Veterans Affairs Network Contracting Office 20 (V4CONT) 1601 E. Fourth Plain Boulevard Building 17, Suite B428 Vancouver WA 98661

To all Offerors/Bidders

36C26026Q0775

06-25-2026

X

X X

** HOUR & DATE for Receipt of Offers is EXTENDED to: 07-20-2026 1PM MDT **

496-3660160-287-825500-2519 CS01Q00A1

X one (1)

The purpose of this amendment is to answer questions received and extend the date/time for offers received.

Please see continuation page. Questions are in black font. Answers are in red font. The hour and date specified for receipt of Offers is extended to 07/20/2026, 1PM Mountain.

Jennifer Robles Contracting Officer

VA-VHA-RPOW-2024-0043

A.1 QUESTIONS AND ANSWERS SOLICITATION 36C26026Q0775

1) Question: To help us prepare a comprehensive bid, could you please provide details regarding your previous licensing costs, context, and counts?

Answer: Contract number 36C26025P0591 was awarded to Velocity Applications LLC on 03/27/2025 in the amount of $460,932.00.

2) Question: This is open to small businesses, not just Service-Disabled Veteran Owned Small Businesses?

Answer: Solicitation 36C26026Q0775 is 100% set-aside for small businesses.

3) Question: The response itself, does it have to use the PDF posted, or a Word document that addresses all of the questions in the RFQ acceptable? Can you confirm a response will be accepted?

Answer: Please refer to Solicitation, SF 1449 on page 1 and Section E.1. Instructions for Offerors on pages 36 – 39. For information on how offers will be evaluated, please refer to Section E.8, pages 45 – 47 of the solicitation

4) Question: Please clarify an apparent inconsistency within the solicitation. Specifically, the solicitation indicates that VISN 20 has a need for renewing software licensing and support for their existing cloud-based image exchange platform, Vaultara, or an equivalent or better solution that provides fast, secure, contact-less sharing of medical imaging and data with community healthcare partners, while simultaneously describing the procurement as "Brand Name or Equal" to Vaultara.

a) Please provide guidance on how these two provisions are intended to be reconciled.

b) To the extent this procurement constitutes a subscription renewal, it would follow that the renewal pertains specifically to the Vaultara subscription, as Vaultara is understood to be the sole vendor of that system. If this is the case, we respectfully request confirmation as to whether a Notice of Intent to sole source, as contemplated under FAR 5.203, was issued in connection with this procurement, or alternatively, an explanation as to why such notice was not required.

c) Further, a subscription renewal would appear to be in tension with VA’s stated policy of a common enterprise-wide solution. For image exchange, every VISN other than VISN 20 is using Medicom’s ImageX solution. Please explain the basis upon which VISN 20 has identified Vaultara as the benchmark for this solicitation.

d) Should the VA instead be evaluating alternative vendors for this requirement, please explain how the VA would differentiate between the incumbent system and other available systems.

e) Please provide clarity as to how alternative offerors are to provide the SF 1449 in their response to this solicitation if the SF 1449 in this solicitation is already pre-filled with details regarding Vaultara services such as the quantity being requested for each CLIN item.

Answer: This solicitation is for license renewal and maintenance services for existing cloud-based image exchange platform (Vaultara) or an equivalent or better image exchange solution.

This is not a brand name requirement. If vendors have an equivalent or better image exchange platform to replace the existing system, they are encouraged to submit an offer. For information on how offers will be evaluated, please refer to Section E.8, pages 45 – 47 of the solicitation. For instructions to offerors, please refer to Section E.1, pages 36 – 39.

3) Question: In Section 2 - Background of the Statement of Work it states, “This contract also provides system steward support for VISN 20 to continue migrating Vaultara’s Software-as-a-Service (SaaS) Fedramp authorized platform into VA’s Enterprise Cloud (VAEC) environment”. Will alternative offerors be given the same system steward support?

Answer: This statement is not in Section 2 – Background of the Statement of Work. Please refer to the Statement of Work in solicitation number 36C26026Q0775.

4) Question: On page 18 of the Solicitation, under Section C.6 52.219-14 LIMITATIONS ON SUBCONTRACTING (NOV 2025) (DEVIATION) - It provides two options under f.1 on how the contractor shall comply with the limitations on subcontracting, but neither of the two options is selected. Under the prior solicitation for these services, 36C26026Q0728, the first option “By the end of the base term of the contract and then by the end of each subsequent option period” was selected. Please explain which of the two options is intended to be selected for this solicitation.

Answer: The Contractor shall comply with the limitations on subcontracting as by the end of the base term of the contract and then by the end of each subsequent option period. Please see A.2 below for full corrected clause.

5) Question: In the Statement of Work, under Section 3.B.: System Specifications - it states, “vendor response must include a transition plan”. Can you please explain the role and requirements of the incumbent vendor during the transition period?

Answer: The incumbent vendor would be required to adhere to the contractual obligations within their current contract.

6) Question: In the Statement of Work, Section 3.B.1.xviii of the Technical Requirements - Basic, the document specifies that “VA client requires less than 50GB local storage and 16GB RAM to minimize resource provisioning on the hosting system”. With increased utilization, a rigid 50GB storage ceiling may create a data-ingestion bottleneck and artificially limit application throughput. If local storage capacity emerges as an operational bottleneck, please explain the mechanism for adjusting or scaling the local storage threshold, given that it is currently an evaluation criterion?

Answer: We require that the solution design account for data-ingestion bottlenecks and efficient throughput with minimal resource-provisioning needed, regardless of increased utilization. In the event the solution cannot meet this, please state “requirement cannot be met” and describe when and why this situation may occur, as well as provide (1) a plan(s), including timeline, to achieve the requirement or (2) any compensating measure(s) or technical capability(s) for a comparable offering to the stated requirement.

7) Question: In the Statement of Work, Section 3.B.1.xx of the Technical Requirements - Basic, the document specifies that “Provide VA the ability to request images from CCPs; tracks request statuses and provides VA and CCP visibility into CCPs’ fulfillment and completion of image requests”.

Please explain the format and desired workflow in which VISN 20 anticipates the prior imaging requests to CCPs will be done. Will it be electronic or paper format, and which service line at VISN 20 is expected to manage those requests?

Answer: This is a requirement of the solution; the solution/system must provide VA the ability to submit requests for images to the CCPs electronically as part of the system, as well as track the statuses of those requests and provide VA and the CCP visibility into the CCP’s fulfillment and completion of the image requests electronically and as part of the system. The service line relevant to the request should have the ability to submit and track the requests within the solution.

8) Question: In the Statement of Work, Section 3.B.2.i of the Technical Requirements - Performance, Scaling, and Monitoring, it states that “Support exchange of over 2M static images a month, or over 1,000 transactions a week with transaction times never exceeding 2 minutes for studies under 1GB or 5 minutes for studies under 3GB”. When it refers to supporting 1,000 transactions a week, does that mean 1,000 imaging exams exchanged each week, or is there another intended meaning for “transactions”?

Answer: Solution must support exchanging at minimum 1,000 imaging exams each week with the minimum transaction time and size efficiencies specified.

9) Question: In the Statement of Work, Section 3.B.2.vi of the Technical Requirements - Performance, Scaling, and Monitoring, it states that “Centralized management system that supports remote management of local agent configuration changes, log analysis, and transaction re-sends for quick problem resolution without intervention needed by VA”.

a) Please explain who the intended party is that will be responsible for this?

b) If it is intended for the contractor to perform these management services, please explain if there are additional considerations, approval processes, or requirements needed for the contractor to conduct transaction re-sends on behalf of VA?

Answer: The contractor must provide these support services. Transaction re-sends are to occur in the event of a transaction failure/error or stalled/hung transaction that was originally executed by VA or CCP, and is to be a continuance of sending that same transaction after an investigation by the contractor, system, or VA staff yields that resuming the processing of the transaction is the next appropriate troubleshooting action to help facilitate the transaction successfully reaching its destination.

10) Question: In the Statement of Work, under Section 3.B.3.i: Technical Requirements - for CCPs, it states “PACS-to-PACS connections must be capable of being deployed with CCPs in under an hour via a client that is a lightweight software application on CCP’s network, and must not require the CCP to provision or run a server or virtual machine; application file size is under 1GB and requires less than 20GB of local storage to minimize resource provisioning on the hosting device”.

a) Please explain the technical architecture of the lightweight software application that is not to require the CCP to provision or run a server to operate?

b) If it is intended to be solely a web-based application, please explain the inconsistency with the requirement for a PACS-to-PACS workflow without any interface outside of the respective PACS system.

c) Please explain the inconsistency with this requirement regarding how the application must not require the CCP to provision or run a server, but then, in the same requirement, states the application is to require less than 20GB of local storage. If there isn’t a local server provisioned by the CCP, why is it referencing local storage size requirements?

d) If the application must not require the CCP to provision or run a server for PACS-to-PACS connections, then that means that there will be no local network component for direct DICOM communication to the CCP PACS, which is another requirement listed in the SOW. Please explain the anticipated protocol that will be leveraged instead of DICOM DIMSE for PACS-to-PACS connections.

e) If DICOMweb is to be leveraged, what is the plan if the CCP’s imaging archive is not able to communicate via DICOMweb?

Answer: The contractor must offer a lightweight, installable software program that the CCP can install as an application on a Windows, Linux, or Mac OS. The solution must not be a virtual machine or package that requires another application to run it. The requirement does not state that it is to be a web-based application, nor does it state that DICOMweb will be required. The solicitation does not state there would be no local network component for direct DICOM communication to the CCP PACS. The solicitation states that the user must not be required to login to any interface outside of their respective PACS in order to exchange images via a PACS-to-PACS connection; it does not state that there would be no interface outside of the respective PACS system.

11) Question: In the Statement of Work, under Section 3.B.3.ii: Technical Requirements - for CCPs, it states “Allows CCP to install the software application for image exchange between VA PACS and CCP PACS without vendor support”. Based on the requirement that the CCP does not have to provision a local server, please explain what VISN 20 means by ‘allow CCP to install the software’ if there is no local server being provisioned at CCP? Is it per workstation?

Answer: VA requires the contractor to provide a lightweight, easy to install software program that technical or non-technical CCP staff can quickly install as an application on a Windows, Linux, or Mac OS, that facilitates PACS-to-PACS image exchange between VA PACS and CCP PACS. The solution must not be a virtual machine or package that requires another application to run it.

12) Question: In the Statement of Work, under Section 3.B.5.ii: Technical Requirements - EHR Interface, it states, “Supports automated Study-to-Patient matching using patient name, date of birth, MRN, and/or accession number from MWL, HL7, or FHIR interface release 4 and above”. Can you please explain which FHIR instance VISN 20 plans to use for the FHIR interface?

Answer: The requirement is that the system must be capable of performing/supporting automated Study-to-Patient matching using patient name, date of birth, MRN, and/or accession number from MWL, HL7, or FHIR interfaces release 4 and above. This is a 5-year contract, during which it is expected that FHIR version 4 will be released. During the contract period, the solution must support at minimum FHIR version 2 as well as any subsequent releases of the standard that occur during this contract.

13) Question: In the Statement of Work, under Section 3.B.5.iii: Technical Requirements - EHR Interface, it states, “Supports automated workflows such as “Send-By Schedules” to increase outside study submission to VA, wherein the system notifies CCP of procedure, sends VA prior studies and reports to CCP, requests CCP send outside study to VA, and ingests outside study matched to a patient into

VA EHR”.

a) Please explain how this requirement is applied in situations where a Veteran has a non-scheduled CCP visit.

b) Please explain if “VA EHR” refers to a single EHR or if it will be stored in both Oracle Cerner and

VistA?

c) Please explain the scheduling source intended for the automated workflows and the interfaces anticipated to be used?

Answer: The system workflow shall not be dependent on whether a veteran has been scheduled for a CCP visit, just that the referral/request for the visit has been provided to the CCP. VA EHR refers to the EHR that the VA site is currently using- Vista or Oracle Cerner. VISN 20 has a mix of sites, wherein some sites are using Vista, and some are using Oracle Cerner. During the duration of this 5-year contract, the system must be able to interact with the existing VA workflow systems and related interfaces, defined in section 5. Technical Requirements i. The contractor is expected to explain how they/their solution meets, exceeds, or cannot meet this requirement. In instances where the system cannot currently meet a requirement, the response must state “requirement cannot currently be met” and where feasible, provide (1) a plan(s), including timeline, to achieve the requirement or (2) any compensating measure(s) or technical capability(s) for a comparable offering to the stated requirement.

14) Question: In the Statement of Work, under Section 3.B.6.iii: Technical Requirements - Logic Engine, it states, “System must also provide remote search capabilities, allowing studies to be located, collected, and anonymized using a custom rule set, tagged specifically for the study, and distributed to the research group automatically”.

a) Please explain if the research group referred here is an internal VA research group or from an academic affiliate?

b) Please explain if the exchange of studies for research is managed by the same service line that will be managing the exchange of studies for Community Care.

Answer: The research group can either be internal or external to the VA. Any service line relevant to the exchange of research studies must be able to utilize this feature.

15) Question: In the Statement of Work, under Section 3.B.7.iii: Technical Requirements - Security, it states, “Has a system-specific VA Authorization to Operate (ATO) for VA Enterprise Cloud (VAEC) or SaaS Fedramp AWS GovCloud environment”. Please explain if VISN 20 will support the contractor in obtaining an ATO for this deployment in the scenario that the incumbent vendor is not selected.

Answer: The contractor is expected to explain how they/their solution meets, exceeds, or cannot meet this requirement. In the event they cannot meet the requirement, the response must state “requirement cannot currently be met” and where feasible, provide (1) a plan(s), including timeline, to achieve the requirement or (2) any compensating measure(s) or technical capability(s) for a comparable offering to the stated requirement.

A.2 52.219-14 LIMITATIONS ON SUBCONTRACTING (NOV 2025) (DEVIATION)

(a) This clause does not apply to the unrestricted portion of a partial set-aside.

(b) Definition. Similarly situated entity, as used in this clause, means a first-tier subcontractor, including an independent contractor, that—

(1) Has the same small business program status as that which qualified the prime contractor for the award (e.g., for a small business set-aside contract, any small business concern, without regard to its socioeconomic status); and

(2) Is considered small for the size standard under the North American Industry Classification System (NAICS) code the prime contractor assigned to the subcontract.

(c) Applicability. This clause applies only to—

(1) Contracts that have been set aside for any of the small business concerns identified in 19.000(a)(3);

(2) Part or parts of a multiple-award contract that have been set aside for any of the small business concerns identified in 19.000(a)(3);

(3) Contracts that have been awarded on a sole-source basis in accordance with sections 19.105, 19.106, 19.107, and 19.108;

(4) Orders expected to exceed the simplified acquisition threshold and that are set aside for small business concerns under multiple-award contracts, as described in 8.4 and 16.5;

(5) Orders, regardless of dollar value, that are set aside in accordance with sections 19.105, 19.106, 19.107, and 19.108 under multiple-award contracts, as described in 8.4 and 16.5; and

(6) Contracts using the HUBZone price evaluation preference to award to a HUBZone small business concern unless the concern waived the evaluation preference.

(d) Independent contractors. An independent contractor shall be considered a subcontractor.

(e) By submission of an offer and execution of a contract, the Contractor agrees that in performance of a contract assigned a North American Industry Classification System (NAICS) code for—

(1) Services (except construction), it will not pay more than 50 percent of the amount paid by the Government for contract performance to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor’s 50 percent subcontract amount that cannot be exceeded. When a contract includes both services and supplies, the 50 percent limitation shall apply only to the service portion of the contract;

(2) Supplies (other than procurement from a nonmanufacturer of such supplies), it will not pay more than 50 percent of the amount paid by the Government for contract performance, excluding the cost of materials, to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor’s 50 percent subcontract amount that cannot be exceeded. When a contract includes both supplies and services, the 50 percent limitation shall apply only to the supply portion of the contract;

(3) General construction, it will not pay more than 85 percent of the amount paid by the Government for contract performance, excluding the cost of materials, to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor’s 85 percent subcontract amount that cannot be exceeded; or

(4) Construction by special trade contractors, it will not pay more than 75 percent of the amount paid by the Government for contract performance, excluding the cost of materials, to subcontractors that are not similarly situated entities. Any work that a similarly situated entity further subcontracts will count towards the prime contractor’s 75 percent subcontract amount that cannot be exceeded.

(f) The Contractor shall comply with the limitations on subcontracting as follows:

(1) For contracts, in accordance with paragraphs (c)(1), (2), (3) and (6) of this clause—

[x] By the end of the base term of the contract and then by the end of each subsequent option period; or

[] By the end of the performance period for each order issued under the contract.

(2) For orders, in accordance with paragraphs (c)(4) and (5) of this clause, by the end of the performance period for the order.

(g) A joint venture agrees that, in the performance of the contract, the applicable percentage specified in paragraph (e) of this clause will be performed by the aggregate of the joint venture participants.

(1) In a joint venture comprised of a small business protégé and its mentor approved by the Small Business Administration, the small business protégé shall perform at least 40 percent of the work performed by the joint venture. Work performed by the small business protégé in the joint venture must be more than administrative functions.

(2) In an 8(a) joint venture, the 8(a) participant(s) shall perform at least 40 percent of the work performed by the joint venture. Work performed by the 8(a) participants in the joint venture must be more than administrative functions.

(End of Clause)