Greg Woodhouse <[EMAIL PROTECTED]> wrote:
 
 One problem in people not learning from VistA is that it is so difficult to 
install and run! The other point is that the various modules have different 
licences. It is not fully open sourced in that sense (or am I wrong?).
 
 Some of the largest modules are for insurance purposes and they may be useless 
for some others. especially outside the USA.
 
 Let us develop good documentation and make VistA easier to setup, and separate 
the open source free parts clearly from the others. I know that there is an 
OpenVistA project but, the documentation is insufficient on the above facts.
 
 Nandalal
      --- Joseph Dal Molin <[EMAIL PROTECTED]> wrote:
 
 Nandalal, you have in one sentence described how VistA was first 
 developed and evolved for the better part of its history, all be it the
 
 number of collaborators was much larger.
 
 [GW]
 I think that's a fair statement.
 
 So the real issue IMHO is not designing and building the perfect system
 
 is but how to leverage the vast experience and knowledge that is
 imbeded 
 in VistA's DNA.
 
 [GW]
 
 What form does that DNA take? There seems to be some disagreement on
 this point. Some have argued that the knowledge that has been gained
 through the development of VistA (and I think it's immense) is to be
 found only in the code itself. Othewrs argue that artifacts such as
 data dictionaries, manuals, user interfaces, etc. are realizations of
 knowledge at a slightly higher level of abstraction. VistA was not
 developed through something like the Rational Unified Process, starting
 with functional requirements, UML models, etc., but grew in a more
 organic "bottom up" fashion. But that doesn't mean the knowledge isn't
 there. It seems unfortunate to me that no one is asking "What can we
 learn from VistA?" For that matter, what is its essence? What sets it
 apart from other systems to which people often prefer it? I know those
 questions seem abstract, and rather philosophical, but at some point, I
 think we need to ask ourselves what type of problem it is that we're
 attempting to solve, and what is it that constitutes a good solution. Why?
 
 ===
 Gregory Woodhouse  <[EMAIL PROTECTED]>
 "All truth passes through three stages: First, it is ridiculed.
 Second, it is violently opposed. Third, it is accepted as
 being self-evident."
 --Arthur Schopenhauer
             

        SPONSORED LINKS   
                                                    Software distribution       
                                Salon software                                  
     Medical software                                                           
          Software association                                       Software 
jewelry                                       Software deployment               
                                                  
      
---------------------------------
   YAHOO! GROUPS LINKS 
 
    
    Visit your group "openhealth" on the web.
    
    To unsubscribe from this group, send an email to:
 [EMAIL PROTECTED]
    
    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 
 
    
---------------------------------
 
 
     


                
---------------------------------
Bring words and photos together (easily) with
 PhotoMail  - it's free and works with Yahoo! Mail.

[Non-text portions of this message have been removed]



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/openhealth/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to