CPRS-connection-to-the-VM

CPRS-connection-to-the-VM


This Wiki page describes how to connect CPRS to the Virtual Machine.

 

[Update: Please note that a newer version of the Virtual Machine is here:]

http://osehra.org/wiki/virtual-machine-testing-osehra-code-base-pre-configured-2

This newer version contains the FOIA version of December 6th.

 

For the instructions in this page,

please use the Virtual Machine that is described here

http://osehra.org/wiki/virtual-machine-testing-osehra-code-base-pre-configured

This Virtual Machine contains the FOIA release of August 19th, 2012.

 

Please go through the following steps:

 

A) Launch the VM from Virtual Box

B) Login as the "softhat" user with the password = softhat

C) Double click on the "Terminal" icon in the Desktop to open a terminal.

D) In that terminal, type "ifconfig" and ENTER. This should show you something similar to the image below:

The output of this command describes all the network interfaces that are currently enabled in the VM.

In the first block, labeled as "eth1" look for the field labeled as "inet addr" in the second line.

In this case it contains the values "inet addr:192.168.200.8"

This is the IP number of the current eth1 interface in the network. This number will be different for you, and will depend on the DNS configuration of your network. The number can also change from one time of booting the VM to the next, depending on the setup of your local network.

At this point, simply write down the number. We will refer to it as the "IP number of the VM".

 

E)  Download the CPRS package from the following link:

F) Expand the zip file in your computer

You will see a set of files similar to the screenshot below:

G) Select the "CPRSChart" icon, right click on it and create a shortcut. You can place the shortcut in this same directory, or in your Desktop, or in another directory.

H) Once you have created the shortcut, right click on it, and select "Properties".  You will see a window similar to the screenshot below:

 

I)  In the field "Target", add the text that is highlighted here in blue,

  •        S=192.168.200.8  P=9200 CCOW=disable

but, instead of using the IP number "192.168.200.8", use the IP number that you found in your VM in step (D).

Keep the port number "9200" unchanged.   Once you have changed the IP number, click on the OK button.

 

J) Now that your shortcut is configured to locate the VM by its IP number, you are ready to run CPRS. Make sure that your VM is still ON.  Now simply double click in the shortcut of CPRSchart. This will show you the following initial screen while CPRS is loading...

 

K) Once CPRS has finished loading, you will se a screen similar to:

 

L) In this screen you can now

enter the "Access Code" that is        softhat2011!

and then the "Verify Code" that is        osehra2011%

 

M) The login process should go smoothly, and you should be presented with the following screen:

 

CREDITS: These instructions were extracted from a document that Nancy Anthracite kindly shared with the community. I have extracted what I think were the key pieces to connect CPRS to the pre-configured VM.

 

Of course, you can be sure that if there are any errors, they are all mine     :-)

 

Please let us know if you run into any trouble while following these instructions.

like0

Comments

VM IP Address Issue

Brian Sur's picture

Hello,  Thanks for the instructions and I got struck at the step of changing IP address in the short cut.  The IP address my VM gives of a Win 7 machine is 10.0.2.15 and when I try to connect, it gives me "Error encountered.  Funcation was: connect, Error was: WSAECONNREFUSED.

Any idea?

Thanks!

like0

VM IP Address issue

Robert Sax's picture

Make sure that you both forwarded the port on VirtualBox (settings->network->adapter 1->port forwarding) and that the firewall on ubuntu allows the incomming connection or is disabled. Generally you should be able to use the local loopback (127.0.0.1) as the ip if you are connecting CPRS on your windows box to the Ubuntu box running on the same hardware.

Rob

like0

CPRS to VM IP Address issue

Brian Sur's picture

Thanks for your input.  I have done the following and getting various errors.

1. Turned off firewall on both my host machine (win XP), and Ubuntu ($ sudo efw disable).

2.  Tried with loopback address (127.0.0.1) which gives me WSAECONNREFUSED error.

3.  Tried with inet addr:10.0.2.15 which gives me WSAETIMEDOUT error.

4.  When I do sudo iptables -L  I get Chain INPUT, FORWARD, OUTPUT (policy ACCEPT).

Any other settings to be altered?

Thanks!

 

like0

CPRS to VM IP Address Issue

Robert Sax's picture

Did you set up the port forward?  For your VM under settings->network->advanced->port forwading, there should be a line for forwarding:

protocol: TCP

host port: 9200

guest port: 9200

 

I just ran through setting up the CPRS enabled VM (don't confuse with the original VM) and it worked fine, but I did add the above port forward. Without this forwarding it will not connect.

 

Rob

like0

Firewall?

Christopher Edwards's picture

Have you checked any firewalls running on the host and guest systems?

To check a linux firewall you can type:

sudo iptables -L

like0

VM IP Address

Shane McClaughry's picture

If you're attempting to connect to the VM from a external machine, I would suggest switching the VM network adapter to bridged adapter and flushing the IP address and DNS, or rebooting the box and then attempting to connect again.

like0

Batch Import/Export of demo patient data to VistA: How?

Rafael Richards MD, MS's picture

Wonderful work above getting the VistA VM and CPRS connection working.  Thanks!

This leaves us with a blank VistA with no patient data, so we cannot test functionality.   In order to validate any features developed we need a curated validated demo patient set of known quality and known data, so we can do quality assurance on the resulting display of CPRS.

This needs to be a completely automated script  to eliminate any possibility or inconsistency in having different users importing calibration patient data.

Are there any built-in routines for importing patient data records from external  text (XML, HL7) files?

 

 

 

like0

CPRS connection ACCESS and VERIFY codes

Paul Bradley's picture

Are the softhat2011! and softhat2011% codes still valid for the OSEHRA-VCM-2012 VM?  I am able to establish a CPRS connection but receive a message "Not a valid ACCESS CODE / VERIFY CODE pair" when I used the above codes.

like0

CPRS connection ACCESS and VERIFY codes

Joseph Snyder's picture

Hi Paul,

The verify code for the CPRS is "osehra2011%" 

From above:

...

enter the "Access Code" that is        softhat2011!

and then the "Verify Code" that is        osehra2011%

...

EDIT:

The above code is for the old VM (http://osehra.org/wiki/virtual-machine-testing-osehra-code-base-pre-configured)

 

For the newer VM (http://osehra.org/wiki/virtual-machine-testing-osehra-code-base-pre-configured-2), the year just goes up by one:

...

enter the "Access Code" that is        softhat2012!

and then the "Verify Code" that is        osehra2012%

...

- Joe

like0

CPRS connection ACCESS and VERIFY codes

Michael Meador's picture

I am researching the VistA platform for the State of Tennessee Department of Health. I have successfully installed VistA and the CPRS Demo. I have the CPRS pointed at the VistA instance as per the instructions on this site. The Access Code: "softhat2012!" and Verify Code: "osehra2012%" do not work. I can see the CPRS is conneting to the VistA server in the virtual machine. I am installing the test bed before we install a produciton site.

Please advise.

Thank you.

Michael J. Meador

Business Analyst, Tennessee Finance and Adminstration

Business Solutions Delivery

Please Reply To:

mm@meadmj.org

UPDATE:

I actually got these codes to work ACCESS CODE="softhat2012!" and VERIFY CODE="osehra2012#".

Note that the VM installation page uses these ACCESS and VERIFY codes. The difference being the '#" rather than the "%" at the end of the "osehra2012" VERIFY code.

like0

Unable to start the client

Tilak Kola's picture

Hi,

The process goes smooth until I try to start up the client where I am constantly getting the error - 'WSAETIMEDOUT error'. I tried fixing the IP as well within the VM but still the same. Have tried all the other probable solutions listed. Do suggest if there is anything I can try to be able to start up. Thank you.

like0

Quick Troubleshooting Steps

Christopher Edwards's picture

Can you check the following:

  1. Is the broker running?
    1. You can either check by using D ^%SS in Caché
    2. At a command prompt (or bash prompt) type "netstat -an" and look for the port number configured for the broker (commonly 9210)
  2. Is TaskMan running?
    1. Type "D ^ZTMON" - you should see "TaskMan is current" on the screen (type "^" to exit)
  3. Is there a firewall enabled on the host or client that is blocking the connection?
like0

CPRS connection to VM

Tilak Kola's picture

Thanks Christopher,

I am not well knowledgeable technically but did try the steps -

1) I could run the second command and the output showed a big list but I could not find the port number 9210. It was not listed.

2) I could not get any output for 'Task man' command - says 'command not found'

3) I switched off the firewall on the host and also no firewall on the guest

Do suggest if I am missing anything. Thanks again.

like0

Unable to start the client.

Ignacio Valdes's picture

Hi dr.hit,

That battle is a very old one. You may want to try the astronaut distribution:

http://astronautvista.com/astronaut-help/how-to/how-to-install-astronaut-vista-server-and-client

It is designed to be up and running doing clinically useful things in less than an hour.

-- IV

like0

Astronaut

Tilak Kola's picture

Thanks ivaldes1.

I am not much knowledgeable technically and thought to try a readymade VM. Also this is the first time I am trying out Vista. So, setting up a database and client might be difficult I presume. But will try this, if the other fails.

 

like0