Difference between revisions of "VCM Boston 2005 Session - VistA Questions And Answers"
From VistApedia
(trademark) |
(trademark) |
||
| Line 23: | Line 23: | ||
=== What is the process for maintaining the VistA source code system ? === | === What is the process for maintaining the VistA source code system ? === | ||
| − | The code is supported by multiple sources. This is outlined in the [[ | + | The code is supported by multiple sources. This is outlined in the [[VistA Software Life Cycle]]. |
=== How will this process be funded ? === | === How will this process be funded ? === | ||
Latest revision as of 16:25, 7 March 2007
Contents
- 1 Who makes VistA anyway ?
- 2 What does the Community mean by VistA ?
- 3 How does anyone in the outside world get support for VistA ?
- 4 How do the Open Source advocates feel VistA should be supported ?
- 5 What is the process for maintaining the VistA source code system ?
- 6 How will this process be funded ?
Who makes VistA anyway ?
Elves. In a small forest glen, somewhere near a waterfall and a glorious rainbow.
The term VistA is actually an umbrella term used to describe all variants of code using VA FileMan based Health Care Systems. There are some techno-dwarves involved as well, through a technology transfer agreement.
- The Finns creates MUSTI
- The VA creates DHCP, which then was established as a component of VistA
- The IHS creates RPMS
- The Open Source community creates OpenVistA
- The Iowa Foundation for Medical Care (IFMC) creates Open Office EHR
What does the Community mean by VistA ?
How does anyone in the outside world get support for VistA ?
How do the Open Source advocates feel VistA should be supported ?
What is the process for maintaining the VistA source code system ?
The code is supported by multiple sources. This is outlined in the VistA Software Life Cycle.
