VistAWebInstallationGuide - VistA Institute

tukwilagleefulInternet and Web Development

Oct 31, 2013 (3 years and 7 months ago)

52 views




VistAWeb

________________________________






Installation Guide


February

2005













Department of Veterans Affairs



VistAWeb Installation Guide

ii

February 2005


Revision History


Date

Patch

Page(s)

Change(s)

1/31/05

Informational
Patch number
OR*3*230

All

Initial Installation Guide fo
r
use with beta test version

2/10/05


Page 1 and 9

Removed URL referenced on
Page 1; Removed reference
to Special User scripts on
page 9

2/18/05

Informational
Patch number
OR*3*230

Page 5

Fixed date, removed URL
(VISN CIO will provide URL)

2/23/2005


All

Revised flow























VistAWeb Installation Guide

iii

February 2005


Table of
Contents


REVISION HISTORY

................................
................................
................................
......................

ii

TABLE OF C
ONTENTS

................................
................................
................................
................

iii

VISTAWEB

................................
................................
................................
................................
.....

1

I
NTRODUCTION
................................
................................
................................
..............................

1

A
SSUMPTIONS
................................
................................
................................
...............................

1

SYSTEM REQUIREMENTS

................................
................................
................................
...........

3

H
ARDWARE

................................
................................
................................
................................
...

3

Components that apply to both web and database servers

................................
...................

3

Web Server Components

................................
................................
................................
........

3

Database Server Components

................................
................................
................................

3

S
OFTWARE

................................
................................
................................
................................
...

4

Figure 2: Web Service Extension Settings
................................
................................
..............

4

INSTALLATION
................................
................................
................................
..............................

5

W
EB
A
PPLICATION
I
NSTRUCTIONS

................................
................................
................................
.

5

Figure 3: VistAWeb Website and Accompanying Web Applications

................................
......

5

Figure 4: Application Server General Settings

................................
................................
........

6

SQL

S
ERVER
D
ATABASE
S
CHEMA
I
NSTRUCTIONS

................................
................................
.........

6

MANAGING FUTURE UPDA
TES VIA FTP
................................
................................
...................

7

Figure 5: FTP Anonymous Settings

................................
................................
........................

7

Figure 6: View of Production, FTP, and Archive Folders
................................
........................

8

APPENDIX A: DATABASE

SCHEMA
................................
................................
...........................

9

L
OG CREATION SCRIPT

................................
................................
................................
..................

9

C
PRS
U
SERS CREATION SCRIPT

................................
................................
................................
.....

9

L
OG
D
ESC VIEW CREATION SC
RIPT
................................
................................
...............................

10




VistAWeb Installation Guide

iv

February 2005





VistAWeb Installation Guide

1

February 2005



VistAWeb


Introduction

Veterans Health Information Systems and Technology Architecture
(VistA) VistAWeb is an
intranet web application used to review
remote
patient information found in VistA.

There are
two ways to use
VistAWeb. VistAWeb may be made available from the Tools Menu within
the Computerized Patient Record System (CPRS); or from a
command line (
URL
)

established by the
VISN

CIO as a secondary option.
VistAWeb mirrors the behavior of
CPRS

and Remote Data View
+

(RDV
+
)
.
VistAWeb is
an enhancement to

CPRS
/
RDV
+ by
permitting a more robust and timely retrieval of remote site
patient data
.

Assumptions

Th
e

intended audience of this
I
nstallation
G
uide
is system administrator
(
s
)

(specifically, web
administrator
(
s
)
) and
assumes the reader
(s)

possess the technical
knowledge of how to
configure and interact with application servers
.
This document also assumes the necessary
security hardening guidelines have
already
been implemented (see

the Office of Cyber and
Information S
ecurity link below for information pertaining to security requirements:
https://vaww.ocis.va.gov/portal/s
erver.pt?in_hi _opt_comm_community=257&in_hi_space=SearchRes
ult&in_hi_control=bannerstart&in_hi_useri d=2&in_se_sel _1=everything&i n_tx_query=hardening+guid
elines

VistAWeb does not need to
be
installed
at each site
.
The link to the application
may be
incorpo
rated into the existing CPRS Tools Menu at the local site.

The
installation
instructions provided in this guide shall identify

the required configuration/settings for
VistAWeb use from the CPRS Tools Menu.

Additional
reference

material

may be viewed in
the C
PRS GUI Technical Manual by selecting the following link:
http://www.va.gov/vdl/VistA_Lib/Clinical/Comp_Patient_Recrd_Sys_(CPRS)/CPRSGUITM.p
df

Tools

Menu

Quick
Configuration

According to Page 21 of the CPRS GUI Technical Manual, the parameter,
ORWT TOOLS
MENU
, is used to set up the list of software that appears on the
CPRS Tools M
enu. This
parameter may be set up for the site, then overridden as appro
priate at the division, service,
and user levels.

Each item entered on the
Tools M
enu should have the form
:


NAME=COMMAND




NAME r
epresents what the user will see on the menu for that line item
. An
ampersand
“&”
may
also
be used in front of a letter to a
llow keyboard access to
the menu item.



COMMAND may be a line
,

which
is
execut
able

by Windows. It may
b
e any file
which has a
Windows
file association.


For example:
Name=Command: &CPRSInfo=http://vista.med.va.gov/cprs/index.html

For VistAWeb:
VistAWeb=
Command: line provided by VISN CIO





VistAWeb Installation Guide

2

February 2005




VistAWeb from the
Tools Menu


A site may use the Tools
M
enu to give users access to other client software from within
CPRS.
As stated previously, t
he parameter, ORWT TOOLS MENU, is used to set up the list
of software tha
t appears on the menu. This parameter may be set up for the site, then
overridden as appropriate at the division, service, and user levels.

If you note the following example in Figure 1 below

(extracted from
Page 21 of the CPRS
GUI
T
echnical Manual
)
, you w
ill n
ote that
CPRSInfo

did not require an executable file to be
identified.

Since Windows understands hypertext transfer protocol (HTTP), it will launch the
workstation’s default browser and navigate to the address. Also note the quotation marks in
the Vis
tA Terminal example. A path that contains space characters (like C:
\
Program Files
\
...)
must be surrounded by quotation marks. Entries on the command line may also contain
parameters. In the example above, LOCALVAMC is the name of a KEA!
session
, which
is
p
assed as a command line parameter.

Figure 1: Tools Menu Example Configuration


It is
also
possible to pass context
-
sensitive parameters. These are parameters that are
entered as placeholders, and then converted to the appropriate values at runtime. These
placeholder parameters are:

%SRV


= Server name for the current broker connection

%PORT

= Port number for the current broker connection

%MREF

= M code giving the global reference where the patient DFN is stored

%DFN


= The actual DFN of the currently selec
ted patient

%DUZ


= Internal entry number of the current user





VistAWeb Installation Guide

3

February 2005



So, if you have another application that needs to know, for example, the identity of the
current user and currently selected patient, you could list %DUZ and %DFN as parameters
in the command th
at executes that program.


VistAWeb from a Sole App
lication
Server/Database Server

The remainder of the
Technical Manual will
describe the one
-
time installation of the
VistAWeb application on a sole application server cluster
,

in addition to th
e one
-
time
i
nstallation of the SQL Server database on a database server cluster. It is divided into the
following
four
sections:



System Requirements

S
ettings that must be made on the server to operate
VistAWeb

(
Hardware: Comp
onents that apply to both web and database
servers,
Web Server Components and Database Server Components
. Software: Application
configurations and settings
)



Installation Instructions

I
nstructions both for the
W
eb
A
pplication
Server
and SQL
Server
D
atabase



Managing Future Updates via FTP

Creation a
nd configuration of FTP “staging”
folder for receipt of developer updates



Appendi
x A: Database Schema

database specifications (written for SQL Server
2000
)


System Requirements


Hardware

The servers
which

will run VistAWeb are already purchased and configu
red in Silver Spring,
Maryland
.
The basic components for the web servers and the database servers are listed
below.

Components that apply to both web and database servers



Dell PowerEdge 4210 Rack with KVM (16
-
port switch)



Two SAN adapter cards, and Emulex
FC HBA with Power Path licenses


Web Server Components



Two Dell PowerEdge 6650s



Dual
-
CPU 2.2 GHz processors



8 GB RAM



Five 36
-
GB SCSI hard drives



Dual network interface cards


Database Server Components



Two Dell PowerEdge 6650s



Quad
-
CPU 2.2 GHz processors



8

GB RAM



Five 36
-
GB SCSI hard drives



Dual network interface cards






VistAWeb Installation Guide

4

February 2005



Software



Windows Server 2003 Enterprise, configured with the role of Application Server



Internet Information Services (IIS) 6.0 (installed by default as part of the Application
Server role)



Microsoft Visual J#.NET 2003 runtime component



.NET Framework 1.1 (part of the Windows Server 2003 operating system default
installation)



FTP services and an FTP folder (to be used as a staging location for updates to
VistAWeb)



SMTP Virtual Server



.NET Fra
mework 1.1 is installed by default on Windows 2003 systems
.
Services packs
and updates to all three components are available through Microsoft Windows update
(
http://windowsupdate.microsoft.com
).



Web Exte
nsion Services set to allow ASP.NET extensions (see Figure
2
)



SQL Server 2000 (The database does not need to run on the same server as the web
application.)



Figure
2
: Web Service Extension Settings






VistAWeb Installation Guide

5

February 2005




Installation

The installation instructions are divid
ed into two sections

the web application and the
SQL Server database schema. Note that for production purposes, the installation of both
the web application and the SQL Server database need only be performed once.

Web Application Instructions

There are two

other applications
used by
VistAWeb

VistAWebDocs and
VistAWebUserMgt, depicted in Figure
3
.
VistAWebDocs is a web application that houses
current and future documentation about the development of VistAWeb and related
components
.
VistAWebUserMgt is a web a
pplication that allows select users to control
VistAWeb users’ access to VA sites’ patients other than users’ local site
.
VistAWebDocs
is linked to VistAWeb, while VistAWebUserMgt is not
.
Both of these applications are
included in the EMR.zip file mentione
d in steps
1
-
5
below.


Figure
3
: VistAWeb Website and Accompanying Web Applications


1.

Extract the EMR.zip file to the desired location for EMR; note that the extraction will
automatically create a root folder called EMR.

2.

Configure the EMR folder to run eit
her as its own website or as a virtual directory
under the default website; the former allows the application to run as its own website,
while the latter allows the application to operate as one of a collection of web
applications under another dominant we
bsite
.

3.

For production purposes, a domain address was established for VistAWeb (
VISN
CIO will provide URL
), with VistAWeb configured as its own website.

4.

Set the default content page to “loginframeset.htm”.






VistAWeb Installation Guide

6

February 2005



5.

Configure VistAWebDocs and VistAWebUserMgt as web

applications under the
VistAWeb website; the virtual directories for each are VistAWebDocs and
VistAWebUserMgt, respectively.


Figure
4

depicts the image of some of the settings made to the application server.


Figure
4
: Application Server General Setting
s



SQL Server Database Schema Instructions

A
database schema is required for maintaining the VistAWeb log files and from what
sites a user can perform patient lookups
.
Appendix A contains the database
specifications (written for SQL Server 2000)
.
For sec
urity 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”.

2.

Run the scripts in Appendix A.

3.

Add the user account used by VistAWeb (call
VistAWeb Support
at
734
-
769
-
7100
x.5782 for the account/password).

4.

Grant the provided user account “dbowner” rights to the EMR database.






VistAWeb Installation Guide

7

February 2005



Managing Future Updates via FTP

In order to
seamlessly
manage future enhancements to VistAWeb, the following process
is recommended:

1.

Creat
e an FTP “staging” folder for developers to place updates; ensure the folder
has NOT been left open for anonymous access and requires user authentication to
access; see Figure
5

below for an example.


Figure
5
: FTP Anonymous Settings


2.

When updates are cop
ied to the staging folder, an email message will be sent to the
webmaster, asking for release of the updates. Detailed instructions of where specific
files should be placed will be provided.

3.

The webmaster will make a backup copy (e.g., a zip file, or a cop
y of the file/folder
structure) of the current production version of VistAWeb before copying the staging
files to production and place the backup file(s) in an archive folder.

4.

The webmaster will copy the file(s) to the appropriate location(s) identified.

5.

Once the updates are placed into production, the webmaster will delete the files
placed in the staging folder.

6.

The webmaster will reply to the sender and copied parties that the release is done.


Figure
6

shows a Windows Explorer view of the FTP staging fo
lder, the archive folder,
and the production folder.





VistAWeb Installation Guide

8

February 2005




Figure
6
: View of Production, FTP, and Archive Folders







VistAWeb Installation Guide

9

February 2005



Appendix A: Database Schema

Database Name: EMR

Database Tables:



SpecialUsers



Requests



Log



CprsUsers

Views:



LogDesc


Log creation script

CREATE T
ABLE [Log] (


[id] [numeric](19, 0) IDENTITY (1, 1) NOT NULL ,


[requestDate] [datetime] NULL ,


[remoteAddr] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


[userId] [numeric](19, 0) NULL ,


[userName] [varchar] (100) COLLATE SQL_Latin1_Genera
l_CP1_CI_AS NULL ,


[userSitecode] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


[userSitename] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS


NULL ,


[requestPage] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS

NULL ,


[requestS
itecode] [varchar] (6) COLLATE SQL_Latin1_General_CP1_CI_AS

NULL ,


[requestSitename] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS

NULL ,


[patientID] [numeric](19, 0) NULL ,


[patientName] [varchar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS

NUL
L ,


[patientSensitivity] [tinyint] NULL ,


[message] [varchar] (1000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


CONSTRAINT [PK_Log] PRIMARY KEY CLUSTERED


(



[id]


) ON [PRIMARY]

) ON [PRIMARY]

GO

CprsUsers creation script

CREATE TABLE [CprsUsers]

(


[UserID] [numeric](19, 0) NOT NULL ,


[Sitecode] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


[DUZ] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


[SSN] [varchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,


[Name] [varch
ar] (100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL

) ON [PRIMARY]

GO





VistAWeb Installation Guide

10

February 2005



LogDesc view creation script

CREATE VIEW dbo.LogDesc

AS

SELECT *

FROM dbo.Log

ORDER BY id DESC