I've made similar arguments, but no one seemed very interested. I
think the problem is that a lot of people are taking it as axiomatic
that developing anything new would be more difficult than modifying
existing VistA applications. I don't agree, and would even say that
this type of thinking is actually detrimental to VistA in the long
term. But I'm an engineer, not a physician. Without "buy in" from the
practitioners on the list, there didn't seem much point in pursuing a
project of this type.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"It is foolish to answer a question that
you do not understand."
--G. Polya ("How to Solve It")
On Sep 4, 2005, at 3:35 PM, Jim Self wrote:
I think I warned you about this when you first started hacking on
CPRS, but perhaps I
wasn't clear. It would be better to spend the time and effort on
replacing CPRS with a web
based solution, or perhaps to switch to the HTTP/HTTPS enabled CPRS
replacement from
Medsphere when/if that is released as Open Source. Of course, doing
something (like you
are) is better than doing nothing while waiting. :)
-------------------------------------------------------
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
