Visage 7 is presented by Visage Imaging as an enterprise imaging platform for viewing and distributing medical images and reports. The vendor's technical documentation describes a server-side streaming architecture, DICOM and HL7 interfaces, and an Open Archive component. This profile reviews documented functions, workflow capabilities, and implementation boundaries without evaluating clinical outcomes or regulatory status beyond what the public documents state. [1][4][5][6]
Architecture and Client Access
Visage 7 uses a server-side architecture in which image data remains on the server and is streamed to client devices. The online help states that image data does not need to be sent to client computers, and users can access data from radiology workstations, office PCs, laptops, or other devices. The technical page describes Visage 7 as a smart-client application native on Windows or macOS with no client-side dependencies. [4][6]
The DICOM conformance statement describes a modular architecture for viewing and distributing medical images and reports within and outside a clinical area. It states that external systems can send images for temporary storage, retrieve information about images, and retrieve the images themselves. The document also lists prefetch, autorouting, export to CD/DVD, and print mechanisms. [5]
Interoperability and Standards
The HL7 Interface Specification describes communication between Visage 7 and other HL7 systems. Documented functions include patient information reconciliation, quality assurance of incoming DICOM images, and prefetching of prior studies from a remote DICOM archive upon receipt of order or appointment messages. The interface uses a unidirectional TCP/IP socket with configurable character encoding. [1]
The IHE Integration Statement lists implemented profiles and actors, including Access to Radiology Information, Scheduled Workflow, and Cross-Enterprise Clinical Documents Share. The statement notes that IHE does not guarantee interoperability by itself, and that test procedures should be defined to validate the desired level of connectivity. [2]
The DICOM conformance statement indicates support for DICOM 3.0 to allow sharing of medical information with other systems. It lists storage, query/retrieve, worklist, performed procedure step, storage commitment, and print functions. The document states that DICOM conformance does not by itself guarantee interoperability. [5]
HL7 Prefetching Workflow
The HL7 Interface Specification describes a prefetching workflow in which Visage 7 receives incoming HL7 messages, converts the data to update a prefetching queue in the Visage 7 database, and sends response messages to the sender. Prefetching can be triggered by appointment or order event messages. For prefetching, HL7 messages are not separately stored in the database. [1]
Open Archive and Data Management
Visage 7 Open Archive is described on the vendor's website as a high-performance, standards-based vendor neutral archive for radiology and non-radiology data. The page states that the archive supports tiered storage architectures and provides retrieval from nearline or coldline storage. It also describes support for traditional radiology workflows such as IHE Scheduled Workflow and Encounter-based Imaging Workflow. [7]
The technical page describes Visage 7 Open Archive as a standards-based, vendor neutral archive and a core component of Visage 7. The Open Archive page states that the archive is designed with a cacheless architecture to eliminate long retrieval times for ad-hoc data access. It also describes support for read-only storage configurations for ransomware protection. [4][7]
Cloud Deployment
The cloud page describes Visage 7 CloudPACS as a fully managed Software-as-a-Service product. It states that cloud infrastructure can be provisioned in a few clicks, and that Visage 7 uses up to 60 parallel I/O streams to cloud object storage. The page also describes S3 storage configured as immutable for security. [3]
The cloud page states that Visage maintains SOC 2 Type II and HIPAA audit annual certification, and that Visage 7 streaming uses end-to-end TLS encryption. It also states that no equipment is necessary at the organization other than one or more routers for redundancy to secure cloud delivery of DICOM and HL7 data. These are vendor statements about the cloud service. [3]
Viewer Workflow and Clinical Roles
The productivity page describes a One Viewer philosophy in which all end users access Visage 7 tools based on clinical need. It states that the same viewer is used on Windows and macOS, with role-based access and an unlimited number of clinical roles. The online help describes user levels that can enable or disable individual tools. [6][8]
The online help describes the Study Browser as an overview of all data stored on the Visage 7 server or connected network nodes, and explicitly states that it is not a worklist. It also describes tools for viewing PACS reports or HL7 reports for currently loaded studies. The technical page describes native thin-slice and 3D processing, including multiplanar reformatting and volume rendering. [4][6]