First, let's talk a little more about the speed test. I guess we are at apples and oranges right now. I think you said on the same computer. You wouldn't want to test on from one location to another on the same computer as that will be blazing fast as it does not have to go over the network.
You want to run four tests.
1. From a problem computer to the server (a folder on the server) may as well make it Amazing Charts.
2. From the best performing computer to the same folder on the server.
3. From the same problem computer to another computer on the network. \\computername\Users\
4. From the best performing computer to another computer on the network \\computername\Users\ to the same computer
The best way to test or at least the best way for some of us to interpret the data is to use 2,000 packet length and use the measure Mbps. Not sure which version you are using. I like the older versions such as 1.3.2. Time to complete isn't that helpful. In 1.3.2 Mbps is in bold. Think about it. Your entire wired network is configured at 1Gbps speed. Cat5e or Cat6, your switch, hopefully your NIC cards, etc. So, theoretically, you should be getting 1000Mbps, but you will almost never attain that on your network. Read speed will almost always best faster that writes. It will determine how fast AC opens up, how fast your chart opens, how fast medication data loads into the script writer, etc. So, for some examples:
My computer to the server:
Let's see what we can learn here. This is a decent connection, but less than half the 1Gb speed it should be getting. And, writes are faster than reads. Here, I will have fairly normal AC speeds. It will open OK. And, I probably won't notice, because I don't have a ton of computers going faster.
My computer to reception (two clients)
When the same computer (my computer) reads and writes to another computer on the network, I get much better speeds. I would get nearly double the performance at these speeds. Still not near the 1Gb.
Checkout to server
Here is a computer to server issue I have had and was troubleshooting for a while. Changed NIC cards and settings. Changed Ethernet. Changed switch ports. But, you can see the speeds are horrible. Given the low read speeds, AC takes a minute to load as it has to load all the demographics and other things over this slow connection. ePrescribe would be slow as far as loading a patient with a lot of meds, especially inactivated meds. Once brought over, I would be fine. Given this computer is not used much in production, I am waiting until my new server is brought online. You won't do much writing. Saving the chart would be one. Messages are small. I don't do a lot of II, so I can't talk to that much.
So, office to server was decent. Checkout horrible. Office to reception was pretty good, so the server must have an issue, but Checkout must be a problematic computer, right?
Checkout to reception (two clients - to the same computer)
So we would expect checkout to reception to be better than to server but not as good as Office to Reception. But, not the case. Blazing speeds and read speeds approaching the theoretical limit. So, we can't really say its Checkout.
We can only surmise that:
Office to server not bad
Checkout to server rather slow
Office to reception much faster
Checkout to reception very fast
So that really tells me two things:
Checkout to server is not good. AC on checkout will not perform well. It should be slower. Keep in mind that AC preloads for speed. I can't tell you everything that is preloaded, but it is demographics for sure. Also, note if you click on the demographics tab or the MRE tab, any computer will take three to five seconds to load (lets say). Do it again and it's instantaneous.
But, it also tells me that it doesn't seem to be the Checkout computer. So, if AC were rather slow there, it probably isn't AC's fault.
It tells me that it isn't AC, it seems to be more likely my network. While the connections all seem good, and the Ethernet and Switch and NICs are all 1Gbps, something is causing a bottleneck. And, there seems to be a problem with Checkout to server. Why? I don't know. But, both are slower to the server. So, is there an issue there?
So just for fun, we run Checkout to a different folder. Same issue. So, we have issues with the server speeds, worse with Checkout. Checkout computer is fine, but has an issue when connecting to server. So, what is our biggest common denominator. When checkout had blazing speeds to reception, it went:
NIC -> Patch cable -> Wall jack -> Ethernet cable -> Switch -> Ethernet cable of reception -> Wall jack -> Patch cable -> NIC of reception
When checkout went to server, it followed the same path, but the cable from the switch to the server jack to the patch panel to NIC was different. So, we have ruled out nearly everything except cable from switch to wall jack to patch panel to NIC of server. So there are various things you can do trouble shoot. You can get rid of patch panel, wall jack and Ethernet cable to switch, by connecting the Checkout computer via long Ethernet cable directly to the NIC. If that is still slow, then you probably have an answer. Still there are more steps.
But, if you notice, while you can do one troubleshooting step after another, it is complicated given the different speeds even with different computers. So, do you blame AC, do you keep spending all night troubleshooting? Or do you do the sensible thing and write all this down, call a reputable computer networking shop who can come over with a fairly expensive fluke meter and test all your connections in seconds to minutes. Total cost for one hour of work: $185? Then you will know if you have an issue with your network, if so, where it is, what it is.
As far the script writer, on the settings at top right, you can see how many things are turned on for allergy checking and interactions and insurance tier checking, etc. If you use MU, then some of these have to be on. These, I believe but I could be wrong, are going to be dependent somewhat on the Internet. I don't think the AC database can check BCBS copays and tiers, etc. But, it shouldn't need much speed to do that.
Finally, it's hard to know exactly, because most people say ePrescribe is slow, but I am not sure where it is slow. Opening, writing a med, preparing the script, prescribing it, etc. If it were with sending, you could use NC's screens and send in about 15 seconds. To prepare a script there takes longer. Any med that you prescribe there that is codified will be save in your current meds in AC.