I know exactly what you mean. I am by no means a SQL programming expert, but we did identify something just like what you are talking about on the PM side of CPS 10, reported it to GE, and actually got them to address it in a service pack (after several months). At the time, we had one site rolled out on EMR with potential for three more so we sort of used that as leverage and told them we'd go with another product unless they addressed the issue.
We used to be able to run CPO 2004 (and before that, Millbrook) in a fat client WAN environment with only 1.5mbps in between sites, but performance took a huge dump when we upgraded to CPS 10. We've since gone to thin client environment at our EMR sites, but that presents a whole seperate set of challenges (half assed printer preference tracking in CPS, difficulty with cameras, scanning, etc).
Basically, when opening a patient's profile (demographic screen), the app was querying for the ENTIRE doctorfacility table and the entire thing was being returned over the network. In our case since we have many thousands of referring doctors, this was several megabytes transmitting needlessly over the network. Only a couple of rows were actually needed - the ones that pertained to that patient - his doctor, PCP, and referring doc, but GE was returning several thousand rows of data (about 10 megabytes in our case).
I have no doubt there are countless other examples of this kind of thing throughout the application. We've been dealing with random SEH errors on the PM side for 7 years now that are always supposed to get better with each service pack, but they never do. They always want to blame it on the network (even when the errors still happen on a LAN) or have us throw more hardware at the problem, but the truth is, it won't make a difference. We're on our third hardware iteration since I started and it's the same thing still. They need to pay more attention to quality control.
My hope is that since they are discontinuing the Oracle version and moving forward only with SQL, that they will start to address some of these quality issues. If they don't, they might lose those Oracle customers. From Oracle customers that I've spoken to, they seem relatively okay with the reliability/stability of the product. The CPS people seem to be the opposite. Constantly working around problems, rebooting servers, etc to keep things running.
-Matt
Posted : December 21, 2012 12:34 am