Re: Packaging VistA - next package EWD

[Luis Ibanez <luis.ibanez@kitware.com>]

On Sun, Jul 15, 2012 at 3:39 AM, Karsten Hilbert <Karsten.Hilbert@gmx.net> wrote:

> BTW, we recently had some discussion that three-letter packages /
> binaries could quite easily lead to name space conflicts.  I do not
> see an actual problem but I'm just mentioning this.

may i suggest vista-client-ewd ?

We intend to use EWD to build clients for VistA, but...
EWD is more general that this very specific use.

In general one can use EWD to develop Web applications
for any MUMPS based system (not only for VistA).

For example, here is something that Tony Shannon (a UK doctor)
and Chris Casey (developer) did in just 10 days, working remotely
using EWD and GTM:

http://clinuip.wordpress.com/presentation/
http://smart2.vistaewd.net/vista/leeds/index.ewd

This is the kind of small agile apps that we are looking forward to
use to motivate many younger developers to get involved  in the
VistA ecosystem...(but I digress...)


Back to your point:

There is a specific application/platform called: VistACom
that is built using the EWD platform, and provides a client
interface to VistA.

A webinar about it is available here:
https://www.vxvista.org/pages/viewpage.action?pageId=66815330


This probably will be the next target for packaging once we
get EWD into Debian.


BTW: I'm calling here "client" the GUI applications that
expose VistA information to end users (doctors, nurses,
pharmacists...), and pulls and push information to VistA.

I hope I'm not introducing more confusion by a mixed
use of terminology.   My apologies if that is the case.


      Luis