PACS RFI 20250807.docx

DLA Troop Support Request for Information (RFI) 8/7/2025

I. Background

The Defense Logistics Agency (DLA) Troop Support is performing market research in preparation for a fifth-generation solicitation for medical Picture Archive and Communications System (PACS) products. Under the previous solicitation (SPE2D1-15-R-0004, “DIN-PACS IV”) and resultant multiple award contracts, DLA Troop Support and permitted ordering agencies, particularly the Department of Veterans Affairs (VA), have acquired radiology and cardiology PACS products. DLA Troop Support supports the PACS for Department of Defense (DoD) Military Services’ Medical Treatment Facilities worldwide, and other U.S. Government health agencies.

II. Purpose

This RFI is being issued to identify interested PACS vendors and inquire about their system’s unique capabilities and value-added features that are currently available for sale to commercial customers and/or the U.S. Government. The focus of this RFI is on commercial offerings in the following “Ologies” and integration with the Vendor Neutral Archive (VNA): Radiology, Cardiology, Ophthalmology, Dental, Oncology, Endoscopy, OB/GYN, Nuclear Medicine, Point-of-Care Ultrasound, Sleep Lab, Pathology, and Veterinary.

III. Disclosure

This RFI is issued solely for information and planning purposes and is not a solicitation for proposals, proposal abstracts, or quotations. Release of this RFI shall not be construed as a commitment to procure items or services. Responses are not offers and cannot be accepted by the Government to form a binding contract. Responses will assist the Government in the development of its acquisition strategy, including the determination of small business capabilities and interest in any possible future acquisition.

Any information provided in response to this RFI which the vendor considers to be proprietary must be clearly identified by the vendor as proprietary, which will be handled accordingly. Information not specifically marked as proprietary will be considered and treated as unrestricted information. All information, comments, and suggestions determined to be beneficial to DLA Troop Support may be incorporated into future acquisition documents or contracts, without identifying the source or obtaining prior approval from the source, unless it has expressly and specifically been designated as proprietary by the vendor.

Information provided in response to this RFI may be shared between DLA and Defense Health Agency (DHA).

The Government will not pay for any information or administrative cost incurred in response to this RFI; all associated costs with responding to this RFI are solely at the respondent’s expense.

IV. Vendor Questions

**Please note that responses to questions should be based on current system capabilities and product/software releases. A vendor’s planned future offerings should only be discussed if a question specifically requests such information. Additionally, responses to this RFI should not include any products that rely on the cloud, in whole or in part, in their operation.

Responses to these questions are due via email to DIN-PACSV@dla.mil no later than (11:00 AM EST on Tuesday, August 19, 2025.) Please include “August 2025 PACS RFI Response” in subject line.

Vendor Name: _______________________________ Vendor UEI Number (or indicate if not currently registered in SAM.gov): __________________

1. Vendor Products

(a) Initial Description.

(1) Briefly describe your PACS platform, including primary and additional Ologies involved (refer to Section II Purpose, above, for Ologies under consideration). Please include product names/versions and types (e.g. storage, workstations, software).

(2) What are the minimum technical requirements for product performance, e.g. viewer bandwidth, image transfer, storage?

(3) Does your firm provide maintenance plans for each product? If so, please briefly describe how your firm defines updates/upgrades in relation to your vendor intellectual licensed software application and operating system, and how these are covered in your commercial maintenance plan.

(4) Does your PACS interface with other vendor provided systems (including other vendor PACS) in a vendor neutral manner without modification, and without loss of any functionality with either system?

(5) List all modalities (by type, not individual model) that can interface with your PACS platform.

(6) Does your PACS use both DICOM and HL7 standards? Does your PACS support non-DICOM formats (i.e. JPEG, PNG, TIFF, GIF, and BMP), if so which ones?

(7) Does your PACS currently integrate, or have the capability to integrate, with MHS GENESIS (Oracle Cerner Millennium, Dentrix Enterprise, Rhapsody), Veterans Health Administration (VHA) VistA, and VHA Oracle Cerner Millennium, which are the current respective DoD/VA Electronic Health Records (EHR)? Is your PACS able to connect bidirectionally with these EHRs, if so, how is this accomplished?

(8) What is your backup plan for any provided software (including third party) inability to integrate with customer (DoD/VA) clinical information systems and enterprise applications?

(9) What is your procedure for performing quick data migration from a legacy system to a new system, and what is the turnaround time for this process?

(10) What is your system capability for future growth to accommodate increasing patient study volume and image storage?

(11) What strategy does your firm employ to mitigate high latency environments while pulling from the VNA, rendering images, transferring images to other facilities, etc.?

(12) Have your products received any recognized certifications to ensure they meet specific standards for functionality, security, and interoperability regarding structured image data and secure sharing of this data (e.g. Center for Medicare & Medicaid Services’ Meaningful-Use (MU), Office of the National Coordinator for Health Information Technology (ONC) Health IT Certification)?

(b) Workflow considerations.

(1) Does your PACS work as a single platform that can facilitate workflow from multiple independent hospital sections with different needs (i.e. radiology, cardiology, dental, ENT, ophthalmology, and other ologies)?

(2) Does your PACS manage workflow based on patients, providers, facilities connected to the network, tasks, mixed, customizable, etc.?

(3) Briefly describe any attributes/benefits of your system’s workflow management, including speed, accuracy, collaboration, patient care, and ability to integrate with other vendor systems without impacting functionality.

(4) Does your system support hanging protocols?

(i) Are your system’s hanging protocols customizable on a per facility, per doctor basis?

(ii) Does your system learn hanging protocols based on login credentials?

(iii) Can the hanging protocols be standardized for teaching institutions?

(c) Toolsets.

(1) List all toolsets that are native to your product line. Indicate any ease-of-use benefits from a technical or clinical perspective.

(2) List all toolsets that depend on third party products, and if they are sold with your product. Indicate any ease-of-use benefits from a technical or clinical perspective.

(3) State whether the following visualization and analysis tools are available, and whether they are standard or optional, native or third party:

(i) Augmented Intelligence

(A) Brain: Detection of traumatic brain injury (TBI) and hemorrhagic stroke, but also for the identification and quantification of acute ischemic stroke

(B) Heart/Chest: Detection of Pulmonary Embolisms, Aortic Dissections, and perform bone suppressions

(C) Breast: Review 2D & Tomography 3D images to identify cancers

(D) Lung: Track and characterize lung nodules

(E) Worklist Orchestration: Ensure the right doctor receives the right type of images in a seamless swift manner (Specialty Radiologist & Enabling Critical Results)

(F) Other

(ii) Data mining and reporting for clinical and technical parameters

(iii) Critical Test Results Management

(iv) Multi-site Peer Review

(v) Teaching Files

(vi) Lesion management

(vii) Cardiac perfusion analysis

(viii) Advanced 3D rendering, visualization, analysis

(ix) ECG management, non-DICOM

(x) Toolsets for non-DICOM modalities, multiple ologies

(xi) Advanced pulmonary and orthopedic analysis tools, native to the PACS

(xiii) Other (add any additional relevant tools if not listed – see Section II Purpose)

(4) Does your PACS come with integrated voice dictation, orthopedic templating software, 3D reconstruction software, etc.? Are these options available to the Government? Does your PACS integrate with third-party voice products – such as Nuance Powerscribe?

(5) Regarding system messaging options: Does your PACS have integrated messaging tools that allow colleagues to discuss studies while physically at separate and possibly distant locations?

(d) Web-based tools.

(1) Can the users perform Quality Control tasks using a web-based interface, without the need for a dedicated PACS workstation?

(2) In addition to viewing, please identify what other system functionality (i.e. Reporting, workflow management, etc.) is available via the Web Viewer?

(3) Is full functionality of the PACS achievable remotely (from non-MTF site locations) and/or from non-PACS workstations?

(e) Maintenance.

(1) Does your system rely on remote support for correcting failures and downtime, or are field support engineers/techs typically available to physically arrive at the facility within a short period of time? What is typical? What access do you solely rely on?

(2) How is monitoring accomplished for 99.9% total system and individual component uptime per month?

(3) What is the frequency of any system updates, and how often will the system have to be taken offline for maintenance, and/or software updates or upgrades?

(4) Reference question (a)(3) above, if updates/upgrades are not covered in your commercial maintenance plan, how would your firm structure a maintenance plan for the Government so that updates/upgrades are covered?

2. Security

All systems that connect to either the DoD or VA networks are required to meet current respective DoD and VA Cybersecurity (RMF) & Authority to Operate (ATO) requirements.

(a) Is your firm (at a time to be stated in a future solicitation or fair opportunity process) willing to obtain and maintain an ATO through the RMF/Cybersecurity processes? Note: For Government contracts, all 3rd party accessories or components of PACS must also meet the RMF/Cybersecurity requirements. Part of this process includes completing a Medical Device and Equipment Risk Assessment (MDERA). The attached MDERA is for REFERENCE ONLY – do not complete or submit in response to this RFI.

(b) If your response to (a) is affirmative, is your firm able to directly make any required modifications to your firm’s software (including proprietary code), third party software, and hardware, to meet cybersecurity/RMF requirements, or is your firm reliant on third parties to make these changes?

(c) Is your firm capable of identifying (down to the PACS component/sub-component level) all countries of origin involved in component manufacturing/production, and changing production lines as security threats are identified and considered high risk?

(d) What security measures do you have in place to protect storing and transferring patient data? Does your system use Secure Sockets Layer (SSL) for secure data transfer? If so, what version?

3. Previous Government experience

(a) Has your firm received Government contracts for your PACS offerings. If so, please provide the name of each Government Agency in which a contract was awarded for your system(s), a brief description of the contract scope (including Ologies involved and study capacity), contract length, and an estimate of the total contract dollar value over the life of the contract.

(b) If a Government contract was received, what is the difference, in terms of software and hardware, of any system offered commercially and the Government offered counterpart (particularly with respect to cybersecurity)?

(c) Additionally, what is the difference between any cyber-specific annual or routine maintenance/support provided on commercial offerings versus Government offerings?

(End)