P02 RFI 36C10B25Q0290 A0003.pdf

PDF 190 KB Posted

Attached to
6515--Mammography Tracking System
Solicitation number
36C10B25Q0290
Issued by

About this file

This document is an Amendment (Amendment 0003) to a Request for Information (RFI) for a Department of Veterans Affairs (VA) Mammography Tracking System. The amendment contains seven detailed questions and responses from potential vendors, addressing technical requirements such as system integration capabilities, AI software compatibility, data exchange methods, and procedural volumes. Key technical details include the system's need to support cross-coverage across multiple VA sites, ability to receive multiple HL7 feeds, integration with external AI systems like cancer detection and clinical decision support software, and compatibility with various electronic health record systems.

The RFI indicates the VA is seeking a mammography tracking system with specific requirements, targeting an anticipated volume of 300,000 exams across 57 sites. The system must support complex functionality including demographic updates, third-party AI software integration, reporting capabilities, and potential multi-instance deployment with configurable user access. Vendors are asked to provide detailed responses about their solution's technical capabilities, integration methods, security protocols, and pricing models, with responses due by 10:00 am EST on May 14, 2025. The opportunity is set aside for Service-Disabled Veteran-owned small businesses (SDVOSBs) or Veteran-owned small businesses (VOSBs).

View the file

Other files

File Type Posted
P02 RFI 36C10B25Q0290 A0004.pdf PDF
P02 RFI 36C10B25Q0290 A0002.pdf PDF
P02 RFI 36C10B25Q0290 A0001.pdf PDF
P02 RFI 36C10B25Q0290 A0002.pdf PDF
36C10B25Q0290.docx DOCX document
P02 RFI Draft PWS.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

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 2

0003 05-13-2025

VA-25-00073499

36C10B

Department of Veterans Affairs

Office of Procurement, Acquisition, and Logistics

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

36C10B

Department of Veterans Affairs

Office of Procurement, Acquisition, and Logistics

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

To all Offerors/Bidders

36C10B25Q0290

X

X X

See Continuation Pages

Brett Schwerin

Contracting Officer

RFI: 36C10B25Q0259

Amendment 0003

CONTINUATION PAGE

The purpose of this amendment is to provide the following questions and responses to industry:

Question 1:

I understand that for those VA facilities that do not perform mammography and send the patients to outpatient clinics there are about 1,200 of these facilities. I also understand that those VAs that do send their patients out are required to send results of the patient’s procedure despite not performing the procedure. Would this proposal include tracking statistics and generating result (and potentially recall/reminder) letters for these outside clinics?

Response:

The functionality of having non-VA private institutions sending tracking statistics and results back to the VA’s mammography tracking system are outside the scope of this

RFI.

In this scenario outside institutions would send the lay letter to the patient and results will be sent to the VA through broader exchange platforms.

Question 2:

In accordance with (IAW) RFI Section II. Requirement, Section C.

“Can your solution be deployed in multiple instances while also allowing providers access to view patients and studies not on their instance of the solution?”

Is this question asking if our system has the capability to allow the patient’s referring physician to see their patients’ exams and outcomes, or is this asking about the radiologists being able to see the studies?

Response:

This question is geared towards cross coverage and remote read flexibility to access data/information assuming there are several instances of the MTS solution deployed across the country. Essentially can users in region A see data from region B if they have two separate deployments of the same MTS system. Also, we would be interested to hear if there are ways to set permissions based on role (i.e. view only vs. clinical cross read vs. business analytics).

Question 3:

IAW Draft PWS Section D. Clinical Functionality, Section 1 Patient Registration, d.

Ability to receive demographic updates from DEERS and other external systems.

How does DEERS communicate with outside applications, is it HL7?

Response:

DEERS communicates with the mammography tracking system via HL7 and is only applicable for Oracle Health Millennium sites.

RFI: 36C10B25Q0259

Amendment 0003

Question 4:

IAW Draft PWS Section D. Clinical Functionality, Section 2, Reporting, m. Ability for the product to integrate with third (3rd) party AI software systems

Please elaborate on what AI systems this is referring to as there are many AI systems.

Also please describe what is expected when this states “Integrate with”, what is that functionality?

Response:

The scope of interest includes on AI systems includes:

a. Cancer detection (Transpara Breast Care)

b. Clinical decision support

c. Breast density quantitation (i.e. Densitas Health DensityAI)

d. Positioning software feedback

We are interested AI software that could integrate with the mammography tracking software for both clinical documentation and business analytic use cases.

Question 5:

Our pricing model heavily takes annual breast procedural volume into account. What is the expected/forecasted volume for this combined system?

Response:

The anticipated volume is 300,000 exams across 57 sites.

Question 6:

Would each VA facility have their own separate HL7 feed into the system or would that traffic be sent to an interface engine that would then send a single feed?

Response:

We are currently exploring this, and it is unclear right now whether the VA can support an interface engine that would take disparate HL7 feeds and send a single feed to MTS.

For RFI response purposes, please indicate whether your solution can receive multiple HL7 feeds and if there is a limit to how many.

Question 7:

Please provide a current MDS2 form, the most current document I have is from 2014.

Response:

The latest version of the MDS2 can be found at the NEMA standards link https://www.nema.org/standards/view/manufacturer-disclosure-statement-for-medical-device-security https://www.nema.org/standards/view/manufacturer-disclosure-statement-for-medical-device-security https://www.nema.org/standards/view/manufacturer-disclosure-statement-for-medical-device-security

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