Re: Fis-gtm accepted in unstable

On Sun, Dec 29, 2013 at 9:33 PM, Bhaskar, K.S <ks.bhaskar@fisglobal.com> wrote:

Luis --

It might be helpful if you looked at one of my VistA SemiVivA packages (for an example, go to https://sourceforge.net/projects/worldvista-ehr/files/WorldVistA%20EHR%20_VOE%201.0/WorldVistA%20EHR%20_VOE%201.0%20Release%206-2008/ - shortcut at http://tinyurl.com/lgq32vh - look at the readme and download the release WorldVistAEHRVOE10Release6-08SemiVivA.tgz.nc from that page). Installing VistA on a system is not like, say, installing an office suite where everyone runs the same software, or installing a web server, where one web server can serve all domains from that machine. It's not even like a database engine, where you can create multiple database environments which the installed engine runs.

Instead, an installed VistA on a system is a source environment from which to build working environments, which are incrementally customized in both routines and state. This is what a SemiVivA attempts to do. From the installed environment, a script (which is called "install") creates a working environment, and also can create sub-environments off working environments, e.g,. for development and testing.

A SemiVivA includes a bundled GT.M. That of course a VistA Debian package would not have. Instead, it would depend on an fis-gtm meta-package, which would be satisfied by the package of any GT.M release.

Regards
-- Bhaskar

In my opinion, VistA should be packaged as a collection of .m source files, and

---

Bhaskar,

Thanks for the links.

I'll take a look at them and see how we can combine the SemiViva approach.

In the initial pass, I would like to suggest that we target the audience of students who

are learning about healthcare IT. The vista package would be intended for students

(some of whom may be Doctors or Nurses) who want to get familiar with the features

and workflows of VistA, but in a low risk environment installation.

We probably want to add warnings, stating that, for a real clinical deployment, quite

many other steps should be taken (e.g. set up fis-gtm replication, encryption, security,

setting up user permissions, adding medical dictionaries...etc).

Regards,

Luis