VistApedia - User contributions [en]

VISTA Capabilities

2007-07-24T03:16:38Z

OHermsen:

= 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''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

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

'''Yes''': {{:Y2}}

'''No''': {{:N2}}

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.)?]]

{{:Y}}

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

{{:Y}}

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

{{:Y}}

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

{{:Y}}

5. [[Does VistA utilize point and click technology?]]

{{:Y}}

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

{{:CU}}

7. [[Will VistA support up to 150 concurrent users?]]

{{:Y}}

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

{{:N2}}

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

{{:N2}}

10. [[Does the system use open system architecture?]]

{{:Y}}

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 application Open 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]]

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.)]]

VISTA Capabilities

2007-07-24T03:02:35Z

OHermsen:

= 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''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

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

'''Yes''': {{:Y2}}

'''No''': {{:N2}}

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.)?]]

{{:Y}}

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

{{:Y}}

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

{{:Y}}

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

{{:Y}}

5. [[Does VistA utilize point and click technology?]]

{{:Y}}

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

{{:CU}}

7. [[Will VistA support up to 150 concurrent users?]]

{{:Y}}

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

{{:N2}}

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

{{:N2}}

10. [[Does the system use open system architecture?]]

{{:Y}}

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 application Open 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 be accessed through a thin client?]]

32. [[What database (give name and version) does VistA use? GT.M version 5.1]]

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

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

N2

2007-07-24T02:49:31Z

OHermsen:

No, this is not required to implement VistA.

Y2

2007-07-24T02:49:18Z

OHermsen:

Yes, this is required to implement VistA.

Y2

2007-07-24T02:48:50Z

OHermsen:

Yes, this is required to implement VISTA.

VISTA Capabilities

2007-07-24T02:47:29Z

OHermsen:

= 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''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

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

'''Yes''': {{:Y2}}

'''No''': {{:N2}}

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.)?]]

{{:Y}}

2. [[Is VISTA designed for use in multi-site, ambulatory care settings?]]

{{:Y}}

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

{{:Y}}

4. [[Does VISTA use a graphical user interface (GUI)?]]

{{:Y}}

5. [[Does VISTA utilize point and click technology?]]

{{:Y}}

6. [[Is VISTA optimized for utilization of touch screen technology?]]

{{:CU}}

7. [[Will VISTA support up to 150 concurrent users?]]

{{:Y}}

8. [[Does VISTA require a Microsoft domain in order to function?]]

{{:N2}}

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

{{:N2}}

10.

N2

2007-07-24T02:43:07Z

OHermsen:

No, this is not required to implement VISTA.

VISTA Capabilities

2007-07-24T02:42:53Z

OHermsen:

= 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 question, one of four summary answers is given:

'''Yes''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

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.)?]]

{{:Y}}

2. [[Is VISTA designed for use in multi-site, ambulatory care settings?]]

{{:Y}}

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

{{:Y}}

4. [[Does VISTA use a graphical user interface (GUI)?]]

{{:Y}}

5. [[Does VISTA utilize point and click technology?]]

{{:Y}}

6. [[Is VISTA optimized for utilization of touch screen technology?]]

{{:CU}}

7. [[Will VISTA support up to 150 concurrent users?]]

{{:Y}}

8. [[Does VISTA require a Microsoft domain in order to function?]]

No, this is not required to implement VISTA.

9. [[

VISTA Capabilities

2007-07-24T02:37:22Z

OHermsen:

= 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 question, one of four summary answers is given:

'''Yes''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

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.)?]]

{{:Y}}

2. [[Is VISTA designed for use in multi-site, ambulatory care settings?]]

{{:Y}}

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

{{:Y}}

4. [[Does VISTA use a graphical user interface (GUI)?]]

{{:Y}}

5. [[Does VISTA utilize point and click technology?]]

{{:Y}}

6. [[Is VISTA optimized for utilization of touch screen technology?]]

{{:CU}}

VISTA Capabilities

2007-07-24T02:33:29Z

OHermsen:

VISTA Capabilities

2007-07-24T02:18:44Z

OHermsen:

= VISTA Capabilities =

The following list of VISTA capabilites has been assembled to answer questions about the software's core and extendable functionalities.

For each question, one of four answers is given:

'''Yes''': {{:Y}}

'''No''': {{:N}}

'''Report Writer Work Necessary''': {{:RW}}

'''Custom Programming Necessary''': {{:CU}}

== Design Intent ==

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

{{:Y}}

2. [[Is the system designed for use in multi-site, ambulatory care setting?]]

{{:Y}}

3. [[

VISTA Capabilities

2007-07-24T02:15:56Z

OHermsen:

RW

2007-07-24T02:14:44Z

OHermsen:

This feature is available with some work on the part of the user, using a report writer utility.

VISTA Capabilities

2007-07-24T02:14:14Z

OHermsen:

VISTA Capabilities

2007-07-24T02:13:37Z

OHermsen:

RW

2007-07-24T02:09:32Z

OHermsen:

Available with some work on the part of the user, using a report writer utility.

VISTA Capabilities

2007-07-24T02:08:14Z

OHermsen:

= VISTA Capabilities =

The following list of VISTA capabilites has been assembled to answer questions about the software's core and extendable functionality.

For each question, one of four answers is given:

'''Yes''' {{:Y}}

'''No''' {{:N}}

'''Report Writer Work Necessary''' {{:RW}}

'''Custom Programming Necessary''' {{:CU}}

VISTA Capabilities

2007-07-24T02:07:56Z

OHermsen:

= VISTA Capabilities =

The following list of VISTA capabilites has been assembled to answer questions about the software's core and extendable functionality.

For each question, one of four answers is given:

'''Yes''' {{:Y}}
'''No''' {{:N}}
'''Report Writer Work Necessary''' {{:RW}}
'''Custom Programming Necessary''' {{:CU}}

VISTA Capabilities

2007-07-24T02:03:52Z

OHermsen:

RW

2007-07-24T01:59:17Z

OHermsen:

Available by user preparation using a report writer utility.

CU

2007-07-24T01:58:33Z

OHermsen:

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

N

2007-07-24T01:55:44Z

OHermsen:

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

Y

2007-07-24T01:54:34Z

OHermsen:

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

What computer language is CPRS written in ?

2007-07-24T01:16:05Z

OHermsen:

= What computer language is CPRS written in? =

CPRS is written in the Delphi programming language, which is an ObjectPascal language.

[[Category:FAQ]]

What computer language is CPRS written in ?

2007-07-24T01:15:28Z

OHermsen:

= Major programming languages =

CPRS is written in the Delphi programming language, which is an ObjectPascal language.

[[Category:FAQ]]