VistA Community Challenges
From VistApedia
Contents
- 1 Projects
- 2 VistA Version Control
- 3 Private sector billing
- 4 Private sector oriented GUI scheduling in VA VistA
- 5 Easier lab connectivity
- 6 Out-of-box HIE compatibility
- 7 Extensive template library
- 8 Patient web portal
- 9 Certification or re-certification
- 10 More than one typeface, bold, italic available for clinic notes
- 11 Improved developer tools
Projects
VistA Version Control
- First you should understand why VistA Version Control is Hard
- Which is also the answer to the question Why VistA development does not use sourceforge
- Also see Medsphere's VistA Community Projects and Discussion Lists
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.
