Virtualization VAM can operate on any standard virtual server.
Server Configuration VAM supports deployment in multiple configurations depending upon the need and size of deployment.
Network Connectivity VAM requires the server to be connected to the hospital intranet through the hospital's LAN (10M or higher speeds), and supports dual network deployments with physical separation of external IP and internal IP.
External IP/URL Name (SSL Requirement)
For mobile device access from outside the hospital, VAM's application server requires a static external IP address.
Firewall Considerations
These sections describe ports and blocking access to the VAM Console.
Shared Folder Connections VAM uses shared folder connections to receive data through XML interfaces. In such cases, the shared folder should be accessible by the process account used by VAM at the site.
History Query Path and Web Services VAM uses a web service on the EKG Archival system for querying for and retrieving historic EKGs for each patient message that is processed through the VAM communication system.
SMTP For Email Notifications VAM's server includes system health monitors that can report current or potential problems, as well as daily use statistics, through email.
Console Support
The VAM console operates as a web-based (thin client) console. It is supported on all versions of Internet Explorer (7 and later) and current versions of Chrome and Firefox browsers.
SSL / Secure Data Pipe
These sections provide information on certificates that can be used with the VAM server.
Firewall Configuration
The firewall needs to be configured so that HTTP requests that come in on port 443 at the static external IP are routed to the VAM IIS server.
