36C10B21Q0524.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. 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 89

36C10B21Q0524 01/26/2021

Eleanor Slocum 732-440-9677 02/02/2021

1:00 PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X

Y

541519

$30.0 Million

N/A

X

See Delivery Schedule

Technology Acquisition Center

Eatontown NJ 07724

See Section B.3 Contract Administration

Data

This RFQ is for brand name Curapatient software licenses and support services. The period of performance shall be 12 months form date of award inclusive of one, 12-month option period.

See Section B for a list of required deliverables.

Points of Contact:

Eleanor Slocum, Contract Specialist

Eleanor.Slocum@va.gov 732-440-9677

Michael Weckesser, Contracting Officer

Michael.Weckesser@va.gov 732-795-1097 x x

Michael Weckesser

Contracting Officer

36C10B21Q0524

Table of Contents

SECTION A

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

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

RIGHTS IN DATA

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

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

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR

INFORMATION SYSTEMS (JUN 2016)

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (JAN 2021)

C.4 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)... 60

C.5 VAAR 852.212-70 PROVISIONS AND CLAUSES APPLICABLE TO VA

ACQUISITION OF COMMERCIAL ITEMS (APR 2020)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

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

1998)

E.2 52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (OCT 2020)

E.3 52.204-26 COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES—

REPRESENTATION (OCT 2020)

E.4 52.209-5 CERTIFICATION REGARDING RESPONSIBILITY MATTERS (OCT

2015)

E.5 52.209-11 REPRESENTATION BY CORPORATIONS REGARDING DELINQUENT

TAX LIABILITY OR A FELONY CONVICTION UNDER ANY FEDERAL LAW (FEB 2016)

E.6 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL ITEMS ( JAN 2021)

E.7 52.216-1 TYPE OF CONTRACT (APR 1984)

E.8 52.222-22 PREVIOUS CONTRACTS AND COMPLIANCE REPORTS (FEB 1999)

E.9 52.233-2 SERVICE OF PROTEST (SEP 2006)

E.10 VAAR 852.233-70 PROTEST CONTENT/ALTERNATIVE DISPUTE

RESOLUTION (OCT 2018)

E.11 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (OCT 2018)

E.12 RESPONSE INSTRUCTIONS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this

Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the

Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the

Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance

(38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement.

In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the

Government all data first produced under this Contract/Order with unlimited rights as defined by FAR

52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation.

Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

RIGHTS IN DATA

The Contractor shall deliver to VA all data first produced under this contract. “Data” shall be defined by Federal Acquisition Regulation (FAR) 52.227-14; it includes, but is not limited to, all deliverables, software and all data, documents, and plans created or otherwise generated from the software delivered under this contract. VA shall own exclusively all data first produced under this contract. Data shall be delivered in a readable, agreed upon format between CO, COR, and Contractor in accordance with FAR 52.227-16.

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

(1). Definitions.

a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans

Affairs (“VA”) and is synonymous with “Government.”

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the

Licensor, the Contractor remains responsible for performance under this

Contract/Order.

c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to

5.4). An example of an update is the addition of new hardware.

g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2). Software License.

a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the

Government is a perpetual, nonexclusive license to use the software.

b) The Government may use the software in a networked environment.

c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

d) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

(3). Software Maintenance and Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers so as to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the

Performance Work Statement or Product Description. However, prolonged delay

(exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). Disabling Software Code. The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications. Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

http://www.cpars.gov/

B.3 CONTRACT ADMINISTRATION DATA

(continuation from Standard Form 1449, block 18A.)

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

a. CONTRACTOR: To be completed at time of award.

b. GOVERNMENT: Michael Weckesser, Contracting Officer

Technology Acquisition Center

Eatontown, NJ 07724

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

[X] 52.232-33, Payment by Electronic Funds Transfer—System For Award Management, or

[] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly [ ]

b. Semi-Annually [ ]

c. Other [X] Upon Government acceptance of supplies/services set forth in Section B.4, Price Schedule, and

Section B.5, Performance Work Statement.

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.

5. ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

AMENDMENT NO DATE

B.4 PRICE SCHEDULE

BASE PERIOD

Period of Performance shall be 12 months from date of award.

All “days” referenced shall be calendar days, unless otherwise noted.

Contract Line

Item Number

(CLIN)

Description Qty Unit Unit Price Total Price

0001 Project Management in Accordance

With (IAW) Performance Work Statement (PWS) Sections 5.1 and all of its subparagraphs.

This Firm Fixed Price (FFP) Contract

Line Item Number (CLIN) includes all labor and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1 and inclusive of all subparagraphs for the base period and option period, if exercised.

The cost of Reporting Requirements

CLIN 0001 and SLINs 0001AA through 0001AC shall be included in and allocated to SLIN 0002AA.

1 LOT (LO) Not

Separately

Priced (NSP)

NSP

0001AA Contractor Project Management Plan

IAW PWS Section 5.1.1.

Due Thirty (30) days after contract

(DAC) and updated monthly thereafter.

Electronic Submission to: VA

Program Manager (PM), Contract

Specialist (CS) and Contracting

Officer Representative (COR).

Inspection: destination Acceptance: destination

12 EACH

(EA)

NSP NSP

0001AB Monthly Progress Report IAW PWS

Section 5.1.2.

Due the fifth day of each month throughout the period of performance

(PoP).

12 EA NSP NSP

Electronic Submission to: VA PM, CS and COR.

Inspection: destination

Acceptance: destination

0001AC Quarterly Report IAW PWS Section

5.1.4.

Due 90 days after award and quarterly thereafter.

and COR.

4 EA NSP NSP

0002 Curapatient Care Plan Management

Platform Rollout IAW PWS 5.2 and all of its subparagraphs.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.2 and its underlying subparagraphs.

The period of performance shall complete upon the end of the base period.

1 LO NSP NSP

0002AA COVID-19 Care Plan Management

SaaS capability /Licensing IAW PWS

Sections 5.2.1 and 5.2.2.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.2.2.

EA = cost of 1 site, (700 patients and

10 clinicians at each site)

Sites: VAMC Washington, DC

VAMC Long Beach, CA

Licenses shall be provided within 30 days after successful achievement of the Authority to Operate (ATO) and

FedRAMP compliance.

2 EA Not to

Exceed

The Contractor shall invoice at a rate of

*n

Not to Exceed

The Not-to-exceed cost for this cost for this CLIN shall be Annual licensing Cost.

Annual licensing Cost/Not to exceed

Value: $__________

The rate of *n that the Contractor shall invoice for is based on prorated cost from the receipt of the licenses after the aforementioned conditions through the end of the base period of performance. The cost to be invoiced, shall be calculated as follows:

*n= number of months after successful achievement of

ATO/FedRAMP Compliance * monthly licensing cost

Monthly licensing cost shall be calculated by taking the annual licensing cost and dividing by 12.

There shall be no partial costs. For days 1-15, the Contractor shall round down, for days 15-31, the contractor shall round up.

Monthly Licensing Cost: $________

(e.g- If achievement of

ATO/FedRAMP in month 4 of the base period, the *n/total value invoiced shall be 8* Monthly

Licensing Cost per site)

The period of performance shall complete upon the end of the base period.

0003 Curapatient Care Plan Management

Platform Training and Support IAW

PWS 5.3.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.3.

1 LO NSP NSP

The period of performance shall complete upon the end of the base period.

The cost of CLIN 0003 and SLIN

0003AA shall be included in and allocated to SLIN 0002AA.

0003AA Training Materials IAW PWS Section

5.3.

Due 5 days prior to each training event

Electronic Submission to: VA PM, CS and COR.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

0004 Assessment, Authorization, and

Continuous Monitoring IAW PWS

Section 5.4

Any costs associated with this task shall be included in SLIN 0002AA.

1 EA NSP NSP

0004AA FedRAMP System Security Plan

(SSP) and supporting documentation

IAW PWS Section 5.4

Due within 30 days after contract award.

Electronic Submission to: VA PM and

COR.

1 LO NSP NSP

0004AB 3PAO Security Assessment Plan

(SAP) IAW PWS Section 5.4

Due within 75 days after contract award.

Electronic Submission to: VA PM, CS and COR.

1 LO NSP NSP

0004AC 3PAO Security Assessment Report

(SAR) IAW PWS Section 5.4

Due within 90 days after contract award.

Electronic Submission to: VA PM, CS

0005 Contractor Staff Roster IAW PWS

Section 6.2.2.

Due within 3 business days after contract award and updated as required.

Electronic Submission to: VA PM, CS and COR.

BASE PERIOD TOTAL $

OPTION PERIOD 1

Period of Performance shall be 12 months

This Option Period may be exercised IAW FAR 52.217-9 “Option to Extend the Term of the Contract” (MAR 2000).

Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, the option shall commence immediately after expiration of the base period.

Contract Line Item

Number (CLIN) Description Qty Unit Unit Price Total Price

1001 Project Management IAW PWS

Sections 5.1 and all of its subparagraphs.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1 and inclusive of all subparagraphs for the base period and option period, if exercised.

The cost of Reporting Requirements

CLIN 1001 and SLINs 1001AA through 1001AC shall be included in and allocated to SLIN 1002AA.

1 LO NSP

NSP

1001AA Contractor Project Management Plan

IAW PWS Section 5.1.1.

To be updated monthly.

Electronic Submission to: VA PM, CS and COR.

12 EA NSP NSP

1001AB Monthly Progress Report IAW PWS

Section 5.1.2.

Due the fifth day of each month throughout the PoP.

Inspection: destination

Acceptance: destination

12 EA NSP NSP

1001AC Quarterly Report IAW PWS Section

5.1.4.

To be updated quarterly in accordance with the schedule set forth in SLIN

0001AC.

4 EA NSP NSP

1002 Curapatient Care Plan Management

Platform Rollout IAW PWS 5.2 and all of its subparagraphs.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in

PWS paragraphs 5.2 and its underlying subparagraphs.

1 LO NSP NSP

1002AA COVID-19 Care Plan Management

SaaS capability /Licensing IAW PWS

Sections 5.2.1 and 5.2.2.

This FFP CLIN

EA = cost of 1 site, (700 patients and

10 clinicians at each site)

Sites: VAMC Washington, DC

VAMC Long Beach, CA

2 EA $

1003 Curapatient Care Plan Management Platform Training and Support IAW

PWS 5.3.

This FFP CLIN includes all labor and deliverables required for the successful completion of the services detailed in

PWS paragraphs 5.3.

The period of performance shall complete upon the end of the base period.

The cost of CLIN 1003 and SLIN 1003AA shall be included in and allocated to SLIN 1002AA.

1003AA Training Materials IAW PWS Section

5.3.

Due 5 days prior to each training event

Electronic Submission to: VA PM, CS and COR.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

0005 Contractor Staff Roster IAW PWS

Section 6.2.2.

Updated as required.

Electronic Submission to: VA PM, CS and COR.

1 LO NSP NSP

OPTION PERIOD 1 TOTAL $

TOTAL BASE and OPTION PERIOD 1 $

B.5 PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner. VA depends on Information

Management/Information Technology (IM/IT) systems to meet mission goals.

During the 2019 Artificial Intelligence (AI) Tech Sprint, the National Artificial Intelligence Institute recognized that care plan management, hospital readmissions, and the outpatient management of complex health conditions was something that could be better managed with the assistance of Artificial

Intelligence. Further, the use of AI in case management poses unique opportunities to advance research into the use of AI to train models relevant to case management and complex care conditions.

With the arrival of COVID-19 as a public health emergency, the same principles of case management with additional complications of social distancing, tracking large panels of potentially at-risk patients, and monitoring a condition that can rapidly accelerate towards hospitalization or death, the need for artificially intelligence cast management solutions became even more evident and the proposed scope of the project shifted to focus on AI driven solutions for COVID case management at home.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements

For Cryptographic Modules”

4. FIPS Pub 199. Standards for Security Categorization of Federal Information and Information

Systems, February 2004

5. FIPS Pub 200, Minimum Security Requirements for Federal Information and Information

Systems, March 2016

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,”

August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

8. Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon

Software Engineering Institute, Capability Maturity Model® Integration for Acquisition

(CMMI-ACQ), Version 1.3 November 2010

9. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

10. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of

2006, Title IX, Information Security Matters

11. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

12. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

13. VA Handbook 0710, Personnel Security and Suitability Program, May 2, 2016, https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs

14. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019

15. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” January 18, 2017

16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services

(CHAMPUS)”

18. NIST SP 800-66 Rev. 1, An Introductory Resource Guide for Implementing the Health

Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18,

20. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

21. VA Directive 6500, “VA Cybersecurity Program,” January 24, 2019

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3:

VA Information Security Program,” March 10, 2015

23. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information

(SPI)”, July 28, 2016

24. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA

Information Systems,” February 3, 2014

25. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development

Lifecycle”, March 22, 2010

26. VA Handbook 6500.6, “Contract Security,” March 12, 2010

27. VA Handbook 6500.8, “Information System Contingency Planning”, April 6, 2011

28. VA Handbook 6500.11, “VA Firewall Configuration”, August 22, 2017

29. OI&T Process Asset Library (PAL), https://www.va.gov/process/ . Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

30. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

31. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact

Assessment,” October 15, 2014

32. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact

Assessment,” July 30, 2015

33. VA Handbook 6510, “VA Identity and Access Management”, January 15, 2016

34. VA Directive and Handbook 6513, “Secure External Connections”, October 12, 2017

35. VA Directive 6300, Records and Information Management, September 21, 2018

36. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

37. NIST SP 800-37 Rev 1, Risk Management Framework for Information Systems and

Organizations: A System Life Cycle Approach for Security and Privacy, December 2018

38. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and

Organizations, January 22, 2015

39. OMB Memorandum, “Transition to IPv6”, September 28, 2010

40. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, October 26, 2015

41. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014 https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

42. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of

HSPD-12, June 30, 2006

43. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16,

44. OMB Memorandum 05-24, Implementation of Homeland Security Presidential Directive

(HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and

Contractors, August 5, 2005

45. OMB memorandum M-11-11, “Continued Implementation of Homeland Security

Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal

Employees and Contractors, February 3, 2011

46. OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12

Implementation, May 23, 2008

47. Federal Identity, Credential, and Access Management (FICAM) Roadmap and

Implementation Guidance, December 2, 2011

48. NIST SP 800-116 Rev 1, Guidelines for the Use of Personal Identity Verification (PIV)

Credentials in Facility Access, June 2018

49. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of

Personally Identifiable Information, May 22, 2007

50. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, December

51. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

52. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012

53. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981

Mobile, PIV, and Authentication, March 2014

54. VA Memorandum, VAIQ #7100147, Continued Implementation of Homeland Security

Presidential Directive 12 (HSPD-12), April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

55. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

56. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy

Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

57. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal

Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017, https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf

58. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

59. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name System

Infrastructure, August 22, 2008

60. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental

Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference

Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)

61. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law

110–140), December 19, 2007 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552

62. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

63. Executive Order 13834, “Efficient Federal Operations”, dated May 17, 2018

64. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

65. VA Directive 0058, “VA Green Purchasing Program”, July 19, 2013

66. VA Handbook 0058, “VA Green Purchasing Program”, July 19, 2013

67. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

68. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

69. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

70. VA Memorandum “Proper Use of Email and Other Messaging Services”, January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

71. VA Directive 6066, “Protected Health Information (PHI) And Business Associate

Agreements Management”, September 2, 2014

3.0 SCOPE OF WORK

The Contractor shall provide a Commercial-Off-the-Shelf (COTS), hosted, cloud-based, COVID-19 Care

Plan Management solution, which utilizes Artificial Intelligence (AI) techniques and technologies, and

Software as a Service (SaaS) delivery model, to assist clinicians and patients in managing complex health conditions, specifically for COVID-19 monitoring and management, and promoting social distancing.

The SaaS solution shall include a web-based, patient-facing component, along with a web-based, clinician facing component compatible with MS Windows. The Contractor shall provide training and operational support for the capability, and implement the solution at two VAMC locations in Washington, DC and

Long Beach, CA.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12-months from date of award, with up to one subsequent 12-month option period. Total not to exceed 24 months.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

There are ten (10) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, four are set by date:

New Year's Day January 1

Independence Day July 4 Veterans Day November 11

Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

Martin Luther King's Birthday Third Monday in January

Washington's Birthday Third Monday in February

Memorial Day Last Monday in May

Labor Day First Monday in September

Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed primarily at Contractor facilities, with some on-site support at

VA facilities in Washington, DC and Long Beach, CA. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is four. Anticipated locations include the following, estimated at five days in duration each, for up to six people:

1. Washington, DC

2. Long Beach, CA

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft

Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the

Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

A. Monthly Progress Report

5.1.3 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after contract award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), as the Post-

Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the

COR. The Contractor shall provide a draft agenda to the CO and VA PM at least five (5) calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation. At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting and the following statement “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical

Kickoff Meeting for the COVID-19 Care Management SaaS.” The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) calendar days after the meeting.

The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR and all attendees within three (3) calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.

5.1.4 ALGORITHM REPORTING

The Contractor shall prepare a Quarterly Report on approaches used for data preparation, technique selection, mean square error/receiver operator characteristic curve, area under curve, accuracy, variables used, and amount of data (e.g., patients), etc as part of the SaaS solution. Furthermore, the Contractor shall make a de-identified version, as identified by the VA PM and confirmed by the privacy officer, of a subset(s) of dataset(s) leveraged/generated by the SaaS solution which are suitable for use with future AI tech sprints, etc. The above information, and perspectives gained, will be leveraged by the VA for report and/or publications on the results of this pilot and future work.

A. Quarterly Report

5.2 COVID-19 CARE PLAN MANAGEMENT PLATFORM

5.2.1 PLATFORM FUNCTIONAL REQUIREMENTS

The Contractor shall provide a cloud-hosted, Commercial Off-the-Shelf (COTS) digital health platform

SaaS solution to perform unique COVID-19 Care Plan Management, on a Contractor-provided infrastructure that is complaint with the Federal Risk Authorization Management Program (FedRAMP).

See Section 5.4 of this PWS for additional detail regarding FedRAMP requirements. The Contractor shall follow VA’s Veteran-Focused Integration Process (VIP) in the implementation and release of the capability at the sites and user quantities defined in section 5.2.2 of this PWS. Further information on

VIP can be found in section 6.1.6 of this PWS. The COVID-19 Care Plan Management SaaS solution shall include the following features and capabilities:

a. Provide access to the COVID-19 Care Plan Management SaaS solution for Veterans and clinicians to assist with COVID-19 monitoring for patients at home who are at-risk or have been positively diagnosed with COVID-19. The COVID-19 Care Plan Management SaaS solution shall include the following functions:

1. Introduction Process - As Veterans come in for COVID-19 testing, the SaaS solution shall provide each patient with a QR code to initiate the onboarding process onto the platform. Patients shall be provided instruction through the SaaS solution (as needed) to go along the standard paper-based work.

2. Patient at Home – The SaaS solution shall include an immersive, easy to use mobile application that allows Veterans to keep track of their symptoms and report key vitals, such as temperature and oxygen level. The application shall include features for contact tracing, quarantine compliance, and up-to-date information on the Veterans lab work.

b. The solution shall include the ability to facilitate Veteran and clinician engagement, support contact tracing and quarantine analysis, and provide Veteran statuses at a snapshot while supporting panel-wide discovery of patient trends. The SaaS solution shall include the ability to create a COVID-19 plan of care for the patient and assist in tracking daily symptoms as well as overall condition. The data shall be compiled and sent to VA for population health analysis as well as enhanced treatment opportunities. The solution shall use Machine Learning (ML) to assist in patient assessments and include reinforced learning algorithms to alert providers of changes in patient condition.

c. The SaaS solution shall utilize AI to assist in managing complex patient health conditions, specifically COVID-19, and promoting social distancing. The SaaS solution shall include unsupervised learning to perform cluster analysis and provide easily understood dashboards that clinicians can use to manage large clusters of patients who are isolating at home.

d. The SaaS solution shall include an intuitive, web-based user interface which shall be accessible for Veterans and clinicians across the spectrum of VA Care. The user interface shall be designed to be engaging and provide a seamless experience to help Veterans and clinicians work together, including:

1. Dashboards and data visualization to bring transparency to metrics and charts.

2. Gamification which incorporates both near and long-term milestones for complete care.

3. Modern, card-based designs.

e. The SaaS solution shall include functionality for contact tracing, population health, communication between Veteran and clinician and the ability to create a customized plan of care.

f. The SaaS solution shall include the ability for the user to do daily symptom tracking and respond to targeted assessment questions, as created by the clinician.

g. The SaaS solution shall be capable of accepting verbal responses to the questions and evaluate the responses using Natural Language Processing to capture sentiments and trended to identify which patients require an in-person visit or further interaction via their digital virtual twin using reinforced learning principles.

h. The SaaS solution shall include the ability to develop a tailored roadmap for the needs of the individual Veteran while being able to scale and engage resources across VHA. This shall include a capability for clinicians to ensure that each patient is on a plan with the proper milestone, team, and resources to ensure their success.

i. The SaaS solution shall allow patients to be easily onboarded to a plan which is tailored to their needs and which has the appropriate resources and team assigned to support the patient.

j. The SaaS solution shall measure key metrics such as patient conditions, patient engagement, cycle times, aging, and compliance.

k. The SaaS solution shall include care plan templates that are targeted specifically to address symptoms of COVID-19. This shall include the ability to create data-driven care plans, tailored guided assessments, monitor key vitals to track health conditions (heart rate, oxygen level, and temperature), and the ability to fine-tune changes and checkpoints with clinicians.

l. The SaaS solution shall leverage advanced AI and ML capabilities to enhance the user experience, including:

1. Provide the ability to identify and reconcile medications virtually to allow medication in pill form to be identified in real-world situations through images (or video) by analyzing features such as texture, color, shape, dimensions, and text encoding to recognize markings.

2. Natural language processing to identify sentiment and variations within it and to create a bag-of-words representation of the text dataset.

m. The SaaS solution shall include the ability to manage the entire patient under investigation (PUI) process as described by the CDC’s infectious disease group, including contact tracing, patient self-quarantine, care compliance, and daily COVID-19 check-ins.

n. The SaaS solution shall include predictive analytic algorithms to allow clinicians to virtually triage patients and allow identification of clusters and the outliers within them.

o. The SaaS solution shall include the ability for segregation of roles and duties pertaining to the data’s use and allow patients full control of this data with opt-in/out settings readily accessible.

p. The Contractor shall provide VA access to backend data from the COVID-19 Care Plan

Management SaaS solution to allow VA to research and analyze the effectiveness of the capability. Additionally, the Contractor shall comply with all applicable records management laws and regulations, National Archives and Records Administration (NARA) records policies, and Freedom of Information Act (FOIA).

q. SaaS solution shall include a secure API which enables rapid onboarding of new Medical

Centers and Clinics.

r. The SaaS solution shall operate in an IT environment external to the VA. The cloud environment used for the COVID-19 Care Plan Management solution shall comply with applicable federal policies.

s. The Contractor shall be responsible for all Operations and Maintenance (O&M) support of the

COVID-19 Care Plan Management platform solution and hosted infrastructure.

t. The Contractor shall propose Service Level Agreements (SLA) for the SaaS solution to accurately monitor the objectives described within the PWS.

5.2.2 COVID-19 CARE PLAN MANAGEMENT IMPLEMENTATION

The Contractor shall implement the COVID-19 Care Plan Management capability at the VAMC locations in Washington, DC and Long Beach, CA to a total of approximately 700 patients and 10 clinicians at each site. The COVID-19 Care Plan Management SaaS capability shall be configured and ready for release within 30 days after the ATO approval/FedRAMP certification and shall be provided for the remainder of the PoP. The Contractor shall provide a secure URL to enable access, set up, and configuring of the

COVID-19 Care Plan Management platform at each site. The platform shall be capable of being client supported, however during this pilot, the Contractor shall provide operational support and advice to medical center personnel on the use of the platform.

Deliverable:

A. SaaS Licenses

5.3 COVID-19 CARE PLAN MANAGEMENT PLATFORM TRAINING AND SUPPORT

The Contractor shall:

1. Provide two, remote (virtual) training sessions for up to 20 VA clinicians. Training dates shall be coordinated with VA PM and the individual sites. Training shall be recorded for future use and provided to VA. The Training shall include both an overview of the platform and detailed walkthrough of the capabilities.

2. Provide Training Materials to VA five (5) days prior to any training event. The Training

Materials shall provide role base training information and user guide to address how the users utilize the COVID-19 Care Plan Management platform and features, both for clinicians and

Veterans.

3. Provide technical support, online and via phone, during normal duty hours (Sunday –

Saturday, 0800-1630 Local Time) to troubleshoot and resolve technical/functional issues with the SaaS solution, to include accessing the capability. The Contractor shall provide this support for the duration of the PoP.

A. Training Materials

5.4 ASSESSMENT, AUTHORIZATION, AND CONTINUOUS MONITORING

The Contractor shall ensure the COVID-19 Care Plan Management SaaS solution has completed the

FedRAMP ATO process as detailed below and received approval for FedRAMP High prior to billing for any software or licensing fees. This shall include:

1. The information system solution selected by the Contractor shall comply with the Federal Information

Security Management Act (FISMA).

2. The Contractor shall comply with FedRAMP requirements as mandated by Federal laws and policies, including making available any documentation, physical access, and logical access needed to support this requirement.

3. Following guidance from the Federal CIO, VA will utilize existing JAB ATO or agency ATO issued by another agency as a starting point for FedRAMP requirements. If neither of those exist, VA will sponsor FedRAMP ATO. VA will be using the FedRAMP baselines as a starting point, since they are specifically tailored for cloud services.

https:/…