- This topic has 2 replies, 2 voices, and was last updated 3 years, 4 months ago by
.
-
Topic
-
When your EMR is hosted, there is some small latency in your TCP/IP connection to and from the EMR.
When you add a cloud-hosted Cloverleaf to the mix, is the latency increasing to the point where it is noticeable, especially the ADT feed from the EMR to Cloverleaf? Or does the EMR in one data center talk directly to Cloverleaf in another data center? And basically all ancillary TCP/IP connections must have firewall entries in the Cloverleaf cloud network?
If you have batch shell scripts that perform SFTP file transfers to external sites, and some of those sites have exchanged keys with you such that you no longer have to supply a password when connecting, do you get that same level of access control from the Cloverleaf cloud?
Peter Heggie
-
Replies
-
-
There is some extra latency, yes, but not noticeable. We have had no problems at all with latency even for busy interfaces and large hospital systems.
The on-premise network connects to Cloverleaf Cloud over a site-to-site VPN tunnel. All other networking on the customer side goes through the customer network and over the VPN tunnel. For example Epic <–> On-Premise <–> Cloverleaf.
SFTP scripts running outside of CLoverleaf (ex. cron) should be converted to Cloverleaf threads (ex. fileset-ftp or UPoC). Full control is available for SSH keys. The Secure Messenger license, which enables FTPS/SFTP/TCP-TLS, is included with CLoverleaf Cloud.
-- Max Drown (Infor)
-
-
- You must be logged in to reply to this topic.
