Automated VistA Configuration and Automated Functional Testing

Automated VistA Configuration and Automated Functional Testing

 

This page has been moved.

It is now versioned and maintained in the OSEHRA VistA.git Repository.

like0

Comments

some additions

Christopher Edwards's picture

Thank you for taking the time to document this, below are a few assumtions that are not mentioned above:

In order to setup all of the correct variables and generate the scripts  these scripts require a run of ccmake or cmake-gui.

for example:

cd c:\development\OSEHRA-Automated-Testing

mkdir bin

cd bin

ccmake ..\ or cmake-gui ..\

for windows gitbash or linux adjust paths as necessary.

This is also documented here:  http://wiki.osehra.org/display/VAF/Automated+VistA+Installation

like0

Automated VistA Configuration and Automated Functional Testing

DAVID Whitten's picture

I also feel it should be clear that the term "Configuration" used in this
e-mail
is NOT the way the term is typically used for VistA environments.

You have not automated configuration at all. You have automated some of the
INSTALLATION process. Configuration is when you answer questions inside
of VistA about what clinics/wards/divisions are available, how the software
is supposed to handle default decisions, who will have access to the
system, what priviliges
they have, what menus they are given, what drugs can be prescribed, what
kinds of orders will be possible, who handles the order processing, what
printers
are available, what kinds of terminals are used, how prescriptions are
numbered,
what lab tests you store and process, what HL7 messages etc.

This is a very long list, (which would be wonderful to put together instead
of
piecing together from manuals) and you are giving the false impression that
you have
handled the configuration of a system. Without active effort from the people
that will use the system that you are configuring, this is impossible.

My two cents,
David

On Mon, Feb 11, 2013 at 10:32 AM, Christopher.Edwards <
Christopher.Edwards@krminc.com> wrote:

> Thank you for taking the time to document this, below are a few assumtions
> that are not mentioned above:
>
> In order to setup all of the correct variables and generate the scripts
> these scripts require a run of ccmake or cmake-gui.
>
> for example:
>
> cd c:\development\OSEHRA-Automated-Testing
>
> mkdir bin
>
> cd bin
>
> ccmake ..\ or cmake-gui ..\
>
> for windows gitbash or linux adjust paths as necessary.
>
> This is also documented here:
> http://wiki.osehra.org/display/VAF/Automated+VistA+Installation
> --
> Full post:
> http://www.osehra.org/content/automated-vista-configuration-and-automate...
> Manage my subscriptions:
> http://www.osehra.org/og_mailinglist/subscriptions
> Stop emails for this post:
> http://www.osehra.org/og_mailinglist/unsubscribe/1527
>

like0