DigitalVA



Now that your PowerShare account has been setup our next step is to install your Accelerator gateway. I will need you to identify the following before our gateway install:A host PC or VM for our software to be installed on.?Make sure that this meets specs, is always on, and has a static IP address. You will need to identify an IT resource that will remote us into the PC or VM for the install. They will need to start up our WebEx for the Accelerator install on the host PC or VM. Identify who will be configuring PACS with the DICOM destinations we setup during the install.This is the required information before we can schedule the install of your Accelerator gateway. Please return the requested information within 5 business days. Once we receive this complete information one of our Optimization Consultants will reach out to your assigned IT resource to schedule the Accelerator install. Listed below are some frequently asked questions regarding the Accelerator install. Please share with your IT resource selected for the install. What is the Accelerator?It is software installed on a local PC or server at your facility that receives DICOM from your PACS/modalities and then forwards those studies to the PowerShare cloud. It temporarily stores the studies locally on the hard drive, while it encrypts, compresses, and sends them to the cloud.? It then deletes the files.? It can also pull studies down from the cloud, decompress, decrypt, and then do a DICOM send to your PACS system.Do we need a dedicated server for the Accelerator?It depends on your volume.?Please refer to the attached specs document to view volume information. Our software runs in the background as a windows service and creates DICOM ports that listen for studies from your PACS.? It has no interface installed on the machine and doesn't store PHI permanently.? It can run in the background of a process server or a strong tech PC as long as it meets specs.? Our specs increase as the expected volume increases.Can our software run in a VM environment?Yes, our software can run in a VM as long as it stays on, meets specs, and has a static IP address.Does your software use Java?? If so, what version?Our 2.3.4 Accelerator version includes Java JRE 1.7.0_45.? However, we copy the files to our directory and do not install it into the Windows registry.? Only our software references it and it does not affect existing installations of Java.? Do we need to do any special backups of our software?No, we do not store any PHI permanently on the machine and the Accelerator configuration is stored in the cloud. ?If the computer hosting our software crashes, we can simply reinstall and push the configuration back down from the cloud.Is there a requirement for a server to be in the DMZ?No.If yes, what inbound and outbound ports are needed to be open?Outbound ports to specific IP addresses are in the attached specs document.What encryption do you use to transfer data to the cloud?TLS 1.2 with 256-bit AES encryption using RSA key-exchange mechanism.? HTTPS over port 443.What are the network requirements?The PC needs to be able to talk to the imaging LAN and have outbound access to the port/IP's listed on the specs document.What do I need to setup the receiving channel?Our Calling AE title will be “POWERSHARE”.? Our Calling IP address will be the IP address of the PC hosting our Accelerator software.? Our Calling Port will be the same as your PACS listening port.RecommendationProcessorRAMProcessor ThreadsSender ThreadsHD SpaceDaily Study VolumeInternet SpeedMinimumCore2Duo 2.4ghz+4GB4560GBUp to 200/day5MB/s+MediumCore2Quad, i5-Dual, i7-Dual, Xeon-Dual8GB81060GB200-600/day10MB/s+Optimali5-Quad, i7-Quad, Xeon(Quad or Hex)8GB122060GBOver 600/day10MB/s+Operating Systems ConsiderationsAll 32 and 64 Bit Server OS versions above Win-2000, Server 2016 supported. VM environments are fully supported. The hardware must have a static or reserved IP address, no DHCP. Local Windows Firewall must allow inbound connections. The range for all external IPs is 216.52.195.129/26 Specific IPs for network traffic URLs are:upload1.:443 = 216.52.195.130upload.:443 = 216.52.195.172www1.:443 = 216.52.195.149gwconfig.:443 = 216.52.195.148api.:443 = 216.52.195.186turbo.:443 = 216.52.195.182hl7v2.:443 = 216.52.195.183prrs.:443 = 216.52.195.152?Adding “*.:443” and “*.:443” to firewall exclusions would cover the URL and port range.*Exclude these from scanning content filter – i.e. Websense, Sonic Wall ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download