https://vistapedia.com/api.php?action=feedcontributions&feedformat=atom&user=JohnLeoZVistApedia - User contributions [en]2026-04-30T10:38:31ZUser contributionsMediaWiki 1.43.0https://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=8383Setting up a VISTA Printer2009-12-12T19:20:23Z<p>JohnLeoZ: /* GT.M pipe for print DEVICE: */</p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
__TOC__<br />
=== GT.M pipe for print DEVICE: ===<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simple, secure, and elegant method can be used:<br />
<br />
* To begin, [[Begin_Configuration_of_Vista#Update_the_Devices,_Start_Taskman_and_Mail_a_Message|Update the Devices]] file. To create a new DEVICE, enter an unused NAME of your choice.<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use [[FILE_3.5|TYPE:OTHER]] rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. For example, one can write: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103". Set it to give us 12 characters/inch, 8 lines/inch and a 1 inch left margin). And then set IO to that device." <br />
<br />
FileMan will then send his output to that IO device, the just-defined pipe. <br />
<br />
Finally, the POST-CLOSE EXECUTE simply closes the pipe. And it's gone. No Linux /tmp/print.txt file to clean up. No fuss, no muss. <br />
<br />
Another option is to define the device with option raw:<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P 1100A -o raw"")::""pipe"" s IO=""p"""<br />
And then the SUBTYPE can manage the details of formating... Portrait vs Landscape and fonts, etc.<br />
----<br />
==== [[pipe to identify CUPS printers]] ====<br />
<br />
--[[User:JohnLeoZ|JL.Z]] Aug 2009<br />
----<br />
<br />
=== VistA output to a temporary Linux file (Calling ^TMGPRNTR) ===<br />
<br />
Below is an older way of setting up a Linux printer.<br />
<br />
Here is the DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
--[[User:Kdtop|Kdtop]] 10:34, 18 Sep 2005)<br />
----<br />
=== '''Linux /tmp/file (With ZSYSTEM call)''' ===<br />
<br />
On a Linux system with CUPS.<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----</div>JohnLeoZhttps://vistapedia.com/index.php?title=Astronaut_README-FIRST.txt&diff=7612Astronaut README-FIRST.txt2009-10-16T22:50:13Z<p>JohnLeoZ: </p>
<hr />
<div>== Astronaut WorldVistA ==<br />
<br />
Installers for Linux Beta 0.7 (Falling with Style!) (see WorldVistA license below)<br />
<br />
Description: Installs WorldVistA EHR/VOE 1.0 via rpm (Fedora/RedHat) or dpkg (.deb file Ubuntu/Debian)<br />
<br />
Downloads: http://sourceforge.net/projects/worldvistaautoi/files/<br />
<br />
Changes: Mostly minor changes and fixes to ensure that multiple instances work using a simple bash-style default override file and the --force option. This release anticipates ewd-for-astronaut to work soon. gpg signing is now present in rpm, deb to follow.<br />
<br />
Default ID's and passwords: System Linux id for an instance now follow the VistA Standard Base spec of <branding>vista<instance> to avoid conflict and allow multiple instances to run side by side. For example worldvistaEHR is the default Linux id for rpm install with password vista!123. The default VistA id is sys.admin vista!123.<br />
<br />
Author: Ignacio Valdes <ivaldes@hal-pc.org><br />
<br />
Contributors of code, modules or other in Alphabetic order (Ommitted? Don't want to appear? Let me know.)<br />
<br />
Individuals:<br />
Anthracite, Nancy -- Original install document, general knowledge.<br />
Bodtke, Peter -- Testing, documentation.<br />
Bhaskar, KS -- GT.M, Acculturation documentation, architecture, shell scripts.<br />
Dorsey, Jon -- VistA Standard Base co-proposer.<br />
Hagood, Eddie -- TMG-GUI-Config and fixes.<br />
Habiel, Sam -- BMX functionality, GUI-Scheduling.<br />
Landis, "Gus" -- VistA Standard Base co-proposer.<br />
Noorden, Lars -- Mupip man page.<br />
Meiling, Ben -- VistA Standard Base co-proposer.<br />
Papillion, Anthony -- VistA Standard Base co-proposer.<br />
Pardue, Andy -- OVID.<br />
Self, Jim -- m2web<br />
Tai, Jonathan -- GT.M knowledge, VistA Standard Base, rpm wizardry.<br />
Timson, George -- Pointed out IHS fix for SSN problem.<br />
Toppenberg, Kevin -- TMG-CPRS, TMG-GUI-Config, TMGIDE, general knowledge.<br />
Trotter, Fred -- VistA Standard Base co-proposer.<br />
Trotter, Rick -- Assistance with Launchpad.<br />
Watson, Steve -- Testing, documentation, VistA Standard Base co-proposer.<br />
Whitby, Butch -- Testing, , VistA Standard Base co-proposer, Misc.<br />
Whitten, David -- Global expertise, debugging, architecture, IPv6 patch. <br />
<br />
Corporations:<br />
Fidelity Information Services -- GT.M<br />
Medsphere Systems Corp -- OVID, Other.<br />
M/Gateway Developments Ltd -- EWD<br />
WorldVistA -- Processed FOIA VistA/VOE.<br />
<br />
Government:<br />
Indian Health Service -- BMX, scheduling GUI.<br />
Veterans Affairs -- FOIA VistA.<br />
<br />
Problems, comments, bugs: Post problems or issues to the Hardhats group: http://groups.google.com/group/Hardhats or to <ivaldes@hal-pc.org><br />
<br />
License: Installer: Affero GNU GPL version 3. No warranties expressed or implied, use at your own risk. (see WorldVistA license below)<br />
<br />
This installer has been tested on Fedora 10 and Ubuntu 9.<br />
<br />
To install on rpm based systems, log in as root:<br />
<br />
# yum install -y --nogpg astronaut-<version info>.rpm<br />
<br />
Will install all depencencies and then the rpm or somewhat independently:<br />
<br />
# rpm -i astronaut-wv-server-installer-XXX-0.X-X.i386.rpm<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
# rpm -e astronaut-wv-server-installer-XXXX-0.X-X<br />
<br />
(NOTE: the absence of .i386.rpm for uninstalling)<br />
<br />
To install on .deb, dpkg apt-get based systems, use sudo or sudo su to log in as root:<br />
<br />
# dpkg -i astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
# dpkg -r astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
You can over-ride the default installation parameters: location, port, etc by creating a file called astro-defaults in /, (rpm apparently can only find it in /). You should probably only try to change the default vista_instance but all changeable defaults are:<br />
<br />
gtm_path="/opt/lsb-gtm/gtm"<br />
export gtm_dist=$gtm_path<br />
gtm_group="gtm"<br />
#gtm_path="/opt/lsb-gtm/V5.3-004A_i686"<br />
vista_instance="EHR"<br />
vista_path="/opt/worldvista/$vista_instance"<br />
VISTAUSER="worldvista$vista_instance"<br />
VISTAUSER_PASSWD="vista!123"<br />
VISTAGROUP="worldvista$vista_instance"<br />
TEXTUSER="text$vista_instance"<br />
TEXTUSER_PASSWD="not#1sostrong"<br />
instance_client_port=9260<br />
vista_port_old_rpc=9210<br />
vista_port_vistalink=8002<br />
astro_vers_release="0.7.5"<br />
gtm_vers_release="V5.3-004A"<br />
<br />
Alter the above parameters as desired before running the rpm and it will override the above defaults.<br />
<br />
Follow the next steps after the rpm install has run. This gets you to the point of being able to login as a text or CPRS client. The pre-set Access Code is: sys.admin with Verify Code: vista!123. You will have to re-set the verify code upon first login. Download the Windows client installers which should all work out of the box with this server. The pre-set Linux id is worldvistaEHR password is vista!123 which you will also have to re-set on first login to the Linux worldvistaEHR id. To start m2web simply start or restart apache then go to step 10 here: http://vista.vmth.ucdavis.edu/notebook/index/48.html<br />
<br />
Features:<br />
<br />
1) Conforms to VistA Standard Base 0.9 RC 10.<br />
2) Quick install.<br />
3) Automatically sets BOX:VOLUME pair!<br />
4) Creates a text<instance> id, automatically edits, compiles and installs Bhaskar's runzu so that text<instance> runs with no shell and no home directory.<br />
5) Relatively smaller download size 155Mb complete package containing all files.<br />
6) Controller software such as vistactl.sh start | stop | restart, xinetd listener automatically configured and installed.<br />
7) Automatic vista startup with journaling on server start and graceful shutdown. Bhaskar's code.<br />
8) Automatically opens CPRS port.<br />
9) Has a backup solution (some assembly required).<br />
10) Latest WorldVistA and gtm V53004A<br />
11) Installs /opt/worldvista/EHR<br />
12) Creates default vista id automatically.<br />
13) Management commands: copy_this_vista_to.sh and change_client_port.sh and uninstall_this_vista.sh<br />
14) Requires two-factor deletion to really delete an instance. rpm -e only removes symlinks to log files, text-client id and auto-start routines. Requires explicit rm -Rf to really delete it all. rpm -i --force will NOT over-write an existing instance.<br />
15) Checks for file wv-rpm-defaults and overrides default install parameters for different locations for the install.<br />
16) Port handling files correspond to worldvista name spaces.<br />
17) Pre-installs m2web. Start or restart apache then go to step 10 here: http://vista.vmth.ucdavis.edu/notebook/index/48.html Turn off and on SELinux between boots by: echo 0 >/selinux/enforce or echo 1 >/selinux/enforce<br />
18) Refreshed: Pre-installs Kevin Toppenberg's debugger, see http://vistapedia.net for activation.<br />
19) Pre-installs EWD (currently broken).<br />
20) Pre-installs OVID.<br />
21) Pre-installs Victory Programming Environment, see http://vistapedia.net for activation.<br />
# 22) MSC Fileman 1034 Had to be removed as it was causing a problem. Stay tuned!<br />
23) TMG-CPRS support with all associated bug fixes.<br />
24) TMG-GUI-Config now supports user management.<br />
25) BMX RPC broker and necessary parts pre-loaded.<br />
26) GUI-Scheduling components pre-loaded.<br />
27) Man page for mupip command.<br />
<br />
Caveats:<br />
<br />
1) Beta installer.<br />
<br />
<br />
WorldVistA EHR /VOE 1.0 Release 6-2008<br />
<br />
IMPORTANT FOR ALL PROVIDERS:<br />
<br />
All drugs that the provider may need must be entered into the database<br />
BEFORE THE PROVIDER PRESCIBES THEM from WorldVistA EHR.THE DRUG FILE<br />
INCLUDED HAS NOT BEEN PREVIOUSLY RELEASED. IT IS ALWAYS IMPERATIVE THAT<br />
ANY AND ALL DRUG ORDERS AND PRESCRIPTIONS BE CAREFULLY REVIEWED BY THE<br />
PRESCRIBING PHYSICIAN AND DISPENSING PHARMACIST TO INSURE ACCURACY. IF<br />
PROBLEMS ARE FOUND, PLEASE REPORT THEM HERE<br />
<br />
INFO@WORLDVISTA.ORG<br />
OR<br />
http://trac.opensourcevista.net/worldvistaehr<br />
<br />
Please see this link for information about entering new drugs and drug<br />
doseages:<br />
<br />
<http://worldvista.org/World_VistA_EHR/license-and-readme/ReadMe%20-%20WorldVistA%20Pharmacy%20Drug%20File%202008-01-31.pdf><br />
<br />
Please look for additional information and updates about this release<br />
here:<br />
<br />
<http://worldvista.org/World_VistA_EHR/license-and-readme><br />
<br />
All portions of this release that are modified from the original Freedom<br />
of Informtion Act release provided by the Department of Veterans Affairs<br />
carry the GPL license and are Copyright WorldVistA. See this URL for the<br />
<br />
full text of the license:<br />
<br />
http://worldvista.org/World_VistA_EHR/license-and-readme/WorldVistA%20EHR%20GPL%20License.txt<br />
<br />
YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING<br />
THIS PRODUCT. DOWNLOADING OR USING ANY PART OF THE SOFTWARE AND<br />
DOCUMENTATION INDICATES THAT YOU ACCEPT THESE TERMS AND CONDITIONS. IF<br />
YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT<br />
PROCEED.<br />
<br />
A. General Disclaimer. THE WORLDVISTA-EHR (WV-EHR) SOFTWARE IS<br />
PROVIDED TO RECIPIENT HEREUNDER "AS IS" AND ANY USE OF WV-EHR SOFTWARE BY<br />
REQUESTOR SHALL BE AT ITS OWN RISK. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, WORLDVISTA AND ITS CONTRACTORS, EMPLOYEES AND AGENTS<br />
DISCLAIM ALL WARRANTIES WITH RESPECT TO WV-EHR SOFTWARE, EXPRESS, IMPLIED<br />
AND STATUTORY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF<br />
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY,<br />
COMPLETENESS, TIMELINESS, NON INFRINGEMENT OF THIRD-PARTY RIGHTS, NON<br />
INTERFERENCE, AND ERROR FREE SERVICE. WORLDVISTA TAKES NO RESPONSIBILITY<br />
<br />
FOR MONITORING OR REGULATING THE USE OR ACCURACY OF WV-EHR SOFTWARE.<br />
RECIPIENT ACKNOWLEDGES AND AGREES THAT WORLDVISTA IS UNDER NO OBLIGATION<br />
TO VERIFY THE ACCURACY OF OR OTHERWISE UPDATE WV-EHR SOFTWARE OR ANY<br />
CONTENT CONTAINED THEREIN OR TO NOTIFY RECIPIENT OF ANY INACCURACIES<br />
THEREIN OR UPDATES THERETO THAT MAY COME TO THE ATTENTION OF OR BE<br />
DEVELOPED BY WORLDVISTA. WV-EHR MAY BE UPDATED PERIODICALLY, AND IT IS<br />
THE RESPONSIBILITY OF THE RECIPIENT TO OBTAIN UPDATED VERSIONS OF THE<br />
WV-EHR RELEASE AS REQUIRED. WORLDVISTA BEARS NO RESPONSIBILITY FOR<br />
PROVIDING UPDATES TO RECIPIENTS. PASSWORD IS asdTYU<br />
<br />
B. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF ITS EMPLOYEES, AGENTS OR<br />
CONTRACTORS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL,<br />
CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION DAMAGES<br />
FOR LOST PROFITS OR REVENUES, GOODWILL, WORK STOPPAGE, SECURITY BREACHES,<br />
VIRUSES, COMPUTER FAILURE OR MALFUNCTION, USE, DATA OR OTHER INTANGIBLE<br />
LOSSES OR COMMERCIAL DAMAGES, EVEN IF ANY OF SUCH PARTIES IS ADVISED OF<br />
THE POSSIBILITY OF SUCH LOSSES, ARISING UNDER OR IN CONNECTION WITH THIS<br />
AGREEMENT, COMPLIANCE EFFECTIVENESS STUDY TOOLS, THE USE OF OR INABILITY<br />
TO USE THE SAME, OR ANY OTHER SUBJECT MATTER HEREOF. IN ADDITION, TO THE<br />
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF<br />
ITS EMPLOYEES, AGENTS OR CONTRACTORS SHALL BE LIABLE FOR ANY LOSS OR<br />
DAMAGE SUFFERED BY RECIPIENT WHICH ARISES OUT OF OR IN CONNECTION WITH<br />
ANY INFORMATION OBTAINED BY RECIPIENT VIA OR IN CONNECTION WITH WV-EHR<br />
SOFTWARE.</div>JohnLeoZhttps://vistapedia.com/index.php?title=Astronaut_Installers&diff=5983Astronaut Installers2009-10-16T22:15:25Z<p>JohnLeoZ: </p>
<hr />
<div>[[category:Installers]]<br />
The Astronaut installers are the most advanced, easy and comprehensive way of installing WorldVistA and OpenVistA(tm). Began in January of 2009, active development continues on them. They have obsoleted many other ways of installing WorldVistA. <br />
<br />
The following excerpt comes from a thread on Hardhats[http://groups.google.com/group/Hardhats/browse_thread/thread/288b85582d62184f?hl=en#]. Download links lead to the Astronaut Installer, updated to Beta 0.7.6 (16 October 2009).<br />
[[Astronaut README-FIRST.txt]]<br />
----<br />
----<br />
[[Ignacio Valdes]] Date: Tue, 26 May 2009 01:16:00 -0500<br />
<br />
Astronaut WorldVistA Installers for Linux Beta 0.6.3 (Zoltar) (see<br />
WorldVistA license below)<br />
<br />
Description: Installs WorldVistA EHR/VOE 1.0 via rpm (Fedora/RedHat)<br />
or dpkg (.deb file Ubuntu/Debian)<br />
<br />
Downloads: <br />
* https://sourceforge.net/projects/worldvistaautoi/files<br />
<br />
Changes: This release adds full support and bug fixes to support Kevin<br />
Toppenberg's superlative TMG-CPRS! Patient registration is finally<br />
solved! This also cleans up the design to work side by side with other<br />
VSB compliant VistA's like Astronaut Nostromo (installs<br />
OpenVistA(tm)). OVID now works, m2web should work by starting or<br />
re-starting httpd. m2web does NOT work with SELinux currently and is<br />
installed but not working with .deb see below for the last few steps<br />
to get m2web to work. EWD is partially installed, but broken.<br />
<br />
Default ID's and passwords: System Linux id for an instance now follow<br />
the VistA Standard Base spec of <branding>vista<instance> to avoid<br />
conflict and allow multiple instances to run side by side. For example<br />
worldvistaEHR is the default Linux id for rpm install with password<br />
vista!123. The default VistA id is sys.admin vista!123.<br />
<br />
Author: Ignacio Valdes [http://groups.google.com/groups/profile?hl=en&enc_user=AkEOmRIAAAAjdhBNd96ium9PDiiUTs9QII73Nnd8MGuFrQYThHx-nw]<br />
<br />
Problems, comments, bugs: Post problems or issues to the Hardhats<br />
group: <br />
* http://groups.google.com/group/Hardhats or to<br />
* [http://groups.google.com/groups/profile?hl=en&enc_user=AkEOmRIAAAAjdhBNd96ium9PDiiUTs9QII73Nnd8MGuFrQYThHx-nw Ignaco Valdes]<br />
<br />
License: Installer: Affero GNU GPL version 3. No warranties expressed<br />
or implied, use at your own risk. (see WorldVistA license below)<br />
<br />
These installers have been tested on Fedora 9 and Ubuntu 9.04<br />
<br />
To install on rpm based systems, log in as root:<br />
<br />
* # rpm -i astronaut-wv-server-installer-XXX-0.X-X.i386.rpm<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
* # rpm -e astronaut-wv-server-installer-XXXX-0.X-X<br />
<br />
(NOTE: the absence of .i386.rpm for uninstalling)<br />
<br />
To install on .deb, dpkg apt-get based systems, log in as root:<br />
<br />
* # dpkg -i astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
* # dpkg -r astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
You can change the default installation parameters: location, port,<br />
etc by creating a file called wv-rpm-defaults in /, (rpm apparently<br />
can only find it in /):<br />
<pre><br />
gtm_path="/opt/lsb-gtm/V5.3-003_i686"<br />
vista_instance="EHR"<br />
vista_path="/opt/worldvista/$vista_instance"<br />
VISTAUSER="worldvista$vista_instance"<br />
VISTAGROUP="worldvista$vista_instance"<br />
port=9260<br />
vista_port_old_rpc=9210<br />
vista_port_vistalink=8002<br />
</pre><br />
<br />
Alter the above parameters as desired before running the rpm and it<br />
will override the above defaults.<br />
<br />
Follow the next steps after the rpm install has run. This gets you to<br />
the point of being able to login as a text or CPRS client. BOX:VOLUME<br />
PAIR GETS AUTOMATICALLY SET! The pre-set Access Code is: sys.admin<br />
with Verify Code: vista!123. You will have to re-set the verify code<br />
upon first login. Download the Windows client installers which should<br />
all work out of the box with this server. The pre-set Linux id is<br />
vista.world password is vista!123 which you will also have to re-set<br />
on first login to the Linux vista.world id. To start m2web simply<br />
start or restart apache then go to step 10 here:<br />
http://vista.vmth.ucdavis.edu/notebook/index/48.html<br />
<br />
Features:<br />
<br />
# Conforms to VistA Standard Base 0.9 RC 7.<br />
# Quick install.<br />
# Automatically sets BOX:VOLUME pair!<br />
# Creates a text<instance> id, automatically edits, compiles and installs Bhaskar's runzu so that text<instance> runs with no shell and no home directory.<br />
# Relatively smaller download size 155Mb complete package containing all files.<br />
# Controller software such as vistactl.sh start | stop | restart, xinetd listener automatically configured and installed.<br />
# Automatic vista startup with journaling on server start and graceful shutdown. Bhaskar's code.<br />
# Automatically opens CPRS port.<br />
# Has a backup solution (some assembly required).<br />
# Latest WorldVistA and gtm V53003<br />
# Installs /opt/worldvista/EHR<br />
# Creates default vista id automatically.<br />
# Management commands: copy_this_vista_to.sh and change_client_port.sh and uninstall_this_vista.sh<br />
# Requires two-factor deletion to really delete an instance. rpm -e only removes symlinks to log files, text-client id and auto-start routines. Requires explicit rm -Rf to really delete it all. rpm -i --force will NOT over-write an existing instance.<br />
# Checks for file wv-rpm-defaults and overrides default install parameters for different locations for the install.<br />
# Port handling files correspond to worldvista name spaces.<br />
#* M2WEB:<br />
#Pre-installs m2web. Start or restart apache then go to step 10 here: http://vista.vmth.ucdavis.edu/notebook/index/48.html Turn off and on SELinux between boots by: echo 0 >/selinux/enforce or echo 1 >/selinux/enforce <br />
# Pre-installs Kevin Toppenberg's debugger.<br />
# Pre-installs EWD (currently broken).<br />
# Pre-installs parts of Ovid (currently broken).<br />
# Pre-installs Victory Programming Environment.<br />
# MSC Fileman 1034 Had to be removed as it was causing a problem. Stay tuned!<br />
# TMG-CPRS support with all associated bug fixes!<br />
#* Caveats:<br />
# Beta installer.<br />
<br />
WorldVistA EHR /VOE 1.0 Release 6-2008<br />
<br />
IMPORTANT FOR ALL PROVIDERS:<br />
<br />
All drugs that the provider may need must be entered into the database<br />
BEFORE THE PROVIDER PRESCIBES THEM from WorldVistA EHR.THE DRUG FILE<br />
INCLUDED HAS NOT BEEN PREVIOUSLY RELEASED. IT IS ALWAYS IMPERATIVE THAT<br />
ANY AND ALL DRUG ORDERS AND PRESCRIPTIONS BE CAREFULLY REVIEWED BY THE<br />
PRESCRIBING PHYSICIAN AND DISPENSING PHARMACIST TO INSURE ACCURACY. IF<br />
PROBLEMS ARE FOUND, PLEASE REPORT THEM HERE<br />
<br />
INFO "at" WORLDVISTA.ORG<br />
OR<br />
* http://trac.opensourcevista.net/worldvistaehr<br />
<br />
Please see this link for information about entering new drugs and drug<br />
doseages:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme/ReadMe%20-%20WorldVistA%20Pharmacy%20Drug%20File%202008-01-31.pdf/view<br />
<br />
Please look for additional information and updates about this release<br />
here:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme<br />
<br />
All portions of this release that are modified from the original Freedom<br />
of Information Act release provided by the Department of Veterans Affairs<br />
carry the GPL license and are Copyright WorldVistA. See this URL for the full text of the license:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme/WorldVistA%20EHR%20GPL%20License.txt/view<br />
<br />
YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING<br />
THIS PRODUCT. DOWNLOADING OR USING ANY PART OF THE SOFTWARE AND<br />
DOCUMENTATION INDICATES THAT YOU ACCEPT THESE TERMS AND CONDITIONS. IF<br />
YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT<br />
PROCEED.<br />
<br />
A. General Disclaimer. THE WORLDVISTA-EHR (WV-EHR) SOFTWARE IS<br />
PROVIDED TO RECIPIENT HEREUNDER "AS IS" AND ANY USE OF WV-EHR SOFTWARE BY<br />
REQUESTOR SHALL BE AT ITS OWN RISK. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, WORLDVISTA AND ITS CONTRACTORS, EMPLOYEES AND AGENTS<br />
DISCLAIM ALL WARRANTIES WITH RESPECT TO WV-EHR SOFTWARE, EXPRESS, IMPLIED<br />
AND STATUTORY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF<br />
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY,<br />
COMPLETENESS, TIMELINESS, NON INFRINGEMENT OF THIRD-PARTY RIGHTS, NON<br />
INTERFERENCE, AND ERROR FREE SERVICE. WORLDVISTA TAKES NO RESPONSIBILITY<br />
<br />
FOR MONITORING OR REGULATING THE USE OR ACCURACY OF WV-EHR SOFTWARE.<br />
RECIPIENT ACKNOWLEDGES AND AGREES THAT WORLDVISTA IS UNDER NO OBLIGATION<br />
TO VERIFY THE ACCURACY OF OR OTHERWISE UPDATE WV-EHR SOFTWARE OR ANY<br />
CONTENT CONTAINED THEREIN OR TO NOTIFY RECIPIENT OF ANY INACCURACIES<br />
THEREIN OR UPDATES THERETO THAT MAY COME TO THE ATTENTION OF OR BE<br />
DEVELOPED BY WORLDVISTA. WV-EHR MAY BE UPDATED PERIODICALLY, AND IT IS<br />
THE RESPONSIBILITY OF THE RECIPIENT TO OBTAIN UPDATED VERSIONS OF THE<br />
WV-EHR RELEASE AS REQUIRED. WORLDVISTA BEARS NO RESPONSIBILITY FOR<br />
PROVIDING UPDATES TO RECIPIENTS. PASSWORD IS asdTYU<br />
<br />
B. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF ITS EMPLOYEES, AGENTS OR<br />
CONTRACTORS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL,<br />
CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION DAMAGES<br />
FOR LOST PROFITS OR REVENUES, GOODWILL, WORK STOPPAGE, SECURITY BREACHES,<br />
VIRUSES, COMPUTER FAILURE OR MALFUNCTION, USE, DATA OR OTHER INTANGIBLE<br />
LOSSES OR COMMERCIAL DAMAGES, EVEN IF ANY OF SUCH PARTIES IS ADVISED OF<br />
THE POSSIBILITY OF SUCH LOSSES, ARISING UNDER OR IN CONNECTION WITH THIS<br />
AGREEMENT, COMPLIANCE EFFECTIVENESS STUDY TOOLS, THE USE OF OR INABILITY<br />
TO USE THE SAME, OR ANY OTHER SUBJECT MATTER HEREOF. IN ADDITION, TO THE<br />
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF<br />
ITS EMPLOYEES, AGENTS OR CONTRACTORS SHALL BE LIABLE FOR ANY LOSS OR<br />
DAMAGE SUFFERED BY RECIPIENT WHICH ARISES OUT OF OR IN CONNECTION WITH<br />
ANY INFORMATION OBTAINED BY RECIPIENT VIA OR IN CONNECTION WITH WV-EHR<br />
SOFTWARE.<br />
<br />
----<br />
I, Valdes Date: Tue, 26 May 2009 07:18:19 -0700 (PDT)<br />
Forgot to add that I have packaged Kevin's TMG-CPRS into an easy to<br />
install point-click installer:<br />
<br />
* https://sourceforge.net/project/platformdownload.php?group_id=255113<br />
<br />
To download the TMG-CPRS client installer, it is the one in the big<br />
green button called astronaut-tmg-cprs-client-alpha-0.1.exe<br />
<br />
Let me know if the dimensions of the Select Patient dialog box are<br />
funny where some of the buttons are off screen or not.<br />
<br />
Congratulations to the T's: Kevin T and George T, this one is for<br />
you!<br />
<br />
The windows-vm appliance I hope to have up by today as well.<br />
<br />
-- IV<br />
<br />
---- <br />
steve wang Date: Tue, 26 May 2009 06:57:38 -0800<br />
<br />
Hi All:<br />
<br />
What is the official website for WorldVistA EHR/VOE 1.0. It doesn't seem<br />
like this is on the worldvista website. Where can I find more documentation<br />
on this new version? Also, how can I find out about new releases of EHR/VOE<br />
when they come out?<br />
<br />
Thanks<br />
<br />
Steve<br />
---- <br />
Nancy Anthracite Date: Tue, 26 May 2009 11:07:12 -0400<br />
<br />
New releases of WorldVistA EHR will be announced on Hardhats.<br />
<br />
---- <br />
K.S. Bhaskar Date: Tue, 26 May 2009 08:31:29 -0700 (PDT)<br />
<br />
Steve --<br />
<br />
The official web site for WorldVistA EHR is the WorldVistA web site<br />
<br />
* http://worldvista.org <br />
<br />
The distribution point for WorldVistA EHR is Source Forge <br />
* http://sourceforge.net/projects/worldvista-ehr<br />
<br />
and the WorldVistA web site points you to the Source Forge site.<br />
<br />
Built on the release of WorldVistA EHR from Source Forge are<br />
distributions of repackaged software, sometimes with enhancements.<br />
Ignacio's Astronaut packages are an example. By way of analogy, the<br />
WorldVistA EHR distributions are like Linux kernels from http://kernel.org<br />
whereas the redistributions are like GNU/Linux distributions from<br />
Debian, Red Hat, Ubuntu, etc.<br />
<br />
New releases of WorldVistA EHR will appear on Source Forge, and will<br />
be announced on hardhats, as well as elsewhere.<br />
<br />
Regards<br />
-- Bhaskar<br />
<br />
K.S. Bhaskar<br />
President, WorldVistA<br />
---- <br />
I, Valdes Date: Tue, 26 May 2009 19:36:05 -0700 (PDT)<br />
<br />
Kevin,<br />
<br />
I've used TMG-CPRS all day today and I must say that the integrated<br />
patient registration works phenomenally well. Especially when you are<br />
under pressure and have lots of distractions. Not having to bring up<br />
the text based interface or switch back and forth between them is a<br />
dramatic improvement as well as the ability to edit spelling mistakes<br />
quickly and easily.<br />
<br />
Question: what are you using to render html in notes?<br />
<br />
-- IV<br />
----<br />
----<br />
<br />
I, Valdes Date: Wed, 17 Jun 2009 14:46:07 -0700 (PDT)<br />
<br />
FYI, I just released Astronaut WorldVistA Beta 0.6.4 on rpm and deb on<br />
sourceforge.net<br />
<br />
Changes: After 5 months of intermittent not workings and me just not<br />
getting it, iptables (server firewall) rule addition and removal on<br />
uninstall for the client port now should work correctly and reliably.<br />
The very useful but hard to find or access gtm_acculturation document<br />
is now installed in the doc directory by default. There is also few<br />
dependency checking tweaks in anticipation of the VistA Community<br />
Meeting demo this Friday in Bethesda.<br />
<br />
-- IV</div>JohnLeoZhttps://vistapedia.com/index.php?title=Astronaut_Installers&diff=5884Astronaut Installers2009-10-16T22:13:04Z<p>JohnLeoZ: </p>
<hr />
<div>[[category:Installers]]<br />
The Astronaut installers are the most advanced, easy and comprehensive way of installing WorldVistA and OpenVistA(tm). Began in January of 2009, active development continues on them. They have obsoleted many other ways of installing WorldVistA. <br />
<br />
The following excerpt comes from a thread on Hardhats[http://groups.google.com/group/Hardhats/browse_thread/thread/288b85582d62184f?hl=en#]. Download links lead to the Astronaut Installer, updated to Beta 0.7.6 (16 October 2009).<br />
<br />
----<br />
----<br />
[[Ignacio Valdes]] Date: Tue, 26 May 2009 01:16:00 -0500<br />
<br />
Astronaut WorldVistA Installers for Linux Beta 0.6.3 (Zoltar) (see<br />
WorldVistA license below)<br />
<br />
Description: Installs WorldVistA EHR/VOE 1.0 via rpm (Fedora/RedHat)<br />
or dpkg (.deb file Ubuntu/Debian)<br />
<br />
Downloads: <br />
* https://sourceforge.net/projects/worldvistaautoi/files<br />
<br />
Changes: This release adds full support and bug fixes to support Kevin<br />
Toppenberg's superlative TMG-CPRS! Patient registration is finally<br />
solved! This also cleans up the design to work side by side with other<br />
VSB compliant VistA's like Astronaut Nostromo (installs<br />
OpenVistA(tm)). OVID now works, m2web should work by starting or<br />
re-starting httpd. m2web does NOT work with SELinux currently and is<br />
installed but not working with .deb see below for the last few steps<br />
to get m2web to work. EWD is partially installed, but broken.<br />
<br />
Default ID's and passwords: System Linux id for an instance now follow<br />
the VistA Standard Base spec of <branding>vista<instance> to avoid<br />
conflict and allow multiple instances to run side by side. For example<br />
worldvistaEHR is the default Linux id for rpm install with password<br />
vista!123. The default VistA id is sys.admin vista!123.<br />
<br />
Author: Ignacio Valdes [http://groups.google.com/groups/profile?hl=en&enc_user=AkEOmRIAAAAjdhBNd96ium9PDiiUTs9QII73Nnd8MGuFrQYThHx-nw]<br />
<br />
Problems, comments, bugs: Post problems or issues to the Hardhats<br />
group: <br />
* http://groups.google.com/group/Hardhats or to<br />
* [http://groups.google.com/groups/profile?hl=en&enc_user=AkEOmRIAAAAjdhBNd96ium9PDiiUTs9QII73Nnd8MGuFrQYThHx-nw Ignaco Valdes]<br />
<br />
License: Installer: Affero GNU GPL version 3. No warranties expressed<br />
or implied, use at your own risk. (see WorldVistA license below)<br />
<br />
These installers have been tested on Fedora 9 and Ubuntu 9.04<br />
<br />
To install on rpm based systems, log in as root:<br />
<br />
* # rpm -i astronaut-wv-server-installer-XXX-0.X-X.i386.rpm<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
* # rpm -e astronaut-wv-server-installer-XXXX-0.X-X<br />
<br />
(NOTE: the absence of .i386.rpm for uninstalling)<br />
<br />
To install on .deb, dpkg apt-get based systems, log in as root:<br />
<br />
* # dpkg -i astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
IT IS NORMAL TO SEE A BUNCH OF ERROR MESSAGES DURING COMPILATION.<br />
<br />
To uninstall:<br />
<br />
* # dpkg -r astronaut-wv-server-installer-XXXX_0.X-0.X.deb<br />
<br />
You can change the default installation parameters: location, port,<br />
etc by creating a file called wv-rpm-defaults in /, (rpm apparently<br />
can only find it in /):<br />
<pre><br />
gtm_path="/opt/lsb-gtm/V5.3-003_i686"<br />
vista_instance="EHR"<br />
vista_path="/opt/worldvista/$vista_instance"<br />
VISTAUSER="worldvista$vista_instance"<br />
VISTAGROUP="worldvista$vista_instance"<br />
port=9260<br />
vista_port_old_rpc=9210<br />
vista_port_vistalink=8002<br />
</pre><br />
<br />
Alter the above parameters as desired before running the rpm and it<br />
will override the above defaults.<br />
<br />
Follow the next steps after the rpm install has run. This gets you to<br />
the point of being able to login as a text or CPRS client. BOX:VOLUME<br />
PAIR GETS AUTOMATICALLY SET! The pre-set Access Code is: sys.admin<br />
with Verify Code: vista!123. You will have to re-set the verify code<br />
upon first login. Download the Windows client installers which should<br />
all work out of the box with this server. The pre-set Linux id is<br />
vista.world password is vista!123 which you will also have to re-set<br />
on first login to the Linux vista.world id. To start m2web simply<br />
start or restart apache then go to step 10 here:<br />
http://vista.vmth.ucdavis.edu/notebook/index/48.html<br />
<br />
Features:<br />
<br />
# Conforms to VistA Standard Base 0.9 RC 7.<br />
# Quick install.<br />
# Automatically sets BOX:VOLUME pair!<br />
# Creates a text<instance> id, automatically edits, compiles and installs Bhaskar's runzu so that text<instance> runs with no shell and no home directory.<br />
# Relatively smaller download size 155Mb complete package containing all files.<br />
# Controller software such as vistactl.sh start | stop | restart, xinetd listener automatically configured and installed.<br />
# Automatic vista startup with journaling on server start and graceful shutdown. Bhaskar's code.<br />
# Automatically opens CPRS port.<br />
# Has a backup solution (some assembly required).<br />
# Latest WorldVistA and gtm V53003<br />
# Installs /opt/worldvista/EHR<br />
# Creates default vista id automatically.<br />
# Management commands: copy_this_vista_to.sh and change_client_port.sh and uninstall_this_vista.sh<br />
# Requires two-factor deletion to really delete an instance. rpm -e only removes symlinks to log files, text-client id and auto-start routines. Requires explicit rm -Rf to really delete it all. rpm -i --force will NOT over-write an existing instance.<br />
# Checks for file wv-rpm-defaults and overrides default install parameters for different locations for the install.<br />
# Port handling files correspond to worldvista name spaces.<br />
#* M2WEB:<br />
#Pre-installs m2web. Start or restart apache then go to step 10 here: http://vista.vmth.ucdavis.edu/notebook/index/48.html Turn off and on SELinux between boots by: echo 0 >/selinux/enforce or echo 1 >/selinux/enforce <br />
# Pre-installs Kevin Toppenberg's debugger.<br />
# Pre-installs EWD (currently broken).<br />
# Pre-installs parts of Ovid (currently broken).<br />
# Pre-installs Victory Programming Environment.<br />
# MSC Fileman 1034 Had to be removed as it was causing a problem. Stay tuned!<br />
# TMG-CPRS support with all associated bug fixes!<br />
#* Caveats:<br />
# Beta installer.<br />
<br />
WorldVistA EHR /VOE 1.0 Release 6-2008<br />
<br />
IMPORTANT FOR ALL PROVIDERS:<br />
<br />
All drugs that the provider may need must be entered into the database<br />
BEFORE THE PROVIDER PRESCIBES THEM from WorldVistA EHR.THE DRUG FILE<br />
INCLUDED HAS NOT BEEN PREVIOUSLY RELEASED. IT IS ALWAYS IMPERATIVE THAT<br />
ANY AND ALL DRUG ORDERS AND PRESCRIPTIONS BE CAREFULLY REVIEWED BY THE<br />
PRESCRIBING PHYSICIAN AND DISPENSING PHARMACIST TO INSURE ACCURACY. IF<br />
PROBLEMS ARE FOUND, PLEASE REPORT THEM HERE<br />
<br />
INFO "at" WORLDVISTA.ORG<br />
OR<br />
* http://trac.opensourcevista.net/worldvistaehr<br />
<br />
Please see this link for information about entering new drugs and drug<br />
doseages:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme/ReadMe%20-%20WorldVistA%20Pharmacy%20Drug%20File%202008-01-31.pdf/view<br />
<br />
Please look for additional information and updates about this release<br />
here:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme<br />
<br />
All portions of this release that are modified from the original Freedom<br />
of Information Act release provided by the Department of Veterans Affairs<br />
carry the GPL license and are Copyright WorldVistA. See this URL for the full text of the license:<br />
<br />
* http://worldvista.org/World_VistA_EHR/license-and-readme/WorldVistA%20EHR%20GPL%20License.txt/view<br />
<br />
YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING<br />
THIS PRODUCT. DOWNLOADING OR USING ANY PART OF THE SOFTWARE AND<br />
DOCUMENTATION INDICATES THAT YOU ACCEPT THESE TERMS AND CONDITIONS. IF<br />
YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT<br />
PROCEED.<br />
<br />
A. General Disclaimer. THE WORLDVISTA-EHR (WV-EHR) SOFTWARE IS<br />
PROVIDED TO RECIPIENT HEREUNDER "AS IS" AND ANY USE OF WV-EHR SOFTWARE BY<br />
REQUESTOR SHALL BE AT ITS OWN RISK. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, WORLDVISTA AND ITS CONTRACTORS, EMPLOYEES AND AGENTS<br />
DISCLAIM ALL WARRANTIES WITH RESPECT TO WV-EHR SOFTWARE, EXPRESS, IMPLIED<br />
AND STATUTORY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF<br />
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY,<br />
COMPLETENESS, TIMELINESS, NON INFRINGEMENT OF THIRD-PARTY RIGHTS, NON<br />
INTERFERENCE, AND ERROR FREE SERVICE. WORLDVISTA TAKES NO RESPONSIBILITY<br />
<br />
FOR MONITORING OR REGULATING THE USE OR ACCURACY OF WV-EHR SOFTWARE.<br />
RECIPIENT ACKNOWLEDGES AND AGREES THAT WORLDVISTA IS UNDER NO OBLIGATION<br />
TO VERIFY THE ACCURACY OF OR OTHERWISE UPDATE WV-EHR SOFTWARE OR ANY<br />
CONTENT CONTAINED THEREIN OR TO NOTIFY RECIPIENT OF ANY INACCURACIES<br />
THEREIN OR UPDATES THERETO THAT MAY COME TO THE ATTENTION OF OR BE<br />
DEVELOPED BY WORLDVISTA. WV-EHR MAY BE UPDATED PERIODICALLY, AND IT IS<br />
THE RESPONSIBILITY OF THE RECIPIENT TO OBTAIN UPDATED VERSIONS OF THE<br />
WV-EHR RELEASE AS REQUIRED. WORLDVISTA BEARS NO RESPONSIBILITY FOR<br />
PROVIDING UPDATES TO RECIPIENTS. PASSWORD IS asdTYU<br />
<br />
B. LIMITATION OF LIABILITY. TO THE MAXIMUM EXTENT PERMITTED BY<br />
APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF ITS EMPLOYEES, AGENTS OR<br />
CONTRACTORS SHALL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL,<br />
CONSEQUENTIAL OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION DAMAGES<br />
FOR LOST PROFITS OR REVENUES, GOODWILL, WORK STOPPAGE, SECURITY BREACHES,<br />
VIRUSES, COMPUTER FAILURE OR MALFUNCTION, USE, DATA OR OTHER INTANGIBLE<br />
LOSSES OR COMMERCIAL DAMAGES, EVEN IF ANY OF SUCH PARTIES IS ADVISED OF<br />
THE POSSIBILITY OF SUCH LOSSES, ARISING UNDER OR IN CONNECTION WITH THIS<br />
AGREEMENT, COMPLIANCE EFFECTIVENESS STUDY TOOLS, THE USE OF OR INABILITY<br />
TO USE THE SAME, OR ANY OTHER SUBJECT MATTER HEREOF. IN ADDITION, TO THE<br />
MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, NEITHER WORLDVISTA NOR ANY OF<br />
ITS EMPLOYEES, AGENTS OR CONTRACTORS SHALL BE LIABLE FOR ANY LOSS OR<br />
DAMAGE SUFFERED BY RECIPIENT WHICH ARISES OUT OF OR IN CONNECTION WITH<br />
ANY INFORMATION OBTAINED BY RECIPIENT VIA OR IN CONNECTION WITH WV-EHR<br />
SOFTWARE.<br />
<br />
----<br />
I, Valdes Date: Tue, 26 May 2009 07:18:19 -0700 (PDT)<br />
Forgot to add that I have packaged Kevin's TMG-CPRS into an easy to<br />
install point-click installer:<br />
<br />
* https://sourceforge.net/project/platformdownload.php?group_id=255113<br />
<br />
To download the TMG-CPRS client installer, it is the one in the big<br />
green button called astronaut-tmg-cprs-client-alpha-0.1.exe<br />
<br />
Let me know if the dimensions of the Select Patient dialog box are<br />
funny where some of the buttons are off screen or not.<br />
<br />
Congratulations to the T's: Kevin T and George T, this one is for<br />
you!<br />
<br />
The windows-vm appliance I hope to have up by today as well.<br />
<br />
-- IV<br />
<br />
---- <br />
steve wang Date: Tue, 26 May 2009 06:57:38 -0800<br />
<br />
Hi All:<br />
<br />
What is the official website for WorldVistA EHR/VOE 1.0. It doesn't seem<br />
like this is on the worldvista website. Where can I find more documentation<br />
on this new version? Also, how can I find out about new releases of EHR/VOE<br />
when they come out?<br />
<br />
Thanks<br />
<br />
Steve<br />
---- <br />
Nancy Anthracite Date: Tue, 26 May 2009 11:07:12 -0400<br />
<br />
New releases of WorldVistA EHR will be announced on Hardhats.<br />
<br />
---- <br />
K.S. Bhaskar Date: Tue, 26 May 2009 08:31:29 -0700 (PDT)<br />
<br />
Steve --<br />
<br />
The official web site for WorldVistA EHR is the WorldVistA web site<br />
<br />
* http://worldvista.org <br />
<br />
The distribution point for WorldVistA EHR is Source Forge <br />
* http://sourceforge.net/projects/worldvista-ehr<br />
<br />
and the WorldVistA web site points you to the Source Forge site.<br />
<br />
Built on the release of WorldVistA EHR from Source Forge are<br />
distributions of repackaged software, sometimes with enhancements.<br />
Ignacio's Astronaut packages are an example. By way of analogy, the<br />
WorldVistA EHR distributions are like Linux kernels from http://kernel.org<br />
whereas the redistributions are like GNU/Linux distributions from<br />
Debian, Red Hat, Ubuntu, etc.<br />
<br />
New releases of WorldVistA EHR will appear on Source Forge, and will<br />
be announced on hardhats, as well as elsewhere.<br />
<br />
Regards<br />
-- Bhaskar<br />
<br />
K.S. Bhaskar<br />
President, WorldVistA<br />
---- <br />
I, Valdes Date: Tue, 26 May 2009 19:36:05 -0700 (PDT)<br />
<br />
Kevin,<br />
<br />
I've used TMG-CPRS all day today and I must say that the integrated<br />
patient registration works phenomenally well. Especially when you are<br />
under pressure and have lots of distractions. Not having to bring up<br />
the text based interface or switch back and forth between them is a<br />
dramatic improvement as well as the ability to edit spelling mistakes<br />
quickly and easily.<br />
<br />
Question: what are you using to render html in notes?<br />
<br />
-- IV<br />
----<br />
----<br />
<br />
I, Valdes Date: Wed, 17 Jun 2009 14:46:07 -0700 (PDT)<br />
<br />
FYI, I just released Astronaut WorldVistA Beta 0.6.4 on rpm and deb on<br />
sourceforge.net<br />
<br />
Changes: After 5 months of intermittent not workings and me just not<br />
getting it, iptables (server firewall) rule addition and removal on<br />
uninstall for the client port now should work correctly and reliably.<br />
The very useful but hard to find or access gtm_acculturation document<br />
is now installed in the doc directory by default. There is also few<br />
dependency checking tweaks in anticipation of the VistA Community<br />
Meeting demo this Friday in Bethesda.<br />
<br />
-- IV</div>JohnLeoZhttps://vistapedia.com/index.php?title=Quality_Management_and_Reporting&diff=11640Quality Management and Reporting2009-09-25T23:46:49Z<p>JohnLeoZ: </p>
<hr />
<div>== Place holder for Matt King ==</div>JohnLeoZhttps://vistapedia.com/index.php?title=Old_Main&diff=6049Old Main2009-09-25T23:44:50Z<p>JohnLeoZ: /* Overview of VistA */</p>
<hr />
<div>This wiki covers questions regarding the VistA software, the various components of that software, and configuration and installation of the same. It incorporates information from many people. We have been repeatedly vandalized by people trying to advance their google page rank, hence this is now a closed community wiki.<br />
<br />
To get access, contact David Whitten ( whitten at worldvista.org ) through an e-mail,<br />
or phone 713 870 3834 to get an account.<br />
Please send a contact telephone number with your e-mail, and/or<br />
have an e-mail address ready when you call. (I need both.)<br />
Please decide on your preferred User name.<br />
We have provided a [[User Status|page]] for new users and their current status.<br />
Thank you. <br />
<br />
__TOC__<br />
<br />
Configuration is the process of changing details about a VistA package. <br />
These details are fine level controls over the behaviour of the package.<br />
<br />
=== Overview of VistA ===<br />
* [[Basic Questions]]<br />
* [[Frequently Asked Questions]]<br />
* [[VistA System Components]]<br />
* [[Documentation Overview]]<br />
** [[Glossary of Terms]] ([[Glossary Template]])<br />
* [[FileMan Overview]] (with details also)<br />
* [[Kernel Overview]]<br />
* [[Operating Systems Overview]]<br />
* [[VistA Packages Overview]]<br />
** [[CPRS Overview]]<br />
* [[M2Web Overview]]<br />
* [[Quality Management and Reporting]]<br />
<br />
=== Programming VistA Topics ===<br />
* [[Programming VistA Issues | Programming VistA Issues (submenu with multiple entries)]]<br />
* [[Victory Programmer Environment (VPE) Installation]]<br />
* [[Programming Languages Overview]]<br />
<br />
=== Collaboration Tools ===<br />
* [[OpenForum]]<br />
* Message Board (read only): http://www.mail-archive.com/hardhats-members@lists.sourceforge.net/<br />
* [[CHC Corner]] for ''' Community Health Centers ''' discussion/wish list/collaboration/etc.<br />
* [[From Hardhats Listserve:]]<br />
<br />
=== Projects Information ===<br />
* Information is available at the [[Projects_List]] page<br />
<br />
=== Installation Guides ===<br />
* [[Installation Overview]]<br />
* [[Installation How To VistA GT.M Linux]]<br />
* [[Installation How To VistA GT.M Ubuntu Linux | Installation How To VistA GT.M Ubuntu Linux including VistALink (Java)]]<br />
* [[Migrating a VistA/GT.M installation from one platform to another]]<br />
* [[Installation How To VistA/Cache]]<br />
* [[Introducing VistA VivA 0.1]]<br />
* [[Hardware Issues]]<br />
* [[CPRS Installation]]<br />
* [[VistALink]]<br />
* [[EsiObjectsRegistration | VistA GUI Registration (Based on EsiObjects)]]<br />
<br />
=== Installation of VistA Demos ===<br />
* [[Installation How To VistA/GT.M coLinux]]<br />
* [[Using the VistA Appliance]]<br />
<br />
=== Configuration of Packages ===<br />
* [[Configuration Overview]]<br />
* [[Register a Patient]]<br />
* [[HL7 Multi-Listener]]<br />
<br />
=== Volunteer Opportunities with WorldVistA ===<br />
* [[Volunteer Coordinator]]<br />
* [[Planning for VistA Advances]]<br />
* [[Advocating VistA]]<br />
* [[Documenting VistA]]<br />
* [[Organization and Planning For VistA Community Meeting]]<br />
* [[Recording Results Of A VistA Community Meeting]]<br />
* [[Categorizing Needs For New VistA Packages]]<br />
* [[Developing New VistA Packages]]<br />
* [[Administration Of OpenForum]]<br />
* [[VistA Community Weekly Conference Call]]<br />
<br />
=== Working Groups ===<br />
*[[Software Development (WG1)]]<br />
*[[Education and Training (WG2)]]<br />
*[[Finance (WG3)]]<br />
*[[Membership and Community (WG4)]]<br />
*[[International (WG5)]]<br />
<br />
=== [[Community Meeting]] ===<br />
* [[VistA Community Meeting Q1 2006]]<br />
* [[VistA Community Meeting Q2 2006]]<br />
* [[VCM Boston 2005]]<br />
<br />
=== [[Weekly Conference Calls]] ===<br />
<br />
=== Details about this page ===<br />
To limit vandalism, this page has been write-protected. If you need to make modifications to this page,<br />
contact DavidWhitten, who will help you make changes. Thank you for your support.<br />
=== Details of this website's software ===<br />
<br />
This Wiki is based on the mediawiki software. [[Unique Features of Forum Wiki]]<br />
<br />
Please see [http://meta.wikipedia.org/wiki/MediaWiki_i18n documentation on customizing the interface]<br />
and the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage and configuration help.<br />
<br />
Editing help see http://meta.wikimedia.org/wiki/Help:Editing#Sections.2C_paragraphs.2C_lists_and_lines</div>JohnLeoZhttps://vistapedia.com/index.php?title=What_version_of_MUMPS_am_I_using_%3F&diff=5760What version of MUMPS am I using ?2009-08-25T15:26:21Z<p>JohnLeoZ: /* Cache */</p>
<hr />
<div>*The version is in the Intrinsic Special Variable $ZVersion:<br />
==GT.M==<br />
<br />
*Start up GT.M. If you have your environment set up to do so, simply type "gtm".<br />
<br />
<pre><br />
~$ gtm<br />
<br />
GTM>W $ZVersion<br />
GT.M V5.3-004A Linux x86<br />
GTM><br />
</pre><br />
<br />
==Caché==<br />
<pre><br />
EHR>W $ZVERSION<br />
Cache for UNIX (Linux Intel/32-bit) 5.2.4 (Build 809U) Mon Feb 11 2008 10:34:22 EST<br />
<br />
or...<br />
Cache for Windows (Intel) 5.2 (Build 329) Thu Jun 15 2006 16:40:08 EDT<br />
EHR><br />
</pre><br />
[[Category:FAQ]][[Category:HOWTO]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=What_version_of_MUMPS_am_I_using_%3F&diff=5750What version of MUMPS am I using ?2009-08-25T15:22:11Z<p>JohnLeoZ: </p>
<hr />
<div>*The version is in the Intrinsic Special Variable $ZVersion:<br />
==GT.M==<br />
<br />
*Start up GT.M. If you have your environment set up to do so, simply type "gtm".<br />
<br />
<pre><br />
~$ gtm<br />
<br />
GTM>W $ZVersion<br />
GT.M V5.3-004A Linux x86<br />
GTM><br />
</pre><br />
<br />
==Cache==<br />
<pre><br />
EHR>W $ZVERSION<br />
Cache for UNIX (Linux Intel/32-bit) 5.2.4 (Build 809U) Mon Feb 11 2008 10:34:22 EST<br />
<br />
or...<br />
Cache for Windows (Intel) 5.2 (Build 329) Thu Jun 15 2006 16:40:08 EDT<br />
EHR><br />
</pre><br />
[[Category:FAQ]][[Category:HOWTO]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=9710Setting up an SSH Tunnel between CPRS & VistA2009-08-22T22:41:43Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto our Windows client machine. <br />
Download from [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html here]. We need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Now we can use plink.exe to construct an encrypted path between the local machine (127.0.0.1) and a remote location. Here the remote machine, at address 192.168.5.102, happens to be listening at port 9260. Note that the ''local'' port chosen in this example is independently set to 9210. We could have used 9260, or any port that has no conflict.<br />
<br />
Finally, on the remote machine we have added a user arbitrarily named "remoteaccess" with password "remotepw" solely to establish the tunnel. Here is the complete command to implement an encrypted path to the remote location:<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
Putty is capable of generating public/private key pairs that can replace the -pw section of the plink command [http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter8.html#pubkey "Putty Manual Chapter8"]<br />
<br />
''under construction, input welcome.''<br />
Needs more on securing user<br />
--[[User:JohnLeoZ|JL.Z]] 17:38, 22 Aug 2009 (CDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5745Setting up an SSH Tunnel between CPRS & VistA2009-08-22T22:40:24Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto our Windows client machine. <br />
Download from [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html here]. We need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Now we can use plink.exe to construct an encrypted path between the local machine (127.0.0.1) and a remote location. Here the remote machine, at address 192.168.5.102, happens to be listening at port 9260. Note that the ''local'' port chosen in this example is independently set to 9210. We could have used 9260, or any port that has no conflict.<br />
<br />
Finally, on the remote machine we have added a user arbitrarily named "remoteaccess" with password "remotepw" solely to establish the tunnel. Here is the complete command to implement an encrypted path to the remote location:<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
Putty is capable of generating public/private key pairs that can replace the -pw section of the plink command [http://the.earth.li/~sgtatham/putty/0.60/htmldoc/Chapter8.html#pubkey "Putty Manual Chapter8"]<br />
<br />
''under construction, input welcome.''<br />
Needs more on securing user<br />
--[[User:JohnLeoZ|JL.Z]] 17:38, 22 Aug 2009 (CDT)<br />
--[[User:JohnLeoZ|gra'pa Z]] 15:40, 22 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5744Setting up an SSH Tunnel between CPRS & VistA2009-08-22T16:38:09Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto our Windows client machine. <br />
Download from [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html here]. We need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Now we can use plink.exe to construct an encrypted path between the local machine (127.0.0.1) and a remote location. Here the remote machine, at address 192.168.5.102, happens to be listening at port 9260. Note that the ''local'' port chosen in this example is independently set to 9210. We could have used 9260, or any port that has no conflict.<br />
<br />
Finally, on the remote machine we have added a user arbitrarily named "remoteaccess" with password "remotepw" solely to establish the tunnel. Here is the complete command to implement an encrypted path to the remote location:<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
Needs more on securing user<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5743Setting up an SSH Tunnel between CPRS & VistA2009-08-22T16:28:54Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto our Windows client machine. <br />
Download from here: [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html http://www.chiark.greenend.org.uk]. We need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Now we can use plink.exe to construct an encrypted path between the local machine (127.0.0.1) and a remote location. Here the remote machine, at address 192.168.5.102, happens to be listening at port 9260. Note that the ''local'' port chosen in this example is independently set to 9210. We could have used 9260, or any port that has no conflict.<br />
<br />
Finally, on the remote machine we have added a user named "plinkuser" with password "plinkpw" solely to establish the tunnel. Here is the complete command to implement our tunnel:<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l plinkuser -pw plinkpw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5742Setting up an SSH Tunnel between CPRS & VistA2009-08-22T16:19:00Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto your Windows client machine. Download from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
We then can use plink.exe to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 happens to be listening at port 9260. Note that the local port chosen in this example is independently set to 9210. We could have used 9260, or any port that has no conflict.<br />
<br />
And on the remote machine we have added a user named "plinkuser" with password "plinkpw" solely to establish the tunnel. Here is the complete command to implement our tunnel:<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l plinkuser -pw plinkpw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5741Setting up an SSH Tunnel between CPRS & VistA2009-08-22T16:02:48Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto your Windows client machine. Download from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9260 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end. So you replace<br />
... -s 192.168.5.102 -p 9260 ...<br />
with<br />
... -s 127.0.0.1 -p 9210 ...<br />
and the CPRS client will connect exactly as before but now over the secure SSH tunnel.<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5740Setting up an SSH Tunnel between CPRS & VistA2009-08-22T15:50:36Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto your Windows client machine. Download from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9210 192.168.5.102<br />
<br />
translation (from plink documentation):<br />
-N Do not start a shell<br />
-ssh encrypted link<br />
-l user name on the remote system, here we have set up "remoteaccess"<br />
-pw password for the remote user, in this example it is "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
Now, if the Windows shortcut for CPRS will use the local port and address, a secure connection will be made to the remote port and address at the other end.<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5739Setting up an SSH Tunnel between CPRS & VistA2009-08-22T13:52:48Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto your Windows client machine. Download from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9210 192.168.5.102<br />
<br />
translation:<br />
-N<br />
-ssh<br />
-l user name on the remote system, here "remoteaccess"<br />
-pw password for that user, here "remotepw"<br />
-L local_port:address:remote_port remote_address<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|JL.Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5738Setting up an SSH Tunnel between CPRS & VistA2009-08-21T14:21:10Z<p>JohnLeoZ: </p>
<hr />
<div>Begin by installing putty onto your Windows client machine. Download from here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html You need the program Plink (a command-line interface to the PuTTY back ends).<br />
<br />
Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9210 192.168.5.102<br />
<br />
<br />
<br />
<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|gra'pa Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5732Setting up an SSH Tunnel between CPRS & VistA2009-08-21T14:00:03Z<p>JohnLeoZ: </p>
<hr />
<div>Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9210 192.168.5.102<br />
<br />
''under construction, input welcome.''<br />
--[[User:JohnLeoZ|gra'pa Z]] 07:00, 21 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_an_SSH_Tunnel_between_CPRS_%26_VistA&diff=5731Setting up an SSH Tunnel between CPRS & VistA2009-08-21T13:56:48Z<p>JohnLeoZ: </p>
<hr />
<div>Here is a shortcut that uses the program "plink.exe" to construct an encrypted path between the local machine (127.0.0.1) and a remote location (here it is 192.168.5.102). The remote machine at address 192.168.5.102 needs to be listening at port 9210, in this example, and has to be configured with a password (here it is "remotepw".<br />
<br />
"C:\Program Files\PuTTY\plink.exe" -N -ssh -l remoteaccess -pw remotepw -L 9210:127.0.0.1:9210 192.168.5.102</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Installation&diff=8173CPRS Installation2009-08-21T13:49:36Z<p>JohnLeoZ: </p>
<hr />
<div>__TOC__<br />
<br />
This page records the process of installation of the [[CPRS|Computerized Patient Record System]] Graphical User Interface client program on the [[Microsoft Windows OS]].<br />
<br />
=== CPRS Versions ===<br />
<br />
This table will list links for the various CPRS versions. (The most current version is at the top)<br />
<br />
{| class="grey" border="1" cellpadding="2"<br />
|+ CPRS Versions<br />
|-<br />
! Version Number<br />
! Distribution File<br />
! Availability<br />
! Date<br />
|-<br />
| version 1.0.27.83 <br />
| OR_30_304.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 05/2009<br />
|-<br />
| version 1.0.27.77 <br />
| OR_30_243.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 09/2008<br />
|-<br />
| version 1.0.26.69 <br />
| OR_30_270.zip<br />
| on http://opensourcevista.net:8888/NancysVistAServer and on ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/<br />
|-<br />
| version 1.0.26.69 <br />
| for WorldVistA EHR <br />
| on the Sourceforge WorldVistA EHR site and http://opensourcevista.net:8888/NancysVistAServer <br />
| (dated June 2007)<br />
<br />
|-<br />
| version 1.0.26.68<br />
| OR_30_258.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| Note Below (NB):(dated July 17, 2006)<br />
|-<br />
| version 1.0.25.42<br />
| OR_30_235.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety<br />
|-<br />
| version 1.0.25.40 <br />
| OR_30_231.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated May 06, 2005)<br />
|-<br />
| version 1.0.25.28 <br />
| OR_30_195.zip <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Feb 09, 2005)<br />
|-<br />
| version 1.0.24.27<br />
| OR_30_224.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Sep 03, 2004)<br />
|-<br />
| version 1.0.24.26<br />
| OR_30_190.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Aug 02, 2004)<br />
|-<br />
| version 1.0.23.15 <br />
| OR_30_187.ZIP <br />
| *Sourceforge WorldVistA and http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 02/04)<br />
|-<br />
| version 1.0.22.16<br />
| OR_30_206.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 01/04)<br />
|-<br />
| version 1.0.20.21 <br />
| OR_30_148.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 11/02)<br />
|-<br />
| version 1.0.20.21<br />
| OR_30_148.ZIP<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
|(dated about 11/02)<br />
|-<br />
| version 1.0.19.7 <br />
| OR_30_132.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 05/02)<br />
|-<br />
| version 1.0.18.2 <br />
| OR_30_125.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 12/01)<br />
|}<br />
<br />
----<br />
<br />
=== version change trick ===<br />
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:<br />
<br />
http://downloads.opensourcevista.net/VADemo9-26-06<br />
<br />
<br />
To find out which version to use, look next to the option [[OPTION OR CPRS GUI CHART|named "OR CPRS GUI CHART"]] like this example where CPRS version 1.0.23.15 was needed:<br />
<br />
D Q^DI<br />
<br />
VA FileMan 22.0<br />
Select OPTION: 5 INQUIRE TO FILE ENTRIES<br />
<br />
OUTPUT FROM WHAT FILE: DEVICE// OPTION<br />
1 OPTION (10126 entries)<br />
2 OPTION SCHEDULING (116 entries)<br />
CHOOSE 1-2: 1 OPTION (10126 entries)<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15<br />
ANOTHER ONE: <br />
<br />
To use a particular version of CPRS, the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory <br />
<br />
Thus: <br />
<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
The wget(1) utility is capable of fetching the files from this server<br />
<br />
AceFTP is a freeware FTP program that works, if needed<br />
http://software.visicommedia.com/en/productsfreeware/<br />
<br />
''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''<br />
----<br />
<br />
=== 1.0.26.69 (and TMG-CPRS) spoof --> 1.0.26.76 ===<br />
<br />
Since the changes between 1.0.26.69 and 1.0.26.76 are relatively minor, in this case, version can be used by changing the option in the option file like this:<br />
<br />
D P^DI<br />
<br />
VA FileMan 22.0<br />
<br />
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES<br />
<br />
INPUT TO WHAT FILE: OPTION//<br />
EDIT WHICH FIELD: ALL//<br />
<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.26.76<br />
NAME: OR CPRS GUI CHART//<br />
MENU TEXT: CPRSChart version 1.0.26.76 Replace 76 With 69<br />
Replace<br />
CPRSChart version 1.0.26.69<br />
----<br />
When using TMG-CPRS, another way of reaching the exact same result is to add ''' "SPOOF-VER=1.0.26.76" ''' to the end of the Windows shortcut to CPRS like so:<br />
<br />
... S=192.168.xxx.xxx P=92xx CCOW=DISABLE SPOOF-VER=1.0.26.76<br />
<br />
(This method has the (admittedly dubious) advantage of allowing ''both'' a CPRS v1.0.26.68 ''and'' a v1.0.26.76 to connect without changing the server side.<br />
<br />
'''Caution:''' One needs to know that the two versions truly are compatible or be willing to risk nasty side-effects, perhaps even damage to the server's database.<br />
----<br />
=== SSH Tunnel ===<br />
Communications between CPRS and the VistA server are not encrypted by default. Access/Verify Codes and all patient data are transmitted in the clear. However, these can be protected by setting up an encrypted "tunnel" between client and server.<br />
<br />
[[Setting up an SSH Tunnel between CPRS & VistA]]<br />
----<br />
=== Automatic Windows Installer ===<br />
<br />
The [http://sourceforge.net/projects/worldvistaautoi/files Astronaut] suite of automatic installers includes cprs, tmg-cprs and many other clients, available in point-click windows .exe installers. IP address and port number are entered by the user. <br />
----<br />
=== Wine/Crossover compatability ===<br />
<br />
[[Wine/Crossover]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=How_do_I_get_a_list_of_what_Patients_exist_in_VistA_%3F&diff=5717How do I get a list of what Patients exist in VistA ?2009-08-18T16:37:53Z<p>JohnLeoZ: </p>
<hr />
<div>There are several ways to find out what Patients exist in VistA.<br />
<br />
A simple way is to use [[VA FileMan]]:<br />
<br />
Select OPTION: PRINT FILE ENTRIES <br />
<br />
OUTPUT FROM WHAT FILE: INSTALL// 2 PATIENT (359461 entries)<br />
SORT BY: NAME// <br />
START WITH NAME: FIRST// <br />
FIRST PRINT FIELD: NUMBER<br />
THEN PRINT FIELD: NAME<br />
1 NAME <br />
2 NAME COMPONENTS <br />
CHOOSE 1-2: 1 NAME<br />
THEN PRINT FIELD: <br />
Heading (S/C): PATIENT LIST// <br />
DEVICE: HOME GENERIC TELNET TERMINAL Right Margin: 80// <br />
PATIENT LIST AUG 18,2009 11:11 PAGE 1<br />
NUMBER NAME<br />
---------------------------------------------------------------------------<br />
256807 ANDREWS,ARCHIE<br />
220870 BECK,BLUTO<br />
397624 BECK,BRUTUS<br />
111345 BOOP,BETTY<br />
348052 DUCK,DAISY<br />
179792 DUCK,DONALD<br />
264262 MOUSE,MICKEY<br />
140335 PEA,SWEET<br />
124961 OYL,OLIVE<br />
132515 THE SAILOR,POPEYE</div>JohnLeoZhttps://vistapedia.com/index.php?title=How_do_I_get_a_list_of_what_Patients_exist_in_VistA_%3F&diff=5693How do I get a list of what Patients exist in VistA ?2009-08-18T16:36:52Z<p>JohnLeoZ: </p>
<hr />
<div>There are several ways to find out what Patients exist in VistA.<br />
<br />
A simple way is to use [[VA FileMan]]:<br />
<br />
Select OPTION: PRINT FILE ENTRIES <br />
<br />
OUTPUT FROM WHAT FILE: INSTALL// 2 PATIENT (359461 entries)<br />
SORT BY: NAME// <br />
START WITH NAME: FIRST// <br />
FIRST PRINT FIELD: NUMBER<br />
THEN PRINT FIELD: NAME<br />
1 NAME <br />
2 NAME COMPONENTS <br />
CHOOSE 1-2: 1 NAME<br />
THEN PRINT FIELD: <br />
Heading (S/C): PATIENT LIST// <br />
DEVICE: HOME GENERIC TELNET TERMINAL Right Margin: 80// <br />
PATIENT LIST AUG 18,2009 11:11 PAGE 1<br />
NUMBER NAME<br />
---------------------------------------------------------------------------<br />
256807 ANDREWS,ARCHIE<br />
220870 BECK,BLUTO<br />
397624 BECK,BRUTUS<br />
111345 BOOP,BETTY<br />
348052 DUCK,DAISY<br />
179792 DUCK,DONALD<br />
264262 MOUSE,MICKEY<br />
140335 PEA,SWEET<br />
124961 OYL,OLIVE<br />
2515 THE SAILOR,POPEYE</div>JohnLeoZhttps://vistapedia.com/index.php?title=How_do_I_get_a_list_of_what_Patients_exist_in_VistA_%3F&diff=5692How do I get a list of what Patients exist in VistA ?2009-08-18T16:34:52Z<p>JohnLeoZ: </p>
<hr />
<div>There are several ways to find out what Patients exist in VistA.<br />
<br />
A simple way is to use [[VA FileMan]]:<br />
<br />
Select OPTION: PRINT FILE ENTRIES <br />
<br />
OUTPUT FROM WHAT FILE: INSTALL// 2 PATIENT (359461 entries)<br />
SORT BY: NAME// <br />
START WITH NAME: FIRST// <br />
FIRST PRINT FIELD: NUMBER<br />
THEN PRINT FIELD: NAME<br />
1 NAME <br />
2 NAME COMPONENTS <br />
CHOOSE 1-2: 1 NAME<br />
THEN PRINT FIELD: <br />
Heading (S/C): PATIENT LIST// <br />
DEVICE: HOME GENERIC TELNET TERMINAL Right Margin: 80// <br />
PATIENT LIST AUG 18,2009 11:11 PAGE 1<br />
NUMBER NAME<br />
--------------------------------------------------------------------------------<br />
256807 ANDREWS,ARCHIE<br />
220870 BECK,BLUTO<br />
397624 BECK,BRUTUS<br />
111345 BOOP,BETTY<br />
348052 DUCK,DAISY<br />
179792 DUCK,DONALD<br />
264262 MOUSE,MICKEY<br />
140335 PEA,SWEET<br />
124961 OYL,OLIVE<br />
2515 THE SAILOR,POPEYE</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Installation&diff=5698CPRS Installation2009-08-18T14:25:14Z<p>JohnLeoZ: </p>
<hr />
<div>__TOC__<br />
=== CPRS Versions ===<br />
<br />
This will list links for the various CPRS versions. (Most current at the top)<br />
<br />
{| class="grey" border="1" cellpadding="2"<br />
|+ CPRS Versions<br />
|-<br />
! Version Number<br />
! Distribution File<br />
! Availability<br />
! Date<br />
|-<br />
| version 1.0.27.83 <br />
| OR_30_304.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 05/2009<br />
|-<br />
| version 1.0.27.77 <br />
| OR_30_243.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 09/2008<br />
|-<br />
| version 1.0.26.69 <br />
| OR_30_270.zip<br />
| on http://opensourcevista.net:8888/NancysVistAServer and on ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/<br />
|-<br />
| version 1.0.26.69 <br />
| for WorldVistA EHR <br />
| on the Sourceforge WorldVistA EHR site and http://opensourcevista.net:8888/NancysVistAServer <br />
| (dated June 2007)<br />
<br />
|-<br />
| version 1.0.26.68<br />
| OR_30_258.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| Note Below (NB):(dated July 17, 2006)<br />
|-<br />
| version 1.0.25.42<br />
| OR_30_235.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety<br />
|-<br />
| version 1.0.25.40 <br />
| OR_30_231.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated May 06, 2005)<br />
|-<br />
| version 1.0.25.28 <br />
| OR_30_195.zip <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Feb 09, 2005)<br />
|-<br />
| version 1.0.24.27<br />
| OR_30_224.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Sep 03, 2004)<br />
|-<br />
| version 1.0.24.26<br />
| OR_30_190.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Aug 02, 2004)<br />
|-<br />
| version 1.0.23.15 <br />
| OR_30_187.ZIP <br />
| *Sourceforge WorldVistA and http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 02/04)<br />
|-<br />
| version 1.0.22.16<br />
| OR_30_206.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 01/04)<br />
|-<br />
| version 1.0.20.21 <br />
| OR_30_148.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 11/02)<br />
|-<br />
| version 1.0.20.21<br />
| OR_30_148.ZIP<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
|(dated about 11/02)<br />
|-<br />
| version 1.0.19.7 <br />
| OR_30_132.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 05/02)<br />
|-<br />
| version 1.0.18.2 <br />
| OR_30_125.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 12/01)<br />
|}<br />
<br />
----<br />
=== version change trick ===<br />
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:<br />
<br />
http://downloads.opensourcevista.net/VADemo9-26-06<br />
<br />
<br />
To find out which version to use, look next to the option OR CPRS GUI Chart like this where 1.0.23.15 was needed:<br />
D Q^DI<br />
<br />
VA FileMan 22.0<br />
Select OPTION: 5 INQUIRE TO FILE ENTRIES<br />
<br />
OUTPUT FROM WHAT FILE: DEVICE// OPTION<br />
1 OPTION (10126 entries)<br />
2 OPTION SCHEDULING (116 entries)<br />
CHOOSE 1-2: 1 OPTION (10126 entries)<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15<br />
ANOTHER ONE: <br />
<br />
To use a particular version of CPRS, the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory <br />
<br />
Thus: <br />
<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
The wget(1) utility is capable of fetching the files from this server<br />
<br />
AceFTP is a freeware FTP program that works, if needed<br />
http://software.visicommedia.com/en/productsfreeware/<br />
<br />
''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''<br />
----<br />
=== 1.0.26.69 (and TMG-CPRS) spoof --> 1.0.26.76 ===<br />
<br />
Since the changes between 1.0.26.69 and 1.0.26.76 are relatively minor, in this case, version can be used by changing the option in the option file like this:<br />
<br />
D P^DI<br />
<br />
VA FileMan 22.0<br />
<br />
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES<br />
<br />
INPUT TO WHAT FILE: OPTION//<br />
EDIT WHICH FIELD: ALL//<br />
<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.26.76<br />
NAME: OR CPRS GUI CHART//<br />
MENU TEXT: CPRSChart version 1.0.26.76 Replace 76 With 69<br />
Replace<br />
CPRSChart version 1.0.26.69<br />
----<br />
Another way of reaching the exact same result is to add ''' "SPOOF-VER=1.0.26.76" ''' to the end of the Windows shortcut to CPRS like so:<br />
<br />
... S=192.168.xxx.xxx P=92xx CCOW=DISABLE SPOOF-VER=1.0.26.76<br />
<br />
(This method has the (admittedly dubious) advantage of allowing ''both'' a CPRS v1.0.26.68 ''and'' a v1.0.26.76 to connect without changing the server side.<br />
<br />
'''Caution:''' One needs to know that the two versions truly are compatible or be willing to risk nasty side-effects, perhaps even damage to the server's database.<br />
----<br />
=== Automatic Windows Installer ===<br />
<br />
The [http://sourceforge.net/projects/worldvistaautoi/files Astronaut] suite of automatic installers includes cprs, tmg-cprs and many other clients, available in point-click windows .exe installers. IP address and port number are entered by the user. <br />
----<br />
=== Wine/Crossover compatability ===<br />
<br />
[[Wine/Crossover]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Installation&diff=5687CPRS Installation2009-08-18T14:10:41Z<p>JohnLeoZ: /* version change trick */</p>
<hr />
<div>__TOC__<br />
=== CPRS Versions ===<br />
<br />
This will list links for the various CPRS versions. (Most current at the top)<br />
<br />
{| class="grey" border="1" cellpadding="2"<br />
|+ CPRS Versions<br />
|-<br />
! Version Number<br />
! Distribution File<br />
! Availability<br />
! Date<br />
|-<br />
| version 1.0.27.83 <br />
| OR_30_304.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 05/2009<br />
|-<br />
| version 1.0.27.77 <br />
| OR_30_243.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 09/2008<br />
|-<br />
| version 1.0.26.69 <br />
| OR_30_270.zip<br />
| on http://opensourcevista.net:8888/NancysVistAServer and on ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/<br />
|-<br />
| version 1.0.26.69 <br />
| for WorldVistA EHR <br />
| on the Sourceforge WorldVistA EHR site and http://opensourcevista.net:8888/NancysVistAServer <br />
| (dated June 2007)<br />
<br />
|-<br />
| version 1.0.26.68<br />
| OR_30_258.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| Note Below (NB):(dated July 17, 2006)<br />
|-<br />
| version 1.0.25.42<br />
| OR_30_235.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety<br />
|-<br />
| version 1.0.25.40 <br />
| OR_30_231.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated May 06, 2005)<br />
|-<br />
| version 1.0.25.28 <br />
| OR_30_195.zip <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Feb 09, 2005)<br />
|-<br />
| version 1.0.24.27<br />
| OR_30_224.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Sep 03, 2004)<br />
|-<br />
| version 1.0.24.26<br />
| OR_30_190.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Aug 02, 2004)<br />
|-<br />
| version 1.0.23.15 <br />
| OR_30_187.ZIP <br />
| *Sourceforge WorldVistA and http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 02/04)<br />
|-<br />
| version 1.0.22.16<br />
| OR_30_206.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 01/04)<br />
|-<br />
| version 1.0.20.21 <br />
| OR_30_148.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 11/02)<br />
|-<br />
| version 1.0.20.21<br />
| OR_30_148.ZIP<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
|(dated about 11/02)<br />
|-<br />
| version 1.0.19.7 <br />
| OR_30_132.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 05/02)<br />
|-<br />
| version 1.0.18.2 <br />
| OR_30_125.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 12/01)<br />
|}<br />
<br />
=== version change trick ===<br />
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:<br />
<br />
http://downloads.opensourcevista.net/VADemo9-26-06<br />
<br />
<br />
To find out which version to use, look next to the option OR CPRS GUI Chart like this where 1.0.23.15 was needed:<br />
D Q^DI<br />
<br />
VA FileMan 22.0<br />
Select OPTION: 5 INQUIRE TO FILE ENTRIES<br />
<br />
OUTPUT FROM WHAT FILE: DEVICE// OPTION<br />
1 OPTION (10126 entries)<br />
2 OPTION SCHEDULING (116 entries)<br />
CHOOSE 1-2: 1 OPTION (10126 entries)<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15<br />
ANOTHER ONE: <br />
<br />
To use a particular version of CPRS, the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory <br />
<br />
Thus: <br />
<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
The wget(1) utility is capable of fetching the files from this server<br />
<br />
AceFTP is a freeware FTP program that works, if needed<br />
http://software.visicommedia.com/en/productsfreeware/<br />
<br />
''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''<br />
<br />
== 1.0.26.69 (and TMG-CPRS 1.0.26.76) --> ...26.76 ==<br />
<br />
Since the changes between 1.0.26.69 and 1.0.26.76 are relatively minor, in this case, version can be used by changing the option in the option file like this:<br />
<br />
D P^DI<br />
<br />
VA FileMan 22.0<br />
<br />
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES<br />
<br />
INPUT TO WHAT FILE: OPTION//<br />
EDIT WHICH FIELD: ALL//<br />
<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.26.76<br />
NAME: OR CPRS GUI CHART//<br />
MENU TEXT: CPRSChart version 1.0.26.76 Replace 76 With 69<br />
Replace<br />
CPRSChart version 1.0.26.69<br />
<br />
Another way of reaching the same result is to add ''SPOOF-VER=1.0.26.76'' to the end of the Windows shortcut to CPRS like so:<br />
<br />
... S=192.168.xxx.xxx P=92xx CCOW=DISABLE SPOOF-VER=1.0.26.76<br />
<br />
(This method has the advantage of allowing ''both'' 1.0.26.68 and 1.0.26.76 to connect without changing the server side.<br />
<br />
'''Caution:''' One needs to know that the two versions truly are compatible or be willing to risk nasty side-effects such as damage to the server.<br />
<br />
=== Automatic Windows Installer ===<br />
<br />
The [http://sourceforge.net/projects/worldvistaautoi/files Astronaut] suite of automatic installers includes cprs, tmg-cprs and many other clients, available in point-click windows .exe installers. IP address and port number are entered by the user. <br />
=== Wine/Crossover compatability ===<br />
<br />
[[Wine/Crossover]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=Pipe_to_identify_CUPS_printers&diff=11531Pipe to identify CUPS printers2009-08-17T16:08:04Z<p>JohnLeoZ: </p>
<hr />
<div>Here is a code snippet that uses the pipe device to query Linux for the names of available CUPS printers. It returns them in a MUMPS array.<br />
<br />
lpstat(DEVICE) ;;<br />
;; (CUPS has been configured with<br />
;; the desired printers defined.)<br />
;;Sample run:<br />
;; GTM>d lpstat^testing(.jlz)<br />
;; GTM>zwr<br />
;; jlz=""<br />
;; jlz("HP_LaserJet_1100A")=""<br />
;; jlz("Photosmart_192.168.5.103")=""<br />
;;<br />
New P Set P="pipe"<br />
Open P:(command="lpstat -a")::P<br />
For Use P Read DEVICE Quit:$ZEOF Do<br />
. Set DEVICE($P(DEVICE," "))=""<br />
. Quit<br />
Close P<br />
Quit<br />
<br />
Compare to GetPrinters^TMGPRNTR(Printers)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Programming_VistA_Issues&diff=6936Programming VistA Issues2009-08-15T14:07:13Z<p>JohnLeoZ: </p>
<hr />
<div>This page will cover programming issues. <br />
<br />
=== Programming Issues ===<br />
<br />
* [[M/Mumps Language Issues]]<br />
* [[TIU Package API]]<br />
* [[Batch Signing of Documents]]<br />
* [[Debugging with GT.M]]<br />
* [[CPRS Stuff]]<br />
* [[VistA Imaging Issues]]<br />
* [[Pharmacy Issues]]<br />
* [[Scheduling Issues]]<br />
* [[Add on Functions]]<br />
* [[Setting up a Linux Printer]]<br />
* [[Using a linux editor inside VistA]]<br />
* [[Lab Interfacing]]<br />
* [[Indirection (@) issues]]<br />
* [[VistA Database Globals]]<br />
* KIDS/[[Patching Instructions]]<br />
* [[Redirecting pointers]]<br />
* [[VistA Links]]<br />
* [[Object Oriented Programming with M]]<br />
* [[Programming with the VPE code library]]<br />
* [[SSH Tunneling for CPRS]]<br />
* [[GT.M Job Examine / System Status Overview]]<br />
* [[Error Trapping with $ETRAP]]<br />
* [[RPC's with Visual Cpp]]<br />
* [[VPE]]<br />
* [[Purge Old ACCESS/VERIFY Codes]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=Purge_Old_ACCESS/VERIFY_Codes&diff=9337Purge Old ACCESS/VERIFY Codes2009-08-15T14:06:26Z<p>JohnLeoZ: </p>
<hr />
<div>This code snippet is intended to replace the routine call AOLD^XUSPURGE in Menu Option XUSERAOLD. Checks for Production system, and uses new code only if system is Testing.<br />
<br />
This allows clearing all codes if desired, Option XUSERAOLD can also be scheduled in Taskman if desired.<br />
<br />
AOLD ;; check whether Production or Testing<br />
If $$PROD^XUPROD DO AOLD^XUSPURGE QUIT ;; If this is a production system, Keep the legacy 270 day minimum.<br />
;<br />
N DIRUT,DIR,XUT,XUDAYS,XUDT,XUI,XUJ,XUK,X<br />
I $D(ZTQUEUED) D Q<br />
. S X=$G(ZTQPARAM)-1 D A02^XUSPURGE(X),V02^XUSPURGE(X)<br />
. Q ;; Option can be scheduled with number of days in Parameter field<br />
W !!,"This option will purge the log of inactive access and verify codes ",!<br />
W "older than the date specified to allow for their re-use."<br />
S DIR("A")="Do you wish to continue",DIR(0)="Y",DIR("B")="NO" D ^DIR<br />
I $D(DIRUT)!(Y'=1) K DIRUT,DIR,XUT,XUDAYS,XUDT,XUI,XUJ,XUK Quit<br />
S DIR("?")="Enter a number of days indicating what date codes should be purged."<br />
S DIR("A",1)=" VHA has set the minimum time to keep old codes at 270 days."<br />
S DIR("A",2)=" But this not the VA..."<br />
S DIR("A",3)=" And this is not a Production System."<br />
S DIR("A")="So how many days back do you wish to retain codes?"<br />
S DIR("B")=30 ;; default; was 270<br />
S DIR(0)="N^0:400" ;; allowed range; was 270:400<br />
D ^DIR Q:$D(DIRUT)<br />
S X=X-1 ;; X=0 will leave Today.<br />
D A02^XUSPURGE(X),V02^XUSPURGE(X)<br />
Q</div>JohnLeoZhttps://vistapedia.com/index.php?title=Pipe_to_identify_CUPS_printers&diff=5684Pipe to identify CUPS printers2009-08-15T13:16:03Z<p>JohnLeoZ: </p>
<hr />
<div>Here is a code snippet that uses the pipe device to query Linux for the names of available CUPS printers. It returns them in a MUMPS array.<br />
<br />
lpstat(DEVICE) ;;<br />
;; (CUPS has been configured with<br />
;; the desired printers defined.)<br />
;;Sample run:<br />
;; GTM>d lpstat^testing(.jlz)<br />
;; GTM>zwr<br />
;; jlz=""<br />
;; jlz("HP_LaserJet_1100A")=""<br />
;; jlz("Photosmart_192.168.5.103")=""<br />
;;<br />
New P Set P="pipe"<br />
Open P:(command="lpstat -a")::P<br />
For Use P Read DEVICE Quit:$ZEOF Do<br />
. Set DEVICE($P(DEVICE," "))=""<br />
. Quit<br />
Close P<br />
Quit</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5751Setting up a VISTA Printer2009-08-15T13:12:37Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
__TOC__<br />
=== GT.M pipe for print DEVICE: ===<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simple, secure, and elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:OTHER rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. For example, one can write: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103". Set it to give us 12 characters/inch, 8 lines/inch and a 1 inch left margin). And then set IO to that device." <br />
<br />
FileMan will then send his output to that IO device, the just-defined pipe. <br />
<br />
Finally, the POST-CLOSE EXECUTE simply closes the pipe. And it's gone. No Linux /tmp/print.txt file to clean up. No fuss, no muss. <br />
<br />
----<br />
==== [[pipe to identify CUPS printers]] ====<br />
<br />
--[[User:JohnLeoZ|JL.Z]] Aug 2009<br />
----<br />
=== VistA output to a temporary Linux file (Calling ^TMGPRNTR) ===<br />
<br />
Below is an older way of setting up a Linux printer.<br />
<br />
Here is the DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
--[[User:Kdtop|Kdtop]] 10:34, 18 Sep 2005)<br />
----<br />
=== '''Linux /tmp/file (With ZSYSTEM call)''' ===<br />
<br />
On a Linux system with CUPS.<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5668Setting up a VISTA Printer2009-08-15T12:38:01Z<p>JohnLeoZ: /* GT.M pipe for print DEVICE: */</p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
__TOC__<br />
=== GT.M pipe for print DEVICE: ===<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simple, secure, and elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:OTHER rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. For example, one can write: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103". Set it to give us 12 characters/inch, 8 lines/inch and a 1 inch left margin). And then set IO to that device." <br />
<br />
FileMan will then send his output to that IO device, the just-defined pipe. <br />
<br />
Finally, the POST-CLOSE EXECUTE simply closes the pipe. And it's gone. No Linux /tmp/print.txt file to clean up. No fuss, no muss. <br />
<br />
----<br />
<br />
== [[pipe to identify CUPS printers]] ==<br />
<br />
----<br />
--[[User:JohnLeoZ|JL.Z]] Aug 2009<br />
<br />
=== VistA output to a temporary Linux file (Calling ^TMGPRNTR) ===<br />
<br />
Below is an older way of setting up a Linux printer.<br />
<br />
Here is the DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
--[[User:Kdtop|Kdtop]] 10:34, 18 Sep 2005)<br />
----<br />
=== '''Linux /tmp/file (With ZSYSTEM call)''' ===<br />
<br />
On a Linux system with CUPS.<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5667Setting up a VISTA Printer2009-08-15T12:35:33Z<p>JohnLeoZ: /* GT.M pipe for print DEVICE: */</p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
__TOC__<br />
=== GT.M pipe for print DEVICE: ===<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simple, secure, and elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:OTHER rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. For example, one can write: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103". Set it to give us 12 characters/inch, 8 lines/inch and a 1 inch left margin). And then set IO to that device." <br />
<br />
FileMan will then send his output to that IO device, the just-defined pipe. <br />
<br />
Finally, the POST-CLOSE EXECUTE simply closes the pipe. And it's gone. No Linux /tmp/print.txt file to clean up. No fuss, no muss. <br />
<br />
--[[User:JohnLeoZ|JohnLeoZ]] 15:57, 12 Aug 2009 (CDT)<br />
<br />
----<br />
[[pipe to identify CUPS printers]]<br />
<br />
=== VistA output to a temporary Linux file (Calling ^TMGPRNTR) ===<br />
<br />
Below is an older way of setting up a Linux printer.<br />
<br />
Here is the DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
--[[User:Kdtop|Kdtop]] 10:34, 18 Sep 2005)<br />
----<br />
=== '''Linux /tmp/file (With ZSYSTEM call)''' ===<br />
<br />
On a Linux system with CUPS.<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----</div>JohnLeoZhttps://vistapedia.com/index.php?title=Pipe_to_identify_CUPS_printers&diff=5669Pipe to identify CUPS printers2009-08-15T12:35:12Z<p>JohnLeoZ: </p>
<hr />
<div>Here is a code snippet that uses the pipe device to query Linux for the names of available CUPS printers. It returns them in an MUMPS array.<br />
<br />
lpstat(DEVICE) ;;<br />
;; (CUPS has been configured with<br />
;; the desired printers defined.)<br />
;;Sample run:<br />
;; GTM>d lpstat^testing(.jlz)<br />
;; GTM>zwr<br />
;; jlz=""<br />
;; jlz("HP_LaserJet_1100A")=""<br />
;; jlz("Photosmart_192.168.5.103")=""<br />
;;<br />
New P Set P="pipe"<br />
Open P:(command="lpstat -a")::P<br />
For Use P Read DEVICE Quit:$ZEOF Do<br />
. Set DEVICE($P(DEVICE," "))=""<br />
. Quit<br />
Close P<br />
Quit</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Installation&diff=5686CPRS Installation2009-08-14T12:31:17Z<p>JohnLeoZ: </p>
<hr />
<div>__TOC__<br />
=== CPRS Versions ===<br />
<br />
This will list links for the various CPRS versions. (Most current at the top)<br />
<br />
{| class="grey" border="1" cellpadding="2"<br />
|+ CPRS Versions<br />
|-<br />
! Version Number<br />
! Distribution File<br />
! Availability<br />
! Date<br />
|-<br />
| version 1.0.27.83 <br />
| OR_30_304.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 05/2009<br />
|-<br />
| version 1.0.27.77 <br />
| OR_30_243.ZIP <br />
| ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_SINCE_2008/<br />
| 09/2008<br />
|-<br />
| version 1.0.26.69 <br />
| OR_30_270.zip<br />
| on http://opensourcevista.net:8888/NancysVistAServer and on ftp://ftp.va.gov/vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/<br />
|-<br />
| version 1.0.26.69 <br />
| for WorldVistA EHR <br />
| on the Sourceforge WorldVistA EHR site and http://opensourcevista.net:8888/NancysVistAServer <br />
| (dated June 2007)<br />
<br />
|-<br />
| version 1.0.26.68<br />
| OR_30_258.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| Note Below (NB):(dated July 17, 2006)<br />
|-<br />
| version 1.0.25.42<br />
| OR_30_235.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety<br />
|-<br />
| version 1.0.25.40 <br />
| OR_30_231.zip<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated May 06, 2005)<br />
|-<br />
| version 1.0.25.28 <br />
| OR_30_195.zip <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Feb 09, 2005)<br />
|-<br />
| version 1.0.24.27<br />
| OR_30_224.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Sep 03, 2004)<br />
|-<br />
| version 1.0.24.26<br />
| OR_30_190.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated Aug 02, 2004)<br />
|-<br />
| version 1.0.23.15 <br />
| OR_30_187.ZIP <br />
| *Sourceforge WorldVistA and http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 02/04)<br />
|-<br />
| version 1.0.22.16<br />
| OR_30_206.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 01/04)<br />
|-<br />
| version 1.0.20.21 <br />
| OR_30_148.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 11/02)<br />
|-<br />
| version 1.0.20.21<br />
| OR_30_148.ZIP<br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
|(dated about 11/02)<br />
|-<br />
| version 1.0.19.7 <br />
| OR_30_132.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 05/02)<br />
|-<br />
| version 1.0.18.2 <br />
| OR_30_125.ZIP <br />
| http://opensourcevista.net:8888/NancysVistAServer<br />
| (dated about 12/01)<br />
|}<br />
<br />
=== version change trick ===<br />
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:<br />
<br />
http://downloads.opensourcevista.net/VADemo9-26-06<br />
<br />
<br />
To find out which version to use, look next to the option OR CPRS GUI Chart like this where 1.0.23.15 was needed:<br />
D Q^DI<br />
<br />
VA FileMan 22.0<br />
Select OPTION: 5 INQUIRE TO FILE ENTRIES<br />
<br />
OUTPUT FROM WHAT FILE: DEVICE// OPTION<br />
1 OPTION (10126 entries)<br />
2 OPTION SCHEDULING (116 entries)<br />
CHOOSE 1-2: 1 OPTION (10126 entries)<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15<br />
ANOTHER ONE: <br />
<br />
To use a particular version of CPRS, the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory <br />
<br />
Thus: <br />
<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
The wget(1) utility is capable of fetching the files from this server<br />
<br />
AceFTP is a freeware FTP program that works, if needed<br />
http://software.visicommedia.com/en/productsfreeware/<br />
<br />
''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''<br />
<br />
+++ Since 1.0.26.76 is not released, in this case, version 1.0.26.69 can be used by changing the option in the option file like this:<br />
<br />
D P^DI<br />
<br />
VA FileMan 22.0<br />
<br />
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES<br />
<br />
INPUT TO WHAT FILE: OPTION//<br />
EDIT WHICH FIELD: ALL//<br />
<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.26.76<br />
NAME: OR CPRS GUI CHART//<br />
MENU TEXT: CPRSChart version 1.0.26.76 Replace 76 With 69<br />
Replace<br />
CPRSChart version 1.0.26.69<br />
<br />
<br />
=== Automatic Windows Installer ===<br />
<br />
The [http://sourceforge.net/projects/worldvistaautoi/files Astronaut] suite of automatic installers includes cprs, tmg-cprs and many other clients, available in point-click windows .exe installers. IP address and port number are entered by the user. <br />
=== Wine/Crossover compatability ===<br />
<br />
[[Wine/Crossover]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5666Setting up a VISTA Printer2009-08-13T21:10:43Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
__TOC__<br />
=== GT.M pipe for print DEVICE: ===<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simple, secure, and elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:OTHER rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. For example, one can write: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103". Set it to give us 12 characters/inch, 8 lines/inch and a 1 inch left margin). And then set IO to that device." <br />
<br />
FileMan will then send his output to that IO device, the just-defined pipe. <br />
<br />
Finally, the POST-CLOSE EXECUTE simply closes the pipe. And it's gone. No Linux /tmp/print.txt file to clean up. No fuss, no muss. <br />
<br />
--[[User:JohnLeoZ|JohnLeoZ]] 15:57, 12 Aug 2009 (CDT)<br />
<br />
----<br />
<br />
=== VistA output to a temporary Linux file (Calling ^TMGPRNTR) ===<br />
<br />
Below is an older way of setting up a Linux printer.<br />
<br />
Here is the DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
--[[User:Kdtop|Kdtop]] 10:34, 18 Sep 2005)<br />
----<br />
=== '''Linux /tmp/file (With ZSYSTEM call)''' ===<br />
<br />
On a Linux system with CUPS.<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5659Setting up a VISTA Printer2009-08-13T11:49:36Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
<br />
<br />
== 1.) VistA output to a temporary linux file: ==<br />
<br />
(But see here [[GT.M pipe for print DEVICE:]] for the better way to print, neat and clean without the temporary file kludge.) JL.Z<br />
----<br />
'''A.) Calls to Routine ^TMGPRNTR'''<br />
<br />
Here is my DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
------------------------------------------<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
<br />
---------------------------------------------------------------------------<br />
---------------------------------------------------------------------------<br />
<br />
'''B.) Bare bones print via a Linux /tmp/file'''<br />
<br />
On a Linux system with CUPS.<br />
<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
----<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----<br />
----<br />
<br />
== 2.) [[GT.M pipe for print DEVICE:]] ==<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simpler, more secure, even elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:Other rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. Thus one could do: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103" with the previously mentioned details set, and then set IO to that device." FileMan will then send his output to IO. Finally the POST-CLOSE just closes the pipe. No Linux /tmp/print.txt file to clean up. No fuss, no muss. '''What's not to love?!?!'''<br />
<br />
<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 22:30, 12 Aug 2009 (CDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=GT.M_pipe_for_print_DEVICE:&diff=11530GT.M pipe for print DEVICE:2009-08-13T11:41:17Z<p>JohnLeoZ: /* 2.) GT.M pipe for print DEVICE: */</p>
<hr />
<div><br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simpler, more secure, even elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:Other rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. Thus one could do: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103" with the previously mentioned details set, and then set IO to that device." FileMan will then send his output to IO. Finally the POST-CLOSE just closes the pipe. No Linux /tmp/print.txt file to clean up. No fuss, no muss. '''What's not to love?!?!'''<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 06:40, 13 Aug 2009 (EDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=GT.M_pipe_for_print_DEVICE:&diff=5657GT.M pipe for print DEVICE:2009-08-13T11:40:03Z<p>JohnLeoZ: </p>
<hr />
<div>== 2.) GT.M pipe for print DEVICE: ==<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simpler, more secure, even elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:Other rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. Thus one could do: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103" with the previously mentioned details set, and then set IO to that device." FileMan will then send his output to IO. Finally the POST-CLOSE just closes the pipe. No Linux /tmp/print.txt file to clean up. No fuss, no muss. '''What's not to love?!?!'''<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 04:40, 13 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5658Setting up a VISTA Printer2009-08-13T03:33:06Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
<br />
<br />
== 1.) VistA output to a temporary linux file: ==<br />
<br />
<br />
----<br />
'''A.) Calls to Routine ^TMGPRNTR'''<br />
<br />
Here is my DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO='''$$GETJOBNM^TMGPRNTR()'''<br />
POST-CLOSE EXECUTE: DO '''FINISH^TMGPRNTR("laughlin_laser")'''<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
------------------------------------------<br />
<br />
Here are the supporting calls to routine ^TMGPRNTR that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
<br />
---------------------------------------------------------------------------<br />
---------------------------------------------------------------------------<br />
<br />
'''B.) Bare bones print via a Linux /tmp/file'''<br />
<br />
On a Linux system with CUPS.<br />
<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
----<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
----<br />
----<br />
<br />
== 2.) GT.M pipe for print DEVICE: ==<br />
<br />
With the introduction of the pipe device to GT.M (version V5.3-003) this simpler, more secure, even elegant method can be used:<br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <pipe><br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr"")::""pipe"" s IO=""p"""<br />
POST-CLOSE EXECUTE: X "c ""p""" <br />
SUBTYPE: P-OTHER80<br />
TYPE: OTHER<br />
<br />
Note: We use TYPE:Other rather than Host File Server. No host file needed; output will be "piped" to the default CUPS printer. Also the fancy stuff is in the PRE-OPEN EXECUTE. Thus one could do: <br />
<br />
PRE-OPEN EXECUTE: X "o ""p"":(command=""lpr -P Photosmart_@192.168.5.103 -o cpi=12 -o lpi=8 -o page-left=72"")::""pipe"" s IO=""p"""<br />
<br />
In human (ok in geekspeak), this last PRE-OPEN EXECUTE says, "Open a pipe device named "p" with the command to print to the CUPS printer named "Photosmart_@192.168.5.103" with the previously mentioned details set, and then set IO to that device." FileMan will then send his output to IO. Finally the POST-CLOSE just closes the pipe. No Linux /tmp/print.txt file to clean up. No fuss, no muss. '''What's not to love?!?!'''<br />
<br />
<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 22:30, 12 Aug 2009 (CDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5656Setting up a VISTA Printer2009-08-13T02:30:19Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
<br />
<br />
Here is my DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO=$$GETJOBNM^TMGPRNTR()<br />
POST-CLOSE EXECUTE: DO FINISH^TMGPRNTR("laughlin_laser")<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
------------------------------------------<br />
<br />
Here are the supporting routine calls that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
<br />
---------------------------------------------------------------------------<br />
---------------------------------------------------------------------------<br />
<br />
Here is another, more bare bones DEVICE to print from GT.M.<br />
<br />
It's running on an Ubuntu Linux system with CUPS.<br />
<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
----<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -r /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
Note: This DEVICE does not require the calls to ^TMGPRNTR. And, by exposing the lpr call in the POST-CLOSE EXECUTE, it allows more flexibility. For example, this relatively simple change will direct output to the default CUPS printer with 12 characters/inch, 8 lines/inch and a 1 inch left margin. :<br />
<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -o cpi=12 -o lpi=8 -o page-left=72 -r /tmp/""_$J_""print.txt"""<br />
<br />
<br />
<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 19:30, 12 Aug 2009 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=Setting_up_a_VISTA_Printer&diff=5655Setting up a VISTA Printer2009-08-13T02:09:18Z<p>JohnLeoZ: </p>
<hr />
<div>Back to [[Programming VistA Issues]]<br />
<br />
<br />
Here is my DEVICE file entry:<br />
<br />
NAME: S121-LAUGHLIN-LASER<br />
$I: <TO BE SET IN PRE-OPEN EX.> <br />
LOCATION OF TERMINAL: Laughlin_Office<br />
SUPPRESS FORM FEED AT CLOSE: YES <br />
PAGE LENGTH: 70 <br />
PRE-OPEN EXECUTE: SET IO=$$GETJOBNM^TMGPRNTR()<br />
POST-CLOSE EXECUTE: DO FINISH^TMGPRNTR("laughlin_laser")<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
------------------------------------------<br />
<br />
Here are the supporting routine calls that create a file for writing, and then send the output file to the Linux lpr system<br />
<br />
<br />
GETJOBNM()<br />
;"Purpose: To create a unique printer job name. <br />
;" This will be used during a printing process<br />
;" that writes the printer file to the host file system, <br />
;" then passes file to Linux<br />
;" printing system.<br />
;"Output: Returns name of file to put output into<br />
<br />
;"UNIQUE will generate a filename based on time and job number<br />
;" i.e. 'Print-Job-628233034.tmp<br />
<br />
;"write !,"here in GETJOBNM^TMGPRNTR",!<br />
new cJobs set cJobs="PRINT JOBS"<br />
new Filename set Filename=$$UNIQUE^%ZISUTL("/tmp/Print-Job.tmp")<br />
<br />
;"Now store Filename for later transfer to Linux lpr<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
if index="" set index=1<br />
set ^TMP("TMG",cJobs,$J,index)=Filename<br />
<br />
;"write !,"Print job name will be:",Filename,!<br />
quit Filename ;"result returned by altering Filename<br />
<br />
<br />
FINISH(Printer)<br />
;"Purpose: to complete the printing process by sending the now-created file<br />
;" to Linux CUPS (the printing system).<br />
;"Note: The lpr system itself will delete this print file when <br />
;" done (option -r)<br />
;"Input: Printer OPTIONAL -- the name of the linux printer to send the job to.<br />
<br />
new cJobs set cJobs="PRINT JOBS"<br />
new index set index=$order(^TMP("TMG",cJobs,$J,""))<br />
new Filename set Filename=$get(^TMP("TMG",cJobs,$J,index))<br />
<br />
close IO<br />
kill IO(1,IO)<br />
<br />
kill ^TMP("TMG",cJobs,$J,index)<br />
if Filename'="" do<br />
. new CmdStr<br />
. set CmdStr="lpr "<br />
. if $get(Printer)'="" set CmdStr=CmdStr_"-P "_Printer<br />
. ;"option -r --> lpr deletes file after printing done.<br />
. set CmdStr=CmdStr_" -r "_Filename_" &"<br />
. ;"write !,"Here is where I call:",!,"ZSYSTEM "_CmdStr,!<br />
. zsystem CmdStr<br />
. ;"write "Back from zsystem. Returning to Fileman.",!<br />
<br />
quit<br />
<br />
<br />
---------------------------------------------------------------------------<br />
---------------------------------------------------------------------------<br />
<br />
Here is another, more bare bones DEVICE to print from GT.M.<br />
<br />
It's running on an Ubuntu Linux system with CUPS.<br />
<br />
<br />
NAME: PRINTSERVER <br />
$I: /tmp/vistaprint.txt<br />
LOCATION OF TERMINAL: lpr <br />
OPEN COUNT: 1<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -r /tmp/vistaprint.txt"""<br />
SUBTYPE: P-OTHER80 <br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
----<br />
And for an elaboration of this method <br />
<br />
NAME: HP-PHOTOSMART <br />
$I: <TO BE SET IN PRE-OPEN EXECUTE><br />
PRE-OPEN EXECUTE: S IO="/tmp/"_$J_"print.txt"<br />
POST-CLOSE EXECUTE: X "ZSYSTEM ""lpr -P Photosmart_@192.168.5.103 -l /tmp/""_$J_""print.txt"""<br />
SUBTYPE: P-OTHER80<br />
TYPE: HOST FILE SERVER<br />
<br />
<br />
<br />
<br />
<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 00:38, 12 Sep 2006 (CDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=VistA_Version_Control_is_Hard&diff=10216VistA Version Control is Hard2009-07-08T23:31:53Z<p>JohnLeoZ: </p>
<hr />
<div>People have suggested that we use a version control system for VistA countless times. However, VistA cannot just use git or subversion or whatever. Those systems cannot handle the way VistA's code is designed. This wiki article was copied in mass from a [http://medsphere.org/people/jon.tai/blog/2009/07/01/the-case-for-distributed-revision-control-in-the-vista-community post on the subject by Jonathan Tai]. In response to a [http://groups.google.com/group/Hardhats/browse_thread/thread/af94f540f527d10d Hardhats thread on the subject]<br />
<br />
For VistA development to really take off, we need distributed revision<br />
control and automated merging.<br />
<br />
Take Linux for example. Linux uses a distributed revision control<br />
system called git. Linus has a branch of Linux that is the "official"<br />
branch. This is called the "mainline". Everyone can make a copy of<br />
this branch and do their own development. So far, it sounds just like<br />
centralized revision control, but the difference between centralized and<br />
distributed is that you can commit to your own private branch. You<br />
don't need permission from anyone. With a centralized system like<br />
Subversion, you have to have commit access to the repository, so you<br />
start by submitting one-off patches here and there until you gain enough<br />
karma to be entrusted with commit access. This doesn't scale. More on<br />
this later...<br />
<br />
Getting back to the example, when you have done some development and are satisfied with it, you can publish your branch in a public location. You can then bring the branch to the official maintainer's attention, and request that he "merge" or "pull" your branch. This is another critical difference - with distributed version control, changes are *pulled*, not *pushed*. So the first time you request a merge, the maintainer can inspect your code closely. He may suggest changes. You can do those in your own branch (and each change is tracked because you can commit to your own branch) and re-submit your request. With a centralized system, you'd be sending a patch. If you're a frequent contributor, the maintainer may review your code less closely because he trusts you more, but the review process is built in.<br />
<br />
After a little re-working, the maintainer finally decides your code is<br />
worthy for merging. With automated merging, even if that maintainer has<br />
made changes to other parts of the codebase since you cloned his branch,<br />
when the maintainer merges your branch, your changes are brought in<br />
automatically. If other people have branched off *your* branch and<br />
those changes have been merged already, most distributed systems are<br />
smart enough to figure that out and only merge the unmerged revisions.<br />
Subversion has gotten a lot better at this recently, but in earlier<br />
versions, it was *terrible* at this.<br />
<br />
Another important point is that each branch is equal (at least on a<br />
technical level) - the maintainer's branch is only special because it's<br />
the maintainer's branch and is recognized by the community as the<br />
official branch. If the maintainer were to become disinterested in the<br />
software or otherwise unable to maintain it, or should you want to take<br />
the software in a different direction, your branch could just as easily<br />
become *the* branch. Getting back to the Linux example, each subsystem<br />
maintainer has his own tree - there are trees dedicated to filesystems,<br />
to memory managers, drivers, etc. There are also trees dedicated to<br />
stability, so they branch off an official Linux release and then only<br />
merge critical bugfixes from that point on. If you wanted a more stable<br />
version of Linux, you may follow that branch instead of the official<br />
mainline branch.<br />
<br />
So in the VistA world - imagine several distributions like WorldVistA,<br />
OpenVista, FOIA VistA, vxVistA, etc. Each would have their own<br />
mainline. We could have package branches - so the FileMan group might<br />
have their own branch that's distro-independent. All the distros would<br />
merge changes from the FileMan group to maintain a "shared core", while<br />
each distribution does their own application work. Provided that the<br />
code/data structures are compatible and the licenses are compatible, the<br />
distributions could merge changes across - so WorldVista could merge in<br />
the server-side OpenVista CIS patches to allow CIS to run against<br />
WorldVista. And most importantly, when OpenVista updates those patches,<br />
WorldVista could just merge the new changes. If automated merging<br />
worked properly, this would be very seamless and easy - no re-porting<br />
required.<br />
<br />
In fact, you could take it a step further. Each implementing site could<br />
choose to have (and maintain) their own branch. So a site might branch<br />
off of WorldVistA's mainline, make a few local mods, then merge new<br />
changes from WorldVista as time goes on. And if WorldVistA liked those<br />
local changes, they could merge in the other direction - the local<br />
changes are accepted back into the main distribution. For an<br />
all-volunteer distribution like WorldVistA, this may be the main source<br />
of their changes.<br />
<br />
So why don't we do all of this now? First of all, some of us are still<br />
using centralized revision control. That's what Ignacio was trying to<br />
address by starting this thread. Fixing this is the easy part -<br />
switching from a centralized model to a distributed model is fairly<br />
simple because the centralized model is just a subset of the distributed<br />
model. It's like having just one branch that everyone commits to.<br />
<br />
The second thing we need is automated merging. What we need to do is<br />
come up with a way to express VistA structures in a way that existing<br />
revision control tools can understand. Right now, a menu is stored in<br />
FileMan, which is stored as globals in a binary database file. A tool<br />
designed to handle source code can't handle that. It doesn't know how<br />
to merge two multi-gigabyte binary blobs to make a meaningful new<br />
version. We could export the database as plain text (e.g., %GO or<br />
ZWRITE format), but even that is not enough to allow automated merging<br />
because a menu might have a certain IEN at one site but another IEN at<br />
another site. The existing tools have no idea what's important and<br />
needs to be merged and what is site-specific and can be discarded. What<br />
we need is an abstract representation of a menu, similar to what KIDS<br />
has. If we can present these VistA structures to an existing tool, we<br />
can leverage the power of these existing tools to do development as a<br />
community more efficiently.<br />
<br />
From talking to various folks at the VistA Community Meetings, some<br />
thought has gone into how to do #2, but I haven't seen anything workable<br />
yet. For now, I agree with Ignacio that we should do what we can, i.e., #1. Standardize on a distributed revision control tool so we can build the tools for #2 around it.<br />
<br />
editors note: because this was copied from Medsphere.org, its creative commons license applies.<br />
<br />
<br />
----<br />
<br />
<br />
See also:[http://vistaexpertise.blogspot.com/2009/06/point-2-vista-requires-many-code.html VISTA Expertise Network]</div>JohnLeoZhttps://vistapedia.com/index.php?title=KT_Pharmacy_Setup_Howto&diff=9735KT Pharmacy Setup Howto2009-04-08T23:24:53Z<p>JohnLeoZ: /* ~ */</p>
<hr />
<div>Pharmacy Packages for Configuration<br />
<br />
<br />
1. Outpatient Pharmacy<br />
<br />
2. Inpatient Medications<br />
<br />
3. Bar Code Medication Administration (BCMA)<br />
<br />
4. Automatic Replenish/Ward Stock (AR/WS)<br />
<br />
5. Controlled Substances<br />
<br />
6. Pharmacy Data management (PDM)<br />
<br />
7. Drug Accountability - ?? Maybe configure<br />
<br />
8. National Drug File (NDF)<br />
<br />
9. Prescription Practices (PPP) – NOT CONFIGURED<br />
<br />
10. Electronic Claims Management Engine – NOT CONFIGURED DORMATE RELEASE<br />
<br />
11. Pharmacy Benefits Management (PBM) – NOT CONFIGURED<br />
<br />
12. Consolidated Mail Outpatient Pharmacy (CMOP) – NOT CONFIGURED<br />
<br />
<br />
<br />
Outpatient Pharmacy<br />
<br />
Required Packages:<br />
<br />
Accounts Receivable (AR) 4.5<br />
Adverse Reaction Tracking (ART) 4.0<br />
Clinical Information Resources Network (CIRN) 1.0<br />
Consolidated Mail Outpatient Pharmacy (CMOP) 2.0<br />
Computerized Patient Record System (CPRS) 3.0<br />
Decision Support System (DSS) 3.0<br />
Fee Basis 3.5<br />
VA FileMan 22.0<br />
Integrated Funds Control, Accounting, and Procurement<br />
(IFCAP) 5.0<br />
Inpatient Medications (IP) 5.0<br />
Integrated Billing (IB) 2.0<br />
Kernel 8.0<br />
Laboratory 5.2<br />
MailMan 7.1<br />
Master Patient Index/Patient Demographics (MPI/PD) 1.0<br />
National Drug File (NDF) 4.0<br />
Order Entry/Results Reporting (OERR) 3.0<br />
Patient Information Management System (PIMS) 5.3<br />
Pharmacy Data Management (PDM) 1.0<br />
Remote Procedure Call (RPC) Broker 1.1<br />
<br />
<br />
<br />
Outpatient Options used to define Outpatient Pharmacy:<br />
Site parameter Enter/Edit<br />
<br />
Site Name= WVOPharmacy<br />
<br />
Outpatient Parameters set:<br />
<br />
Jobs to be Queued for Outpatient Pharmacy:<br />
Must use option PSO AUTOQUEUE JOBS<br />
<br />
Menu’s<br />
<br />
OutPatient Package Corridinator – PSO MANAGER<br />
OutPatient Pharmacist – PSO USER1<br />
OutPatient Tech – PSO USER2<br />
<br />
Keys<br />
Archive Device<br />
=~=~=~=~=~=~=~= PuTTY log 2005.10.27 14:16:54 =~=~=~=~=~=~=~=<br />
WV oU OUTPATIENT<br />
Are you adding 'WV OUTPATIENT' as a new OUTPATIENT SITE (the 1ST)? No// Y<br />
(Yes)<br />
OUTPATIENT SITE SITE NUMBER: ??<br />
This field is used to show the site/station number.<br />
<br />
OUTPATIENT SITE SITE NUMBER: ???<br />
This field is used to show the site/station number.<br />
<br />
OUTPATIENT SITE SITE NUMBER: 007<br />
OUTPATIENT SITE INACTIVE DATE: <br />
Would you like to see all site parameters for this division? Y// ES [6;1H [1;1H [J [2J [H<br />
NAME: WV OUTPATIENT SITE NUMBER: 007<br />
<br />
<br />
NAME: WV OUTPATIENT// <br />
MAILING FRANK STREET ADDRESS: <br />
AREA CODE: <br />
PHONE NUMBER: <br />
MAILING FRANK ZIP+4 CODE: <br />
SITE NUMBER: 007// <br />
MAILING FRANK CITY: <br />
MAILING FRANK STATE: <br />
MAILING COMMENTS: <br />
INACTIVE DATE: <br />
HOLD FUNCTION?: ?<br />
Enter 'Y' if the 'Hold' feature will be used at the facility.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
HOLD FUNCTION?: 0 NO<br />
SUSPENSE FUNCTION?: ?<br />
Enter if the 'Suspense' feature will be used at the facility.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
SUSPENSE FUNCTION?: 0 NO<br />
CANCEL DRUG IN SAME CLASS: ?<br />
Enter yes if you wish prescriptions for drugs in the same class to be<br />
cancelled.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
CANCEL DRUG IN SAME CLASS: 0 NO<br />
REFILL INACTIVE DRUG RXS: ?<br />
Enter yes to allow refilling a prescription for a drug which is inactive.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
REFILL INACTIVE DRUG RXS: 1 YES<br />
ASK METHOD OF PICKUP: ?<br />
Enter yes to put special pickup instructions on window prescriptions.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
ASK METHOD OF PICKUP: 0 NO<br />
PASS MEDS ON PROFILE: ?<br />
Enter yes if pass meds should appear on the profile printed with new<br />
prescriptions<br />
Choose from: <br />
1 YES<br />
0 NO<br />
PASS MEDS ON PROFILE: 0 NO<br />
PROFILE `SORT BY' DEFAULT: ?<br />
Enter the default method of sorting medication profile.<br />
Choose from: <br />
0 DATE<br />
1 CLASS<br />
2 MEDICATION<br />
PROFILE `SORT BY' DEFAULT: 2 MEDICATION<br />
COPIES ON NEW: ?<br />
Enter yes to ask the number of copies of each label to be print.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
COPIES ON NEW: 0 NO<br />
DRUG CHECK FOR CLERK: ?<br />
Enter yes if clerks should see the duplicate drug warning during order<br />
entry.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
DRUG CHECK FOR CLERK: 0 NO<br />
FEE BASIS SUPPORT: ?<br />
Enter yes if your pharmacy processes prescriptions for Fee basis<br />
providers.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
FEE BASIS SUPPORT: 1 YES<br />
MULTI RX REQUEST FORM: ?<br />
Enter yes to print the multi RX request form.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
MULTI RX REQUEST FORM: 0 NO<br />
BARCODES ON REQUEST FORMS: ?<br />
Select whether you want barcodes on the single refill request, the<br />
multi-RX request form or both<br />
Choose from: <br />
0 REFILL REQUEST ONLY<br />
1 MULTI RX REQUEST ONLY<br />
2 BOTH<br />
BARCODES ON REQUEST FORMS: 2 BOTH<br />
BARCODES ON ACTION PROFILES: ?<br />
Enter 'Yes' if barcodes are to print with action profiles. Printer must<br />
be setup for barcodes.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
BARCODES ON ACTION PROFILES: 1 YES<br />
VERIFICATION: ?<br />
Answer yes if prescriptions entered by a technician must be verified by a<br />
pharmacist.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
VERIFICATION: 1 YES<br />
DISPLAY GROUP: ?<br />
Choose the display group which will be used to display the prescription<br />
ready messages.<br />
DISPLAY GROUP: ???<br />
This field is used to determine which bingo board display screen will<br />
be shown on the waiting room monitor.<br />
<br />
DISPLAY GROUP: <br />
SCREEN PROFILES: ??<br />
This field is used to determine if profiles are displayed when refilling<br />
and renewing medications.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
SCREEN PROFILES: 0 NO<br />
EDIT PATIENT DATA: ??<br />
This field is used to determine if editing of patient data will be allow<br />
ed.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
EDIT PATIENT DATA: 1 YES<br />
EDIT DRUG: ??<br />
This field will be used to determine if drugs can be changed during<br />
the prescription edit option.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
EDIT DRUG: 0 NO<br />
RENEWING RX'S ALLOWED: ??<br />
This field will be used to determine if renewing of medications will be<br />
allowed.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
RENEWING RX'S ALLOWED: 1 YES<br />
PASS MEDS CANCEL: ??<br />
This field is used to determine if pass medications are to be cancelled.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
PASS MEDS CANCEL: 1 YES<br />
AUTO SUSPEND: ??<br />
This field is used to determine if medication that is refilled or renewe<br />
d<br />
before the next possible fill date is to be placed <br />
in suspense automatically.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
AUTO SUSPEND: 0 NO<br />
SHALL COMPUTER ASSIGN RX #S: ??<br />
This field is used to determine if the computer will auto generate<br />
prescription numbers.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
SHALL COMPUTER ASSIGN RX #S: 1 YES<br />
PROFILE WITH NEW PRESCRIPTIONS: ??<br />
This field is used to determine if medication profiles are printed when<br />
new medication is ordered.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
PROFILE WITH NEW PRESCRIPTIONS: 0 NO<br />
SLAVED LABEL PRINTING: ??<br />
This field will be used to allow printing of RX labels without being<br />
able to queue to a printer. This parameter is primarily for slaved<br />
printing of RX labels. If 'yes' is the answer the prompt for action<br />
to be taken on the label will include the '/PRINT' action.<br />
<br />
Choose from: <br />
1 YES<br />
0 NO<br />
SLAVED LABEL PRINTING: 0 NO<br />
METHADONE PROGRAM: ??<br />
This field will be used to determine if the site has a methadone program<br />
<br />
and if a particular drug should be prompted for.<br />
<br />
Choose from: <br />
0 NO<br />
1 YES<br />
METHADONE PROGRAM: 0 NO<br />
METHADONE DRUG: ?? <br />
DAYS TO PULL FROM SUSPENSE: ??<br />
This field will be used to pull a patient's medication from suspense for<br />
a specified number of days. The day range is from 0 to 10.<br />
<br />
THIS NUMBER IS DIVISION SPECIFIC.<br />
<br />
DAYS TO PULL FROM SUSPENSE: 10<br />
DAYS TO PULL SUSPENDED CS CMOP: ??<br />
This field will be used to pull a patient's controlled substances from<br />
suspense for CMOP medications for a specified number of days. The range<br />
is between 0 and 10.<br />
<br />
DAYS TO PULL SUSPENDED CS CMOP: 0<br />
NEW LABEL STOCK: ?<br />
If new medication label stock will be used enter '1' for Yes.<br />
Choose from: <br />
1 YES<br />
0 NO<br />
NEW LABEL STOCK: 1 YES<br />
EXTERNAL INTERFACE: ??<br />
This field allows sites to alter the characteristics of the external<br />
interface. The Set of Codes field have the following values:<br />
<br />
0 - the external interface is off<br />
1 - send all drugs to the external interface; print labels locally<br />
2 - send all drugs to the external interface; don't print labels locally<br />
3 - send only marked drugs to the external interface; don't print labels<br />
locally<br />
4 - send only marked drugs to external interface and print labels throug<br />
h<br />
VistA.<br />
<br />
Choose from: <br />
0 INTERFACE TURNED OFF<br />
1 SEND ALL ORDERS AND PRINT LABEL<br />
2 SEND ALL ORDERS AND DON'T PRINT LABEL<br />
3 SEND MARKED ORDERS AND DON'T PRINT<br />
4 SEND MARKED ORDERS AND PRINT LABEL<br />
EXTERNAL INTERFACE: 0 INTERFACE TURNED OFF<br />
Select DISPENSING SYSTEM PRINTER: ?? <br />
You may enter a new DISPENSING SYSTEM PRINTER, if you wish<br />
'^' TO STOP: This field identifies the name of the printer(s) that, when selected, an<br />
d<br />
the interface is in use, an HL7 message is generated to the dispensing<br />
system.<br />
<br />
<br />
Choose from:<br />
BROWSER (CIRN) Text Browser Utility NUL <br />
BROWSER CACHE/NT HFS/CRT USER$:[TEMP]DDBR.TXT <br />
BROWSER DSM/VMS HFS/CRT DDBR.TXT <br />
BROWSER MSM/DOS HFS/CRT 51 <br />
BROWSER MSM/NT HFS/CRT 51 <br />
DG FIELD MONITOR DG field editing protocol DG FIELD MONITOR <br />
FAUX PRINTER LAT TERMINAL LC- <br />
GMRA UPDATE RESOURCE Allergy update control GMRA UPDATE RESOURCE <br />
<br />
GTM-UNIX-NULL Bit Bucket (GT.M-Unix) /dev/null <br />
HDIS STATUS RESOURCE DEVICE Resource Device HDIS STATUS RESOURCE DE<br />
VICE <br />
HDIS VUID RESOURCE DEVICE Resource Device HDIS VUID RESOURCE DEVICE<br />
<br />
HFS Host File Server USER$:[TEMP]TMP.DAT <br />
IMAGING WORKSTATION BROKER WS.DAT <br />
MESSAGE P-MESSAGE-HFS-MSM/DOS HFS (MSM/DOS) FILE => MESSAGE 51 <br />
<br />
MESSAGE P-MESSAGE-HFS-MSM/NT HFS (MSM/NT) FILE => MESSAGE 51 <br />
'^' TO STOP: MESSAGE P-MESSAGE-HFS-OPENM-NT HFS (OpenM-NT) FILE => MESSAGE V:\P<br />
LATINUM\XMHFS.TMP <br />
MESSAGE P-MESSAGE-HFS-VXD HFS (VXD) FILE => MESSAGE XMHFS.DAT <br />
MSM/HFS Host File Server 51 <br />
NULL-DSM Bit Bucket _NLA0: <br />
OR MOVEMENT RESOURCE OR movement event process OR MOVEMENT RESOURCE<br />
<br />
OR WINDOWS HFS OR Windows Print HFS Device ORWINDEV.DAT <br />
OR WORKSTATION OR Workstation HFS Device ORDEV.DAT <br />
ORB NOTIFICATION RESOURCE OE/RR notifications ORB NOTIFICATION RESO<br />
URCE <br />
ORW THREAD RESOURCE CPRS GUI background data retrieval ORW THREAD R<br />
ESOURCE <br />
ORW/PXAPI RESOURCE CPRS to PCE transactions ORW/PXAPI RESOURCE <br />
SCCV RESOURCE Scheduling Conversion Resource Device SCCV RESOURCE <br />
<br />
VIC CARD REGISTRATION FAUX <br />
XDRBROWSER1 HFS/CRT USER$:[TEMP]XDRBR.TXT <br />
<br />
Select DISPENSING SYSTEM PRINTER: <br />
BLANK LABEL BETWEEN PATIENTS: ?<br />
Choose from: <br />
0 NO<br />
1 YES<br />
BLANK LABEL BETWEEN PATIENTS: 1 YES<br />
VERIFYING PHARMACIST ON LABELS: ?<br />
Enter Yes to print the Verifying Pharmacist number on Outpatient labels.<br />
Choose from: <br />
1 YES<br />
VERIFYING PHARMACIST ON LABELS: 1 YES<br />
AUTOMATED DISPENSE: ??<br />
This field will determine what version of the automated dispense machine<br />
<br />
this site is running. If the machine is older than HL7 V.2.4, enter <br />
letter O, if HL7 V.2.4 has been installed, enter 2.4.<br />
<br />
Choose from: <br />
0 Less than V2.4<br />
2.4 HL7 V.2.4<br />
AUTOMATED DISPENSE: <br />
FILE RELEASE DATE/TIME: ??<br />
This field is used to indicate if the release date/time is to be filed f<br />
or<br />
the prescription dispensed by an external interface.<br />
<br />
Choose from: <br />
1 YES<br />
FILE RELEASE DATE/TIME: 1 YES<br />
ENABLE MASTER FILE UPDATE: ??<br />
This field will determine if the automated dispense machines are ready t<br />
o <br />
receive HL7 V.2.4 messages.<br />
<br />
Choose from: <br />
N NO<br />
Y YES<br />
ENABLE MASTER FILE UPDATE: <br />
DISPENSE DNS NAME: ??<br />
THIS IS THE DNS COMPUTER NAME OF THE AUTOMATED DISPENSING MACHINE THAT I<br />
S <br />
USED FOR THIS OUTPATIENT SITE DIVISION.<br />
<br />
DISPENSE DNS NAME: <br />
DISPENSE DNS PORT: <br />
Select CPRS ORDERING INSTITUTION: ? <br />
You may enter a new CPRS ORDERING INSTITUTION, if you wish<br />
Enter the Institution for this Outpatient site for CPRS orders.<br />
<br />
Answer with INSTITUTION NAME, or STATUS, or STATION NUMBER, or<br />
OFFICIAL VA NAME, or CURRENT LOCATION, or CODING SYSTEM/ID PAIR, or<br />
NAME (CHANGED FROM), or CODING SYSTEM<br />
Do you want the entire INSTITUTION List? Y (Yes)<br />
Choose from:<br />
AUSTIN 200 <br />
BVA/VBA SUPPORT OFFICE DC BVA/VBA-SO 397 <br />
OFFICE OF INFORMATION SRV CNTR 776 <br />
SOFTWARE SERVICE VAO 050 <br />
VISN 1 VISN <br />
VISN 10 VISN <br />
VISN 11 VISN <br />
VISN 12 VISN <br />
VISN 13 VISN <br />
VISN 14 VISN <br />
VISN 15 VISN <br />
VISN 16 VISN <br />
VISN 17 VISN <br />
VISN 18 VISN <br />
VISN 19 VISN <br />
VISN 2 VISN <br />
VISN 20 VISN <br />
VISN 21 VISN <br />
VISN 22 VISN <br />
VISN 23 VISN <br />
'^' TO STOP: VISN 3 VISN <br />
VISN 4 VISN <br />
VISN 5 VISN <br />
VISN 6 VISN <br />
VISN 7 VISN <br />
VISN 8 VISN <br />
VISN 9 VISN <br />
<br />
Select CPRS ORDERING INSTITUTION: SOFTWARE SERVICE VAO 050 <br />
Are you adding 'SOFTWARE SERVICE' as <br />
a new CPRS ORDERING INSTITUTION (the 1ST for this OUTPATIENT SITE)? No// Y<br />
(Yes)<br />
LOGICAL LINK: <br />
Select CPRS ORDERING INSTITUTION: <br />
RELATED INSTITUTION: ??<br />
Institution associated with the site.<br />
<br />
<br />
Choose from:<br />
AUSTIN 200 <br />
BVA/VBA SUPPORT OFFICE DC BVA/VBA-SO 397 <br />
OFFICE OF INFORMATION SRV CNTR 776 <br />
SOFTWARE SERVICE VAO 050 <br />
VISN 1 VISN <br />
VISN 10 VISN <br />
VISN 11 VISN <br />
VISN 12 VISN <br />
VISN 13 VISN <br />
VISN 14 VISN <br />
VISN 15 VISN <br />
VISN 16 VISN <br />
VISN 17 VISN <br />
VISN 18 VISN <br />
VISN 19 VISN <br />
VISN 2 VISN <br />
VISN 20 VISN <br />
VISN 21 VISN <br />
VISN 22 VISN <br />
'^' TO STOP: VISN 23 VISN <br />
VISN 3 VISN <br />
VISN 4 VISN <br />
VISN 5 VISN <br />
VISN 6 VISN <br />
VISN 7 VISN <br />
VISN 8 VISN <br />
VISN 9 VISN <br />
<br />
RELATED INSTITUTION: ??<br />
RELATED INSTITUTION: ??<br />
RELATED INSTITUTION: ?<br />
Answer with INSTITUTION NAME, or STATUS, or STATION NUMBER, or<br />
OFFICIAL VA NAME, or CURRENT LOCATION, or CODING SYSTEM/ID PAIR, or<br />
NAME (CHANGED FROM), or CODING SYSTEM<br />
Do you want the entire INSTITUTION List? Y (Yes)<br />
Choose from:<br />
AUSTIN 200 <br />
BVA/VBA SUPPORT OFFICE DC BVA/VBA-SO 397 <br />
OFFICE OF INFORMATION SRV CNTR 776 <br />
SOFTWARE SERVICE VAO 050 <br />
VISN 1 VISN <br />
VISN 10 VISN <br />
VISN 11 VISN <br />
VISN 12 VISN <br />
VISN 13 VISN <br />
VISN 14 VISN <br />
VISN 15 VISN <br />
VISN 16 VISN <br />
VISN 17 VISN <br />
VISN 18 VISN <br />
VISN 19 VISN <br />
VISN 2 VISN <br />
VISN 20 VISN <br />
VISN 21 VISN <br />
VISN 22 VISN <br />
VISN 23 VISN <br />
'^' TO STOP: VISN 3 VISN <br />
VISN 4 VISN <br />
VISN 5 VISN <br />
VISN 6 VISN <br />
VISN 7 VISN <br />
VISN 8 VISN <br />
VISN 9 VISN <br />
<br />
RELATED INSTITUTION: SOFTWARE SERVICE VAO 050 <br />
LABEL/PROFILE MONITOR MAX: ??<br />
Maximum number of label/profiles to be stored in the Label/Profile<br />
Monitor list for each printer device. The default and minimum value<br />
for this number is 1000. Each time the printer is used an entry is<br />
made in the Label/Profile monitor and if the monitor holds more<br />
entries than specified by this parameter, the oldest entry is<br />
deleted.<br />
<br />
LABEL/PROFILE MONITOR MAX: 100000<br />
NARCOTICS NUMBERED DIFFERENTLY: ?<br />
Choose from: <br />
1 YES<br />
0 NO<br />
NARCOTICS NUMBERED DIFFERENTLY: 1 YES<br />
NARCOTIC LOWER BOUND: 10000<br />
NARCOTIC UPPER BOUND: 49 499999<br />
PRESCRIPTION # LOWER BOUND: 10 250 300000<br />
PRESCRIPTION # UPPER BOUND: 3999 4000000<br />
IB SERVICE/SECTION: ?<br />
Answer with SERVICE/SECTION NAME, or ABBREVIATION, or MAIL SYMBOL, or<br />
TYPE OF SERVICE, or MIS COSTING CODE:<br />
IRM <br />
<br />
IB SERVICE/SECTION: ???<br />
Select the appropriate entry in the Service/Section file (#49) that is<br />
to be used for the Pharmacy Copayment/Integrated Billing procedures.<br />
<br />
Answer with SERVICE/SECTION NAME, or ABBREVIATION, or MAIL SYMBOL, or<br />
TYPE OF SERVICE, or MIS COSTING CODE:<br />
IRM <br />
<br />
IB SERVICE/SECTION: ??<br />
IB SERVICE/SECTION: IRM <br />
<br />
Entry in this field must match the SERVICE field for pharmacy action<br />
types in the IB ACTION TYPE file AND be a valid entry in your<br />
SERVICE/SECTION file to generate copay charges!<br />
<br />
??<br />
IB SERVICE/SECTION: IRM <br />
<br />
Entry in this field must match the SERVICE field for pharmacy action<br />
types in the IB ACTION TYPE file AND be a valid entry in your<br />
SERVICE/SECTION file to generate copay charges!<br />
<br />
??<br />
IB SERVICE/SECTION: ^<br />
<br />
Outpatient System Parameters<br />
<br />
DEFAULT OUTPATIENT SITE: ?<br />
Enter name of default site.<br />
Answer with OUTPATIENT SITE NAME, or SITE NUMBER, or<br />
RELATED INSTITUTION:<br />
WV OUTPATIENT 007 <br />
<br />
DEFAULT OUTPATIENT SITE: wv WV OUTPATIENT 007 <br />
ADMISSION CANCEL OF RXS: ?<br />
Choose from: <br />
1 YES<br />
0 NO<br />
ADMISSION CANCEL OF RXS: 0 NO<br />
Select EXEMPT WARD FROM AUTOCANCEL: ? <br />
DAYS PRINTED RX STAYS IN 52.5: ?<br />
Enter from 7 to 90 days printed Rx's are to remain in suspense during the<br />
purge option.<br />
DAYS PRINTED RX STAYS IN 52.5: 10<br />
POLYPHARMACY W/ACTION PROFILE: ?<br />
Enter '1' or Yes to indicate if a polypharmacy report is to print with<br />
action profiles.<br />
Choose from: <br />
1 YES<br />
POLYPHARMACY W/ACTION PROFILE: 1 YES<br />
<br />
Select SITE NAME: ?<br />
Answer with OUTPATIENT SITE NAME, or SITE NUMBER, or<br />
RELATED INSTITUTION:<br />
WV OUTPATIENT 007 <br />
<br />
You may enter a new OUTPATIENT SITE, if you wish<br />
ANSWER MUST BE 3-20 CHARACTERS IN LENGTH<br />
<br />
Select SITE NAME: WV OUTPATIENT 007 <br />
Would you like to see all site parameters for this division? Y// ES [10;1H [1;1H [J [2J [H<br />
NAME: WV OUTPATIENT SITE NUMBER: 007<br />
LABEL/PROFILE MONITOR MAX: 100000 BARCODES ON ACTION PROFILES: YES<br />
VERIFICATION: YES EDIT DRUG: NO<br />
RENEWING RX'S ALLOWED: YES PASS MEDS CANCEL: YES<br />
AUTO SUSPEND: NO SHALL COMPUTER ASSIGN RX #S: YES<br />
PROFILE WITH NEW PRESCRIPTIONS: NO DAYS TO PULL SUSPENDED CS CMOP: 0<br />
CANCEL DRUG IN SAME CLASS: NO REFILL INACTIVE DRUG RXS: YES<br />
ASK METHOD OF PICKUP: NO PASS MEDS ON PROFILE: NO<br />
PROFILE `SORT BY' DEFAULT: MEDICATION<br />
COPIES ON NEW: NO DRUG CHECK FOR CLERK: NO<br />
FEE BASIS SUPPORT: YES MULTI RX REQUEST FORM: NO<br />
BARCODES ON REQUEST FORMS: BOTH SCREEN PROFILES: NO<br />
EDIT PATIENT DATA: YES HOLD FUNCTION?: NO<br />
SUSPENSE FUNCTION?: NO SLAVED LABEL PRINTING: NO<br />
DAYS TO PULL FROM SUSPENSE: 10 NEW LABEL STOCK: YES<br />
EXTERNAL INTERFACE: INTERFACE TURNED OFF<br />
BLANK LABEL BETWEEN PATIENTS: YES VERIFYING PHARMACIST ON LABELS: YES<br />
NARCOTICS NUMBERED DIFFERENTLY: YES NARCOTIC LOWER BOUND: 10000<br />
NARCOTIC UPPER BOUND: 499999 METHADONE PROGRAM: NO<br />
PRESCRIPTION # LOWER BOUND: 300000 PRESCRIPTION # UPPER BOUND: 4000000<br />
FILE RELEASE DATE/TIME: YES RELATED INSTITUTION: SOFTWARE SERVICE<br />
CPRS ORDERING INSTITUTION: SOFTWARE SERVICE<br />
<br />
Enter RETURN to continue or '^' to exit: <br />
<br />
<br />
NAME: WV OUTPATIENT// <br />
MAILING FRANK STREET ADDRESS: <br />
AREA CODE: ^<br />
<br />
Outpatient System Parameters<br />
<br />
DEFAULT OUTPATIENT SITE: WV OUTPATIENT// <br />
ADMISSION CANCEL OF RXS: NO// <br />
Select EXEMPT WARD FROM AUTOCANCEL: 6 ??<br />
Select EXEMPT WARD FROM AUTOCANCEL: ^<br />
<br />
Select SITE NAME: <br />
Outpatient Pharmacy software - Version 7.0<br />
Select LABEL PRINTER: HOME// TELNET<br />
<br />
OK to assume label alignment is correct? YES// <br />
<br />
Select SITE NAME: <br />
Outpatient Pharmacy software - Version 7.0<br />
Select LABEL PRINTER: HOME// ^<br />
<br />
Select SITE NAME: ^<br />
Outpatient Pharmacy software - Version 7.0<br />
Select LABEL PRINTER: HOME// ^<br />
<br />
Select SITE NAME: ^<br />
Outpatient Pharmacy software - Version 7.0<br />
Select LABEL PRINTER: HOME// TELNET<br />
<br />
OK to assume label alignment is correct? YES// <br />
<br />
**> Sorry, access to your primary menu has been denied by the application.<br />
An XQUIT was encountered in the Entry Action code.<br />
Please see your computer person.<br />
<br />
Hit the "Enter" or "Return" Key to Continue<br />
<br />
<br />
Inpatient Medications<br />
<br />
Required Packages:<br />
<br />
<br />
<br />
<br />
INpatient Options used to define INpatient Pharmacy:<br />
Site parameter Enter/Edit<br />
<br />
Site Name= WVINPharmacy<br />
<br />
INpatient Parameters set:<br />
<br />
Jobs to be Queued for INpatient Pharmacy:<br />
<br />
Menu’s<br />
<br />
<br />
Keys<br />
<br />
Archive Device</div>JohnLeoZhttps://vistapedia.com/index.php?title=User:JohnLeoZ&diff=9491User:JohnLeoZ2009-04-08T23:21:23Z<p>JohnLeoZ: </p>
<hr />
<div>'''John Leo Zimmer''' is a retired family physician, and a long-time VistA advocate. He has been called affectionately ''<nowiki>gra'pa Z</nowiki>'' from his evident love for his grandsons, Mateo and Diego.<br />
<br />
User of DHCP and RPMS in private medical practice in the 80's and 90's.</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Versions&diff=9485CPRS Versions2008-10-07T12:01:02Z<p>JohnLeoZ: </p>
<hr />
<div>== CPRS Versions and corresponding OR patches ==<br />
<br />
<br />
<br />
version 1.0.18.2 ---> in the OR_30_125.ZIP (dated about 12/01)<br />
version 1.0.19.7 ---> in the OR_30_132.ZIP (dated about 5/02)<br />
version 1.0.20.21 ---> in the OR_30_148.ZIP (dated about 11/02)<br />
version 1.0.22.16 ---> in the OR_30_206.ZIP (dated about 1/04)<br />
version 1.0.23.15 ---> in the OR_30_187.ZIP (dated about 2/04)<br />
version 1.0.24.26 ---> in the OR_30_190.ZIP (dated Aug 2, 2004<br />
version 1.0.24.27 ---> in the OR_30_224.ZIP (dated Sep 3, 2004)<br />
version 1.0.25.28 ---> in the OR_30_195.zip (dated Feb 9, 2005)<br />
version 1.0.25.40 ---> in the OR_30_231.ZIP (dated MAY 05, 2005)<br />
version 1.0.25.42 ---> in the OR_30_235.ZIP (dated July 9,2005)<br />
version 1.0.26.66 ---> in the OR_30_215.ZIP (dated May 5, 2006) <br />
version 1.0.26.68 ---> in the OR_30_258.ZIP (dated July 17,2006)<br />
version 1.0.26.69 ---> in the [ftp://ftp.va.gov/Vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/Order%20Entry-Results%20Reporting%20-%20OR/OR_30_270.ZIP OR_30_270.ZIP] (dated 12/13/2007) [ftp://ftp.va.gov/Vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/Order%20Entry-Results%20Reporting%20-%20OR/OR_30_270_SRC.ZIP Source code]<br />
version 1.0.26.76 ---> in the [ftp://ftp.va.gov/Vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/Order%20Entry-Results%20Reporting%20-%20OR/OR_30_277.ZIP OR_30_277.ZIP] (dated 12/13/2007)<br />
<br />
These can be found here: <br />
<br />
[ftp://ftp.va.gov/Vista/Software/VISTA_FOIA_RELEASES_BEFORE_2008/Order%20Entry-Results%20Reporting%20-%20OR/]<br />
<br />
They used to be here: [ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_231_SRC.ZIP) will be found in the subdirectory <br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
Note: Mozilla & Firefox do not like the ftp://ftp.va.gov/ site; and give this error: <br />
The FTP server 215 MSDOS A N (FTPServer V4R2 by BisonWare International)<br />
is currently unsupported.<br />
MS Explorer and Konqueror function just fine. UPDATE: Firefox 3 seems to work fine with it also.</div>JohnLeoZhttps://vistapedia.com/index.php?title=Wine/Crossover&diff=11411Wine/Crossover2008-09-20T21:11:35Z<p>JohnLeoZ: </p>
<hr />
<div>[http://www.winehq.org/ Wine] is an open source reimplementation of the Windows API, a compatibility layer for running Windows programs on Linux. And [http://www.codeweavers.com/products/cxlinux/ Crossover] is Codeweavers' proprietary version of the same API.<br />
<br />
Although there are still points of failure, over several years now we have seen gradual reduction in the number of failures in attempts to run CPRS on Linux using Crossover.<br />
<br />
With the approach of CPRS 1.0.27.77 we anticipate another attempt to detail the remaining failures in the hope for a final push by our friends at Codeweavers to close the gap.<br />
<br />
== Places in CPRS where Wine/Crossover fail: ==<br />
<br />
1. Please add details here...<br />
<br />
2.<br />
<br />
3.<br />
<br />
Back to [[CPRS_Installation]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=Wine/Crossover&diff=5169Wine/Crossover2008-09-20T20:43:02Z<p>JohnLeoZ: </p>
<hr />
<div>[http://www.winehq.org/ Wine] is an open source reimplementation of the Windows API, a compatibility layer for running Windows programs on Linux. And [http://www.codeweavers.com/products/cxlinux/ Crossover] is Codeweavers' proprietary version of the same API.<br />
<br />
Although there are still points of failure, over several years now we have seen gradual reduction in the number of failures in attempts to run CPRS on Linux using Crossover.<br />
<br />
With the approach of CPRS 1.0.27.77 we anticipate another attempt to detail the remaining failures in the hope for a final push by our friends at Codeweavers to close the gap.<br />
<br />
== Places in CPRS where Wine/Crossover fail: ==<br />
<br />
1. Please add details here...<br />
<br />
2.<br />
<br />
3.<br />
<br />
--[[User:JohnLeoZ|gra'pa Z]] 13:43, 20 Sep 2008 (PDT)</div>JohnLeoZhttps://vistapedia.com/index.php?title=CPRS_Installation&diff=5260CPRS Installation2008-09-20T20:10:23Z<p>JohnLeoZ: </p>
<hr />
<div>__TOC__<br />
<br />
<br />
=== CPRS Versions ===<br />
<br />
This will list links for the various CPRS versions.<br />
<br />
{| class="grey" border="1" cellpadding="2"<br />
|+ CPRS Versions<br />
|-<br />
! Version Number<br />
! Distribution File<br />
! Availability<br />
! Date<br />
|-<br />
| version 1.0.27.77 <br />
| OR_30_243.ZIP <br />
| (not available yet)<br />
| 09/2008<br />
|-<br />
| version 1.0.26.69 <br />
| OR_30_270.zip<br />
| <br />
| (on VA ftp site)<br />
|-<br />
| version 1.0.26.69 <br />
| for WorldVistA EHR <br />
| on the Sourceforge WorldVistA EHR site<br />
| (dated June 2007)<br />
<br />
|-<br />
| version 1.0.26.68<br />
| OR_30_258.zip<br />
|<br />
| Note Below (NB):(dated July 17, 2006)<br />
|-<br />
| version 1.0.25.42<br />
| OR_30_235.zip<br />
| <br />
| (dated July 09, 2005) <br>Note: Replace .25.40 with .25.42 for patient safety<br />
|-<br />
| version 1.0.25.40 <br />
| OR_30_231.zip<br />
| <br />
| (dated May 06, 2005)<br />
|-<br />
| version 1.0.25.28 <br />
| OR_30_195.zip <br />
| <br />
| (dated Feb 09, 2005)<br />
|-<br />
| version 1.0.24.27<br />
| OR_30_224.ZIP <br />
|<br />
| (dated Sep 03, 2004)<br />
|-<br />
| version 1.0.24.26<br />
| OR_30_190.ZIP <br />
|<br />
| (dated Aug 02, 2004)<br />
|-<br />
| version 1.0.23.15 <br />
| OR_30_187.ZIP <br />
| *Nancy and Sourceforge WorldVistA have this one.<br />
| (dated about 02/04)<br />
|-<br />
| version 1.0.22.16<br />
| OR_30_206.ZIP <br />
|Nancy Anthracite has it.<br />
| (dated about 01/04)<br />
|-<br />
| version 1.0.20.21 <br />
| OR_30_148.ZIP <br />
|Nancy Anthracite has it.<br />
| (dated about 11/02)<br />
|-<br />
| version 1.0.20.21<br />
| OR_30_148.ZIP<br />
|Nancy Anthracite has it.<br />
|(dated about 11/02)<br />
|-<br />
| version 1.0.19.7 <br />
| OR_30_132.ZIP <br />
| Nancy Anthracite has it.<br />
| (dated about 05/02)<br />
|-<br />
| version 1.0.18.2 <br />
| OR_30_125.ZIP <br />
| Nancy Anthracite has it.<br />
| (dated about 12/01)<br />
|}<br />
<br />
<br />
<br />
<br />
<br />
=== version change trick ===<br />
NB: There is a trick to making version 1.0.26.68. It is done for you in CPRSDir.zip which can be found along with the instructions for creating it at:<br />
<br />
http://downloads.opensourcevista.net/VADemo9-26-06<br />
<br />
<br />
To find out which version to use, look next to the option OR CPRS GUI Chart like this where 1.0.23.15 was needed:<br />
D Q^DI<br />
<br />
VA FileMan 22.0<br />
Select OPTION: 5 INQUIRE TO FILE ENTRIES<br />
<br />
OUTPUT FROM WHAT FILE: DEVICE// OPTION<br />
1 OPTION (10126 entries)<br />
2 OPTION SCHEDULING (116 entries)<br />
CHOOSE 1-2: 1 OPTION (10126 entries)<br />
Select OPTION NAME: OR CPRS GUI CHART CPRSChart version 1.0.23.15<br />
ANOTHER ONE: <br />
<br />
To use a particular version of CPRS, the server-side software code must match. The files are found at ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ and the source code is in the "Programs" subdirectory of this directory <br />
<br />
Thus: <br />
<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/ <nowiki>ftp://ftp.va.gov/vista/Software/Packages/Order Entry-Results Reporting - OR/ </nowiki>]<br />
<br />
The Delphi source code for each of these (e.g. OR_30_235_SRC.ZIP) will be found in the subdirectory<br />
[ftp://ftp.va.gov/vista/Software/Packages/Order%20Entry-Results%20Reporting%20-%20OR/Programs/ <nowiki>...Packages/Order Entry-Results Reporting - OR/Programs/ </nowiki>]<br />
<br />
The wget(1) utility is capable of fetching the files from this server<br />
<br />
AceFTP is a freeware FTP program that works, if needed<br />
http://software.visicommedia.com/en/productsfreeware/<br />
<br />
''(In the past this FTP site could not be reached with Mozilla/Firefox. That has been corrected.)''<br />
<br />
=== Wine/Crossover compatability ===<br />
<br />
[[Wine/Crossover]]</div>JohnLeoZhttps://vistapedia.com/index.php?title=VistA_Community_Weekly_Conference_Call&diff=9372VistA Community Weekly Conference Call2008-03-16T22:34:42Z<p>JohnLeoZ: </p>
<hr />
<div>== VistA Community Weekly Conference Call ==<br />
<br />
<br />
Occurs on each Friday at 12:00 pm EST, 11 am CST, 9am PST. <br />
<br />
Focus of the call varies depending on the current needs and interests of the community. Topics are posted weekly on Hardhats. Recordings, mp3 or ogg, are sometimes available; ask on Hardhats.<br />
<br />
<br />
Starts: 12:00 Noon (EST) 03/14/2008<br />
Duration: 1 hour<br />
The community call is currently using FreeConferenceCall.com.<br />
The phone number and access code are provided below.<br />
Please note that the phone number is located in St. Louis, MO and is not toll free.<br />
Participants are encouraged to join the call using their preferred<br />
VOIP service (Vonage, Skype, etc.)<br />
<br />
Free Conference Call Conference Dial-in Number: (616) 712-8000<br />
Participant Access Code: 819555#<br />
When prompted enter the access code that has been assigned,<br />
followed by the # key.<br />
<br />
<br />
== 12 August 2005 ==<br />
I know this is a pretty weak effort at recording the events of today's call. But I think this may be the place to start logging some info from these calls. Please add, subtract, comment. --[[User:JohnLeoZ|gra'pa Z]] 21:54, 12 Aug 2005 (CDT)<br />
<br />
VistA CPRS is compatible with Dragon Dictate. <br />
Also, is being run on tablet pc's and handwriting recognition input to CPRS works "out of the box".<br />
Discussion of Putty and other methods of telnet and ssh terminal access.<br />
<br />
The VVSO test, elsewhere on this site, includes a beta version of VistA Office EHR.<br />
<br />
Wishlist: <br />
1 [http://www.linuxmednews.com/ Ignatio Valdez] is seeking collaboration for a grant application to advance VistA's HL7 functions to version 3.<br />
2 CPRS with built in option for ssh connection.<br />
3 ?<br />
<br />
== PodCasts ==<br />
<br />
For podcasts of<br />
[http://www.4vista.net/ past calls]<br />
<br />
(An old, 2006, experiment.)<br />
<br />
To obtain these mp3 files: Add this [http://sage.mozdev.org/ Sage plugin] to Firefox</div>JohnLeoZhttps://vistapedia.com/index.php?title=Recording_Results_Of_A_VistA_Community_Meeting&diff=10253Recording Results Of A VistA Community Meeting2008-03-16T22:09:42Z<p>JohnLeoZ: </p>
<hr />
<div></div>JohnLeoZ