TheraManager Help Note

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 1 of 7

Subject: Client-Server vs. Cloud

This Help Note provides a brief, lay perspective of TheraManager operating in either a client/server or cloud environment.

Client/Server

Not a client Not a server

Help Notes related to TheraManager operating on a network frequently refer to “clients” and “servers.” What is the difference between a client and a server?

 A client is the installation of TheraManager (literally, the TheraManager.exe and affiliate files) installed on each computer, which accesses Main Data on the server. Clients can access the server via a local area network (LAN), wide area network (WAN) or over the Internet.

 The server has the Main Data folder comprising your database residing on it. It is

recommended that the server also have the Master Data folder as well. Both Main Data and Master Data are shared so that all TheraManager client s can access them.

A server can (and, in most instances, usually does) have the .\TheraManager client installed as well. There can be many TheraManager clients on a network, but only one server.

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 2 of 7 Type Default Client File Path Default Server File Path (to Main Data)

File Path Resettable?

Client/ Server

C:\Program Files (x86)\TheraManager (64-bit)

C:\Program Files\TheraManager (32-bit)

Local: Same as client

LAN: \\[myserver:2000] or static IP address

Yes†

Cloud C:\Program Files (x86)\TheraManager – [unique practice identifier]

Same as client No

For simplicity, throughout these Help Notes the convention .\TheraManager is used to denote a TheraManager client.

[continued]

†

For example, the file path for a local client can be reset to E:\ Program Files (x86)\TheraManager or to a shared C$ drive. However, care must be exercised that the ads.ini file be reset accordingly. See Resetting the ads.ini File.pdf as needed.

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 3 of 7 This is visible in the address bar in the Computer/My Computer view:

     

   

 

On the server, the recommended location for Main Data (and Master Data, if on a LAN) is on a newly created folder on the root directory:

(additional folders within the C:\ drive [also known as “root directory”])

(additional folders within the Program Files folder)

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 4 of 7 C:\TheraManager\Main Data

Also, the Advantage Database Server must be installed on the same drive as the Main Data. See the applicable Installation Help Notes (keyword: install) for details.

Cloud

Clouds The cloud

With TheraManager in the cloud, no TheraManager client or database resides on the practice’s premises. Instead, the TheraManager application and the practice’s data reside on a HIPAA-compliant server leased by TheraManager LLC. Each device (desktop, notebook, tablet, phone etc.) wishing to access TheraManager establishes a “remote desktop connection” to an Internet protocol (IP) address representing the server.

For workstations, such a connection can be launched either from a Remote Desktop Protocol (Cloud.rdp) file installed on the desktop, or via the Windows Start button. For phones, you can access the IP address via an RDP app designed for Android, iPhone etc.

Risk: Client/Server or Cloud?

The following table provides an approach to assessing the risks of implementing TheraManager in a client/server or cloud environment. You should carefully consider the economic impact, probability and cost to your practice of each risk criterion.

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 5 of 7 Risk Assessment: Client/Server vs. Cloud (Disadvantage Advantage Neutral)

Criterion Client/Server Cloud (RDP)

Upfront cost of server  Borne by customer

 Updating each client required (inconsistent program versions can cause database corruption)  Often poorly executed (or not

done at all)

 Embedded in monthly fee

 Professionally managed

 HIPAA- compliant (with TheraManager) Ongoing server maintenance Backup/Restoration Client installation/ updates

Login – out-of-office  Must have TheraManager installed on client (unless using remote desktop client)

 Access via Mac computers require Windows virtualization app (e.g., Parallels)

 Access via tablet or phone requires client’s server to be powered on

 Subject to Internet availability  Latency can be significant

 Available on any computer (Windows or Mac) via RDP shortcut

 TheraManager client installed on cloud server

 Access via tablet or phone (requires RDP client)

 (According to numerous field reports) Little or no latency

 Subject to Internet availability  Connection subject to

sporadic “whiteout” termination

Login – within an office

 Varies according to load on LAN from contending resources, wireless signal strength, server condition etc.

 Not subject to Internet availability (generally)

Printing Generally, non-issue  Printing can be slower  RDP client may not

consistently recognize printer  Certain printer models can

disable printing for other cloud users

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 6 of 7 [continued]

Criterion Client/Server Cloud RDP

Security High Risk:

 Resident server unlikely to be HIPAA-compliant without cost-prohibitive infrastructure investment

 Single login/password per user to access Main Data

 On laptops, unencrypted XLS exports on laptops

 Historically, > 2x greater frequency of hacker attacks than cloud

 More-stringent HIPAA

regulations can be prohibitive for many practices

Low Risk:

 Two-level access to Main Data

 RDP user names and

passwords maintained by TheraManager LLC

 Encrypted links between

cloud server and all end-user devices

 Facility-wide emergency power and lighting and protection from fire and water damage

 24/7/365 physical security monitoring

 90-day video surveillance and retention

 Secure cabinets and cages

used to house all server hardware

 Monthly cabinet and cage

access reports

 Badges and biometrics

required for user access to the data center

 Availability of data center for external audits

 Response plans in case of

security incidents

TheraManager Help Note

Last updated: November 24, 2014 © TheraManager LLC 2000-2014 Page 7 of 7 [continued]

Criterion Client/Server Cloud RDP

Cost  Significant upfront expense  Annual or biannual support

contract expense

 Infractions from ONC can be prohibitive (~$100Ks to $M!)