Web Application Instructions of VistAWeb
Install the VistAWeb application on the server following steps 1-5 below
1 Remove prior versions of VW (and vwContext, if it exists.)
2 Unzip vistaweb_<version>.<date>.zip into the target VW folder.
3 Unzip vistawebcontext_<version>.<date>.zip into the target folder created in step 3 of the one-time BSE configuration mentioned above.
4 Change the <vistaweb>/resources/xml/log4net.xml file to add the login ID and password from step 2 above. Strip out the text “Provider=SQLOLEDB” from the connection string.
5 Change the <vistawebcontext>/resources/xml/log4net.xml to add the login ID and password from step 2 above. Strip out the text “Provider=SQLOLEDB” from the connection string.
6 Change the <vistaweb>/web.config file
a. Change userActivity.connectionString to specify the SQL Server database.
b. Change version.useFullVersion to “false”.
c. Change allowViewLog to “false”.
d. Change excludeChemHem to “true”.
7 Change the <vistawebcontext>/web.config file to specify the SQL Server database (set it to the same value as what’s in 6.a.)
8 For Production purposes, a domain address was established for VistAWeb (https://vistaweb.med.va.gov/), with VistAWeb configured as its own website.
9 Set the default VistAWeb content page to “loginframeset.htm.”
10 Grant “Write” permission to the NETWORK SERVICE user on the Windows 2003 server to the folder ~/resources/images/temp.
11 Start the vistawebcontext application pool and the vistaweb web application, then start the vistaweb application pool.
12 Start the vistawebcontext web application, then start the vistaweb application.
13 Copy vhasites.xml file from the prior VistAWeb instance into <vistaweb>/resources/xml.
14 Start <vistawebcontext>
15 Start <vistaweb>
The configuration in steps 4 – 7 can be done by using the script and properties file provided in Appendix B.
SQL Server Database Schema Instructions
A database schema is required for maintaining the VistAWeb log files and identity of sites from which a user can perform patient lookups. Appendix A contains the database specifications (written for SQL Server 2000). For security purposes, the user account and password that is needed by the VistAWeb application will not be included in this document.
1. Create a database called EMR, or something similar.
2. Run the SQL scripts in Appendix A.
3. Add the user account used by VistAWeb (contact the VA Service Desk for information regarding the account/password at 1-888-596-4357 or by e-mail at VASD@va.gov.)
4. Grant the provided user account “dbowner” rights to the EMR database.
VistA Security
VistAWeb can optionally handle VistA security similarly to the way CPRS does, by requiring the user to have CPRS patient selection and/or CPRS GUI tab access in order to gain access to patient reports through VistAWeb. This setup is global in nature; that is, if set up, all users would have to have one or both of these settings in order to be able to login to VistAWeb.
You can see a user’s CPRS tabs and patient selection settings in the user management area of VistA FileMan.
Posted in: Others | Tags: