Nothing Special   »   [go: up one dir, main page]

Installing WVEHR 2.0 GTM Linux

Download as pdf or txt
Download as pdf or txt
You are on page 1of 22

Installing WorldVistA EHR 2.0 for GT.

M and Linux
Please email nanthracite@earthlink.net for errors in this document, requests for help and suggested for improvements

This is assuming you have a Debian derived version of Linux installed so that these commands will work. This is one of multiple ways that an installation of WorldVistA EHR can be handled. 1. Add a user for VistA at the Linux root command prompt (which is a # sign). Lets assume your users name will be vista. The command will likely be useradd instead of adduser for nonDebian Linux distributions. You will be asked to give the new user a password after the user is created. If you need to change the password, enter passwd vista or whatever your users name is and provide a good password. Dictionary words are not good passwords. You are inviting your system to be hacked if you do not provide a good password for Linux. adduser vista 2. Get the following files from my server and put them in the home directory of the user vista. You can do this by changing to the home directory of the new user and running the wget commands below from the command line. If wget is not installed in you Linux instance, you can download and install it, either with apt-get or aptitude install You can also do it using your browser with this link. The font is small so the commands will fit on one line. So you might be able to copy and paste them. You may have to put them in a text editor first and then copy and paste them. http://opensourcevista.net:8888/NancysVistAServer/WVEHR-2.0-Install-GTM/ Files to get: env2 WVEHR-gui WVEHR-guiXINETD These wget commands will download them for you from the command line.
wget http://opensourcevista.net:8888/NancysVistAServer/WVEHR-2.0-Install-GTM/env2 wget http://opensourcevista.net:8888/NancysVistAServer/WVEHR-2.0-Install-GTM/WVEHR-gui wget http://opensourcevista.net:8888/NancysVistAServer/WVEHR-2.0-Install-GTM/WVEHR-guiXINETD

3. From the directory /home/vista or the home directory of your VistA user, download the globals and routines by using the following command on the command line.
wget http://downloads.sourceforge.net/worldvista-ehr/WVEHR-2.0-Release-2.11-GTM.zip

page 1 of 22

4. When in the home directory of your new user, presumably vista, make a directory which I will call EHR and subdirectories g and o. An r directory will be added in the next step for the routines. This is not the only way to do this, but it is one option you can use
mkdir EHR cd EHR mkdir g o

5. Copy WVEHR-3-09-Release-GTM.zip file into the home directory of your vista user, presumably /home/vista, if it is not there already unzip it. It should unzip into Globals-GTM-WVEHR-2-0Release-2-11.zip and Routines-GTM-WVEHR-2.0-Release-2-11.zip.
$ cd /home/vista ~$ unzip WVEHR-2.0-Release-2.11-GTM.zip Archive: WVEHR-2.0-Release-2.11-GTM.zip extracting: Globals-GTM-WVEHR-2-0-Release-2-11.zip extracting: Routines-GTM-WVEHR-2.0-Release-2-11.zip

6. Move the env2 file and the WVEHR-gui file into the EHR directory and made the WVEHRgui file executable. These commands work if you are in the /home/vista directory when you issue them. Copy the Routines-WVEHR-VOE1.0-Release6-08-GTM-Linux.zip into the EHR subdirectory of your user and unpack the routines file and that will create the r directory loaded with routines. (For the Linux administrators information, in the routines file, there are over 20,000 routines so when you compress them, you really need to do the directory with it or the argument list is too long, which is why it is done this way.)
~$ cd /home/vista ~$ cp env2 ./EHR/ ~$ cp WVEHR-gui ./EHR/ ~$ chmod 755 ./EHR/WVEHR-gui ~$ Routines-GTM-WVEHR-2.0-Release-2-11.zip ./EHR/ ~$ cd EHR ~/EHR$ unzip Routines-GTM-WVEHR-2.0-Release-2-11.zip Archive: Routines-GTM-WVEHR-2.0-Release-2-11.zip creating: r/ inflating: r/GMRAY18L.m inflating: r/SDOQMP2.m inflating: r/XU8P378B.m inflating: r/SROPCEU0.m this will continue for almost 27,000 routines

7. Copy Globals-GTM-WVEHR-2-0-Release-2-11.zip into the g directory and extract it. It decompresses into mumps.dat and mumps.gld. The mumps.dat is a large file so this may take some time do decompress.

page 2 of 22

If you are still in the /home/vista/EHR subdirectory


~/EHR$ unzip /home/vista/Globals-GTM-WVEHR-2-0-Release-2-11.zip -d /home/vista/EHR/g/ Archive: /home/vista/Globals-GTM-WVEHR-2-0-Release-2-11.zip inflating: /home/vista/EHR/g/mumps.dat inflating: /home/vista/EHR/g/mumps.gld

Now that you have these in place, assuming you have named your user vista, you will need to change the owner and group of all of these files to vista, so go back to /home/vista and do that as follows. You will need to be root to perform this step. cd /home/vista chown -R vista: * 7. Now download and install the latest version of GT.M if you have not done it already. I am assuming that you will be getting GTM version 6.0000 so these instructions will be for that. Put this file in its own directory, unpack it and then run the ./configure script as root to install it. I recommend putting it in /usr/local/gtm_V60000-64 when you are asked where to put it. Accept the defaults and run the script as root. Either click the link below, go to the http://Sourceforge.net, search for GT.M (note the dot in there) and find the file and download it or use the wget command below pasted into your terminal. Get the correct version or your Linux system. You can also download the GT. M Installer and use that. It can be downloaded from http://sourceforge.net/projects/fis-gtm/files/?source=navbar You can find out if you have a 32 bit or 64 bit command by using the command prints your system information: uname -a In this example, to download the 64 bit version of GT.M 6.0000 using a wget command from the command line:
wget http://sourceforge.net/projects/fis-gtm/files/GT.M-amd64Linux/V6.0-000/gtm_V60000_linux_x8664_pro.tar.gz

There is also a 32 bit version if you prefer. That can be downloaded from the command line using the wget command below:
wget http://sourceforge.net/projects/fis-gtm/files/GT.M-x86-Linux/V6.0000/gtm_V60000_linux_i686_pro.tar.gz

page 3 of 22

For example, you might do this as user vista or whatever user you are cd <========== this puts you into the /home/[your user] mkdir gtm-install cp gtm_V60000_linux_x8664_pro.tar.gz ./gtm-install/ cd gtm-install tar -xzvf gtm_V60000_linux_pro.tar.gz You must be root starting here! You can use the command su or sudo su to become root. . ./configure <======= this runs the script to install gtm it is dot space dot at the beginning of the line
# ./configure GT.M Configuration Script Copyright 2009, 2012 Fidelity Information Services, Inc. Use of this software is restricted by the provisions of your license agreement. What user account should own the files? (bin) <==Press Enter Here What group should own the files? (bin) <==Press Enter Here Should execution of GT.M be restricted to this group? (y or n) n In what directory should GT.M be installed? /usr/local/gtm_V60000-64 Directory /usr/local/gtm_V60000-64 does not exist. Do you wish to create it as part of this installation? (y or n) y Installing GT.M.... Should UTF-8 support be installed? (y or n) n n <==Important to be

All of the GT.M MUMPS routines are distributed with uppercase names. You can create lowercase copies of these routines if you wish, but to avoid problems with compatibility in the future, consider keeping only the uppercase versions of the files. Do you want uppercase and lowercase versions of the MUMPS routines? (y or n)n Compiling all of the MUMPS routines. This may take a moment.

page 4 of 22

GTM> %GDE-I-GDUSEDEFS, Using defaults for Global Directory /usr/local/gtm_V60000-64/gtmhelp.gld GDE> GDE> GDE> %GDE-I-VERIFY, Verification OK %GDE-I-GDCREATE, Creating Global Directory file /usr/local/gtm_V60000-64/gtmhelp.gld GTM> %GDE-I-GDUSEDEFS, Using defaults for Global Directory /usr/local/gtm_V60000-64/gdehelp.gld GDE> GDE> GDE> %GDE-I-VERIFY, Verification OK %GDE-I-GDCREATE, Creating Global Directory file /usr/local/gtm_V60000-64/gdehelp.gld Object files of M routines placed in shared library /usr/local/gtm_V60000-64/libgtmutil.so Keep original .o object files (y or n)? y Installation completed. Would you like all the temporary files removed from this directory? (y or n) y

8. After you have done this, you need to get your environment set up. I have included some small files for you and you will need to edit them to fit your situation. Looking first at env2. (env2 to distinguish it from env which is a command instead of a file.) Here is the contents of the env2 included with this group of files. It includes a number of aliases for commands to make things easier. The aliases in env2 are helpful because, if you start a new shell and log in as the VistA user, which maybe vista, you will be able to just type gtm or GTM and roll and scroll VistA using GT.M will start right up because gtm is an alias for the command $gtm_dist/mumps -direct. (Within that command, the $gtm_dist tells the computer to substitute what ever directory gtm_dist is set to in the env2 file.) The lines you will likely need to edit to match your installation I have put in bold red type. Change to the the appropriate user if you need o and change export gtm_dist="/usr/local/gtm" to whatever you chose when you installed GT.M. Do this with a text editor. I use the command line text editor nano so I would enter nano env2 at the command line and then edit the file using the arrow keys and backspace and delete page 5 of 22

keys and then save it with Ctrl-O (press the Ctrl key and o at the same time) and Exit using Ctrl-X. There are many different text editors including GUI editiors. If you have a GUI installation, I would recommend using one of them if you are new to Linux. #!/bin/sh #put directory with r o and g in it and no trailing slash here ## for vista_home export vista_home="/home/vista/EHR"; export gtm_dist="/usr/local/gtm_V60000-64" export gtm_zinterrupt="I \$\$JOBEXAM^ZU(\$ZPOSITION)" export gtmgbldir="$vista_home/g/mumps.gld" export gtmroutines="$vista_home/o($vista_home/r) $gtm_dist" export gtm_log=/var/log alias GTM="$gtm_dist/mumps -direct" alias gtm="$gtm_dist/mumps -direct" alias mupip="$gtm_dist/mupip" alias gde="$gtm_dist/mumps -r ^GDE" alias GDE="$gtm_dist/mumps -r ^GDE" alias lke="$gtm_dist/lke" alias dse="$gtm_dist/dse" alias LKE="$gtm_dist/lke" alias DSE="$gtm_dist/dse" alias rundown="$gtm_dist/mupip rundown -r \"*\"" 9. Whenever a user such as vista logs on to a system, a file called .bashrc is run to set some things up to run certain ways for that particular user. I usually edit the .bashrc file to include setting up some things for using VistA automatically every time the user logs in. To do the same thing from yourself, add the appropriate line to the .bashrc file. The fact the name of the file begins with a period means that it is usually hidden when you list the contents of a directory with the usual command, ls, but it is there and you can see it if you add the -a after the ls, i.e., ls -a, when you list the contents of a directory. So do do this, open file /home/[your users name]/.bashrc for the user, in this case vista in a text editor, perhaps with the command nano /home/vista/.bashrc and add the line so if your user name is vista, the line is a period followed by a space and then /home/vista/EHR/env2 . /home/vista/EHR/env2

page 6 of 22

or whatever is the appropriate path to this file and save it. I usually put it near the end of the file so I can find it again. Here is the end of MY .bashrc . Yours may differ. //snip # some more ls aliases #alias ll='ls -l' #alias la='ls -A' #alias l='ls -CF' . /home/vista/EHR/env2 <======= note the space after the . # enable programmable completion features (you don't need to enable # this, if it's already enabled in /etc/bash.bashrc and /etc/profile # sources /etc/bash.bashrc). if [ -f /etc/bash_completion ]; then . /etc/bash_completion fi

10. As the VistA user, presumably vista, you will need to get your mumps.gld file pointing at the right file. You will need to be logged into Linux as the user to do this. A hint for the future, even though the mumps.gld file is largely unreadable, you can cat it and see the file it is pointing at in text, so you can figure out if things are working or not working because it is pointed at the wrong file. In this case, it will almost certainly be pointed at the wrong file. To get it pointed at the right file, do this. Type GDE should start up the global directory editor if you have the environment setup right and change the part after -file= to match your environment. If you don't do it in a sensible fashion, when you type exit, the GDE will tell you you goofed! Do not cut and paste this line in as you may end up with control characters that will cause things to not work later. This is what it looks like. Your entries are in red: vista@computer:~$ GDE %GDE-I-LOADGD, Loading Global Directory file /home/nancy/EHR/g/mumps.gld %GDE-I-VERIFY, Verification OK GDE> change -segment DEFAULT -file=/home/vista/EHR/g/mumps.dat GDE> exit %GDE-I-VERIFY, Verification OK

page 7 of 22

%GDE-I-GDUPDATE, Updating Global Directory file /home/vista/EHR/g/mumps.gld You can check to be sure it worked by entering cat /home/vista/EHR/g/mumps.gld and see if you see that file listed in there as just about the only think you can read. It should look something like this when you started, and have the appropriate changes when you try it again. I made the type small so it would fit except for what you need to see. # cat /home/vista/EHR/g/mumps.gld (note the section in red)
GTCGBDUNX005D,4#)%DEFAULTddDEFAULT/home/vista/EHR/g/mumps.dat NI.DAT002BG0031000011003128001000310000000100026400100032560010002BG0031000041024000000003100007DYNAMIC004102 4002400010000002MM00310000410240000011003100007DYNAMIC0041024002400010000 owl:/home/vista#

11. If you haven't installed xinetd in your Linux distribution, do it now. (For Debian Linux, you can install it with the command apt-get install xinetd.) To use xinetd. copy the file WVEHR-guiXINETD to the directory /etc/xinetd.d and then rename it to WVEHR-gui . You will have to be root to do this. As root in the directory that has the file WVEHR-guiXINETD, this command will copy and rename the file # cp WVEHR-guiXINETD /etc/xinetd.d/WVEHR-gui This is the contents of /etc/xinetd.d/WVEHR-gui service WVEHR-gui { port = 9211 socket_type = stream protocol = tcp user = vista server = /home/vista/EHR/WVEHR-gui type = UNLISTED wait = no disable = no }

page 8 of 22

12. Now to fix up the file it is pointed at. I would recommend putting the file WVEHR-gui in the /home/vista/EHR directory. To change the owner of the file, presuming the user is vista, as root enter chown vista:vista /home/vista/EHR/WVEHR-gui 13. This is what the /home/vista/EHR/WVEHR-gui file probably looks like and you should edit it to match your system. The log file will be automatically generated when you first connect to your system with CPRS or when testing the connection with telnet, but the path to it should be corrected if it does not match your system. #!/bin/sh #WVEHR-gui: This is a file to run RPCBroker as a Linux service # #make sure of our directory cd /home/vista/EHR date>>/home/vista/EHR/WVEHR-gui.log #Get the GTM profile source /home/vista/EHR/env2 #Run routine $gtm_dist/mumps -run GTMLNX^XWBTCPM 2>>/home/vista/EHR/WVEHRgui.log # 14. Now assuming your user is vista, change to the /home/vista/EHR/o directory and as user vista, run this command which will compile all of the *.m routines that are in ~/EHR/r . You will see a lot of errors fly by because the routines are not all written for GT.M on Linux and some routines have pieces written for several operating systems in one routine. Just ignore them and wait until it finishes compiling the routines. If you didn't use a symbolic link /usr/local/gtm then fix that line /usr/local/gtm/mumps to be right. This command is tricky as there is a single space between {} and \; and if you don't get that right, you will be have a bad time! This may take a long time depending upon the speed of your processor, etc. cd /home/vista/EHR/o find ../r -iname *.m -exec /usr/local/gtm_V60000-64/mumps {} \; 15. If you have not left the shell of user vista, log out and log back in to get the .bashrc to run so that the gtm command will work (as the .bashrc is run). Now start up gtm with the command, gtm . Note that the alias set up by the env2 script run from .bashrc should start up gtm just like it made the command GDE work. You will see a GTM> prompt if this works.

page 9 of 22

16. Set your DUZ=1 and edit your Taskman Site Parameters. In this example, the BOX:VOLUME pair was set at EHR:owl but you will need to reset it to match the name of your machine. BE CAREFUL to match the upper and lower case letters in your machine name exactly. In this example, it was changed from owl to debian. Setting your DUZ=1 gives you the privileges of the user with the internal entry number of 1 in file 200, which is the NEW PERSON file. (Eventually you will set yourself up with an Access and Verify code to use instead of the DUZ and to use with CPRS.) (As a general rule, setting your DUZ=1 in any installation of VistA will work, including this one, for this step.) If after it says INPUT TO WHAT FILE: ******// you have something different than you see below, that is just the last file that was used is displayed where the ****** is, so put in Taskman after the // and hit enter. It will complete the entry and take you where you need to go. Note that it is IMPORTANT to FIRST select the old BOX:VOLUME pair and then change it to the new BOX:VOLUME pair. The part that is red is what you type in. You only need to type in enough to uniquely identify a menu item and press [Enter] for the entry to be completed for you. The ^ is used to back out of a part of the chart when you enter it. vista@debian:~$ gtm GTM>S DUZ=1 GTM>D Q^DI VA FileMan 22.0 Select OPTION: 1 ENTER OR EDIT FILE ENTRIES

INPUT TO WHAT FILE: DEVICE// TASKMAN SITE PARAMETERS (1 entry) <=== Note that the DEVICE// might be something else here. It is the name of the last file edited, which, in this case, was DEVICE. EDIT WHICH FIELD: ALL// [Press Enter here] Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ?

<==Type ? here

Answer with TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: EHR:owl <===THIS Location on the page IS WHAT IT IS set at AND YOU page 10 of 22

MUST SELECT IT You may enter a new TASKMAN SITE PARAMETERS, if you wish Answer must be 3-30 characters in length. The value for the current account is EHR:debian <== This is what you must change it to Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: EHR:owl <==Select BOX-VOLUME PAIR: EHR:owl// EHR:debian <===Change RESERVED: [Press Enter here] LOG TASKS?: NO//[Press Enter here] DEFAULT TASK PRIORITY: 7// [Press Enter here] TASK PARTITION SIZE: 100// [Press Enter here] SUBMANAGER RETENTION TIME: 20// [Press Enter here] TASKMAN JOB LIMIT: 100// ^ 17. After changing this, you will need to go in and get rid of the tasks still set to run on the wrong BOX:VOLUME pair. In this example instance, I am going to get rid of those running on EHR:owl that begin ^%ZTSCH("SUB","EHR:owl" DO this CAREFULLY. You are doing a direct global edit here and if you do it wrong, you may just want to give up and switch out that mumps.dat with your backup copy. Use cut and paste to make the kill statements to minimize your chance of goofing up. The statements the cut and paste were take from are bolded here. What you see in your installation will not exactly match this, but look carefully for the entries with SUB and the old box volume pair, which may be EHR:owl. In this instance, what is the important part is bolded. GTM>D ^%G Output device: <terminal>: [Press Enter here] List ^%ZTSCH ^%ZTSCH("ER")="" ^%ZTSCH("ER",60577,50636)="NEWSUB+2^%ZTM, Global variable undefined: ^ %ZTSCH(""S UB"",150372994,-%GTM-E-GVUNDEF" ^%ZTSCH("ER",60577,50636,1)="Caused by the manager." ^%ZTSCH("IDLE")=5234137497 ^%ZTSCH("MON","EHR:owl",60577)="0^^^^^^^^^^^^^^0^0^1^0^0^1^0^0^0^0^" ^ %ZTSCH("MON","EHR:owl",60578)="0^0^0^0^0^0^0^0^0^0^0^0^0^0^0^0^0^0^0^0 page 11 of 22

^0^0^0 ^0^" ^%ZTSCH("STOP","MGR","EHR:owl")="60580,25521" ^%ZTSCH("STOP","MGR","EHR:debian")="60580,25521" ^%ZTSCH("STOP","SUB","EHR:owl")="60580,25524" ^%ZTSCH("STOP","SUB","EHR:debian")="60580,25524" ^%ZTSCH("SUB","EHR:owl")=0 ^%ZTSCH("SUB","EHR:owl",0)=0 ^%ZTSCH("SUB","EHR:debian")=0 ^%ZTSCH("SUB","EHR:debian",0)=0 List ^[Press Enter here] GTM>K ^%ZTSCH("SUB","EHR:owl") GTM>K ^%ZTSCH("SUB","EHR:owl",0)

18. Now you can start Taskman. You enter what is in red and press enter. The program will automatically complete uniquely identified menu items with as little as a one letter entry. vista@debian:~$ gtm GTM>D ^XUP S DUZ=9 Setting up programmer environment This is a TEST account. Terminal Type set to: C-VT320 Select OPTION NAME: EVE 1 EVE Systems Manager Menu 2 EVENT CAPTURE (ECS) EXTRACT AU ECX ECS SOURCE AUDIT Event Capture (ECS) Extract Audit 3 EVENT CAPTURE DATA ENTRY ECENTER Event Capture Data Entry 4 EVENT CAPTURE EXTRACT ECXEC Event Capture Extract 5 EVENT CAPTURE MANAGEMENT MENU ECMGR Event Capture Management Menu Press <RETURN> to see more, '^' to exit this list, OR page 12 of 22

CHOOSE 1-5: 1 EVE

Systems Manager Menu

WARNING -- TASK MANAGER DOESN'T SEEM TO BE RUNNING!!!! Select Systems Manager Menu Option: taskman Management WARNING -- TASK MANAGER DOESN'T SEEM TO BE RUNNING!!!! Select Taskman Management Option: taskman Management Utilities Select Taskman Management Utilities Option: restart Task Manager ARE YOU SURE YOU WANT TO RESTART TASKMAN? NO//yes (YES) Restarting...TaskMan restarted! Select Taskman Management Utilities Option: monitor Task Manager

Checking Taskman. Current $H=60580,26006 (Nov 11, 2006@07:13:26) RUN NODE=60580,25999 (Nov 11, 2006@07:13:19) Taskman is current.. Checking the Status List: Node weight status time $J EHR:debian RUN T@07:13:19 4135 Main Loop Checking the Schedule List: Taskman has no tasks scheduled. Checking the IO Lists: There are no tasks waiting for devices. Checking the Job List: There are no tasks waiting for partitions. Checking the Task List: There are no tasks currently running. On node EHR:debian there is 1 free Sub-Manager(s). Status: Run Enter monitor action: UPDATE// ^ If you see something like this, then you probably did not first select the old box:volume pair and then change it in the earlier step. It may be easier to go back and unpack a new page 13 of 22

mumps.tar.gz than it is to try to get help fixing this. Checking Taskman. Current $H=61007,7240 (Jan 12, 2008@02:00:40) RUN NODE=EHR:debianva is the wrong type in taskman site parameters. (EHR:debian is the wrong type in taskman site parameters.) Taskman is late by 5271012025 seconds. not running.. Checking the Status List: Node weight status time $J

Now you can jump to the manage Mailman menu by using an upcaret and requesting that menu because you entered it as a secondary menu and you have the key for it. Select Taskman Management Utilities Option: ^MANAGE MAILMAN Select Manage Mailman Option: ? Check MailMan Files o! E!!o!s C!eate a Mail"o# o! a $se! %isk Space Management &&& G!o$p'%ist!i"$tion Management &&& Local %eli(e!) Management &&& MailMan Site *a!amete!s Net+o!k Management &&& Ne+ Feat$!es o! Managing MailMan ,emote MailLink %i!ecto!) Men$ &&& Ente! ?? o! mo!e options- ??? o! help te#t& o! "!ie .esc!iptions- ?O*TION

Select Manage Mailman Option: Local %eli(e!) Management Select Local %eli(e!) Management Option: sta!t "ackg!o$n. // 0ackg!o$n. File!s +ill sta!t soon& 11 Select Local %eli(e!) Management Option: 19. Now to set yourself up as the system manager with a lot of privileges to manage and program and use CPRS instead of stealing the identity of user 9. Follow along with these entries and make the entries that are in RED. For the Access and Verify Code, it is suggested you use all upper case alphabetic characters when you use characters because although CPRS has case sensitive Access and Verify codes, not all Applications for VistA do and if you try to log into page 14 of 22 ile!

them, you will be rejected until all of the conversions to case sensitive codes are made.
GTM1S %U234 GTM1% ^5U* Setting $p p!og!amme! en(i!onment This is a TEST acco$nt& Te!minal T)pe set to: C67T488 9o$ ha(e :8 ne+ messages& Select O*TION NAME: GTM1% ;^%I 7A FileMan <<&8 Select O*TION: 4 ENTE, O, E%IT FILE ENT,IES

IN*UT TO =>AT FILE: %,UG'' <88 NE= *E,SON ?@: ent!iesA E%IT =>IC> FIEL%: ALL'' BE9S 4 BE9S ?m$ltipleA < BE9ST,OBES F,OM LM =* C>OOSE 46<: 4 BE9S ?m$ltipleA E%IT =>IC> BE9S SU06FIEL%: ALL'' CEnte!D T>EN E%IT FIEL%: C*,S TA0 ?m$ltipleA E%IT =>IC> C*,S TA0 SU06FIEL%: ALL'' T>EN E%IT FIEL%: *,IMA,9 MENU O*TION T>EN E%IT FIEL%: SECON%A,9 MENU O*TIONS ?m$ltipleA E%IT =>IC> SECON%A,9 MENU O*TIONS SU06FIEL%: ALL'' T>EN E%IT FIEL%: %ISUSE, T>EN E%IT FIEL%: AUT>O,I2E% TO =,ITE ME% O,%E,S T>EN E%IT FIEL%: ,EST,ICT *ATIENT SELECTION T>EN E%IT FIEL%: ACCESS CO%E =ant to e.it ACCESS CO%E ?9'NA T>EN E%IT FIEL%: 7E,IF9 4 7E,IF9 CO%E =ant to e.it 7E,IF9 CO%E ?9'NA < 7E,IF9 CO%E ne(e! e#pi!es C>OOSE 46<: 4 =ant to e.it 7E,IF9 CO%E ?9'NA T>EN E%IT FIEL%: *E,SON CLASS ?m$ltipleA E%IT =>IC> *E,SON CLASS SU06FIEL%: ALL'' T>EN E%IT FIEL%: ELECT,ONIC SIGNATU,E CO%E T>EN E%IT FIEL%: CEnte!D STO,E T>ESE FIEL%S IN TEM*LATE: CEnte!D Select NE= *E,SON NAME: LastName- Fi!stName 33)o$! name he!e A!e )o$ a..ing ELastName- Fi!stNameF as a ne+ NE= *E,SON ?the @GT>A? No'' )es ?9esA Checking SOUN%E5 o! matches&

page 15 of 22

No matches o$n.& NE= *E,SON INITIAL: FL NE= *E,SON MAIL CO%E: CEnte!D Select BE9: O,ES 333*h)sician Be) ,E7IE= %ATE: CEnte!D Select BE9: 5U*,OG 4 5U*,OG < 5U*,OGMO%E C>OOSE 46<: 4 5U*,OG ,E7IE= %ATE: CEnte!D Select BE9: 5U*,OGMO%E ,E7IE= %ATE: CEnte!D Select BE9: %G SENSITI7IT9 ,E7IE= %ATE: CEnte!D Select BE9: 5UMG, ,E7IE= %ATE: CEnte!D Select BE9: 5UMG,'' 5MMG, ,E7IE= %ATE: CEnte!D Select BE9: Select BE9: CEnte!D Select C*,S TA0: CO, C*,S GUI Hco!eH ta"s& A!e )o$ a..ing ICO,I as a ne+ C*,S TA0 ?the 4ST o! this NE= *E,SONA? No'' )es ?9esA EFFECTI7E %ATE: T ?JUL 4K- <88LA E5*I,ATION %ATE: CEnte!D Select C*,S TA0: Select C*,S TA0: *,IMA,9 MENU O*TION: E7E 4 E7E S)stems Manage! Men$ < E7ENT CA*TU,E ?ECSA E5T,ACT AU EC5 ECS SOU,CE AU%IT E(ent Capt$!e ?ECSA E#t!act A$.it M E7ENT CA*TU,E %ATA ENT,9 ECENTE, E(ent Capt$!e %ata Ent!) : E7ENT CA*TU,E E5T,ACT EC5EC E(ent Capt$!e E#t!act G E7ENT CA*TU,E MANAGEMENT MENU ECMG, E(ent Capt$!e Management Men$ *!ess /,ETU,N1 to see mo!e- I^I to e#it this list- O, C>OOSE 46G: 4 E7E S)stems Manage! Men$ Select SECON%A,9 MENU O*TIONS: O, C*,S GUI C>A,T C*,SCha!t (e!sion 4&8&<K& @K A!e )o$ a..ing IO, C*,S GUI C>A,TI as a ne+ SECON%A,9 MENU O*TIONS ?the 4ST o! this NE= *E,SONA? No'' )es ?9esA S9NON9M: CEnte!D Select SECON%A,9 MENU O*TIONS: O, C*,S GUI C>A,T'' MANAGE MAILMAN 5MMG, Man age Mailman A!e )o$ a..ing I5MMG,I as a ne+ SECON%A,9 MENU O*TIONS ?the <N% o! this NE= * E,SONA? No'' )es ?9esA S9NON9M: Select SECON%A,9 MENU O*TIONS: CEnte!D %ISUSE,: NO NO /33 this .isa"les a $se! i it is set to 9es AUT>O,I2E% TO =,ITE ME% O,%E,S: 9ES 9ES

page 16 of 22

,EST,ICT *ATIENT SELECTION: NO NO =ant to e.it ACCESS CO%E ?9'NA: 9 Ente! a ne+ ACCESS CO%E />i..en1: NNNNNNNNNN *lease !e6t)pe the ne+ co.e to sho+ that I ha(e it !ight: NNNNNNNNNN OB- Access co.e has "een change.O The 7E,IF9 CO%E has "een .elete. as a sec$!it) meas$!e& 9o$ +ill nee. to ente! a ne+ 7E,IF9 co.e so the $se! can sign6on& =ant to e.it 7E,IF9 CO%E ?9'NA: 9 Ente! a ne+ 7E,IF9 CO%E: NNNNNNNNNN *lease !e6t)pe the ne+ co.e to sho+ that I ha(e it !ight: NNNNNNNNNN OB- 7e!i ) co.e has "een change.O

Select Person Class: physicians 1 PHYSICIANS Allopathic and Osteopathic Physicians 390200000X Resident, Allopathic (includes Interns, Residents, Fellows) 2 PHYSICIANS Allopathic and Osteopathic Physicians 390200000X Resident, Osteopathic (includes Interns, Residents, Fellows) 3 PHYSICIANS Allopathic and Osteopathic Physicians 204C00000X Neuromusculoskeletal Medicine, Sports Medicine 4 PHYSICIANS Allopathic and Osteopathic Physicians 204D00000X Neuromusculoskeletal Medicine and OMM 5 PHYSICIANS Allopathic and Osteopathic Physicians 204E00000X Oral and Maxillofacial Surgery Press <RETURN> to see more, '^' to exit this list, OR CHOOSE 1-5: 1 Are you adding 'Allopathic and Osteopathic Physicians' as a new PERSON CLASS (the 1st for this NEW PERSON)? No// Yes Effective Date:// T Expiration Date: <=== just hit enter here ELECTRONIC SIGNATURE CODE: <Hidden>// ******* <===it will not be hidden when you type it the first time 20. Finally, put an up caret (often called and up arrow) until you get back to the OPTION prompt. At the option prompt, enter 5 for Inquire Into File Entry. At output from what file just hit enter because you are already in the New Person File. At the Select New Person Name, Enter your name. At Another One, Hit Enter and for Standard Caption output, enter Y and for Computed fields, put B for both. The response will be a page full of data showing the entries you have made and at the upper left hand corner will be a number called the DUZ, which is the internal entry number for that user. Back out to the EHR prompt and enter S DUZ= and then put the number you found in the steps above. The at the prompt type this CAREFULLY S $P(^VA(200,DUZ,0),"^",4)="@"

page 17 of 22

Here is how it all looks for the user we just set up:
Select NE= *E,SON NAME: ^

Select O*TION: G

IN;UI,E TO FILE ENT,IES

OUT*UT F,OM =>AT FILE: NE= *E,SON'' Select NE= *E,SON NAME: LASTNAME-FI,STNAME FL ANOT>E, ONE: STAN%A,% CA*TIONE% OUT*UT? 9es''CEnte!D ?9esA Incl$.e COM*UTE% iel.s: ?N'9','0A: NO'' 0OT> Comp$te. Fiel.s an. ,eco!. N$m"e! ?IENA %IS*LA9 AU%IT T,AIL? No''CEnte!D NO NUM0E,: 74 ===THIS IS THE LOCATION OF THE NUMBER YOU NEED NAME: LASTNAME-FI,STNAME INITIAL: LF ACCESS CO%E: />i..en1 %ISUSE,: NO %ATE 7E,IF9 CO%E LAST C>ANGE%: A*, 48-<88G 7E,IF9 CO%E: />i..en1 %ATE ENTE,E%: JUL 4K- <88L C,EATO,: =7E>,-*ATC> INSTALLE, Ent!) Last E.it %ate: JUL 4K- <88L NAME COM*ONENTS: <88 SIGNATU,E 0LOCB *,INTE% NAME: LASTNAME-FI,STNAME BE9: 5U*,OG GI7EN 09: =7E>,-*ATC> INSTALLE, %ATE GI7EN: JUL 4K- <88L BE9: 5UMG, GI7EN 09: =7E>,-*ATC> INSTALLE, %ATE GI7EN: JUL 4K- <88L BE9: 5U*,OGMO%E GI7EN 09: =7E>,-*ATC> INSTALLE, %ATE GI7EN: JUL 4K- <88L BE9: O,ES GI7EN 09: =7E>,-*ATC> INSTALLE, %ATE GI7EN: JUL 4K- <88L BE9: %G SENSITI7IT9 GI7EN 09: =7E>,-*ATC> INSTALLE, %ATE GI7EN: JUL 4K- <88L *,IMA,9 MENU O*TION: E7E SECON%A,9 MENU O*TIONS: O, C*,S GUI C>A,T TIMESTAM*: K44PM-GKG:: Ente! ,ETU,N to contin$e o! I^I to e#it: C*,S TA0: CO, EFFECTI7E %ATE: JUL 4K- <88L C*,S TA0: ,*T EFFECTI7E %ATE: JUL 4K- <88L AUT>O,I2E% TO =,ITE ME% O,%E,S: 9ES %ATE ACCESS CO%E LAST C>ANGE% ?cA: JUL 4K-<88L *,O7I%E, BE9 ?cA: 8 Select NE= *E,SON NAME: Select O*TION: GTM1S %U23@: /333 this nee.s to match the n$m"e! a"o(e GTM1 S Q*?^7A?<88-%U2-8A-H^H-:A3HRH GTM1h

page 18 of 22

21. Now restart xinetd with this command as you are almost ready to connect CPRS and you have made some changes that may affect xinetd from when you initially installed it. /etc/init.d/xinetd restart Then after restarting xinetd, check netstat to be sure there is a listener started netstat -a | grep 9211 <== grep is to find 9211 in the output of the command You should get this return tcp 0 0 *:9211 *:* LISTEN

And if you don't see anything, try restarting xinetd one more time or stopping and starting xinetd with /etc/init.d/xinetd stop and then /etc/init.d/xinetd start. 24. Now is the time for what may be close to the greatest moment in your VistA experience, the first time you get CPRS to connect. Go to https://sourceforge.net/projects/worldvistaehr/files/WorldVistA_EHR_2.0/ and download CPRSChart_27.90ForWVEHR-2.0-Ver10-12Files.zip Unzip this CPRS specific for WorldVistA EHR 2.0 and place the files in C:\Program Files\ Create a shortcut to the CPRS*exe file and drag it to wherever you would like it to be. Edit the target line adding what you see below i.e., S=127.0.0.1 P=9211 CCOW=Disable showrpcs. Click on Apply and OK.

page 19 of 22

25. Now double click on the shortcut and enter the access and verify codes where indicated, all caps.

page 20 of 22

26. I would like to briefly address journaling an replication of your database. If you wish to be sure that the work you do with this instance of VistA can be recovered in the event of a power failure or another problem with hardware, etc., you are going to want to use journaling and database replication. This can be accomplished using GT.M in a manner which will cause only the loss of transactions that are not completed when the failure occurs. Journal files should be kept on a disk separate from the disk that VistA is kept on and replication should preferably be done to a machine very remote from the primary machine for maximum safety of your data. Documentation for GT.M and how to accomplish journaling and replication can be found here:
http://www.fidelityinfoservices.com/fnfis/markets/nonfinancialindustries/healthcare/gtm/userdocumentation

You can also learn more from using the GT.M Acculturation Live CD that can be found on Sourceforge.net in the GT.M area here: http: sourceforge.net pro!ects fis"gtm files GT.M#$%Acculturation#$%&or'shop %.(

page 21 of 22

To get )ourself started *hile )ou are learning to set up GT.M for !ournaling and replication+ turn on !ournaling li'e this after shutting do*n Tas'man and the bac'ground filers and logging ever)one off the ,istA database:
m$pip set 6So$!nal 3Hena"le-on-"e o!eH 6 ile 'home'(ista'E>,'g'm$mps&.at

and *hen )ou stop !ournaling


m$pip set 6 ile 'home'(ista'E>,'g'm$mps&.at 6So$!nal3.isa"le

and *hen )ou restart !ournaling after an abnormal or normal shutdo*n m$pip So$!nal 6!eco(e! 6"ack+a!. m$mps&mSl and to re"enalble !ournaling -ere is an e.ample of *hat )ou *ill see *hen the !ournal file is created in home vista
nanc)/o*l:01 mupip set "!ournal23enable+on+before+filename2 home vista 4-5 !ournalfiles nanc).m!l3 "file home nanc) 4-5 g mumps.dat #GTM"6"78LC54AT4+ 7ournal file home vista 4-5 !ournal"files nanc).m!l created for database file home nanc) 4-5 g mumps.dat *ith 94:;54<6MAG4S #GTM"6"78LSTAT4+ 7ournaling state for database file home vista 4-5 g mumps.dat is no* ;8 T; 54=4AT+ this !ournal file should be *ritten to another machine. This can be done b) mounting a remote director) locall) under home vista 4-5 !ournal"files and *riting to it or b) various other means.

27. ;nce ever)thing is *or'ing for )ou+ if this is not a test s)stem+ )ou can disable an) users )ou do not *ish to have active b) finding them and setting the D6S>S45 in the 8e* =erson :ile to Y4S e.cept )ou do not *ant to do that for the &,4-5+=ATC- 68STALL45+ the =;STMAST45+ and probabl) also for some of the application pro.) users such as L5LA9+-L+ L5LA9+ =;C+ etc. You can use a :ileman Search to find them in the 84&=45S;8 file. This is !ust one of man) things )ou *ill need to do to configure the s)stem for clinical use. You could also change all of the access and verif) codes as )ou changed them above *hen )ou created the ne* highl) privileged user.

page 22 of 22

You might also like