36C24921Q0641.docx

36C24921Q0641

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

DUNS:

DUNS+4:

PHONE:

FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER 18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA

26. TOTAL AWARD AMOUNT (For Govt. Use Only) 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA

ARE

ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER) 30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

36C24921Q0641 09-18-2021 Shawn Hendricks 615-225-6409 09-22-2021

2PM

CDT

90C Department of Veterans Affairs Network Contracting Office 9 1639 Medical Center Parkway Suite 400 Murfreesboro TN 37129 X 541519 $30 Million Net 30 N/A X Department of Veterans Affairs VISN 9 VA Medical Centers 1639 Medical Center Pkwy Suite 400 Murfreesboro TN 37129 90C Department of Veterans Affairs Network Contracting Office - 9 1639 Medical Center Parkway Suite 400 Murfreesboro TN 37129

FSC e-Invoicing Payment http://www.fsc.va.gov/fsc/einvoice.asp Invoice Setup Information 1-877877-48948 Invoice must be submitted electronically Setup 1-877-489-6135 See CONTINUATION Page See CONTINUATION Page X Shawn Hendricks Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR:

b. GOVERNMENT: Contracting Officer 36C249 Shawn Hendricks Department of Veterans Affairs Network Contracting Office 9 1639 Medical Center Parkway Suite 400 Murfreesboro TN 37129

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

3. INVOICES: Invoices shall be submitted in arrears:

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of Payment Requests.

FSC e-Invoicing Payment http://www.fsc.va.gov/fsc/einvoice.asp Invoice Setup Information 1-877877-48948 Invoice must be submitted electronically ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

36C24921Q0641

Page 1 of Page 1 of Page 1 of Page 1 of

STATEMENT OF WORK

DEPARTMENT OF VETERANS AFFAIRS

VHA VISN 9 CLINICOMP|EHR EXPANSION

PRODUCT DESCRIPTION

Background CliniComp|EHR is a complete system for house-wide charting that extends the continuum of care while offering unparalleled reliability for acute, critical, and emergency care with medical device integration. This integrated solution offers an adaptable & scalable Service Oriented Architecture (SOA) platform that can connect to new or legacy systems.

VISN 9 currently utilizes the CliniComp|EHR system for patient care documentation in the critical care units, step down units and COVID units at the Lexington, Louisville, Memphis, Mountain Home, Murfreesboro and Nashville VA Medical Centers. The CliniComp|EHR system is fully integrated with the VistA/CPRS Patient Record System at all sites utilizing the DSS DataBridge and DSS VSOA solutions.

The existing CliniComp|EHR system within VISN 9 has proven to be robust and reliable, providing exceptional compatibility with medical devices and other medical systems. In addition, the existing CliniComp solution has provided VISN 9 with a 99.99% hardware and software availability with no scheduled or unscheduled downtime over the last five years.

Requirements The Department of Veterans Affairs VA Medical Centers within VISN 9 require expansion of the CliniComp|EHR system for patient documentation in Post Anesthesia Care Unit (PACU), ProceduralCare Areas, and Emergency Department. This requirement shall include installation and implementation of CliniComp software, proprietary hardware such as the Universal Data Acquisition System (UDAS) and associated cables, all associated interfacing with DSS DataBridge and DSS VSOA, as well as all system and end user application configurations. This requirement shall also include all licensing for software, server and use, face to face training for end users provided by the CliniComp clinical specialists and a minimum of one year warranty, maintenance and support services for all software and hardware provided.

To minimize costs, contractor shall use all existing CliniComp|EHR software, hardware, infrastructure and interfaces to the fullest extent possible. The contractor shall provide all upgrades to or replacement of existing CliniComp hardware and servers as required in support of the expansion. The VA shall be responsible for providing network data connections at the patient bedside and in network data closets.

Period of Performance The Contractor shall complete installation of the CliniComp|EHR expansion software and hardware at all VISN 9 sites within a 12-month base period from date of award. The expectation for sustainment of Warranty, Maintenance and Support after the base year is for the contractor to pro-rate as required and add this cost to the existing VISN 9 CliniComp support contract.

Place of Performance:

Efforts under this contract shall be performed at the following VA facilities:

Memphis, TN 38104

Mountain Home, TN 37684 Mailing Address:

P.O. Box 4000 Mountain Home, TN 37684

Louisville, KY 40206

Lexington, KY 40502

Nashville Campus 1310 24th Avenue South Nashville, TN 37212 IMPORTANT NOTE: TVHS is a dual campus site using a single instance of VistA to serve both Nashville and Murfreesboro with primary data center located at the Nashville campus.

Murfreesboro Campus 3400 Lebanon Pike Murfreesboro, TN 37129

Hours of Work All implementation services, system maintenance or repairs shall be performed during the normal working hours of 7:30 am – 4:00 pm, Central Time, (Monday through Friday, excluding Federal Holidays) unless it is identified as an emergency repair. If it is considered to be an emergency then the Contractor will provide an immediate response no greater than 1 hour by telephone upon receipt of this notification. The time to complete any emergency repair will be mutually agreed upon between the Contractor and the COR at the individual station. When required, the contractor shall coordinate a monthly maintenance window (not to exceed 4 hours) with each facility for remote operating system and application patching, as well as, database server maintenance. Included in routine system maintenance is the furnishing and installation of all upgrades, version changes and/or updates to the system as further defined in the SOW/Specifications. Continual software updates and patches shall be included in order to keep the software components at the most current software releases and to include software feature requests. It is understood by the Contractor that the licensed software contains critical product functionality that must meet the minimum needs of the Government and is the basis for the Government’s procurement of the system. Consequently, the Contractor agrees that the Government has the right to successor products, software updates, version changes and upgrades at no additional cost provided the Government has exercised its option for renewal of the maintenance as previously defined herein. All maintenance services will be provided in a timely manner as further defined herein and in accordance with the Contractor’s customary practice.

Brand Name Hardware and Software The contractor shall provide expansion of CliniComp|EHR software, hardware and services to the specific clinical areas and in the quantities identified below for each VISN 9 site.

Implementation, Installation, Integration and Testing The Contractor shall review (with the Government), receipt of all contract line items for accuracy and completeness. The Contractor shall manage the installation of all equipment, parts, software, and software licenses to complete the receiving report and make the system operational as prescribed in this product description.

The Contractor shall integrate their solution with the existing CliniComp, Intl. CliniComp|EHR system.

The Contractor shall provide an Implementation Plan and schedule an implementation meeting within two (2) weeks of contract award. The Contractor shall identify specific deployment tasks and milestones in the Implementation Plan.

The Contractor shall deliver, install and configure the system to make it operational.

The Contractor shall provide solution testing.

The Contractor shall provide and maintain an accurate detailed Inventory List of the Contractor installed equipment and software including serial numbers, Equipment Entry (EE) Tag numbers, version release, and licenses.

Deliverables:

Implementation Plan Inventory List

CliniComp|EHR Implementation Requirements The Contractor shall ensure the CliniComp|EHR databases continue to be identical within each VAMC and across VISN 9. The CliniComp|EHR database and template modifications must be entered only once and immediately propagated throughout the hospital. The CliniComp|EHR databases and templates must be locked to prevent local modifications.

The Contractor shall continue to provide a mechanism(s) to prevent changes to flowsheet template and database elements that might be mandated by the VA nationally for purposes of standardization.

The Contractor shall ensure the ability to create new database elements, controlled at the national level, are maintained. Note: this must not prevent the ability to assign informational lines (e.g., specific templets or assessments), unique for the management of a specific patient, for use at the individual facility level and to be included in the patient’s permanent medical record.

The Contractor shall continue to provide the following implementation requirements:

Meet all VA security requirements as well as ensure data against system failures (disaster recovery) and user input or errors (audit trail).

A reliable and robust application able to survive network and server failures without loss of data or of real time data display.

Ensure CIS production and database server has redundancies for the hospital/national/IT region to include support for network failures.

The data extraction system for ALL clinical and administrative data in the CIS database must be capable of creating data extracts at least every 4 hours without degrading performance of CIS.

Real time data from patient monitors, infusion pumps, ventilators, assist devices and other devices that may transmit data must be stored and extracted from the CIS at frequencies independent of the display time period and, in no case, less than every 5 minutes, preferably at least once per minute.

CIS data must meet all VA nomenclature and standardization requirements. The CIS software must use the VA supplied data concepts including a unique Serial Number for each concept throughout the contact period. Data is updated as frequently as quarterly and must be 'installed automatically in CNVAMC within two (2) - four (4) weeks after delivery of the equipment.

All required interfaces shall use Health Level 7 (HL7) communications as well as Veterans Information Systems and Technology Architecture (VISTA) Broker Calls (APIs). The Contractor must extend the current HL7 communication network established in the critical care environment. The Contractor shall run a test script prior to go live implementation

CIS application must support remote view capabilities within and from outside hospital utilizing virtual private networks (VPN) and Citrix

One or more clinically active CIS records must be able to be viewed entirely by authorized users or administrators on remote, non-clinical workstations throughout the local area network (LAN). Access of CIS records by remote, non-clinical workstations must be via a browser-based application or a special viewing program.

All off-site performance monitoring of CIS hardware or software must satisfy VA Cyber-Security Requirements, the Administrative Simplification provisions of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and the provisions of The Privacy Act of 1974 and its Veterans Affairs applications.

Upgrades to the CIS server or workstation software that are accomplished by the manufacturer through remote access must satisfy VA Cyber-Security Requirements, preserve firewalls, and meet Enterprise Architecture Standards and VA security guidelines for virus protection. Software or hardware upgrades must not disrupt or alter a clinically active CIS record. An audit trail of all software changes must be maintained. All upgrades must be coordinated with Project Manager or COR.

CIS application must not interfere with VA approved programs (including the following)

BCMA

VISTA/CPRS

VISTA Imaging Clinical Note Templates Internet Browser Microsoft Offices Products Java/Active X-Plug Ins

SMS

McAfee Virus Scan ISS Proventia firewall Sentillion Vergence Locator Analytic Database

The CIS client application Microsoft Terminal Services or Citrix shall support remote viewing within the VA Firewall and via the One VA VPN.

An implementation program that is specifically designed for VA to leverage system knowledge and efficiencies

Device drivers to all VA medical devices for patient use in Endoscopy Unit, Dialysis Unit, PACU, Interventional Radiology, Cardiac Cath Lab and Same Day Procedural/Post Procedural Area must be capable of accepting all data, measured and calculated. These drivers must be available without additional cost.

Once properly accessed, CIS workstations must have the capability to toggle (foreground/background continuous functionality) between the CIS applications and the Computerized Patient Record System (CPRS).

Provide CIS applications in every clinical monitoring location of the Endoscopy Unit, Dialysis Unit, PACU, Interventional Radiology, Cardiac Cath and must interface with VISTA

CliniComp|EHR Applications must be able to be run on the typical VA workstation hardware. Any requirements that deviate from this standard must be clearly outlined. The Contractor shall submit a list of equipment required which will include the minimum requirement for the CIS and Interface Software to operate at an efficient level as intended. The list of this equipment (including estimated pricing for each individual item suggested) shall be provided.

CliniComp|EHR Network Requirements The Contractor shall ensure the CIS client application continues to run with a standard 100 Mbps full duplex network connection to the CIS server. The Contractor is required to submit with his/her signed proposal, a list of any additional network resources that are required for any associated CIS connection. The VA will provide all necessary network hardware to meet this connection speed.

The Contractor shall continue to provide the following network requirements:

A listing of port and protocols used by the CIS system.

The CIS software shall be able to be run on PC located on the hospital domain.

The CIS system shall be able to operate over a wide area network (WAN) with a T3 connection. The Contractor shall ensure that the CIS servers can operate from remote locations for decreased hardware maintenance.

The CIS software shall have ability to operate off a WAN link with common intra national network latencies of up to 30 milliseconds (mS) and VPN latencies of up to 100 mS

Ensure the CIS is able to survive network and server failures

Ensure CIS production and database servers have redundancies for the hospital/IT region/national level to include support for network failures.

CIS device drivers or other electronic communication means to all VA medical devices for patient use must be capable of accepting all data, measured and calculated.

Provide HL7 (or other) interfaces to Endoscopy Unit, Dialysis Unit, PACU, Interventional Radiology, Cardiac Cath Lab and Same Day Procedural/Post Procedural Area physiologic monitoring systems for VISN 07.

Provide connectivity for CareFusion Infusion Pumps, Critical Care Ventilators, IABP devices and Dialysis/ CVVH Machines for CNVAMC.

Provide allowance for additional medical devices interface as new equipment is identified for interfacing existing equipment/software identified herein for the CIS. These medical device interfaces shall be developed and provided at no charge to the CNVAMC upon request of the COR

Ensure applications collection data from medical devices shall run as a service or a daemon and shall not require a user to be interactively logged into the computer to collect the data.

CliniComp|EHR to VISTA Interfaces The Contractor shall continue to provide interfaces that solve the problem of electronic documentation, continuum of care, advance clinical access, and clinical workflow in critical care areas. The interfaces shall exchange data bi-directionally between VISTA/CPRS and CIS applications. The interface is a key element in the creation of an electronic medical record for the critical care areas.

The Government will furnish the appropriate interfaces to operate on the VISTA systems. These interfaces are referred to as the VISTA-side interfaces. That is, they provide only one half of the interface requirements. The Contractor shall be responsible to provide the other half, (the vendor-side) as part of this contract. The Contractor shall coordinate the above with the COR and shall work with either VA staff and/or third party contractors to make a successful connection and transfer of data with the VISTA system through the Government provided interface.

For this particular contract and the products being acquired, the VISTA-side interfaces have been developed by a third party. That company is Document Storage Systems (DSS), 12575 US Hwy 1, Suite 200, Juno Beach, FL 33408, 561-227-0207.

CliniComp|EHR Integration Requirements The functional integration requirements needed to meet VHA requirements are listed below. The VA-side of the VISTA interface will be provided to the Contractor. The Contractor shall perform quality assurance testing, of the CIS interface, within the VISTA testing environment prior to go live.

CliniComp|EHR Integration Interface Components The Contractor shall ensure the CliniComp|EHR system continues to provide single sign-on source for all vendors using the VA master list permitting clinical users access to a CIS using only VA passwords.

The CliniComp|EHR system shall continue to provide the following integration interface components:

Enable Users to sign-on to CIS using their VISTA access/verify codes in a logon dialog box with asterisks (***) displayed for both codes. A separate authentication system is not maintained in the CIS for standard logons. A shadow list may be employed for use only when the network or CPRS is down utilizing VA security standards. All changes in VA access/verify codes must be used immediately for subsequent CIS authentications.

A successful logon through VISTA returns the user’s VISTA credentials to the CIS, to include user name, user class, title, service, CIS administrator.

The user group credentials shall determine the users’ privileges within the CIS. The CIS application shall allow creation of a “user group” and assign user groups specific levels of CIS access, such as 'read/write', 'read-only', specific template access privileges.

The VISTA interface determines the user group using “rules” based upon the user’s keys, title, and/or ASU user class. Each site must also create keys matching the CIS user group name.

Rules defining user groups are included with this interface.

If the logon is unsuccessful, the user may not gain further access to the application. (Logons shall be limited to a fixed number of failed attempts, e.g., <10.)

A temporary ‘work around’ must become available to allow users to logon only if network access is not available. As soon as the network is available—and it is feasible clinically—user must logon to the CIS by the standard method.

Electronic Signature data shall be received by CIS to allow provider signing in CIS, including notes and records signed in CIS prior to sending to VISTA.

CliniComp|EHR Patient Selection / Registration in CIS The Contractor shall ensure the CliniComp|EHR system continues to accurately select individual patients and send patient specific information to the CIS with updates triggered by the CIS and VISTA as necessary. VISTA identity management procedures are maintained and extended within the CIS.

The CliniComp|EHR system shall continue to provide the following patient selection/registration capabilities:

Patients shall be selected from within CIS by multiple methods including the following: from a list in CIS, which must be updated contemporaneously from Admit, Discharge, Transfer (ADT) messages or poling the Surgery Schedule when appropriate, utilizing a graphical user interface (GUI) similar to CPRS patient selection (e.g., initial + “last 4 SSN”, Teams, wards), scanning patient’s barcode, when it becomes available and a ‘John Doe’ option permitting use of the CIS without first requiring patient registration in VISTA Patient identification information consists of multiple identifiers and the CIS patient identification process must meet VA standards (ENTR888 and ENTR942: vendor transactions/messages from or to VISTA shall be capable of including the source identifiers within all messages that exchange data with other VHA systems.)

Upon registration of a valid patient in the CIS, the patient information will be sent to CIS triggered by multiple events including query from CIS, ADT message, surgery schedule message or patient information update. The patient information, to be updated in CIS, shall include patient identification identifiers, patient demographics, Code Status, CWAD, bed location, treating specialty.

New messages to CIS are sent for updates to the patient data stored when Master Patient Index (MPI) updates data in VISTA. CIS must update its database with the new data contemporaneously.

CWAD (Clinical Warnings and Advanced Directives) will accompany patient registration/ADT messages, as well as provide a ‘re-send message’ trigger when information is updated. If Patient Record Flags (Category 1 and 2) exist in VISTA, transmit to CIS for display including any changes/updates during that episode of care.

For each patient, CIS must accept hospital specific team names, Unit locations (e.g., bed names) and treating specialty names, (e.g., PACU, Dialysis) to correctly identify patient locations and clinical provider groups/teams.

Procedures must be included to allow the emergent, manual entry of patient demographics entered into the CIS prior to Registration through ADT in VISTA. Easy identification and resolution of any differences once VISTA registration is accomplished must be facilitated by CIS.

There must be a simple, reliable method to retroactively match duplicate identities stored within both systems with ‘John Doe’ or incorrect patient assignments to prevent the creation of duplicate patient records in CIS.

Implementation Training The Contractor shall provide onsite technical and administrative training on the use of the CliniComp|EHR system. Contractor shall ensure a training schedule is provided to maximize staff participation of the PACU, ASC, Cardiac Cath, Endoscopy, Interventional Radiology and Dialysis staff. The Contractor shall provide a written material (i.e., manuals, handbook, training manual) to ensure user competency of the CliniComp|EHR system. The Contractor shall provide CliniComp|EHR training for approximately 54 beds on-site at the Charlie Norwood VA Medical Center as shown below:

Training shall provide skills and knowledge to effectively navigate the system, navigate security features, major applications, document clinical notes, identify and utilize workflow processes, understand content and flow of data as well as understand all function of the CliniComp|EHR system

Training System Administrators (2), Bio Medical Engineers (2) and Super Users (6) on how to operate and administer the CliniComp|EHR system.

Details are as follows:

Two (2) days for Super User training (16 hours) One (1) day for System Administrator training (8 hours) Four (4) days for end user (32 hours)

Maintenance The Contractor shall provide annual maintenance and repair services that include unlimited, perpetual, non-exclusive software and interface licenses for all interventional and critical care areas including Post Anesthesia Care Unit (PACU), Emergency Department (ED), Gastroenterology (GI), Endoscopy, Dialysis, Pain Clinic and Cardiac Catheterization Laboratory (Cath Lab) CIS software excluding; installation and implementation.

The Contractor shall provide a toll-free help desk phone number for CliniComp|EHR service related issues. This includes a telephone line operating 24 hours x 7 days x 365 days for VA customers for all service requirements.

The Contractor shall provide a call back response to the customer POC within one (1) hour of the original contact when contacted. The Contractor shall establish a service direct ticket for call resolution activities subsequent to calling the customer back.

The Contractor shall provide remote and on-site hardware and software maintenance support for PACU, ED, GI, Dialysis, Pain Clinic and the Cath Lab.

Hardware Maintenance – The hardware maintenance support shall cover all hardware including the server and UDAS provided by the Contractor. In the event of component failure, the Contractor shall determine the cause of the failure and execute repairs. For serviceable components, the Contractor shall correct the failure and return the system to operation within two (2) days. Unserviceable components shall be replaced and operational within two (2) business days.

Software Maintenance - The software maintenance support shall include, at a minimum, support for installation of manufacturer software releases as well as all software upgrades, updates, and manufacturer released security patches and maintenance of licensing integrity. Security patches shall be installed within four (4) business days of vendor issuance.

The Contractor shall provide annual maintenance and repair services as defined above. Option renewal period shall commence upon expiration of the warranty as defined herein. Services performed without this approval will be provided at no cost to the government.

Hardware and Software Warranty The Contractor shall provide a 90 day warranty beginning on implementation (go live) date. All items on the quote including software shall be covered by a 90 day warranty with Keep Your Hard Drive. The warranty shall include both licenses and hardware replacement with a 24 hour 7 day per week, and a 1 hour call-back response time service level agreement.

The Contractor shall provide VA packages (either on compact disk (CD) or downloadable) of required updates and new releases, to maintain hardware stability and supportability for 90 days beginning on implementation (go live) date. The deliverable shall include a description of the update, with version numbers, and any required ordering of the updates plus a link to the download and instructions for installation.

The Contractor shall provide a hard drive retention service whereby VA maintains control over these devices, regardless of condition, to ensure the security of VA sensitive data and components.

SECTION 508

NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL ELECTRONIC AND INFORMATION TECHNOLOGY PROCUREMENTS

On August 7, 1998, Section 508 of the Rehabilitation Act of 1973 was amended to require that when Federal departments or agencies develop, procure, maintain, or use Electronic and Information Technology, that they shall ensure it allows Federal employees with disabilities to have access to and use of information and data that is comparable to the access to and use of information and data by other Federal employees. Section 508 required the Architectural and Transportation Barriers Compliance Board (Access Board) to publish standards setting forth a definition of electronic and information technology and the technical and functional criteria for such technology to comply with Section 508. These standards have been developed and published with an effective date of December 21, 2000. Federal departments and agencies shall develop all Electronic and Information Technology requirements to comply with the standards found in 36 CFR 1194.

Section 508 – Electronic and Information Technology (EIT) Standards:

The Section 508 standards established by the Architectural and Transportation Barriers Compliance Board (Access Board) are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure Electronic and Information Technology (EIT). These standards are found in their entirety at: http://www.section508.gov and http://www.section508.gov/acquisition-regulations. A printed copy of the standards will be supplied upon request.

The Contractor shall comply with the technical standards as marked:

Equivalent Facilitation Alternatively, offerors may propose products and services that provide equivalent facilitation, pursuant to Section 508, subpart A, §1194.5. Such offerors will be considered to have provided equivalent facilitation when the proposed deliverables result in substantially equivalent or greater access to and use of information for those with disabilities.

Compatibility with Assistive Technology The Section 508 standards do not require the installation of specific accessibility-related software or the attachment of an assistive technology device. Section 508 requires that the EIT be compatible with such software and devices so that EIT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

Acceptance and Acceptance Testing Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the identified Section 508 standards’ requirements for accessibility and must include final test results demonstrating Section 508 compliance.

Deliverables should meet applicable accessibility requirements and should not adversely affect accessibility features of existing EIT technologies. The Government reserves the right to independently test for 508 Compliance before delivery. The Contractor shall be able to demonstrate 508 Compliance upon delivery.

Automated test tools and manual techniques are used in the VA Section 508 compliance assessment. Additional information concerning tools and resources can be found at http://www.section508.va.gov/section508/Resources.asp.

Deliverable:

Final Section 508 Compliance Test Results

INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS

The Contractor shall comply with Sections 524 and Sections 525 of the Energy Independence and Security Act of 2007; Section 104 of the Energy Policy Act of 2005; Executive Order 13514, “Federal Leadership in Environmental, Energy, and Economic Performance,” dated October 5, 2009; Executive Order 13423, “Strengthening Federal Environmental, Energy, and Transportation Management,” dated January 24, 2007; Executive Order 13221, “Energy-Efficient Standby Power Devices,” dated August 2, 2001; and the Federal Acquisition Regulation (FAR) to provide ENERGY STAR®, FEMP designated, low standby power, and Electronic Product Environmental Assessment Tool (EPEAT) registered products in providing information technology products and/or services.

The Contractor shall ensure that information technology products are procured and/or services are performed with products that meet and/or exceed ENERGY STAR, FEMP designated, low standby power, and EPEAT guidelines. The Contractor shall provide/use products that earn the ENERGY STAR label and meet the ENERGY STAR specifications for energy efficiency. Specifically, the Contractor shall:

Provide/use ENERGY STAR products, as specified at www.energystar.gov/products (contains complete product specifications and updated lists of qualifying products).

Provide/use the purchasing specifications listed for FEMP designated products at www.femp.energy.gov/procurement. The Contractor shall use the low standby power products specified at http://energy.gov/eere/femp/low-standby-power-products.

Provide/use EPEAT registered products as specified at www.epeat.net. At a minimum, the Contractor shall acquire EPEAT® Bronze registered products. EPEAT registered products are required to meet the technical specifications of ENERGY STAR, but are not automatically on the ENERGY STAR qualified product lists. The Contractor shall ensure that applicable products are on both the EPEAT Registry and ENERGY STAR Qualified Product Lists. N/A

The Contractor shall use these products to the maximum extent possible without jeopardizing the intended end use or detracting from the overall quality delivered to the end user.

The following is a list of information technology products for which ENERGY STAR, FEMP designated, low standby power, and EPEAT registered products are available:

Computer Desktops, Laptops, Notebooks, Displays, Monitors, Integrated Desktop Computers, Workstation Desktops, Thin Clients, Disk Drives Imaging Equipment (Printers Copiers, Multi-Function Devices, Scanners, Fax Machines, Digital Duplicators, Mailing Machines) Televisions, Multimedia Projectors

This list is continually evolving, and as a result is not all-inclusive. N/A

Notes to the Contracting Officer

SCHEDULE FOR DELIVERABLES

Due 14 days after contract award Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

Due 35 days after contract award Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

Due on first day of training Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

Due 5 days after testing is completed Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

INFORMATION SECURITY CONSIDERATIONS:

The Assessment and Authorization (A&A) requirements do not apply and a Security Accreditation Package is not required.

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

A prohibition on unauthorized disclosure: “Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA.” See VA handbook 6500.6, Appendix C, paragraph 3.a.

A requirement for data breach notification: Upon discovery of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the contractor/subcontractor has access, the contractor/subcontractor shall immediately and simultaneously notify the COR, the designated ISO, and Privacy Officer for the contract. The term “security incident” means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. See VA Handbook 6500.6, Appendix C, paragraph 6.a.

A requirement to pay liquidated damages in the event of a data breach: “In the event of a data breach or privacy incident involving SPI the contractor processes or maintains under this contract, the contractor shall be liable to VA for liquidated damages for a specified amount per affected individual to cover the cost of providing credit protection services to those individuals.” See VA handbook 6500.6, Appendix C, paragraph 7.a., 7.d.

A requirement for annual security/privacy awareness training: “Before being granted access to VA information or information systems, all contractor employees and subcontractor employees requiring such access shall complete on an annual basis either: (i) the VA security/privacy awareness training (contains VA security/privacy requirements) within 1 week of the initiation of the contract, or (ii) security awareness training provided or arranged by the contractor that conforms to VA’s security/privacy requirements as delineated in the hard copy of the VA security awareness training provided to the contractor. If the contractor provides their own training that conforms to VA’s requirements, they will provide the COR or CO, a yearly report (due annually on the date of the contract initiation) stating that all applicable employees involved in the VA’s contract have received their annual security/privacy training that meets VA’s requirements and the total number of employees trained. See VA Handbook 6500.6, Appendix C, paragraph 9.

A requirement to sign VA’s Rules of Behavior: “Before being granted access to VA information or information systems, all contractor employees and subcontractor employees requiring such access shall sign on annual basis an acknowledgement that they have read, understand, and agree to abide by VA’s Contractor Rules of Behavior which is attached to this contract.” See VA Handbook 6500.6, Appendix C, paragraph 9, Appendix D. Note: If a medical device vendor anticipates that the services under the contract will be performed by 10 or more individuals, the Contractor Rules of Behavior may be signed by the vendor’s designated representative. The contract must reflect by signing the Rules of Behavior on behalf of the vendor that the designated representative agrees to ensure that all such individuals review and understand the Contractor Rules of Behavior when accessing VA’s information and information systems.

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

Lexingotn VAMC - PACU CliniComp\F\EHR System as a Service (SYaaS) Solution \F\ includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year Contract Period: Base POP Begin: 09-27-2021 POP End: 09-26-2022

Lexingotn VAMC - Procedural Care Areas CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Lexingotn VAMC - Emergency Department CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Louisville VAMC - PACU CliniComp\F\EHR System as a Service (SYaaS) Solution \F\ includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Louisville VAMC - Procedural Care Areas CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Louisville VAMC - Emergency Department CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Murfreesboro VAMC - PACU CliniComp\F\EHR System as a Service (SYaaS) \F\ Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Murfreesboro VAMC - Emergency Department CliniComp\F\EHR System as a \F\ Service (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Nashville VAMC - PACU CliniComp\F\EHR System as a Service (SYaaS) Solution \F\ includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Nashville VAMC - Procedural Care Areas CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

Nashville VAMC - Emergency Department CliniComp\F\EHR System as a Service \F\ (SYaaS) Solution includes software licensing for Clinical Documentation, Data Acquisition, Interfaces, and Reporting within the PACU, Procedural Care Areas, and Emergency Department units. CliniComp, Intl. will provide all the hardware and software necessary to support the expanded use of the existing system. POP: Base Year

VISN 9 CLINICOMP|EHR EXPANSION

SECTION C - CONTRACT CLAUSES

IT CONTRACT SECURITY

VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

1. GENERAL

Contractors, contractor personnel, subcontractors, and subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.

2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS

a. A contractor/subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees, subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.

b. All contractors, subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for contractors must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures.

c. Contract personnel who require access to national security programs must have a valid security clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.

d. Custom software development and outsourced operations must be located in the U.S.