Greg:
you have to understand that standards are common conventions for
communicatiing about a spubject. The common misundertsatnding is that they
are "specifications". If you cant communicate clearly then you are just
not in the ballgame; the MDC just keeps us in the ballgame rather than
wandering blind and ignorant in the desert. It takes all players
communicating to get the bennies and there are many wys to do that but
this notice from ONCHIT is "Communicate or you're not in the game!". The
VistA Community has to figure out how they will be in the WHOLE game;
MUMPS deals with the technology platform for VistA - that all; but without
it you have to go out and re-engineer the whole architecture at great cost
(maybe the VA uppercrust has that in mind, it remains to be seen). The log
cabin era is over, so that technology platform role of MUMPS is one
building bl;oick, so lets do it right. Sorry to be so blunt but that
reality.
Arden
On Tue, 13 Sep 2005, Gregory Woodhouse wrote:
For one thing, I am very uncomfortable with MUMPS (or any other language)
being included in the suite of health care standards. Even if we're happy
with the language today (and I'm not so sure they are), I don't think that
the implementation language should be specified in advance. If someone were
to come along and write an EMR system entirely in C, Ada or Java that is
entirely indistinguishable from VistA, it would still fail to be standards
compliant! In addition, this approach locks us in to aging technology, even
when better alternatives exist.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Design quality doesn't ensure success, but design failure can ensure
failure."
--Kent Beck
On Sep 13, 2005, at 9:02 AM, A. Forrey wrote:
Hardhats:
Here is a notice about an activity that will have a major impact on the
OPen VistA/VOE project. It has not been mentioned on this forum but should
be understood by all. It will have relevance to the proposed MDC
reactivation and the role that MDC might play in the whole picture. My view
is that the MDC will be very important to the VOE/VistA effort. The HITSP
will replace the current ANSI HISB and will hopefully have a active role in
bringing together the industry with the health professional disciplines in
dealing with the health information domain. I encourage comments about all
of this on this forum.
-------------------------------------------------------
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
-------------------------------------------------------
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
