36C77619R0003-002.docx

HIG19-1 Healthcare Identity Management Support

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Health Informatics (OHI) Health Information Governance (HIG)

HIG19-1

Healthcare Identity Management (HCIdM) Support

Date: 10/31/18 PWS Version Number: 1.0

Contents

BACKGROUND

The Healthcare Identity Management (HC IdM) Program operates within the Veterans Health Administration’s (VHA) Data Quality Program. The HC IdM Program’s primary role is to serve as the steward of patient and beneficiary identity data, performing data integrity tasks to maintain and support the Veterans Identity, traits and their subsequent VA system records linked to the identity. The HC IdM Program ensures integrity of patient and beneficiary identity data within the Master Veteran Index (MVI). The MVI is a database that holds over 42 million unique entries and is populated from patient and beneficiary databases at VA facilities nationwide. Veteran patients and beneficiaries are matched within the MVI database through an assigned, unique Integration Control Number (ICN). This number is assigned based on matching of key identity traits. The MVI provides the mechanism for linking the patient or beneficiaries’ information, enabling an enterprise-wide view of individual and aggregate electronic healthcare records and their other beneficiary records. This ICN allows for the creation of a single longitudinal record, consisting of all the records a Veteran accumulates from the period of service, through post service care and benefits. This record will include any Department of Defense (DoD), Veterans Health Administration (VHA), Veterans Benefits Administration (VBA) and National Cemetery Administration (NCA) and Veteran Health Information Exchange (VHIE) (formerly known as NwHIN) participant records.

Creating and maintaining a correlation between these records and ensuring that they all identify a single individual, relies heavily on the integrity of the data within the MVI. When one or more VA sites, and/or our sharing partners, have a patient identified by the same ICN or matching identity traits, the MVI facilitates the sharing of information, resulting in coordinated and integrated health care for Veterans and a single view of a Veterans total record for VA.

APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following agency specific Directives and Procedures and a copy of these items are electronically available to the contractor as a part of the solicitation:

1. VHA Directive 2013-1906 Data Quality Requirements for Healthcare Identity Management and Master Veteran Index Functions. (Task 1,2,3)

2. VHA Directive 2012-036 Identity Authentication for Health Care Services (Task 1,2,3)

3. VHA Directive 2013-003 Providing Health Care for Transgender and Intersex Veterans (Task 3)

4. Privacy Fact Sheet, Volume 8No9, Revised Nov 2012 (Task 1,2,3)

5. Health Information Management, VHA Handbook 1907.01 (Task 1,2,3)

6. Transgender Identity Changes Fact Sheet, October 2012 Volume12No4 (Task 3)

7. Identity Management Toolkit (IdM TK) User Manual (Task 1,2,3)

8. Identity Management Toolkit (IdM TK) User Guide for POC (Task 1,2,3)

9. Override (OVR) Task Guidelines (Task 1,2,3),

10. Toolkit (TK) Request Pilot Procedure (Task 1,2,3)

11. Toolkit (TK) Request Procedures (Task 1,2,3)

12. Toolkit (TK) Task Procedures (Task 1,2,3)

13. Toolkit (TK) Template (Task 1, 2)

14. Healthcare Identity Management (HC IdM) Team Tips (General Overview Task 1,2,3)

15. Master Veteran Index (MVI) Exception Processing (Task 5)

16. Email Distribution Duties (Task 1,2,3)

17. Email Security Fact Sheet (Task 1,2,3)

18. DOD Correlation Guidelines (Task 1,2)

19. Test Patient Record Guidelines (Reference Guide Task 1,2,3)

20. HC IdM Detailed Metrics Report (Reference Guide Task 1,2,3)

21. HC IdM Contract Workload Metrics Report (Reference Guide Task 1,2,3)

22. HC IdM Training Schedule Timeline (Task 5)

The Contractor shall also comply with the following:

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

24. “Federal Information Security Modernization Act of 2014”

25. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements For Cryptographic Modules”

26. FIPS Pub 199. Standards for Security Categorization of Federal Information and Information Systems, February 2004

27. FIPS Pub 200, Minimum Security Requirements for Federal Information and Information Systems, March 2016

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

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

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

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

32. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

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

34. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, http://www.va.gov/vapubs/

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

36. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008

37. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003

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

39. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”

40. An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

41. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998

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

43. VA Directive 6500, “Managing Information Security Risk: VA Information Security Program,” September 20, 2012

44. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015

45. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008

46. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016

47. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA Information Systems,” February 3, 2014

48. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development Lifecycle”, March 22, 2010

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

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

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

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

53. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

54. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

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

56. VA Directive 6300, Records and Information Management, February 26, 2009

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

58. NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, June 10, 2014

59. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

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

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

62. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014

63. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006

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

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

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

67. OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation, May 23, 2008

68. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

69. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification (PIV) Credentials in Physical Access Control Systems, November 20, 2008

70. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

71. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, June 2017

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

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

74. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 2014

75. 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)

76. 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)

77. VA Memorandum “Mandate to meet PIV Requirements for New and Existing Systems” (VAIQ# 7712300), June 30, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846

78. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0, Federal Interagency Technical Reference Architectures, Department of Homeland Security, October 1, 2013, https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf

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

80. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name System Infrastructure, August 22, 2008

81. 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)

82. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

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

84. Executive Order 13693, “Planning for Federal Sustainability in the Next Decade”, dated March 19, 2015

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

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

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

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

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

90. VA Memorandum, “Implementation of Federal Personal Identity Verification (PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

91. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

92. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015; https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

93. “Veteran Focused Integration Process (VIP) Guide 2.0”, May 2017, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

94. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411

95. “POLARIS User Guide”, Version 1.2, February 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

96. VA Memorandum “Use of Personal Email (VAIQ #7581492)”, April 24, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

97. VA Memorandum “Updated VA Information Security Rules of Behavior (VAIQ #7823189)”, September, 15, 2017, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

SCOPE OF WORK

The Contractor shall identify and resolve data discrepancies, anomalies and exceptions; complete data verification/validation resolution activities; duplicate record resolutions; and daily/monthly HC IdM Contract Workload Metrics Reports containing statistics relating to the HC IdM Program workload. Tasks will originate from the MVI and IdM Toolkit. A Toolkit task is a potential data anomaly identified within the MVI database such as potential duplicate records and identity trait changes that could impact the validity of the data and the correct matching of patient records.

The HC IdM Program Office has established policies and procedures for handling exceptions and managing the data within the MVI. The formal policies and procedures for use of the MVI and the IdM Toolkit may be found in Section 2.0, items 1-21. These procedures and guidelines define how to handle the many different exceptions and tasks, and the required documentation with details of their research, verifications, findings and resolution. The contractor shall follow HC IdM standard policies and procedures when operating in this environment.

The VA has an established internal training program for this requirement which will be required for all initial contractors after award. In the option years, subsequent contractor staff shall be trained by the contractor supervisor.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The period of performance shall be a 12 month base period, with four (4) 12-month option periods (if exercised).

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:

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:

PLACE OF PERFORMANCE

Tasks under this PWS shall be performed in VA facilities located in the Birmingham, AL, Office of Health Information Field Office and the Tuscaloosa, AL, Office of Health Information Field Office. Coverage shall be provided during the Business hours from 7:30 a.m. to 6:00 p.m.; Central Time; Monday through Friday. A minimum level of support (4 contractors) must be provided during all hours of operation.

TRAVEL

The Government does not anticipate travel under this PWS.

SPECIFIC TASKS AND DELIVERABLES

TASK 1: POTENTIAL DUPLICATE RECORD TASK

A potential duplicate record task is generated when a new record is added to the MVI, and the Threshold Score (TS) from the identity trait comparison performed by the matching algorithm is not high enough to allow the new record to auto-link to an existing record. The TS is high enough to be a potential match to the existing record but is not high enough to be an actual match, therefore it requires manual resolution.

The Contractor shall respond (responses shall be in the format of email, phone, Remedy or Toolkit software) to all routine inquiries from the user community within two business days.

For more information on this process, please refer to the following attachments referenced in the PWS section 2.0:

· Identity Management Toolkit (IdM TK) User Manual

· Override (OVR) Task Guidelines

· Toolkit (TK) Task Procedures

· Toolkit (TK) Template

. Deliverables 5.1:

A. Number of requests received will be documented on HC IdM Detailed Metrics Report (Reference Deliverable 5.3B). Daily, the contractor shall log the number of external support requests processed and categorized by assignment format (email/telephone/Remedy ticket). This documentation shall be provided in an existing VA format excel spreadsheet. (Historically 300-350 duplicate tasks per month)

1.1 TASK 2: IDENTITY TRAIT DATA ANOMALY RESOLUTION AND CHANGE/VERIFICATION REQUESTS

Identity Trait Data Anomaly resolution includes resolution of all exceptions described in the MVI Exceptions Processing document, with the exception of Potential Catastrophic Edits, Catastrophic Edits, Identity Theft Resolution, Potential Mismatches, and Inter-facility Consults.

The Contractor shall respond (responses shall be in the format of email, phone, Remedy or Toolkit software) to all routine inquiries from the user community within two business days.

For more information on this process, please refer to the following attachment referenced in the PWS section 2.0:

· Master Veteran Index (MVI) Exception Processing

Identity Trait Change/Verification Requests include all requests from sites to correct identity data, including legal name changes and gender changes. It also includes verification of demographic data via approved resources.

The Contractor shall follow a predefined procedure (See PWS Section 2) to verify and validate identity data as requests are received through the Program Office in the forms of e-mails, phone calls, Remedy tickets and web portals, internal and external to the VA, including Veterans Benefits Administration (VBA), DoD and other partners.

The Contractor shall respond (responses shall be in the format of email, phone, Remedy or Toolkit software) to all routine inquiries from the user community within two business days.

For more information on this process, please refer to the following attachments referenced in the PWS section 2.0:

· Toolkit (TK) Request Pilot Procedure

· Toolkit (TK) Request Procedures.

Deliverables 5.2:

A. Status of requests and actions taken will be identified on the HC IdM Detailed Metrics Report (Reference Deliverable 5.3B). Historically 1400-1600 per month

TASK 3: REPORTING FOR TASKS 5.1, 5.2

The Contractor shall complete the HC IdM Detailed Metrics Report daily and provide a monthly HC IdM Contract Workload Metrics Report (Reference Deliverable 5.3A).

Deliverable 5.3:

A. HC IdM Contract Workload Metrics Report

The HC IdM Contract Workload Metrics Report is distributed internally and externally. It shall provide complete and accurate statistics on resolved tasks and exceptions for the appropriate month. The data for the report is generated from the VA ToolKit and MVI Systems individually by the Contractor and then consolidated in this monthly report. This documentation shall be provided in an existing VA format excel spreadsheet. See attachment 21 referenced in the PWS section 2.0; this is not a representation of the workload required.

B. HC IdM Detailed Metrics Report

The HC IdM Detailed Metrics Report is an internal report documenting completely and accurately, the number of external support requests processed daily. The report shall categorize the completed work by assignment format (email/telephone/remedy ticket). The Contractor shall complete the documentation on a daily basis in an existing VA format excel spreadsheet. See attachment 20 referenced in the PWS section 2.0; this is not a representation of the workload required.

TASK 4: TRAINING PLAN

The VA has an established internal training program for this requirement which will be required for all initial contractors after award. In the option years, subsequent contractor staff shall be trained by the contractor supervisor. The contractor shall provide a training plan that will be implemented during the option years. The training plan shall include all subject matter from training provided by the Government at onset of contract and shall follow the attached training schedule for subsequent training. Contractor shall progress thru the training by meeting the minimum level of acceptability at each level as specified in the Training Timeline, reference PWS section 2.0, attachment 22.

Deliverable 5.4:

A. Training Plan: Draft due within 120 days after contract award, final due 30 days after acceptance of the draft. Updates to the training plan shall be made as needed throughout the life of the contract.

HISTORICAL DATA

Based on historical data, the Government estimates that eight (8) FTEs can process the following number of actions per month. This information is provided as information only and may not be a representation of the actual workload required:

GENERAL REQUIREMENTS

MINIMUM QUALIFICATIONS

The following minimum standards shall apply for all personnel performing under this contract and shall be maintained throughout the life of the contract.

A. On-site supervisor

Functional Responsibilities:

Performs analytical tasks designed to collect and analyze information. Develops briefings, presentations, training and reports. Possesses experience in specialty areas as required by the contract; works independently and can manage the work effort of other team members.

Minimum Experience/Education:

Proposed staff should possess at least a 2 year degree in healthcare related field, with Registered Health Information Administrator (RHIA) degree preferred and minimum 2 years related experience.

B. Analyst

Functional Responsibilities:

Supports other project team members. Performs analytical tasks designed to collect and analyze information. Has experience in specialty areas as required by the contract and works effectively and efficiently work with limited supervision.

Minimum Experience/Education:

Proposed staff should possess at least a 2 year degree in healthcare related field, with RHIA degree preferred, or minimum 1 year experience with maintenance/validation of data within a large scale (10M+ entry) database

ENTERPRISE AND IT FRAMEWORK

ONE-VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OI&T Technical Reference Model (One-VA TRM). One-VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. One-VA TRM includes the Standards Profile and Product List that collectively serves as a VA technology roadmap. Architecture, Strategy, and Design (ASD) has overall responsibility for the One-VA TRM.

FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Technical Architecture (ETA), http://www.ea.oit.va.gov/VA_EA/VAEA_TechnicalArchitecture.asp, and VA Identity and Access Management (IAM) approved enterprise design and integration patterns, http://www.techstrategies.oit.va.gov/enterprise_dp.asp. The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in the VA Handbook 6510 and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-3, VA Handbook 6500 Appendix F, “VA System Security Controls”, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the design and integration patterns. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-04-04, M-05-24, M-11-11, and NIST Federal Information Processing Standard (FIPS) 201-2. OMB Memoranda M-04-04, M-05-24, and M-11-11 can be found at: https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy04/m04-04.pdf, https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-24.pdf, and https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2011/m11-11.pdf respectively. Contractor delivered applications and systems shall be on the FIPS 201-2 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Veteran Index (MVI) to provision identity attributes, if the solution relies on VA user identities. MVI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable design pattern as outlined in VA Enterprise Design Patterns.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-3 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VAIQ# 7712300 Mandate to meet PIV requirements for new and existing systems. https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support the latest Internet Protocol Version 6 (IPv6) based upon the directives issued by the Office of Management and Budget (OMB) on August 2, 2005 (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf) and September 28, 2010 (https://cio.gov/wp-content/uploads/downloads/2012/09/Transition-to-IPv6.pdf). IPv6 technology, in accordance with the USGv6 Profile, NIST Special Publication (SP) 500-267 (https://www.nist.gov/programs-projects/usgv6-technical-basis-next-generation-internet), the Technical Infrastructure for USGv6 Adoption (http://www-x.antd.nist.gov/usgv6/index.html), and the NIST SP 800 series applicable compliance (http://csrc.nist.gov/publications/PubsSPs.html) shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and/or dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and/or dual stack (IPv6/ IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and/or dual stack (IPv6/ IPv4) operations. Guidance and support of improved methodologies which ensure interoperability with legacy protocol and services in dual stack solutions, in addition to OMB/VA memoranda, can be found at: https://www.voa.va.gov/documentlistpublic.aspx?NodeID=282.

TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M08-05 mandating Trusted Internet Connections (TIC) (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-05.pdf), M08-23 mandating Domain Name System Security (NSSEC) (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-23.pdf), and shall comply with the Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0 https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf.

STANDARD COMPUTER CONFIGURATION

The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, currently Windows 7 (64bit), Internet Explorer 11 and Microsoft Office 2010. In preparation for the future VA standard configuration update, end user solutions shall also be compatible with Office 365 ProPlus and Windows 10. However, Office 365 ProPlus and Windows 10 are not the VA standard yet and are currently approved for limited use during their rollout, we are in-process of this rollout and making them the standard by OI&T. Upon the release approval of Office 365 ProPlus and Windows 10 individually as the VA standard, Office 365 ProPlus and Windows 10 will supersede Office 2010 and Windows 7 respectively. Applications delivered to the VA and intended to be deployed to Windows 7 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using System Center Configuration Manager (SCCM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by the VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the United States Government Configuration Baseline (USGCB) and Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.

VETERAN FOCUSED INTEGRATION PROCESS (VIP)

The Contractor shall support VA efforts IAW the Veteran Focused Integration Process (VIP). VIP is a Lean-Agile framework that services the interest of Veterans through the efficient streamlining of activities that occur within the enterprise. The VIP Guide can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371. The VIP framework creates an environment delivering more frequent releases through a deeper application of Agile practices. In parallel with a single integrated release process, VIP will increase cross-organizational and business stakeholder engagement, provide greater visibility into projects, increase Agile adoption and institute a predictive delivery cadence. VIP is now the single authoritative process that IT projects must follow to ensure development and delivery of IT products

PROCESS ASSETT LIBRARY (PAL)

The Contractor shall utilize PAL, the OI&T-wide process management tool that assists in the execution of an IT project (including adherence to VIP standards). PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards or guides to assist project teams in facilitating their VIP compliant work.

SECURITY AND PRIVACY REQUIREMENTS

It has been determined that protected health information may be disclosed or accessed and a signed Business Associate Agreement (BAA) shall be required. The Contractor shall adhere to the requirements set forth within the BAA, referenced in Section D of the contract, and shall comply with VA Directive 6066.

POSITION/TASK RISK DESIGNATION LEVEL(S)

In accordance with VA Handbook 0710, Personnel Security and Suitability Program, the position sensitivity and the level of background investigation commensurate with the required level of access for the following tasks within the PWS are:

Position Sensitivity and Background Investigation Requirements by Task

The Tasks identified above and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal.

CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

Contractor Responsibilities:

1. The Contractor shall prescreen all personnel requiring access to the computer systems to ensure they maintain the appropriate Background Investigation, and are able to read, write, speak and understand the English language.

Within 3 business days after award, the Contractor shall provide a roster of Contractor and Subcontractor employees to the COR to begin their background investigations in accordance with the PAL template artifact. The Contractor Staff Roster shall contain the Contractor’s Full Name, Date of Birth, Place of Birth, individual background investigation level requirement (based upon Section 6.2 Tasks), etc. The Contractor shall submit full Social Security Numbers either within the Contractor Staff Roster or under separate cover to the COR. The Contractor Staff Roster shall be updated and provided to VA within 1 day of any changes in employee status, training certification completion status, Background Investigation level status, additions/removal of employees, etc. throughout the Period of Performance. The Contractor Staff Roster shall remain a historical document indicating all past information and the Contractor shall indicate in the Comment field, employees no longer supporting this contract. The preferred method to send the Contractor Staff Roster or Social Security Number is by encrypted e-mail. If unable to send encrypted e-mail, other methods which comply with FIPS 140-2 are to encrypt the file, use a secure fax, or use a traceable mail service.

1. The Contractor should coordinate with the location of the nearest VA fingerprinting office through the COR. Only electronic fingerprints are authorized. The Contractor shall bring their completed Security and Investigations Center (SIC) Fingerprint request form with them (see paragraph d.4. below) when getting fingerprints taken.

b. The Contractor shall ensure the following required forms are submitted to the COR within 5 days after contract award:

1) Optional Form 306

2) Self-Certification of Continuous Service

3) VA Form 0710

4) Completed SIC Fingerprint Request Form The Contractor personnel shall submit all required information related to their background investigations (completion of the investigation documents (SF85, SF85P, or SF 86) utilizing the Office of Personnel Management’s (OPM) Electronic Questionnaire for Investigations Processing (e-QIP) after receiving an email notification from the Security and Investigation Center (SIC).

The Contractor employee shall certify and release the e-QIP document, print and sign the signature pages, and send them encrypted to the COR for electronic submission to the SIC. These documents shall be submitted to the COR within 3 business days of receipt of the e-QIP notification email. (Note: OPM is moving towards a “click to sign” process. If click to sign is used, the Contractor employee should notify the COR within 3 business days that documents were signed via e-QIP).

1. The Contractor shall be responsible for the actions of all personnel provided to work for VA under this contract. In the event that damages arise from work performed by Contractor provided personnel, under the auspices of this contract, the Contractor shall be responsible for all resources necessary to remedy the incident.

1. A Contractor may be granted unescorted access to VA facilities and/or access to VA Information Technology resources (network and/or protected data) with a favorably adjudicated Special Agreement Check (SAC), completed training delineated in VA Handbook 6500.6 (Appendix C, Section 9), signed “Contractor Rules of Behavior”, and with a valid, operational PIV credential for PIV-only logical access to VA’s network. A PIV card credential can be issued once your SAC has been favorably adjudicated and your background investigation has been scheduled by OPM. However, the Contractor will be responsible for the actions of the Contractor personnel they provide to perform work for VA. The investigative history for Contractor personnel working under this contract must be maintained in the database of OPM.

1. The Contractor, when notified of an unfavorably adjudicated background investigation on a Contractor employee as determined by the Government, shall withdraw the employee from consideration in working under the contract.

Failure to comply with the Contractor personnel security investigative requirements may result in loss of physical and/or logical access to VA facilities and systems by Contractor and Subcontractor employees and/or termination of the contract for default.

Identity Credential Holders must follow all HSPD-12 policies and procedures as well as use and protect their assigned identity credentials in accordance with VA policies and procedures, displaying their badges at all times, and returning the identity credentials upon termination of their relationship with VA.

Deliverable:

A. Contractor Staff Roster

METHOD AND DISTRIBUTION OF DELIVERABLES

The Contractor shall deliver documentation in electronic format, unless otherwise directed in Section B of the solicitation/contract. Acceptable electronic media include: MS Word 2000/2003/2007/2010, MS Excel 2000/2003/2007/2010, MS PowerPoint 2000/2003/2007/2010, MS Project 2000/2003/2007/2010, MS Access 2000/2003/2007/2010, MS Visio 2000/2002/2003/2007/2010, AutoCAD 2002/2004/2007/2010, and Adobe Postscript Data Format (PDF).

PERFORMANCE METRICS

The table below defines the Performance Standards and Acceptable Levels of Performance associated with this effort.

The COR will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the Contractor is performing the services required by this PWS in an acceptable level of performance. The Government reserves the right to alter or change the surveillance methods in the QASP at its own discretion. A Performance Based Service Assessment will be used by the COR in accordance with the QASP to assess Contractor performance.

FACILITY/RESOURCE PROVISIONS

The Government will provide office space, telephone service and system access when authorized contract staff work at a Government location as required in order to accomplish the Tasks associated with this PWS. All procedural guides, reference materials, and program documentation for the project and other Government applications will also be provided on an as-needed basis.

The Contractor shall request other Government documentation deemed pertinent to the work accomplishment directly from the Government officials with whom the Contractor has contact. The Contractor shall consider the COR as the final source for needed Government documentation when the Contractor fails to secure the documents by other means. The Contractor is expected to use common knowledge and resourcefulness in securing all other reference materials, standard industry publications, and related materials that are pertinent to the work.

VA may provide remote access to VA specific systems/network in accordance with VA Handbook 6500, which requires the use of a VA approved method to connect external equipment/systems to VA’s network. Citrix Access Gateway (CAG) is the current and only VA approved method for remote access users when using or manipulating VA information for official VA Business. VA permits CAG remote access through approved Personally Owned Equipment (POE) and Other Equipment (OE) provided the equipment meets all applicable 6500 Handbook requirements for POE/OE. All of the security controls required for Government furnished equipment (GFE) must be utilized in approved POE or OE. The Contractor shall provide proof to the COR for review and approval that their POE or OE meets the VA Handbook 6500 requirements and VA Handbook 6500.6 Appendix C, herein incorporated as Addendum B, before use. CAG authorized users shall not be permitted to copy, print or save any VA information accessed via CAG at any time. VA prohibits remote access to VA’s network from non-North Atlantic Treaty Organization (NATO) countries. The exception to this are countries where VA has approved operations established (e.g. Philippines and South Korea). Exceptions are determined by the COR in coordination with the Information Security Officer (ISO) and Privacy Officer (PO).

This remote access may provide access to VA specific software such as Veterans Health Information System and Technology Architecture (VistA), ClearQuest, PAL, Primavera, and Remedy, including appropriate seat management and user licenses, depending upon the level of access granted. The Contractor shall utilize government-provided software development and test accounts, document and requirements repositories, etc. as required for the development, storage, maintenance and delivery of products within the scope of this effort. The Contractor shall not transmit, store or otherwise maintain sensitive data or products in Contractor systems (or media) within the VA firewall IAW VA Handbook 6500.6 dated March 12, 2010. All VA sensitive information shall be protected at all times in accordance with VA Handbook 6500, local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this PWS. The Contractor shall ensure all work is performed in countries deemed not to pose a significant security risk. For detailed Security and Privacy Requirements (additional requirements of the contract consolidated into an addendum for easy reference) refer to ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED and ADDENDUM B - VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE.

GOVERNMENT FURNISHED PROPERTY

The Government will provide each contractor with a government furnished telephone, desktop computer along with access to a local/network printer and fax machine. This equipment is for office use only and is not to be removed from the VA facility. They will not provide IT accessories including but not limited to Mobile Wi-Fi hotspots/wireless access points, additional or specialized keyboards or mice, laptop bags, extra charging cables, extra PIV readers, peripheral devices, additional RAM, etc. The Contractor is responsible for providing these types of IT accessories in support of the contract as necessary and any VA installation required for these IT accessories shall be coordinated with the COR.

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

Cyber and Information Security Requirements for VA IT Services The Contractor shall ensure adequate LAN/Internet, data, information, and system security in accordance with VA standard operating procedures and standard PWS language, conditions, laws, and regulations. The Contractor’s firewall and web server shall meet or exceed VA minimum requirements for security. All VA data shall be protected behind an approved firewall. Any security violations or attempted violations shall be reported to the VA Program Manager and VA Information Security Officer as soon as possible. The Contractor shall follow all applicable VA policies and procedures governing information security, especially those that pertain to certification and accreditation.

Contractor supplied equipment, PCs of all types, equipment with hard drives, etc. for contract services must meet all security requirements that apply to Government Furnished Equipment (GFE) and Government Owned Equipment (GOE). Security Requirements include: a) VA Approved Encryption Software must be installed on all laptops or mobile devices before placed into operation, b) Bluetooth equipped devices are prohibited within VA; Bluetooth must be permanently disabled or removed from the device, unless the connection uses FIPS 140-2 (or its successor) validated encryption, c) VA approved anti-virus and firewall software, d) Equipment must meet all VA sanitization requirements and procedures before disposal. The COR, CO, the PM, and the Information Security Officer (ISO) must be notified and verify all security requirements have been adhered to.

Each documented initiative under this…