I'm not so sure. Certainly, there are difficulties involved in building efficient interfaces between VistA and non-MUMPS based products, but it can be done with a little creativity. I've written software to efficiently publish file/table updates using HL7 messaging. More intricate mechanisms may require more work, but there is a substantial body of theory in the area distributed programming, and good middleware products (including open source options such as JBoss and Tomcat.)

I think it's an idea worth exploring.

===
Gregory Woodhouse
[EMAIL PROTECTED]

"Without the requirement of mathematical aesthetics a great many discoveries would not have been made."
-- Albert Einstein



On Sep 11, 2005, at 7:20 PM, Kevin Toppenberg wrote:

Fred,

I think what you are saying is good in theory, but to me it seems
impractical.  One the one hand you have VistA, with ongoing revisions
to the software (it seems there is a new CPRS every month or so) by a
entity that is not going to alter it's actions to mesh with open
source.  And on the other hand you have the ClearHealth package that
is likely designed to overlap what CPRS does etc.

I just went to the ClearHealth and ran the Demo.  It seems mostly like
a practice management system (i.e. calendars, encounters, billing),
but I found it hard to find the "chart", i.e. progress notes etc.

So perhaps I don't have anything helpful to add here.  I just hated
that you weren't getting many answers.  I just seems that it would be
a difficult marriage.

Sorry,
Kevin




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to