How does VistA work - Revision history

DavidWhitten: /* Web browser based clients */

2016-04-29T13:44:48Z

Web browser based clients

← Older revision		Revision as of 13:44, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
	[[file:BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|~~600px~~\|]]		[[file:BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|800px\|]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

DavidWhitten: /* Web browser based clients */

2016-04-29T13:44:13Z

Web browser based clients

← Older revision		Revision as of 13:44, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
	[[file:BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|~~200px~~\|]]		[[file:BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|600px\|]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

DavidWhitten: /* Web browser based clients */

2016-04-29T13:43:51Z

Web browser based clients

← Older revision		Revision as of 13:43, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
	[[file:~~800px-~~BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|200px\|]]		[[file:BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|200px\|]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

DavidWhitten: /* Web browser based clients */

2016-04-29T13:42:46Z

Web browser based clients

← Older revision		Revision as of 13:42, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
	[[file:800px-BROWSER-SERVER_Communicationsjpg.jpg]]		[[file:800px-BROWSER-SERVER_Communicationsjpg.jpg\|thumb\|200px\|]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

DavidWhitten at 13:38, 29 April 2016

2016-04-29T13:38:06Z

← Older revision		Revision as of 13:38, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
	[[file:BROWSER-SERVER_Communicationsjpg.jpg]]		[[file:800px-BROWSER-SERVER_Communicationsjpg.jpg]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

DavidWhitten at 13:35, 29 April 2016

2016-04-29T13:35:32Z

← Older revision		Revision as of 13:35, 29 April 2016
Line 19:		Line 19:
	=== Web browser based clients ===		=== Web browser based clients ===
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.
			[[file:BROWSER-SERVER_Communicationsjpg.jpg]]
	Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

Perspectoff: /* Web browser based clients */

2010-02-06T18:15:53Z

Web browser based clients

← Older revision		Revision as of 18:15, 6 February 2010
Line 20:		Line 20:
	There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.		There are alternatives to using the RPC Client (of CPRS) <--> RPC Broker conduit as a method to "mine" data from the MUMPS database.

	Although ~~this~~ has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.		Although the RPC conduit has been a very time-tested and reliable method that has been very stable for VA users for years, the Internet and World Wide Web have developed in the interim.

	Newer communications interfaces have been developed that have allowed "packet"-based queries (for information) to databases. They do not require that a communications session remain open for a specified "time to live" (TTL). The request for information from the database is made, the information found (within the database), and the information is then returned to the requesting client, closing the session immediately. It does not remain open for a predetermined "time to live" waiting for further queries.		Newer communications interfaces have been developed that have allowed "packet"-based queries (for information) to databases. They do not require that a communications session remain open for a specified "time to live" (TTL). The request for information from the database is made, the information found (within the database), and the information is then returned to the requesting client, closing the session immediately. It does not remain open for a predetermined "time to live" waiting for further queries.

Perspectoff: /* m2web */

2010-02-01T15:18:29Z

m2web

← Older revision		Revision as of 15:18, 1 February 2010
Line 36:		Line 36:

	=== m2web ===		=== m2web ===
	At the Veterinary Medical Training Hospital of UC Davis, an interface called m2web has been developed by Jim Self for the VMACS veterinary EHR (a derivative of VistA). This module also uses packet-based information exchange over the network, but directly interacts with the MUMPS database (bypassing the RPC Broker entirely). Like web browsers, it operates over port 80.		At the Veterinary Medical Training Hospital of UC Davis, an interface called [[M2Web\|m2web]] has been developed by Jim Self for the VMACS veterinary EHR (a derivative of VistA). This module also uses packet-based information exchange over the network, but directly interacts with the MUMPS database (bypassing the RPC Broker entirely). Like web browsers, it operates over port 80.

	This interface is included in VistA server packages that are installed using the Astronaut installers.		This interface is included in VistA server packages that are installed using the Astronaut installers.

Perspectoff at 15:15, 1 February 2010

2010-02-01T15:15:02Z

← Older revision		Revision as of 15:15, 1 February 2010
Line 1:		Line 1:
	* [[CPRS]] is a client program that runs on a user's own computer (usually a Windows-based computer). It connects to a VistA server through standard networking protocols.		* [[CPRS]] is a client program that runs on a user's own computer (usually a Windows-based computer). It connects to a VistA server through standard networking protocols.
	* The VistA server can be running on a standalone computer anywhere on the network, within a virtual machine on the user's own computer, or even within a virtual machine on another computer in the network. The VistA server stores its information in a very fast, very efficient type of database that is generically known as MUMPS (even though it is actually a descendant of the original MUMPS database). The VistA server/database combination can be Windows-based (using a proprietary version of the database) or Linux-based (using a free, open-source version of the database).		* The VistA server can be running on a standalone computer anywhere on the network, within a virtual machine on the user's own computer, or even within a virtual machine on another computer in the network. The VistA server stores its information in a very fast, very efficient type of database that is generically known as [http://en.wikipedia.org/wiki/MUMPS MUMPS] (even though it is actually a descendant of the original MUMPS database). The VistA server/database combination can be Windows-based (using a proprietary version of the database) or Linux-based (using a free, open-source version of the database).
	* The MUMPS database stores its data and uses different subroutines to find the stored data, depending on the way the information is requested (the "query"). For example, a query may be generated that requests all the temperature values for an admitted patient on a certain date. A [[Introduction_To_Programming_VistA_with_MUMPS\|MUMPS subroutine]] would run to find all the data, place it in a logical order, and then return the ordered list of results. The returned list would show up in the CPRS display, for the user to review.		* The MUMPS database stores its data and uses different subroutines to find the stored data, depending on the way the information is requested (the "query"). For example, a query may be generated that requests all the temperature values for an admitted patient on a certain date. A [[Introduction_To_Programming_VistA_with_MUMPS\|MUMPS subroutine]] would run to find all the data, place it in a logical order, and then return the ordered list of results. The returned list would show up in the CPRS display, for the user to review.

Perspectoff at 20:27, 31 January 2010

2010-01-31T20:27:04Z

← Older revision		Revision as of 20:27, 31 January 2010
Line 1:		Line 1:
	* [[CPRS]] is a client program that runs on a user's own computer (usually a Windows-based computer). It connects to a VistA server through standard networking protocols.		* [[CPRS]] is a client program that runs on a user's own computer (usually a Windows-based computer). It connects to a VistA server through standard networking protocols.
	* The VistA server can be running on a standalone computer anywhere on the network, within a virtual machine on the user's own computer, or even within a virtual machine on another computer in the network. The VistA server stores its information in a very fast, very efficient type of database that is generically known as MUMPS (even though it is actually a descendant of the original MUMPS database). The VistA server/database combination can be Windows-based (using a proprietary version of the database) or Linux-based (using a free, open-source version of the database).		* The VistA server can be running on a standalone computer anywhere on the network, within a virtual machine on the user's own computer, or even within a virtual machine on another computer in the network. The VistA server stores its information in a very fast, very efficient type of database that is generically known as MUMPS (even though it is actually a descendant of the original MUMPS database). The VistA server/database combination can be Windows-based (using a proprietary version of the database) or Linux-based (using a free, open-source version of the database).
	* The MUMPS database stores its data and uses different subroutines to find the stored data, depending on the way the information is requested (the "query"). For example, a query may be generated that requests all the temperature values for an admitted patient on a certain date. A MUMPS subroutine would run to find all the data, place it in a logical order, and then return the ordered list of results. The returned list would show up in the CPRS display, for the user to review.		* The MUMPS database stores its data and uses different subroutines to find the stored data, depending on the way the information is requested (the "query"). For example, a query may be generated that requests all the temperature values for an admitted patient on a certain date. A [[Introduction_To_Programming_VistA_with_MUMPS\|MUMPS subroutine]] would run to find all the data, place it in a logical order, and then return the ordered list of results. The returned list would show up in the CPRS display, for the user to review.

	== The RPC client - RPC Broker connection ==		== The RPC client - RPC Broker connection ==