And I would add that the "soon" would be on the order of days if not hours. Moving the routines and globals for VistA (the sum total of all that there is to the VistA-M side of things) from Cache to GT.M (or vice versa) is quite straight-forward. The infrastructure components of VistA run on both and VOE enhancements will not change that. VOE as it will be released will have much of the "day one files" predefined which is what gets moved in the globals when moved from one M implementation to another.
Cameron -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nancy Anthracite Sent: Wednesday, January 11, 2006 7:06 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] Why is VistOffice being released on Cache' I would say it is a virtual guarantee that if VOE is released, a GTM port will soon follow. However, it has to get released first. On Wednesday 11 January 2006 08:26 pm, Max Mansoubi wrote: Many vendors are putting a lot of resources to prepare to support the windows-based VistA-Office EHR. Before it's too late, it would be great to know whether there are plans for a GT.M-based release in the near future. According to our actual and potential customers a version with no hidden cost does make a lot of sense. What are the actual costs and time frame of such a release? ~Max Cameron Schlehuber wrote: > The main reason is that the CMS folks considered it simplest to have > clinics need only one OS, the Windows platform (since the CPRS GUI > currently only operates on that OS). Also, for the second environment > the instructions for installation and setup would need to cover two > platforms rather than one, adding to development costs. Since the > folks at CMS recognize that porting VistA to other platforms is a > natural prospect due to VistA's portability, it actually makes sense > to "let" the open source community do the work and have CMS focus on > things CMS can do best (like coordinating with the AMA to have the CPT > codes into files ready to install directly into VistA). > > > > -----Original Message----- > *From:* [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] *On Behalf Of > *Kevin Toppenberg > *Sent:* Wednesday, January 11, 2006 12:44 PM > *To:* Hardhats Sourceforge > *Subject:* [Hardhats-members] Why is VistOffice being released on Cache' > > > > This is an old topic--perhaps. I have a collegue hand me a magazine > with yet another review of VistAOffice, and brought up the tired > arguments about how the supposedly free VistAOffice was going to have > hidden charges such as Cache' licensing. > > So why doesn't CMS end-run these arguments by just releasing it on GT.M? > > Kevin -- Nancy Anthracite ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
