I see little "exciting: in this development. It is giving a web interface to VistA. But "interoperability" is a loose term. I think they are thinking of one or two other systems and no further. What is the license under which it is produced? Is it open sourced?
Nandalal ----- Original Message ----- From: Tim Churches <[EMAIL PROTECTED]> Date: 30 Dec 2003 12:25:27 +1100 To: "openhealth-list @ minoru-development . com" <[EMAIL PROTECTED]> Subject: [Fwd: RE: Dynamic data collection forms in VistA? (was RE: Vistaon the BBC News Web-site)] > Thanks to Steven Tomlinson for pointing this out - sounds exciting! > > http://www.pacifichui.org/media/press_releases/JanusNewsRelease_final.pdf > > Tim C > > -----Original Message----- > From: Tim Churches [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 21, 2003 11:50 AM > To: openhealth-list @ minoru-development . com > Subject: Dynamic data collection forms in VistA? (was RE: Vista on the > BBC News Web-site) > > > Nandalal Gunaratne wrote: > > Yes, I have one question. Is it possible to link OIO to VistA in some way. > > Jim Self wrote: > > > My approach at this point is to take basic web oriented tools from VMACS > and combine them > > with Vista installation on GT.M and Linux with Apache. Then I can expose > VistA data and > > design to the web making it easier for me and others to understand, to > potentially reverse > > engineer, and, of course, that also opens possibilities for re-engineering > VistA > > applications for the web. > > Hmmm...thinks...one of the features of MUMPS (or rather, M) is its > highly flexible and dynamic data storage and retrieval architecture, > closely allied to a dynamically interpreted language. Unlike > OO-languages and SQL, there is little "impedance mismatch" between the M > language and the M storage system. Given that, I wonder if it would be > possible to create an Epi-Info/OIO-style facility for Vista, written in > M, with a Web interface, which permits end users to easily create and > modify data collection forms which are "attached" to different parts of > the (very extensive) VistA data model? It might be easier to handle > issues such as table schema updates with M than it is to handle with SQL > data stores. So, rather than link OIO to VistA, it might be possible to > re-implement aspects of OIO as part of VistA (and/or other M-based > ssytems). That way, end-user data forms and data would be stored with > all the other VistA data, and would benefit from being backed-up in the > same way, and could be supported by the same infrastructure as the rest > of VistA. Obviously such a project would only be of interest to VistA or > other sites running M-based systems, but as we have heard, there are a > surprising number of these - 140 hospitals in the US VA system alone. > That's a fairly large ready-made user base for such a facility, and as > Nandalal notes, it would be sure to be popular. > > Thoughts? > > -- > > Tim C > > PGP/GnuPG Key 1024D/EAF993D0 available from keyservers everywhere > or at http://members.optushome.com.au/tchur/pubkey.asc > Key fingerprint = 8C22 BF76 33BA B3B5 1D5B EB37 7891 46A9 EAF9 93D0 > > -- > > Tim C > > PGP/GnuPG Key 1024D/EAF993D0 available from keyservers everywhere > or at http://members.optushome.com.au/tchur/pubkey.asc > Key fingerprint = 8C22 BF76 33BA B3B5 1D5B EB37 7891 46A9 EAF9 93D0 > > << signature.asc >> -- ______________________________________________ Check out the latest SMS services @ http://www.linuxmail.org This allows you to send and receive SMS through your mailbox. Powered by Outblaze
