Draft PWS_VISN 7_Philips VUE PAC Services Support.docx

Dedicated Admin for Philips Vue PACS Support

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

VISN 7 Healthcare Technology Management

Dedicated Admin for Philips Vue PACS Support

Date: 05/13/2024

(VA-24-00002236)

PWS Version Number: 1.0

Contents

BACKGROUND

Veterans Integrated Service Network (VISN) 7 employs a proprietary networked brand name Philips Vue Picture Archiving Communication System (PACS) across all eight of its VA Medical Centers (VAMCs) located in Decatur, GA; Augusta, GA; Birmingham, AL; Charleston, SC; Columbia, SC; Dublin, GA; Montgomery/Tuskegee, AL; and Tuscaloosa, AL. The overarching VISN 7 Philips Vue PACS arrangement also includes a structured reporting and dictation system (Vue Reporting), an enterprise-wide read-only application for use by non-Imaging personnel (Vue Motion), and an imaging informatics & analytics application (Performance Bridge).

The VA VISN 7 requires the Radiology PACS to be operational 24x7 to enable Radiologists to view images and complete reports for routine and emergent exams. Delays in access to images and the reporting infrastructure may cause adverse impact on patient care. Radiologists must be able dictate reports via interface with the existing brand name Philips Vue and send the resulting report back to the site’s VistA system. Warranty coverage includes service maintenance for hardware (200 workstations, 396 monitors, servers, etc.) and software (Vue PACS 12.2.8 client, Vue PACS (WFM) Cluster 12.2.8, Vue Motion, Vue Explorer, Web Reporting, OrthoView, Carestream EIS, SQL Server 2016 Database Engine Services. In addition to warranty coverage, VISN 7 is requesting a dedicated Philips PACS Admin for improved response times, downtime coordination, and applications support.

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 2006

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

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

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

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

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

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

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

13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

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

15. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

16. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

17. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021

18. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019

19. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle,” March 22, 2010

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

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

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

23. OIT 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

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

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

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

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

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

29. VA Directive 6300, “Records and Information Management,” September 21, 2018

30. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

31. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

32. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

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

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

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

36. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

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

38. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

39. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

40. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

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

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

43. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

44. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

45. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

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

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

48. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

49. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

50. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

SCOPE OF WORK

The contractor shall provide a dedicated PACS Admin for VISN 7 Vue PACS sustainment, which includes application issue resolution, software configuration, 200 licenses, upgrades, software patches, direct customer support, clinical training, troubleshooting and resolution of all issues with Vue PACS. Dedicated PACS Admin shall coordinate directly with clinical end-users for this work. Skillset should be a hybrid of Clinical Consultant and Technical Consultant, but primarily clinical.

Contractor to provide resume of proposed candidate. Candidate should have minimum 12 months experience as clinical consultant with Philips Vue PACS application (Version 12).

Troubleshooting visits shall be conducted to assess and diagnose issues onsite as necessary. Additional visits shall be conducted for new software releases to ensure new features are successfully tested and deployed. In addition to troubleshooting and enhancement visits, a minimum of two scheduled on-site health visits shall be conducted at each VISN 7 VA facility annually.

Recurring monthly meetings shall be conducted with all VISN 7 PACS stakeholders. Recurring weekly meetings shall be conducted with the VISN 7 PACS admin group. Recurring monthly meetings shall be conducted with each individual site to review open support cases and ensure site agreement before cases are closed.

Dedicated PACS Admin’s normal business hours shall be Monday – Friday, 8:00 a.m. - 4:30 p.m. EST. Dedicated PACS Admin shall respond to unscheduled downtime issues outside of normal business hours (WHEN: Weekends, Holidays, Evenings, Nights).

Dedicated PACS Admin shall request and utilize a Personal Identity Verification (PIV) card and Non-Mail Enabled Account (NMEA) for self-sufficient software installations. With these tools, dedicated PACS Admin shall coordinate directly with Healthcare Technology Management (HTM) and Office of Information and Technology (OIT) as needed to meet the aforementioned work.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Period of Performance shall be for one 12-month base year, with four additional 12-month option periods.

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

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

Under current definitions, five 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

The tasks under this PWS shall be performed in VA facilities located in Table 1 below and at the contractor’s remote site as needed. Routine service support & maintenance, troubleshooting, remote upgrades & patching may be done remotely. Any installation, upgrade, or repair of physical hardware applicable to this contract shall be performed on site by the contractor or contractor’s representative in coordination with local VISN 7 Healthcare Technology Management (HTM) personnel.

TABLE 1

Decatur, GA 30033-4004

Augusta, GA 30904-2608

Birmingham, AL 35233-1927

Charleston, SC 29401-5799

Columbia, SC 29209-1638

Dublin, GA 31021-3620

Montgomery, AL 36109-3725

Tuscaloosa, AL 35404-5099

TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort. A minimum of two scheduled on-site health visits shall be conducted at each VISN 7 VA facility annually. Additionally, troubleshooting visits shall be conducted to assess and diagnose issues onsite as necessary and additional visits shall be conducted for new software releases to ensure new features are successfully tested and deployed.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

PROJECT MANAGEMENT

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 due thirty days after contract (DAC) (not recurring deliverable)

REPORTING REQUIREMENTS

The contractor shall provide the Contracting Officer’s Representative (COR) with weekly written progress reports. These are due to the COR by end of each week.

The progress report will cover all work completed during the preceding week and will present the work to be accomplished during the subsequent week. This report will also identify any problems that arose and a statement explaining how the problem was resolved. This report will also identify any problems that have arisen but have not been completely resolved with an explanation.

After any unscheduled downtime, Dedicated PACS Admin shall provide an After Action Report (AAR) describing the root cause of issue and any preventative steps Philips shall take.

Deliverable:

Weekly Progress Report due five days after Kickoff meeting and updated weekly thereafter After Action Report

TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 30 days after TO 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) 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 VISN 7 Vue PACS Admin Contract.” The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) 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) 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.

Deliverable:

a. Kickoff Meeting Tentative Agenda due thirty days after contract (not recurring deliverable)

b. Kickoff Meeting Final Agenda due thirty days after receiving review comments from VA project manager (PM)

c. Kickoff Meeting Presentation Slides, or any other material presented during meeting, due two days before scheduled kickoff meeting (not recurring deliverable)

d. Kickoff Meeting Updated Presentation Slides, with Summary Report slide, due three days after meeting (not recurring deliverable)

e. Kickoff Meeting Minutes due three days after meeting (not recurring deliverable)

PRODUCT CHARACTERISTICS AND REQUIREMENTS

The Current environment consists of the following:

The below notations identify where the current software is hosted and its function. VA may, at its own discretion, elect to remove software in accordance with its bona fide need. Any changes shall be notated via a bilateral modification.

Philips VUE PACS software is an advanced radiology diagnostic application that provides a comprehensive, full-resolution diagnostic presentation of current and prior procedures and associated clinical information. Contractor shall provide unlimited viewing licenses for Diagnostic Radiology Client application. Vue PACS includes the following applications.

· Global Vue Motion

· Vue Reporting

· Orthoview

· Performance Bridge

· CD Direct The contractor shall upgrade to the latest version of these software upon implementation of the SLA requirements and maintain in accordance with PWS Sections 6.3 and 6.4.

Description OF SERVICES

HL7 INTEGRATION

All “Health Level 7” (HL7) Radiological Information System (RIS) shall be integrated with VistA at each VISN 7 facility. HL7 interfaces shall include processing orders from VistA and resulting messages sent back to VistA, and a Technologist Worklist that provides reconciliation of metadata by technologists on PCs.

WEB DISTRIBUTION AND REMOTE VIEWING

Contractor shall:

1. Provide Web distribution through the Vue enterprise viewer (chronological timeline with reports, status, and presentation states available from standard PCs)

2. Provide Unlimited view rate for all studies with Vue Motion or Vue PACS

3. Provide for Unlimited concurrent users on Vue Motion with full fidelity (no loss compressed or key images)

4. Provide CD Burning capabilities at both the main facilities and their designated Community Based Outpatient Clinics (CBOCs) for patient studies for Release of Information (studies, reports, presentation states, help menu, and viewing software).

INTEGRATION AND CUSTOMIZATION

The Contractor shall provide Application Program Integration (API) toolkit for integrating third-party applications as needed. Provide Integration to the VISN 7 secure DICOM image exchange system for bi-directional sharing of image studies & SR between VISN 7 and community care providers.

SUPPORT SERVICES

The contractor shall maintain all hardware, software for the applications noted under PWS Section 5.2, and any upgrades thereto as a result of PWS Section 5.3. Operating system patches, when at the recommendation of Philips and approved by the VA, shall be installed as made available from third party vendors on a monthly schedule unless deemed to be a critical security vulnerability. Anti-virus shall be executed nightly and updated to include any new virus definitions and product specific updates when available. Systems will be set up to sync with the VA national time server to ensure that all systems have a common time reference. Contractor will proactively monitor system health with real-time server status monitoring and will take corrective/preventive action when system performance is outside of normal operating limits.

Further, the Contractor shall ensure meeting of the below:

1. Conformance Standards:

The Contractor shall provide services and material to ensure that the equipment functions in conformance with the latest requirements of NFPA-99, The Joint Commission (TJC), National Electric Code (NEC), Federal and VA information security specifications and requirements as applicable.

a. The equipment shall be maintained such that it meets or exceeds the performance specifications as established in the OEM’s technical specifications.

b. The Contractor shall ensure that all hardware & software upgrades meet applicable VA information and network security requirements for placement on the VA network. Specifically, but not all-encompassing, the Contractor shall maintain current Enterprise Risk Analysis (ERA) and Technical Resource Manual (TRM) approval for all products covered by this contract. Contractor shall coordinate with the COR and VISN 16 Biomedical Engineering personnel for completing & obtaining approval documentation.

2. System Monitoring and Help Desk

Contractor shall provide Active system monitoring with in-house support desk 24x7x365. 48-hour onsite guarantee for hardware repair/replacement. All service/updates will be performed during normal hours of coverage unless requested or approved by Facility POC designee.

Hours for Support shall be:

· For Clinical Application Support and Education: 24 hours a day, 7 days a week and 365 days a year (24x7x365).

· Technical Support: Contractor shall provide technical support 24 hours a day, 7 days a week, 365 days a year. Contractor shall provide dedicated help desk for VISN 7 (or all VA as a minimum).

· Response Time: Contractor must respond to a phone call within 4 hours for any call. For emergency technical support issues, Contractor must provide immediate technical support.

Service Manuals:

The contractor shall obtain, have on file, and make available to its PACS Admin all operational and technical documentation, (such as: operational and service manuals, schematics, and parts list), which are necessary to meet the performance requirements of this contract. The location and listing of the service data manuals, by name, and/or the manuals themselves will be provided to the COR upon request.

DISASTER RECOVERY

The Contractor shall utilize the existing local PACS and dual data center for future support and disaster recovery or shall develop, propose, & maintain an alternate offsite Disaster Recovery System at a dedicated VA disaster recovery site. No additional funds will be provided by VISN 7, above what is included for maintenance, support, & upgrades for the existing data centers. Any alternate system developed shall be acceptable to VISN 7 and approved by VA OIT and shall include real-time backup of image files, ensure continuous log files are updated, ensure an incremental database backup at least twice daily, and ensure weekly full database backups are completed. Contractor will provide a process for rapid recovery of the production environment in the event of catastrophic failure or destruction of the production environment.

HARDWARE, STORAGE, AND REPAIR PARTS

Contractor shall provide all parts for maintenance, repair, and sustainment of the PACS. The Contractor shall have ready access to all OEM parts, including unique and/or high mortality replacement parts. All parts supplied shall be new from the OEM as required under VAAR 852.212-71. All parts shall perform identically to the OEM specifications and not invalidate the Food and Drug Administration (FDA) certification.

TRAINING

The contractor shall provide Original Equipment Manufacturer (OEM) approved and validated training to the clinical staff on all components of the PACS and VNA systems and software. All educators shall have current certification from the OEM. Education shall be provided for any major software release and be scheduled at the request of the clinical or PACS administration staff. Training shall ensure that clinical end users and PACS Administrators at each facility are capable of fully using and supporting the PACS efficiently and effectively. Expected minimum training requirements are listed below:

PACS Administration Training:

· One session with a minimum of three days on-site per facility, to be conducted at the time of PACS upgrade for up to six individuals per site.

· Training Materials shall contain “how to” guides, trouble shooting checklists, etc.

PACS Application Support Training:

· One session with a minimum of three days on-site for two individuals, to be conducted at the time of PACS upgrade, for an indefinite number of clinical end users (imaging technologists, residents, and radiologists). Training shall be individual, over-the-shoulder training unless a formal structured training is agreed to by the facility’s imaging service leadership and approved by the COR.

· Training Materials shall contain “how to” guides, trouble shooting checklists, etc.

Deliverables

A. PACS Administration Training Material B. PACS Application Support Training Material Facility reporting REQUIREMENTS The contractor shall report to Biomedical Engineering to "check-in" upon arrival and prior to performance of work at any location covered under this contract. This check-in is mandatory and can be accomplished in person or by phone contact. When the service(s) is/are completed, the dedicated PACS Admin shall document the services rendered on a legible Engineering Service Report (ESR). The Dedicated PACS Admin shall check out with the Biomedical Engineering Department (location to be specified at time of contract award) and submit the ESR(s) to the COR. All ESRs shall be submitted to the equipment user for an "acceptance signature" and to the COR or designee for an "authorization signature." If the COR or designee is unavailable, a signed accepted copy of the ESR will be sent to the COR within 5 business days of work completion.

OPTION PERIOD ONE

If exercised, the Contractor shall provide all services listed under PWS Sections 5.1 through 5.8 upon completion of the Base Period.

OPTION PERIOD TWO

If exercised, the Contractor shall provide all services listed under PWS Sections 5.1 through 5.8 upon completion of the Option Period One.

OPTION PERIOD THREE

If exercised, the Contractor shall provide all services listed under PWS Sections 5.1 through 5.8 upon completion of the Option Period Two.

OPTION PERIOD FOUR

If exercised, the Contractor shall provide all services listed under PWS Sections 5.1 through 5.8 upon completion of the Option Period Three.

ENTERPRISE AND IT FRAMEWORK

VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The 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. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the 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), https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp, and VA Identity and Access Management (IAM) approved enterprise design and integration patterns, https://www.oit.va.gov/library/recurring/edp/index.cfm. 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 VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, 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-05-24, M-19-17, and NIST Federal Information Processing Standard (FIPS) 201-2. OMB Memoranda M-05-24 and M-19-17 can be found at: https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf, and https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.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 Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI 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 VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

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 Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance 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 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 dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents). Any deviations must be approved by the VA TIC 3.0 Working Group at vaoisesatic30team@va.gov.

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 10 (64bit), Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 10 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 Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by 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) AND PRODUCT LINE MANAGEMENT (PLM)

The Contractor shall support VA efforts IAW the updated Veteran Focused Integration Process (VIP) and Product Line Management (PLM). The major focus of the new VIP is on Governance and Reporting and is less prescriptive, with a focus on outcomes and continuous delivery of value. Product Line Management (PLM) is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. The PLM Playbook pivots from project-centric to product-centric delivery and contains descriptive practices that focuses on outcomes. The PLM Playbook contains a set of “plays” that implement Development, Security, and Operations (DevSecOps) principles and processes such as automated development, continuous integration/continuous delivery, and release on demand. The PLM Playbook details how product lines implement Lean-Agile principles, methods, practices, and techniques through levels of maturity. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.

PROCESS ASSET LIBRARY (PAL)

The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL scope includes the full spectrum of OIT functions and activities, such as VIP project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. The Contractor shall follow the PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at https://www.va.gov/PROCESS/artifacts/maps/process_CONB_ext.pdf. The main PAL can be accessed at www.va.gov/process.

AUTHORITATIVE DATA SOURCES

The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:

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

2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.

3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor and vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.

4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data.

5. Interfacing with Vet360 to access personal contact information, if the solution relies on VA Veteran personal contact information data. Vet360 is the authoritative source for VA Veteran Personal Contact Data.

6. Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for Qualifying Active Duty military service in VA.

SOCIAL SECURITY NUMBER (SSN) REDUCTION

The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the ICN in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA Master Person Index (MPI) for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA or whenever the VA system providing the information has not fully transitioned from using SSNs to using ICNs for patient identification.

SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the provision of all software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

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. If a BAA already exits, the Contractor shall maintain the MOU-ISA and BAA.

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: Microsoft 365, MS Word 2000/2003/2007/2010/2019, MS Excel 2000/2003/2007/2010/2019, MS PowerPoint 2000/2003/2007/2010/2019, MS Project 2000/2003/2007/2010/2019, MS Access 2000/2003/2007/2010, MS Visio 2000/2002/2003/2007/2010/2019, 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 contractor shall provide all maintenance, support, and ongoing sustainment for the existing and upgraded complete VISN 16 Vue PACS system as described herein. Support shall include furnishing and maintaining all necessary server & storage hardware, software licensing & upgrades, and professional & installation services required to maintain the complete VISN 16 PACS at > 99.99% uptime.

2. Efficient and…