Comments on: The Future of VistA: Community versus Congressionally Mandated Leadership http://blog.crossoverhealth.com/2008/07/30/the-future-of-vista-community-versus-congressionally-mandated-leadership/ The Next Generation of Health Care Fri, 26 Feb 2010 06:55:13 +0000 http://wordpress.com/ hourly 1 By: GCPR Redux - The Call For Government EHR Unification « Crossover Healthcare http://blog.crossoverhealth.com/2008/07/30/the-future-of-vista-community-versus-congressionally-mandated-leadership/#comment-424 GCPR Redux - The Call For Government EHR Unification « Crossover Healthcare Tue, 05 Aug 2008 06:45:19 +0000 http://crossoverhealth.wordpress.com/?p=201#comment-424 [...] on my VistA kick (here and here), I need to respond to several important errors of understanding in the recent press release hailed [...] [...] on my VistA kick (here and here), I need to respond to several important errors of understanding in the recent press release hailed [...]

]]> By: Fred Trotter http://blog.crossoverhealth.com/2008/07/30/the-future-of-vista-community-versus-congressionally-mandated-leadership/#comment-412 Fred Trotter Thu, 31 Jul 2008 05:02:21 +0000 http://crossoverhealth.wordpress.com/?p=201#comment-412 Excellent points. In fact the only counter that I have to your idea, and the only reason that I did not suggest the same thing, is that Congress continually does things or allows things that really threaten the VistA lifecycle. But you either have to solve one of two problems. You either have to get some FOSS organization be trusted MORE than the VA itself regarding VistA. OR you have to accomplish what I am suggested, embedding a Mozilla foundation directly within the VA itself. Frankly, either one is pretty unlikely, which is why fear for the future of VistA. The nice thing about your plan, is that if the VA falls flat on its face, is that an "Apache Foundation for VistA" is much more likely to arise under those circumstances. Excellent points. In fact the only counter that I have to your idea, and the only reason that I did not suggest the same thing, is that Congress continually does things or allows things that really threaten the VistA lifecycle.

But you either have to solve one of two problems. You either have to get some FOSS organization be trusted MORE than the VA itself regarding VistA. OR you have to accomplish what I am suggested, embedding a Mozilla foundation directly within the VA itself.

Frankly, either one is pretty unlikely, which is why fear for the future of VistA. The nice thing about your plan, is that if the VA falls flat on its face, is that an “Apache Foundation for VistA” is much more likely to arise under those circumstances.

]]>