RFQ 36C10B26Q0213_FINAL.docx

36C10B26Q0213

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD: $34M

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

UEI:

EFT:

PHONE:

FAX:

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

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

ITEM NO.

SCHEDULE OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

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

25. ACCOUNTING AND APPROPRIATION DATA

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

ARE

ARE NOT ATTACHED.

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

ARE

ARE NOT ATTACHED

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

29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

DATED ________________________________. YOUR OFFER ON SOLICITATION

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

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

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

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

AUTHORIZED FOR LOCAL REPRODUCTION

(REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

03-10-2026 Sean McAvoy – Contract Specialist 848-377-5094 03-17-2026

12PM

EST

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541511

N/A

See Section B.

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724 L4267

LES SYSTEMES MEDICAUX INTELERAD INCORPOREE

INTELERAD MEDICAL SYSTEMS

800 BOUL. DE MAISONNEUVE E 12TH FLOOR

MONTREAL, QUEBEC H2L 4L8

Department of Veterans Affairs

Financial Services Center PO Box 149971 Austin, TX 78714-8971

National Teleradiology Program (NTP) Picture Archive and Communication System (PACS) Upgrade

Period of Performance: 18 months from date of award, with one (1) 12-month option period.

The resultant contract will be Firm Fixed Price.

Points of Contact:

Sean McAvoy, Contract Specialist sean.mcAvoy@va.gov 848-377-5094

Kathryn Pantages, Contracting Officer

Kathryn.pantages@va.gov 848-377-5039

Kathryn Pantages Contracting Officer

Table of Contents

SECTION B – CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

b. GOVERNMENT: Contracting Officer 36C10B, Kathryn Pantages/Kathryn.pantages@va.gov

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

3. INVOICES: Invoices shall be submitted in arrears:

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

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

B.2 GOVERNING LAW CLAUSE

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), Source Code Harmonization and Reuse in Information Technology Act “SHARE IT Act” (P.L. 118-187), and FAR clauses 52.212-4 and 52.227-14 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14, this includes any custom code developed for the purpose of performing under this contract. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.3 SOFTWARE LICENSE, MAINTENANCE, AND TECHNICAL SUPPORT

(1). Definitions.

a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements, or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2). Software License.

a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software.

b) The Government may use the software in a networked environment.

c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

d) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

(3). Software Maintenance and/or Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/Order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received, the Contractor is neither authorized nor permitted to renew any of the previously furnished services.

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers to cause the software to perform according to its specifications, documentation or demonstrated claims.

c) Any telephone support provided by Contractor shall be at no additional cost.

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding two business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.gov).

e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4). Disabling Software Code.

The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out, or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications.

Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

B.4 PRICE SCHEDULE

All days referenced below shall be considered calendar days, unless otherwise noted. All items are Inspection/Acceptance/FOB Destination.

Any resulting contract will be awarded on a firm-fixed-price basis as defined by Federal Acquisition Regulation Subpart 16.202. Accordingly, the Contractor shall ensure that any and all costs associated with the Contractor’s proposed application(s), software products, software solution, and/or system, shall be included in the Contractor’s proposed firm-fixed price, and shall serve as the Contractor’s firm-fixed price for the life of any resulting contract. No additional costs or fees relative to the Contractor’s proposed application(s), software products, software solution, and/or system including, but not limited to, licensing costs and any associated licensing maintenance required for the development, delivery, integration, operation, and/or maintenance of the Contractor’s proposed solution will be allowed, accepted, and/or paid by the Government.

Base Period

The Base Period of Performance (PoP) shall be 18 months from date of award.

Project Management Project Management in accordance with (IAW) the Performance Work Statement (PWS) paragraph 5.1, inclusive of all subparagraphs.

This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all travel, labor and deliverables required for the successful completion of services detailed in PWS paragraph 5.1, inclusive of all subparagraphs.

Product and Service Code (PSC): DA10 - IT and Telecom—Business Application/Application Development Software as a Service

The price of this CLIN shall be allocated to CLIN 0002 and CLIN 0003.

Period of Performance: 18 months

MO

NSP

NSP

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

LO

NSP

NSP

NTP PACS Upgrade IAW PWS paragraph 5.2 and 5.3, inclusive of all subparagraphs.

This FFP CLIN includes all travel, labor, materials, and deliverables required for the successful completion of the requirements detailed in PWS paragraphs 5.2 and 5.3, inclusive of all subparagraphs.

PSC: DA10

Invoices may be submitted upon successful completion of the tasks IAW with the following:

Government approval of invoices for payment shall be subject to successful completion of task requirements and associated deliverables required by the PWS.

Period of Performance: up to 6 months

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 14 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 14 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 14 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 14 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 14 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Due 30 days after award of the contract and updated monthly thereafter throughout the PoP.

Upgraded IntelePACS Service and Support IntelePACS service and support IAW PWS paragraph 5.4, inclusive of all subparagraphs.

This FFP CLIN includes all travel, labor, materials, project management and deliverables required for the successful completion of the requirements detailed in PWS.

PSC: DA10

*The unit price shall equal the monthly unit price for uptime performance of 99.9% and above.

IAW PWS paragraph 5.4.3, please complete the chart below with your proposal to include discounted monthly pricing in the event of system uptime lower than 99.9%:

The Contractor shall invoice monthly based on the number of exams complete in the preceding month. Government approval of invoices for payment shall be subject to successful completion of task requirements and associated deliverables required by the PWS.

Period of Performance: Up to 18 months. The PoP shall begin upon successful completion of NTP PACS Upgrade (CLIN 0002)

Due 30 days after go-live and updated monthly thereafter throughout the PoP.

Due 30 days after go-live and updated monthly thereafter throughout the PoP.

Option Period One This 12-month option may be exercised in accordance with FAR 52.217-9, Option to Extend the Term on the Contract. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, Option Period One shall begin immediately after expiration of the Base Period.

Project Management in accordance with (IAW) the Performance Work Statement (PWS) paragraph 5.1, inclusive of all subparagraphs.

This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all travel, labor and deliverables required for the successful completion of services detailed in PWS paragraph 5.1, inclusive of all subparagraphs.

PSC: DA10

The price of this CLIN shall be allocated to CLIN 1002.

Period of Performance: 12 months

Due monthly throughout the PoP.

NSP

NSP

NSP

NSP

NSP

NSP

IntelePACS service and support IAW PWS paragraph 5.5, inclusive of all subparagraphs.

This FFP CLIN includes all travel, labor, materials, project management and deliverables required for the successful completion of the requirements detailed in PWS.

PSC: DA10

*The unit price shall equal the monthly unit price for uptime performance of 99.9% and above.

IAW PWS paragraph 5.4.3 please complete the chart below with your proposal to include discounted monthly pricing in the event of system uptime lower than 99.9%:

The Contractor shall invoice monthly based on the number of exams complete in the preceding month. Government approval of invoices for payment shall be subject to successful completion of task requirements and associated deliverables required by the PWS.

Period of Performance: 12 months

Due 30 days after Option Period is exercised and updated monthly thereafter throughout the PoP.

Due 30 days after Option Period is exercised and updated monthly thereafter throughout the PoP.

Option Period One Total

Optional Task

This Optional Task may be exercised at any time and from time to time during the base period of performance up to the maximum number of months specified in the CLIN in accordance with FAR 52.217-7, Option for Increased Quantity-Separately Priced Line Item. Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

IntelePACS Legacy Hardware and Software service and support IAW PWS paragraph 5.6, inclusive of all subparagraphs

This FFP CLIN includes all travel, labor, materials, project management and deliverables required for the successful completion of the requirements detailed in PWS.

PSC: DA10

*This CLIN may be exercised in 1 month increments.

Government approval of invoices for payment shall be subject to successful completion of task requirements and associated deliverables required by the PWS.

Period of Performance: up to 12 months

Due 30 days after exercising of Optional Task and updated monthly thereafter throughout the PoP.

Optional Task Total

TOTAL BASE PERIOD + OPTION PERIOD ONE + OPTIONAL TASK

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration (VHA) National Teleradiology Program (NTP) IntelePACS Upgrade 2026

Date: 02/26/2026

VA-26-00042676

PWS Version Number: 2.0

1.0 BACKGROUND

The Veteran Health Administration (VHA) National Teleradiology Program (NTP) is the Department of Veterans Affairs (VA) in-house Teleradiology service and has been providing 24x7 Teleradiology service to VA facilities since 2010. NTP is currently supporting over 120 sites across all Veterans Integrated Service Networks (VISNs). Yearly workload is approximately 1.4 million exams of which 80% are STAT interpretations. Currently NTP has approximately 230 Picture Archive and Communication System (PACS) workstations distributed across remote users and in-house reading centers providing remote Radiology interpretations.

NTP’s current Teleradiology PACS archive (IntelePACS) and core application servers are located in the Sacramento Data Center, and the software and hardware are well past their end of life. Additional servers are located in regional data centers and NTP reading centers and those system are similarly past their useful life. NTP requires an upgrade of the existing IntelePACS software to the latest commercially available release while providing ongoing service/support to the legacy system until the upgrade is approved for clinical use.

In November 2018, VA issued the Cloud First Policy mandating that all new and existing Information Technology (IT) solutions be assessed to determine suitability to be offered as an enterprise cloud computing service. The VA Enterprise Cloud (VAEC) was established by the Enterprise Cloud Solutions Office (ECSO) in 2017, to host cloud computing solutions. The upgraded system shall be deployed in the VA Enterprise Cloud (VAEC) and the VA shall be responsible for VAEC hosting, while the Contractor shall provide all software and licenses beyond items within the VAEC catalog. The Contractor shall be responsible for managing all VAEC resources associated with the PACS as part of initial deployment and ongoing service and support.

2.0 APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

2. Federal Information Processing Standards (FIPS) Publication 140-3, “Security Requirements for Cryptographic Modules”, March 22, 2019

3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022

6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

7. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters

9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

10. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

11. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended

14. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

15. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended

16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025

25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

26. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

27. OIT Process Asset Library (PAL), OIT Process Asset Library.

28. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

30. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024

31. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024

32. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

33. VA Directive 6300, “Records and Information Management,” September 21, 2018

34. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

39. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

40. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

41. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

44. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

46. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

47. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

48. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

49. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

50. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

51. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

52. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007

53. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

54. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

55. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

56. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

57. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

58. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

59. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

60. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

61. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

62. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

63. Social Security Number (SSN) Fraud Prevention Act of 2017

64. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

65. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

66. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

67. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

68. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

69. OMB M-22-18, “Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” September 14, 2022

70. OMB M-23-16, “Update to Memorandum M-22-18,” June 9, 2023

71. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

78. VA Enterprise Cloud Technical Reference Guide, Version 1.3 July 2018

3.0 SCOPE OF WORK

The Contractor shall upgrade NTP’s existing IntelePACS system from version 4.9 to version 5.7, or the latest commercially available version, and migrate all NTP specific applications to the upgraded platform. The upgraded IntelePACS system shall be installed and hosted in the VAEC infrastructure, specifically Azure Virginia with dual availability zone configuration for fail-over and hardened to VA baseline configurations. The Contractor shall provide activation and installation services of software, testing, validation and training of the software on the VAEC. There shall be design and deployment of NTP custom tools. The Contractor shall obtain and maintain a VA Authority to Operate (ATO). There shall be support and maintenance of the system after the system is deployed.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The period of performance (PoP) shall be 18 months from date of award with 1 12-month option period and 1 optional task. The base period includes up to 6 months for system deployment and acceptance, followed by ongoing service and support post go-live. Option Period One includes 12 months of ongoing service and support after the base period. Optional Task One includes service and support of the legacy IntelePACS which may be exercised at any time and from time to time during the base PoP, up to a maximum of 12-months.

4.2 PLACE OF PERFORMANCE

Tasks under this Performance Work Statement (PWS) shall be performed at Contractor facilities via remote access to the VA network utilizing Personal Identity Verification (PIV). The Contractor shall identify the Contractor’s place of performance in their proposal submission. Applications training will be provided remotely and may include contractor-hosted web-based training and on-line meetings.

4.3 TRAVEL

The Government does not anticipate travel to perform the tasks associated with the effort, as work such as installation of software and service/support will be via remote access. Any travel costs will not be directly reimbursed by the Government and will be included within the Contractor’s implementation work.

4.4 GOVERNMENT FURNISHED PROPERTY

The Government shall provide:

· Cloud capacity in and connectivity to the VA Enterprise Cloud (VAEC) environments.

· VA Enterprise Cloud Operational Tools (VAECOT) comprised of a suite of COTS cloud management tools as identified in the VAEC Technical Reference Guide

· Enterprise Development Environment (EDE) and Tools as identified in the VAEC Technical Reference Guide

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the tasks with specific milestones as outlined below:

Installation and configuration of VAEC servers, storage, and software

Activation, testing, and validation of all Digital Imaging and Communications in Medicine (DICOM) interfaces

Activation, testing, and validation of all HL7 interfaces

Design, implementation, and deployment of NTP custom workflow tools equivalent to or better than existing

Obtain VA Authority to Operate (ATO) for core PACS and Enterprise Risk Analysis (ERA) for workstations, to include ongoing updates, serving in the role of System Steward/Control Owner

Import of all reports from legacy PACS to upgraded PACS

PACS service/support for upgraded IntelePACS v5.7 or newer post deployment

Upgrade must be completed no later than September 30, 2026. System may be put into clinical use during the implementation phase as part of system validation, but it must be 100% operational with ALL functionalities as specified within this PWS before being considered complete.

The upgraded system will replicate or improve existing functionality and shall include at a minimum the following features/functionality:

· PACS archive with promiscuous DICOM interface to all VHA PACS and imaging modalities. DICOM ingest will be to a single load balanced IP address across both availability zones (multiple Application Entity Titles (AETs) to account for different workflows such as Telestroke, external peer review, etc. – matching existing functionality) and Query/Retrieve (Q/R) will present a single IP/AET to called VHA PACS.

· Diagnostic PACS viewer shall be optimized for WAN streaming.

· Fully integrated PACS worklist/assignment engine designed to optimize turn-around times, ensure reading prioritization and subspecialty assignment. Assignment Engine shall assign based off prioritization and first in first out.

· Assigned RadPeer peer review as well as peer learning modules.

· Collaboration functionality in the PACS shall generate a pop-up message in front of other windows so that Radiologists can clearly see the notification.

· Critical and non-critical callback workflow for PACS Assistants.

· When a Critical exam comes in that needs immediate attention, notification shall happen in front of all windows so that Radiologists know they need to address a critical exam immediately.

· Suspend button for Radiologists when they take breaks or are preparing to end their shift so they do not get additional cases assigned to them.

· PACS shall combine images, order, and report artifacts into a combined study and show only once on the worklist.

· Acquisition Traffic Controller (ATC) Worklist for case review and processing to mirror existing functionality. ATC to include thumbnail view of series received, pertinent study information, 1-click current and prior image retrieval with automated listing of available images based on prior report availability and targeted c-find to facilities/VISN where the patients have previously received case in VHA.

· Fully functional test system scaled for 10% load for update/upgrade testing and Oracle Health Federal Electronic Health Record (OH FEHR) integration testing.

· System shall be configured initially with 6 months of image storage capacity.

· Master Patient Index (MPI) functionality to consolidate disparate patient identifiers in use by VA: Social Security Number (SSN) with dashes, SSN without dashes, and Electronic Data Interchange Personal Identifier (EDIPI) (OH FEHR identifier). Must be able to manage patients with multiple IDs as a single entity and must have DICOM Q/R intelligence to query source PACS using the primary patient ID used by that specific VA location.

· DICOM normalization per existing IntelePACS standard.

· Image fusion module along with Positron Emission Tomography (PET) viewer and 3D reformatting tools.

· FDA cleared mammography viewer/tools with integration to NTP provided mammography tracking system (MagView), Densitas and Transpara AI modules with Secondary Capture (SC) and Presentation State (PR) writeback to sending mammography PACS.

· System shall include image quality, support assist and critical callback modules.

· Deployment shall include ingestion of all existing reports from current IntelePACS.

· Ongoing support shall include HL7 configuration support for OH FEHR conversion and VistA updates, e.g. HL7 2.3 to HL7 2.4 conversion.

· Activation to be completed within 6 months of contract award.

· Estimated study volume of 1.5 million exams with 10% buffer.

The contractor shall interface the upgraded IntelePACS with the following VHA provided components to provide a fully integrated teleradiology system:

· Voice Recognition (VR) - Existing VHA provided PowerScribe One v2109 system (VAEC Azure Virginia).

· Artificial Intelligence (AI) - Existing VHA provided Blackford AI platform with ICH, LVO, Breast Density, and Breast Nodule Detection (VAEC Azure Virginia) – image routing and worklist escalation for positive findings will be primary integration points.

· HL7 Integration Engine – Existing VHA Provided Rhapsody HL7 engine (VAEC Azure Virginia) for VistA ORM and ORU integration and OH FEHR ORM, ORU and ADT integration.

· Foundations by Health Level – Existing VHA provided PACS analytics tool used for STAT Portal submissions, workflow tracking, productivity and NTP billing (Sacramento Data Center).

The Contractor shall support setup, configuration, and provisioning of the solution in the VAEC environments and work with VA to provide inputs for establishing VAEC capacity, accounts and privileges. This includes monitoring and tracking the creation, update, and deletion of application user (e.g., developer, systems administrator) accounts, and ensuring cloud capacity requirements are satisfied.

The Contractor shall Provide information and documentation to support operational and production readiness reviews and go-no-go decisions. The Contractor shall execute corrective actions to address gaps and provide all required data and prepare supporting documents/artifacts for the reviews

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, 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 PWS. 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.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft Word format. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

Deliverable:

A. Monthly Progress Report

5.2 NTP PACS UPGRADE

The Contractor shall upgrade the NTP PACS from IntelePACS version 4.9 and migrate all NTP PACS specific applications to version 5.7 or newer. The legacy NTP PACS must remain in continuous 24x7 operation throughout every stage of this upgrade.

The Contractor shall perform a review to identify functionality gaps between the current NTP IntelePACS deployment and IntelePACS version 5.7.

The Contractor shall provide an Identified Applications Report which shall include a list of each identified application with a 4.9 to 5.7 migration dependency and timeline to remediate.

The Contractor shall provide a project plan that outlines upgrade milestones throughout the course of the project.

Per VAEC requirements, the Contractor shall complete the following tasks:

· Develop and maintain the solution architecture aligned with the VAEC Technical Reference Architecture as well as the One-VA Enterprise Architecture. The Contractor shall design the VAEC hosted solution and address VA identified cloud-readiness gaps.

· Develop, maintain, and execute the VAEC Implementation Plan that defines the implementation approach, processes and activities (prior to, during, and after), test strategy, setup and configuration procedure, inventory of IT assets, implementation checklist, risk assessment, key dependencies, and schedule.

· Develop and update project’s VIP Deployment and Installation, Back-out, and Rollback Plan that describes the installation, back-out, and rollback approach, processes and activities, dependencies, and schedule. The plan shall also include the provisioning and installation procedures for VAEC resources.

· Determine cloud capacity and workload requirements. VA shall review and approve cloud capacity requirements and provide the VAEC cloud capacity for the solution as GFE.

Deliverables:

A. Identified Applications Report B. Overall Project Plan C. VAEC Solution Design D. VAEC Implementation Plan

5.3 AUTHORITY TO OPERATE

The Contractor shall develop necessary artifacts to obtain a VA authority to operate (ATO) for the solution and complete VA Assessment and Authorization (A&A) process. After ATO is achieved, the Contractor shall update and maintain the A&A documentation as required to ensure continued compliance.