36C10B26R0035 0001.docx

SUBJECT*

Enterprise Mammography Tracking and Reporting System Amendment 00001

GENERAL INFORMATION

SET-ASIDE

Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

POINT OF CONTACT*

Contract Specialist Terricia Lloyd, Terricia.Lloyd@va.gov

Contracting Officer:

Brett Scwerin, Brett Schwerin@va.gov

PLACE OF PERFORMANCE

ADDRESS

POSTAL CODE

ADDITIONAL INFORMATION

AGENCY’S URL

URL DESCRIPTION

AGENCY CONTACT’S EMAIL ADDRESS

EMAIL DESCRIPTION

Amendment to a Previous Combined Solicitation

Amendment to a Previous Combined Solicitation

Page 1 of

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) 08-12-2026

VA-25-00046145

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

36C10B26R0035 08-10-2026 36C10B26R0034 x See Contiuation Pages

Brett Schwerin Contracting Officer A. The purpose of this amendment is to provide response to questions received from industry. The following questions were submitted by industry regarding the above-referenced solicitation. The Government's responses are provided below.

1. For each site, should offerors assume there is one centralized system/hub that connects to the relevant computers and departments, or should offerors assume each individual computer/access point requires its own deployment hardware, secure key/media, local continuity setup, and access-control device?

Response: Offerors should assume there is one national centralized system/hub that all sites (and respective workstations) will connect to. Each individual computer/access point will not require its own site/VISN level servers. Contractors can propose traditional install application or web-based offerings based on capabilities for their respective solution. The expectation is for the national high availability server configuration to account for primary system fault tolerance. If offerors are recommending additional local hardware for an added layer of fault tolerance, that can be included in the proposal.

2. Please also clarify the expected number of physical access points or workstations across the full mammography workflow where users may access or input MTRS-related information. This includes, as applicable, imaging, lab/pathology, provider/physician, nursing/clinical, patient intake/scheduling, radiology/reporting, administration, and any central control or server locations.

Response: The exact number of physical access points is dynamic as staffing and mammography program change occurs. Workstation connection at any given time will also fluctuate with differences in clinical program business hours across time zones. The following serves as a baseline estimate based on the sites outlined in PWS appendix C.

88 Mammography Sites x 7 average # workstations per site = 616 workstation connections.

3. We also request clarification on the expected annual storage volume per site for:

· imaging data;

· non-imaging MTRS data;

· local continuity storage;

· backup/retention storage.

If exact site-by-site numbers are not available, please advise whether offerors should use Government-provided planning assumptions or state their own assumptions in the proposal.

Response: Offerors should provide a national instance centralized server architecture and a national procedure volume of approximately 450,000 exams based on fiscal year 2025 data.

4. Please confirm that the Government’s unlimited-rights requirements apply only to custom code or deliverables first created specifically under the resulting contract.

Response: We confirm that the unlimited-rights requirement under this clause applies solely to custom code, modifications, or deliverables first produced specifically for the VA under the resulting contract. It does not extend to the Contractor's pre-existing commercial software, its underlying source code, or commercial improvements made independent of this contract, which remain governed by the applicable commercial software license terms.

5. Please confirm that the vendor’s pre-existing commercial software, source code, architecture, schemas, APIs, workflows, algorithms, dashboard logic, and other proprietary technology will remain vendor property and will be provided to VA under a software license rather than transferred to the Government.

Response: We confirm the vendor pre-existing commercial software, source code, architecture, schemas, APIs, workflows, algorithms, dashboard logic, and other proprietary technology constitute vendor proprietary commercial technology. This pre-existing technology will remain the property of the vendor and will be provided to VA under the vendor’s standard commercial software license.

6. Should offerors price the requirement as deployment across all 88 VHA mammography programs/sites? CS accepted Carolyn’s track changes which removed the vendor’s name.

Response: Yes, offerors should price requirements as deployment across all 88 VHA mammography programs/sites with each connecting to the national instance of the solution in accordance with the price schedule at Section B.5 in the RFP.

7. For each site, how many points of entry into the mammography tracking/reporting workflow should offerors account for? By points of entry, I mean the number of places where mammography-related records, images, reports, workflow updates, audit events, patient notification data, or compliance data can enter or be retrieved from the system.

Response:

· PWS Appendix C outlines the number of sites that have existing MTRS solutions whose historical records and reports will need to be ingested as part of data migration services. Other points of entry would include the Powerscribe API integration, HL7 notifications for ADT inbounds info, HL7 outbounds for reports, encapsulated PDF reports outbound, and DICOM/HL7 for lay letter outbounds.

· The solution will have active connections to both VistA/CPRS and Federal EHR through a DAS SPOE middleware integration point.

· Connection with AI solutions (such as density) should be included in the proposal with a future potential to connect with all 88 sites.

8. For each site, is the technical environment generally one centralized system connection, several smaller computer/system groups, or individual workstation-level connections?

Response: Individual workstation level connections to the national instance of the solution.

9. What annual mammography imaging storage volume per site should offerors use for pricing?

Response: Diagnostic Mammography imaging storage will be handled by the PACS solutions. Diagnostic mammography images will not be stored in the MTRS solution.

10. What annual non-imaging mammography data storage volume per site should offerors use for pricing?

Response: Since this will be a national deployment instance of the MTRS solution, a national benchmark of 450,000 exams for all 88 sites should be used once all sites are live. The base year 30 site implementation exam volume is estimated at 175,000.

11. Will the final solicitation provide standard assumptions or site-by-site ranges for points of entry, storage volumes, and technical connection architecture so vendor pricing can be consistent and comparable?

Response: The final PWS was updated. See Section 5.2.3(H) for points of entry, and technical connection architecture, and Section 5.3(K)(b) for storage volumes considerations.

12. What languages must patient letters and communication support?

Response: At a minimum, the MTRS solution shall have the capability to print patient lay summary letters in English and Spanish, see PWS Section 5.2.8(F).

13. Is there an expectation for a tool to automatically capture the density grade?

Response: The capability to automatically capture the density language and document in the MTRS is a requirement.

14. Will VA provide the test environment and network connectivity for building the interfaces?

Response: Yes, VA will provide the test environment and network connectivity for building the interfaces.

15. What FedRAMP level is required?

Response: No FedRAMP level is required to be eligible for award. Proposed solution must comply with all applicable VA policies and security authorization requirements:

1. NIST SP 800-53, Revision 5 (including updated controls in Rev 5.2.0);

2. VA Directive 6500, VA Cybersecurity Program, and VA Handbook 6500;

3. VA Handbook 6500.6, Appendix C (Contract Security), incorporated into the PWS as Addendum B;

4. VA Directive 6517, Risk Management Framework for Cloud Computing Services, applicable to any cloud-hosted components.

16. Should the system be hosted in VA's cloud (VAEC), vendor-hosted, or on-premise?

Response: This will depend on the vendor’s capability and offerings to deploy in either VAEC or on-premise. A final determination will not be made until the technical capabilities are reviewed and a selection is made. The Government will accept proposals for either VAEC-hosted or vendor, or on-premise hosted solutions, provided the offeror's technical proposal demonstrates the ability to meet all requirements under the selected hosting approach. Each offeror shall propose one hosting approach and submit a single price volume reflecting that approach. Offerors should not submit multiple pricing options for different hosting models; select the hosting approach that best reflects your capabilities and offerings, and price accordingly.

17. How many HL7 interfaces should we plan for per site?

Response: Each site will minimally have interfaces for ADT, ORM, and ORU. An HL7 interface for patient lay summary transfer to the EHR is also preferred. These will be coming from a single middleware HL7 integration point on the VA side. The vendor will need to have an HL7 integration engine to receive, parse, and manage site specific messaging accordingly.

18. Regarding the AI – 5-year score, is the expectation to run a score for each patient?

Response: Yes, the expectation is to run a score for each patient.

19. Is there an expectation that the awarded vendor would supply SQL licensing?

Response: Yes, as noted in the PWS section 5.3 the contractor shall provide turnkey licensing for all databases (e.g. SQL, Oracle) required for the MTRS deployment.

20. Regarding the price schedule. Does the VA expect to make monthly or annual payments?

Response: Invoice shall be submitted in accordance with the B.5 Schedule of Supplies and Services. Payments will be made accordingly.

21. What award/start date should we assume for pricing?

Response: The date of award is the start date. September 2026.

22. Will the Government provide the fillable templates referenced in the instructions with the formal RFP — the Price Exhibit / B.5 Schedule of Supplies and Services.

Response: Offerors must complete the Schedule of Supplies and Services.

23. Do the required screenshots and capability statements count toward that page limit?

Response: Response: The required screenshots or appropriate documentation is a part of the technical approach and shall count toward that page limit.

24. Are vendors required to submit VIA the portal, or can these volumes be submitted VIA email?

Response: Proposal shall be submitted via email and in accordance with the solicitation submission instructions.

B. The RFP response date and time of August 20, 2026; 09:00:00 AM Eastern Time, is unchanged.

C. All terms and conditions of RFP 36C10B26R0035, remains unchanged and in full force and effect Page 1 of Page 1 of