36C25223Q0580 0001.docx

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 NUMBERE

D 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 amendmen t, 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) None 07-26-2023 695-23-2-133-2037 Department of Veterans Affairs

GLAC (69D)

115 South 84th Street, Suite 101 Milwaukee WI 53214-1476 Department of Veterans Affairs

GLAC-MILWAUKEE (69D)

Great Lakes Acquisition Center - HC 115 South 84th Street, Suite 101 Milwaukee WI 53214-1476 To all Offerors/Bidders

36C25223Q0580 07-26-2023

X X X August 7, at 10:00 am Local Time 695-3630160-133-825500-3131 0100555Y1 X one (1) Amendment to Solicitation 36C25223Q0580 for Cardiac (Telemetry and Bedside Monitoring) Documentation and Reporting Digital Solution for VISN 12 VA Medical Centers (see Solicitation for addresses). This amendment is for clarification of questions regarding the Statement of Work. Please see continuation page for responses.

The due date for quotes has not been extended. Quotes are still due on Monday, August 7, at 10:00 am Local (Central) Time.

Please ensure this signed amendment is included in your quote package to be considered for evaluation Ashley Johnson Contracting Officer Questions in Blue Answers in red

In regards to Section B.1 – Purchase Order Administration Data, Part 9 – SECURITY & PRIVACY CONTROL:

All contractor employees are subject to the same level of investigation as VA employees who have access to VA Sensitive Information. The level of background investigation commensurate with the level of access needed to perform in accordance with the statement of work is: Special Agreement Check (SAC) & National Agency Check with Inquiries (NACI). This requirement is applicable to all subcontractor personnel requiring the same access.

Please define VA Sensitive Information levels for this project.

Special Agreement Check (SAC) and Tier 1 National Agency Check with Inquiries (NACI) are the levels required for this project. Pricing is defined for these levels on page 4 and 5 of the solicitation.

In regards to B.2 – SOW, Part 3 – Standards/Requirements:

3.1. Integration Requirements

• Patient Monitoring o Integrate to all patient monitoring systems in VISN 12 to the patient monitoring vendors’ current software and current version

• Spacelabs Patient Monitoring is currently installed at VA Illiana Health Care System, but currently under contract for migration to GE

Does vendor need to scope both GE and Spacelabs for VA Illiana?

No, vendor only needs to scope to GE for Danville.

In regards to B.2 – SOW, Part 3 – 3. Standards/Requirements:

• Patient Monitoring o Integrate to all patient monitoring systems in VISN 12 to the patient monitoring vendors’ current software and current version

• Vendor must specifically highlight if additional procurements shall be needed for their integration

• For example, what servers, software, and/or licensing shall be required to make the integration functional

Please confirm VA will provide virtual servers. Please confirm Microsoft Licensing OS and SQL will be provided by VA Servers.

Confirmed – however the vendor shall provide documentation on server, OS, and SQL requirements to support their system within their response.

• Active Directory o Integrate to Active Directory for single sign on in accordance with the Personal Identity Verification (PIV) Compliance Playbook – see attachment AD-IWA in Section D

• Solution must be Single Sign On

• Single Sign On must be achieved using Integrated Windows Authentication (IWA) - see attachment AD-IWA in Section D o FHCC Department of Defense (DOD) employees have Common Access Card (CAC) cards rather than PIV cards

• Additional testing may be required to accommodate this distinction

Would VA be willing to allow for validation testing for this requirement?

VA is willing to do validation testing on all integrations, including IWA Active Directory integration for PIV Compliance. It is expected that these activities will be built into the project schedule supplied by the successful contractor.

3.3. Clinical Functionality Requirements

• Single sign on via active directory integration functional requirements:

o Roles and access shall be based on membership to active directory group

• i.e.) An Active Directory (AD) group in Milwaukee named VHAMIWTeleDocUsers, and a user must be part of that group to get User Level permissions in TeleDoc solution. Similar scenario for Admin Level role.

Please confirm TeleDocUsers an AD group versus a product?

Correct “TeleDocUsers” is an example of an Active Directory (AD) group. The purpose of this AD group is to contain users with a basic user level of permission. We can name the AD group whatever makes sense after go live.

3.8. Training and education

• 24 hours of on-premise end-user support during implementation

Please confirm total of 24 hours vs 24 consecutive hours.

During implementation (go-live), we need vendor support staff available on prem during each shift for support. Not necessarily 24 consecutive hours, but 24 total hours during go live that will cover each shift (1st, 2nd, and 3rd shift).

Is it required to provide smartphone access for waveform, event, and trended vitals visualization on hospital provided or personal smartphones?

Smartphones were not part of the requirements. If that functionality is available, please describe. Indicate whether that is included in your proposal or considered an add-on feature.

In a hypothetical scenario, they would use hospital provided cell phones that could operate on the VA network. Bring Your Own Device (BYOD) or utilization of any cloud components is out of scope and not desired.