On Jan 19, 10:57pm, [email protected] wrote: } Subject: Re: VOE and Linux efforts.
Good day to everyone, hope your week is starting out well. > [EMAIL PROTECTED] wrote: > >the VOE sources seems to be largely locked up inside of the > >Cache database on Windows > As I understand it, the VOE sources are standard MUMPS and the > server will therefore run as well or better on GT.M/Linux as it will > on Cache/Microsoft. I also understand that VOE is 99% the same as > the FOIA version of VistA and the version available now from > worldvista.org and sourceforge. The sources do indeed seem to be standard MUMPS or VistA origin. I have not doubt they will percolate just fine under Linux after we get done exporting them from Cache. I have a FOIA implementation up and running but our group is looking at the potential for VOE under Linux. It thus seems prudent to actually run under Linux what is being developed for the Cache/Microsoft environment. One of my goals is to actualy define what VOE is. At the present time it appears somewhat unclear. I haven't been able to find a clear description or strategy for tracking how the FOIA code is being modified to produce VOE. One of the comments I've heard is that 'things are being cleaned up and old cruft removed'. The first set of files were indeed 100% equivalent to the FOIA sources. Since one of the files makes reference to handling special processes for 'Desert Shield' veterans there would seem to be minimal cleanup or de-crufting at this point. It would seem to be to the bbenefit the VistA community at large if there was a common Open-Source repository for FOIA and VOE. I will probably generate GIT repositories after this exercise is complete so we at least have a fighting history of tracking revisions and modifications. > >The best interests of Linux/OSS/Vista will be best served by having > >some type of native client capability. > > >After a bit of time studying the FOIA XWB* sources and scrutinizing > >packet traces we were able to develop a preliminary implementation of > >a Java client architecture which knows how to talk to a Vista RPC > >server/broker. > Medsphere claims to have made a VistA middleware server and a > cross-platform CPRS replacement client that connect via HTTP and > SOAP. They have promised to release all of it for use and part of it > as Open Source some time in the near future. I hope they do. It > seems like a step forward. Based on a 50,000 foot view of all the politics which seem to be in this arena I'm not optimistic to see much in the way of Open Source release coming from the commercial entities. Perhaps we will be surprised. > > but my sense is that something a LOT like CPRS is needed in the > >intermediate timeframe to make Linux client implementations a > >reality. > Unfortunately, CPRS only covers part of the functionality of > VistA. There is no GUI for administrative functions like patient > registration and scheduling. These must be done on terminal > emulators unless a new interface is developed for them. Indeed, we perceive this as a significant barrier to VOE. My hopes would be for the VistA codebase to become an important rallying point for community development of an OSS solution to health care informatics. Unfortunately it isn't clear to me how or if a development community will emerge. In this arena there would almost seem to be an economic disincentive for commercial organizations to foster an OSS development community. Linux emerged into its own since there were trained systems people who could manage and integrate the technology into the enterprise. The politics of medicine is there are probably a very minimal number of organizations who will deploy a VistA based solution with a 'professional' services organization. Obviously anything which increases the usability of a VistA based solution would be a market advantage for the service provider. It will be interesting to see where this all plays out. > My own belief is that it would be easier to build it on Mozilla and > M2Web, but perhaps that varies with your skills and interests. You certainly could be right. I need to spend a bit more time looking on the M2Web stuff and understand how it integrates with VistA and what it represents. If this is the optimum technology for a new interface architecture there still needs to be the emergence of a development community willing to work from and coordinate off a standard source base. If that is happening I'm not aware of it. > Jim Self Thanks for the comments. Best wishes for the success of your project and a productive week. Greg }-- End of excerpt from [email protected] As always, Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC. 4206 N. 19th Ave. Specializing in information infra-structure Fargo, ND 58102 development. PH: 701-281-1686 FAX: 701-281-3949 EMAIL: [EMAIL PROTECTED] ------------------------------------------------------------------------------ "Whenever you find that you are on the side of the majority, it is time to reform." -- Mark Twin
