Eliminate patient no-shows
Handle patient calls 24/7
Schedule patient appointments online
CALL 000-000-000

Frequently Asked Questions

1. Why do I need a separate server when I use the on-premises version of AssistMedic? Can't it just run on my desktop computer?

In theory AssistMedic should be able to run on any desktop machine including all flavors of Windows desktops. However after weighing all the pros and cons we have chosen to ship the on-premises versions of AssistMedic on our own servers. There are numerous reasons behind this choice but the most important ones are:

  • We are constantly working on improvements to our system. So at some point in time it may turn out that it is very beneficial to our customers to upgrade the system to a newer version because of all the new features that have been added. If the system is located on our dedicated system, then the upgrade can be performed seamlessly because we are well familiar with the system on the dedicated server. On the other hand if the system is located on the user's computer this means that we will have to perform the upgrade in an unknown environment. The upgrade could interfere with some programs that are already installed on the user's computer. Some of the doctor's programs may start to malfunction or the medical system itself may have problems working correctly. So the bottom line is that having the medical system run on a separate server greatly lowers the maintainance costs and thus translated to a lower prices for our customers.

  • System security might be a problem if the system uses the desktop computer as a server. If we use a separate server, we can configure its firewall and other security components to be quite restrictive. We know well what internet services are being used by our medical system, so we can configure the server in such a way that the only allowed internet services are the ones required by our medical system. On the other hand if we use the doctor's desktop computer as a server, then we do not know in advance what internet services he is going to use. So in this case we will have two choices - either configure the security to be quite strict and in this case some of the desktop applications may stop working correctly. Or we can configure the security restrictions to be rather lax. In this case the doctor's custom programs will work fine, but his data would be endangered by hackers.

  • The computer with our system on it should run uninterrupted 24/7, since some patients may want to access the system at night either through the web browser or over the phone. A continuous 24/7 work is something expected from servers but it may be a problematic for regular desktop computers.

  • The speech processing component of our service requires lots of computing power. On a desktop computer it would compete for processor power with other desktop applications, which would lead to both slower desktop application and degraded speech processing of incoming phone calls.