S02 Sources Sought - Pyxis Medstation Upgrade.docx

THIS IS A SOURCES SOUGHT NOTICE ONLY: This announcement seeks information from the industry, which will be used for preliminary planning purposes for procurement. No proposals are being requested or accepted with this synopsis. THIS IS NOT A SOLICITATION FOR PROPOSALS AND NO CONTRACT SHALL BE AWARDED FROM THIS SYNOPSIS. THIS IS STRICTLY MARKET RESEARCH.

The purpose of this synopsis is to gain knowledge of interest, capabilities, and qualifications of various members of industry, who have the capability to provide upgrade and installation to the Medstations currently in use at the Providence VAMC.

The NAICS is 339112. The size standard is 1000 Employees. The PSC/FSC is 6515 No SBA NMR waiver in effect for this equipment.

A letter of authorization from the Original Equipment Manufacturer (OEM) is requested with your response.

All interested firms must be registered in SAM (System for Award Management) to be eligible for the award of Government contracts. Interested parties responding to this Sources Sought request shall submit the following information at a minimum:

(1) Company name and address point of contact with phone number and SAM UEI.

(2) Documentation relating to capability of performance, including installation in a hospital environment, training, and a current point of contact and phone number).

(3) Socio-economic status to identify the business class as being a large business, SDVOSB, VOSB, small business, Woman Owned, etc.

(4) Place of manufacture

(5) Any other pertinent company documentation prior to submission of offers to a solicitation.

Any SD/VOSB firms responding to this Sources Sought Notice must also provide proof of registration in the SBA Vet Cert, prior to submission of offers to a solicitation.

This market research is for informational and planning purposes. This is not a solicitation and does not obligate the Government to issue a solicitation. Please be advised that the government will not pay any costs for responses and information submitted. All submissions are acceptable via frederic.revah1@va.gov

RESULTS INFORMATION: Respondents will not be notified of the results, and it is at the discretion of the Government to utilize results. Firms responding to this Sources Sought announcement, who fail to meet all requirements as stated above, and who fail to provide ALL the required information requested, will not be used to help the Government make the acquisition decision, which is the intent of this sources sought announcement.

STATEMENT OF WORK Pyxis 2025

SCOPE OF WORK: The Contractor shall provide all labor, personnel, equipment, tools, materials, supervision and other items and services necessary to perform the following:

Upgrade of Pharmacy Equipment: BD Pyxis, BD Logistics, and BD IV Prep.

The Pharmacy service at the Providence VA utilizes BD equipment, servers and applications for its medication dispensing, inventory management and IV Prep workflow. This includes three major systems: BD Pyxis, BD Logistics and BD IV Prep. These systems are integrated and are the backbone of pharmacy medication dispensing/ordering, inventory management and IV Prep workflow.

The equipment included in this contract described below are direct replacements/upgrades to existing BD Pyxis, BD Logistics and BD IV Prep equipment that has reached the end of life. BD sets a service life on equipment when it goes into service and will not include it on the service contract once it reaches end of life.

· BD Pyxis Medstation ES and Anesthesia System ES

· Automated medication dispensing system supporting decentralized medication management. These are cabinet-based storage systems used by hospitals and similar institutions to store and safeguard medications and floor stock items. Using a Windows-10 based computer in the main cabinet, users can unlock and open drawers in the cabinets and access the contents of the medications stored in the cabinets.

· BD Pyxis Auxiliary cabinet/Auxiliary Tower

· BD Pyxis Medstation ES Auxiliary cabinets and towers provide additional storage to a BD Pyxis Medstation ES. They are co-located with a Medstation ES in a particular clinical area and their drawers/doors are unlocked via the application on the associated Medstation ES.

· BD Logistics Printers, Handheld scanners, check scanner kits

· BD Logistics is the enterprise medication management system for the inpatient pharmacy. This integrates with ES Platform to provide inventory to low stock in Pyxis Medstation, drive automated workflows for ordering, receiving, picking, and returning of medications. The scanners are used to log inventory into the BD logistics application. The printers are used for printing medication labels and inventory sheets.

· BD Carousel Mechanical refresh

· The BD Pyxis Pharmologistics carousel is a medication storage and retrieval system. It integrates with the BD Logistics application to log inventory and allows picking of medications based on pharmacy orders. The mechanical refresh will replace the critical mechanical components of the carousel system, extending the life of system by seven years

· BD IV Prep Gravimetric Pack and Server Upgrade

· BD IV Prep is the system that helps the inpatient pharmacy department monitor the process of making IVs in the compounding room. It guides technicians through the process of compounding by scanning barcodes, verifying the right medication is being added.

· The BD IV Prep Gravimetric pack includes the scale, scanner and camera used to document the medication being compounded.

· The BD IV Prep Server upgrade will migrate the IV Prep application and dataset that are currently installed on unsupported hardware and using an unsupported operating system to Virtual Machines on a supported operating system (Windows Server 2019)

· BD Pyxis Server Upgrade

· The BD Pyxis Server upgrade will migrate the BD Pyxis Servers that are currently installed on unsupported hardware and using an unsupported operating system to Virtual Machines on a supported operating system (Windows Server 2019). These servers control the interface between the BD Pyxis medstations and facilitate communication between orders placed in VistA/CPRS, Pyxis Medstations and the patient record.

1. EQUIPMENT:

The following equipment shall be provided and installed by the Contractor in the space determined by the Government. All equipment installed by the Contractor shall be FDA approved for use, in new condition, and fully operational in accordance with manufacturer literature specifications. A minimum of two (2) copies of any associated operational and/or service manuals shall be provided for all equipment listed below as applicable.

The Contractor shall provide all tools and equipment necessary to properly and safely perform the services set forth within this statement of work. This shall include, but is not limited, to all Personal Protective Equipment (PPE) which may be required for the work to be completed in a safe manner.

1000276371 - LOGISTICS PERIPHERALS

1000276357 - IV PREP

1000279503 - CAROUSEL MECHANICAL REFRESHMENT

1000276344 - PYXIS FY25

1000276239 - PYXIS FY26

1000276345 - PYXIS FY27

1000264091 - Providence VA - IVP SW Only 2019 SRVR Migration 022525

1000281061 Providence VA - Middletown 6 Drawer Medstation 022525

1000281061 Providence VA - Middletown 6 Drawer Medstaion 022525

2. AREAS TO BE SERVICED:

(one or all as necessary and appropriate to this contract)

Providence VA Medical Center 830 Chalkstone Ave Providence, RI 02908

Eagle Square VA Clinic 589 Atwells Ave Providence, RI 02909

Middletown VA Clinic One Corporate Pl Middletown, RI 02842-6406

New Bedford VA Clinic 175 Elm St New Bedford, MA 02740

Hyannis VA Clinic 233 Stevens St Hyannis, MA 02601

3. INSTALLATION:

a) The Contractor shall provide all labor, materials, tools, equipment and etc. to prepare for and complete the installation of the equipment in the space determined by the Government.

b) Installation dates are to be coordinated in advance with the Contractor and the Providence VA Medical Center’s Pharmacy Service and Clinical Engineering Service.

c) All employees of the Contractor and subcontractors shall comply with VA security management program and obtain the permission of the VA police, be identified by project and employer, and restricted from unauthorized access.

d) All installation personnel shall be trained by the manufacturer on how to properly install the equipment. Resumes and certifications shall be submitted for review prior to installation.

e) The Contractor shall request information regarding determined installation space construction such as wall blocking and/or stud placement, room dimensions, finish materials, etc. as required to complete a safe and functional installation.

f) The Contractor shall communicate the estimated noise level produced during the installation process to the Providence VA Medical Center prior to the start of installation. The Contractor shall modify equipment, tools, etc. used during installation and/or installation time of day to ensure the estimated noise level is within the acceptable threshold as communicated by the Government.

g) The Contractor shall be responsible for the safe removal and disposal of all packing materials and related waste generated during installation.

4. TRAINING:

The Contractor shall provide a comprehensive onsite training program for the operating clinicians as required. This training program shall include at the minimum the following sessions: (i) Technical Training, (ii) Operational Training, (iii) Administrative Training, and (iv) Hardware and Software Troubleshooting. Training shall occur onsite during normal business hours, 8:00am-4:30pm, Monday through Friday. Competency assessments shall be provided with the training. Onsite training is to be scheduled in advance with the Providence VA Medical Center’s Pharmacy Service and Clinical Engineering Service.

5. TASK FREQUENCY AND INSTRUCTIONS:

The work set forth in the Scope of Work shall be completed in a single visit, be it a single day or multiple days as required for appropriate completion. All work is to be scheduled in advance with the Providence VA Medical Center’s Pharmacy Service and Clinical Engineering Service.

Equipment delivery, installation, and training shall occur on the same day determined in advance by the Contractor and the Providence VA Medical Center’s Pharmacy Service and Clinical Engineering Service.

6. SPECIAL WORK REQUIREMENTS:

The Contractor shall comply with any and all Infection Control Risk Assessment requirements deemed appropriate by the Providence VA Medical Center during all portions of the work set forth in the Scope of Work.

The Contractor must comply with security, privacy, and safety issues in accordance to VA standards, policies, and directives set forth at all times while providing the work outlined in the Scope of Work.

7. PROPERTY DAMAGE:

The contractor shall take all necessary precautions to prevent damage to any government property. The contractor shall report any damages immediately and shall be assessed current replacement costs for property damaged by the contractor, unless corrective action is taken. Any damaged material (e.g. trees, shrubs, lawn/turf, curbs, gutters, sidewalks, etc.) will be replaced in a timely manner or corrected by the contractor with like materials, at no extra cost to the government, upon approval of the Contracting Officer.

8. ATTACHMENTS:

None.

9. IDENTIFICATION, PARKING, SMOKING, CELLULAR PHONE USE AND VA REGULATIONS:

The contractor's employees shall wear visible identification at all times while on the premises of the VA property. It is the responsibility of the contractor to park in the appropriate designated parking areas. Information on parking is available from the VA Police-Security Service. The VA will not invalidate or make reimbursement for parking violations of the contractor under any conditions. Smoking is prohibited inside any buildings at the VA. Cellular phones and two-way radios are not to be used within six feet of any medical equipment. Possession of weapons is prohibited. Enclosed containers, including tool kits, shall be subject to search. Violations of VA regulations may result in a citation answerable in the United States (Federal) District Court, not a local district state, or municipal court.

10. COMPLIANCE WITH OSHA BLOODBORNE PATHOGENS STANDARD:

The contractor shall comply with the Federal OSHA Blood borne Pathogens Standard. The contractor shall:

A. Have methods by which all employees are educated as to risks associated with blood borne pathogens.

B. Have policies and procedures which reduce the risk of employee exposure to blood borne pathogens.

C. Have mechanisms for employee counseling and treatment following exposure to blood borne pathogens.

D. Provide appropriate personal protective equipment/clothing such as gloves, gowns, masks, protective eyewear, and mouthpieces for the employee during performance of the contract.

13. INFORMATION SECURITY LANGUAGE.

VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE

FOR INCLUSION INTO CONTRACTS, AS APPROPRIATE

1. GENERAL

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. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). 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 located 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.

3. VA INFORMATION CUSTODIAL LANGUAGE

a. 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. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).

b. 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 are in compliance with VA directive requirements.

c. Prior to termination or completion of this contract, contractor/subcontractor must not destroy information received from VA, or gathered/created by the contractor in the course of 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.

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

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

f. If VA determines that the contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.

g. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.

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

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

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

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

l. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COTR.

9. TRAINING

a. All contractor employees and subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:

(1) Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Contractor Rules of Behavior, Appendix E relating to access to VA information and information systems.

(2) Successfully complete the VA Cyber Security Awareness and Rules of Behavior training and annually complete required security training.

(3) Successfully complete the appropriate VA privacy training and annually complete required privacy training; and

(4) Successfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access [to be defined by the VA program official and provided to the contracting officer for inclusion in the solicitation document – e.g., any role-based information security training required in accordance with NIST Special Publication 800-16, Information Technology Security Training Requirements.]

b. The contractor shall provide to the contracting officer and/or the COTR a copy of the training certificates and certification of signing the Contractor Rules of Behavior for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required.

c. Failure to complete the mandatory annual training and sign the Rules of Behavior annually, within the timeframe required, is grounds for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the training and documents are complete.

14 Records Management Language for Statement of Work.

Records Management Language for Statement of Work (SOW):

The following standard items relate to records generated in executing the contract and should be included in a typical procurement contract:

1. Citations to pertinent laws, codes and regulations such as 44 U.S.C chapters 21, 29, 31 and 33; Freedom of Information Act (5 U.S.C. 552); Privacy Act (5 U.S.C. 552a); 36 CFR Part 1222 and Part 1228.

2. Contractor shall treat all deliverables under the contract as the property of the U.S. Government for which the Government Agency shall have unlimited rights to use, dispose of, or disclose such data contained therein as it determines to be in the public interest.

3. Contractor shall not create or maintain any records that are not specifically tied to or authorized by the contract using Government IT equipment and/or Government records.

4. Contractor shall not retain, use, sell, or disseminate copies of any deliverable that contains information covered by the Privacy Act of 1974 or that which is generally protected by the Freedom of Information Act.

5. Contractor shall not create or maintain any records containing any Government Agency records that are not specifically tied to or authorized by the contract.

6. The Government Agency owns the rights to all data/records produced as part of this contract.

7. The Government Agency owns the rights to all electronic information (electronic data, electronic information systems, electronic databases, etc.) and all supporting documentation created as part of this contract. Contractor must deliver sufficient technical documentation with all data deliverables to permit the agency to use the data.

8. Contractor agrees to comply with Federal and Agency records management policies, including those policies associated with the safeguarding of records covered by the Privacy Act of 1974. These policies include the preservation of all records created or received regardless of format [paper, electronic, etc.] or mode of transmission [e-mail, fax, etc.] or state of completion [draft, final, etc.].

9. No disposition of documents will be allowed without the prior written consent of the Contracting Officer. The Agency and its contractors are responsible for preventing the alienation or unauthorized destruction of records, including all forms of mutilation. Willful and unlawful destruction, damage or alienation of Federal records is subject to the fines and penalties imposed by 18 U.S.C. 2701. Records may not be removed from the legal custody of the Agency or destroyed without regard to the provisions of the agency records schedules.

10. Contractor is required to obtain the Contracting Officer's approval prior to engaging in any contractual relationship (sub-contractor) in support of this contract requiring the disclosure of information, documentary material and/or records generated under, or relating to, this contract. The Contractor (and any sub-contractor) is required to abide by Government and Agency guidance for protecting sensitive and proprietary information.

image1.emf image2.emf

Appendix C 6500 ISO Info 6-2022.pdf

MARCH 12, 2010 VA HANDBOOK 6500.6

APPENDIX C

C-1

VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE FOR

INCLUSION INTO CONTRACTS, AS APPROPRIATE

1. GENERAL

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/subcontrator 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. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). 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 located 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.

VA HANDBOOK 6500.6 MARCH 12, 2010

C-2

3. VA INFORMATION CUSTODIAL LANGUAGE

a. 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. This clause expressly limits the contractor/subcontractor's rights to use data as described in Rights in Data

- General, FAR 52.227-14(d) (1).

b. 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 are in compliance with VA directive requirements.

c. Prior to termination or completion of this contract, contractor/subcontractor must not destroy information received from VA, or gathered/created by the contractor in the course of 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.

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

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

C-3

f. If VA determines that the contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold

C-4 payment to the contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12.

g. If a VHA contract is terminated for cause, the associated BAA must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.

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

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

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

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

l. For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or an MOU-ISA for system interconnection, the contractor/subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the COTR.

4. INFORMATION SYSTEM DESIGN AND DEVELOPMENT

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

C-5

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.

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

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

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

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

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

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

C-6

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

h. 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 considered to be 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 agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.

i. The vendor shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as “Systems”), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.

j. The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than ____ days.

k. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to the VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes within ____ days.

C-7

l. All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g. for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and Technology.

5. INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE

a. For information systems that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities, contractors/subcontractors are fully responsible and accountable for ensuring compliance with all HIPAA, Privacy Act, FISMA, NIST, FIPS, and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerablity scanning, system patching and change management procedures, and the completion of an acceptable contingency plan for each system. The contractor’s security control procedures must be equivalent, to those procedures used to secure VA systems. A Privacy Impact Assessment (PIA) must also be provided to the COTR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA’s network involving VA information must be reviewed and approved by VA prior to implementation.

b. Adequate security controls for collecting, processing, transmitting, and storing of Personally Identifiable Information (PII), as determined by the VA Privacy Service, must be in place, tested, and approved by VA prior to hosting, operation, maintenance, or use of the information system, or systems by or on behalf of VA. These security controls are to be assessed and stated within the PIA and if these controls are determined not to be in place, or inadequate, a Plan of Action and Milestones (POA&M) must be submitted and approved prior to the collection of PII.

c. Outsourcing (contractor facility, contractor equipment or contractor staff) of systems or network operations, telecommunications services, or other managed services requires certification and accreditation (authorization) (C&A) of the contractor’s systems in accordance with VA Handbook 6500.3, Certification and Accreditation and/or the VA OCS Certification Program Office. Government-owned (government facility or government equipment) contractor-operated systems, third party or business partner networks require memorandums of understanding and interconnection agreements (MOU-ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks.

d. The contractor/subcontractor’s system must adhere to all FISMA, FIPS, and NIST standards related to the annual FISMA security controls assessment and review and update the PIA. Any deficiencies noted during this assessment must be provided to the VA contracting officer and the ISO for entry into VA’s POA&M management process. The contractor/subcontractor must use VA’s POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies must be corrected within the timeframes approved by the government. Contractor/subcontractor procedures are subject to periodic, unannounced assessments by VA officials, including the VA Office of Inspector General. The physical security aspects associated with contractor/subcontractor activities must also be subject to such assessments. If major changes to the system occur that may

C-8 affect the privacy or security of the data or the system, the C&A of the system may need to be reviewed, retested and re-authorized per VA Handbook 6500.3. This may require reviewing and updating all of the documentation (PIA, System Security Plan, Contingency Plan). The Certification Program Office can provide guidance on whether a new C&A would be necessary.

e. The contractor/subcontractor must conduct an annual self assessment on all systems and outsourced services as required. Both hard copy and electronic copies of the assessment must be provided to the COTR. The government reserves the right to conduct such an assessment using government personnel or another contractor/subcontractor.