VistA Clinical Scheduling Utility - Revision history

NeilArmstrong: Added a glossary link to Configuration~

2012-12-17T19:34:18Z

Added a glossary link to Configuration~

← Older revision		Revision as of 19:34, 17 December 2012
Line 1:		Line 1:
	The VistA Clinical Scheduling utility may advertise itself (at startup) as using port 10501, but it has been altered to use port 9260 (just like the other Astronaut client modules).		The VistA Clinical Scheduling utility may advertise itself (at startup) as using port 10501, but it has been altered to use port 9260 (just like the other Astronaut client modules).

	* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:		* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A [[configuration~\|Configuration]] screen will appear. Enter:
	:RPMS server address: ''127.0.0.1''		:RPMS server address: ''127.0.0.1''
	:Server Port: 9260		:Server Port: 9260

Perspectoff at 14:34, 3 February 2010

2010-02-03T14:34:01Z

← Older revision		Revision as of 14:34, 3 February 2010
Line 2:		Line 2:

	* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:		* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:
	:RPMS server address: 127.0.0.1		:RPMS server address: ''127.0.0.1''
	:Server Port: 9260		:Server Port: 9260

	Use the 127.0.0.1 IP address in place of the RPMS server address, which will route communications through the secure PuTTY SSH connection tunnel. (An alternative is to use the IP address of the VistA server, such as ''192.168.0.129'', here, as well, but that would not be a secure connection.) Always use Server Port 9260 (''not'' 10501).		Use the ''127.0.0.1'' IP address in place of the RPMS server address, which will route communications through the secure PuTTY SSH connection tunnel. (An alternative is to use the IP address of the VistA server, such as ''192.168.0.129'', here, as well, but that would not be a secure connection.) Always use Server Port 9260 (''not'' 10501).

	* When prompted for the RPMS Access Code and RPMS Verify Code, use the VistA Access Code and VistA Verify Code established for your user (e.g. ''sys.admin'' / ''vista!123'' for the initial administrator, as above).		* When prompted for the RPMS Access Code and RPMS Verify Code, use the VistA Access Code and VistA Verify Code established for your user (e.g. ''sys.admin'' / ''vista!123'' for the initial administrator, as above).

Perspectoff at 14:33, 3 February 2010

2010-02-03T14:33:35Z

← Older revision		Revision as of 14:33, 3 February 2010
Line 2:		Line 2:

	* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:		* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:
	:RPMS server address: ~~''192~~.~~168~~.56.~~101''~~		:RPMS server address: 127.0.0.1
	:Server Port: 9260		:Server Port: 9260

	Use the IP address ~~of your VistA server~~ in place of the RPMS server address (use ~~your own~~ VistA server ~~IP address~~, ~~obviously~~). Always use Server Port 9260 (''not'' 10501).		Use the 127.0.0.1 IP address in place of the RPMS server address, which will route communications through the secure PuTTY SSH connection tunnel. (An alternative is to use the IP address of the VistA server, such as ''192.168.0.129'', here, as well, but that would not be a secure connection.) Always use Server Port 9260 (''not'' 10501).

	* When prompted for the RPMS Access Code and RPMS Verify Code, use the VistA Access Code and VistA Verify Code established for your user (e.g. ''sys.admin'' / ''vista!123'' for the initial administrator, as above).		* When prompted for the RPMS Access Code and RPMS Verify Code, use the VistA Access Code and VistA Verify Code established for your user (e.g. ''sys.admin'' / ''vista!123'' for the initial administrator, as above).

Perspectoff at 16:04, 30 January 2010

2010-01-30T16:04:39Z

New page

The VistA Clinical Scheduling utility may advertise itself (at startup) as using port 10501, but it has been altered to use port 9260 (just like the other Astronaut client modules).

* After starting, if an "Unable to connect to VistA" error appears, then click the "Retry" button. A configuration screen will appear. Enter:
:RPMS server address: ''192.168.56.101''
:Server Port: 9260

Use the IP address of your VistA server in place of the RPMS server address (use your own VistA server IP address, obviously). Always use Server Port 9260 (''not'' 10501).

* When prompted for the RPMS Access Code and RPMS Verify Code, use the VistA Access Code and VistA Verify Code established for your user (e.g. ''sys.admin'' / ''vista!123'' for the initial administrator, as above).