Attachment 1 Specifications_11132026.xlsx
XLSX spreadsheet 48 KB Posted
- Solicitation number
- 36C10B27R0003
About this file
This file is a specifications attachment in spreadsheet format for the Department of Veterans Affairs Technology Acquisition Center Austin solicitation for a Radiology and Cardiology Foundational Enterprise Imaging System (Solicitation Number 36C10B27R0003). The specifications document outlines the technical and functional requirements that vendors must meet when submitting proposals for this enterprise imaging system procurement. The file serves as a detailed requirements matrix defining the capabilities, performance standards, and system specifications necessary for the radiology and cardiology imaging infrastructure that the VA intends to procure. Vendors responding to this solicitation must address how their proposed solutions align with and satisfy the specifications enumerated in this attachment to be considered for award under this opportunity.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment 2 Timeline.pdf | ||
| 36C10B27R0003.pdf | ||
| Attachment 3 20190620_VA DIRECTIVE 6550 V3 - Appendix A_Fillable 1.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| GENERAL SPECIFICATIONS | |
| In order to avoid requirement duplication it is implied that requirements apply to both Radiology and Cardiology unless otherwise noted. | |
| 1 | The prime vendor or principal subcontractor (providing 60% or more of the overall solution) shall be the Original Equipment manufacturer (OEM) of the PACS diagnostic viewer and vendor neutral archive and shall have current Food and Drug Administration (FDA) 510(k) clearance for applicable components. |
| 2 | The Contractor shall design, deploy, and support a radiology and cardiology enterprise imaging solution for the Veterans Health Administration with an estimated annual study volume of 12 million exams. The system shall be designed so that it can support all VHA Radiology, Cardiology and Nuclear Medicine exams performed in 18 Legacy VISNs and NTP. VHA requires the vendor provide a workflow orchestrator for workload shareing through specific shifts, roles, escalation rules and manual assigment of tasks. |
| 3 | Final signed reports and addendums recieved from the VHA electronic medical record shall be configured by the vendor to stored by the VHA PACS and be visible with or without images. |
| 4 | The system shall include integrated radiology and cardiology worklists that dynamically refresh to ensure study locking across the application in less than 0.5 seconds to prevent duplicate reading. NTP shall have a distinct worklist with designated assignment engine/workflow tools, while VISN PACS shall have the option to set up unique VISN-based or site-based worklists for their use. |
| 5 | The system shall provide seamless API integration with VA/DoD Joint Longitudinal Viewer (JLV), which requires the use of Clinical Context Object Workgroup (CCOW). This shall include a button or other mechanism to launch JLV directly from within the PACS application, have it pass patient context via CCOW to JLV, and then maintain patient context as different studies are viewed within the VHA PACS (i.e. update CCOW context). |
| 6 | VHA PACS and associated applications shall utilize application authentication using Single Sign-On (SSO). |
| 7 | The system is a mission/life-critical medical system that is required to be fully operational 24x7x365. The system shall be designed and deployed with appropriate redundancy and fault tolerance to eliminate single points of failure. The target uptime threshold for the overall system must be 99.99%. The Contractor’s design and technical support infrastructure must meet or exceed that level of performance. System shall be designed for 99.99% uptime as measured by 24x7 availability with performance penalties applied when uptime falls below 99.9% as calculated monthly. Downtime will be defined as failure of one or more components that measurably impacts VA’s ability to receive or interpret studies or transmit reports to the originating EMR. Contractor shall provide VHA with a monthly uptime report with adjusted billing of the ongoing service/support cost per the discount rate below. Note that scheduled downtime such as work to complete software upgrades and maintenance is excluded from the downtime calculation. Fail-over and/or test servers shall be used to perform these activities with little or no impact to the clinical operations. The system shall define and meet Recovery Time Objective (RTO) <=30 minutes and Recovery Point Objective (RPO) <=5 minutes for enterprise cardiology and radiology services, with documented cross-region failover testing performed at least annually. |
| NTP SPECIFIC SPECIFICATIONS | |
| 8 | Upon receipt of a recent unread study sent (or assigned via site worklist) for NTP interpretation, the system shall issue an automated preliminary “stub” to the VHA provided HL7 broker via HL7v2 message, within 2 minutes of complete study receipt. |
| 9 | The system shall support the removal of a NTP prelim report from VistA or Oracle Health Federal Electronic Health Record (OH FEHR) via transmission of a custom VAQ message via HL7v2. |
| 10 | Upon receipt of a preliminary or final HL7v2 encoded report generated by a VA customer site, the study shall automatically be removed from the NTP unread worklist. For sites using the system, their worklist shall include a designation that the study was assigned to NTP, but the HL7 message shall still be broadcast to VistA or OH FEHR for study tracking purposes. |
| 11 | Contractor shall provide database access to NTP's analytics application, Foundations, such that data can be extracted from VHA PACS to Foundations. Additionally, VHA PACS shall provide workflow status messages to Foundations via HL7 messages for tracking and analytics report creation. Sample workflow status messages include but are not limited to, image receipt, QA approved to dictate, study opened, report started, final report signed. |
| 12 | System shall interface with existing NTP STAT web portal (Foundations from Health Level) or contractor can provide a customer-facing web portal for Support interaction and case submission. STAT and Critical cases sent to NTP have 2 separate submission components: DICOM export of case to be read along with relevant priors and an accompanying web portal submission. The web portal submission is used by the Techs at the site to notify NTP that a case has been sent and it provides contact information if a callback is required, image count, exam notes. The existing web portal sends VHA PACS an HL7 message with the submitted information. That data shall be incorporated into VHA PACS for pre-read QC and Radiologist viewing. |
| 13 | System shall immediately assign critical exams (stroke and intraoperative radiograph) to a qualified Radiologist once processed by Support and shall be treated as the highest priority. Once cleared to read, the assigned Radiologist shall receive an automated notification within their worklist or viewing window alerting them that they have a case that needs immediate interpretation. Notification must popup into the foreground in front of all other windows. |
| 14 | The VHA PACS shall provide a pre-read QC worklist for cases sent to NTP. The cases shall be automatically placed in a pending QC status with a distinct worklist for NTP PACS Assistants (Support). Support shall utilize this worklist to review unread cases for completeness and determine if relevant priors have been sent. The QC worklist shall include functionality such that cases that are opened by Support shall be “claimed” by the specific Support staff reviewing the case and once they mark the case ready to read, it shall be released for interpretation. |
| 15 | Upon receipt of a Foundations STAT Portal web request, the system shall automatically upgrade the priority of the case within PACS to the same status regardless of the HL7 ORM priority value, or subsequent order update message, i.e. upgraded priority will remain fixed for the life of a study unless manually changed by a PACS Administrator. |
| 16 | The pre-read QC worklist shall display relevant HL7 exam information along with image thumbnails for each series transmitted. The worklist shall display the patient history/exam timeline, show available reports on VHA PACS, available images/studies on VHA PACS and shall provide an integrated tool to query various PACS in VA where the patient has images. |
| 17 | Upon receipt of a study to be interpreted, the VHA PACS shall automatically issue a c-find to each PACS instance where there is an order or report on file, using the native patient identifier(s) within the source PACS. The c-find response shall be normalized to provide a consistent accession number and patient ID format across all sites and shall be utilized to update the pre-QC worklist with the image availability status in VHA PACS across all instances where images for that patient reside (online or query-able). |
| 18 | Within the pre-read QC worklist for Support, it shall take no more than 4 mouse clicks total to open a case, retrieve a relevant prior, and mark ready to dictate: click 1 – open case from Support worklist, click 2 – select patient history tab or window and review list of priors that are on VHA PACS or have been identified via automated c-find to PACS where the patient has previous imaging, click 3 – retrieve relevant prior(s), and click 4 - mark ready to dictate. Patients with multiple exams shall be reviewed and marked ready to dictate as a group. |
| 19 | VHA PACS shall incorporate a post-assignment problem list to track cases that the Radiologists identify which need to be addressed by Support prior to sign off (Support Assist). Worklist shall function similar to the pre-read QC list where Support will claim the case and will address the issue until resolved. The post-assignment problem list shall also incorporate workflow for critical callbacks where the Radiologist is notifying Support that a critical callback is required. |
| 20 | Query and Retrieve function (Q/R) shall be available via GUI tool embedded within the Support QC workspace and shall also be available within the VHA PACS viewer. |
| 21 | The system shall immediately notify the Radiologist if a local report for a study they are viewing has been received. This can occur when a site disregards the stub message or initiates dictation before the NTP stub report is filed. The system shall also immediately notify the Radiologist if additional images are received on a case they are currently dictating. |
| 22 | The VHA PACS application shall correctly utilize the appropriate patient ID parameters when issuing a query to a source PACS to successfully execute the Q/R. For example, a patient in Spokane has a STAT x-ray and the site is using EDIPI as their primary identifier. That same patient has studies and reports in Bay Pines and within their PACS, the patient is identified via SSN. The VHA PACS shall be configured to utilize the native patient identifier within the target PACS, e.g. query to Spokane's PACS will use EDIPI while a query to Bay Pines' PACS will use SSN. |
| 23 | The system shall include a closed-loop support request tool between Support and the Radiologists to facilitate assistance requests and critical results. The support tool shall provide a mechanism for Support to “claim” a request, so multiple individuals do not work on the same problem and the requestor knows who has the assignment. |
| 24 | All artifacts associated with a study (order, results, images) shall be managed as a single entity, associated with the accession number. |
| ARCHITECTURE AND SECURITY | |
| 25 | System shall be designed and deployed in accordance with Medical Device Protection Program (MDPP) guidelines with Medical Device Isolation Architecture (MDIA) equivalent isolation firewalls and network security groups (NSGs). |
| 26 | For all contractor deployed components, all unused services shall be disabled. The systems shall be hardened to the greatest extent possible without impacting clinical performance or utility. |
| 27 | All DICOM and HL7 traffic shall utilize resilient links that shall auto-restart with message/data failure/rejection/time-out and the system shall include a notification mechanism to the contractor and VA support when failure is detected. |
| 28 | System shall incorporate a GUI tool (“dashboard”) for system administrators that at a minimum provides notification and visibility into all transmission and link failures. |
| 29 | System shall be deployed with Federal Information Processing Standards (FIPS) 140-2 (or successor) compliant encryption of sensitive data at rest. |
| 30 | HL7 interfaces shall support TLS 1.2 or its successor for connection to VHA provided HL7 broker. The system shall support HL7 ADT, ORM and ORU messages from all VA EMRs. |
| 31 | System shall be designed to optimally utilize bandwidth across the Wide Area Network (WAN) and to/from the cloud-based components. |
| 32 | All cloud-based components shall be hosted in VA Enterprise Cloud (VAEC). |
| 33 | System shall provide a mechanism for downtime situations (i.e. HL7 from EMR is unavailable and acquired studies do not have an associated EMR order) so that studies can be read with temporary orders and are later associated with the EMR order when it becomes available. In downtime scenarios, VHA PACS will generate temporary orders that will be sent to the voice recognition system. |
| 34 | At a minimum, the VHA PACS shall log transactions in an audit trail at the following time points: user logon/logoff, receipt of images, each instance of a study being opened and who viewed and closed that study, on which workstation it was viewed (including if it was opened from the EMR), start of reporting, signature of report, successful upload of report, deletion of study and/or report, and any change to demographic or study information. Logs shall be maintained while the study is on the system. If a study is deleted and subsequently repulled, the original audit trail shall be reinstated. |
| 35 | The audit trail shall be kept for no less than three years and all messages shall be synced with an internal VA time server. |
| 36 | Under administrative privileges, the system shall be able to support deletion of patient studies and images with an audit trail for all actions. |
| 37 | Transmission of any data outside of the VA network for vendor support or QC shall be via a VA approved VPN solution and is allowed only with FIPS 140-3 or successor compliant encryption. Sensitive patient information shall not be stored outside of VA organizational control for purposes other than for short term troubleshooting purposes. After the requirement for the data has been satisfied, the data shall be securely erased. |
| 38 | Workstations and servers shall run VA approved anti-virus software and accept automated patching. |
| 39 | Non-diagnostic workstations for Tech and PACS Admin access shall utilize the standard VA baseline PC image and shall operate with the full suite of VA security controls. All applications, web-apps and associated components required for non-diagnostic support, workflow, management, administration, and operation shall be required to be fully functional on a VA baseline image PC. |
| 40 | Web-based applications for diagnostic and non-diagnostic workstations shall be fully functional with VA baseline browser and accept the VA browser security settings. |
| 41 | System shall operate without external Internet access per VA Medical Device Protection Program guidelines (exclusive of VPN connectivity). |
| 42 | Workstation application upgrades (including vendor provided third party applications) shall not require administrative or elevated privileges to install. |
| 43 | Images shall not be permanently stored in non-volatile memory or hard disk on the reading workstations. |
| SYSTEM ADMINISTRATION | |
| 44 | Erroneous, malformed, or non-conformant DICOM images or HL7 messages shall be automatically moved to an offline queue for resolution with a Graphical User Interface (GUI)-based notification/resolution tool. These messages shall not cause queues to back up or loop while other transactions await processing. |
| 45 | The system shall incorporate monitoring tools to track performance, storage usage, hardware health, system capacity, and uptime, and display critical parameters in real time. These monitoring tools shall be made available to VA PACS administrators. |
| 46 | The system shall provide a means for notifying both the VA PACS administrators and the contractor in the event of a failure. |
| 47 | System shall have a web-based administrative tool that enables PACS Administrators and Support to reconcile/correct studies sent with improper demographic or case number information. |
| 48 | When images are identified as belonging to the same study and are sent from a site to the VHA PACS, the system shall group them together for storage and display purposes. |
| 49 | System shall provide a web-based administrative tool to split studies with duplicate Unique Identifiers (UIDs) and to split “combo studies” (head/chest CT, PET/CT) and assign a unique Study Instance UID (SIUID) to targeted images. It shall support aggregation of images into appropriate studies even if all images are not sent in the same association and it shall provide an admin tool to merge studies with distinct Study Instance UIDs. Studies with the same demographic information and same accession number, but different SIUIDs will be merged and handled as a single study. |
| 50 | The Contractor shall support all current DICOM SOP classes and provide a DICOM conformance statement to VHA listing all supported classes. |
| 52 | DICOM servers shall be a promiscuous SSCP without a license restriction on the number of Application Entity (AE) Titles. This includes all modalities, including AI, third-party analysis tools and subspecialty workstations interacting with the enterprise archive, there will be no licensing limitations restricting the number of connections and users. |
| 53 | VHA PACS shall support de-identification of reports and images and then export of those de-identified reports and images via DICOM. |
| 54 | VHA PACS shall support the import/ingest of scanned documents into both a DICOM Secondary Capture or DICOM Encapsulated PDF format. |
| INTEGRATION – PACS, HL7, EMR, MPI | |
| 55 | System shall support multiple identifiers for each patient via internal Master Patient Index (MPI) functionality internal to the system. DICOM images, DICOM configurations for store, query/retrieve, and modality worklist, and HL7 messages shall incorporate MPI data to ensure that image and report interfaces uniquely identify patients across EMRs and PACS instances throughout VHA. |
| 56 | System shall normalize all VistA generated Radiology accession numbers to the following format: ###-MMDDYY-123 where ### is the 3-digit site code for the originating VistA instance. Accession numbers within the images, reports and orders shall all be normalized to this consistent format. |
| 57 | System shall support individual VistA upgrades from HL7 2.3 to 2.4 and normalize the accession number, regardless of whether the 3-digit site code arrives prepended or not. |
| 58 | System shall normalize all studies and reports that utilize SSN as the primary identifier to the dashed format 000-00-0000. |
| 59 | For VistA sites, the VHA PACS shall support inbound ORMs and ORUs. For OH FEHR sites, the PACS shall support inbound ORM and ORU messages, as well as A08 and A34 ADT messages. |
| 60 | For sites that utilize OH FEHR as their EMR, the system shall be able to uniquely identify the patient via both the EDIPI and SSN. That patient shall appear as a single instance within the VHA PACS. |
| 61 | Contractor shall provide a fully operational test instance of the VHA PACS with all components. This shall be used for OH FEHR interface testing, application upgrade testing and potentially as a backup in case of either catastrophic failure and/or serious cybersecurity events. The system shall be capable of simulating at least 10% load of current production. |
| PACS VIEWER | |
| 62 | The referring physician viewer shall be a zero-footprint web application compatible with VA baseline browser. |
| 63 | The system shall be designed to accommodate 5 different categories/priorities: CRIT, STAT, Inpatient, ASAP, and Routine, with distinct turn-around times (TATs) for each level. The worklist shall display the time remaining before expiration of TAT for each unread exam. |
| 64 | The PACS diagnostic viewer shall fully launch and be ready for review/dictation within 3 seconds after study selection from the worklist or activation of the Next Study function. This shall include full fidelity display of current exam and 1 prior exam across all modalities based on 2x3 hanging protocol (HP) for cross sectional exams and 1x HP for DX exams. Performance target shall be met for users working within a VA site and home users working via VPN at 10 Mb/s minimum throughput. For cardiology imaging workflows, echo cine loops and interventional image sequences shall load within 2 seconds over enterprise WAN conditions, and synchronized waveform and imaging playback shall occur without perceptible latency. |
| 65 | Workstation PACS diagnostic client shall have system level and user-defined hanging protocols based as a minimum on modality, series description, view, and body part, with ability to quickly re-hang studies to a different layout as desired. For axial modalities, series in the same plane shall provide the user the option to link and scroll the series in synchronization, even if the distance between slices differs or if the slices are of different thickness. Diameters shall be measured in metric dimensions for all modalities that have the pixel size available in the header, and it shall be possible to perform calibration for modalities that lack the pixel size. |
| 66 | PACS and third party integrated viewers shall support on the fly 3D reformatting including Maximum Intensity Projection (MIP) and Multiplanar Reformatting (MPR). |
| 67 | System shall have a scout and 3D localizer function. Via the mouse, users shall be able to drag the scout line to the desired location and the display shall move to that slice. Reference lines shall display and scroll in all planes. |
| 68 | PACS Viewer shall provide support for teaching cases with deidentification of patient information. |
| 69 | PACS Viewer shall support automated auto-linking/registration of multi-slice images across series among current and prior exams and shall include a semi-automated spine labeling tool. |
| 70 | The PACS Viewer shall run on VA-provided hardware with Windows 10 LTSC, Windows 10 Enterprise, Windows 11, or Windows 11 LTSC operating systems. Workstations shall support VA approved anti-virus software (currently Windows Defender but may change with subsequent VA-wide AV award). AV shall be deployed with contractor provided file or folder exclusions. Diagnostic workstations shall permit automated Windows patching. |
| 71 | End user applications shall be made compatible with any new Windows major versions within 24 months of its commercial release. |
| 72 | VHA PACS application and associated viewer shall be a cloud-native design with dynamic streaming as a fundamental design feature. The VHA PACS application shall be fast, intuitive, stable, easy to use, and designed to optimize productivity and quality and reduce repetitive motion injuries. |
| 73 | Diagnostic viewer shall be optimized for WAN use with full fidelity streaming with a default of JPEG 2000 lossless compression. Image streaming shall be through encrypted traffic, ideally utilizing a fixed TCP port greater than 1023 if possible (use of higher ports decreases system vulnerability and provides an opportunity for more effective use of QoS). |
| 74 | Diagnostic viewer shall be designed as a cloud-native WAN-enabled streaming application with a minimum required bandwidth no greater than 10 Mb/s with WAN/VPN latency of 80 ms or less. WAN optimization is also required for DICOM traffic. Optimal WAN performance for all components of the PACS will be critical for the success of the overall project. |
| 75 | Data cached/stored on the workstation shall be deleted from the system at the close of the study or application. |
| 76 | System shall include a real-time productivity tracking tool visible for each respective Radiologist or Cardiologist within their PACS worklist. The tool shall be configurable to display daily wRVU. |
| 77 | Viewer shall include an integrated collaboration tool for communication within the VHA PACS between all user roles to include support staff with the ability to send embedded study links in the messages. Collaboration tool shall have the ability to broadcast messages to online users with individual and group responses and shall incorporate logging as well. Collaboration tool shall open in separate window above other windows so that notifications are not missed. |
| 78 | The system shall provide the ability for Reading Physicians to jointly confer on a study in real time while they view it. |
| 79 | The system shall provide visual cues on the worklist that indicate when a study is approaching expiration of the assigned turn-around-time within the 5 priorities (CRIT, STAT, Inpatient, ASAP, and Routine) and indicate when it is overdue. |
| 80 | The Reading Physicians shall be notified if another user is viewing the same exam on another workstation and shall be prevented from creating a duplicate report. |
| 81 | Worklist shall allow manual reassignment of studies to another Reading Physician and this shall be a logged event. |
| 82 | Patient history and reason for study shall be mapped from the HL7 message and shall be available for review within the worklist. |
| 83 | For compressed images, compression ratio shall be displayed for each image. For images that have been lossy compressed in the past, the “compression” flag available in the header shall be indicated to the user. |
| 84 | System shall be able to support Values of Interest Look Up Table (VOI LUT) and be able to selectively apply all the LUTs sent with the study. |
| 85 | System shall be capable of creating and storing multiple presentation states and key images/series. Key images and images with annotations shall be automatically written back to the originating PACS once the report is finalized. |
| 86 | System shall be capable of accepting and displaying a site created study with multiple presentation states. |
| 87 | User annotations shall be stored and retrievable for future viewing. |
| 88 | System shall have viewer-based query/retrieve for Radiologists Cardiologists and Nuclear Medicine Physicians. Q/R shall be via 1 click on the prior report and will not require the user to input source or destination information. The system will know which site the report is associated with and the query(ies) will be directed to the associated PACS. |
| 89 | Text overlays shall be configurable as a system-wide setting based on modality. The system administrator and/or user shall be able to change the overlay based on any DICOM tag. |
| 90 | System shall support flexible image placement of any image, and any series on any monitor via drag and drop or simple mouse clicks. |
| 91 | The viewer shall include an integrated PET/CT fusion tool. |
| 92 | The viewer shall include the full suite of mammography viewing and hanging protocol tools for both traditional full field digital mammography and tomosynthesis studies and be approved for diagnostic interpretation of these exams. |
| 93 | The viewer shall implement all common combinations of pixel size, photometric interpretations, overlays, scaling, and negative/positive pixels in addition to the pixel pipeline instructions as directed by Presentation States as defined in the Consistent Presentation for Images (CPI) IHE. |
| VOICE RECOGNITION (VR) | |
| 94 | The VHA PACS shall have a seamless API integration with the VHA provided VR system (PowerScribe1 v2109) and shall launch the VR report in patient context. All workflow steps shall remain in sync between the VHA PACS and VR system so study status is consistent across both platforms. |
| 95 | As VR system updates or replacements occur, the VHA PACS shall update required integrations to ensure ongoing interoperability. |
| ARTIFICIAL INTELLIGENCE (Radiology) | |
| 96 | System shall integrate with a vendor provided artificial Intelligence (AI) platform that supports the following applications: Intracranial Hemorrhage (ICH), large vessel occlusion (LVO), breast density, breast nodule detection and integrate existing VHA Riverain system as well as Cardiology specific AI requirements located in the cardiogy section of this document. The AI platform is to be hosted in VA Enterprise Cloud (VAEC). Contractor may provide equivalent, native AI tools within the VHA PACS but all AI modules must have FDA 510k clearance. The System will also have provisions to host non-commercial, VHA developed AI models. |
| 97 | System shall automatically route candidate cases to the various AI algorithms based on configurable parameters using HL7 and DICOM values. All routing shall be optimized to reduce transfer and analysis timelines. In specific cases (e.g., FFRCT in cardiac CT software), the system should allow users to initiate transfer of studies for AI processing with a single click (rather than automatic transfer). |
| 98 | Positive AI findings shall trigger a change to a higher priority status. Negative findings shall not decrement the submitted priority level. |
| 99 | AI processing shall write back to the the radiology and cardiology enterprise imaging system a secondary capture series identifying the finding (positive, negative, unable to process) and will identify the specific slice that triggered the finding. System will also be capable of exporting AI SC results external systems. |
| WORKFLOW TOOLS – IMAGE QUALITY, CALLBACK, SUPPORT, PEER REVIEW & NTP SPECIFIC TOOLS | |
| 100 | System shall include an internal collaboration tool. User list shall default to online users within the logged-in user’s organization (NTP, VISN X or site Y) but shall permit cross org communication via org drop down selection. The online user list shall include the Radiologist's names, their subspecialties and be filterable by Org. |
| 101 | System shall provide PACS administrators with the ability to dynamically change DICOM Q/R targets as facilities change PACS contractors and/or servers, without a system downtime. |
| 102 | System shall include a GUI tool for DICOM export to any connected PACS. Tool shall permit PACS Administrators to configure and select destinations and shall provide status on transfer actions. |
| ASSIGNMENT ENGINE & WORKLIST | |
| 103 | The system shall include an assignment engine (AE) that is fully integrated with the radiology worklist and viewer. The AE shall be designed to minimize report turn-around time while maximizing subspecialty interpretations. |
| 104 | AE shall support no less than 12 distinct subspecialty designations. Radiologists will have multiple subspecialty designations. |
| 105 | AE shall utilize a combination of CPT codes, LOINC codes (for OH FEHR sites), study descriptions, and priorities to identify the subspecialty group(s) for each case to be interpreted. |
| 106 | AE shall assign a fixed number of CRIT/STAT and ASAP/Routine cases to each logged in Radiologist. The system shall also support assignment of a fixed wRVU amount to each active Radiologist. |
| 107 | System shall have a default setting of “Auto Next” to automatically open the next case on the Radiologist’s worklist along with an associated report template. |
| 108 | System shall incorporate a “Skip” function that shall allow a Radiologist and Cardiologist to move to the next case and temporarily bypass Auto Next. If Skip is invoked, it shall require a comment from the Radiologist and it shall be an auditable/logged event. |
| 109 | System shall incorporate a "Suspend" function that allows Radiologists and Cardiologists to cease receiving additional cases via the AE until they are "Unsuspended", i.e. for breaks or to respond to callbacks. |
| 110 | Once the VHA PACS application is closed, any remaining exams on a Radiologist's and Cardiologist's worklist will be put back into the assignment queue after a pre-determined number of minutes. |
| 111 | For patients with multiple unread exams of the same modality, the AE will assign all of them to the same Radiologist and Cardiologist, provided they are all within the Radiologist's subspecialty. |
| 112 | Future design capability shall allow NTP and VISNs shall operate on unique instances of the AE so that NTP workflow shall not dictate subspecialty assignment for other VISNs who use the VHA PACS. In other words, each Org, (NTP, VISN1, VISN2, site X) shall have their own worklist and AE setup and an administrative tool to manage AE configuration. |
| 113 | AE shall continually update system status in the background and within 1 second of report signoff, it shall have the next available case assigned to any Radiologist and Cardiologist. |
| 114 | AE shall be configurable by PACS Administrators via GUI to change assignment parameters, subspecialty groups and subspecialty mapping. |
| 115 | Multipart exams such as CT chest plus abdomen/pelvis shall be managed as separate exams if sent to the PACS with distinct image sets and shall be evaluated by the AE accordingly. |
| 116 | AE shall assign the highest priority studies in the order received and will sequentially work through lower priority studies based on their SLAs, e.g., a routine priority case with an expired SLA should not be assigned before a study of a higher priority. |
| ADDITIONAL CAPABILITIES | |
| 117 | The system shall provide integrated American College of Radiology (ACR) compliant peer review and peer learning functionality as well as focused peer review capability. The scoring criteria that is used for each type of review: OPPE, peer learning, focused reviews, shall be set at the Org level. |
| 118 | System shall be designed so that in the future, radiology and cardiology groups can operate as a distinct organizations at the VISN, Health Service Area (HSA), facility or resource hub within the overall VHA PACS system. Security roles shall be limited to the specific organizations that the user is assigned to. |
| 119 | System and application administrative rights shall be configurable for least privileges based on the Org, i.e. a local PACS Admin shall not have access to administrative functions for another VISN. NTP will have system level privileges. |
| 120 | Application authentication shall be via single sign-on and users shall be permitted access to multiple Orgs as required. For example, a VA Radiologist working at a site that utilizes VHA PACS, but also works as a Fee Basis Radiologist for NTP, shall be presented with a drop-down to select the Org they will log into, and their Org-specific configuration shall be loaded. |
| 121 | The Vendor shall migrate all studies from the legacy radiology and cardiology PACS systems located in the 18 legacy VISN PACS archives to the new Radiology and Cardiology Enterprise Imaging system. Three years or more of historical images is expected to be migrated prior to legacy system transition. Volume is estimated to be 20 petabytes total. (Approximately 85% radiology, 15% Cardiology). |
| 122 | The system shall provide a full suite of vendor agnostic nuclear medicine tools that enable the post processing and reading of Planar Imaging, SPECT, PET, and Hybrid Imaging such as PET/CT, PET/MRI and SPECT/CT. Additional cardiac imaging requirements are listed in the cardiology section of this document |
| Cardiology Specific Technical Requirements | |
| 123 | The primary and preferred deployment architecture for all third-party advanced imaging and post-processing software (e.g., 3D/Advanced Visualization, Cardiac quantification) shall be installed directly onto standard VHA Government Furnished Equipment (GFE) as a zero-footprint web viewer, Thin Client, Launcher Application or VHA-certified thick client, eliminating the requirement for separate, dedicated diagnostic workstations whenever possible. If VHA preferred technology is not available at the time of the award, the vendor shall provide the technology as soon as it is commercially available. |
| For all cardiology imaging modalities, zero-footpring diagnostic display and structured reporting client is preferred. For echocardiography imaging, it is essential that the functionality be available via Citrix Gateway or GFE and easily deployable via VHA software center without administrator privilege/rights; therefore zero-footprint client or lightweight streaming client is required. | |
| All third-party systems, whether deployed on standard GFE or dedicated diagnostic workstations, must natively integrate with VHA Enterprise Single Sign-On (SSO) and Identity and Access Management (IAM) protocols (e.g., SAML 2.0, OAuth, OIDC) to support mandated two-factor PIV authentication. | |
| The system must not rely solely on proprietary hardware-level smartcard readers that force session termination upon card removal if it disrupts the physician workflow. The system must have functionality with PIV exemption (e.g., is able to recognize temporary PIV exemption credentials) | |
| In scenarios where a physician must operate a primary GFE (for EHR access) alongside a dedicated diagnostic workstation, the vendor’s authentication architecture must support VHA-approved federated or delegated authentication workflows (e.g., session persistence, derived credentials, or proximity-based SSO). This ensures the user can maintain secure, concurrent active sessions across both devices without being forced to physically swap the PIV card back and forth. | |
| If the vendor’s solution strictly requires deployment on dedicated workstations placed within isolated Medical Device Virtual Local Area Networks (VLANs), the vendor must engineer and document a VHA OIT/Cybersecurity-approved boundary traversal architecture. |
This network architecture must guarantee that interpreting physicians have unencumbered, concurrent access to standard VHA domain applications; specifically the Federal Electronic Health Record (FEHR/CPRS), enterprise imaging archives, and secure communication tools, directly from the dedicated diagnostic workstation.
Solutions that isolate the physician on a dedicated workstation without seamless, same-screen access to the patient's longitudinal EHR data for clinical context and report generation are unacceptable.
| Viewer designed with human factors focus to optimize viewing efficiency and minimize fatigue and repetitive motion injuries |
| System must support cross-site collaboration, reading, and reporting in both VistA and Oracle Health environments. |
| Enterprise-based VR profiles and structured reporting allowing users to work at alternate workstations/reading centers with minimal or no reconfiguration. |
| Migration of all studies and reports currently in local/VISN cardiology PACS. Support for both EDIPI and SSN for patient identity, with ability to normalize SSN to EDIPI during migration. |
| DICOM Modality Worklist provider for both order- and consult-based exams for cardiology procedures using imaging (including cath lab, EP lab, and structural heart workflows). |
| Support for current VA order and encounter-based workflows in the current CPRS/Vista environment, as well as to-be-state Oracle Health FEHR. |
| The system shall interface with the enterprise integration engine (e.g., COMPASS router) to transmit finalized, structured imaging reports directly to the FEHR via standard HL7 messaging (e.g., HL7 v2.x ORU). |
| Reports must be transmitted and rendered within the EHR as native, fully readable text documents. The system shall not rely on encapsulated, base64-encoded PDFs or external image hyperlinks as the primary or sole method of report delivery to the EHR. In addition to the text document required above, a PDF-based version of the report must also be sent to image archive. |
| The system’s outbound messaging must parse the structured report into discrete data elements (utilizing discrete HL7 OBX segments or HL7 FHIR resources). |
This discrete data formatting must ensure that specific, individual sections of the report, most notably the "Impression," "Interpretation," "Measurements," and "Conclusions" should be independently extracted, queried, and imported into other clinical documentation (e.g., provider progress notes, discharge summaries) in the exact same manner as discrete laboratory values or EKG results.
| Master Patient Index (MPI) support for VA’s transition from VistA to Oracle Health and SSN to EDIPI, functioning with both EMRs and using appropriate identifiers per system so each patient appears as a single instance in the enterprise imaging archive. System shall support archival, diagnostic display, and export of raw hemodynamic and electrophysiology waveform data (pressure tracings, cardiac output, electrograms) without loss of compression or degradation. |
| Advanced AI support including third-party integrations across all listed imaging specialties, not limited to image analysis, and extending to workflow, routing, prioritization, results tracking, notifications, patient safety, demographics verification, system administration, and research. |
| Natural language report search tool available to all end users. |
| Seamless API integration into VHA voice recognition. |
| Viewer must support export of deidentified reports and images, including support for de-identified export of structured cardiology datasets for registry reporting and outcomes research in accordance with VA data governance policies. |
| System must support electronic transfer and reconciliation of electronic images and other records between VA and outside providers/institutions via the Image Exchange currently in development. |
| Functionality to support automated assignment of case reviews and tracking of results for OPPE. |
| Support for current IHE VNA image and document management standards. System shall support DICOMWeb (QIDO-RS, WADO-RS, STOW-RS) and FHIR ImagingStudy and DiagnosticReport resources to ensure long-term interoperability and prevent vendor lock-in. |
| Diagnostic viewer typically launched with pass-through authentication from the Operating System but must also support stand-alone launch using SSO, WIA, or LDAP via PIV/CAC. |
| Enterprise viewer typically launched from the EMR with pass-through authentication but must also support stand-alone launch using SSO, WIA, or LDAP via PIV/CAC. |
| Third party imaging software systems have to either be viewable on government furnished equipment (GFE), or not require single-sign-on if on separate, dedicated workstations. |
| Business intelligence reporting system including standard enterprise reports and user-customizable Boolean search and reporting for all components. Third-party structured cardiac imaging reports shall be stored as structured, text‑searchable data within the EHR and shall not be PDF-only reports. |
| Reporting should include longitudinal cardiovascular analytics and registry-ready data extraction capabilities, with integration to invasive cardiovascular reporting system (CART) where applicable and when interface becomes available. |
| Reporting shall include longitudinal cardiovascular analytics and registry ready data extraction capabilities. In alignment with the 2025 ASE guidelines emphasizing standardized reporting for machine learning and AI workflows, the system shall also provide AI-ready data formatting and programmatic access. This includes support for an API-based data extraction mechanism and export of structured imaging data, including measurements, metadata, and derived parameters, in standardized machinereadable formats such as JSON or equivalent. These capabilities shall enable VHA researchers to directly utilize structured imaging and hemodynamic datasets for training machine learning models, Large Language Models (LLMs), and other advanced analytics tools, while maintaining consistency with VA data governance and security requirements. |
| Full security auditing and automated archiving of audit trails with notification capabilities. |
| Access control conformant with VA’s Least Privileges policy; roles and worklists must support this and separate cardiology worklists by site, VISN, and NTP. |
| System must support Section 508 accessibility or justify an exemption. |
| Vendor must commit to continuous product development and enhancement to keep the system on the latest commercial version, including new client functionality as needed by VA. Vendor shall provide a documented product roadmap and commit to maintaining regulatory compliance (FDA clearance, cybersecurity standards) for cardiology modules throughout the contract lifecycle. |
| System supports future integration of new technologies as they evolve and become standard of care. |
Echocardiography-specific software designed for viewing and postprocessing echocardiography images and building a structured report for the electronic medical record, with following specifications:
| System shall support ingestion and structured mapping of advanced echocardiographic quantitative metrics—including Strain/GLS, 3D volumetric measurements, and myocardial work indices—from all VA supported ultrasound platforms into the structured reporting database, using vendor-neutral DICOM SR or equivalent standardized data formats and using EHR-integrated worklists for patient identification. |
| Archiving and image/report distribution to the VHA enterprise |
| Rapid, on-demand access to images across the VHA enterprise |
| To ensure the system's structured reporting logic, reference ranges, and auto-generated conclusions can be dynamically updated by administrators to reflect new societal severity gradings without requiring a full software upgrade from the vendor. |
| Ability to import images acquired from point-of-care ultrasound systems in a vendor-neutral manner, using EHRM-integrated worklists for patient identification, for image viewing and reporting. |
| Ability to handle high frame-rate large echo datasets |
| Seamlessly integrate third-party software to allow image transfer to central Radiology/Cardiology PACS system while retaining ability for multi-frame cine display |
| Functionality for automated population of templated reports using DICOM SR and AI analysis. |
| Supports standard echo analysis tools, including LV and RV measurements and function analysis, Simpson biplane calculation, Doppler measurement tools, diastolic function analysis tools, valve function tools, strain imaging tools, 3D imaging tools |
| Ability to perform automated LV, RV, RA, LA quantification using AI assisted border detection with manual override capability |
| Full 3D echocardiography analysis tools including 3D LV, RV volumetric quantification |
| Ability to prioritize STAT or urgent (such as inpatient) studies within the cardiology reading queue |
| Ability to bookmark key frames or clips for report reference |
| Ability to export selected cine clips for presentations, research or educational use, as well to anonymize DICOM studies |
| Ability to easily share and view echo studies across the VA systems, preferably using an enterprise system. |
| Ability to add/edit annotations by technologists or cardiologists. |
| Allows post-processing functions including changing cine display speed, contrast/brightness manipulation, measurement tools, strain analysis support |
| Ability to simultaneously view multiple prior studies for longitudinal comparison with automatic trending of key parameters (ejection fraction, valve gradients, pulmonary pressures, RV function, myocardial perfusion metrics). |
| Ability to view and edit specific imaging types from third-party vendors (e.g., 3D ultrasound, strain imaging) across multiple dimensions, with visibility into which third party produced them. The system shall support vendor-neutral strain analysis (GLS) and 3D echo rendering independent of acquisition platform, without proprietary lock-in. |
| Ability to support on-the-fly 3D and other advanced visualization and analysis capabilities. |
| System includes structured echo reporting capability with embedded templates that can be edited by the end-user facility. |
| The structured report will include ASE (American Society of Echocardiography) guidelines-aligned reporting fields. |
| The structured report will automatically populate the measurements obtained and verified by the echocardiography sonographer. |
| The system allows end-user (reading physician) to determine which measurements are used in system-calculated values, create user- defined rules to replace system-calculated values, and override values selected by the system and set a different value. |
| Ability to create and select structured templated forms for specific research projects. |
| Ability to edit conclusion reports within the system and update amended studies. |
| System shall include correct variable mapping for data points between echo machine software and PACS. |
| System shall implement intuitive, easy mouse and keyboard navigation that is not confusing and supports appropriate selections based on the current task |
| System must include a worklist/assignment engine that presents Cardiologists with studies they are credentialed to read and supports configurable assignment and workload balancing logic. The cardiology assignment engine shall account for credentialing in invasive vs. Non-invasive procedures and support sub-specialty distinctions including interventional, structural, electrophysiology, advanced imaging, and nuclear cardiology. |
| Allows future integration of artificial intelligence (AI) tools as they become standard of care (including automatic chamber size and function measurements). |
| Allows optional addition of specialty modules in the future as needed. |
| Structured report connects to the VHA/DOD FEHR, allowing the end-user (reading physician) to electronically sign the report, using their PIV card or signature code. |
| Redundant archiving of final reports in image series, PDF copies to the EHR, and test versions to TIU notes in CPRS. |
| Cardiac Catheterization and Electrophysiology Laboratory Generated Image Requirements: |
| Full-featured vendor-neutral modular cardiology diagnostic display and review system for invasive cardiac catheterization, cardiac interventional and cardiac electrophysiology procedures to allow integration of third-party systems, such as IVUS, OCT, coronary physiology (FFR/IFR) or other similar future systems, with synchronized hemodynamic waveform display, and electrophysiology mapping images saved as DICOM images, with preserved signal fidelity. |
| The viewer should be capable of integrating with third-party software for image interpretation as it becomes available via standard interfaces. |
| Obtained cine and still images will be transferred in vendor-agnostic manner from third-party systems to the combined Radiology/Cardiology PACS, using EHRM-connected patient worklist for patient identification. |
| The PACS viewer will allow clinicians access to a zero-footprint web application to view cardiovascular angiographic data, as well as ancillary DICOM imaging data acquired during these procedures (ultrasound / intravascular ultrasound / optical coherence tomography). The PACS viewer will be accessible enterprise wide and thus any clinician at any facility will be able to access these clinical data as needed, regardless where the data was initially generated within the healthcare system. As the interpretation and reporting of these studies are performed outside of the PACS system (eg, CART program), these data will not be included in workflow lists for interpretation nor be included in the acquisition traffic controller worklist for case review. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .