This document applies to OnePacs Gateway version 2.5.1+. |
The OnePacs Gateway is software that receives DICOM images from an imaging device or archive, then compresses and securely transfers them to OnePacs.
The OnePacs Gateway runs on a Windows-based computer on the local network of an imaging facility or hospital. The computer may be a physical server or a virtual machine. The OnePacs Gateway runs as a system service on the computer and does not require a user to be logged in.
No. The OnePacs Gateway uses transport layer security (TLS) to securely communicate with the OnePacs Cloud over the internet.
Hardware, software and bandwidth requirements:
Network Requirements:The OnePacs Gateway does not require a public IP address or any inbound ports to be opened in your organization's firewall. A static private IP address on the local area network is required to provide a fixed target for your DICOM devices to communicate with. Inbound DICOM traffic is received on port 4104 (configurable) and the gateway communicates with the OnePacs Cloud on a *.onepacs.com domain on port 443 using only secure protocols. Installation Requirements:
|
All information transmitted to the cloud platform is encrypted using using transport layer security (TLS) with a minimum of 128-bit Advanced Encryption Standard (AES) public key encryption utilizing a SHA-2 hash algorithm.
The OnePacs license agreement requires physical access restrictions limiting physical access to the gateway computer to authorized personnel with a legitimate need to access the equipment and/or the use of whole hard disk encryption (e.g. BitLocker).
It is recommended that an anti-virus with a current subscription be in place on the Gateway PC. To ensure proper operation of the Gateway exclude the following directories from the anti-virus scans:
The OnePacs Gateway should not be configured to support storage of DICOM images from multiple unrelated organizations.