USA - D--TAC-19-56081 Peer Review-Radiation Therapy Treatment Plans (medical software)
For more information and to make a bid you will need to go to the third party website.
- Opportunity closing date
- 14 August 2019
- Opportunity publication date
- 10 August 2019
- Value of contract
- to be confirmed
- Your guide to exporting
Added: Aug 09, 2019 4:24 pm
Radiation Oncology Peer Review Software Program RFI
Page 3 of 51
Radiation Oncology Peer Review Software Program
This is a request for information (RFI) only. The Department of Veterans Affairs (VA) has a requirement to provide a robust peer review software program for quality assurance in radiation treatment planning. The vendor product should be a software as a service (SaaS) hosted on the vendor cloud environment. Vendor s peer review program must include a software module for anonymization of patient health information that will be deployed at each VA radiation oncology clinic. The software should have mechanisms to upload DICOM/DICOM-RT data to the vendor hosted cloud database for data archival. Peer review software viewer should be able to display the DICOM/DICOM-RT data and need to be zero foot print (HTML-5 based) that can work on any modern day web browser. The peer review viewer should be accessible via Internet or Cloud. Software will be used to provide remote peer-review services for the purpose of providing expert peer-reviews to radiation oncologists within VHA. It is also requested that the vendor respond to the following questions:
Provide a brief summary of your technical approach (not to exceed 15 pages) for meeting the Product Description requirements for the Peer Review Software Program.
Provide a cost estimate for the SaaS licensing and training.
Please provide existing GSA schedule, NASA SEWP, and/or GWAC contract information in which you are a contract holder that can be utilized to procure these services.
Please provide your company profile (to include, but not limited to, history, business size and socioeconomic category under North American Industry Classification (NAICS) 511210.
This RFI is for planning purposes only and shall not be considered an Invitation for Bid, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI. Your response to this RFI will be treated only as information for the Government to consider. You will not be entitled to payment for direct or indirect costs that you incur in responding to this RFI. This request does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated or received for this effort. The information provided may be used by the VA in developing its acquisition strategy and Product Desciption. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The Government does not intend to pay for the information submitted in response to this RFI.
Responses are due by 2:30 pm EST, August 14, 2019 to Robert Geran (Robert.Geran@va.gov)
Radiation Oncology Peer Review Software Program RFI
Page 51 of 51
Page 1 of 59
Page 1 of 25
High quality patient care is important to any medical discipline but is of particular concern in radiation oncology given the potential for serious harm in the event of a treatment-related error. Radiation treatment planning is a very complicated process with many safety aspects involved and with the increased application of more sophisticated technologies in radiation therapy, concerns have arisen about whether radiation is being used appropriately. Quality-assurance procedures must evolve with complex radiotherapy planning and delivery systems in order to ensure that consistently effective and safe therapy is delivered. The Veterans Health Administration (VHA) concurred with the Office of Inspector General (OIG) Health Inspection report, dated March 10, 2011, that there was a need for a robust physician peer review process related to all VHA radiotherapy programs. The Radiation Oncology Peer Review will give VA centers providing inhouse radiation oncology care the capability to seek prospective physician peer reviews online. The capability will enable VA radiation oncologists to consider treatment refinements and alternatives prior to radiation delivery for the safety of Veterans.
The Contractor shall provide a Web-based software package to facilitate peer review of radiotherapy treatment plans to all 40 Radiation Oncology Service with the VA system. The contracted services shall include access to the application software hosted on the vendor cloud environment via internet explorer v10 or higher or google chrome based web browsers, training, documentation, and helpdesk support. The contract will be based on Software-as-a-Service (SaaS) subscription. The acceptance testing for this software will be performed based the American Assocication of Medical Physics recommendations in Task Group report # 53 - Quality assurance for clinical radiotherapy treatment planning (https://www.aapm.org/pubs/reports/rpt_62.pdf)
The peer review software shall be accessible to all 40 VA Radiation Oncology clinics and will enable VHA radiation oncologists to seek treatment plan peer reviews on demand from any expert anywhere with Web access. The peer review software shall be FDA approved and will have no dependencies on or interfaces with other VA software systems. The software architecture shall allow prospective peer reviews of radiotherapy treatment plans by VA contracted nationally recognized experts in radiation oncology outside the VA. The contractor Peer Review Software-as-a-Service product shall be a hosted on the contractor cloud environment. This procurement will include one-year license with 2 option years for unlimited users, upgrades, technical support and training.
1.1 SOFTWARE APPLICATION REQUIREMENTS
The software shall meet the following general criteria:
Users shall be able to securely upload & download imaging from modalities such as computerized tomography (CT), magnetic resonance (MR), secondary capture (SC), computer radiograph (CR), portal, and digitally-constructed radiograph (DRR) as well as radiation therapy data objects over the VA Intranet (Digital Imaging and Communication in Medicine (DICOM), scanned images, etc.).
All DICOM dataset shall be securely submitted to the Contractor cloud-based RT PACS server. The system shall be automated such that the data is automatically registered and entered into the Radiotherapy Picture Archiving and Communication System (RT PACS) database.
Patient confidentiality shall be maintained throughout the peer review process and anonymous case datasets and peer reviewers observations data cannot be accessed by an unauthorized user within or external to the system.
Peer review cases submitted by the VA clinical providers need to be made immediately (within 1 hour) available for rapid review by the VA contracted nationally recognized experts in radiation oncology outside the VA.
The Contractor shall provide tools to download all clinical data in the Contractor cloud RT-PACS server to a local archive in the VA.
Data objects shall be editable with the support of data authoring and versioning (DAV) control.
The peer review software shall be accessible to multiple simultaneous VA users at any given time. We estimate 40 user accounts and the same number of simultaneous users of this software. It is estimated that there will be up to 10,000 cases per year.
Security is implemented by performing lossless compression and encryption on all data before transmission. Data shall also be stored both compressed and encrypted in the database as a further measure of security.
The data exchange protocol employed throughout shall be secure hypertext transfer protocol (HTTPS) for all transfers. This enables transfer from most firewall-protected networks which typically allow HTTP and secure hypertext transfer protocol HTTPS data transfers
Provide a User Manual detailing all user capabilities and functions with troubleshooting section on the use of software and transmission of planning data files to National Expert and transmission of planning data files to the program office representative.
1.2 SOFTWARE COMPONENTS
The Peer Review software application shall satisfy the following software components requirement as illustrated in the figure from appendix A. All the below mentioned software components are illustrated in the figure from appendix A.
Web-based secure object archiving system (Web based RT-PACS): The software shall support all DICOM Message Service Elements (DIMSE) listed in the table below and can read, write and analyze DICOM (including all radiotherapy information object definitions [IODs]) and flat files (Part 10 Format). The software application shall be able to accept data over secure HTTPS web services protocol
DICOM RT data viewer: The software shall have the infrastructure of comprehensive tools required for preparation, submission, auto-archiving, Web-based review, and retrieval of diagnostic images, treatment-planning images, and radiation therapy objects. The software shall have the features of auto anonymizing datasets before they are submitted for peer review. Also, the software shall have tools for calculating Dose Value Histograms (DVHs) and compositing doses from different trials of the patient. In addition to DICOM RT data the software shall be able to handle PDF attachments with the clinical cases for review.
Data analytics: The Contractor shall provide data analytic tools and dashboards to quantitatively evaluate the quality of treatment plans. The data analytics tool shall have interactive dashboards to view aggregated data from peer review results and treatment plans over time.
Data anonymizer: Template based anonymization tools shall be provided by the Contractor to remove any PHI/PII from the DICOM/DICOM-RT datasets before they are uploaded to the Contractor hosted cloud RT-PACS. The template-based anonymization shall have custom anonymization schemes to be applied automatically to the incoming treatment plan data. Upon anonymization the DICOM and clinical data shall be encrypted using Federal Information Processing Standards-140/2 (FIPS-140/2) supported encryption protocols.
The Peer review software application shall be seamlessly interoperable with radiotherapy planning and oncology information systems that comply with the DICOM and Integrating the Healthcare Enterprise Radiation Oncology (IHE-RO) standards & specifications
1.3 SOFTWARE APPLICATION DATA SECURITY REQUIREMENTS
1.3.1 DATA SECURITY
The software shall meet the following data security criteria:
The software capability shall include a secure (access to patient data) and unsecure (access to general information regarding the functionalities of software) section. Access to secure section shall be divided into multiple levels, based on the privilege level assigned to a user. The privilege level shall be assigned based on the need of a user to view clinical data submitted to the RT servers. Each expert reviewing cases will have access to data submitted for his/her domain only. The software shall ensure end-users have access to only their data. Each user will have to register once with the software server and get a user name and user password. Before an account is activated, the software shall send a notification to a VA system administration requesting user credentials verification. Access to data shall be hierarchical. Browsers and Web services shall use a Secure Socket Layer (SSL) for secure communication. The RT servers shall exchange a public key certificate with client applications. The key certificate shall be published for the domain and signed by a certificate authority; the client application (browser) establishes an encrypted connection between itself and the RT servers.
Once a user logs in, a unique session shall be created on the server memory. This session shall expire after a specified time if there is no activity on the software. Thus, if the user computer is left unattended, the session data cannot be accessed after the expired time by others. In addition, presentation of each dynamic page depends on this unique session.
The Contractor shall coordinate with applicable VA stakeholders for an Authority to Operate (ATO) to interface the hosted environments to the VA Network. The Contractor shall provide all Assessment and Authorization (A&A) support and documentation required to achieve and maintain full A&A certification using the process specified in the FedRAMP Program Requirements.
Be fully responsible and accountable for ensuring compliance with all HIPAA, Privacy Act, Federal Information Security Management Act (FISMA), National Institute of Standards and Technology (NIST), Federal Information Processing Standards (FIPS), and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerability scanning, continuous monitoring, 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.
Ensure adequate security controls for collecting, processing, transmitting, and storage and removal of Personally Identifiable Information (PII) and Personal Health Information (PHI), 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.
Ensure these security controls are to be assessed and stated within the Privacy Impact Assessment (PIA) and if these controls are determined not to be in place, or inadequate, a Plan of Action and Milestones (POA&M) shall be submitted and approved prior to the collection of PII and PHI.
The Contractor shall be responsible for generating the A&A ATO Package that includes the following security documentation IAW Appendix C Authorization Requirements SOP:
System Security Plan (SSP),
Risk Assessment (RA),
Incident Response Plan (IRP),
Information Security Contingency Plan (ISCP),
Disaster Recovery Plan (DRP),
Configuration Management Plan (CMP),
Interconnection Security Agreement/Memorandum of Understanding (ISA/MOU),
Additional system description/and diagrams required by VA to gain access to VA network and receive an Authority to Operate (ATO).
1.3.2 ASSESSMENT, AUTHORIZATION, and CONTINUOUS MONITORING
The information system solution selected by the Contractor shall comply with the Federal Information Security Management Act (FISMA).
The Contractor shall comply with FedRAMP requirements as mandated by Federal laws and policies, including making available any documentation, physical access, and logical access needed to support this requirement.
Following guidance from the Federal CIO, VA will utilize existing JAB ATO or agency ATO issued by another agency as a starting point for FedRAMP requirements. If neither of those exist, VA will sponsor FedRAMP ATO. VA will be using the FedRAMP baselines as a starting point, since they are specifically tailored for cloud services.
The Contractor shall, where applicable, assist with the VA Authority to Operate (ATO) Process to help achieve agency authorization of the cloud service or migrated application.
The Contractor shall afford VA access to the Contractor s and Cloud Service Provider s facilities, installations,technical capabilities, operations, documentation, records, and databases.
If new or unanticipated threats or hazards are discovered by either VA or the Contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party
The Contractor shall not release any data without the consent of VA in writing. All requests for release must be submitted in writing to the COR/CO.
Trusted Internet Connection (TIC) Include TIC requirements for SaaS that interfaces with VA systems, SaaS must meet all VA Security requirements for non-SaaS.
Include Addendum A Additional VA Requirements, Consolidated
A&A ATO Package
Plan of Action and Milestones
1.3.3 PEER REVIEW APPLICATION - FedRAMP REQUIREMENT
The Peer Review application shall be hosted on a FedRAMP-Low certified cloud solution. The Contractor shall provide a copy of the certificate issued granting Authority to Operate the cloud provider that is hosting the Peer Review application. The Contractor shall maintain its security authorization throughout the contract period of performance.
A. FEDRAMP Low Certification
1.4 TRAINING AND TRAINING DOCUMENTS/MATERIALS
The Contractor shall provide two virtual Instructor led training sessions (on skype or webex) with the approximately 200 users on the operations and functionality of the software including a troubleshooting section. The training shall also include procedures to submit radiotherapy treatment plans to the Contractor cloud RT-PACS server. The Contractor shall deliver the PowerPoint Training Slide Deck. The Contractor shall record the training session and provide a copy of the recorded training session playable on MS Windows10 environment. The Contractor shall coordinate with the COR to schedule the training sessions to be completed prior to software going operational.
The Contractor shall conduct quarterly virtual software update webinar sessions (via skype/webex) to approximately 100 users in the VA. The Contractor shall deliver the Quarterly webinar PowerPoint Training Slide Deck. The Contractor shall record the Quarterly webinar training session and provide a copy of the recorded training session playable on MS Windows10 environment. The Contractor shall coordinate with the COR to schedule the Quarterly webinar training sessions with the COR.
PowerPoint Training Slide Deck and Video.
Quarterly Webinar PowerPoint Training Slide Deck and Video.
1.5 HELP DESK SUPPORT
The Contractor shall provide Help Desk support to Users in resolving problems encountered using the Radiation Oncology Peer Review software. The Help Desk support shall include users access to live chat, email, toll free telephonic support. The support shall be available Monday through Friday 8 AM to 8 PM Eastern Time.
The Contractor shall maintain a Help Desk trouble ticket log. The trouble ticket log shall log the date and time of the original help desk request, date and time of initial response, detailed description of action(s) taken, including date and time of each action, name of technician, and date and time of final resolution.
1.6 CONTRACT AWARD MEETING
The contractor shall not commence performance on the tasks in this Product Description until the CO has conducted a kick off meeting or has advised the contractor that a kick off meeting is waived.
1.7 CONTRACTOR PROJECT MANAGEMENT PLAN
The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor s approach, tasks, subtasks, timeline and tools to be used in execution of the contract. Â The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support.Â Â The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the Product Description (PD). The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.
Contractor Project Management Plan
1.8 Monthly status briefing
The Contractor shallsubmit monthly status reports to present previous month activities, open issues, risk and mitigation actions, issues closed and Help Desk activities from the trouble ticket log. The contractor status report should include any action items from the pervious month s status report.
Monthly Status reports
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:
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
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 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
VA TECHNICAL REFERENCE MODEL
The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OI&T 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 OI&T. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.
ADDENDUM B VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE
APPLICABLE PARAGRAPHS TAILORED FROM: THE VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE, VA HANDBOOK 6500.6, APPENDIX C, MARCH 12, 2010
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.
ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMS
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.
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.
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.
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 (e.g. Business Associate Agreement, Section 3G), 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.
The Contractor or Subcontractor must notify the CO 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 CO must also be notified immediately by the Contractor or Subcontractor prior to an unfriendly termination.
VA INFORMATION CUSTODIAL LANGUAGE
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 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).
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 information is returned to 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.
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 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 CO 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 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.
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.
If a VHA contract is terminated for cause, the associated Business Associate Agreement (BAA) must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.05, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship.
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.
The Contractor/Subcontractor s firewall and Web services security controls, if applicable, shall meet or exceed VA 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 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 CO 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 CO for response.
For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require Assessment and Authorization (A&A) or a Memorandum of Understanding-Interconnection Security Agreement (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 COR.
INFORMATION SYSTEM DESIGN AND DEVELOPMENT
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 VA Handbook 6500, Risk Management Framework for VA Information Systems Tier 3: VA Information Security Program, and the TIC Reference Architecture). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COR, and approved by the VA Privacy Service in accordance with Directive 6508, Implementation of Privacy Threshold Analysis and Privacy Impact Assessment.
The Contractor/Subcontractor shall certify to the COR 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 VA. This includes Internet Explorer 11 configured to operate on Windows 7 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, Risk Management Framework for VA Information Systems Tier 3: VA 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:
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:
The Systems of Records (SOR); and
The design, development, or operation work that the Contractor/Subcontractor is to perform;
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
Include this Privacy Act clause, including this subparagraph (c), 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 considered to be an employee of the agency.
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.
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.
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.
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, hot fixes, 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.
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 7 days.
When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to 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 7 days.
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 CO and the VA Assistant Secretary for Office of Information and Technology.
INFORMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USE
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 vulnerability 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 COR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA network involving VA information must be in accordance with the TIC Reference Architecture and reviewed and approved by VA prior to implementation. For Cloud Services hosting, the Contractor shall also ensure compliance with the Federal Risk and Authorization Management Program (FedRAMP).
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.
Outsourcing (Contractor facility, Contractor equipment or Contractor staff) of systems or network operations, telecommunications services, or other managed services requires A&A of the Contractor s systems in accordance with VA Handbook 6500.3, Assessment, Authorization and Continuous Monitoring of VA Information Systems 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 security 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.
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 CO and the ISO for entry into the VA POA&M management process. The Contractor/Subcontractor must use the VA 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 affect the privacy or security of the data or the system, the A&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, and Contingency Plan). The Certification Program Office can provide guidance on whether a new A&A would be necessary.
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 COR. The Government reserves the right to conduct such an assessment using Government personnel or another Contractor/Subcontractor. The Contractor/Subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weaknesses discovered during such testing, generally at no additional cost.
VA prohibits the installation and use of personally-owned or Contractor/Subcontractor owned equipment or software on the VA network. If non-VA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW or contract. All of the security controls required for Government furnished equipment (GFE) must be utilized in approved other equipment (OE) and must be funded by the owner of the equipment. All remote systems must be equipped with, and use, a VA-approved antivirus (AV) software and a personal (host-based or enclave based) firewall that is configured with a VA approved configuration. Software must be kept current, including all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-viral software and the firewall on the non-VA owned OE.
All electronic storage media used on non-VA leased or non-VA owned IT equipment that is used to store, process, or access VA information must be handled in adherence with VA Handbook 6500.1, Electronic Media Sanitization upon: (i) completion or termination of the contract or (ii) disposal or return of the IT equipment by the Contractor/Subcontractor or any person acting on behalf of the Contractor/Subcontractor, whichever is earlier. Media (hard drives, optical disks, CDs, back-up tapes, etc.) used by the Contractors/Subcontractors that contain VA information must be returned to VA for sanitization or destruction or the Contractor/Subcontractor must self-certify that the media has been disposed of per 6500.1 requirements. This must be completed within 30 days of termination of the contract.
Bio-Medical devices and other equipment or systems containing media (hard drives, optical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:
Vendor must accept the system without the drive;
VA s initial medical device purchase includes a spare drive which must be installed in place of the original drive at time of turn-in; or
VA must reimburse the company for media at a reasonable open market replacement cost at time of purchase.
Due to the highly specialized and sometimes proprietary hardware and software associated with medical equipment/systems, if it is not possible for VA to retain the hard drive, then;
The equipment vendor must have an existing BAA if the device being traded in has sensitive information stored on it and hard drive(s) from the system are being returned physically intact; and
Any fixed hard drive on the device must be non-destructively sanitized to the greatest extent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be preapproved and described in the purchase order or contract.
A statement needs to be signed by the Director (System Owner) that states that the drive could not be removed and that (a) and (b) controls above are in place and completed. The ISO needs to maintain the documentation.
SECURITY INCIDENT INVESTIGATION
The term security incident means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The Contractor/Subcontractor shall immediately notify the COR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the Contractor/Subcontractor has access.
To the extent known by the Contractor/Subcontractor, the Contractor/Subcontractor s notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the Contractor/Subcontractor considers relevant.
With respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.
In instances of theft or break-in or other criminal activity, the Contractor/Subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and Security and Law Enforcement. The Contractor, its employees, and its Subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The Contractor/Subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident.
LIQUIDATED DAMAGES FOR DATA BREACH
Consistent with the requirements of 38 U.S.C. Â§5725, a contract may require access to sensitive personal information. If so, the Contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the Contractor/Subcontractor processes or maintains under this contract. However, it is the policy of VA to forgo collection of liquidated damages in the event the Contractor provides payment of actual damages in an amount determined to be adequate by the agency.
The Contractor/Subcontractor shall provide notice to VA of a security incident as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non-Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.
Each risk analysis shall address all relevant information concerning the data breach, including the following:
Nature of the event (loss, theft, unauthorized access);
Description of the event, including:
date of occurrence;
data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;
Number of individuals affected or potentially affected;
Names of individuals or groups affected or potentially affected;
Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;
Amount of time the data has been out of VA control;
The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons);
Known misuses of data containing sensitive personal information, if any;
Assessment of the potential harm to the affected individuals;
Data breach analysis as outlined in 6500.2 Handbook, Management of Breaches Involving Sensitive Personal Information, as appropriate; and
Whether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.
Based on the determinations of the independent risk analysis, the Contractor shall be responsible for paying to VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:
One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;
Data breach analysis;
Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;
One year of identity theft insurance with $20,000.00 coverage at $0 deductible; and
Necessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.
SECURITY CONTROLS COMPLIANCE TESTING
On a periodic basis, VA, including the Office of Inspector General, reserves the right to evaluate any or all of the security controls and privacy practices implemented by the Contractor under the clauses contained within the contract. With 10 working-day s notice, at the request of the Government, the Contractor must fully cooperate and assist in a Government-sponsored security controls assessment at each location wherein VA information is processed or stored, or information systems are developed, operated, maintained, or used on behalf of VA, including those initiated by the Office of Inspector General. The Government may conduct a security control assessment on shorter notice (to include unannounced assessments) as determined by VA in the event of a security incident or at any other time.
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:
Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Information Security Rules of Behavior, updated version located at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4848, relating to access to VA information and information systems;
Successfully complete the VA Privacy and Information Security Awareness and Rules of Behavior course (TMS #10176) and complete this required privacy and information security training annually;
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 CO 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.]
The Contractor shall provide to the CO and/or the COR a copy of the training certificates and certification of signing the Contractor Rules of Behavior for each applicable employee within 2 days of the initiation of the contract and annually thereafter, as required.
Failure to complete the mandatory annual training and electronically 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.
- Opportunity closing date
- 14 August 2019
- Value of contract
- to be confirmed
About the buyer
- Department of Veterans Affairs VA Technology Acquisition Center United States
The deadline to apply for this opportunity has passed.
Visit the opportunities page to find another.