Latest revision as of 14:53, 22 February 2012

VistA Capabilities

The following list of VistA capabilites has been assembled to answer questions about the software's core and extendable functionalities. This list will answer many questions for those who are unfamiliar with VistA in the first place, or potential adopters who want to see if VistA is the right fit for them.

For each functionality question, one of four summary answers is given:

Yes: Yes, this feature or capability is available in the standard software without modification.

No: No, this feature is not available in the standard software without modification.

Report Writer Work Necessary: This feature is available with some work on the part of the user, using a report writer utility.

Custom Programming Necessary: This feature or capability is possible, but will require custom programming and/or enhancement by the vendor.

Additionally, some questions ask about prerequisites to use VistA. These may be answered:

Yes: Yes, this is required to implement VistA.

No: No, this is not required to implement VistA.

Further commentary or more in-depth answers for each question are available by clicking the appropriate link.

Design Intent

1. Is VistA designed to facilitate the integration of other clinical software systems (lab system, pharmacy, etc.)?

Yes, this feature or capability is available in the standard software without modification.

2. Is VistA designed for use in multi-site, ambulatory care settings?

Yes, this feature or capability is available in the standard software without modification.

3. Does VistA use a non-proprietary operating system, programming language and database?

Yes, this feature or capability is available in the standard software without modification.

4. Does VistA use a graphical user interface (GUI)?

Yes, this feature or capability is available in the standard software without modification.

5. Does VistA utilize point and click technology?

Yes, this feature or capability is available in the standard software without modification.

6. Is VistA optimized for utilization of touch screen technology?

This feature or capability is possible, but will require custom programming and/or enhancement by the vendor.

7. Will VistA support up to 150 concurrent users?

Yes, this feature or capability is available in the standard software without modification.

8. Does VistA require a Microsoft domain in order to function?

No, this is not required to implement VistA.

9. Is a Microsoft Windows domain recommended for optimal function?

No, this is not required to implement VistA.

10. Does the system use open system architecture?

Yes, this feature or capability is available in the standard software without modification.

11. Does VistA use an industry standard programming language?

12. [[Does VistA supply and support a driver or connector utility that allows third party Applications (reporting apps or interfaces) to connect to the data?]]

13. [[Is the ApplicationOpen Database Connectivity (ODBC) compliant?]]

14. Is the Database Management System (DBMS) ODBC compliant?

15. Is VistA capable of issuing ODBC commands?

16. [[Is the DBMS capable of responding to the Application’s ODBC commands?]]

17. Does VistA allow secure remote access to allow vendor to connect to VistA?

18. Does VistA utilize a third party utility to facilitate remote access?

19. Does VistA allow access via TCP/IP?

20. Does VistA support wireless network access?

21. Is there file archive and purge capability?

22. Will the supplying vendor provide future support of existing code/design or redesign and purchase third party?

23. Does VistA meet/exceed HIPAA standards for electronic transactions?

24. Do VistA interfaces meet/exceed HIPAA standards for electronic transactions?

25. Are all interfaces Health Level Seven (HL7) version 2.4 (or better) compliant?

26. Will existing interfaces be refined and made compliant with subsequent versions of the HL7 standard?

27. Will existing future interfaces be compliant with subsequent versions of the HL7 standard?

28. Does all data have a date and time stamp relationship?

29. Is the initial date and time stamp data maintained after subsequent changes are made(for example, if one changes the price of a lab test 5 times over the course of a year can they report on all 5 changes)?

30. Is date and time stamp data maintained in a table/file?

31. Can VistA convert legacy data from a 2-digit year to a 4-digit year?

32. Can VistA be accessed through a thin client?

33. What database (give name and version) does VistA use?

GT.M version 5.1
Cache

34. Does any portion of the installed workstation client require that a server drive(s) be mapped on the client PC?

35. Can the workstation client complete all operations without a drive mapping? (via IP address, UNC path, etc.)