P09 Final PD DSS.pdf

Product Description Template_MAY_16_2025_Rev.1 PD Template Revision History

PRODUCT DESCRIPTION (PD) TEMPLATE

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology James J. Peters VA Medical Center

Preoperative Care / Surgical Department

DSS Preference Card

Date: 1/13/2026

PD Version Number: 1.0 https://dvagov.sharepoint.com/:w:/r/sites/VACOOALC/TACNJ/DLR/VOA%20Template/CAP%20Template/OPAL%20Acquisition%20Requirements%20Package%20(ARP)%20Templates/Other%20Templates%20(Standard%20Templates)/Product%20Description%20Template_Revision%20History_MAY_16_2025_Rev.1_JUN_02_2025.docx?d=w6cee9ba225d04a51a6398ef2459b2fbf&csf=1&web=1&e=O62pc5

TAC Number: VA-26-00032697

Product DescriptionTemplate_MAY_16_2025_Rev.1

1.0 PRODUCT REQUIREMENTS

The Veterans Affairs (VA) Office of Information & Technology James J. Peters VA Medical Center Preoperative Care / Surgical Department has a requirement for a base plus 4 year option contract for a Brand Name Only requirement of the DSS LiveData Preference Card (PFCD) Platform Annual Limited License manufactured by Document Storage Systems, Inc, needed for each operating room.

Mfg. Part # Description/Part Number* Qty

DSS LD-PFCD-LL

DSS LiveData Preference Card (PFCD) Platform Annual Limited License, per operating room 6

DSS LD-PFCD-AI-

FEE

DSS LiveData Preference Card (PFCD) AI PrefCard Builder, one-time initial fee 1

EMRTEC

Sotware Installation - EMR Technical Installation Services Per Hour 8

DSS-CSA-CWSE

Implementation, Set-Up, Training, and Go-Live - Customer Workflow/ Support Engagements per hour. 16

EMRTRN

Gather Cards, Inventory data from VA, Review Cards with VA provided by certified staff - EMR Training Per Hour 16

DSS-LD-SVC Project Management for implementation 80 PROJ-MGMNT DSS Project Management, price per hour 33

TRAVEL-Z

PREFcards project management Import inventory /Build out cards/standardize data/finalize card build from VA feedback. - Travel Per Diem Expenses, estimated per person per week. Actual expenses to be billed according to government regulations. (Open Market item) 3

2.0 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Access Board issued a final rule that updated accessibility requirements covered by Section 508 and refreshed guidelines for telecommunications equipment subject to Section 255 of the Communications Act. The final rule went into effect on January 18, 2018. 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.

2.1 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: Revised 508 Standards and 255 Guidelines (access-board.gov). A single PDF file version of the Revised Section 508 Standards and 255 Guidelines will be supplied upon request, or can be obtained from the Access Board website. Federal agencies must comply with the Rehabilitation Act of 1973, as amended.

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:

☒ E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

☒ E204 Functional Performance Criteria ☒ E206 Hardware Requirements ☒ E207 Software Requirements ☒ E208 Support Documentation and Services Requirements

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

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

3.0 INFORMATION TECHNOLOGY USING SUSTAINABLE PRODUCTS AND

SERVICES

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 13221, “Energy-Efficient Standby Power Devices,” dated August 2, 2001; and the Federal Acquisition Regulation (FAR) to provide ENERGY STAR®, https://www.access-board.gov/ict/ https://www.access-board.gov/ict/

Federal Energy Management Program (FEMP) designated, and products and services that meet EPA Recommendations of Specifications, Standards, and Ecolabels in effect as of October 2023 (e.g. Electronic Product Environmental Assessment Tool (EPEAT) registered products) in providing information technology products and/or services. The Green Procurement Compilation (GPC) website available at Green Procurement Compilation - GSA Sustainable Facilities Tool (sftool.gov) provides a comprehensive list of sustainable products and services and sustainable acquisition guidance.

The Contractor shall provide products that meet the definition of sustainable products and services if the products are delivered to the Government; furnished by the Contractor for use by the Government, incorporated into the construction of a public building or public work, or acquired by the Contractor for use in performing services under a Government contract where the cost of the products is a direct cost to a Government contract (versus costs which are normally applied to a contractor's general and administrative expenses or indirect costs).

Specifically, the Contractor shall provide sustainable products under this contract in accordance with FAR 52.223-23. The applicable products with their associated certification, designation, and/or ecolabel (e.g. Energy Star, FEMP, and/or EPEAT) are identified within the product specifications in this PD. The Contractor shall ensure proposed products meet the certification(s) / designation(s) / ecolabel(s) specified at the time of submission of proposals and at the time of award.

4.0 SHIPMENT OF HARDWARE OR EQUIPMENT

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

Ship To and Mark For:

Primary Alternate Name: To be given at award Name: To be given at award Address: To be given at award Address: To be given at award Voice: To be given at award Voice: To be given at award Email: To be given at award Email: To be given at award

Packing Slips/Labels and Lists shall also include the following:

IFCAP PO # or Contract No.: ____________ (e.g., 166-E11234 (the IFCAP PO number is located in block #20 of the SF 1449)) Project Description: (e.g. Tier I Lifecycle Refresh)

Total number of Containers: Package ___ of ___. (e.g., Package 1 of 3) https://sftool.gov/greenprocurement https://sftool.gov/greenprocurement

5.0 GENERAL REQUIREMENTS

5.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

5.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

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

https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

5.4 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support IPv6-Only 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). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only 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, applications, and systems shall support all applicable functionality on native IPv6-Only as well as 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-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.

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

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

https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119 https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents

6 POINTS OF CONTACT

VA Program Manager:

Name: To be given at award Address: To be given at award Voice: To be given at award Email: To be given at award

Contracting Officer:

Name: Claudetta Smith Address: 23 Christopher Way Eatontown, New Jersey 07724 Voice: 512-981-4135 Email: Claudetta.Smith@va.gov

Contract Specialist:

Name: Belinda Espindola Address: 23 Christopher Way Eatontown, New Jersey 07724 Voice:848-377-5129 Email: Belinda.espindola@va.gov mailto:Claudetta.Smith@va.gov mailto:Belinda.espindola@va.gov