Kevin wrote: >Medsphere has certainly put money into the development >of this technology. And I will understand if they >want a return on that investment.
I am sure that they will see a tremendous return if their solution is widely adopted whether Open Source or not. Making it Open Source would help to ensure wide acceptance and adoption. >Is there any way that we could develop equivalent >technology in an opensource fashion? You know more about the client side of CPRS than I do. On the server side, developing an M2Web/GT.M/Apache based version of the VistA RPC broker seems like a relatively small project. >I don't understand the arrangement he described. As I read it, There could be one server running VistA with an unmodified RPC broker and a separate intermediary server running a web server that receives HTTPS requests from the CPRS client and calls a SOAP middleware application that sends them on to the RPC broker and relays back the responses. >Kevin > > >--- Jim Self <[EMAIL PROTECTED]> wrote: > >> Very interesting. I look forward to learning more >> about it when it becomes available. What >> is the middleware? Perl, Java, other? What is the >> crossplatform foundation for the client? >> >> The split-server configuration is similar to the way >> that we configure VMACS in production >> systems except that we also use https for the local >> connections. >> >> Todd Berman wrote: >> >On Wed, 2005-07-20 at 15:25 -0700, Jim Self wrote: >> >> This sort of approach would undoubtedly simplify >> many things. Since SSL is *THE* secure >> >> protocol for virtually all secure web services, I >> imagine that it was simply overlooked >> >> not rejected. >> >> >> >> Could you give us more specifics as to what you >> (medsphere) are doing and is it available >> >> as Open Source? >> >> >> > >> >We have implemented 2 things, a crossplatform >> version of CPRS that runs, >> >and has been tested, on Windows, Linux and OSX. Our >> goal is to both >> >modernize CPRS in general, and to allow us to >> integrate and expand on >> >the GUI functionality offered. This application >> talks to VistA through a >> >piece of middle-ware, that publishes a >> standards-based SOAP Web Service >> >API instead of RPC calls. This API is available >> over a HTTPS connection, >> >and the middle-ware then speaks directly to the >> VistA server, over a lan >> >connection (thus isolating the VistA server from >> the internet-at-large, >> >and allowing remote connections in a HIPPA >> compliant manner). We are in >> >the midst of heavy discussions about how to open >> source the various >> >pieces involved. >> > >> > >> >--Todd >> --------------------------------------- Jim Self Systems Architect, Lead Developer VMTH Computer Services, UC Davis (http://www.vmth.ucdavis.edu/us/jaself) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
