Novarad NovaPACS and Visage 7 are not interchangeable answers to the same procurement question. The available official documents describe different architectural emphases, different customer-facing claims, and different types of evidence. NovaPACS EI is presented as an enterprise imaging system that scales from large hospitals to critical access hospitals and includes radiology, cardiology, pathology, mammography, and encounter-based imaging workflows [2][3]. Visage 7 is documented primarily through interface specifications and platform pages that emphasize a server-side, cloud-native architecture, standards-based interoperability, and a smart-client viewer on Windows or macOS [9][10][11][12]. A buyer comparing the two should separate what is explicitly documented from what the public materials cannot settle, including performance, pricing, clinical outcomes, and integration success in a specific environment.

Documented DICOM and HL7 Scope

The Novarad DICOM Conformance Statement, dated June 2026 and applying to NovaPACS Version 9.x, defines the system as a self-contained networked computer system for routing and archiving diagnostic medical images [1]. It lists support for storage of X-ray, digital mammography, intra-oral X-ray, multi-frame grayscale secondary capture, and 12-lead and ambulatory ECG waveform objects [1]. The document also lists modality worklist, storage commitment, and patient root, study root, and patient/study only query/retrieve functions, while noting that relational queries are not supported as either an SCU or SCP [1]. These entries describe protocol-level capabilities, not clinical performance or workflow quality.

Visage 7's public documentation takes a different form. The HL7 Interface Specification, version V23.00 from June 2026, describes patient information reconciliation, quality assurance for incoming DICOM images, and prefetching of prior studies from a remote DICOM archive based on HL7 order or appointment messages [9]. The IHE Integration Statement, dated June 2026 and covering Visage 7 version 7.1.20, lists implemented actors for profiles including Access to Radiology Information, Scheduled Workflow, Patient Information Reconciliation, and Cross-Enterprise Clinical Documents Share [10]. Both vendors caution that conformance statements alone do not guarantee interoperability and require validation with the specific systems involved [1][10].

Viewer Deployment and Workflow Claims

NovaPACS documentation describes a Diagnostic Viewer and a Web Viewer. The Web Viewer is identified as a thin-client version that downloads Image Viewer files temporarily and is accessed through a secure server, with users required to download and use Microsoft's .NET Framework 4 Client Profile [5][7]. The Diagnostic Viewer manual lists MPR and MIP integration, annotation options, and dictation provider options including Basic, File, Dragon, CMDLine, Fluency Direct, and PowerScribe360 [5][7]. The manual also states that mobile devices are not intended to replace a full workstation and should not be used for mammography or fMRI [5].

Visage 7's platform page describes a smart-client application native on Windows or macOS with zero client-side dependencies [12]. The cloud page describes a fully managed SaaS service with up to 60 parallel I/O streams to cloud object storage and end-to-end TLS encryption [11]. These are vendor claims about architecture and deployment, not independently verified performance results. The two products therefore present different documented viewer models: NovaPACS combines a diagnostic workstation with a web-deployed option, while Visage 7 emphasizes a single smart-client across operating systems and a cloud-native server-side architecture [5][7][11][12].

A Suggested Validation Workflow for a Mixed-Modality Hospital

A hospital evaluating both products could run a structured documentation review before any demo. First, map the required SOP classes from the Novarad DICOM Conformance Statement against the modalities in use, including mammography and ECG if applicable [1]. Second, request the equivalent Visage 7 DICOM conformance statement and compare the implemented IHE actors for Scheduled Workflow and Patient Information Reconciliation [10]. Third, ask each vendor to describe how prior studies are prefetched: Novarad's materials do not document HL7-based prefetching in the public documents, while Visage 7 explicitly describes it [9]. Fourth, request the actual service level agreement and disaster recovery terms from both vendors, since the public pages describe these differently [2][11]. This sequence is a suggestion for buyer due diligence, not a test result or a recommendation.

Service, Support, and Customer Segment Differences

Novarad's public pages make specific service claims. NovaPACS EI is described as evergreen, with upgrades included at no charge, disaster recovery always included, and support from a US-based, 24/7 team [2][3][8]. The pages also state that the system scales from large hospitals down to a critical access hospital [2][3]. These are vendor statements about included services and target settings, not evidence of service quality or contractual terms. A buyer should request the actual service level agreement and disaster recovery documentation rather than treating the marketing page as a binding commitment.

Visage Imaging's cloud page describes a fully managed service with a service level agreement between Visage and the customer organization, hosted with cloud hyperscalers in certified data centers, and annual SOC 2 Type II plus HIPAA audit certification [11]. The page also states that the largest and most sophisticated imaging organizations run on Visage 7 CloudPACS, but this is a vendor claim without a published customer list in the public documents [11]. The two vendors appear to address overlapping but not identical segments: Novarad explicitly names critical access hospitals, while Visage emphasizes scale, cloud infrastructure, and organizations of varying size and mission [2][11].

What the Public Documents Cannot Settle

Several decision-critical questions remain unanswered by the public documents. Neither vendor provides pricing, total cost of ownership, or implementation timelines in the retrieved documents. Neither public documentation includes independent test results for image loading speed, diagnostic accuracy, or user satisfaction. The Novarad materials do not document a comparable cloud-native architecture or SOC 2 certification, while the Visage materials do not document bundled modules for mammography, orthopedics, wound care, or emergency department workflows in the same way Novarad's pages do [2][6][11]. Absence from the retrieved documents is not proof that a capability does not exist.

A buyer should also distinguish between software capability and service delivery. Novarad's pages emphasize included disaster recovery, evergreen upgrades, and US-based support as part of the product positioning [2][3]. Visage's pages emphasize managed cloud service, certified data centers, and a service level agreement [11]. These are different commercial models, not directly comparable feature lists. A procurement team evaluating both should request a written statement of work, a DICOM and HL7 conformance review against the specific modalities and EMR in use, and a reference check with organizations of similar size and imaging volume.