P01 - DRAFT Product Description - Brillians.docx

Brillians (SupraVISTA) Software

VA-23-00067135

PRODUCT DESCRIPTION (PD) TEMPLATE

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA), Veterans Integrated Service Network (VISN) Regional Area 16 (VISN 16) Medical Center (VAMC)

Brand Name Brillians (formerly, SupraVISTA) Software License

Date: May 9, 2023

VA-23-00067135

PD Version Number: 1.0

Contents

PRODUCT REQUIREMENTS

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA), Veterans Integrated Service Network (VISN) regional area 16 (VISN 16) Medical Center (VAMC) has a requirement for a brand name Brillians (formerly, SupraVISTA) software license, Technical Support and End User Training. The Brillians software (hereafter “Brillians”) is a cognitive support system which works with VHA’s Veterans Health Information System Technology Architecture (VistA) system. It is a Windows desktop application which runs on the VHA’s computer systems. Therefore, no hardware purchase is included in this request. The application will be used by a wide range of clinical staff in performing their patient care duties.

The Contractor shall provide the following fully functional brand name Brillians software licenses not later than three working days after contract award:

Base Period

The annual licensing fee allows use of the licensed software on unlimited number of workstations by unlimited number of users at all the VAMCs, OPCs and CBOCs in the licensing VISN.

Option Period 1

Option Period 2

REPORTING REQUIREMENTS

If requested, the Vendor shall provide progress reports to the designated Point of Contact (POC) at the customer VAMC. The progress report shall be a summary of total different reports/letters that are produced on a weekly, monthly, or quarterly basis.

VISN POCs:

John Areno Chief Medical Officer john.areno@va.gov

(601) 206-6973

Terrie Hawkins VISN 16 Chief Health Informatics Officer terrie.hawkins@va.gov

(501) 766-7803

Jose Rivera VISN 16 Primary Care Lead jose.rivera2@va.gov

(318) 466-2565

Inga Pavalock VISN 16 Primary Care HSS inga.pavalock@va.gov

(601) 985-9324

SUPPORT

The Contractor shall provide requested assistance via email within two (2) working days, if requested by VA’s COR/Program Manager. The Contractor shall assist VA’s staff with software installation and configuration related questions.

The Tier 1 technical support will be provided by the VAMC’s staff.

The Tier-2 and Tier-3 technical support shall be provided by the Contractor via email within two working days except in case of a natural disaster or breakdown of electronic communication systems beyond the Contractor’s control.

Tier-1 Technical support:

The Tier-1 support is provided by the organization’s informatics or other designated staff. The Tier-1 support includes, but is not limited to, the following:

1. Historically, most of the help requests are minor and typically relate to:

a. New users: How to access the application (typically, a link on the CPRS Tools menu).

b. Ne`w users: Request access to the application using an established request process (typically, OIT staff grants privileges via Active Directory).

c. How do I do X, or can Brillians do X? (Typically, informatics staff provides brief information, or points the user to the appropriate training resources).

2. Verify and reproduce the user-identified issues/errors. If the error is reproducible and cannot be resolved by the local staff, then communicate the issue to the vendor for resolution.

3. Network, Operating System and other IT infrastructure related issues are beyond the Contractor's control. These are handled by the VAMC IT staff and are transient in most cases.

4. General issues which can be addressed via training, e.g., misunderstanding or misuse of features resulting in unexpected results.

5. Local configuration issues including initial configuration, and the subsequent need to tweak the configuration due to changes to the VistA system, e.g., lab names are changed, or new document titles are added. Historically, after the initial configuration, such needs are rather infrequent.

6. Any support issues which are not specifically listed under the Tier-2, or the Tier-3 support below.

Note: To escalate to the Tier-2 support, the local VAMC staff must be able to reproduce the issue on one or more actual patient records (not the test patients).

Tier-2 Technical support The Tier-2 support includes the actual or perceived application error(s) (see Tier-1 issue) in one or more features which the VA staff can reproduce but cannot explain or solve. However, the rest of the application remains fully functional.

For Tier-2 technical support needs, the Contractor shall provide support via email within two working days.

Tier-3 Technical support Typically, this will be something which causes the application to become unstable or unusable. The resolution requires highest level of technical skill and often includes the developers. For Tier-3 technical support needs, the vendor provides support via email within two working days.

End-user Training:

The Contractor shall provide extensive help and training resources in form of:

• Written documentation including many help documents directly accessible from the conventional Help menu.

• Training Videos - expanding library of training videos on YouTube.

• Various resources on Contractor’s website.

PERIOD OF PERFORMANCE

The period of performance shall be one (1) 12-Month Base Period, with two (2) 12-Month Option Periods to be exercised at the Government’s discretion for continue Brillians subscription renewal, inclusive of technical support and training resources.

NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS (SECTION 508) On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) STANDARDS

The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request.

Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery. The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

INFORMATION TECHNOLOGY USING ENERGY-EFFICIENT PRODUCTS

The Contractor shall comply with Sections 524 and Sections 525 of the Energy Independence and Security Act of 2007; Section 104 of the Energy Policy Act of 2005; Executive Order 13834, “Efficient Federal Operations”, dated May 17, 2018; Executive Order 13221, “Energy-Efficient Standby Power Devices,” dated August 2, 2001; and the Federal Acquisition Regulation (FAR) to provide ENERGY STAR®, Federal Energy Management Program (FEMP) designated, low standby power, and Electronic Product Environmental Assessment Tool (EPEAT) registered products in providing information technology products and/or services.

EPEAT

EPEAT product compliance is not required in this acquisition.

ENERGY STAR

Energy Star compliance is not required in this acquisition.

FEMP

FEMP or FEMP low standby power product compliance is not required in this acquisition.

SHIPMENT OF SOFTWARE

Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination

The Contractor shall provide a website link to download the application Software License Subscriptions not later than three (3) working days after contract award to the following individuals below:

Phone (External)

John Areno VISN 16 Chief Medical Officer john.areno@va.gov

(601) 206-6973

Terrie Hawkins VISN 16 Chief Health Informatics

Jose Rivera VISN 16 Primary Care Lead

Inga Pavalock VISN 16 Primary Care HSS

GENERAL REQUIREMENTS

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.

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 Integrated Control Number (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.

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.

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.

POINTS OF CONTACT

VA Program Manager:

Contracting Officer’s Representative:

Name: Flemiko Tolliver Address: VISN 16 VAMC

Contracting Officer:

Name: Mary Accomando Office of Procurement, Acquisition and Logistics

Contract Specialist:

Name: Tiffany Brown Office of Procurement, Acquisition and Logistics

INFORMATION SECURITY CONSIDERATIONS:

The assessment and authorization (A&A) requirements do not apply and a Security Accreditation Package is not required.

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

image1.jpeg