On Oct 9, 2005, at 4:59 AM, Nancy Anthracite wrote:

I spoke with a physician yesterday who wants to try installing FOIA VistA because he can't get his hands on VOE. He said that VOE is a hot topic of discussion at his hospital and that 100% of the docs are convinced that VOE is not being released because "Big Business" is applying political pressure to CMS to stop it. They think that all of the testing and waiting to meet
standards is just a smoke screen and that it will never be released.

Really? Maybe I shouldn't be so blunt, but I think the real problem is that that making the changes/additions that CMS had in mind turned out to be more difficult than expected. Beyond that, people that are new to VistA *development* always seem to underestimate the learning curve.

I always get grief from my coworkers because I won't buy into the philosophy of just putting the business logic in the middle of a report. The whole thing has grown slowly and organically, often resulting in modules of very poor cohesion (clearly and narrowly defined functionality). At the time, no one worries much about it because "it's just this one change". But it quickly gets out of hand, and it isn't long until global knowledge of code is really necessary to be an effective developer.

It seems quite fashionable on this list to speak disparagingly of VHA's attempt to build a next generation system, and think of it as mere ineptness. All I can say is that you've spent 10 or more years with the code, you will understand that there comes a time, when reworking it really is necessary. "Patching" is attractive in the short run, but it's not a good long term development strategy.

===
Gregory Woodhouse
[EMAIL PROTECTED]

"Prediction is difficult, especially of the future."
--Niels Bohr




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to