Having said this and George's reply, I would be able to give feedback as to users level of acceptance of ScreenMan as the interface especially for labs and pharmacy.
Rgds, Molly
George Timson wrote:
Dear Hardhats,
I would like to respond to what I see on the Hardhats Sourceforge archive page this morning:
From: "Dr Molly Cheah" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, September 18, 2004 8:29 AM Subject: Re: [Hardhats-members] ScreenMan
> Oh, I thought it will be able open source [sic] .... After all Medsphere uses > OpenVistA. Otherwise it sounds like "what"s yours is mine and what is > mine is mine" :) > > Molly > Nancy Anthracite wrote: > > >So all you M programmers out there. How about an OPEN SOURCE version of > >this. Think you can do it? > >
Dr. Anthracite and Dr. Cheah seem to assume that, if I write ScreenMan code for Medsphere, it will not subsequently be open-sourced. I am wondering where they got this impression. What Medsphere representative has ever written or said this?
The facts are that:
1) Medsphere has contributed to the Open-source implementation of GT.M-compatible VistA code since early 2002.
2) Medsphere hosted a World VistA meeting at its offices in Orange County in August 2002, and has sent representatives to virtually every meeting the group has ever conducted.
3) Medsphere offered WorldVistA in 2002 a computer platform and software (CMS) with which to manage open-source code. The VistA community seems to have left this resource unused.
4) In December, 2002, Medsphere gave to the DVA, for free, code changes, written by me and paid for by Medsphere, to over 150 FileMan routines, which enhance FileMan's Internationalization capabilities. DVA has done nothing to disseminate this code in the intervening two years, and has made it more than clear that it will not deal with unsolicited enhancements or patches to its large corpus of "parked" VistA software.
When the VistA community has in place a mechanism for submitting, testing, peer-reviewing, approving, and disseminating code modifications, I will be delighted to know about it. Our ability at Medsphere to support such a mechanism in-house has been hampered this year by our ongoing implementation of VistA for several hospitals in the South Central U.S. Nor do we now believe that such a code-sharing mechanism should be in the hands of one for-profit vendor like Medsphere.
I would suggest that it is time for the community to put a source-code-sharing mechanism in place for the use of all parties interested in VistA (as distinct from a small group of techies who EMail code snippets amongst themselves). When that job is accomplished, be assured that Medsphere will be ready to continue contributing to the promulgation and improvement of Open-source VistA software worldwide.
Yours truly,
--George Timson
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Hardhats-members mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hardhats-members
