Networking
AVImark only works properly on Windows Servers. It is a pretty simple, self-contained database but uses Windows conventions for rebuilding indexes. Some effort was made years ago to adapt the program to Linux but this has fallen by the wayside. Now with the advent of so many third party tie-ins, it is unlikely there will be a Linux version of AVImark. AVImark will not run on Mac computers. However, there are ways to remote into a Windows computer using RDP and the like to allow the owner of a clinic and key doctors to work from home using a Mac computer.
AVImark will run okay on a Workgroup if there are only ten or so computers and the computers are all fairly new, good quality computers. Due to the way the programs works when creating invoices, having slow computers on the network can slow down the check out process. There can also be problems with DNS and DHCP services being controlled by a device (likely your internet router) rather than a proper server. So while a Workgroup is okay for smaller clinics, a better solution is going to a Domain with a standalone server.
Proper cabling throughout the building is also a big help in getting the best performance out of AVImark. Recent versions of the program are a bit better at dealing with slow networks, but any network interruption is going to throw errors. Ideally every computer using AVImark will have its own direct Cat5 or Cat6 connection to the server switch. Sharing a network connection with a phone normally works, but it does add another failure point to the network.
Wireless has gotten better over the years and it is possible to get good results using wireless connectivity to a laptop or a tablet, however, using too many of these devices will cause problems and AVImark crashes. If you do use a wireless connection, close AVImark when you are done using it and start it up again when you need to get back into the program.
Training
I have been working with and training on AVImark for over 20 years. While never directly working for parent company, I have had a lot of direct contact with them as an independent contractor. One of the biggest problems I have seen at clinics running AVImark is the lack of consistency in how the program is used. It is a pretty versatile program which is good and bad. It is good to have different options as to how to use the program, but I have seen some very roundabout operations set up for what should be pretty simple procedures.
Typically this is a lack of training and understanding of how the program works. Training can help with this but also requires buy in from the managers and owners of the business to allocate the time and effort required to get these processes in place.
AVImark only works properly on Windows Servers. It is a pretty simple, self-contained database but uses Windows conventions for rebuilding indexes. Some effort was made years ago to adapt the program to Linux but this has fallen by the wayside. Now with the advent of so many third party tie-ins, it is unlikely there will be a Linux version of AVImark. AVImark will not run on Mac computers. However, there are ways to remote into a Windows computer using RDP and the like to allow the owner of a clinic and key doctors to work from home using a Mac computer.
AVImark will run okay on a Workgroup if there are only ten or so computers and the computers are all fairly new, good quality computers. Due to the way the programs works when creating invoices, having slow computers on the network can slow down the check out process. There can also be problems with DNS and DHCP services being controlled by a device (likely your internet router) rather than a proper server. So while a Workgroup is okay for smaller clinics, a better solution is going to a Domain with a standalone server.
Proper cabling throughout the building is also a big help in getting the best performance out of AVImark. Recent versions of the program are a bit better at dealing with slow networks, but any network interruption is going to throw errors. Ideally every computer using AVImark will have its own direct Cat5 or Cat6 connection to the server switch. Sharing a network connection with a phone normally works, but it does add another failure point to the network.
Wireless has gotten better over the years and it is possible to get good results using wireless connectivity to a laptop or a tablet, however, using too many of these devices will cause problems and AVImark crashes. If you do use a wireless connection, close AVImark when you are done using it and start it up again when you need to get back into the program.
Training
I have been working with and training on AVImark for over 20 years. While never directly working for parent company, I have had a lot of direct contact with them as an independent contractor. One of the biggest problems I have seen at clinics running AVImark is the lack of consistency in how the program is used. It is a pretty versatile program which is good and bad. It is good to have different options as to how to use the program, but I have seen some very roundabout operations set up for what should be pretty simple procedures.
Typically this is a lack of training and understanding of how the program works. Training can help with this but also requires buy in from the managers and owners of the business to allocate the time and effort required to get these processes in place.