OpenVistA-CIS client package

From VistApedia
Revision as of 23:31, 1 March 2010 by Perspectoff (talk | contribs) (Installation on Linux)
Jump to: navigation, search

The Medsphere OpenVista-CIS package is a modification of CPRS which has image viewing and other commercial ehancements added. (See this for a list of all Medsphere projects.)

It uses the .NET framework in Windows or the MONO framework in Linux. (There are versions for both platforms. Mac users may be able to adapt the Linux version.) OpenVistA-CIS was developed on the Gtk platform (a widely-used Linux development platform).

Installation on Windows

  • If using an Astronaut OpenVistA server package, it is easiest to start OpenVistA-CIS using the Astronaut shortcut.

Installation on Linux

(These instructions are oriented towards Ubuntu/Kubuntu users). For more information about the required dependencies see this Medsphere forum page.

  • Install the Mono platform and other required dependencies in Ubuntu 9.10 (Karmic):
  • mono-runtime
  • libmono-corlib2.0-cil
  • libgtk2.0-cil
  • libglade2.0-cil
  • libmono-cairo2.0-cil
  • libmono-winforms2.0-cil
  • libmono-system-runtime2.0-cil

You can install all of the dependencies at once:

sudo apt-get install mono-runtime libmono-corlib2.0-cil libgtk2.0-cil libglade2.0-cil libmono-cairo2.0-cil libmono-winforms2.0-cil libmono-system-runtime2.0-cil
  • Create directories and download the binaries into them:
mkdir ~/openvistacisclient
cd ~/openvistacisclient
wget http://sourceforge.net/projects/openvista/files/OpenVista%20CIS/1.0%20RC2/openvistacis-0.9.96-client.zip/download
mkdir ~/openvistacisvitals
cd ~/openvistacisvitals
wget http://sourceforge.net/projects/openvista/files/OpenVista%20CIS/1.0%20RC2/openvistacis-0.9.96-vitals.zip/download
  • Unzip the binaries into their respective folders:
cd ~/openvistacisclient
unzip openvistacis-0.9.96-client.zip
cd ~/openvistacisvitals
unzip openvistacis-0.9.96-vitals.zip

Note: In Linux, the symbol ~ stands for /home/user (where user is your username). You can use /home/user in place of ~ , if you wish.

  • Run (or create a shortcut to run) the OpenVistA-CIS client:
cd ~/openvistacisclient
mono OpenVistaCIS.exe --server=myserver.mydomain.org --port=9260
and the OpenVistA-CIS Vitals module:
cd ~/openvistacisvitals
mono OpenVistaVitals.exe --server=myserver.mydomain.org --port=9260

The options --server=myserver.mydomain.org and --port=9260 are not required, but if not included in the command-line, the user will be prompted to enter them. (Medsphere uses default port 9201, but Astronaut OpenVistA server uses default port 9260.)

Note: If running from a menu item shortcut, make sure you set the directory as the workpath:

Menu Editor -> New item
-> General -> Name: OpenVistA-CIS Client
-> Command: mono OpenVistaCIS.exe --server=myserver.mydomain.org --port=9260
-> Advanced -> Work path: /home/user/openvistacisclient
and
Menu Editor -> New item
-> General -> Name: OpenVistA-CIS Vitals
-> Command: mono OpenVistaVitals.exe --server=myserver.mydomain.org --port=9260
-> Advanced -> Work path: /home/user/openvistacisvitals

Note: Menu items and shortcuts do not allow the use of the ~ symbol. You must use the full name of the directory.

Connect OpenVistA-CIS to a server through an SSH tunnel

These instructions are for Linux. If using Windows, use the Astronaut CPRS package, which has a PuTTY utility and Astronaut SSH shortcut to initiate the SSH tunnel as well as a shortcut (stub) to start the OpenVistA-CIS Client.

  • A list of SSH commands is here.
ssh -l client9260 -L 9201:127.0.0.1:9260 remoteserver.computer.xyz -p 22

This command uses the client9260 SSH user (the default on the Astronaut OpenVistA server), the local 9201 port (default on OpenVistA-CIS clients), the remote 9260 port (the default on the Astronaut OpenVistA server), and the SSH 22 port (the default). Any of these can be changed, of course (depending on your configuration).

Note: This method requires a password authentication (manually in the terminal).

Note: If creating a Menu item/shortcut for this command, make sure the Advanced -> Run in terminal option is ticked.

  • Start the OpenVistA-CIS Client (as in the preceding section):
mono OpenVistaCIS.exe --server=myserver.mydomain.org --port=9201

Automated SSH password authentication script

  • Install the expect utility:
sudo apt-get install expect
  • If your password is still the Astronaut SSH default (i.e. not#1sostrong), then use this command to start the SSH tunnel:
expect -c 'spawn ssh -l client9260 -L 9201:127.0.0.1:9260 remoteserver.computer.xyz -p 22; expect assword ; send "not#1sostrong\n" ; interact'
  • Of course, I place this command in a Menu Item / Shortcut that I name Astronaut SSH, to keep it consistent with the Astronaut shortcut-naming scheme elsewhere.
  • Start the OpenVistA-CIS Client (as in the preceding section):
mono OpenVistaCIS.exe --server=myserver.mydomain.org --port=9201

Installation on Mac

Connect to a server

Connect OpenVistA-CIS Client to an Astronaut OpenVistA server on the same computer

mono OpenVistaCIS.exe --server=127.0.0.1 --port=9260
  • Use your Access Code / Verify Code as the LoginID / Password ( default at installation for Astronaut systems is sys.admin / vista!123 ).

Connect to the Medsphere Demo server

  • Test your setup by connecting to the Medsphere Demo server. Instructions are here.
  • Connection Information
  • Login ID: PU1234 -> Password: PU1234!!
  • Server: openvista.medsphere.org
  • Port: 9201 for the newer demo database
  • Port: 9202 for the original demo database

Note: if you're not running the latest version of OpenVista-CIS, you must use --proxy-mode=builtin as a command-line option to connect. The demo server no longer runs the bridge.

  • Other OpenVista user accounts include:
  • MANAGER,SYSTEM: -> access/verify/e-sig: SM1234 / SM1234!! / SM1234
  • USER, PHYSICIAN: -> access/verify/e-sig: PU1234 / PU1234!! / PU1234
  • USER,NURSE: -> access/verify/e-sig: NU1234 / NU1234!! / NU1234

Open your firewalls

Don't forget to open your firewalls on both sides of the connection. If you are using an SSH tunnel, the port used for SSH (default is 22) must be open in the firewall on both ends of the connection.

If you are connecting (without an SSH tunnel) using port 9260 or 9201 (or another port), make sure the port(s) used are allowed by the firewalls on each side of the connection.