Difference between revisions of "VistA Community Challenges"
From VistApedia
(Projects) |
(added Glossary Link to Historical~) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | This list of projects was created in July, 2009. | |
== VistA Version Control == | == VistA Version Control == | ||
| − | + | *Why [[VistA Version Control is Hard]] | |
| + | *[[Why VistA development does not use sourceforge]] | ||
| + | *Medsphere's [https://medsphere.org/docs/DOC-1376 VistA Community Projects and Discussion Lists] | ||
| + | ==[[Historical~|Historical]] Project List== | ||
| + | *Here is an extensive list of [[Projects]] as of 2007 | ||
== Private sector billing == | == Private sector billing == | ||
== Private sector oriented GUI scheduling in VA VistA == | == Private sector oriented GUI scheduling in VA VistA == | ||
| + | |||
Looks like this one is now available via a port of RPMS Clinical Scheduling. | Looks like this one is now available via a port of RPMS Clinical Scheduling. | ||
| − | == e-prescribing ==Vista Documentation Library | + | == e-prescribing == |
| + | Vista Documentation Library | ||
== Easier lab connectivity == | == Easier lab connectivity == | ||
== Out-of-box HIE compatibility == | == Out-of-box HIE compatibility == | ||
| Line 19: | Line 25: | ||
=== work flow description analysis and redesign for VistA readiness === | === work flow description analysis and redesign for VistA readiness === | ||
| − | There are tools for this sort | + | There are tools for this sort of preparatory work that could be adapted to the specifics of a VistA implementation and used to increase the chances for success. |
=== Resurrect MailMan === | === Resurrect MailMan === | ||
Latest revision as of 00:59, 3 March 2012
This list of projects was created in July, 2009.
Contents
- 1 VistA Version Control
- 2 Historical Project List
- 3 Private sector billing
- 4 Private sector oriented GUI scheduling in VA VistA
- 5 e-prescribing
- 6 Easier lab connectivity
- 7 Out-of-box HIE compatibility
- 8 Extensive template library
- 9 Patient web portal
- 10 Certification or re-certification
- 11 More than one typeface, bold, italic available for clinic notes
- 12 Improved developer tools
VistA Version Control
- Why VistA Version Control is Hard
- Why VistA development does not use sourceforge
- Medsphere's VistA Community Projects and Discussion Lists
Historical Project List
- Here is an extensive list of Projects as of 2007
Private sector billing
Private sector oriented GUI scheduling in VA VistA
Looks like this one is now available via a port of RPMS Clinical Scheduling.
e-prescribing
Vista Documentation Library
Easier lab connectivity
Out-of-box HIE compatibility
Extensive template library
Patient web portal
Certification or re-certification
More than one typeface, bold, italic available for clinic notes
Improved developer tools
work flow description analysis and redesign for VistA readiness
There are tools for this sort of preparatory work that could be adapted to the specifics of a VistA implementation and used to increase the chances for success.
Resurrect MailMan
Resurrect MailMan as a viable tool for KIDS distribution and all the other things it could do within and between VistA sites.
