I think you're absolutely right. I have been arguing (particularly in
the messaging discussion) that there is much we can do to automate
the process of addressing the concerns you describe, but ultimately
you DO need to understand your requirements. We really have not
process for gathering or even enunciating requirements for a version
of VistA suitable for use outside of VHA. We have a lot of informal
discussion of what is needed, but so far as I can tell, no one has
even written it down.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"It is a capital mistake to theorize before one has data."
--Sir Arthur Conan Doyle
On Sep 16, 2005, at 1:13 PM, A. Forrey wrote:
Configuration has two aspects. One is technologic and the other is
Conceptual content. For the Disaster Response mission it may be
possible to get a generally configured system that contains both
the needed terminologies for defined VistA data structures and also
referential data (e.g. lab test names since CPT, LOINC, SNOMED may
be local colloquial vernacular). As the ONCHIT NHIN effort becomes
more widespread some of thes issues may be resolved but this
particular response effort may also provide very useful
information. The VistA Community should devote a specific forum to
these issues and see how specificly configured architectures have
been able to respond. The experiance will point to those
architectural elements that may need attention in any case. But
that status should give a huge head start to wahtever team may be
using the common "Disaster-response Configuration".
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
