OK. It is difficult for me to compare because all my machines run WIN 7 Pro, Intel i72600k, 8GBs RAM and ridulously fast graphics cards. The lowest WEI scores are 7.4 and the highest is 7.8, 0.1 off for memory. So, I can't tell, because on the machines I have played with, the ePrescribe is split second fast.
After reading all of these posts, I have pretty much come to the conclusion that it may be a SQL problem. One shouldn't have to have a super fast processor or RAM to ePrescribe. The SQL theory given above of getting Lisinopril, then sig, then amount would take longer, but I don't see why an application to SQL database that pulls all of the demograpic data at once, etc. would all of a sudden query the database in this fashion.
The other weird thing is if we are all doing trial and errors or upgrading and coming up with theories, then why would the place with hundreds of sandboxes and tons of code not know what is going on and filling us in?
WIN 7 is better at networking than XP Pro, but I don't think that carries over to working with SQL.
Sorry about the bragging. Just have a friend who knows someone who...kind of like REO Speedwagon.
