S02 - 36C26223Q1635.pdf

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. UEI: EFT:

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. NOV 2021)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

See eCMS P01 documents

VISN wide requirement

36C26223Q1635 08-23-2023

Alvizar, Edgar 562-766-2244 09-06-2023

08:00 PDT

36C262 Department of Veterans Affairs Network Contracting Office 22 4811 Airport Plaza Drive Suite 600 Long Beach CA 90815

X 100

X

513210

N/A

X

N/A

Department of Veterans Affairs Veterans Integrated Network (VISN) 22 See Statatement of Work

36C262

Department of Veterans Affairs Network Contracting Office 22 4811 Airport Plaza Drive

Long Beach CA 90815

Financial Services Center See Statement of Work

See CONTINUATION Page

SOLICITATION FOR IMAGE SHARING SOFTWARE SYSTEM

PLEASE ENSURE THE FOLLOWING INFORMATION IS REFERENCED:

PRICE/COS SCHEDULE, SALIENT CHARACTERISTICS, AND ALL CLAUSES

ALL QUOTE MUST BE SUBMITTED TO EDGAR.ALVIZAR@VA.GOV

SEE INSTRUCTIONS TO OFFERORS

THIS IS A FIRM FIXED PRICE REQUIREMENT.

See CONTINUATION Page

See eCMS P01 (2237 documents)

X X

X 1

Cecil S Nichols

VA-VHA-2021-84859FDA

36C26223Q1635

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 STATEMENT OF WORK

B.2 PRICE/COST SCHEDULE

ITEM INFORMATION

B.3 DELIVERY SCHEDULE

B.4 TERMS AND CONDITIONS

B.5 ADMINISTRATIVE DATA

B.6 PERIOD OF PERFORMANCE

B.7 PERFORMANCE

B.8 OPTION TO EXTEND THE TERM OF THE BPA

B.9 AUTHORIZED LIMITS

B.10 OBLIGATION OF FUNDS

B.11 AUTHORIZED INDIVIDUALS

B.12 ORDER FORMAT

B.13 BPA EMPLOYEE IDENTIFICATION

B.14 AUTHORIZED REPRESENTATIVES

B.15 PRECEDENCE

SECTION C - CONTRACT CLAUSES

C.1 52.204-23 PROHIBITION ON CONTRACTING FOR HARDWARE, SOFTWARE,

AND SERVICES DEVELOPED OR PROVIDED BY KASPERSKY LAB AND OTHER

COVERED ENTITIES (NOV 2021)

C.2 52.204-27 PROHIBITION ON A BYTEDANCE COVERED APPLICATION (JUN

2023)

C.3 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)

C.4 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES (DEC 2022)

C.5 52.232-19 AVAILABILITY OF FUNDS FOR THE NEXT FISCAL YEAR (APR

1984)

C.6 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS (NOV

2018)

C.7 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.8 VAAR 852.201-70 CONTRACTING OFFICER'S REPRESENTATIVE (DEC 2022)

C.9 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (JUN 2023)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.212-1 INSTRUCTIONS TO OFFERORS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (MAR 2023)

ADDENDUM to FAR 52.212-1 INSTRUCTIONS TO OFFERORS—COMMERCIAL

PRODUCTS AND COMMERCIAL SERVICES

E.2 52.212-2 EVALUATION—COMMERCIAL PRODUCTS AND COMMERCIAL

SERVICES (NOV 2021)

E.3 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (DEC 2022)

E.4 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)

E.5 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB

1998)

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 STATEMENT OF WORK

PEER-TO-PEER IMAGE SHARING SYSTEM FOR VISN 22: VA Desert Pacific Healthcare Network

1. Background

1.1. The purpose of this contract is to provide VISN 22 with a peer-to-peer image sharing system (software) to include software, training, and support on a firm fixed price basis with four option years.

1.2. Image and report sharing systems deploy a proprietary peer-to-peer network that would give the United States Department of Veterans Affairs Hospitals the ability to electronically exchange data with the community. In so doing, imaging and report sharing systems would minimize delays in the delivery of care and reduce the operational costs associated with seeing a Veteran imaged outside of VA under the Mission Act. By using the unique peer-to-peer secure network technology provided by image and report sharing systems, the VISN 22 would be able to, in effect, retrieve the requested images from our community providers electronically, saving the time and cost of using courier services to transport the CD-ROMs to the Radiology File Room.

2. Objectives

2.1. The required software shall fulfill the agency need for peer-to-peer image sharing software and support whereby radiology images obtained at any VISN 22 facility may be shared with other VAMCs and/or community providers, likewise radiology images performed at other VAMCs and/or community providers may be shared with any VISN 22 VAMC. The system shall have high reliability and shall be hosted on a VA VISN 22 virtual machine environment.

3. Scope, Tasks, or Requirements

3.1. The general scope of the work the contractor shall perform is to supply comprehensive peer- to-peer image sharing software to include all training, and technical support.

3.2. The offeror shall sign a national VA Memorandum of Understanding and Interconnection Security Agreement.

3.3. The peer-to-peer network shall query multiple systems outside the VA (community care partners) to recognize imaging exams performed on any enrolled VA patient.

3.4. Professional services shall be provided to include customization and integration with third party medical devices and software as well as recruitment and set-up of networks with community- based partners.

3.5. VISN 22 Health Care Systems include:

3.5.1. VA Greater Los Angeles Healthcare System

3.5.2. VA Long Beach Healthcare System

3.5.3. VA Loma Linda Healthcare System

3.5.4. VA San Diego Healthcare System

3.5.5. Northern Arizona VA Health Care System

3.5.6. Phoenix VA Health Care System

3.5.7. Southern Arizona VA Health Care System

3.5.8. New Mexico VA Health Care System

3.6. The required services must integrate with VistA Imaging Importer, Agfa Commercial PACS, VistA Imaging, Computerized Patient Record System (“CPRS”), Laurel Bridges’ Compass DICOM router or any other DICOM router provisioned by the VA, and Cerner.

3.7. The acquired network services must ensure the VA can continue to save these images to Agfa Commercial PACS and to VistA Imaging. The acquired services must authenticate and validate bi-directional, electronic exchange of DICOM images, Radiology reports, and Radiology orders using a FIPS 140-2 validated cryptographic methodology or equal.

3.8. The service must allow the Radiology department to search the commercial imaging providers located within the VISN 22 service area, locate prior medical images and reports, and retrieve them to the VA.

3.9. In addition, the system must automatically match patient IDs to update the patient’s Medical Record Number (MRN) # with the VA’s MRN #, when possible. Further, the system must generate a non-VA order through VistA Imaging in CPRS and update the inbound studies with the VA accession number for reconciliation in Agfa Commercial PACS. In some cases, these studies may be stored through Compass DICOM Router.

3.10. The acquired system facilitates the exchange of medical images and reports through encrypted, peer-to-peer conduits between providers on a federated health information network by way of the FIPS 140-2 validated site-to-site connection or equal, as per Federal security requirements. The system provides enhanced automation which:

3.11. Utilizes an upcoming appointment, procedure, or community consult to automatically pre-fetch relevant images and reports from commercial or private sector imaging providers relevant to the upcoming care event.

3.12. Conducts patient matching to automatically match inbound data to an existing patient and generate an order to obtain a VA accession number.

3.13. Provides a method for non-VA providers to electronically request VISN22 images and reports.

3.14. Facilitates order generation and retrieval of results from community care providers, opposed to calling community care providers to track down patient results and wait on a fax.

3.15. Supports advanced integrations with DICOM, Fast Healthcare Interoperability, Resources (FHIR), Application Programming Interface (API), and Health level -7 (HL7) standards.

3.16. The service must allow the Radiology department to search the commercial imaging providers located within the VISN 22 service area, locate prior medical images and reports, and retrieve them to the VA where they can be inducted to VA systems. In addition, the system must automatically match patient IDs to update the patient’s MRN # with the VA’s MRN #, when possible. Further, the system must generate a non-VA order through VistA Imaging in CPRS and update the inbound studies with the VA accession number for reconciliation in Commercial PACS using a Class 2 interface deployed to each VistA Instance.

3.17. The service must deploy a network that gives the VHA the ability to bi-directionally exchange medical images and diagnostic reports with the community and there shall be no cost for private sector facilities to exchange images bi-directionally with the VA.

3.18. The service must have a fully functional search engine that gives the VA the ability to locate, access, and use medical images, reports even when the Care in the Community location is unknown. The patient query must use four-points of patient identification.

3.19. The service must allow for automated pre-fetch of prior images and reports from the Care in the Community facility or in advance of an upcoming appointment at the VA or during a care in the community consult.

3.20. When outside images and reports are received, the service must attempt to automatically find the correct patient in VistA/CPRS and reconcile the outside data with the correct Patient ID/MRN. If a distinct match is not found, the outside data can be held for manual review by staff in a worklist.

3.21. The service must automatically conduct searches of private sector facilities for relevant priors based on an upcoming appointment/procedure using an HL7 order (ORM) or scheduling (SIU) message from VistA.

3.22. The service must search private sector facilities on the Network for the patient, retrieve clinically relevant prior images and documents, reconcile the prior images, and store the prior images in VistA Imaging and Commercial PACS.

3.23. The service provider must be able and willing to pay for infrastructure and implementation costs at private sector facilities and should have policies and a history of performance with the VHA regarding covering the cost of private sector facility's hosting, HL7 integration, and DICOM connectivity.

3.24. The image sharing system shall maintain at all times 99.99% up time based on a 24/7/365 work schedule.

3.25. The service should be federated. The service should be able to at a minimum:

3.25.1. Broadcast queries to the community to locate VA patients’ prior images in the private sector.

3.25.2. Deploy a federated model meaning data sent from non-VA facilities (Care in the Community Providers) to the VA is sent through a secure conduit by way of a FIPS 140-2 validated connection with the VA TIC and the data is not stored or processed in a cloud or hosted environment.

3.25.3. The vendor should have capability and past performance regarding capability to route data internally using trigger events to ensure data is available where clinicians need it, for example, automated routing to a private sector facility should a Veteran’s care continue there.

3.25.4. The vendor should have past performance references for Patient Matching allowing the VA to update DICOM images and reports as they arrive from the private sector so the service can automatically add the information to the patient’s chart in CPRS and Jacket in Commercial PACS.

3.25.5. Electronic Requests should enable VA employees to request and search for patient information at facilities participating and not participating on the vendor’s Network.

3.25.6. The system must interoperate with other vendors that offer healthcare interoperability solutions.

4. Delivery Schedule: Implementation, configuration, and validation.

4.1. Upon award the contractor shall work with VISN 22 to establish a timeline for installation.

4.2. Implementation, configuration, and validation services shall be performed in an expeditious manner with minimal impact to the daily operations of the facility.

4.3. The Contractor shall implement, configure, and validate the required software within 90 days from Receipt of Award (ROA).

4.4. The cost of Implementation, configuration, and validation shall be included with the price of the required product license.

4.5. The effective date shall be changed via contract modification in order to align the start of 12-month license with the go-live date. The go-live date is the first day after the end of implementation, configuration, and validation.

4.6. Implementation is the process of integrating the required software into VALBHS organization's workflow; and shall achieve, as a minimum, communication among vendor and COR to identify user’s preferences, to install the application, migrate data and test various features, and customize the required product.

4.7. Configuration of the required product means selecting programmable options that make the program function to the user's preferences.

4.8. Software validation procedure is a process that confirms a piece of software is designed for and satisfies its intended purpose.

5. Government-Furnished Equipment and Government-Furnished Information

5.1. The VA-VISN 22 will furnish server space (virtual machine), electrical and environmentals as needed to meet the specifications of the vendor provided hardware.

5.2. The VA-VISN 22 will provide network infrastructure (speed and access will be governed by OI&T and may be subject to limitations), network security/isolation instructions and structure, IP and naming conventions, and other networking/security assistance and instruction as required for project implementation.

5.3. The VA-VISN 22 will furnish on-site administrative and hardware support as required but may be limited by availability of qualified on-site personnel.

6. Security

6.1. The image sharing system shall conform with all current VA required network and patient information security. It shall be the contractor’s responsibility to stay abreast of all current and future changes to this requirement.

6.2. The Contractor is required to assure all personnel working on or remotely servicing meet VA security requirements and have been vetted through the appropriate channels.

6.3. Remote connectivity and active system monitoring shall conform to VA requirements and shall be the responsibility of the contractor to monitor and maintain.

7. Place of Performance

7.1. This work shall be performed at a Government site, specifically at the VAMC facilities within the VA Desert Pacific Healthcare Network (VISN 22)

VA GREATER LOS ANGELES HEALTHCARE

SYSTEM (691)

11301 WILSHIRE BLVD

WAREHOUSE- BLDG 297

LOS ANGELES, CA 90073

VA LONG BEACH HEALTHCARE SYSTEM

(600)

5901 E 7th STREET

WAREHOUSE - BLDG 149

LONG BEACH, CA 90822

VA LOMA LINDA HEALTHCARE SYSTEM (605)

11201 BENTON STREET

WAREHOUSE – 1C05

LOMA LINDA, CA. 92357

VA SAN DIEGO HEALTHCARE SYSTEM (664)

335O LA JOLLA VILLAGE DR

WAREHOUSE BLDG 1

SAN DIEGO, CA 92161

PHOENIX VA HEALTHCARE SYSTEM (644)

(Carl T. Hayden VA Medical Center)

650 E Indian School Rd

PHOENIX, AZ 85012

TUCSON VA MEDICAL CENTER (678 -

Southern)

3601 S 6th Ave

TUCSON, AZ 85723

NEW MEXICO VA HEALTHCARE SYSTEM (501)

(Raymond G. Murphy VA)

1501 San Pedro SE

ALBUQUERQUE, NM 87108

Prescott ARIZONA VA HEALTHCARE SYSTEM (649 (Northern)

(Bob Stump VA Medical Center)

500 AZ 89 North

PRESCOTT, AZ 86313

7.2. Additional work may be performed at facilities owned by community partners.

8. Contractor’s Responsibility

8.1. Work shall be performed 365/24/7 with the goal of providing 99.99% up-time with minimal impact to normal hours of operation (M-F 0700-2200 hours).

8.2. Contractor shall provide qualified support personnel with familiarity and knowledge of VA network and security requirements.

8.3. The Contractor shall be responsible for all software and hardware updates and upgrades during the performance period of this contract.

8.4. The contractor is responsible recruiting, set-up, and maintenance of community partner network connections.

8.5. The Contractor shall provide services in accordance with ethical, professional, and technical standards of the health care industry.

9. Services Not Covered

9.1. Any work other than as specified in the contract shall be identified as a non-priced task, and if determined by the Contracting Officer to be within the overall scope of the contract, work shall be added by a modification to the contract.

9.2. Any work requested that is identified as outside the scope of the contract shall be addressed by the facility as a separate procurement.

10. Federal Holidays Observed By The VA

10.1. Holidays.

New Year's Day 1 January Labor Day 1st Mon. in Sept

M L King's Birthday 3rd Mon. in Jan Columbus Day 2nd Mon. in Oct

President's Day 3rd Mon. in Feb Veterans Day 11 November

Memorial Day Last Mon. in May Thanksgiving Day 4th Thurs. in Nov

Independence Day 4th of July Christmas Day 25 December

Juneteen

10.2. Also included would be any other day specifically declared by the President of the United States to be a National Holiday.

10.3. When a holiday falls on a Sunday, the following Monday shall be observed as a legal holiday by U.S. Government agencies. When a holiday falls on a Saturday, the preceding Friday shall be observed as a legal holiday.

11. Identification, Parking, Smoking, and VA Regulations:

11.1. The Contractor's FSEs shall wear visible identification at all times while on the premises of the VAMC. It is the responsibility of the contractor to obtain and pay for parking as may or may not be required. The VAMC does not guarantee on-site parking.

The VAMC will not invalidate or make reimbursement for parking violations or charges for the Contractor under any conditions. Smoking is prohibited inside any buildings at the VAMC and only in designated areas on campus. Possession of weapons is prohibited. Enclosed containers, including tool kits, shall be subject to search.

Violations of VA regulations may result in citation answerable in the United States (Federal) District Court, not a local district, state, or municipal court.

12. Orientation For Contractor Employees

12.1. Contractor shall attend an orientation meeting as arranged by the Contracting Officer’s Representative (COR) on-line or other written training may be substituted at the discretion of the COR. The VA will schedule this meeting and it will include discussion of the following topics: (VA will provide information to the contractor regarding these topics and will document the meeting)

12.2. The Contractor shall be responsible to ensure that Contractor employees coming to the work site will receive the information required below:

Fire and Safety

Infection control

Disaster procedures

12.3. The Contractor shall be responsible to ensure Contractor employees providing work on this contract are fully trained and completely competent to perform the required work.

13. Contractor Personnel Security Requirements:

13.1. All contractor employees who require access to the Department of Veterans Affairs' Contractors computer systems or have access to sensitive information shall be the subject of a background investigation. The contractor is encouraged to have its employee immediately download the background investigation packet from http://www.osp.va.gov/Security_and_Investigations_Center_FF.asp upon notification of contract award. A contractor’s employee shall not commence working at VA under contract until the Contracting Officer receives notification from the VA Office of Security and Law Enforcement that the contract employee’s application was received complete.

A favorable adjudication from the VA Office of Security and Law Enforcement must be received in order for a contractor employee to continue contract performance. This requirement is applicable to all subcontractor personnel.

13.2. Position Sensitivity - The position sensitivity has been designated as low risk.

13.3. Background Investigation - The level of background investigation commensurate with the required level of access is National Agency Check with Written Inquiries (NACI).

13.4. Contractor Responsibilities

13.4.1. The contractor shall bear the expense of obtaining background investigations. If the Office of Personnel Management (OPM) conducts the investigation, the contractor shall reimburse VA within 30 days. If timely payment is not made within 30 days from date of bill for collection, then VA shall deduct the cost incurred from the contractor’s 1st month’s invoice(s) for services rendered.

13.4.2. It is imperative for the contractor to provide, at the request of VA, a listing of contractor personnel performing services under the contract in order for the background investigation process to commence. This list will include name (first, middle, last) social security number; date of birth; city, state, and country of birth.

13.4.3. The contractor or their employees shall submit a complete background investigation packet. Additional guidance and information in completing the required forms, and examples of the forms, can be found at http://www1.va.gov/VABackground_Investigations/page.cfm?pg=2.

http://www.osp.va.gov/Security_and_Investigations_Center_FF.asp http://www1.va.gov/VABackground_Investigations/page.cfm?pg=2

13.4.4. All contractor employees and subcontractors are required to complete VA’s Privacy training annually. All Contractor employees and subcontractors requiring access to VA computer network are required to complete Cyber Security training courses annually either on-line or hard copy. Documented proof must be provided to the Contracting Officer.

13.4.5. The contractor shall notify the COR immediately when their employee(s) no longer require access to VA computer systems.

14. Security Training

14.1. Due to the increased emphasis on privacy and information security, the following special contract requirements are established and hereby made part of the contract entered into with the Department of Veterans Affairs.

14.2. Privacy Training: Contractor and their sub-contractors assigned work under the contract are required to receive annual training on patient privacy as established by HIPAA statues. Training must meet VHA’s and the Department of Health and Human Services Standards (HSS) for Privacy of Individually identifiable health information.

Contractor shall provide documented proof to the contracting officer that all employees assigned work and/or having access to protected health information have received annual training. Proof of training is to be forwarded to the COR. Training can be obtained through http://www.insidelms.va.gov/index.shtm. An account must be set up in order to access the training site by visiting https://www.tms.va.gov/plateau/user/login.jsp. page and contacting the local LMS Administrator or contacting the VA TMS Help Desk by phone at 1-866-496-0463 or via e-mail at vatmshelp@va.gov. For contractors and sub-contractors who do not have access to VHA computer systems, this requirement is met by receiving VHA National Privacy Training, other VHA approved privacy training or contract furnished training that meets the requirements of the HHS standards.

14.3. Rules of Behavior for Automated Information Systems: Contractor personnel having access to VA Information Systems are required to read and sign a Rules of Behavior statement which outlines rules of behavior related to VA Automated Information Systems. The COR will provide, through the facility Information Security Officer (ISO), the Rules of Behavior to the contractor for the respective facility.

14.4. VA Information Security Awareness Training: Each contractor assigned work under the contract is required to receive and document completion of VA training on Information Security. Training can be obtained through http://www.insidetms.va.gov/index.shtm. An account must be set up in order to access the training site by visiting https://www.tms.va.gov/plateau/user/login.jsp. page and contacting the local LMS Administrator or contacting the VA TMS Help Desk by phone at 1-866-496-0463 or via e-mail at vatmshelp@va.gov. Contractor shall provide documented proof to the COR that all contractor employees servicing a VA contract have received annual training.

15. Access to VA Information and VA Information Systems http://www.insidelms.va.gov/index.shtm https://www.tms.va.gov/plateau/user/login.jsp mailto:vatmshelp@va.gov http://www.insidetms.va.gov/index.shtm https://www.tms.va.gov/plateau/user/login.jsp mailto:vatmshelp@va.gov

15.1. 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.

15.2. 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.

15.3. 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.

15.4. 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.

15.5. Custom software development and outsourced operations must be located in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the contractor/subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor.

15.6. The contractor or subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the contractor or subcontractor's employ. The Contracting Officer must also be notified immediately by the contractor or subcontractor prior to an unfriendly termination.

16. VA Information Custodial Language

16.1. Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor 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. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).

16.2. VA information should not be co-mingled, if possible, with any other data on the contractors/subcontractor's information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the contractor must ensure that VA's information is returned to the VA or destroyed in accordance with VA's sanitization requirements. VA reserves the right to conduct on site inspections of contractor and subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements.

16.3. Prior to termination or completion of this contract, contractor/ subcontractor must not destroy information received from VA, or gathered/ created by the contractor in the course of performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook

6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.

16.4. The contractor/subcontractor must receive, gather, store, back up, maintain, use, disclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations, and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations, and policies in this contract.

16.5. The contractor/subcontractor shall not make copies of VA information except as authorized and necessary to perform the terms of the agreement or to preserve electronic information stored on contractor/subcontractor electronic storage media for restoration in case any electronic equipment or data used by the contractor/subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed.

16.6. If VA determines that the contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.

16.7. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.

16.8. The contractor/subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated.

16.9. The contractor/subcontractor's firewall and Web services security controls, if applicable, shall meet or exceed VA's minimum requirements. VA Configuration Guidelines are available upon request.

16.10. Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the contractor/subcontractor may use and disclose VA information only in two other situations:(i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA's prior written approval. The contractor/subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response.

16.11. Notwithstanding the provision above, the contractor/subcontractor shall not release VA records protected by Title 38 U.S.C. 5705, confidentiality of medical quality assurance records and/or Title 38 U.S.C. 7332, confidentiality of certain health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus. If the contractor/subcontractor is in receipt of a court order or other requests for the above-mentioned information, that contractor/subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response.

16.12. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COR.

17. Information System Design and Development

17.1. Information systems that are designed or developed for or on behalf of VA at non- VA facilities shall comply with all VA directives developed in accordance with FISMA, HIPAA, NIST, and related VA security and privacy control requirements for Federal information systems. This includes standards for the protection of electronic PHI, outlined in 45 C.F.R. Part 164, Subpart C, information and system security categorization level designations in accordance with FIPS 199 and FIPS 200 with implementation of all baseline security controls commensurate with the FIPS 199 system security categorization (reference Appendix D of VA Handbook 6500, VA Information Security Program). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COR, and approved by the VA Privacy Service in accordance with Directive 6507, VA Privacy Impact Assessment.

17.2. The contractor/subcontractor shall certify to the COR that applications are fully functional and operate correctly as intended on systems using the VA Federal Desktop Core Configuration (FDCC), and the common security configuration guidelines provided by NIST or the VA. This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista) and future versions, as required.

17.3. The standard installation, operation, maintenance, updating, and patching of software shall not alter the configuration settings from the VA approved and FDCC configuration. Information technology staff must also use the Windows Installer Service for installation to the default "program files" directory and silently install and uninstall.

17.4. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.

17.5. The security controls must be designed, developed, approved by VA, and implemented in accordance with the provisions of VA security system development life cycle as outlined in NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, VA Handbook 6500, Information Security Program and VA Handbook 6500.5, Incorporating Security and Privacy in System Development Lifecycle.

17.6. The contractor/subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C.

552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties.

17.7. The contractor/subcontractor agrees to:

17.7.1. Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies: The Systems of Records (SOR); and The design, development, or operation work that the contractor/ subcontractor is to perform;

17.7.2. Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a SOR on individuals that is subject to the Privacy Act; and

17.7.3. Include this Privacy Act clause, including this subparagraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a SOR.

17.8. In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a SOR on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a SOR on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a SOR on individuals to accomplish an agency function, the contractor/subcontractor is considered to be an employee of the agency.

17.9. "Operation of a System of Records" means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records. "Record" means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person's name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph. "System of Records" means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.

17.10. The vendor shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as "Systems"), throughout the life of this contract and any extension, warranty, or maintenance periods.

This includes, but is not limited to workarounds, patches, hot fixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.

17.11. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 3 days.

17.12. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor shall provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within days.

17.13. All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g. for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and Technology.

18. Security Incident Investigation

18.1. 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. The contractor/ subcontractor shall immediately notify the COR and simultaneously, the designated ISO and Privacy Officer for the contract 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.

18.2. To the extent known by the contractor/subcontractor, the contractor/ subcontractor's notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the contractor/subcontractor considers relevant.

18.3. With respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.

18.4. In instances of theft or break-in or other criminal activity, the contractor/subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and Security and Law Enforcement. The contractor, its employees, and its subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The contractor/subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident.

19. Liquidated Damages for Data Breach

19.1. Consistent with the requirements of 38 U.S.C. 5725, a contract may require access to sensitive personal information. If so, the contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the contractor/subcontractor processes or maintains under this contract.

19.2. The contractor/subcontractor shall provide notice to VA of a "security incident" as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non- Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.

19.3. Each risk analysis shall address all relevant information concerning the data breach, including the following:

19.3.1. Nature of the event (loss, theft, unauthorized access);

19.3.2. Description of the event, including:

19.3.2.1. date of occurrence;

19.3.2.2. data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;

19.3.2.3. Number of individuals affected or potentially affected;

19.3.2.4. Names of individuals or groups affected or potentially affected;

19.3.2.5. Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;

19.3.2.6. Amount of time the data has been out of VA control;

19.3.2.7. The likelihood that the sensitive personal information shall or has been compromised (made accessible to and usable by unauthorized persons);

19.3.2.8. Known misuses of data containing sensitive personal information, if any;

19.3.2.9. Assessment of the potential harm to the affected individuals;

19.3.2.10. Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; and

19.3.2.11. Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.

19.3.3. Based on the determinations of the independent risk analysis, the contractor shall be responsible for paying to the VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:

19.3.3.1. Notification;

19.3.3.2. One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;

19.3.3.3. Data breach analysis;

19.3.3.4. Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;

19.3.3.5. One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and

19.3.3.6. Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.

20. Security Controls Compliance Testing

20.1. On a periodic basis, VA, including the Office of Inspector General, reserves the right to evaluate any or all of the security controls and privacy practices implemented by the contractor under the clauses contained within the contract. With 10 working-day's notice, at the request of the government, the contractor must fully cooperate and assist in a government-sponsored security controls assessment at each location wherein VA information is processed or stored, or information systems are developed, operated, maintained, or used on behalf of VA, including those initiated by the Office of Inspector General. The government may conduct a security control assessment on shorter notice (to include unannounced assessments) as determined by VA in the event of a security incident or at any other time.

21. Training

21.1. All contractor employees and subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:

21.1.1. Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Contractor Rules of Behavior, Appendix E relating to access to VA information and information systems.

21.1.2. Successfully complete the VA Cyber Security Awareness and Rules of Behavior training and annually complete required security training.

21.1.3. Successfully complete the appropriate VA privacy training and annually complete required privacy training; and

21.1.4. Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access [to be defined by the VA program official and provided to the contracting officer for inclusion in the solicitation document - e.g., any role-based information security…