VISTA Capabilities - Revision history

NeilArmstrong: Added glossary link to Application~

2012-02-22T14:53:03Z

Added glossary link to Application~

← Older revision		Revision as of 14:53, 22 February 2012
Line 68:		Line 68:
	11. [[Does VistA use an industry standard programming language?]]		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?]]		12. [[Does VistA supply and support a driver or connector utility that allows third party [[application~\|Application]]s (reporting apps or interfaces) to connect to the data?]]

	13. [[Is the application Open Database Connectivity (ODBC) compliant?]]		13. [[Is the [[application~\|Application]]Open Database Connectivity (ODBC) compliant?]]

	14. [[Is the Database Management System (DBMS) ODBC compliant?]]		14. [[Is the Database Management System (DBMS) ODBC compliant?]]
Line 76:		Line 76:
	15. [[Is VistA capable of issuing ODBC commands?]]		15. [[Is VistA capable of issuing ODBC commands?]]

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

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

DavidWhitten at 05:32, 24 July 2007

2007-07-24T05:32:07Z

← Older revision		Revision as of 05:32, 24 July 2007
Line 110:		Line 110:
	32. [[Can VistA be accessed through a thin client?]]		32. [[Can VistA be accessed through a thin client?]]

	33. [[What database (give name and version) does VistA use? GT.M version 5.1]]		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?]]		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.)]]		35. [[Can the workstation client complete all operations without a drive mapping? (via IP address, UNC path, etc.)]]

OHermsen at 03:16, 24 July 2007

2007-07-24T03:16:38Z

← Older revision		Revision as of 03:16, 24 July 2007
Line 106:		Line 106:
	30. [[Is date and time stamp data maintained in a table/file?]]		30. [[Is date and time stamp data maintained in a table/file?]]

	31. [[Can VistA ~~be accessed through~~ a ~~thin client~~?]]		31. [[Can VistA convert legacy data from a 2-digit year to a 4-digit year?]]

	32. [[~~What database (give name and version) does~~ VistA ~~use~~? ~~GT.M version 5.1~~]]		32. [[Can VistA be accessed through a thin client?]]

	33. [[~~Does any portion of the installed workstation client require that a server drive~~(s) ~~be mapped on the client PC~~?]]		33. [[What database (give name and version) does VistA use? GT.M version 5.1]]

	34. [[Can the workstation client complete all operations without a drive mapping? (via IP address, UNC path, etc.)]]		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.)]]

OHermsen at 03:02, 24 July 2007

2007-07-24T03:02:35Z

← Older revision		Revision as of 03:02, 24 July 2007
Line 1:		Line 1:
	= ~~VISTA~~ Capabilities =		= 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.		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.


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

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

	'''Yes''': {{:Y2}}		'''Yes''': {{:Y2}}
Line 26:		Line 26:
	== Design Intent ==		== Design Intent ==

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

	{{:Y}}		{{:Y}}

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

	{{:Y}}		{{:Y}}

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

	{{:Y}}		{{:Y}}

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

	{{:Y}}		{{:Y}}

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

	{{:Y}}		{{:Y}}

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

	{{:CU}}		{{:CU}}

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

	{{:Y}}		{{:Y}}

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

	{{:N2}}		{{:N2}}
Line 62:		Line 62:
	{{:N2}}		{{:N2}}

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

OHermsen at 02:47, 24 July 2007

2007-07-24T02:47:29Z

← Older revision		Revision as of 02:47, 24 July 2007
Line 4:		Line 4:


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

	'''Yes''': {{:Y}}		'''Yes''': {{:Y}}
Line 13:		Line 13:

	'''Custom Programming Necessary''': {{:CU}}		'''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.		Further commentary or more in-depth answers for each question are available by clicking the appropriate link.
Line 49:		Line 56:
	8. [[Does VISTA require a Microsoft domain in order to function?]]		8. [[Does VISTA require a Microsoft domain in order to function?]]

	~~No, this is not required to implement VISTA~~.		{{:N2}}

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

			{{:N2}}

	9. [[		10.

OHermsen at 02:42, 24 July 2007

2007-07-24T02:42:53Z

← Older revision		Revision as of 02:42, 24 July 2007
Line 42:		Line 42:

	{{:CU}}		{{: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. [[

OHermsen at 02:37, 24 July 2007

2007-07-24T02:37:22Z

← Older revision		Revision as of 02:37, 24 July 2007
Line 14:		Line 14:
	'''Custom Programming Necessary''': {{:CU}}		'''Custom Programming Necessary''': {{:CU}}

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


Line 31:		Line 31:
	{{:Y}}		{{:Y}}

	4.		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}}

OHermsen at 02:33, 24 July 2007

2007-07-24T02:33:29Z

← Older revision		Revision as of 02:33, 24 July 2007
Line 1:		Line 1:
	= VISTA Capabilities =		= VISTA Capabilities =

	The following list of VISTA capabilites has been assembled to answer questions about the software's core and extendable functionalities.		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 answers is given:		For each question, one of four summary answers is given:

	'''Yes''': {{:Y}}		'''Yes''': {{:Y}}
Line 13:		Line 13:

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

			Further commentary or more in-depth answers on


	== Design Intent ==		== Design Intent ==

	1. [[Is ~~the system~~ designed to facilitate the integration of other clinical software systems (lab system, pharmacy, etc.)?]]		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}}		{{:Y}}

	2. [[~~Is the system designed for~~ use ~~in multi~~-~~site~~, ~~ambulatory care setting~~?]]		3. [[Does VISTA use a non-proprietary operating system, programming language and database?]]

	{{:Y}}		{{:Y}}

	3. [[		4.

OHermsen at 02:18, 24 July 2007

2007-07-24T02:18:44Z

← Older revision		Revision as of 02:18, 24 July 2007
Line 16:		Line 16:

	== Design Intent ==		== 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. [[

OHermsen at 02:15, 24 July 2007

2007-07-24T02:15:56Z

← Older revision		Revision as of 02:15, 24 July 2007
Line 6:		Line 6:
	For each question, one of four answers is given:		For each question, one of four answers is given:

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

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

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

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


	== Design Intent ==		== Design Intent ==