S02-36C24725Q0922-Getwell Network.docx

36C24725Q0922

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

UEI:

EFT:

PHONE:

FAX:

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

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

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

25. ACCOUNTING AND APPROPRIATION DATA

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

ARE

ARE NOT ATTACHED.

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

ARE

ARE NOT ATTACHED

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

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

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

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

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

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

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

08-25-2025 Michelle Bocage 404-321-6111 08-28-2025

0900 AM

EDT

Department of Veterans Affairs VISN 7 Network Contracting Office 3 FL Directors Office 3700 Crestwood Parkway Duluth GA 30096

X

513210

Net 30

N/A

Department of Veterans Affairs Atlanta VA Medical Center 1670 Clairmont Rd.

Decatur GA 30033 Department of Veterans Affairs VISN 7 Network Contracting Office 3 FL Directors Office 3700 Crestwood Parkway Duluth GA 30096

Austin Payment Center Department of Veteran Affairs

PO Box 149971 Austin TX 78714-8971

(877) 353-9791

(512) 460-5545

See CONTINUATION Page Please See Statement Work All quotes are due 9-19-2025 9:00 AM EST

See CONTINUATION Page

Michelle Bocage Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR:

b. GOVERNMENT: Contracting Officer 36C247 Department of Veterans Affairs VISN 7 Network Contracting Office 3 FL Directors Office 3700 Crestwood Parkway Duluth GA 30096

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

3. INVOICES: Invoices shall be submitted in arrears:

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

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

Page 1 of

STATEMENT OF WORK

1. INTRODUCTION/BACKGROUND:

The Atlanta VA Healthcare System (Atlanta VAHCS) has developed and promoted patient centered care concepts, programs, and initiatives that bring a cultural transformation and improve clinical efficiency and outcomes. The Atlanta VAHCS will maintain the licenses for the GetWellNetwork Interactive Patient Care (IPC) System for 275 bed locations. GetWellNetwork has been procured by the VHA Office of Patient Centered Care & Cultural transformation. The GetWellNetwork is the only provider of IPC purchased by a VA National Office. The system has now expanded to over 71 VA hospitals nationally and has established Veteran-specific features and resources in the GetWellNetwork IPC system. Lastly, GetWellNetwork provides interactive patient care solutions through evidence based clinical pathway outcomes and web-based management and reporting tools.

The scope of work includes:

1. Interactive Patient Care (IPC) Inpatient – Patient Education/Engagement System (Capable of Inpatient, Outpatient, and Home applications)

2. Interactive Patient Care (IPC) Internet Connectivity

3. Dedicated Client Success Manager

4. Interactive Patient Care (IPC) Inpatient Basic Edition Licenses – Patient Education/Engagement System for 275 bed locations.

5. Interactive Patient Care (IPC) Inpatient Pathway Edition with Interactive Digital Whiteboard maintenance for 275 locations.

6. Interactive Patient Care (IPC) Clinical Consulting Dedicated Model – Full-time on-site support person working as the Client Success Manager

Proposals for these items should meet all functional requirements described herein.

EVALUATION CRITERA:

Must be able to meet all criteria as indicated here within this Statement of Work. No deviations or substitutions will be accepted.

2. PERFORMANCE PERIOD:

The period of performance shall be a 12-month base with four 12 month option periods to provide annual licenses agreement for software license, remote support, IPC advisory/support services, internet, and interfaces.

3. TRAVEL:

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to provide management briefings or other consultations as necessary. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

4. SPECIFIC TASKS AND DELIVERABLES:

In delivery of the described services the contractor will not be required to install coax, power or entertainment wiring. Additionally, all work will be completed during normal business hours, Monday through Friday (excluding holidays) from 7:00 am to 4:30 pm. No asbestos or lead abatement work is expected. Except as specified for each Atlanta VAHCS location all tasks will apply to both the Decatur and Carrollton, Georgia locations. The contractor shall perform the following:

a. Provide and implement one (1) care plan of a Digital Care Management system based on the requirements and functionalities of this Performance Work Statement

b. Allow for the government to activate additional licenses and implementations through optional tasks. Government requirements regarding Implementation, system support and digital care management system functionality outlined in this SOW apply to any new licenses the government activates.

c. Maintain responsibility for the on-premise design and architecture as approved by a FedRamp Certification

d. Vendor must have or receive a FedRamp Certification within 3 months of contract award date

e. Provide remote technical support and ongoing maintenance of the Digital Care Management system

f. Provide training for use of the Digital Care Management system

g. Provide software updates and ongoing software patches as required

Acute Care (Decatur, GA) Address: 1670 Clairmont Rd, Decatur, GA 30033 POC: Michael Cox, 404-321-6111, ext. 207633

CLC (Carrollton, GA) Address: 180 Martin Road, Carrollton, GA 30117 POC: Adam Doty, 404-889-7966

Deliverables:

A. Training for IPC system

4.1 PROJECT MANAGEMENT PROFESSIONAL SERVICES

· If any additional authorized modifications to the contract are needed regarding project management professional services, The Contractor shall provide a single point of contact for the implementation to be responsible for all project management activities.

· The Contractor shall draft a Project Management Plan (PMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of the contract. The PMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support. The PMP shall include the contractor’s plans for managing all subcontractors, if applicable.

· The Contractor shall provide an initial PMP to the COR or designee for concurrence and shall be updated and maintained throughout the period of performance. The PMP will include, but not be limited to:

· Project Schedule to include milestones, deliverables, and critical path

· Training Plan

· Risk Management Plan

· Operations and Maintenance Plan

· Project Closeout Activities/Procedures

· The Contractor shall provide weekly progress reports including schedule updates and all work completed during the period. The reports shall identify any problems that arose and a description of how the problems were resolved, or a resolution plan. The Contractor shall monitor performance against the PMP and report any deviations. It is expected that the Contractor will remain in communication with the VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

· The Contractor shall provide the COR with detailed installation progress in the weekly progress reports, and a summary of the task order deliverables.

Deliverables:

A. Project Management Professional Services for implementation of IPC system

4.2 INTERACTIVE PATIENT CARE SYSTEM:

The Contractor shall provide, install and configure an Interactive Patient Care System to educate and engage patients in their care.

a. Work with Government to select/confirm the Initial Care Plan and create an appropriate enrollment workflow, including automated trigger events and Care Plan mapping, inline with established best practices.

b. Configure, validate and activate the following interfaces:

i. One (1) HL7 ADT or SIU feed for veteran enrollment

c. Provide a government Review Cycle as required to match Care Plan content to government unique needs.

i. Support government branding with logos and personalized messages with VA and physician-specific greetings where available in the application.

d. Conduct end-to-end functionality testing prior to Initial Care Plan Readiness

e. Provide up to two (2) remote Training Sessions (per Service Line) for First Responders, Technical and System Manager users.

Contractors must be able to demonstrate all required characteristics exist in production and should specifically describe how the contractor’s functionality meets each requirement.

7.1 Patient Experience Configurable for each individual patient

7.2 Patient Experience Configurable for each individual patient

· Patient Experience focused on Outcomes – patient experience should have gamification functionality to show patient tasks they've completed and remaining unfinished tasks

· IPC System should be customizable to the patient at each location based on information received through the VistA/CPRS interface

· IPC Vendor must offer the ability for patients to interact with the software using assistive adaptor technology such as sip and puff controls.

· Low Visibility Experience with Screen Reader technology for blind Veterans

7.3 Patient Education

7.4 Patient Alerts - Overlaid on top of TV Program or Movie

· The size and shape of patient alerts should be configurable to overlay on top of television content and shall not take up the entire TV screen, switch channels, or TV inputs.

· Alerts should be configurable within a management console control panel accessible by VA staff.

7.5 Web Based Management Console

· Executive / Administrative Reporting within the management console

· Real-Time Summary Dashboard with unit/date range filter capabilities showing utilization, Patient Satisfaction Levels, Comments, and Service Requests within the management console

· Real Time System & Content Changes within the management console

· Patient Profiles showing education completion, satisfaction, and discharge readiness within the management console

7.6 Patient Feedback Capability

· Patients should be able to access survey questions in on-demand menu

· IPC System shall be able to prompt patients without taking them completely off their screen to provide feedback at pre-programmed days/times.

· Questions should be capable of being limited based on patient admission/discharge so as not to over prompt a single patient.

· Feedback questions shall be able to be customized by unit.

· Negative feedback should be sent to Staff immediately by email or communication device.

· Web-Based Reports should be available through the management console with a summary patient satisfaction dashboard filterable by unit/date range.

· Follow up questions should be capable of dynamically changing based on patient’s response to a previous question.

7.7 Content Flexibility

· Ability to configure IPC system with custom on-demand and alert content with VA initiatives and content (i.e. Whole Health Model of Care)

7.8 Client Community Website

· Contractor should include unlimited user access to a contractor managed IPC community website for sharing of IPC implementation best practices. Community website should be dedicated to VA clients.

7.9 Staff to Patient Messaging

· Ability for staff to send one-way messages (customizable canned or free text) to the patient from the management console.

7.10 Patient Portal

· Contractor must have capability to allow patients to login into the patient portal (My HealtheVet) in the hospital and at home to access education content assigned specifically to them in any previous VA encounter with the vendor’s inpatient or outpatient IPC system (potential future add on; not required to be included in this PWS).

7.11 VistA/CPRS Interfaces

· Interfaces must include:

· Admissions, Discharge, and Transfer (ADT) Interface (from VistA)

· Education Orders (from VistA/CPRS to IPC System) Interface

· Education Results (from IPC System to VistA/CPRS) Interface

· LDAP (Management Console Login) Interface

· Medications Interface

· Dietary Interface (if the medical center has installed the appropriate dietary system prerequisites)

· Clinical Communication Device Interfaces (e.g. Vocera)

· VistA/CPRS Interface with simultaneous Internet Access from the IPC System patient experience

· Patients cannot access the internet through the VHA network.

· Describe and provide a network diagram demonstrating their system’s capability to provide patients with internet access while interfacing with the VistA/CPRS.

· Vendor must provide OIT Enterprise approval documentation for network design proposed.

7.12 Nursing Tools at the bedside

· The IPC System should offer clinical tools at the bedside that complement nurse/physician workflow at the bedside.

· Nursing bedside login to quickly view education completion without having to review CPRS documentation

· Nursing bedside login to start patient facing workflows

· Nursing bedside login to view and customize generic images to save to the patient’s personalized education menu

Deliverables:

A. Content design: This solution shall be designed to reflect how the Medical Center operates and fully customized to our specifications. The system must be built and implemented such that it reflects the values, goals, and objectives of the Medical Center. The leadership and staff of the Medical Center, as primary stakeholders, are critical to ensuring that this solution meets all their criteria. While overall project management will be handled by the contractor, decisions of the Medical Center stakeholders will drive the design of each of its individual components. The Contractor shall develop the menu options and programming in accordance with the facilities decisions. The Contractor shall discuss IPC with the medical center leadership team and guide them in selecting three key outcome (i.e. performance improvement) priorities to be achieved through the implementation of the IPC program.

B. The IPC functionality, menus, interfaces and content shall be defined and configured to drive the outcomes sought by the organization.

C. One-year software licenses: Beginning at the time of system acceptance by the Government (date of approval for 1st bed in 1st unit to go-live), a one-year license for all software. The Contractor shall provide software licenses for operation of the software provided in the base period of the order. These licenses include the individual license for the IPC System at each television location.

D. Contractor will be responsible for procuring and managing the installation of all equipment, parts, software, and software licenses to complete installation.

4.3 INTERACTIVE PATIENT CARE – ADVANCED PATHWAY SOFTWARE UPGRADE:

The Contractor shall provide, install and configure a software upgrade to provide advanced functionality that will prompt and engage the patient proactively in their care process according to algorithms that provides different alerts and/or content based on patient actions taken within the IPC system or clinician actions in the management console or nursing tools.

Contractors should specifically describe how the contractor’s functionality meets each requirement.

Following Implementation, the Vendor will continue to manage content and reporting needs using the following approach for the remainder of the term.

a. Continue to configure, validate, and activate additional Care Plans at an annual rate not to exceed the total number of Care Plans licensed. Each physician-specific Configuration counts toward this total.

Configuration in excess of the following will require additional scoping and fees: (i) the annual allotment of Care Plan Configurations, (ii) the contracted total of Care Plans, or (iii) twenty-five (25) total annual Configuration hours.

1. The Contractor shall provide system support throughout the term of the software licenses including remote help desk support and regional client support management to both end-users and VA personnel. Support will include routine system updates and 24x7x365 Help desk support provided remote through the Vendor call center. Contractor will provide a regional support team responsible for the overall success of the Digital Care management Platform at the medical center.

1. Provide reports. Any data or analysis requested beyond the following will be separately scoped and quoted:

i. Monthly Impact Report - Snapshot of how they system is providing value to the government

ii. Core Metrics Report (aggregate) - Data includes total Veterans enrolled on a Loop, total Veterans activated, engagement detail, Veteran satisfaction rates, and PRO (patient reported outcomes) response rates (if applicable)

iii. Core Metrics Report (by month) - Same as above but broken down by month to identify trends

iv. Loop Level Raw Data - Detailed Veteran level data for each Loop created

v. PRO Data - Raw survey data, responses, and scores can be downloaded directly from the Loop PRO dashboard

vi. Veteran Satisfaction Data - Raw response data from the Veteran satisfaction survey can be downloaded directly from the Loop Patient Satisfaction Dashboard

1. Provide unlimited access to use any existing surveys in Vender PRO survey library.

i. Capability to create new or custom PRO surveys may be developed for an additional fee via further written agreement. Vender is not responsible for any third party licensing costs for PRO survey

4. Spanish Language Content Subject to the terms set forth in this Section, the Vendor may periodically offer Spanish-language Content for the Base Components of certain Care Plans licensed by the government.

a. Vendor will review Base Components annually to reflect updated clinical best practices and compliance requirements

i. Vendor will provide the Spanish-language Content for such updates to Base Components of a Care Plan

b. Government shall be solely responsible for providing the Spanish-language Content for any Custom Components, altered Base Components, or added resources for any Care Plan. At no point will Vendor be responsible for translating any other Government-developed materials such as brochures, informational marketing materials, websites, or other similar items.

1. Spanish-language Content is available on a limited basis, and shall not include: PROMs, Canned Messages from Clinician Dash, Service Widget, Welcome Messages, or patient comments transmitted through the product.

i. The Clinician Dashboard does not allow for patients to be segmented by preferred language at this time.

1. No configuration of the Spanish-language Content is permitted

1. In order to enroll veterans to receive Spanish-language Content, gov will ensure that HL7 messages include the patient language.

i. Requested changes to standard UI may result in untranslated content

1. The Spanish-language experience is enabled at the government facility-level. Patients enrolled with Spanish-preferred language may see some content in Spanish, even for partially-translated Care Plans.

1. Technical Support may not be available in Spanish. A government resource may be required to facilitate Vendor-provided Technical Support services, and all Training Sessions provided by Vendor will be delivered in English.

5. Digital Care Management System Provide a system which provides virtual check-ins, digital care management and engages patients across the care continuum. The system should enable remote monitoring and scale care team outreach. The system should provide an extensive care plan library and backend system for remote monitoring.

a. One Care Plan Included: A virtual pathway on Get Well’s Loop platform that consists of educational information, reminders, check-in questions, and tasks that are specific to a procedure, diagnosis, or type of care. Care Plans are structured so that the correct information is displayed to the patient at the appropriate time depending on where they are in their journey of care. Each Care Plan should include one full Client Review Cycle, which is comprised of 2 government content review exchanges prior and 1 optional government content review exchange following delivery of the applicable Care Plan. Each Care Plan should be able to be configured down to the provider level and have the option of the following components:

i. Check-In

1. Check-in: Emphasize self-care activities and deliver timely guidance. Check-ins have the ability to generate alerts.

1. Confirmations: Are used to confirm activities and generate alerts when patients are non-compliant.

1. Trackers/Hardcoded Trackers/Complication Groups: Used to monitor clinical signs and symptoms, generating alerts based on trends and assessments

ii. Activity feed

2. System should keep track of activity via an “activity feed” that can be accessed by both the patient and clinician

2. Reminders: Can include educational images, videos and instructions. Patients can find and reference reminders at any time.

iii. Checklist

3. Tasks: Are added to the checklist and used to help patients organize to-dos. Alerts can be generated based on non-compliance

iv. Resources

4. Documents or web links can be stored in one place for patients to download or refer to.

1. Patient Management Dashboard: Dashboard used to help monitor and triage patient alerts, comments, and questions that are triggered through the check-in experience.

1. Care Plan Library: Provide a library of Care Plans that gives the government the option to activate additional Care Plans through optional tasks as required. The Care Plans library should include Care Plans within the Service Lines of but not limited to:

i. Orthopedic, Post-Discharge, Cardiology, Behavioral Health, General Surgery, Urology, Oncology, Spine, Colorectal Surgery, Neurosurgery.

4.4 Patient Pathway Workflow Engine Capability

· IPC System must be capable of engaging patients within existing clinical workflows. Contractors should provide sample workflow diagrams

· Workflow engine must be customizable and capable of alerting patients based on multiple triggers (admission, date, time, gender, patient interaction, medication, diagnosis, nursing trigger in nursing tools). Alerts must allow for branching with branching logic capable of delay between alerts.

· Based on patient interaction/responses to workflow alerts, the workflow engine must be able to follow up with various and multiple automated actions customized to the clinical workflow.

· Vendor workflow engine must be capable of allowing government to customize and create additional patient workflows. Provide a list of the current Pathway templates included.

Deliverables:

A. Content design: This solution shall be designed to reflect how the Medical Center operates and fully customized to our specifications.

B. One-year software licenses: Beginning at the time of system acceptance by the Government (date of approval for 1st bed in 1st unit to go-live), a one-year license for all software. The Contractor shall provide software licenses for operation of the software provided in the base period of the order. These licenses include the individual license for the IPC System at each television location.

C. Contractor will be responsible for procuring and managing the installation of all software licenses to complete installation of the upgrade.

9 DIGITAL WHITEBOARD LICENSES:

· The Contractor shall provide, install and configure an Interactive Digital Patient Facing Whiteboard on the patient television.

· Contractors should specifically describe how the contractor’s functionality meets each of the requirements:

9.1 Interactive Digital Whiteboard

· The Interactive Digital Whiteboard should replace the patient whiteboard in the patient room. Provide screenshots.

· Digital Whiteboard should be a dedicated Whiteboard User Experience and not a content page within the standard IPC System User Experience.

· Digital Patient Whiteboard should include the Staff assigned to the patient, ability to ask questions and see a log of the questions asked, staff visit tracker, Patient Schedule, Patient Tasks, Patient Goals, Clinician notes to the patient, Patient Journal, and Patient Friend/Relative Contact Information. Patient and Staff should have the ability to hide or disable content respectively. The management console should provide the ability to update individual whiteboards or bulk update a group of Digital Patient Whiteboards.

· Patient tasks in whiteboard should be able to be manually created in management console or automatically assigned based on pathways.

· Digital Whiteboard should always have ability to shrink the TV picture in order to display key whiteboard information on TV screen or when called up by clinicians (configurable by the medical center).

Deliverables:

A. The functionality, menus, and content shall be defined and configured to drive the outcomes sought by the organization.

B. One-year software licenses: Beginning at the time of system acceptance by the Government (date of approval for 1st bed in 1st unit to go-live), a one-year license for all software. The Contractor shall provide software licenses for operation of the software provided in the base period of the order. These licenses include the individual license for the Digital Whiteboard at each television location.

IPC PATIENT/CLINICAL WORKFLOW TRAINING:

The Contractor shall provide Patient/Clinical Workflow Training for the IPC system. When implemented correctly, Interactive Patient Care is a new way of delivering care that directly involves patients in the delivery process. Four patient clinical workflows that are aligned with VA and Medical Center strategic priorities include: Discharge Planning, Fall Prevention, Pain Management, and Staff Responsiveness. Contractor will lead training with the executive team and staff teams to build and train on the four designated workflows that actively involve patients within existing clinical workflows. Contractor will then configure the Interactive Patient Care system to implement the functionality required by the new workflows and train front line nursing staff.

Advanced IPC Workflow Training

· Contractor will lead training with the executive team and staff teams to build and train on workflows that actively involve patients within clinical workflows.

· Trainers should have clinical and healthcare leadership backgrounds.

· Should include Executive Kickoff Session, Current State Process Development Session Future State Process Development, Leadership Change Management and Implementation Session, Executive Summary Session Deliverables:

A. Patient/Clinical Workflow Training for IPC system

IPC SYSTEM ADVISORY/SUPPORT SERVICES:

The Contractor shall provide system support throughout the term of the software licenses including remote help desk support and regional client support management to both end-users and VA personnel. Support will include routine system updates and 24x7x365 Help desk support provided remote through the vendor call center. Contractor will provide a regional support team responsible for the overall success of Interactive Patient Care at the medical center. At a minimum, the regional support team should include Clinical, Technical, and Operational Support Resources. IPC Advisory Services staff will work with leadership on outcome priorities and staff on workflow design projects, provide staff and patient training, and work with the Medical Center on content updates.

Deliverables:

A. IPC System Advisory/Support Services

IPC INTERNET SERVICE:

The Contractor shall provide Internet Service to support the IPC System at each facility. Internet service should be used by contractor for remote support and for use by patients within the IPC System.

Deliverables:

A. Internet Service for IPC System

12 TECHNOLOGY SECURITY:

839.201 Contract clause for Information and Information Technology Security:

a. Due to the threat of data breach, compromise or loss of information that resides on either VA-owned or contractor-owned systems, and to comply with Federal laws and regulations, VA has developed an Information and Information Technology Security clause to be used when VA sensitive information is accessed, used, stored, generated, transmitted, or exchanged by and between VA and a contractor, subcontractor or a third party in any format (e.g., paper, microfiche, electronic or magnetic portable media).

b. In solicitations and contracts where VA Sensitive Information or Information Technology will be accessed or utilized, the CO shall insert the clause found at 852.273-75, Security Requirements for Unclassified Information Technology Resources.

CLIN 0004 Base plus each option year is being added:

· Software support is mentioned for the base year (This will be needed for the life of the contract).

· Licensing Support will also be needed for the life of the contract.

· Software | Firmware updates.

· Access and Database (Server) Management if applicable.

· Data Storage and Back-ups.

Parts:

The contractor shall furnish replacement parts to meet operating specifications. The contractor must have ready access to all replacement parts. Contractor shall maintain a sufficient stock of all parts (meeting manufacture’s design and specification) needed for repair and maintenance of the equipment or be able to secure needed parts within five (5) calendar days. All parts supplied shall meet manufacturer approved specifications. The contractor shall use new parts only. When requested, the contractor shall provide the VAMC with a letter from the manufacturer of the equipment specifying that all parts for the equipment will be sold to the contractor. All replacement parts provided under this contract shall be warranted for a period of one (1) year for replacement of same including all applicable costs, e.g., shipping. If published or issued by the equipment manufacturer, field service software/hardware updates/upgrades will be provided at no additional cost (to include parts and labor) during the contract period.

1. CLIN 0004 Service Support Repair Parts & Materials

1. The contract shall include $48,421.62 for repair parts and materials each year.

1. Contractor to handle the ordering and delivery of all repair parts and materials as approved by the AVAMC-Atlanta COTR and/or Designated Point of Contact.

The contractor, their personnel, and their subcontractors shall be subject to the Federal laws, regulations, standards, and VA Directives and Handbooks regarding information and information system security as delineated in this contract

SECURITY CLAUSE

6500.6

1. General

i. Include the appropriate risk designation of the contractors based on the PDAT determination.

ii. Incorporate the security clause (Appendix B) into the contract involved and the appropriate security/privacy language outlined in Appendix C into the solicitation.

iii. Determine if protected health information is disclosed or accessed and if a BAA is required.

Ensure the contractor understands and implements the IT security requirements for system interconnection documents required per the Memorandum of Understanding or Interconnection Agreement (MOU-ISA). The standard operating procedure (SOP) and a template for a MOU-ISA are located on the Information Protection Risk Management (IPRM) Portal and can be provided to the contractor. Ensure contractor understands their participation in IT security requirements for C&A of the VA system to which they connect.

Enforce contractor performance (timely submission of deliverables, compliance with personnel screening requirements, and appropriate termination activity as appropriate)

Ensure that a Contractor Security Control Assessment (CSCA) is completed within 30 days of contract approval and yearly on the renewal date of the contract

Ensure that the CSCA is sent to the ISO and the OCS Certification Program Office for review to ensure that appropriate security controls are being implemented in service contracts. Ensure a copy of the CSCA is maintained in the Security Management and Reporting Tool (SMART) database. COTR will provide a copy of the completed CSCA to ISO for uploading into SMART database.

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

2. ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS

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

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

c. Contract personnel who require access to national security programs must have a valid security clearance. Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.

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

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

Information made available to the contractor or subcontractor by VA for the performance or administration of this contract or information developed by the contractor/subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA.

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

Prior to termination or completion of this contract, contractor/subcontractor must not destroy information received from VA, or gathered/created by the contractor while performing this contract without prior written approval by the VA. Any data destruction done on behalf of VA by a contractor/subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.

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

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

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

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

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

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

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

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

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

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

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

The contractor/subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C. 552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties.

The contractor/subcontractor agrees to:

(1) Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies:

(a) The Systems of Records (SOR); and

(b) The design, development, or operation work that the contractor/subcontractor is to perform;

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

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

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

(1) “Operation of a System of Records” means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records.

(2) “Record” means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person’s name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph.

(3) “System of Records” means a group of any records under the control of any…