Agfa Enterprise Imaging and Novarad NovaPACS are often evaluated together because both vendors use the phrase enterprise imaging, but the public documentation describes different system boundaries. Agfa presents a modular platform spanning PACS, VNA, universal viewing, orchestration, and AI packaging, with separate IHE and HL7 conformance statements for release 8.4.x. Novarad presents NovaPACS EI as a PACS system with enterprise imaging built in, scaling from large hospitals to critical access hospitals and adding encounter-based imaging across service lines. The comparison is therefore not only about feature checklists; it is about whether an organization needs a consolidated imaging platform across many departments and sites, or a PACS-centric solution that extends into enterprise capture and viewing. Public materials do not settle which approach performs better in a given environment.
Documented Workflow Scope Differs More Than Product Labels Suggest
Agfa describes its product as a single platform that unifies imaging across departments and aligns with clinician work. The vendor states that the platform can consolidate imaging systems, reduce infrastructure duplication, and scale across on-premises, hybrid, or cloud deployment [1][7]. Its product page lists components beyond a traditional PACS [7]. This indicates a broader purchasing unit: a buyer may select modules rather than one self-contained PACS. The vendor's product page lists XERO Universal Viewer, Vendor Neutral Archive, RUBEE AI, RUBEE Orchestrator, Business Intelligence, and Enterprise Imaging Scheduling as components beyond a traditional PACS [7].
Novarad uses a different starting point. NovaPACS EI is described as an advanced PACS imaging system with enterprise imaging built in, allowing radiology, cardiology, pathology, mammography, and encounter-based imaging throughout the hospital [10][11]. The vendor emphasizes scaling from large hospitals down to critical access hospitals and highlights always-included disaster recovery, evergreen software with upgrades at no charge, and a US-based 24/7 support team [10][11]. This framing suggests a packaged, service-inclusive product rather than a modular platform assembled from separate components.
Interoperability Claims Rest on Different Types of Evidence
Agfa publishes an IHE Integration Statement for Enterprise Imaging 8.4.x that names specific actors and profiles, including Patient Demographics Query, Cross-Enterprise Document Sharing, Radiology AIR, Integrated Reporting Applications, Web-based Image Access, and Imaging Object Change Management [2]. A separate HL7 Conformance Statement documents supported trigger events, segment processing, and query capabilities, with revision history tracking changes across 8.4.0 through 8.4.4 [4]. The statement also notes that Core Server might support trigger events not listed in the document if the message content can be converted to a supported trigger event, subject to analysis by AGFA Healthcare Professional Services [4]. This level of public documentation allows an integration team to verify actor support before procurement, though it remains vendor-authored material.
Novarad provides a DICOM Conformance Statement for NovaPACS 9.x, dated June 2026. It documents supported SOP classes, modality worklist functions, storage commitment, and query/retrieve models, and notes that relational queries are not supported as SCU or SCP [9]. The document also states that interactions between a Novarad viewer and server are proprietary for performance and functionality reasons [9]. Publicly available Novarad materials do not include an equivalent IHE or HL7 conformance statement for NovaPACS EI, so the depth of profile-based interoperability beyond DICOM remains difficult to compare from the public documents.
Shortlist Exercise: Testing the Two Enterprise Models
A facilities team considering both products could create a one-page internal scenario for a three-site regional system with an aging community radiology PACS and a cardiology department that captures echo and cath studies. The Agfa evaluation would ask how the platform would consolidate those systems into one VNA, which IHE actors would support external retrieval from the legacy archive, and whether the organization would operate the platform on-premises or contract AGFA-managed delivery [7][8][2]. The Novarad evaluation would ask whether NovaPACS EI should replace the community PACS and extend into cardiology and encounter-based imaging, which support and upgrade commitments apply, and how the proprietary viewer-server relationship affects archive portability [9][10][11]. This is a suggestion for evaluation design, not a test result or a vendor recommendation.
Deployment and Delivery Models Target Different Operational Assumptions
Agfa positions its platform around cloud-native architecture with containerized microservices, automated failover, and server-side CPU rendering to reduce GPU dependency [3][1][7]. The vendor states that the platform can run on-premises, in hybrid form, or in full cloud delivery, with cloud storage, cloud teleradiology in North America, and AGFA-managed SaaS options described as stages on a path to full Enterprise Imaging [7]. The vendor says buyers can choose on-premises, hybrid, or full cloud delivery [7]. In this model, adoption can begin with storage or VNA modernization and expand later, but responsibility for operating the platform depends on which delivery route is selected. The vendor describes modular entry points that start with cloud storage or a VNA and scale toward full Enterprise Imaging [7].
Novarad frames NovaPACS EI around bundled service characteristics rather than a multi-stage cloud adoption path. The vendor lists complete customization, intelligent routing, service level agreements, web-deployed viewer, worklist management, and single-click Nova 3D+ as highlighted features [10][11]. Support is described as best-in-class, US-based, and available 24/7, with disaster recovery always included and upgrades evergreen at no charge [10][11]. These statements emphasize operational predictability for smaller or resource-constrained facilities, but the sources do not provide a comparable cloud architecture statement or an IHE-based deployment framework.
Customer Settings and Procurement Questions Remain Distinct
Agfa materials repeatedly align with multi-site health systems, enterprise consolidation, and platform standardization. The vendor publishes testimonials from leaders at large organizations and cites recognition reported by KLAS in PACS, Universal Viewer, and VNA categories [1][8]. Novarad specifically names critical access hospitals alongside large facilities, suggesting its commercial emphasis includes smaller institutions seeking a single vendor for PACS, enterprise capture, support, and upgrades [10][11]. These are different buyer profiles: one may be running multiple legacy systems and seeking a vendor-neutral consolidation layer, while the other may be replacing a departmental PACS and extending it to enterprise imaging.
A practical procurement distinction concerns what is documented versus what must be verified during a demo. Agfa buyers can ask for conformance statements by release number and compare the supported DICOM, HL7, and IHE actors against current interfaces. Novarad buyers can examine the DICOM Conformance Statement and then request a clear list of supported HL7 message types, IHE profiles, and EHR integration paths, because those are not detailed in the retrieved pages. Neither set of public materials supports a claim that one vendor is more interoperable, secure, or clinically effective in a specific deployment.
What the Public Record Does Not Settle
The sources leave several questions unanswered. Agfa does not publish validated turnaround, diagnostic accuracy, or operational cost outcomes from a comparative study; its pages describe intended benefits such as faster access, fewer silos, and reduced infrastructure complexity [1][7]. Novarad likewise attributes patient outcomes and operational efficiencies to its Universal Viewer and storyboards but does not provide independent study data in the retrieved pages [10][11]. The vendor's pages state that the Universal Viewer optimizes case management for reducing readmissions, but the retrieved materials do not include a supporting study [11]. A buyer cannot determine from these documents whether either product reduces repeat imaging or improves reporting speed in any specific department.
The comparison also cannot resolve how each vendor handles multi-vendor archives in production. Agfa's VNA page states that the archive accepts imaging content from AGFA solutions as well as other third-party PACS and departmental systems [8]. Novarad's DICOM Conformance Statement states that the server receives DICOM objects from external systems for permanent storage [9]. Agfa states its VNA accepts content from third-party PACS and departmental systems and supports IHE-XDS, while Novarad states that its viewer-server interactions are proprietary but that the server receives DICOM objects from external systems for storage and retrieval [8][9]. Whether proprietary viewer behavior limits archive migration, historical data access, or third-party viewer options is an implementation question that public materials do not answer. The Novarad statement does not specify whether the proprietary viewer-server relationship affects migration or third-party viewer access [9]. Buyers should request a written interoperability test plan before contract signature.
Sources & references
- Enterprise Imaging - AGFA HealthCare · www.agfahealthcare.com
- AGFA HealthCare Enterprise Imaging 8.4.x · agfahealthcare.com
- Enabling Technologies - AGFA HealthCare · www.agfahealthcare.com
- Enterprise Imaging 8.4.x · www.agfahealthcare.com
- Interoperability - AGFA HealthCare · www.agfahealthcare.com
- Enterprise Imaging Platform - KLAS Award Imaging Empowerment - AGFA HealthCare · www.agfahealthcare.com
- Cloud & Delivery Options - AGFA HealthCare · www.agfahealthcare.com
- Vendor Neutral Archive (VNA) - AGFA HealthCare · www.agfahealthcare.com
- Novarad DICOM Conformance Statement · www.novarad.net
- PACS Imaging for Enterprise Healthcare - NovaPACS EI | Novarad · www.novarad.net
- PACS System with Enterprise Imaging - NovaPACS EI | Novarad · www.novarad.net
- PACS Imaging for Enterprise Healthcare - NovaPACS EI | Novarad · www.novarad.net