OSEHRA has a new process for generating Virtual Machines for testing which utilizes the Vagrant tool to create the VM and populate it with the appropriate tools and repositories.  There is a set of instructions available from the OSEHRA VistA repository which can be found here:

OSEHRA recommends utilizing this capability instead of downloading the VM from below.

An updated Virtual Machine has been configured following the instructions in:

* Instructions-establishing-and-testing-osehra-code-base-main-page

The main features of this virtual machine are:

- Virtual Box

- Ubuntu 11

- GT.M

- Git

- CMake

- VistA-FOIA release from December 6th 2011

- OSEHRA-Testing

- Pre-configured to submit builds to the Dashboard


The Virtual Machine has been updated with a configuration for interfacing to CPRS.

Many Thanks to Nancy Anthracite for her detailed, step-by-step instructions on how to perform the configuration.

The new Virtual Machine can be recreated by downloading the following files:



* OSEHRA-VCM-2012.ovf

* OSEHRA-VCM-disk1.vmdk

  and importing them in a VirtualBox installation.  The files above can also be downloaded using BitTorrent with:  


The username is "softhat"

The password is "softhat"


The Virtual Machine can be freely redistributed.

All the software contained in it is under Open Source licenses, or in the Public Domain.


When connecting to it from CPRS: 

  • The demo Access code is : "softhat2012!"
  • The demo Verification code is : "osehra2012#"

For detailed instructions on how to connect CPRS to the VM, please see the page 


MUnit Testing Framework:

For those looking to experiment with the MUnit Testing framework, the following VM has been patched to utilize the MUnit framework.  The patch was taken from the M-Tools repository found at  Login and connection instructions are the same as those mentioned above.  Patching done by Jason Li (

The previous Virtual Machines can be found here:




link and file mismatch?

Paul Bradley's picture

The link OSEHRA-VCM-2012.ovf appears to points to OSEHRA-CPRS-Enabled.ovf



Chris Uyehara's picture

Thanks - it has been corrected.


Broken Links

Charles Riley's picture

It seems that the links on this page are again failing.  I was able to browse to a git repository, so I'm assuming that the files and location have changed?  Please point me to where the appliances can be downloaded.  Thanks.




torrent link has no torrent

Larry Johnson's picture

I'll be trying the older version then.




Joshua Cope's picture

After I set up this 

should I update VistA-FOIA release to the current version on GitHub and if so how would I go about doing this?


Test Data in Virtual Machine

Dana Miller's picture


I think I got the instance of VistA in the VM to come up and run, and I connected to it from an instance of CPRS.  Now the question is:  How do get patients for testing, or get a set of test patient data to load into the database?



Broken Links

Charles Riley's picture


I believe that I sent this email to a wrong location.  The links above seem to be broken.  I was able to browse to a git repository, so I assume that the files and locations have changed.  Please provide updated URL's for accessing the appliances.  Thanks.



Broken Links

Joseph Snyder's picture

Hi Charles,

Thanks for your interest in trying out the OSEHRA tools.  We have moved away from the download of the VMs to something a bit more flexible.  OSEHRA now recommends the usage of the Vagrant tool to have Vagrant generate an Ubuntu VM for you which has the most recent updates of the available OSEHRA repositories.  Within that Github repository, we do have a set of instructions on how the the Vagrant process works and how to start it running on your local system:  

If you still would prefer the VM download, we can make the files available for you. Just so you are aware, the information that would be available within this VM is now severely behind the current repositories and would require a few extra commands to bring it up to speed.   In the mean time, I will edit this page to have a note about the change and a link to the Vagrant install documentation .  Thanks again for your comments.