Page tree

Header Text

Skip to end of metadata
Go to start of metadata

The following methods of installation of CPRS are available. Sites' choice of which method(s) to use will depend upon Regional/VISN policies, Local Area Network (LAN) performance or other local circumstances. User requirements, physical location and methods of connection to the VA network may warrant more than one of the options below to be used.

  • Network (shared) installation:

This method is typically the simplest to maintain, providing the local network infrastructure is robust enough to handle the additional traffic caused by users running the GUI executable (CPRSChart.exe) across the LAN.
The GUI executable (CPRSChart.exe), and ancillary files (DLLs, Help files etc.), are copied to a network shared location. Users are provided with a desktop shortcut to run CPRSChart.exe directly from the network shared drive. The necessary command line parameters (VistA server address or name and RPC Broker Port number) are entered in the "Target" field of the shortcut properties
At the time of a CPRS version update the copy of CPRSChart.exe (and any updated ancillary files) is simply replaced, on the network share, with the new version.
Any users requiring access to another site's CPRS system can be given an alternate desktop shortcut with command line parameters appropriate to the intended target VistA system.
If a user requires access to an older or newer version of CPRS (e.g. during a phased deployment, when sites are temporarily not all on the same version, or for testing purposes) a different version of CPRSChart.exe can be placed in a separate network location and the user be supplied with an appropriate alternate shortcut (different Target path and different VistA server command line parameters).
Note:The version of CPRSChart a user executes must always match the patch-level version of the VistA system targeted.

  • Citrix installation:

The GUI executable (CPRSChart.exe) and ancillary files (DLLs, Help files etc.) are installed and run from a remote workstation, and the user views the remote workstation's screen on their local workstation.
For the local site users, this method is on a similar level to the Network (shared) installation above. The users' workstations require only an appropriate shortcut (and the necessary Citrix Access Group (CAG) infrastructure).
Note: For issues with CAG, please contact your local or national help desk.
For the Citrix Farm administrator, this method involves installations on the host in a similar manner to either the Gold Path or the Direct Access methods outlined below.
During a phased deployment of a new version of CPRS, if a Citrix Farm is serving users who are scheduled to deploy at different times, the Farm administrator may be required to temporarily maintain hosts with both the old and the new versions of CPRSChart.exe available.

  • Gold Path installation:

This is the "standard" method of installation where the GUI executable (CPRSChart.exe), and ancillary files (DLLs, Help files etc.), are installed on and run from the user's local workstation. In normal day-to-day operation, the user's shortcut executes a locally installed copy of CPRSLoader.exe which looks in a pre-configured network "Gold Path" (specified in a command line parameter) to see if there is a later version of CPRSChart.exe ready to be installed. If not, then execution passes to the locally installed version of CPRSChart.exe. If an updated version is found on the Gold Path, then a silent installation of the new version takes place, following which the newly installed version of CPRSChart.exe is executed on the local workstation.
This method of installation initially requires the distribution and installation of a Microsoft Software Installation (MSI) file (CPRSLoader.msi) to each user's workstation, typically accomplished via SCCM. This is outside the scope of CPRS development. A National package (CPRS Loader 1.30.40) has been prepared and made available to Regional COR Client Technologies leadership.
The CPRS Loader installation package can be found on the System Center Configuration Manager (SCCM) central site at the following locations.
Note:The Loader has not been updated for CPRS v.30.c. There is no need to update the Loader. This is being left here for reference only.
Package Name:1VA - VA CPRS Loader
Package ID:1VA004E7, R03002C4
Test Location:
VA Central Site Packages > Test > 1VA - VA CPRS Loader
Production Location:
VA Central Site Packages > Production > 1VA – Applications > 1VA - VA CPRS Loader
All details of the SCCM package can be found in the build document and should be reviewed before deployment:
http://vaww.eie.va.gov/SysDesign/CS/Shared%20Documents/Build%20Documents/Application%20Tier%203%20and%204/ESE%20VA%20CPRS%20Build%20Document.pdf
The CPRSChart.exe component of the update is held in a Microsoft Software Patch (MSP) file (CPRSChart.msp) which is copied to the network Gold Path location—that should be all that is required for a normal CPRS version update for sites using this method. The exception is if a new version of CPRS Loader is also being released, in which case the cycle begins again with the distribution to users' workstations of the new CPRSLoader.msi (before the new CPRSChart.msp is copied to the network Gold Path)—this is the circumstance in which CPRS v30b is being released.
The CPRS deployment software distribution will include an appropriate version of the CPRS Microsoft patch file (named CPRS_XX_YY.msp, where XX is the current version number for CPRS, and YY is the current build number. At this point the current file name is CPRS_30_72.msp). This file has the named version of CPRSChart embedded within it, along with any updated ancillary files. Also included in the deployment software distribution will be a .VER file. This file will have the same name as the MSP file, with only the file extension changed. As an example, the .VER file for CPRS_30_72.MSP will be named CPRS_30_72.VER. To be effective, the .VER file must be placed in the same Gold Path in which the .MSP file was placed. The .VER is optional but beneficial. It will allow the CPRS loader to much more quickly find an appropriate version of CPRSChart.exe for use with the current VistA system. Including the VER file in the Gold Path can shorten CPRS start times substantially.
For the convenience of local System Administrators, the file CPRSLoader.msi is also included in the release package, in case they need to manually install it on a workstation.

  • Direct Access to a Local Copy of CPRSChart.exe (bypassing the loader)

In cases where a site's network performance is weak enough that CPRSLoader.exe, in checking the Gold Path every time a user starts CPRS, introduces unacceptable delays, some sites have elected to bypass CPRSLoader.exe altogether and have the users' shortcuts point directly to a local installation of CPRSChart.exe. The downside to this approach is that a future release of CPRSChart.exe will not be automatically picked up from the Gold Path by that workstation and the new CPRSChart.exe (plus any additional changed DLLs and Help files) will need to be pushed out to workstations by other means, such as an SCCM package.
NOTE: There is a national SCCM package to distribute the Cprschart.exe file to help sites or regions install the CPRS GUI.
An alternative, hybrid, version of this method would be to have two shortcuts for the users: One, for day-to-day use, which points directly to the local CPRSChart.exe and a second, to be used only for updating, which points to CPRSLoader.exe.


  • Manual install:

This method is used primarily for advanced users and at testing locations.This method is somewhat changed from that used previously for Windows XP workstations.

  1. Locate the OR_30_423.ZIP and unzip the file.
  2. Copy the CPRSChart.exe to a test directory, for example, C:\cprstest. You may need to create this new directory.

Note:You may need to have a user with Administrator rights complete this step.

  1. Create a Shortcut and name it "Test CPRSv30". This is to give the user another visual cue that this is not the normal CPRS icon.


  1. Copy the borlandmm.dll file into the same directory as cprschart.exe (for example, c:\cprstest). This file should be in the same directory as the CPRSChart.exe for CPRS v30C.
  2. Determine the DNS server name or IP address for the appropriate VistA server.
  3. Determine the Broker RPC port for the VistA account.
  4. Enter IP and RPC port in the Target field of the Shortcut properties (or use ServerList.exe).


Example of what the shortcut properties dialog might look like.
The server and port number shown above are not real and are for example only.

  • No labels