S02 36C26027Q0023 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 4

0001 08-27-2026

648-27-1-4083-0003

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

36C26027Q0023

08-12-2026

X

X X

648-3670152-4083-840900-2580 0100431T2 one (1)

The purpose of this amendment is to answer questions received. Questions will appear in black font. Answers will appear in red font. Please see continuation page for details.

Jennifer Robles Contracting Officer

VA-VHA-RPOW-2023-0015

A.1 QUESTIONS AND ANSWERS FOR SOLICITATION 36C26027Q0023

1) Question: Brand Name or Equal & Data Ingestion Specifications: For offerors proposing an "equal" solution, could the Government provide the technical specifications, API documentation, or data export formats currently utilized by Oregon Health & Science University (OHSU) and VA Portland for Amion scheduling data exchange?

Answer: As stated under Scope in the Statement of Work, Oregon Health and Science University utilizes AMiON ENTERPRISES. Any proposed system must be compatible and fully integrate with AMiON ENTERPRISES. Additionally, the Statement of Work requires:

Verification of Capability to Integrate with Amion

Offerors shall provide written verification confirming that their proposed solution can fully integrate with Amion provider scheduling software. Verification must include:

• Technical description of the integration method (API, interface, data import, or other mechanism).

• Confirmation that the solution can successfully - in real-time - ingest, refresh, and utilize Amion scheduling data as used by VA and OHSU.

Previously Verified Solution via Contract

Offerors shall provide documentation demonstrating previously verified, contract-based performance integrating with Amion. This must include:

• Identification of prior contract(s) involving Amion integration.

• Description of services provided.

• Summary of how Amion data was used within the vendor’s platform.

• A point of contact capable of verifying past performance.

Mandatory Demonstration Requirement

Offerors shall provide a demonstration showing their system functioning with Amion scheduling data. Demonstration may include:

• A live system demonstration using real or test Amion data; or

• Evidence of a historically deployed Amion integrated solution.

• The demonstration must show successful ingestion, synchronization, mapping, display, and utilization of Amion scheduling data.

2) Question: OEM Authorization Letter Requirement (Section E.6 Part III): Can the Government clarify that the requirement to provide an OEM Authorized Distributor/Reseller letter applies specifically to third-party vendors quoting the brand name Amion software, and that offerors providing their own proprietary "equal" software product are exempt from providing a third-party OEM letter?

Answer: Offerors shall provide an authorization letter from the Original Equipment Manufacturer (OEM) that verifies vendor is an authorized dealer, authorized distributor, or authorized reseller for the proposed equipment/system. The letter should state that all software licensing, warranty and service associated with the equipment/system shall be in accordance with the OEM terms and conditions. If you are the OEM for your proposed equipment/system, your offer should state that.

3) Question: System Demonstration & Scheduling: Section E.6 references live demonstration requirements. Could the Government clarify the process and timeline for scheduling live demonstrations for offerors proposing equal solutions, or confirm whether documented evidence of historical deployment/synchronization satisfies this requirement?

Answer: In accordance with the Statement of Work, offerors shall provide a demonstration showing their system functioning with Amion scheduling data.

Demonstration may include:

• A live system demonstration using real or test Amion data; or

• Evidence of a historically deployed Amion integrated solution.

• The demonstration must show successful ingestion, synchronization, mapping, display, and utilization of Amion scheduling data.

In accordance with Section E.6, 5.1.4.3, if offer will include a live system demonstration using real or test Amion data, contact Contracting Officer Jennifer Robles at Jennifer.robles1@va.gov no later than 1pm Mountain, 08/25/2026 to schedule. Any live system demonstrations will be scheduled for the following week based on Government availability.

4) Question: Voice Communication / Vocera Integration: Regarding the requirement to integrate with voice-activated communication systems (e.g., Vocera), what specific integration interfaces/protocols (e.g., SIP, REST API, WCTP, SMTP) are currently active and supported by the VA Portland facility infrastructure?

Answer: In general, standard ports are 0 - 1023. Those are going to be pre-defined for specific protocols. Some are unsecure and blocked while others are open for specific use. 1024 and above are for specific vendors and would be used as part of VLANS and ACLs which is segmentation and rules about what information can go where. If there's remote access required from a vendor to perform support tasks, that would be a different port and protocol and controlled in the same manner.

Of the ones you listed above, SMTP is the only protocol and the default port for that is

25. The others are different functions and catch-all names. So, they would have significant variability based on what they do and what they interact with.

5) Question: Telecommunications & Cloud Security: Could the Government confirm whether FedRAMP authorization or a specific VA Technical Reference Model (VA TRM) approval level is required at the time of quotation submission, or if standard VA commercial SaaS security vetting applies upon award?

Answer: Scheduling software must be a Federal or Department of Veterans Affairs approved IT solution. Solutions may have existing FedRAMP authorization or approval through VA TRM alignment and VA’s standard security vetting (NIST SP 800 53 Rev 5, VA Directive 6500, VA Handbook 6500.6, and the VA ATO process).