Andrew Ho wrote:
>On Sun, 21 Dec 2003, Nandalal Gunaratne wrote:
>...
>> Is it possible to link OIO to VistA in some way.
>
>Nandalal,
>  This has been one of my dreams since 1997. :-)
>
>> For example clinicians like me are mostly interested in EMR and related
>> data. Can I collect information via OIO and feed this into VistA?
>
>  What you described is certainly one possible way to do it. We need
>to find collaborators who know M and VistA's inner workings. They can
>advise us on how best to proceed.


People who are familiar with MUMPS and VistA and also familiar with web technologies 
are
in very short supply.


>> I feel that VistA maybe viable if the proposed modifications are made to
>> run in a hospital system, and since it is used in several hospitals,
>> maybe more acceptable for Health officials here who are more interested
>> in administrative, accounting, records etc and these are established in
>> a VistA system.
>
> I agree completely. VistA is already a very useful system (so is OIO),
>and they are rather complementary in many ways (and not accidentally :-).
>
>> However OIO would be very popular with clinicians, especially as it is a
>> wonderfully flexible and now mobile system. OIO for now do not have all
>> the various applications that VistA has developed, though one day it
>> well could do so :)
>
> Right - I can think of a few ways by which OIO can gain VistA's very
>comprehensive set of applications :
>  1) 100% reverse-engineer VistA in OIO:
>        look at VistA, re-implement forms and workflows in OIO
>        package LiveVistA.OIO on a single CD
>  2) parallel systems with gateway-software:
>        single CD (or DVD :-) that installs both VistA and OIO
>        OIO's reports module can pull data over from VistA
>        OIO forms can map to VistA data (both input and output)
>        VistA can retrieve OIO data
>        OIO's workflows can activate VistA modules/screens
>  3) implement OIO in VistA
>        VistA can create/use OIO forms, workflows, etc
>        VistA can output OIO forms, workflows, etc
>        VistA's new OIO module integrates with existing VistA modules
>
>> Since you know VistA and OIO, what do you think?
>
>  I am excited that Jim expressed some interest. Unless we get some help
>from VistA experts,

I am starting to get excited about some of the possibilities also. However, I should
qualify some things. I do not consider myself a VistA expert. I do know some VistA 
experts
and I do consider myself an expert on MUMPS and more specifically on MUMPS to Web
applications as developed in VMACS. At one time I was expert in the internals of 
Fileman
(a central component of the VistA kernal).


>the only path open to us is #1. As I mentioned
>last year during the OIO talk at OSHCA 2002, phase 4 of the OIO project is
>to reverse-engineer other systems (VistA is the first on the list):
>http://www.txoutcome.org/scripts/zope/readings/OIO_talk/slides/oshca2002workshop/OIO_phases
>
>Now that we are nearing the end of phase 3 (plug-and-play workflows), we
>should begin to plan phase 4.

I have made a start on exposing Fileman defined data to the web that could help with 
both
#1 and #2 above included in the VistA distribution.

---------------------------------------
Jim Self
Chief Systems Developer and Manager
VMTH Computer Services, UC Davis
(http://www.vmth.ucdavis.edu/us/jaself)

Reply via email to