PowerServer is RamSoft's radiology software suite, positioned by the vendor as a single platform covering intake, image management, reporting, and workflow automation. The product line appears in multiple named configurations, including RIS/PACS, PACS, TELE PLUS, and LITE PACS, offered through both cloud-hosted and on-premises deployment models. Documentation indicates that DICOM and HL7 conformance, system specifications, and compliance statements are maintained separately from promotional material. [1][2][3][7]
Documented Product Structure and Deployment Models
RamSoft's product page identifies four PowerServer configurations: PowerServer RIS/PACS, PowerServer PACS, PowerServer TELE PLUS, and PowerServer LITE PACS. The RIS/PACS version is described by the vendor as a unified, single-database platform spanning acquisition, interpretation, and workflow, while the PACS version is presented as an image management product with RIS, HIS, and EMR integration. TELE PLUS is marketed for teleradiology access, and LITE PACS is described as aimed at small to mid-sized organizations. These are vendor classifications rather than an independently verified product taxonomy. [1][6][8]
Version 6.7 system documentation states that specifications apply to both RamSoft Hosted and On-Premises models, and that hardware requirements for 6.7 are the same as those documented for version 6.0. The specification document distinguishes feature availability between hosted and on-premises deployments; for example, automated diagnostics and golden image deployment are listed as hosted-only, while on-premises deployments use manual PRU-based deployment. Customers are advised that requirements may change without notice and can vary with modality, retention, and concurrent users. [3]
DICOM, HL7, and Interoperability Scope
The DICOM Conformance Statement covers PowerServer along with Gateway, Gateway Router, PowerCache, and RapidResults. It documents storage support for multiple image types, including digital X-ray presentation and processing states, digital mammography, breast tomosynthesis, X-ray angiographic, ultrasound, secondary capture, and hardcopy grayscale images. The conformance document also lists support for DICOM Web client operations including Echo, Store, Find, and Retrieve, and states that configuration is handled through configuration files and a database. [2][4]
A separate HL7 Conformance Statement describes the RamSoft Mirth Connect integration engine, which is based on Mirth Connect 4.4.2 and supports HL7 version 2.3.1 over MLLP. Documented inbound message types include ADT patient events, ORM orders, ORU results, SIU scheduling, BAR billing account events, DFT financial transactions, and MFN user information. The document adds that the HL7 conformance statement is intended to support integration with external systems such as RIS, HIS, or the RamSoft Gateway for modality worklists. [7]
The 6.7 DICOM documentation revision notes record that High-Throughput JPEG 2000 transfer syntax support was added in 2026 and that the TLS conformance description was updated to reflect TLS 1.2 and higher. These entries are versioned documentation changes rather than claims about clinical performance, and the conformance statement explicitly cautions that DICOM conformance alone does not guarantee interoperability. [2][4]
A Hypothetical Evaluation Scenario
An imaging organization considering PowerServer might structure a demonstration around a representative multi-modality workflow without assuming the vendor's published performance metrics will replicate in its own environment. A hypothetical scenario could load a specified set of de-identified studies across CT, MR, mammography with tomosynthesis, and X-ray, then measure first image render times and full study cache times on hardware matching the documented on-premises specifications. The organization could also test DICOM transfer syntax negotiation using the conformance statement's listed SOP classes and exercise HL7 ADT, ORM, and ORU message flows against a test RIS instance. Because the vendor brochures do not disclose benchmarking methodology, local measurement would be necessary to assess whether the claimed improvements are observable under the organization's network, storage, and user concurrency conditions.
Security and Compliance Documentation
RamSoft's product page states that PowerServer is developed under the ISO 13485 medical device quality management framework and holds SOC 2 Type II and TX-RAMP certifications. The same page describes availability on the Microsoft Azure Marketplace. A separate product page adds that the suite holds industry certifications including HIPAA, TexasRAMP, and SOC 2 Type II, and is hosted on Microsoft Azure. These statements originate from vendor materials and are not reproduced here as independently verified certifications. [1][8]
Version 6.7 documentation includes AES-256 encryption support in its updated security documentation, and the TLS conformance position was revised to TLS 1.2 and higher. The vendor also describes Microsoft Azure hosting with a stated 99.95% uptime for cloud deployments. The specification document notes that PowerServer and PowerReader communication is encrypted by default and that remote staff access can be configured without VPN when PowerServer is deployed in a DMZ. [3][4][5]
Performance Claims in Vendor Materials
RamSoft's PACS and RIS/PACS brochures attribute version 6.7 performance changes to HTJ2K compression and remote rendering architecture. Claimed improvements include approximately 39% faster average first image render time across all modalities, 67% faster first image render for chest X-ray, 57% faster 3D digital breast tomosynthesis render, 40% faster CT study load time, and up to 80% faster full study caching for large frame-count studies. The MR example is specified as an 80% reduction in full cache time from 1 minute 29 seconds to 18 seconds for a 2,000-image study. [5][6]
These figures are promotional performance metrics published by the vendor and should be read as marketing claims rather than independently validated benchmarks. The brochures do not provide study methodology, sample sizes, or testing conditions. Where the PACS and RIS/PACS documents list overlapping metrics, the cited values are generally consistent, but the source material does not contain third-party confirmation of the measurements. [5][6]
Implementation and Operational Boundaries
The platform specification document defines backup responsibilities differently by deployment model. Hosted customers have server-level backup and replication managed by RamSoft, while on-premises customers are responsible for implementing and maintaining their own backup and replication strategies. The document also describes file-level image-only backups as a method that excludes the PowerServer application and database, requiring a new installation and image import for recovery, with patient and study demographics lost in that scenario. [3]
Remote support documentation indicates that RamSoft uses LogMeIn for ongoing remote support and monitoring, with outbound internet access required for the agent to check in. The table lists remote monitoring as performed for PowerServer (all flavors), Gateway Router, and PowerCache, with Gateway Viewer and Gateway Mammo Viewer marked as 'Possible' depending on use case. The same table marks remote monitoring as 'No' for tech workstations and radiologist workstations. [3] On-premises Gateway Router, PowerCache, and workstation specifications were updated in revision 28 of the specification document to 8-core AVX2 processors and 32GB RAM, with 64GB specified for large CT/PET workloads. [3]