A medical PACS is not one product category but a regulated imaging device with documented acceptance, transfer, display, storage, and processing functions. The FDA definition cited in NIST SP 1800-24 describes PACS as a Class II device that "provides one or more capabilities relating to the acceptance, transfer, display, storage, and digital processing of medical images," and the same guidance treats the PACS ecosystem as an authoritative repository connected to clinical systems and medical devices [2][5]. For a professional evaluation, the useful starting point is therefore not a feature list but the primary documentation that states what a specific system is cleared to do, how its interfaces were validated, and which operational limits the manufacturer records. Vendor manuals from Konica Minolta and Philips, the VA's approved HL7 interface table, and NIST's finalized practice guide each answer a different part of that question. The following sections organize those documents around workflow distinctions, interface validation, security scope, and a concrete hypothetical evaluation.
What the Device Documentation States About Intended Use
The Konica Minolta Exa PACS|RIS manual describes the software as receiving digital images and data from CT, MR, ultrasound, radiographic, secondary capture, scanner, gateway, and other imaging sources. Images and data can be stored, communicated, processed, and displayed within the system or across distributed locations [8]. The manual adds a specific restriction: lossy compressed mammographic images are not intended for diagnostic review, mammographic images should be viewed only on an FDA-cleared monitor, and post-process DICOM "for presentation" images must be used for primary diagnosis [8]. These statements are device indications, not marketing claims, and they define the boundary of intended clinical use.
The Philips Vue PACS instructions for use describe an image management device intended to provide scalable local and remote access, with user profiles for radiologists, referring physicians, technologists, and others [6]. The document states that the Diagnostic Viewer includes native clinical applications for lesion management, CT perfusion, MR perfusion, and MR diffusion, and that the system integrates review, dictation, and reporting tools [6]. A warning in the same manual says unsupported software must not be installed because it could interfere with diagnosis or interpretation, cause loss or damage to patient data, or introduce computer viruses [6]. These are operational constraints that an evaluation team should treat as part of the product specification rather than as optional guidance.
Interface Validation Is a Separate Question from Product Quality
The VA publishes a table of commercial PACS products that have passed its internet-based HL7 validation test suite based on the Profiles for HL7 Messaging between VistA and Commercial PACS [1]. The table lists manufacturer, model, version, approval date, and notes. Examples include Agfa Impax 6.3.1 approved 26 November 2008, Carestream VuePACS 12.x approved 21 July 2017, GE Healthcare Centricity PACS 4.0 SP3 approved 1 August 2014, Philips IntelliSpace 4.x approved 29 November 2011, and Siemens syngo dynamics VA20 approved 28 December 2016 [1]. The VA states plainly that this list does not constitute product endorsement and that validation does not indicate how well the product will work operationally [1].
The notes column records functional differences that matter in a workflow review. Several products update patient location in real time, while Philips iSite 4.2 records patient location as it was at the time of the order [1]. Digisonics EC2-Software HL7 Manager 1.1.0 with DigiHL7 NMIS 1.0.0 has neither asserted support for, nor been validated for, report message processing and storage [1]. The VA also states that if a manufacturer revises any part of the PACS HL7 interface, the interface must be re-validated, and that upgrades to vendor equipment can affect interoperability [1]. An evaluation should therefore request the current validation status for the exact version under consideration, not rely on an older approval date.
Reading the VA Notes Column as a Workflow Check
The VA interface table's notes are the most operationally specific part of the document. Note 1 means patient location is updated real time; note 2 means patient location is recorded as it was at the time of the order; note 3 means the product has neither asserted support for, nor been validated for, report message processing and storage; note 6 means the product is required to use the VA MWL SCP [1]. A practical evaluation step is to map each note to a specific workflow question. For example, a facility that relies on report message storage should ask whether the candidate product carries note 3, as Digisonics EC2-Software HL7 Manager 1.1.0 with DigiHL7 NMIS 1.0.0 does [1]. A facility using Volpara Patient Hub Dicom Export Service should note the VA's clarification that the letter export service is not a modality sender and does not generate or transmit imaging data; it functions as an application-level service similar to scanning a letter into the PACS [1].
Security Scope in NIST SP 1800-24
NIST SP 1800-24, finalized in December 2020, addresses the PACS ecosystem rather than a single server. The project scope includes storage, retrieval, management, distribution, and presentation of medical images [2]. The guidance states that PACS may connect with clinical information systems and medical devices and engage with internal and affiliated health professionals, and that this complexity may expose opportunities for malicious actors to compromise confidentiality, integrity, and availability [2]. The NCCoE analyzed risk using the NIST Risk Management Framework and leveraged the NIST Cybersecurity Framework to identify safeguards [5].
The practice guide's control families include access control, configuration management, contingency planning, identification and authentication, risk assessment, system and communications protection, and system and information integrity [5]. Keywords in the publication cover DICOM, EHR, encryption, microsegmentation, multifactor authentication, privileged account management, and vendor neutral archive [5]. The collaborating vendors listed by NCCoE include Cisco, Clearwater, Digicert, Forescout, Hyland, Microsoft, Philips, Symantec, TDI Technologies, Tempered Networks, Tripwire, Virta Labs, and Zingbox [2]. This list identifies participants in a reference architecture, not a set of required products for any particular deployment.
A Hypothetical Evaluation Around Documented Decision Points
Consider a hypothetical radiology group comparing two documented configurations: a Philips Vue PACS 12.2.8.x deployment and a Konica Minolta Exa PACS|RIS 35.0.2 deployment. The evaluation would not ask which product is better in general. It would ask which documented capabilities match the group's workflow. The Philips manual describes a native reporting module for multi-media interactive reports, Vue Motion browser access to DICOM and non-DICOM images, and a patient portal called MyVue [6]. The Konica Minolta manual describes a suite of client tools including Exa Dictation, Exa Trans for transcription, Exa Scans for document scanning, Opal Tools for CD import and burning, and Mobile Rad [4].
The same hypothetical evaluation would then check interface validation. If the group needs VistA HL7 communication, the VA table shows Philips IntelliSpace 4.x approved 29 November 2011 and Philips IntelliSpace Cardiovascular ISCV 8.0 approved 12 December 2018, but the table does not list Vue PACS 12.2.8.x or Exa PACS|RIS 35.0.2 under those exact version numbers [1]. That absence is not evidence of failure; it means the current validation status is unknown from the supplied document and must be confirmed with the VA or the vendor. The evaluation would also compare the mammography restrictions in the Konica Minolta manual against the display and reporting workflow in the Philips manual, since those restrictions are stated differently in the two documents [8][6].
Sources & references
- [PDF] VistA Imaging Approved PACS HL7 Interfaces April 2026 - VA.gov · www.va.gov
- Securing Picture Archiving and Communication System | NCCoE · www.nccoe.nist.gov
- A Comprehensive Guide to Selecting and (Potentially) Replacing PACS: Navigating the Decision-Making Processes | Journal of Imaging Informatics in Medicine | Springer Nature Link · link.springer.com
- Enter the help project title here · healthcare.konicaminolta.us
- SP 1800-24, Securing Picture Archiving and Communication System (PACS): Cybersecurity for the Healthcare Sector | CSRC · csrc.nist.gov
- 8G7607 Vue PACS 12.2.8. Desktop Diagnostic Workstation IFU Rev J_en-US · www.documents.philips.com
- Healthcare It Edison True Pacs | GE HealthCare (United States) · www.gehealthcare.com
- Enter the help project title here · healthcare.konicaminolta.us